I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
getochkn said:
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
Click to expand...
Click to collapse
Are you running a custom rom and/or kernel? Im wondering if this may have something to do with selinux. If not using one already, try flashing an insecure custom kernel. You might also want to try flashing CWM, just to see if it has the same issue.
DocHoliday77 said:
Are you running a custom rom and/or kernel? Im wondering if this may have something to do with selinux. If not using one already, try flashing an insecure custom kernel. You might also want to try flashing CWM, just to see if it has the same issue.
Click to expand...
Click to collapse
Thanks for the reply.
I'm not sure, I'm only running stock+root from the root66 package for the MK5 ROM for my phone from Wind in Canada. I tried installing CWM and it ran the first time, tried clearing cache to see if it had any permission/mount errors, and it froze, pulled the battery and wouldn't boot anymore. Had to reflash root66 package to get my phone to even boot. Rootchecker says I'm rooted fine, SU gives permissions to everything fine, busybox is fine. Donwload mode shows security bit disabled, so the root66 disabled knox. Not sure what to do try next.
EDIT
Installed CWM from ROM-Manager, and it worked, installed liewise ROM and it's working fine. I unno. lol.
getochkn said:
Thanks for the reply.
I'm not sure, I'm only running stock+root from the root66 package for the MK5 ROM for my phone from Wind in Canada. I tried installing CWM and it ran the first time, tried clearing cache to see if it had any permission/mount errors, and it froze, pulled the battery and wouldn't boot anymore. Had to reflash root66 package to get my phone to even boot. Rootchecker says I'm rooted fine, SU gives permissions to everything fine, busybox is fine. Donwload mode shows security bit disabled, so the root66 disabled knox. Not sure what to do try next.
EDIT
Installed CWM from ROM-Manager, and it worked, installed liewise ROM and it's working fine. I unno. lol.
Click to expand...
Click to collapse
Sorry that caused you so much trouble. When you are booted into recovery though, whether or not the rom is rooted makes no difference. What is important here is if the kernel is secure or insecure. I am still fairly certain selinux was causing you your problems with mounting though. If you are running any rom based on my Sprint ND8 port (such as likewise), you shouldn't have anymore problems (if I am correct about it being selinux of course). The kernel included has selinux disabled. Glad you got it working though.
Just curious, what do you mean by download mode shows security bit disabled? I think you might mean selinux? The warranty bit, which is often referred to as the knox counter cannot be disabled and is actually separate from Knox itself. Removing knox is something done only in the rom, not the kernel, and has no effect on what is shown in download mode. Also, selinux is not knox, they are two different technologies. Just fyi for future reference.
getochkn said:
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
Click to expand...
Click to collapse
how i did my wind s3 is
Unified_Android_Toolkit_v1.2.8 seemed to work for me
DocHoliday77 said:
Sorry that caused you so much trouble. When you are booted into recovery though, whether or not the rom is rooted makes no difference. What is important here is if the kernel is secure or insecure. I am still fairly certain selinux was causing you your problems with mounting though. If you are running any rom based on my Sprint ND8 port (such as likewise), you shouldn't have anymore problems (if I am correct about it being selinux of course). The kernel included has selinux disabled. Glad you got it working though.
Just curious, what do you mean by download mode shows security bit disabled? I think you might mean selinux? The warranty bit, which is often referred to as the knox counter cannot be disabled and is actually separate from Knox itself. Removing knox is something done only in the rom, not the kernel, and has no effect on what is shown in download mode. Also, selinux is not knox, they are two different technologies. Just fyi for future reference.
Click to expand...
Click to collapse
Ah. Maybe I was looking at the QualcomSecureboot or something
Either way, all is good. Not sure why TWRP gave problems or CWM did via Odin. I'm using likewise rom, which is based off your sprint so shouldn't have any more problems now anyways. Not a stranger to flashing Samsung phones, just my first newer samsung flash with this whole knox/selinus thing and all that. My old sammy S 4G was flashed hundreds of times while I worked on ROMs'. lol.
Rickyfk said:
how i did my wind s3 is
Unified_Android_Toolkit_v1.2.8 seemed to work for me
Click to expand...
Click to collapse
Be careful with that! I always advise against using it because it is very rarely updated, the op does not provide any support for it, and it has bricked several devices.
yes i forgot that in my post i always back ups of everything before i do anything.
i have also fixed bricked devices befor also but ya you have to be carful tho.
DocHoliday77 said:
Be careful with that! I always advise against using it because it is very rarely updated, the op does not provide any support for it, and it has bricked several devices.
Click to expand...
Click to collapse
i have the same problem
getochkn said:
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
Click to expand...
Click to collapse
my phone is wind T999V, rom is original JB 4.3.
i use root66 rom. i want to downgrade, i want to use twrp to copy system, but , all is no no no , sad.:crying:
welcome2you said:
my phone is wind T999V, rom is original JB 4.3.
i use root66 rom. i want to downgrade, i want to use twrp to copy system, but , all is no no no , sad.:crying:
Click to expand...
Click to collapse
Not sure what you mean there, sorry. But you cannot downgrade your firmware, but you can flash an older rom from TWRP.
DocHoliday77 said:
Not sure what you mean there, sorry. But you cannot downgrade your firmware, but you can flash an older rom from TWRP.
Click to expand...
Click to collapse
i want to use twrp,but cannot find partition, i want to downgrade to 4.1 ,then i can unlock my phone , but i have no way to finish it.
welcome2you said:
i want to use twrp,but cannot find partition, i want to downgrade to 4.1 ,then i can unlock my phone , but i have no way to finish it.
Click to expand...
Click to collapse
How are you trying to install TWRP? There are several ways to do so. Odin, recovery, Goo.Im app..... You can get the twrp files from my sig if you want to try those. No guarantee you will be able to unlock when flashing the 4.1.1 modem, let us know if it works for you.
I had tried TWRP through Odin flashable and also Goo Manager. I tried 2.7.0 and 2.7.1, both Tmo and Can version, and none could mount anything . CWM through Rom Manager works great though.
I know, from my experience working on ROM's and getting the first Heimdall flashable package to upgrade the Galaxy S 4G from Wind, that the Wind models of phones are slightly different than the Tmo versions. It took me a dev a while to find the right files, lots of soft bricking ,etc, to figure out the minute difference to allow Heimdall to flash a package, and even then, Heimdall could never flash a modem to the 4G-Wind Variant. I even tried working with the Heimdall dev to find out why, and never could. Modems would flash from CWM or TWRP, but not from the PC, even though Tmo firmwares and ROM's worked, so maybe the Wind phone is slightly different in partition layout that CWM can adapt for, but TWRP can't. Maybe I'll contact the TWRP team and see if I can help them figure out why, although now I'm working a lot more than I was and don't have a lot of time to flash my phone 100 times and brick it and flash again like in the older days.
getochkn said:
I had tried TWRP through Odin flashable and also Goo Manager. I tried 2.7.0 and 2.7.1, both Tmo and Can version, and none could mount anything . CWM through Rom Manager works great though.
I know, from my experience working on ROM's and getting the first Heimdall flashable package to upgrade the Galaxy S 4G from Wind, that the Wind models of phones are slightly different than the Tmo versions. It took me a dev a while to find the right files, lots of soft bricking ,etc, to figure out the minute difference to allow Heimdall to flash a package, and even then, Heimdall could never flash a modem to the 4G-Wind Variant. I even tried working with the Heimdall dev to find out why, and never could. Modems would flash from CWM or TWRP, but not from the PC, even though Tmo firmwares and ROM's worked, so maybe the Wind phone is slightly different in partition layout that CWM can adapt for, but TWRP can't. Maybe I'll contact the TWRP team and see if I can help them figure out why, although now I'm working a lot more than I was and don't have a lot of time to flash my phone 100 times and brick it and flash again like in the older days.
Click to expand...
Click to collapse
As far as partition layout goes, all of the T999 and I747 variants are the same. I believe the Sprint and Verizon ones are as well, but am not 100% confident in that. You said you tried the d2can and d2tmo versions, but what about d2lte? Everyone should be just using d2lte now as ALL the S3 models have been consolidated into that one. Where did you download it from btw? You can get it from the link in my sig. I know for sure it works. (I think I still need to add 2.7.0.1 though. But 2.7.0.0 is there.)
DocHoliday77 said:
As far as partition layout goes, all of the T999 and I747 variants are the same. I believe the Sprint and Verizon ones are as well, but am not 100% confident in that. You said you tried the d2can and d2tmo versions, but what about d2lte? Everyone should be just using d2lte now as ALL the S3 models have been consolidated into that one. Where did you download it from btw? You can get it from the link in my sig. I know for sure it works. (I think I still need to add 2.7.0.1 though. But 2.7.0.0 is there.)
Click to expand...
Click to collapse
I looked in your sig but don't see a D2LTE TWRP, only the 2.7.0 TMO one, which I downloaded from the official TWRP site, as well as 2.7.1 and neither worked. I also tried installing from Goo Manager. Maybe I'll try yours since it is a CWM flashable zip as opposed to an odin tarball and I have CWM working
getochkn said:
I looked in your sig but don't see a D2LTE TWRP, only the 2.7.0 TMO one, which I downloaded from the official TWRP site, as well as 2.7.1 and neither worked. I also tried installing from Goo Manager. Maybe I'll try yours since it is a CWM flashable zip as opposed to an odin tarball and I have CWM working
Click to expand...
Click to collapse
Ill have to double check that later. Been a while since I've flashed recovery. I know I am using the one in my repo though, so it should work fine whether its d2tmo or d2lte
Related
WARNING: Following any of these instructions WILL void your warranty,
and could possibly cause irreparable harm to your device (i.e. bricked)
If you do Not understand these risks, stop here and do Not proceed.
If you do Not know how to use Odin, stop here and do Not proceed.
This guide is ONLY for SGH-T999 variants that are ALREADY RUNNING android 4.3
If you do Not have a SGH-T999 variant, stop here and do Not proceed.
If you are Not currently running android 4.3, stop here and do Not proceed.
I am not responsible for anything that happens to your device. YOU chose to follow this guide.
I have the SGH-T999V (samsung galaxy S3, canada, Videotron)
I flashed the full 4.3 firmware from samsung-updates.com as soon as it became available ... and then I tried to root it the usual ways
However knox prevented the superSu app from running, and it closed immediately, and obviously root was Not available to any app
This method will obtain ROOT and REMOVE the knox garbage
note ... altho it is optional to remove knox, I have Not tested without removing knox and do Not know if root will work using this method (guide) with knox still installed !
I did NOT create this method ... I simply found it, read thru user comments, and used it
FULL CREDIT goes to
@upndwn4par for the method ... the thread is here
@Kaito95 for the Knox Removal script ... the thread is here
@Dees_Troy for the TWRP recovery
@Chainfire for SuperSu
as you can see, this method was for the AT&T, Rogers, Bell, Telus Samsung Galaxy S3 ... I747 variants, I believe
So here is how I achieved a successful root on 4.3 using the above method, with adjustments for our T999 variant
Using Method #2
1. Download required files
a) download Odin 3.07 to your PC
b) download the latest TWRP recovery for your device, in TAR format, to your PC
click on your device here
scroll down on your device page to the section called Download - Odin Flashable Tar
below that, click on the Select the latest .tar file from here link
scroll to the bottom of the files and click on the latest TAR version
note to d2tmo users ... thanks to @Perseus71 it has been noted that 2.6 versions may have issues on your device, and it is recommended that you choose the 2.5.0.0 TAR version
example: Mine looks like this: openrecovery-twrp-2.6.3.0-d2can.tar
note to T999V users ... both d2can and d2tmo work for our device ... I personally use d2can
c) download SuperSu 1.65 zip to your DEVICE
c) download Knox Removal zip to your DEVICE
2. Reboot into Download mode ... VolumeDOWN + Power + Home
Run Odin
make sure that re-partition is NOT checked!
click the PDA button and point to the TWRP recovery TAR file that you downloaded above
connect your device to the computer ... wait briefly
the COMM port in top left box should turn blue
click Start
when it is done, PASSED, and phone has rebooted, disconnect device
3. Reboot into Recovery mode ... VolumeUP + Power + Home
Flash (install) the Knox Remover zip
Flash (install) the SuperSu zip ... it is version 1.65, current is 1.80, so it will prompt us to update later :good:
Reboot System
4. Update SuperSu from the Play Store
5. Open SuperSu
it should prompt that it needs to update the binary
accept and let it update the binary the Normal way
6. Reboot
7. Enjoy rooted 4.3, knox-free :laugh: :good:
thanks again to @Perseus71 for noting that it is possible that the default Enforcing mode of SElinux may cause issues with the ability and/or performance of some root apps despite being granted root permission
if you are experiencing similar issues, he recommends that you check out the SELINUX Status Changer app.
[I have Not personally tested this app]
reserved
in case
You may also wish to mention the SELINUX Status Changer. Here's the Thread.
With it enabled, root won't be stable.
Ahem. First ?
EDIT - TWRP 2.6.x.x has trouble remounting and formatting /Data. You may wish to reccomend version 2.5.0.0
Perseus71 said:
You may also wish to mention the SELINUX Status Changer. Here's the Thread.
With it enabled, root won't be stable.
Ahem. First ?
EDIT - TWRP 2.6.x.x has trouble remounting and formatting /Data. You may wish to reccomend version 2.5.0.0
Click to expand...
Click to collapse
hi and thanks for your input
I just looked at that SELINUX Status Changer thread and will keep an eye on it ... but for now I won't add it cuz:
the dev says it is pre-alpha version
Mine is Enforcing and root seems stable and hasn't had any problems, yet ... 4 days so far
SElinux is here to stay, and there's a big difference between proper (Google) implementation and samching implementation ... root blocked by samching, but not by standard android enforcing #BAM
congrats on being first, lol
what kind of things are you referring to when you say that root won't be stable?
what is your device d2 id?
I haven't had any problems with twrp 2.6.3 for d2can
THAT is something I WILL add, for your specific device
any particular reason you're recommending all the way back to 2.5 instead of just earlier 2.6 version?
cLogic said:
what kind of things are you referring to when you say that root won't be stable?
what is your device d2 id?
I haven't had any problems with twrp 2.6.3 for d2can
THAT is something I WILL add, for your specific device
any particular reason you're recommending all the way back to 2.5 instead of just earlier 2.6 version?
Click to expand...
Click to collapse
I have D2TMO AKA SGH-T999. Yes this is specific to my variant. I tested all the 2.6.x versions to establish that the /Data Problem exists in all these versions.
As to Root, well, Certain apps such as Nandroid Manager, and other apps have difficulty performing Root operation despite SuperSU granting it. @Aerowinder has a lot of stories. May I suggest you please visit the D2TMO Leaked 4.3 Rom thread in development for more details ?
Perseus71 said:
I have D2TMO AKA SGH-T999. Yes this is specific to my variant. I tested all the 2.6.x versions to establish that the /Data Problem exists in all these versions.
As to Root, well, Certain apps such as Nandroid Manager, and other apps have difficulty performing Root operation despite SuperSU granting it. @Aerowinder has a lot of stories. May I suggest you please visit the D2TMO Leaked 4.3 Rom thread in development for more details ?
Click to expand...
Click to collapse
fair enough ... thanks again for your input ... OP updated
Did this to the letter and soft bricked as soon as I flashed the mod zip in twrp. Stuck on pulsing samsung logo.
Had to reflash. Tried twice just to be sure.
(T999) (root, 4.3 stock)
trepoman said:
Did this to the letter and soft bricked as soon as I flashed the mod zip in twrp. Stuck on pulsing samsung logo.
Had to reflash. Tried twice just to be sure.
(T999) (root, 4.3 stock)
Click to expand...
Click to collapse
what do you mean ... bricked as soon as you flashed mod zip? you mean the knox removal script?
not sure how that's even possible
if you see the pulsing logo, then you rebooted
your T999 is rooted?
meaning it was before, or everything was fine after you did it twice?
cLogic said:
what do you mean ... bricked as soon as you flashed mod zip? you mean the knox removal script?
not sure how that's even possible
if you see the pulsing logo, then you rebooted
your T999 is rooted?
meaning it was before, or everything was fine after you did it twice?
Click to expand...
Click to collapse
The native tether mod. Knox remover worked fine.
Phone is rooted, stock 4.3.
Flashed tether mod in twrp recovery, which succeed but phone would not boot past the pulsing Samsung afterwards (10 minutes of pulsing, never booted past that) nor would it boot to recovery. I could get to boot loader luckily. I pulled the battery and tried again, same thing. Flashed stock 4.3 in Odin to get phone alive, tried flashing tether mod again, exact same result and same solution. HTH.
So close to clicking buy now on a nexus 5...
trepoman said:
The native tether mod. Knox remover worked fine.
Phone is rooted, stock 4.3.
Flashed tether mod in twrp recovery, which succeed but phone would not boot past the pulsing Samsung afterwards (10 minutes of pulsing, never booted past that) nor would it boot to recovery. I could get to boot loader luckily. I pulled the battery and tried again, same thing. Flashed stock 4.3 in Odin to get phone alive, tried flashing tether mod again, exact same result and same solution. HTH.
So close to clicking buy now on a nexus 5...
Click to expand...
Click to collapse
ummm .. not sure what this tether mod is that you are talking about, but it's not part of this guide, lol
this guide simply flashes the knox removal script (to delete knox files) and superSu (to root)
cLogic said:
ummm .. not sure what this tether mod is that you are talking about, but it's not part of this guide, lol
this guide simply flashes the knox removal script (to delete knox files) and superSu (to root)
Click to expand...
Click to collapse
Confounded facts. Always kicking my ass.
This is what happens when I stay up too late and try to do too many things. Linked from another thread and had too many tabs open.
Delete.
Thanks for the post. Sadly, no dice for me. I was directed to this post after creating my own. I've really held off asking for help, but only conclusion I can come to is I got one of those phones that just flat out won't root. Tried everything I can think of. Samsung Galaxy s3, SGH-T999v, 4.3, Wind (Canada). The Odin steps worked, when I boot into recovery, just get the stock android recover menu (original issue I've been having). Nothing seems to work in the slightest.
So I followed this to the letter and it all went well. Except, while the device seems to be rooted, SuperSU seems to be granting permissions to apps, Root Check Pro reports the device is rooted... I still can't use any apps that require root access. GameCIH doesn't work. ROM Manager doesn't work. Nothing wants to work.
Why is this happening? Because every step seemed to go flawlessly. Also, I have no idea how to put it back to stock if I wanted to try and start over lol.
[EDIT]
Oh yeah. Pertinent information. Samsung Galaxy S3 T999V through Mobilicity (Canada) running 4.3.
Used the 2.5 tar rather than the 2.6.
Also set SElinux to permissive.
ksec said:
Thanks for the post. Sadly, no dice for me. I was directed to this post after creating my own. I've really held off asking for help, but only conclusion I can come to is I got one of those phones that just flat out won't root. Tried everything I can think of. Samsung Galaxy s3, SGH-T999v, 4.3, Wind (Canada). The Odin steps worked, when I boot into recovery, just get the stock android recover menu (original issue I've been having). Nothing seems to work in the slightest.
Click to expand...
Click to collapse
are you sure you're running stock 4.3 ? baseband MK5 ?
re-do the Odin steps, except uncheck the auto reboot option .. so that it stops after successfully pushing the recovery tar
unplug the phone from the pc .. it should still be in download mode
pull the battery
then put it back in
boot into recovery immediately
if you see the TWRP recovery, great!, complete the guide and you'll be knox free and rooted
if that worked then there are two files that you seem to still have that are putting stock recovery back on normal boot .. post results here and I'll find them for you
Ergonyx said:
So I followed this to the letter and it all went well. Except, while the device seems to be rooted, SuperSU seems to be granting permissions to apps, Root Check Pro reports the device is rooted... I still can't use any apps that require root access. GameCIH doesn't work. ROM Manager doesn't work. Nothing wants to work.
Why is this happening? Because every step seemed to go flawlessly. Also, I have no idea how to put it back to stock if I wanted to try and start over lol.
[EDIT]
Oh yeah. Pertinent information. Samsung Galaxy S3 T999V through Mobilicity (Canada) running 4.3.
Used the 2.5 tar rather than the 2.6.
Also set SElinux to permissive.
Click to expand...
Click to collapse
did you go into superSu and update it's binary?
what do you mean, exactly, by apps won't work ?
do they run? you said they are being granted permission.
how were they installed?
we're they restored using Titanium?
the 2.5 TWRP was recommended for tmobile users.. we are T999V, can use d2can 2.6.3.0 or d2tmo 2.6.3.1
cLogic said:
did you go into superSu and update it's binary?
what do you mean, exactly, by apps won't work ?
do they run? you said they are being granted permission.
how were they installed?
we're they restored using Titanium?
the 2.5 TWRP was recommended for tmobile users.. we are T999V, can use d2can 2.6.3.0 or d2tmo 2.6.3.1
Click to expand...
Click to collapse
I updated the the SuperSU binary.
The apps will open but when it attempts to do anything requiring root access it is denied or fails.
SuperSU and Knox were installed through the TWRP recovery boot thing as the guide specified. Other things were either installed from the app store or downloaded APK files. I didn't have Titanium at the time I attempted rooting my phone. Wasn't mentioned in the guide so I never got it. I have the basic version now from the play store now. As I'm sure you can tell, I've never rooted my device before. Always had a friend do it for me.
Should I just restore to a stock install (not sure how to do this) and then try again? Especially now that I know the 2.5 warning was specifically for T-Mobile users? Or can I just put the 2.6X version on my phone and try again? lol
it's working
@ cLogic
Thanks a lot man, thanks to you I successfully root my sgh-t999v (stock android 4.3)
I've managed to use GooManager from the Google Play store to install latest TWRP and to flash the 4.3 mod.
Having issues when trying this. I followed all the steps and received no errors. But when the SuperSu ap tries to open on my phone it crashes, the ap only phone is stable.
I have Tomo G3 4.3 Stock rom
Flashed the TW 2.5.0.0 version
Rebooted into the touch recovery
Ran Knox removal
Ran SuperSu
Booted
Knox is not in my list off apps
SuperSu does show
Cant not open supersu, updating binarys does not work since the app crashes.
(Edit)--> Redid the whole process but did not let the phone reboot during the TW flash and the Zip installs. Seemed to of fixed the issue. (Edit)
Thanks added
I flashed Stock 4.3 via Odin before coming across this guide and now my device seems to be stuck at the boot screen. My question is, if I haven't completely booted, can I reflash using the modified version of 4.3 (root, deodexed, knox removed)? Do I have any other options right now?
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!W0JHQKAK!pA52fCAkUxTMia9A21KL1TrR8bmJT10jhNlBvn5j-Mk
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Click to expand...
Click to collapse
Can you please PM @DocHoliday77 to help him build the Stock ROM for us? He does not have the AT&T Device, but can surely help us in building the ROM. Greatness of him!!
He may ask for some other files for building AT&T ROM for us. If he can build the ROM for us, then we dont have to take the pains of testing the CFG file!!
Thanks man!!
Thank you for sharing this. We'll be hard at work on this now
Sent from my SGH-I747 using XDA Premium 4 mobile app
bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
Click to expand...
Click to collapse
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
stoobie-doo said:
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
Click to expand...
Click to collapse
Wait until later tonight or tomorrow when enewman17 or docholiday release a flashable
Sent from my SGH-I747 using XDA Premium 4 mobile app
@bkong
Link is bad, clicking it links to a url with "..." in the middle
CNexus said:
@bkong
Link is bad, clicking it links to a url with "..." in the middle
Click to expand...
Click to collapse
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
bkong said:
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
Click to expand...
Click to collapse
you can't just flash an update.zip through stock recovery?
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Success!
used the odin flashable 4.3 file from http://forum.xda-developers.com/showthread.php?t=2722660 , went back to stock 4.3 and then used the OTA provided by the OP to get to 4.4.2
edit: please wait for the devs to work their magic to get fully working and easily flashable roms
Jakeuten said:
you can't just flash an update.zip through stock recovery?
Click to expand...
Click to collapse
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
could you make an update.zip for users with stock recovery as well?
bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Click to expand...
Click to collapse
OTA shouldn't wipe any of your data. The way it works is it patches the existing files on your device with any changes to bring it up to date. Shouldn't touch any user data at all.
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
It'll be recovery flashable. Im not sure yet if Ill be trying to create an Odin flashable one. Will need to have someone pull the system.img slightly differently if I do. (Would need to Odin flash 4.3, flash TWRP, boot straight to recovery and flash the OTA, then while still in recovery dump the partition.) Even then, no guarantee it would work quite right. These things can be a little finicky.
How is Knox blocking TWRP though? You should be able to flash that via Odin. Since you updated using the OTA though, every time you reboot, it will rewrite the stock recovery. So when you flash TWRP via Odin, uncheck the Auto Reboot box, then after the flash is successful, pull the battery. Then put it back in and boot straight to recovery and flash your rom.
Jakeuten said:
could you make an update.zip for users with stock recovery as well?
Click to expand...
Click to collapse
I will try. No guarantees though. Its been a long time since I've messed with OTA's, so I'm not completely sure I will remember exactly what to do with it. I should be able to do it though. Just not making promises!
bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
stoobie-doo said:
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
Click to expand...
Click to collapse
Tempted to try it (flash through stock recovery) but not my phone lol
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
DocHoliday77 said:
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
Click to expand...
Click to collapse
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Just tried and ADB sideload of this file to my S3. After renaming the .cfg file to .zip.
I get an "assert failed" on "getprop("ro.product.device") == "d2att""
Any suggestions? I'm wondering if the phone is reporting something other than d2att?
So no one tested this via stock recovery? Need to know if the update can be done through stock recovery.
stoobie-doo said:
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Click to expand...
Click to collapse
Just tried this method.
I got the assert failure again, and it happily wiped my internal SD but didn't install the OTA.
Good thing I'm not using this device for anything critical, I'd be rather pissed off.
Hi all, new to all of this. Please keep this in mind as you read this thread.
Well first of all I have been reading about Cyanogenmod and how it helps saves battery. I also wanted to use cputuner to overclock my phone a little. I have in the past rooted this phone and installed cputuner not knowing that it could damage your phone if you didn't have a custom kernel that supported overclocking. After I found that out I uninstalled it and unrooted in fear of damage to my phone. Anyways I have a few questions and was looking knowledge, resources, and help about a few things.
Questions:
Is installing a custom rom and things needed to install a custom rom possible with a PC?
Can I safely reroot my device since I unrooted through #SU?
What do I need to do besides reroot my device in order to install a custom rom? (Cyanogenmod)
Thanks in advance!
Other INFO:
My device is a Samsung Galaxy S3 I-747
Firmware 4.4.2 KitKat
Device was rooted before using towelroot but I unrooted using #SU.
.
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
jason2678 said:
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
KentuckyGuy447 said:
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
Click to expand...
Click to collapse
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
dawgdoc said:
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
Click to expand...
Click to collapse
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
KentuckyGuy447 said:
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
Click to expand...
Click to collapse
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
dawgdoc said:
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
Click to expand...
Click to collapse
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
KentuckyGuy447 said:
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
Click to expand...
Click to collapse
I'm stuck.
You can install a custom recovery without having root, if you have a PC. You would use either Odin, Heimdall, or maybe adb.
You can install a custom recovery without a PC if you have root. You would use an app Like Flashify, Rom Manager, or Goo Manager (if it still exists).
You can flash a rom without a PC if you have a custom recovery, root is not needed.
Some roms, usually stock, can be flashed without a custom recovery if you have a PC.
I don't know the solution until you have access to a PC. I could see it being possible using a live USB with persistence of a Linux distribution, but you still have need for a PC. It's been a while since I created a live USB. The method I used required a small installation on the PC. so I don't see this as an immediate solution for you.
Oh sorry. I don't think towelroot works once you're on nj1, unless it has been updated.
If you get access to a PC, rooting is still fairly easy. You can use download mode and odin or heimdall to flash a custom recovery (be sure to uncheck reboot if using odin, or be really ready to pull battery). Don't let your phone reboot normally, you'll have to pull battery once odin is done.
Reboot to custom recovery, then flash supersu and you'll be rooted again, and set up to do whatever you want with your phone.
Sent from my LG-V410 using XDA Free mobile app
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
KentuckyGuy447 said:
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
Click to expand...
Click to collapse
excuse for butting in .... but if you dont know your bootloader/modem info. here is an app called 'samsung info' that should tell you.
your question "...... but theres no bootloader for my phone model right?" kinda worried me. its important to know because they should match AND trying to downgrade can brick your device. on the plus side ; i've never seen a custom ROM include bootloader/modem in it.
again , just a thought and not trying to butt in.:good:
https://www.dropbox.com/s/4ka74x02tg1rrn1/org.vndnguyen.phoneinfo-1.apk?dl=0
"all i can really do , is stay out of my own way and let the will of heaven be done"
As mrrocketdog stated, the Samsung Info app will tell you your bootloader and modem. If what you previously stated is correct, they should both be NJ1. You can get the same info by issuing these commands in a terminal emulator on the phone:
Code:
getprop ro.bootloader
and
Code:
getprop | grep version.baseband
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
KentuckyGuy447 said:
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
Click to expand...
Click to collapse
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
You have lifted a burden off my shoulders friend! Ever since I wanted to flash a custom Rom I've been worried if my phones bootloader was locked! I can now be at ease now that I know its unlocked. Will check upon that info about bootloader/modem.
Here is the info mrrocketdog
Is there a reason you can't use a PC to install a ROM?
I'm asking because I also do not know of a way to install a ROM without having root.
If you are able to root, you could try using the CM installer again.
audit13;5898140 said:
Thanks friend no worries, mrrocketdog helped me figure it out, than to all who helped!
Click to expand...
Click to collapse
KentuckyGuy447 said:
Here is the info mrrocketdog
Click to expand...
Click to collapse
Those are the latest versions of the bootloader and modem. You will be good for CM 12 or CM 11, and other custom ROMs based on CM. Older versions will work with them, but you probably need to edit the updater-script. (The older versions are not likely to include the NJ1 versions in the checks as they were not out when the ROMs were last updated.) NJ1 will also work with any of the ROMs based on the KitKat TouchWiz releases by Samsung.
As soon as you can find a PC to borrow you should be in business. Any chance of using one at a public library?
Appreciate all the help you gave me too friend, providing the links to cm and gapps, gonna borrow my friends laptop Sunday and try to root flash C-F Root through Odin. Thats the part that scares me but I should be good as people has confirmed it works for NJ1. Wish me luck friend. Would you recommend installing CM12? I personally like kit Kat and I know CM11 is based on that but is CM12 better? I guess its based on Lollipop
I got a Galaxy S3 SPH-L710 and it was all ready updated to the L710VPUDOH1 baseband version. After searching around a little bit I noticed that most of the Roms are for baseband L710VPUDND8 and that some of the ND8 roms would not flash correctly.
I guess maybe i found a workaround for this. When i first tried to flash the CM 12.1 Rom I got error and it did not load. Did not hurt anything either. Was a little tricky getting initial root but got it all working.
Figured id share how i accomplished this in case someone else with the L710VPUDOH1 baseband wants to run the other Roms.
First i tried to root with Odin and the supersu.zip but it didnt take correctly.
Odin showed successful and the supersu flashed to the /system but every time i tried to run supersu I get Unfortunately SuperSU stopped working.
So i ended up using ODIN to get Temp CWM recovery and installed the CF-Autoroot in the CWM recovery. This woorked to get Root.
I downloaded the TWRP manager from playstore andused it to install TWRP 2.8.1.0
The TWRP Manager gave me an error but when i booted into recovery I had TWRP.
After that i tried to flash CM 12.1 in TWRP but got error and it didnt work.
I read that wicked 2.2 would load,
its big all most a gig so i figured it was pretty complete. maybe based off of stock.
I loaded it successfully.
afterwards i booted back into twrp and did an advanced wipe of.
Dalvic Cache
/ system
/data
/internal storage
/cache
Then i loaded Cm 12.1 with no issues.
Tested Pac-Rom No issues.
Im thinking any of the newer roms will flash fine now.
BigCountry907 said:
After that i tried to flash CM 12.1 in TWRP but got error and it didnt work.
Click to expand...
Click to collapse
I'm hoping you left out some steps, because if you tried flashing CM 12.1 without doing a wipe on System/Data/Cache/Dalvik then you will not have a working phone.
BigCountry907 said:
I got a Galaxy S3 SPH-L710 and it was all ready updated to the L710VPUDOH1 baseband version. After searching around a little bit I noticed that most of the Roms are for baseband L710VPUDND8 and that some of the ND8 roms would not flash correctly.
I guess maybe i found a workaround for this. When i first tried to flash the CM 12.1 Rom I got error and it did not load. Did not hurt anything either. Was a little tricky getting initial root but got it all working.
Figured id share how i accomplished this in case someone else with the L710VPUDOH1 baseband wants to run the other Roms.
First i tried to root with Odin and the supersu.zip but it didnt take correctly.
Odin showed successful and the supersu flashed to the /system but every time i tried to run supersu I get Unfortunately SuperSU stopped working.
So i ended up using ODIN to get Temp CWM recovery and installed the CF-Autoroot in the CWM recovery. This woorked to get Root.
I downloaded the TWRP manager from playstore andused it to install TWRP 2.8.1.0
The TWRP Manager gave me an error but when i booted into recovery I had TWRP.
After that i tried to flash CM 12.1 in TWRP but got error and it didnt work.
I read that wicked 2.2 would load,
its big all most a gig so i figured it was pretty complete. maybe based off of stock.
I loaded it successfully.
afterwards i booted back into twrp and did an advanced wipe of.
Dalvic Cache
/ system
/data
/internal storage
/cache
Then i loaded Cm 12.1 with no issues.
Tested Pac-Rom No issues.
Im thinking any of the newer roms will flash fine now.
Click to expand...
Click to collapse
I don't think the roms care if your on ND8 or NJ2 or whatever the latest is . You should also update twrp to 2.8.7.0 . Version 2.8.4.0 and on allow you to flash a new twrp version image right from recovery . 2.8.1.0 is pretty old . Best of luck with your new hobby .
Ya i didnt have any troubles.
Im currently working on 5 devices and writing sort of a kitchen.
But it dose way more than most kitchens. Even creates a CWM style backup over adb like onandroid.
I found a way to patch a factory recovery.img to flash files signed with my own keys and that kinda started it all.
Anyway Merry Christmas
what's the root method for DOH1? ;; I can't seem to find a thread specifically walking through the root method for the latest baseband and i have an old S3 and was thinking of playing around with it for a while for fun turn it into a light weight media player to save battery on my LG G4 since we all know how inconsistent and crap the battery can be with the G4 lol
The root is pretty easy.
I used this.
http://forum.xda-developers.com/showthread.php?t=1963812
Then just get Clockworkmod or TWRP recovery for the d2spr sphl710 and flash it.
After that load any rom you want
silvernirvash said:
what's the root method for DOH1? ;; I can't seem to find a thread specifically walking through the root method for the latest baseband and i have an old S3 and was thinking of playing around with it for a while for fun turn it into a light weight media player to save battery on my LG G4 since we all know how inconsistent and crap the battery can be with the G4 lol
Click to expand...
Click to collapse
Same as always, use odin to flash a .tar of twrp. Then use twrp to flash a .zip of SuperSU. Done
Doh1
Is there any rom working at Doh1 version?
bael616 said:
Is there any rom working at Doh1 version?
Click to expand...
Click to collapse
All of them
madbat99 said:
All of them
Click to expand...
Click to collapse
Really? I have been told there was nothing for the l710vpudoh1 version. Would you mind to help me out with this topic of flashing a rom, please? P.D: Sorry about my english.
bael616 said:
Really? I have been told there was nothing for the l710vpudoh1 version. Would you mind to help me out with this topic of flashing a rom, please? P.D: Sorry about my english.
Click to expand...
Click to collapse
Oh1 is not a version of the phone. It's just a build number.
Do you have the triband model? What carrier?
madbat99 said:
Oh1 is not a version of the phone. It's just a build number.
Do you have the triband model? What carrier?
Click to expand...
Click to collapse
Got no idea. It is the sprint CDMA version.
bael616 said:
Got no idea. It is the sprint CDMA version.
Click to expand...
Click to collapse
Well that's what you need to know. Oh1 doesn't matter. There is oh1 for regular s3 and triband s3. Regular is sph-L710 and triband is sph-L710t. Does it have a t at the end of the model number?
madbat99 said:
Well that's what you need to know. Oh1 doesn't matter. There is oh1 for regular s3 and triband s3. Regular is sph-L710 and triband is sph-L710t. Does it have a t at the end of the model number?
Click to expand...
Click to collapse
It doesn't have any t. So I guess it Ies the regular one. I want to know how to root it and flash a rom.
bael616 said:
It doesn't have any t. So I guess it Ies the regular one. I want to know how to root it and flash a rom.
Click to expand...
Click to collapse
To root, you need odin on your PC. You can get it here.
Use odin to flash twrp recovery. You can get twrp from their site. twrp
Get the .tar of the newest build for d2spr (sprint s3). Put it on you PC somewhere you can find it (download folder is fine)
There are tutorials everywhere for using odin. It's the way to root almost all Samsung phones.
You also need the Samsung drivers on your PC. I don't have a link for that at this moment.
Then launch odin on your PC.
Put phone in download mode (from powered off, hold power+home+volume down)
Plug phone in to PC and odin should say "added"
Click AP button in odin then navigate to where you have the Twrp .tar downloaded and select it
Click start in odin.
When it finishes it should say pass.
Don't let the phone boot to system, unplug it and take out battery
Put batter back in and boot directly to twrp recovery by holding power+home+VOLUME UP
In twrp select reboot, then system. It should say you don't have root and ask if you want root. Swipe the arrow for yes. Once it boots, open SuperSU and update binaries if it asks. Choose normal method.
Done. Rooted.
You should really have looked up how to root before coming to a thread about flashing roms. There are tutorials everywhere for rooting this phone. Google is your friend dude.
Edit: you can get the Samsung USB drivers here
That thread has rooting instructions too. It's for the virgin Mobile s3, but its the same phone. Those instructions work fine. Only difference is I linked you to twrp recovery instead of philztouch (philz development is dead) and I linked you to a newer odin.
If you are that new that you aren't sure about rooting, maybe start over there in Android forums. I'm a guide there.
bael616 said:
Really? I have been told there was nothing for the l710vpudoh1 version. Would you mind to help me out with this topic of flashing a rom, please? P.D: Sorry about my english.
Click to expand...
Click to collapse
I was given a SPH-L710... Originally purchased from sprint.... Currently activated on boost. I got the phone Dec. 24 2015. It had stock unrooted DOH1 with untripped warranty bit. I have successfully booted and ran these roms for a minimum of 24 hrs each. As far as I could tell they were fully functional including: 4G LTE, MMS send and recieve, hotspot, wifi, bluetooth, camera (still and video). All main fuctions worked correctly for the limited time that I used each rom. :
-Wicked-X-Bare-Bones.zip
-Wicked-X-v8.2.zip
-cm-11-20150831_SNAPSHOT-XNG3CAO3FN-d2lte.zip
-cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
-cm-12.1-20160202-NIGHTLY-d2spr.zip
-cm-13.0-20160130-UNOFFICIAL-d2spr.zip
Im currently running CM13 unofficial as a daily driver. Cm12.1 SNAPSHOT was also very responsive and gave me no problems. I flashed them with twrp.2.8.7.2-d2spr.img. i flashed the recovery with odin after i made it into a .tar.md5 using linux mint 17.3 cinnamon. For the lte and mms i used "apn backup and restore" from google play with the root explorer method. Open gapps aroma for each android version i got from cyanogenmod website. i would recommend searching and using the dd command with adb shell in a linux terminal or cygwin to backup every partition on your doh1 first. (You will need root and busybox) There should be 24 partitions in mmcblk0. Make a backup of every one and you can recover one way or another ALMOST regardless of what may or may not go wrong. I used supersu 2.65 zip. Ive had alot of issues due to DOH1 but all the resources are in that easily used omnibox. Hope any of this info helps you.
madbat99 said:
To root, you need odin on your PC. You can get it here.
Use odin to flash twrp recovery. You can get twrp from their site. twrp
Get the .tar of the newest build for d2spr (sprint s3). Put it on you PC somewhere you can find it (download folder is fine)
There are tutorials everywhere for using odin. It's the way to root almost all Samsung phones.
You also need the Samsung drivers on your PC. I don't have a link for that at this moment.
Then launch odin on your PC.
Put phone in download mode (from powered off, hold power+home+volume down)
Plug phone in to PC and odin should say "added"
Click AP button in odin then navigate to where you have the Twrp .tar downloaded and select it
Click start in odin.
When it finishes it should say pass.
Don't let the phone boot to system, unplug it and take out battery
Put batter back in and boot directly to twrp recovery by holding power+home+VOLUME UP
In twrp select reboot, then system. It should say you don't have root and ask if you want root. Swipe the arrow for yes. Once it boots, open SuperSU and update binaries if it asks. Choose normal method.
Done. Rooted.
You should really have looked up how to root before coming to a thread about flashing roms. There are tutorials everywhere for rooting this phone. Google is your friend dude.
Edit: you can get the Samsung USB drivers here
That thread has rooting instructions too. It's for the virgin Mobile s3, but its the same phone. Those instructions work fine. Only difference is I linked you to twrp recovery instead of philztouch (philz development is dead) and I linked you to a newer odin.
If you are that new that you aren't sure about rooting, maybe start over there in Android forums. I'm a guide there.
Click to expand...
Click to collapse
Thanks a lot. I have already rooted the phone but now I want to know what Roms are made to this device.
---------- Post added at 05:28 AM ---------- Previous post was at 05:24 AM ----------
HouseHG said:
I was given a SPH-L710... Originally purchased from sprint.... Currently activated on boost. I got the phone Dec. 24 2015. It had stock unrooted DOH1 with untripped warranty bit. I have successfully booted and ran these roms for a minimum of 24 hrs each. As far as I could tell they were fully functional including: 4G LTE, MMS send and recieve, hotspot, wifi, bluetooth, camera (still and video). All main fuctions worked correctly for the limited time that I used each rom. :
-Wicked-X-Bare-Bones.zip
-Wicked-X-v8.2.zip
-cm-11-20150831_SNAPSHOT-XNG3CAO3FN-d2lte.zip
-cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
-cm-12.1-20160202-NIGHTLY-d2spr.zip
-cm-13.0-20160130-UNOFFICIAL-d2spr.zip
Im currently running CM13 unofficial as a daily driver. Cm12.1 SNAPSHOT was also very responsive and gave me no problems. I flashed them with twrp.2.8.7.2-d2spr.img. i flashed the recovery with odin after i made it into a .tar.md5 using linux mint 17.3 cinnamon. For the lte and mms i used "apn backup and restore" from google play with the root explorer method. Open gapps aroma for each android version i got from cyanogenmod website. i would recommend searching and using the dd command with adb shell in a linux terminal or cygwin to backup every partition on your doh1 first. (You will need root and busybox) There should be 24 partitions in mmcblk0. Make a backup of every one and you can recover one way or another ALMOST regardless of what may or may not go wrong. I used supersu 2.65 zip. Ive had alot of issues due to DOH1 but all the resources are in that easily used omnibox. Hope any of this info helps you.
Click to expand...
Click to collapse
Thanks man is there any link you can share with me? I really want to flash a rom but there is no one with this device in Facebook groups. So if you can share any Rom and the way it should be flashed I will be really thankful.
P. D: as I mentioned before I have no perfect English skills so I hope you understand what I mean.
bael616 said:
Thanks a lot. I have already rooted the phone but now I want to know what Roms are made to this device.
---------- Post added at 05:28 AM ---------- Previous post was at 05:24 AM ----------
Thanks man is there any link you can share with me? I really want to flash a rom but there is no one with this device in Facebook groups. So if you can share any Rom and the way it should be flashed I will be really thankful.
P. D: as I mentioned before I have no perfect English skills so I hope you understand what I mean.
Click to expand...
Click to collapse
I cant post links due to my total number of posts. PM me and I'll send them to you.
bael616 said:
Thanks a lot. I have already rooted the phone but now I want to know what Roms are made to this device.
---------- Post added at 05:28 AM ---------- Previous post was at 05:24 AM ----------
Thanks man is there any link you can share with me? I really want to flash a rom but there is no one with this device in Facebook groups. So if you can share any Rom and the way it should be flashed I will be really thankful.
P. D: as I mentioned before I have no perfect English skills so I hope you understand what I mean.
Click to expand...
Click to collapse
You have the sprint s3, but are you on sprint? If you are not on Sprint there are additional instructions. Any rom that says its for D2spr is fine. That's the sprint s3.
this is the one I'm using.
HouseHG said:
I cant post links due to my total number of posts. PM me and I'll send them to you.
Click to expand...
Click to collapse
Ok man thanks
---------- Post added at 01:39 AM ---------- Previous post was at 01:35 AM ----------
madbat99 said:
You have the sprint s3, but are you on sprint? If you are not on Sprint there are additional instructions. Any rom that says its for D2spr is fine. That's the sprint s3.
this is the one I'm using.
Click to expand...
Click to collapse
Actually, I don't use any company cause I don't live in the US so I use the phone only with WiFi.
Now that i'm in the correct thread.......
this phone is just for messing with so backup isn't needed. Unlocked, son did factory reset only twrp was left on it. D/L Magma rom, went into twrp clicked on zip, nadda. D/L different rom (forget the name) still no dice. D/L Odin, installed stock rom, phone works no issues etc, but twrp was gone. Re-loaded twrp with Odin, but still couldn't get either of the previous 2 roms to load. Searches have yielded inconsistent results. Some say you can load a rom over the stock with Odin, others say you can't. Tried to find a rom I could load via Odin that would work on the sm-n900t but the stock rom is all that comes up in my searches. Not really sure where to go from here, if someone can point me in the right direction it would be appreciated. I'm pretty sure I d/l the correct twrp for my phone as I actively looked to make sure I was getting the one for my phone, and it said it was......
Are you using a version from here: https://dl.twrp.me/hltetmo/ ?
audit13 said:
Are you using a version from here: https://dl.twrp.me/hltetmo/ ?
Click to expand...
Click to collapse
the file I used is twrp-3.2.3-0-hlte.img.tar
kevin24018 said:
this phone is just for messing with so backup isn't needed.
Click to expand...
Click to collapse
Trust me, backup is always needed.
kevin24018 said:
Unlocked, son did factory reset only twrp was left on it. D/L Magma rom, went into twrp clicked on zip, nadda. D/L different rom (forget the name) still no dice.
Click to expand...
Click to collapse
you might be installing wrong version of rom. (i'll tell you why i assumed this)
kevin24018 said:
D/L Odin, installed stock rom, phone works no issues etc, but twrp was gone. Re-loaded twrp with Odin, but still couldn't get either of the previous 2 roms to load. .
Click to expand...
Click to collapse
when you install stock rom through odin. it removes everything. everything means your device is as new as you bought it. so when you installed stock rom, it always removes twrp and installs stock recovery. same goes with any custom rom you previously installed.
kevin24018 said:
Searches have yielded inconsistent results. Some say you can load a rom over the stock with Odin, others say you can't.
Click to expand...
Click to collapse
yes you can load a rom over the stock but not with odin. with twrp instead.
kevin24018 said:
Tried to find a rom I could load via Odin that would work on the sm-n900t but the stock rom is all that comes up in my searches. Not really sure where to go from here, if someone can point me in the right direction it would be appreciated.
Click to expand...
Click to collapse
normally people use odin to install stock roms or twrp or for root. nobody installs custom rom through odin. i don't want you to go deep into this right now so i'm just suggesting you the easiest way.
i assume currently you have stock lollipop rom rooted with twrp. all you need to do is to go to here ans choose your rom. read and follow instruction to the point. i'm sure you'll get things done .
kevin24018 said:
I'm pretty sure I d/l the correct twrp for my phone as I actively looked to make sure I was getting the one for my phone, and it said it was......
Click to expand...
Click to collapse
now sadly. the twrp version you mentioned above is for n9005 international version while you're having n900t (t mobile version) so you'll need correct twrp the says "tmo" or something like this.
above i said you might be installing wrong version of rom because you're not using correct twrp and pretty sure about it. thats why i assumed you may also have d/l wrong version of rom.
long story short : you need everything regarding tmobile (tmo) not any other. just in case please check if you really have n900t or not by taking out battery.
Sharjeel.Khan said:
Trust me, backup is always needed.
you might be installing wrong version of rom. (i'll tell you why i assumed this)
when you install stock rom through odin. it removes everything. everything means your device is as new as you bought it. so when you installed stock rom, it always removes twrp and installs stock recovery. same goes with any custom rom you previously installed.
yes you can load a rom over the stock but not with odin. with twrp instead.
normally people use odin to install stock roms or twrp or for root. nobody installs custom rom through odin. i don't want you to go deep into this right now so i'm just suggesting you the easiest way.
i assume currently you have stock lollipop rom rooted with twrp. all you need to do is to go to here ans choose your rom. read and follow instruction to the point. i'm sure you'll get things done .
now sadly. the twrp version you mentioned above is for n9005 international version while you're having n900t (t mobile version) so you'll need correct twrp the says "tmo" or something like this.
above i said you might be installing wrong version of rom because you're not using correct twrp and pretty sure about it. thats why i assumed you may also have d/l wrong version of rom.
long story short : you need everything regarding tmobile (tmo) not any other. just in case please check if you really have n900t or not by taking out battery.
Click to expand...
Click to collapse
after installing the correct twrp, I was able to install Lineage, thanks for the help. I have a better idea of what I'm doing, I'll continue to play around with it.