Develop Bugs

[Q] what does "E:error in TMP/sideload/package.zip (status 7) mean?

Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake

themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
As far as I can tell, I believe it means you're rooted still. I had the same problem so I Odin'd stock UVALH2 and then installed the leak without issue.

Not trying to hijack this thread but have been wondering why do you guys try to install leaks throw stock recovery. It is super easy to root this phone. Why not root install custom recovery then jush flash leaks?
Sent from my SGH-T999

Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.

Aerowinder said:
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.
Click to expand...
Click to collapse
Same here, I didn't come from a stock rom. Oh well.

So are you flashing the deodexed roms then?
Im talking about the actual ota you download from somewhere like sammobile.
It patches the existing system (UVDLI8 patches UVALI5) if anything is modded in UVALI5 the patch wont work, or if it does it can cause problems.
If you're flashing roms from development section then yes you can flash normally with custom recovery. But those roms are based on the otas, they're not the actual otas themselves.
Sent from my SGH-T999 using xda app-developers app

I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.

Yeah i tried everyway possible. The only way that worked was going uvahl2 thru odin, and then thru stock recovery i applied the ota jb uvdli7 from external sd. It was the only way to get it to work. I think the reason why the error message was coming up was because even though i unrooted my phone, the phone status still said "modified". Once i reflashed hl2 and it didn't say modified it updated the leak.

I think its going to take a video to prove you don't need stock recovery for this operation.

Aerowinder said:
I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.
Click to expand...
Click to collapse
Lol! Im just usually online when they drop! Theres only been a couple where I wasn't.
If cwm touch recovery does flash these otas as is then it just means they've disabled the check the ota does to verify the system meets the requirements. Or they just disable the recovery check/patch to protect their own recovery. I hope its the latter.
Not saying it cant be done but till now I hadn't heard of it. I use TWRP (just personal preference) but actually never bothered to try with it becsuse too many people early on got errors like the OP when anything wasn't matching stock.
I use Mobile Odin for the otas since it not only allows me to meet the stock requirements but it also injects root so you never have to worry about rerooting or anything.
At this point I just want to know how CWM does the otas. Does it completely disable the system check, or just the recovery part of that check.
Sent from my SGH-T999 using xda app-developers app

The zip file still runs the verification process. I've always done it properly, so I don't know what a flashing failure looks like. I have a background in programming, and I'm an amateur for sure, but I suspect that when the update checks for stock recovery, it thinks CWM is the stock recovery. I'm not sure of the code behind this, but I equate it to user-agents in browsers. CWM is saying it is stock recovery, OTA update accepts that, or some such. Without seeing the code, I can't say for sure, but this is my guess.
You get the option to disable the recovery patch, and to keep root when you attempt to exit recovery after the OTA flash.
I never saw much use for Mobile Odin. I did buy it, because the dev is amazing, but I've never used it. It allows you to flash zip files? I've always just done it through CWM. I flash everything through CWM... even other recoveries.

However it does it, I guess it works. Only reason I wanted to know if it bypassed the entire check is because that could cause problems for the more inexperienced.
Yeah, I love Chainfires work. The ability to flash zips with Mobile Odin was just added a few weeks ago and has worked flawlessly for me.
Sent from my SGH-T999 using xda app-developers app

fix it
you need to flash your kernel to man. most stock kernel wouldnt work with cyanogenmod. Update your kernel with unofficial kernel that are compatible with your device

raaaaarrrr!!!
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.

atheistics1 said:
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.
Click to expand...
Click to collapse
Well, first, there is not an Odin flashable 4.3 file, but you said you tried to flash MDL? Not sure what this is exactly. The most likely issue is you are using an incompatible recovery. Probably one that is too old.

I think you are totally confused between odin flashable files and recovery flashable files....

Okay so maybe this will help...omni version is jfltecan...which is Canadian and my baseband is l720vpuemja ...that's sprint which my phone is...I'm getting no data...and I'm not able to revert back to 4.3 or 4.2.
Sent from my SGH-I337M using XDA Premium 4 mobile app

you should probably consider asking in your devices forum. if you use anything here youll likely brick.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2

wolverine
themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
Just downgrade to 4.0.4 and install cwm then flash it through it. it works for me.

[Q] Tmobile update on stock rooted rom

Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2

When it is rooted even if you try to use the OTA update it won't let you, while rooted, you could alternatively flash the update via ODIN w/ root support. Or try some of the sweet ROMs available , the reason I switched to a custom ROM because I was going to have to erase my phone anyway if I wanted to update, so I thought why not just try a custom ROM?
I use LiquidSmoothRC7, but if you want a more stock feel with touchwiz you can try Wicked, Wicked stays true to the "official stock ROMs" and just adds roots and tweaks the ROM to make it as stable as possible

If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section

cobraboy85 said:
If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section
Click to expand...
Click to collapse
OR you could listen to this dude

cobraboy85 said:
If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section
Click to expand...
Click to collapse
Actually there is. There are 10 partitions rewritten with the Odin and OTA update. Only 5 get rewritten if you flash via custom recovery, so you don't get the full update.
Sent from my SGH-T999 using Tapatalk 2

zul8er said:
Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
go to doc's thread, flash his firmware update, reboot, then flash whatever JB ROM you desire. there is absolutely no need to ODIN your phone with the OTA fw, resetting your device completely. you just need to make sure you flash the latest firmware first before you flash a ROM that is based off the latest OTA

cobraboy85 said:
go to doc's thread, flash his firmware update, reboot, then flash whatever JB ROM you desire. there is absolutely no need to ODIN your phone with the OTA fw, resetting your device completely. you just need to make sure you flash the latest firmware first before you flash a ROM that is based off the latest OTA
Click to expand...
Click to collapse
I stayed on 4.0.4 with the base of UVLH2 and just clean installed JB roms so should I update the base? Or is it already updated?
Sent from my SGH-T999 using xda app-developers app

Towle said:
Actually there is. There are 10 partitions rewritten with the Odin and OTA update. Only 5 get rewritten if you flash via custom recovery, so you don't get the full update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Some of those 10 partitions that are getting rewritten are... for one, your recovery... so that makes 9 actually...
My point is, and I'm not trying to be argumentative in any way, merely objective, is that unless it is reformatting the ext4 partition to new file structure (for example) there should be no need to do this. I suppose I would ask somebody to define in depth "rewritten" and how exactly this is being done and why. Every single update we have had since the release of this device I have not once updated my own device with odin merely to put it back to stock. And I have run into zero issues. Seems like a waste of time to me unless there is something highly critical being restructured entirely. In the end, its all the same disk, and disk size for any given partition.
---------- Post added at 05:51 AM ---------- Previous post was at 05:47 AM ----------
neim81094 said:
I stayed on 4.0.4 with the base of UVLH2 and just clean installed JB roms so should I update the base? Or is it already updated?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
If you are on LH2, with that same baseband, I would go ahead and update your baseband via docs packaged update in his thread, and just reboot, then move on to the jelly bean updates. Do a factory reset through recovery before you flash the JB ROM tho since you are coming from a completely different version of android.

zul8er said:
Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
If you want to avoid all the weird miscellaneous problems listed in the Q&A forum, update using Odin and the rooted rom in Docs' thread. If you choose not to use Odin do not be surprised if odd things happen.

Just stating my experience, I was rooted stock ics and ran the ota update. I was able to update, keep root and ran stock jelly bean without any problems at all.
Now I am running frosty jelly and still no problems at all. I am not saying for you to do it (dont want anyone blaming me) just stating that it can be done. Do whats most comfortable for you.
Sent from my SGH-T999 using xda app-developers app

jcbofkc said:
If you want to avoid all the weird miscellaneous problems listed in the Q&A forum, update using Odin and the rooted rom in Docs' thread. If you choose not to use Odin do not be surprised if odd things happen.
Click to expand...
Click to collapse
Again looking for some technical clarity here. Haven't had a single issue myself. With anything. And I have not factory odined my device once since I got it. It is not critical to do this, otherwise I would be suffering from "weird miscellaneous problems"
Hopin doc can jump in here and set me straight if I am wrong, but it seems to me you will be fine just updating your radios and then moving to the latest build (4.1.1) as long as you clear data before flashing your ROM of choice

cobraboy85 said:
Again looking for some technical clarity here. Haven't had a single issue myself. With anything. And I have not factory odined my device once since I got it. It is not critical to do this, otherwise I would be suffering from "weird miscellaneous problems"
Hopin doc can jump in here and set me straight if I am wrong, but it seems to me you will be fine just updating your radios and then moving to the latest build (4.1.1) as long as you clear data before flashing your ROM of choice
Click to expand...
Click to collapse
You could very well be correct. Not trying to debate you.
but....I am seeing thread after thread of issues. Based on experience I suggest using the full proof method. I have updated many phones using many different methods and never have problems, but apparently many have had issues.
I also hope Doc chimes in on this thread.

jcbofkc said:
You could very well be correct. Not trying to debate you.
but....I am seeing thread after thread of issues. Based on experience I suggest using the full proof method. I have updated many phones using many different methods and never have problems, but apparently many have had issues.
I also hope Doc chimes in on this thread.
Click to expand...
Click to collapse
Totally dig it. And yeah, just want to know what exactly is being done differently in odin

cobraboy85 said:
Totally dig it. And yeah, just want to know what exactly is being done differently in odin
Click to expand...
Click to collapse
If I understand the process correctly
ODIN flashes the entire phone OS like the kernel, Rom, baseband, etc
Using recovery to flash only updates the Rom,recovery,boot,kernel
Sent from my SGH-T999

neim81094 said:
If I understand the process correctly
ODIN flashes the entire phone OS like the kernel, Rom, baseband, etc
Using recovery to flash only updates the Rom,recovery,boot,kernel
Sent from my SGH-T999
Click to expand...
Click to collapse
Sorry, I will clarify, I am curious to know why Odin is such a critical issue. I know how it works as far as it being a flashing tool

I am not sure maybe it's just preference and how much you want to use your computer and what how much you want to download etc
Sent from my SGH-T999

neim81094 said:
I am not sure maybe it's just preference and how much you want to use your computer and what how much you want to download etc
Sent from my SGH-T999
Click to expand...
Click to collapse
The file used to flash with Odin is much larger because it is a complete rom. The OTA is a patch that attempts to patch and modify existing files.

I basically said that on the last post not the one you quoted
Sent from my SGH-T999

Finally got the time to Odin Route66 Jelly bean.
Sent from my SGH-T999 using Tapatalk 2

Everything good?

[Q] Unable to flash Stock ROM

I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks

Is it supposed to use T999 firmware?

Only odin flash T999L firmware. I dont see it released yet at samsing-updates.com though.
Maybe samfirmware.com? I can look later.
Sent from my SGH-T999 using xda premium

re: sure fix
newidforu said:
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Click to expand...
Click to collapse
Why not reflash the stock ODIN flash rom and make sure it all works ok for you, that will tell you exactly what the problem is.
If the stock rom is working properly, then there is only one thing left which is the culprit and that is the CM10/AOKP/AOSP
or PORTED roms which many people seem to like flashing.
The CM10/AOKP/AOSP and ported roms are excellent if you are a developer or if you like to do a lot of experimentation with your phone.
So the thing to do now is reboot your phone to recovery mode, do a "Factory Reset", "Wipe Cache", "Wipe System" and "Wipe Dalvik".
When that's done Open Odin and put the stock rooted T999 Tmobile Jellybean 4.1.2 into Odin's PDA slot, go into download mode
and once you see Odin is connected to the phone start the flash. Have patience for the phone to boot after its done flashing.
Here is the stock rooted Odin flash T999 Tmobile Jellybean 4.1.2 rom that you can download if you like: T999_UVDMD5
Official JB Firmware - Latest JB 4.1.2 Firmware
My suggestion to you is to only flash Samsung T999 Tmobile stock based Jellybean 4.1.1 or 4.1.2 roms in the future.
But who am I to say whats best..... This is just my personal opinion...... Which usually is not worth a dime. LOL

Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I am a newbie. I thought the T999 was the same as the T999L. That would explain why Odin doesnt flash stock T999 onto my device. Can anyone here post a link to the stock SGH-T999L ROM?

Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.

newidforu said:
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
Click to expand...
Click to collapse
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.

Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I used Odin to flash Clockwork Mod recovery first. I did not like Clockwork Mod's interface and reflashed with TWRP. I had no problems to gain root with either of these methods. I also tried Cyanogenmod stable 10.0.0 and then 10.1 RC2 without any problems. As far as I can tell, all apps work except for the camera. One word of caution though. As you can see from my posts, I am new and dont know what I am doing. I might have just gotten lucky since my device is still unbricked. I had only one "scary" moment during the entire process. I used TWRP to wipe my phone clean and was stuck with no OS install file. ADB sideload did not work since it could not recognize the device at that point. Luckily, I had a micro SD card lying around and was able to put in a new OS install file using my laptop and then TWRP was able to handle it.

tsticge aye
faytx1 said:
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Click to expand...
Click to collapse
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414

newidforu said:
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
Click to expand...
Click to collapse
Here is the cameradata folder from the T999L.
http://d-h.st/Ciy
Good Luck!

How did you get Cyanogenmod installed on the t999l every time i try it aborts with status 7

Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app

Beefstew said:
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You reverted to stock on the T999L? please exspain how that was done

Re flashed stock ROM using Odin. I believe I got the file from Samsung's website, but I'm not positive of that. I do know its huge, over 1 gig. If you need help with the re flash I know there are already how to's on here about that, so I won't go into it here.
Sent from my SGH-T999 using xda app-developers app

You must be using a T999 as your sig indicates, not a T999L. Am I correct?
Sent from my SGH-T999 using xda premium

Don't I feel like a tool now. Yes Doc, plain old t999 here. Now that I read back through the whole thread here I see that I was being a bit redundant. Now I will return to my closet under the stairs.
Sent from my SGH-T999 using xda app-developers app

No worries! We all do stuff like that from time to time!
Sent from my SGH-T999 using xda premium

Update without OTA and Kies

Been searching and I can't figure this out.
I have a rooted S3 and I can't get 4.1.2 OTA.
I also have no access to a PC I can install Kies on.
What is another solution to getting the update on a rooted S3?

Do you have a custom recovery installed? If so, you can just flash a debloated stock 4.1.2 ROM from the development section.
Sent from my SGH-T999 using XDA Premium 4 mobile app

joshka89 said:
Been searching and I can't figure this out.
I have a rooted S3 and I can't get 4.1.2 OTA.
I also have no access to a PC I can install Kies on.
What is another solution to getting the update on a rooted S3?
Click to expand...
Click to collapse
Root66. It's in the android dev section.

Aerowinder said:
Root66. It's in the android dev section.
Click to expand...
Click to collapse
Yeah I have CWM recovery.
This shouldn't mess with settings right? the reason I haven't messed with ROMs on this one is because it's all set up like I like it.
EDIT: NV can't flash with Odin. I have a Chromebook. I need a zip to send over Kies air and flash through CWM

joshka89 said:
Yeah I have CWM recovery.
This shouldn't mess with settings right? the reason I haven't messed with ROMs on this one is because it's all set up like I like it.
Click to expand...
Click to collapse
I never recommend dirty flashing (flashing one ROM over another, especially when updating to a newer version of android) it eventually just leads to problems and you'll have to start over again sooner or later.
If you do it the right way, you will have to re-setup the ROM again, pictures, music and files like that will be fine but you'll lose all of your settings.
If you do decide to flash ROMs, before you do, search how to backup your imei, you'll be glad you did if you ever lose it.
Sent from my SGH-T999 using XDA Premium 4 mobile app

It's stock rooted is all, don't want to delete everything just for 4.1.2.
I'll keep searching but it would be easiest to find the update zip file, especially since I won't have access to Odin or anything else to back stuff up and flash in an efficient way
EDIT:
Would sending this zip to the sdcard and apply update through CWM work?
http://honai-android.blogspot.com/2013/05/how-to-update-galaxy-s3-t-mobile-sgh.html

joshka89 said:
It's stock rooted is all, don't want to delete everything just for 4.1.2.
I'll keep searching but it would be easiest to find the update zip file, especially since I won't have access to Odin or anything else to back stuff up and flash in an efficient way
EDIT:
Would sending this zip to the sdcard and apply update through CWM work?
http://honai-android.blogspot.com/2013/05/how-to-update-galaxy-s3-t-mobile-sgh.html
Click to expand...
Click to collapse
That's the firmware for Odin it looks like. If you want you can just download the OTA from my firmware thread. Flash in CWM and it should work and allow you to preserve root. Probably the easiest way to get what you want. If you can use Odin from another computer, root66 is definitely preferred, but there's more than one way to do it.
I agree about the dirty flashing, for the most part. Since you are simply updating the stock firmware, you should be fine. Clean is better of course, but it's up to you. Without starting clean.you do run the risk of having issues down the road, and then you wouldn't even know why.
If you decide to try the OTA, please take a few min to read what I've got there.
Sent from my SCH-I535 using Tapatalk 4

Note 3 issues with CWM/Goo Manager recovery bootloops

Hi XDA! I have a Samsung Galaxy Note 3 N900T T-Mobile. I've had custom roms such as CM11 Nightly in the past. Well after trying to do a fresh install a while back of another custom rom, my phone at first had no OS because I wiped it like a doofus. So I flashed it back to stock, 4.3 at the time. And then starting a couple weeks ago I flashed CWM using CWM Manager app. That's when the same issue that's recurring over and over, began. My phone works great as long as I never reboot into recovery. If I reboot into recovery it gets stuck in a bootloop. However I noticed tonight after trying to reboot into recovery using goo manager, I noticed the last line when it first boots, then bootloops, says Set warranty bit-recovery. If I remember correctly shouldn't it say kernel?? I know this is my fault because I'm not as knowledgable as all of you (I'm still learning on my own). SO my question is this. I want to fix this once and for all because I can't ever flash a custom rom like Darthstalker (that's the one I'd like to flash)...after several failed attempts of flashing CM for example, to no avail. What can I do to fix this once and for all and be able to flash a kernel, and Darthstalker? I can get into download mode, needless to say. ANd all the other times it's bootlooped I flashed KitKat 4.4.2 and everything works fine until i try to reboot into recovery. I am at my witts end because this i I really want a custom rom instead of flashing only the md5. Would anyone please be willing to give me a tutorial of some kind? I know it's a lot to ask but I can't find another reliable source that can explain how to do all of this. You're the only site I trust and if anyone is willing to give mea tutorial via email , PM, etc. I'd be eternally grateful beyond belief. Thank you in advance for any advice or info

I posted a few days ago about my bootlooping in the recovery. I finally fixed it by these 3 steps.
1) Odin flashed Stock 4.4.2 complete as this sets the correct boot loader.
2) I downloaded Twrp 2.7.0 the one that list KitKat (Must say this) 4.4 version.
http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.0-hltetmo-4.4.img.tar
3) Right from Odin when flashing this you set it not to reboot, Once finished you then unplug the usb cable and pull the battery. Let is sit for about 10 sec. Then with the upVlm,Home and Power it will boot to the recovery. It first will post what you said but wait about 10 sec more twrp will come up.
4) Now you should be able to flash any rom you want. I am using axmans N3 for now works great. I will be trying CM 11 later.
5) make a backup once in Twrp
Hope this helps.

helterkelter said:
Hi XDA! I have a Samsung Galaxy Note 3 N900T T-Mobile. I've had custom roms such as CM11 Nightly in the past. Well after trying to do a fresh install a while back of another custom rom, my phone at first had no OS because I wiped it like a doofus. So I flashed it back to stock, 4.3 at the time. And then starting a couple weeks ago I flashed CWM using CWM Manager app. That's when the same issue that's recurring over and over, began. My phone works great as long as I never reboot into recovery. If I reboot into recovery it gets stuck in a bootloop. However I noticed tonight after trying to reboot into recovery using goo manager, I noticed the last line when it first boots, then bootloops, says Set warranty bit-recovery. If I remember correctly shouldn't it say kernel?? I know this is my fault because I'm not as knowledgable as all of you (I'm still learning on my own). SO my question is this. I want to fix this once and for all because I can't ever flash a custom rom like Darthstalker (that's the one I'd like to flash)...after several failed attempts of flashing CM for example, to no avail. What can I do to fix this once and for all and be able to flash a kernel, and Darthstalker? I can get into download mode, needless to say. ANd all the other times it's bootlooped I flashed KitKat 4.4.2 and everything works fine until i try to reboot into recovery. I am at my witts end because this i I really want a custom rom instead of flashing only the md5. Would anyone please be willing to give me a tutorial of some kind? I know it's a lot to ask but I can't find another reliable source that can explain how to do all of this. You're the only site I trust and if anyone is willing to give mea tutorial via email , PM, etc. I'd be eternally grateful beyond belief. Thank you in advance for any advice or info
Click to expand...
Click to collapse
I'm honestly confused on what you are asking. What bootloader are you on . Jellybean or Kit Kat. That is the big part of the question. If you are on Kit Kat you can no longer run Darthstalker as it's a 4.3 rom. Just curious because you say that you flashed 4.4.2 rom and everything works. Also, the bootloop would either be your kernel or your recovery. I would suggest Philz or Twrp 2.7 as they are both updated and will work on either bootloader.
Once you have flashed a bootloader and custom recovery NEVER USE ODIN AGAIN UNLESS YOU HAVE BRICKED YOUR PHONE.

dragonstalker said:
I'm honestly confused on what you are asking. What bootloader are you on . Jellybean or Kit Kat. That is the big part of the question. If you are on Kit Kat you can no longer run Darthstalker as it's a 4.3 rom. Just curious because you say that you flashed 4.4.2 rom and everything works. Also, the bootloop would either be your kernel or your recovery. I would suggest Philz or Twrp 2.7 as they are both updated and will work on either bootloader.
Once you have flashed a bootloader and custom recovery NEVER USE ODIN AGAIN UNLESS YOU HAVE BRICKED YOUR PHONE.
Click to expand...
Click to collapse
I'm on 4.4.2.I figured it is my kernel. After sending this message last night I had my phone in download mode but didn't do anything to it. I decided to turn it off and then on again and it booted. So if this is a kernel issue where would I find one and how would I do this? Oh and when the bootloop occurred last night I was trying to boot into recovery via too manager. If I put Twrp on my phone when I have CWM will they interfere? I apologize for the likely stupid questions but I'm just wanting to get it done properly. One last thing is PacMan ROM compatible?

helterkelter said:
I'm on 4.4.2.I figured it is my kernel. After sending this message last night I had my phone in download mode but didn't do anything to it. I decided to turn it off and then on again and it booted. So if this is a kernel issue where would I find one and how would I do this? Oh and when the bootloop occurred last night I was trying to boot into recovery via too manager. If I put Twrp on my phone when I have CWM will they interfere? I apologize for the likely stupid questions but I'm just wanting to get it done properly. One last thing is PacMan ROM compatible?
Click to expand...
Click to collapse
The kernels you can use are listed in the general thread. A user posted a very good listing of what's what. TWRP 2.7 or Philz Touch are the 2 recoveries i would recommend using. Whichever one you decide will overwrite the other. you can never have 2 recoveries.

OK I'm sorry but I'm a little confused. One solution mentioned was to flash 4.4.2 stock using Odin. But you said not to use it unless I've bricked my phone. So now I'm lost. Lol. Do I flash the stock with the above mentioned method? Or do I flash a kernel and then a ROM? I apologize for my inexperienced questions. I'm including my device info below in hopes you can tell me the very first step I should take. Thank you for all your help!!!
Baseband N900TUVUCNB4
KERNEL- 3.4.0-660648 [email protected]#1
BUILD #- KOT49H.N900TUVUCNB4
SE FOR ANDROID STATUS- ENFORCING SEPF_SM-N900T_4.4.2-0005
SECURITY SOFTWARE VERSION- MOF v1. Release 2
Sent from my SM-N900T using xda app-developers app

helterkelter said:
OK I'm sorry but I'm a little confused. One solution mentioned was to flash 4.4.2 stock using Odin. But you said not to use it unless I've bricked my phone. So now I'm lost. Lol. Do I flash the stock with the above mentioned method? Or do I flash a kernel and then a ROM? I apologize for my inexperienced questions. I'm including my device info below in hopes you can tell me the very first step I should take. Thank you for all your help!!!
Baseband N900TUVUCNB4
KERNEL- 3.4.0-660648 [email protected]#1
BUILD #- KOT49H.N900TUVUCNB4
SE FOR ANDROID STATUS- ENFORCING SEPF_SM-N900T_4.4.2-0005
SECURITY SOFTWARE VERSION- MOF v1. Release 2
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You are already on the 4.4 bootloader so you can no longer use the Darthstalker rom, you can only use Kit Kat 4.4.2 and above roms from here on out. Next question would be have your rooted your phone since the update and have a custom recovery. If you have not rooted, then you will need to use Odin to run the CF_Autoroot, but that will trip your Knox to 0x1. Thus voiding your warranty.

Yes I rooted. But every time I try flashing CWM or Twrp it bootloops. And to get out of bootloop I have to boot in download and then cancel download and it reboots normal again. Is this a kernel or boot loader issue?
Sent from my SM-N900T using xda app-developers app

helterkelter said:
Yes I rooted. But every time I try flashing CWM or Twrp it bootloops. And to get out of bootloop I have to boot in download and then cancel download and it reboots normal again. Is this a kernel or boot loader issue?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Which cwm and twrp are you trying to flash. The only 2 that will work on Kit Kat are PHilz touch latest one, and TWRP 2.7

Twrp 5.7.3
Sent from my SM-N900T using xda app-developers app

So do I flash stock as mentioned from another member or do I flash a kernel? I'm not sure what to do next
Sent from my SM-N900T using xda app-developers app

helterkelter said:
So do I flash stock as mentioned from another member or do I flash a kernel? I'm not sure what to do next
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
oh sorry for the late response. Just got back from boy scouts. Anyway. No you don't need to flash back to stock, Your just flashing the wrong version of TWRP. You can go to the android originial development thread and download the TWRP 2.7 and flash via recovery and you will be all good to go. Also, download the latest Wootever kernel just to make sure you have both angles covered. Both downloads are found in the same section.

Ok thanks so much. Im a little scared to flash in TWRP as it always puts me in bootloops. I did download philz and I was considering flashing that via Odin as I can't boot into recovery. Would that be the next best thing to do? Oh and dont apologize!! I can't thank you enough!
Sent from my SM-N900T using xda app-developers app

helterkelter said:
Ok thanks so much. Im a little scared to flash in TWRP as it always puts me in bootloops. I did download philz and I was considering flashing that via Odin as I can't boot into recovery. Would that be the next best thing to do? Oh and dont apologize!! I can't thank you enough!
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Yes, odin the custom recovery and you should have no more issues. As for the bootloops with TWRP, you only had issues with that, because the version you were trying to use was outdated and does not work on Kit Kat

Hmm found an interesting possible solution and would greatly appreciate your guidance. I found a ROM that supports KK and I think in this thread that it may indicate why I bootloop when trying to bootbin recovery. http://www.infamousdevelopment.com/...-recover-from-a-bad-flash-updated-for-kitkat/
I'm seriously considering following this whole tutorial of his to the letter. Would it be wise to do?
Sent from my SM-N900T using xda app-developers app

helterkelter said:
Hmm found an interesting possible solution and would greatly appreciate your guidance. I found a ROM that supports KK and I think in this thread that it may indicate why I bootloop when trying to bootbin recovery. http://www.infamousdevelopment.com/...-recover-from-a-bad-flash-updated-for-kitkat/
I'm seriously considering following this whole tutorial of his to the letter. Would it be wise to do?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You have already upgraded to Kit Kat, that part is done. and you ran CF_Autoroot correct in Odin correct? If you have done both steps all that is left is to Odin the Philz Touch Recovery that you downloaded.

Ok and yes I did both the first two steps you asked above. After I do flash philz can I flash a ROM it CM or PacMan as long ad they're 4.4.2?
Sent from my SM-N900T using xda app-developers app

helterkelter said:
Ok and yes I did both the first two steps you asked above. After I do flash philz can I flash a ROM it CM or PacMan as long ad they're 4.4.2?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
As long as they are AOSP Roms that support both bootloaders yes, and as i've been told most if not all the AOSP Roms do support the Kit Kat bootloader that you are already on.

Ok thank you again. I will likely flash philz tonight (if hubby allows me to cuz I usually stay up all night til I got my phone the way I want it, ie no boot loops lol) I will report back to let you know if it works. This phone has been through hell and back with me but I've learned a lot!! Especially from contributors such as yourself. :thumbup:
Sent from my SM-N900T using xda app-developers app

Cool. I'm glad I read this thread. I too had same problems.
Sent from my NOTE 3 using Tapatalk