Develop Bugs

[Q] need help: trying to update t999 to Leak JB UVDLI7 thru stock recovery

Can someone please tell me what I'm doing wrong. I'm on stock uvalh2, it is rooted but i checked temp unroot in superuser. I downloaded the JB leak update UVDLI7, and i put it on my external SD. I went into stock recovery and i hit "install from external sd" and hit the downloaded JB, file. And everytime i tried installing this came up
"E:error in /tmp/sideload/package.zip (status 7)
Does any one know what that is? I've updated my girlfriends sgs3 and my brothers and it worked flawlessly, but i can never seem to achieve it onon mine. If anyone could help, it would mean the world to me., thanks
Jake

Did u do a factory reset and full wipe I had that problem until I did that..
Sent from my SGH-T999 using xda app-developers app

DNASTY6997 said:
Did u do a factory reset and full wipe I had that problem until I did that..
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I didn't. Going to try that now. Thanks

DNASTY6997 said:
Did u do a factory reset and full wipe I had that problem until I did that..
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ok, tried that. This time it says "Install Aborted". Only thing it did was reset my phone. If anyone knows what i need to do that would be great. Thanks anyways Dnasty

I recommend you verify the integrity of your LI7 file, then use Odin to flash ClockworkMod (links in my signature).
I think its about time people quit messing around with the worthless stock recovery.

Aerowinder said:
I recommend you verify the integrity of your LI7 file, then use Odin to flash ClockworkMod (links in my signature).
I think its about time people quit messing around with the worthless stock recovery.
Click to expand...
Click to collapse
Hey, i had root and cwm on uvalh2. But i was told that to update my phone to the leak JB 4.1.1 UVDLI7, I need to unroot And install it from stock not CWM. Plus ive read about 10 different directions on varius sites saying the Same thing. I was even told to change the file name to Update.zip. i still get the error tmp/sideload/package.zip status 7. I've already done it to 2 other Phones, i just can't get it on mine. If you know a way to flash the JB leak UVDLI7 thru Odin please tell me how. Thanks

I am not sure what error 7 means. It could mean your files didn't pass verification (the update checks them before it applies), or the zip file is corrupted, etc. Did you get it from here: http://www.sammobile.com/firmware/?page=3&model=SGH-T999&pcode=TMB&os=1&type=1#firmware?
My point is that this information about OTA flashing that you are seeing is outdated. People still swear by it, but they are no longer correct. Two months ago, they were correct. But not anymore. If you are using CWM 6.0.1.2, you absolutely do not need to do anything, except flash the leaked OTA update through CWM.
You don't flash the OTA updates through Odin. If you are on UVALH2 right now, here is what you do:
If you are using a modem that is not LH2, you need to flash to LH2.
Run OTA update through CWM.
Done.

Aerowinder said:
I am not sure what error 7 means. It could mean your files didn't pass verification (the update checks them before it applies), or the zip file is corrupted, etc. Did you get it from here: http://www.sammobile.com/firmware/?page=3&model=SGH-T999&pcode=TMB&os=1&type=1#firmware?
My point is that this information about OTA flashing that you are seeing is outdated. People still swear by it, but they are no longer correct. Two months ago, they were correct. But not anymore. If you are using CWM 6.0.1.2, you absolutely do not need to do anything, except flash the leaked OTA update through CWM.
You don't flash the OTA updates through Odin. If you are on UVALH2 right now, here is what you do:
If you are using a modem that is not LH2, you need to flash to LH2.
Run OTA update through CWM.
Done.
Click to expand...
Click to collapse
Thank you so much!!!! You solved my problem. You're the man
Jake

Aerowinder said:
I am not sure what error 7 means. It could mean your files didn't pass verification (the update checks them before it applies), or the zip file is corrupted, etc. Did you get it from here: http://www.sammobile.com/firmware/?page=3&model=SGH-T999&pcode=TMB&os=1&type=1#firmware?
My point is that this information about OTA flashing that you are seeing is outdated. People still swear by it, but they are no longer correct. Two months ago, they were correct. But not anymore. If you are using CWM 6.0.1.2, you absolutely do not need to do anything, except flash the leaked OTA update through CWM.
You don't flash the OTA updates through Odin. If you are on UVALH2 right now, here is what you do:
If you are using a modem that is not LH2, you need to flash to LH2.
Run OTA update through CWM.
Done.
Click to expand...
Click to collapse
And yes i had gotten it from sammobile

Assert failed: getprop("ro.bootloader" == "l710vpbLj7

I just flashed CM10.1 on my Sprint S3.
I am trying to flash the latest nightly and I am getting the following error in both CWM and TWRP
Assert failed: getprop("ro.bootloader" == "l710vpbLj7" ... and it repeats that line specific to other versions (L710VPBMA6 etc)
I had an older version of CWM ... but still a 6+ when I flashed it. I since installed (via goomanager) TWRP as it looked cool. I started getting this error. Next, I used CWM to install the latest 6.0.3.1 version of CWM. It's still not wokring.
I seem to be able to download the goomanager latest DL and that's what I used to get the initial flashable zip.
Any ideas? I'm kinda at a loss. I'd do a full wipe but I'm afraid that if I do that I'll be SOL - as I have a current functional ROM right now.
Thoughts???
Sent from my SPH-L710 using xda app-developers app

Ha ha. You're still in the same, incorrect (international GT-i9300) forum. Try here:
http://forum.xda-developers.com/forumdisplay.php?f=1707

gregory15 said:
I just flashed CM10.1 on my Sprint S3.
I am trying to flash the latest nightly and I am getting the following error in both CWM and TWRP
Assert failed: getprop("ro.bootloader" == "l710vpbLj7" ... and it repeats that line specific to other versions (L710VPBMA6 etc)
I had an older version of CWM ... but still a 6+ when I flashed it. I since installed (via goomanager) TWRP as it looked cool. I started getting this error. Next, I used CWM to install the latest 6.0.3.1 version of CWM. It's still not wokring.
I seem to be able to download the goomanager latest DL and that's what I used to get the initial flashable zip.
Any ideas? I'm kinda at a loss. I'd do a full wipe but I'm afraid that if I do that I'll be SOL - as I have a current functional ROM right now.
Thoughts???
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem on the spring gs3 and I can't figure it out.

Whew, someone else with the Asset faled: getprop error
Have you learned anything more about this? I have found I was able to install CM10.1 up to nightly 0511 but nothing after that.
gregory15 said:
I just flashed CM10.1 on my Sprint S3.
I am trying to flash the latest nightly and I am getting the following error in both CWM and TWRP
Assert failed: getprop("ro.bootloader" == "l710vpbLj7" ... and it repeats that line specific to other versions (L710VPBMA6 etc)
I had an older version of CWM ... but still a 6+ when I flashed it. I since installed (via goomanager) TWRP as it looked cool. I started getting this error. Next, I used CWM to install the latest 6.0.3.1 version of CWM. It's still not wokring.
I seem to be able to download the goomanager latest DL and that's what I used to get the initial flashable zip.
Any ideas? I'm kinda at a loss. I'd do a full wipe but I'm afraid that if I do that I'll be SOL - as I have a current functional ROM right now.
Thoughts???
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse

FlagPonder said:
Have you learned anything more about this? I have found I was able to install CM10.1 up to nightly 0511 but nothing after that.
Click to expand...
Click to collapse
**** UPDATE *****
****THIS SOLUTION and LINKS ARE ONLY APPLICABLE TO SPRINT GALAXY S3 PHONES ... FYI FYI FYI******
yes. I have. The problem is that we have an old version of the FIRMWARE. If you flash the following to update your firmware to MD4:
http://forum.xda-developers.com/showthread.php?t=1910947 and install Galaxy-S-fre3-MD4FirmwareModemAIO.zip from CWM.
There are some new checks that happen that require the MD4 stuff. For more information about that - you can check https://plus.google.com/app/basic/stream/z13cdxpafunnexghb04cc5q4knbyjh4hprg0k
Also, clear cache/dalvik - not that it matters - but I did that - and i found things working. So, after flash, go into /cmupdate folder and flash the latest - it should work (unless i'm just lucky)
_G

gregory15 said:
**** UPDATE *****
****THIS SOLUTION and LINKS ARE ONLY APPLICABLE TO SPRINT GALAXY S3 PHONES ... FYI FYI FYI******
yes. I have. The problem is that we have an old version of the FIRMWARE. If you flash the following to update your firmware to MD4:
http://forum.xda-developers.com/showthread.php?t=1910947 and install Galaxy-S-fre3-MD4FirmwareModemAIO.zip from CWM.
There are some new checks that happen that require the MD4 stuff. For more information about that - you can check https://plus.google.com/app/basic/stream/z13cdxpafunnexghb04cc5q4knbyjh4hprg0k
Also, clear cache/dalvik - not that it matters - but I did that - and i found things working. So, after flash, go into /cmupdate folder and flash the latest - it should work (unless i'm just lucky)
_G
Click to expand...
Click to collapse
Thank you so much. Fixed my issue as well. One thing I have to add is that you should do Advanced > Reboot Recovery if you still cannot flash the ROM that gave you the assert problems.

I remember reading that from now on CM10.1 will need the MD4 bootloader or else you get that assert error.
Sent from my SPH-L710 using Tapatalk 2

anyone know if the sprint md4 firmware update will work with c spire's galaxy s3?

You should not flash firmware not intended for your exact device.

CNexus said:
You should not flash firmware not intended for your exact device.
Click to expand...
Click to collapse
What he said. Flashing modems is about the most dangerous thing you can do to your phone
Sent from my SPH-L710 using xda app-developers app

k good to know how would I be able to successfully flash cm10.1 on my c spire gs3?

Fazzl86 said:
k good to know how would I be able to successfully flash cm10.1 on my c spire gs3?
Click to expand...
Click to collapse
Shoot me a pm. I'll set ya straight

Virgin Mobile?
Anyone know if this will work for the Sph-l710 for Virgin Mobile? I'm trying to flash a 4.4 Rom and I'm wanting to try this but it sounds too risky.... Thoughts?

Ok, so I'm getting the same error as OP, trying to flash the CM10.2 Stable (via TWRP) and I understand that I may need to update my firmware or bootloader (are these different?). The only problem is, I may have accidentally installed the OTA 4.3 rom with Knox. I ended up reflashing right away after I realized what I'd done, and the rom I have now (4.3 stock w/ root) doesn't have any knox apps, nothing about knox in device manager, and root/superuser is working just fine.
That said, I'm a bit scared to update my firmware as I've heard stories about Knox working in the background and bricking. Is there a way I can be sure updating my firmware wont brick me? Can someone point me to the latest file I should be flashing here?
Thing in "About Device":
Model:SPH-L710
Version 4.3
Baseband: L710VPUCMK3
Kernel:[email protected] #1
Build: JSS15J.L710VPUCMK3
SE: Permissive
Hardware:L710.14
Thanks in advance. I've gotta get off the stock 4.3, battery life and sluggish behavior are killing me.
DC

[Q] Please help me get a usable phone again

I decided to try cyanogenmod on my SGH-I747 but have had so many issues I would be happy at this point if I could just get a working phone again.
I started with a 4.3 OTA-updated phone. I rooted the phone, then tried to install the latest 10.2 ROM. I also tried 10.1. I used CWM: I would have preferred the latest version but the best I could find that was not an .img file (I used Odin) was in the 5.x range. In both cases I hit what I believe is a bootloader error ("assert failed: ... Status 7"). At this point the phone is wiped with no recourse. I attempted to install the stock boot image for the I747, but after doing so the phone will no longer boot.
EDIT: I am able to get to downloading mode. I am afraid to use it to install stock firmware b/c of a post I found here claiming that downgrading from 4.3 OTA (e.g., to 4.1) will brick the phone.

tn6 said:
I decided to try cyanogenmod on my SGH-I747 but have had so many issues I would be happy at this point if I could just get a working phone again.
I started with a 4.3 OTA-updated phone. I rooted the phone, then tried to install the latest 10.2 ROM. I also tried 10.1. I used CWM: I would have preferred the latest version but the best I could find that was not an .img file (I used Odin) was in the 5.x range. In both cases I hit what I believe is a bootloader error ("assert failed: ... Status 7"). At this point the phone is wiped with no recourse. I attempted to install the stock boot image for the I747, but after doing so the phone will no longer boot.
EDIT: I am able to get to downloading mode. I am afraid to use it to install stock firmware b/c of a post I found here claiming that downgrading from 4.3 OTA (e.g., to 4.1) will brick the phone.
Click to expand...
Click to collapse
i actually had the same problem earlier today. what i did was use odin to install clockworkmod recovery. after it reboots, hold VOLUME UP and HOME at the same time. if you have a micro sd handy, download any of the two updates here http://forum.xda-developers.com/showthread.php?t=2498233 place them on you sd card and in recovery format cache and factory reset/data. then highlight "install zip from sd card" or something that sounds relevant. select the zip you placed on your sd card earlier and there.

Worked, I think
MrHaPpY66 said:
i actually had the same problem earlier today. what i did was use odin to install clockworkmod recovery. after it reboots, hold VOLUME UP and HOME at the same time. if you have a micro sd handy, download any of the two updates here http://forum.xda-developers.com/showthread.php?t=2498233 place them on you sd card and in recovery format cache and factory reset/data. then highlight "install zip from sd card" or something that sounds relevant. select the zip you placed on your sd card earlier and there.
Click to expand...
Click to collapse
Thank you. The phone now boots to a white screen with an AT&T symbol. How can I install either a stock or custom ROM without ruining everything again?

tn6 said:
Thank you. The phone now boots to a white screen with an AT&T symbol. How can I install either a stock or custom ROM without ruining everything again?
Click to expand...
Click to collapse
i think this should be a help http://forum.xda-developers.com/showthread.php?t=2539313

No luck
MrHaPpY66 said:
i think this should be a help http://forum.xda-developers.com/showthread.php?t=2539313
Click to expand...
Click to collapse
That appears to be the standard tutorial for rooting/flashing. I did it anyway, even though didn't the file you had me install before already root the phone? In any event, I ran CF-root and then I attempted to install CM 10.2 and it failed: "failed to verify whole-file signature." I believe that was the first error I hit in the beginning of this exercise. Additionally, now I get an error on the welcome screen that says "Unfortunately, SuperSU has stopped."

tn6 said:
That appears to be the standard tutorial for rooting/flashing. I did it anyway, even though didn't the file you had me install before already root the phone? In any event, I ran CF-root and then I attempted to install CM 10.2 and it failed: "failed to verify whole-file signature." I believe that was the first error I hit in the beginning of this exercise. Additionally, now I get an error on the welcome screen that says "Unfortunately, SuperSU has stopped."
Click to expand...
Click to collapse
for the supersu, you probably need to go update it on the market or disable KNOX

assert failed... getprop("ro.bootloader")
MrHaPpY66 said:
for the supersu, you probably need to go update it on the market or disable KNOX
Click to expand...
Click to collapse
Thanks for the suggestion. I went back to the no-KNOX file you pointed out earlier. I assume that is the same type of file as the CF-Root so I assume I don't need to install CF-root anymore after installing the no-KNOX file. So now I follow the tutorial from your second response minus the root step. I no longer get the SuperSU error. However, I still can't load a ROM. I get the same "assert failed... getprop("ro.bootloader... Status 7" that I mentioned in my first post. When I googled this in the first round, I saw several posts saying it means I had a bad bootloader. That is when I tried to flash the stock bootloader, which nearly hardbricked the phone. Do the two files you initially posted include a bootloader file?

tn6 said:
Thanks for the suggestion. I went back to the no-KNOX file you pointed out earlier. I assume that is the same type of file as the CF-Root so I assume I don't need to install CF-root anymore after installing the no-KNOX file. So now I follow the tutorial from your second response minus the root step. I no longer get the SuperSU error. However, I still can't load a ROM. I get the same "assert failed... getprop("ro.bootloader... Status 7" that I mentioned in my first post. When I googled this in the first round, I saw several posts saying it means I had a bad bootloader. That is when I tried to flash the stock bootloader, which nearly hardbricked the phone. Do the two files you initially posted include a bootloader file?
Click to expand...
Click to collapse
i think they contained the mj2 bootloader and modem. hmm i've been doing a little snooping around and i found this. http://forum.xda-developers.com/showthread.php?t=2540998 the thing is i still don't understand how to go from leaked (mj2) to the official release (mjb) maybe updating to this will help

MrHaPpY66 said:
i think they contained the mj2 bootloader and modem. hmm i've been doing a little snooping around and i found this. http://forum.xda-developers.com/showthread.php?t=2540998 the thing is i still don't understand how to go from leaked (mj2) to the official release (mjb) maybe updating to this will help
Click to expand...
Click to collapse
I'm worried about switching bootloaders. This post seems to indicate that doing so after I installed 4.3 OTA will brick the phone. Does anyone know if that is true?
http://forum.xda-developers.com/showthread.php?t=2321310

tn6 said:
I'm worried about switching bootloaders. This post seems to indicate that doing so after I installed 4.3 OTA will brick the phone. Does anyone know if that is true?
http://forum.xda-developers.com/showthread.php?t=2321310
Click to expand...
Click to collapse
ohh ho ho it's true alright. the new 4.3 bootloader, i'm guessing it is mjb, doesn't allow any downgrades. Downgrades of any kind will absolutely give you a nice, good brick. anyways do you understand how to go from 4.3 leaked to 4.3 official?

MrHaPpY66 said:
ohh ho ho it's true alright. the new 4.3 bootloader, i'm guessing it is mjb, doesn't allow any downgrades. Downgrades of any kind will absolutely give you a nice, good brick. anyways do you understand how to go from 4.3 leaked to 4.3 official?
Click to expand...
Click to collapse
No idea. I went ahead and tried to install the I747UCDLK3_aio.tar.md5, which I hoped was a 4.3 bootloader (don't know how you are supposed to tell). The error I got was this was another failure--this time saying the package was for d2att and this is a d2spr. My phone is definitely not a sprint phone. Some posts say I have to update the build.prop file, but I don't know how I can do that before a ROM is even installed.

resolved
tn6 said:
No idea. I went ahead and tried to install the I747UCDLK3_aio.tar.md5, which I hoped was a 4.3 bootloader (don't know how you are supposed to tell). The error I got was this was another failure--this time saying the package was for d2att and this is a d2spr. My phone is definitely not a sprint phone. Some posts say I have to update the build.prop file, but I don't know how I can do that before a ROM is even installed.
Click to expand...
Click to collapse
I realized that many of the errors I was getting seemed to be tied to cyanogenmod or stock. So I downloaded Hyperdrive and it installed with zero hiccups or errors. I have a working phone again.
Thank you for your helpful insights.

tn6 said:
I realized that many of the errors I was getting seemed to be tied to cyanogenmod or stock. So I downloaded Hyperdrive and it installed with zero hiccups or errors. I have a working phone again.
Thank you for your helpful insights.
Click to expand...
Click to collapse
you're welcome and i glad i was a help to you. anyways where'd you get hyperdrive? i've been trying to get my phone back to official stock and off the leaked one.

MrHaPpY66 said:
you're welcome and i glad i was a help to you. anyways where'd you get hyperdrive? i've been trying to get my phone back to official stock and off the leaked one.
Click to expand...
Click to collapse
I downloaded hyperdrive from the official spot: http://forum.xda-developers.com/showthread.php?t=2106830. I wouldn't have minded going back to stock, but clearly that was not going to happen any time soon.

tn6 said:
I downloaded hyperdrive from the official spot: http://forum.xda-developers.com/showthread.php?t=2106830. I wouldn't have minded going back to stock, but clearly that was not going to happen any time soon.
Click to expand...
Click to collapse
so how's the rom so far? probably going to get it myself.

MrHaPpY66 said:
so how's the rom so far? probably going to get it myself.
Click to expand...
Click to collapse
Zero issues. Worked great all day with no problems. Plus I am now able to tether and use the mobile hotspot, features that I couldn't get to work on the stock rom even with foxfi or similar apps.

tn6 said:
Zero issues. Worked great all day with no problems. Plus I am now able to tether and use the mobile hotspot, features that I couldn't get to work on the stock rom even with foxfi or similar apps.
Click to expand...
Click to collapse
so i see it's a lot better than stock. i'll install it as soon as i can and thanks for the link to the rom

[Q] How to install d2att roms on d2can?

I have had a problem, I want to install aokp for my GS3 Model Sgh-1747m but I have not seen a single tutorial on how to do so. I am new to the forums and I have some understanding of how Root and Android work(My phone is rooted). I would like someone to show me how to add the aokp rom without any worries. This would be greatly appreciated.
My phone: Samsung Galaxy S III (Android 4.3)
Model: Sgh-1747m
Carrier: Bell

Are you on stock 4.3 ROM? Do you have any warranty left on your phone?
If you still have warranty and you're running a stock 4.3 ROM, you will void your warranty by flashing a custom recovery or rooting your phone.

pfffff
audit13 said:
Are you on stock 4.3 ROM? Do you have any warranty left on your phone?
If you still have warranty and you're running a stock 4.3 ROM, you will void your warranty by flashing a custom recovery or rooting your phone.
Click to expand...
Click to collapse
you did better answer his question than to speak about warrantly,,,pffff

hichem jerbi said:
you did better answer his question than to speak about warrantly,,,pffff
Click to expand...
Click to collapse
Feel free to answer his question. Please tell him what to do

Ketros said:
I have had a problem, I want to install aokp for my GS3 Model Sgh-1747m but I have not seen a singe tutorial on how to do so. I am new to the forums and I have some understanding of how Root and Android work. I would like someone to show me how to add the aokp rom without any worries. This would be greatly appreciated.
My phone: Samsung Galaxy S III (Android 4.3)
Model: Sgh-1747m
Carrier: Bell
Click to expand...
Click to collapse
SEARCH engines are your friend. (WARNING: Some reading is required)
Sent from my awesome phone.

aybarrap1 said:
SEARCH engines are your friend. (WARNING: Some reading is required)
Sent from my awesome phone.
Click to expand...
Click to collapse
I have searched I have already rooted my phone but all I am being told is to change the build.prop from d2Can to d2att
I don't want to do that because if I do I won't have another phone to use so I want to see someone do it so I can do it as well

Ketros said:
I have searched I have already rooted my phone but all I am being told is to change the build.prop from d2Can to d2attl
Click to expand...
Click to collapse
I didn't manually change the build.prop but i installed the d2att version of TWRP 2.6.3.1 and that allowed me to install d2att ROMs (I chose Quantum ROM). When First I tried the d2can TWRP (which I got from Goo Manager) and I couldn't install the ROM. Updating to the d2att TWRP fixed that.

jmppe3 said:
I didn't manually change the build.prop but i installed the d2att version of TWRP 2.6.3.1 and that allowed me to install d2att ROMs (I chose Quantum ROM). When First I tried the d2can TWRP (which I got from Goo Manager) and I couldn't install the ROM. Updating to the d2att TWRP fixed that.
Click to expand...
Click to collapse
How do I get the d2att version of TWRP and install AOKP 4.4, will I need to unlock the bootloader or something? If so how do I do that?

Ketros said:
How do I get the d2att version of TWRP and install AOKP 4.4, will I need to unlock the bootloader or something? If so how do I do that?
Click to expand...
Click to collapse
I did the same with my d2can. I installed the d2att version of twrp and can now flash d2att roms with no issues. Download goomanager from play store, and instead of letting it detect your phone model (d2can), manually select d2att and install. That's what I did.
Sent from my SGH-I747 using xda app-developers app

This might help: http://forum.xda-developers.com/showthread.php?t=2538991.
I have never used this method but it may be worth a read.

Ketros said:
How do I get the d2att version of TWRP and install AOKP 4.4, will I need to unlock the bootloader or something? If so how do I do that?
Click to expand...
Click to collapse
Here, the TWRP website: http://techerrata.com/browse/twrp2/d2att

audit13 said:
This might help: http://forum.xda-developers.com xda-developers.com/showthread.php?t=2538991.
I have never od but it may be worth a read.
Click to expand...
Click to collapse
Thanks for the link but my phone is rooted already I need step by step instructions on how to get twrp d2att and install apk 4.4 on my phone

bdithug said:
I did the same with d2can. I installed the d2att version of twrp and can now flash d2att roms with no issues. Download goomanager from play store, and instead of letting it detect your phone model (d2can), manually select d2att and install. That's what I did.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Can you explain how to Install twrp(d2att) I've already rooted my phone now how do I get goomanager to install the d2att twrp

Ketros said:
Can you explain how to Install twrp(d2att) I've already rooted my phone now how do I get goomanager to install the d2att twrp
Click to expand...
Click to collapse
I just took a look at goomanager and the options look different than when I flashed twrp (d2att). It's either because I already have the recovery installed or maybe the app has updated. It's been so long since I did it myself. Try googling it or searching in twrp's thread here on xda. I'm sure you will be able to find step by step instructions.
Sent from my SGH-I747 using xda app-developers app

bdithug said:
I just took a look at goomanager and the options look different than when I flashed twrp (d2att). It's either because I already have the recovery installed or maybe the app has updated. It's been so long since I did it myself. Try googling it or searching in twrp's thread here on xda. I'm sure you will be able to find step by step instructions.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Use the link to TWRP I posted earlier and then flash with ODIN. I'm sure there's another way to do it via the recovery but I haven't looked into it as I don't need to. Must be something on the forum about it.

jmppe3 said:
Use the link to TWRP I posted earlier and then flash with ODIN. I'm sure there's another way to do it via the recovery but I haven't looked into it as I don't need to. Must be something on the forum about it.
Click to expand...
Click to collapse
I have downloaded the twrp for d2att now all I do is flash it on my phone? My phone is already rooted with the d2can twrp will it still work? Will I lose any of my files?

Ketros said:
I have downloaded the twrp for d2att now all I do is flash it on my phone? My phone is already rooted with the d2can twrp will it still work? Will I lose any of my files?
Click to expand...
Click to collapse
I don't know, try searching on the forums. I told you how I did it and that's all I can help you with, sorry. You should have a backup before trying any of this stuff, anyway.

jmppe3 said:
I don't know, try searching on the forums. I told you how I did it and that's all I can help you with, sorry. You should have a backup before trying any of this stuff, anyway.
Click to expand...
Click to collapse
When I rooted my phone I used this method http://forum.xda-developers.com/showthread.php?t=2538991 I installed the twrp for d2att, but this was a while ago so is there any way to check if it is the d2att version and not the d2can version

Ketros said:
When I rooted my phone I used this method http://forum.xda-developers.com/showthread.php?t=2538991 I installed the twrp for d2att, but this was a while ago so is there any way to check if it is the d2att version and not the d2can version
Click to expand...
Click to collapse
Using which method, #1 or #2? I did #1 and installed TWRP via Goo Manager (IIRC). But that gave me the d2can version. I don't think you need to bother checking, though, just use ODIN to flash the new recovery (TWRP 2.6.3.1) from the link I gave you earlier. After backing up etc etc.

I had the exact same problem as OP.
What the recovery is trying to do is install a D2ATT rom onto a D2ATT phone which the Canadian carriers change to D2CAN in their build.prop file.
1. Find your build.prop file in system/data and make a backup of it however you which. I made a copy and just called it something else. Go to your build.prop file and change any instance of "d2can" to d2att. When I did this there was two. One on build.product=d2can and one on build.device. I just checked and CM changed some of the settings around and now there is just one.
Save the file and it'll ask you to reboot.
Now anything you download will think it's an actual at&t device (which is good).
The standard method for getting TWRP on your device is through goomanager but samsungs knox gave me issues trying to install a custom recovery.
2. Get the app "Recovery Tools" Or, specifically [ROOT]Recovery Tools - Flasher by DSLNEXUS.
and download the recovery file here http://www.teamw.in/project/twrp2/104
Download the .img file via dd into the root folder of your phone.
Open up recovery tools and select flash recovery and select other from storage. You CAN select TWRP and have the app do it for you but sometimes it uses older versions. I chose "other from storage" then you select the twrp file you downloaded.
3. At this point you should be able to boot into twrp and flash from there. Don't forget your gapps.
I spent months on and off wracking my brain trying to figure out how to do this on my phone without bricking it. I did it this way and it worked without a hitch.

SU Problem

Whenever i try to reboot through CWM or flash something, an error always pops up informing me that my root access is possibly lost. It then asks if i want to fix it. I can either say "No" or say "Yes - Fix Root (/system/xbin/su)"
I have tried both options and have discovered that i cant flash anything. I have also checked and i have cobfirmed that /system/xbin/su is in fact on my phone. I dont know what to do. Also, my phone is an AT&T Galaxy S3 i-747 rooted with towelroot, stock ROM, stock kernel(which I hope to change right after this).

Are you running the latest cwm?

audit13 said:
Are you running the latest cwm?
Click to expand...
Click to collapse
Yup, 6.0.4.7

Maybe give twrp a try.

I've gotten that issue all long since 4.3. It's KNOX
Sent from my Nexus 5 using Tapatalk