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
Related
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
Hello I tried to flash pure stock then recovery per instructions and now my t999l is stuck on android system recovery can someone plz tell me if I have bricked my phone crying hard right now
In recovery, factory reset. Then reboot and it should work fine.
Stock recovery will wipe your internal sdcard.
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
In recovery, factory reset. Then reboot and it should work fine.
Stock recovery will wipe your internal sdcard.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
Post is difficult to decipher, but I take it that the stock recovery is overwriting his custom recovery... but then the rest of the post doesn't make any sense. Needs clarification.
DocHoliday77 said:
In recovery, factory reset. Then reboot and it should work fine.
Stock recovery will wipe your internal sdcard.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
Mr. Doc I so appreciate you!!! First time posting to thread and Im grateful of your timely response. Let me just tell you exactly whats going on
my phone is in the android system recovery what I am seeing is green android man with a red warning over top of it. it will not let me do anything and I see a message saying "MANUAL MODE" successfully applied multi CSC. It won't connect to ODIN OR Kies Im so scared that I have ruined my phone crying very hard
Odin doesn't work unless you're in download mode.
What happens when you reboot? If it takes you to recovery, boot into download mode (power+vol down+home) and flash a stock image.
imblessed68 said:
Mr. Doc I so appreciate you!!! First time posting to thread and Im grateful of your timely response. Let me just tell you exactly whats going on
my phone is in the android system recovery what I am seeing is green android man with a red warning over top of it. it will not let me do anything and I see a message saying "MANUAL MODE" successfully applied multi CSC. It won't connect to ODIN OR Kies Im so scared that I have ruined my phone crying very hard
Click to expand...
Click to collapse
Also this happened after I flashed the pure stock then I flashed the recovery and the phone automatically went to what I have explained in prior post
When the phone is recovery it doesn't let me do anything factory/reset or anything and when i put in download mode it doesn't connect to ODIN
What rom were you previously using? And you do have a T999L right? You won't be able odin flash any stock firmware because there isn't any.
Try again to get into download mode. If you can boot recovery you should be able to get there too I'd imagine.
Hold volume down and home while powering up.
If you can do this, odin flash either cwm from aerowinders sig, or twrp from mine. Then reflash whichever rom you were running before trying the pure stock rom.
Sent from my SGH-T999L using xda premium
---------- Post added at 01:07 PM ---------- Previous post was at 01:05 PM ----------
Aerowinder said:
Post is difficult to decipher, but I take it that the stock recovery is overwriting his custom recovery... but then the rest of the post doesn't make any sense. Needs clarification.
Click to expand...
Click to collapse
Sorry bout that.
It sounds like he was on another rom and recovery and tried to flash back to stock.
Am I correct?
Sent from my SGH-T999L using xda premium
Hello I'm a she lol but what originally happened was I rooted phone through Odin. Then when I looked in Twrp and cwm it kept saying i had no recovery image. I went through thread on here and saw someone with same issue and follow Mr. Doc's instructions pertaining to the pure stock and recovery and this is where i landed. Im in download mode so yes i see my phone is not ruined lol I just need the file Mr. Doc is telling me about to reflash because im now connected to odin. I had to use another computer. I greatly appreciate all the time taken to help me get my phone back to working order. Since I am new I need to find the place where I can give a lot of Kudos to mr doc and his team now all i need is where to i go for mr doc file
In my signature, click Recoveries. Then in the twrp folder download version 2.5.0.0. Get the one that's a .tar.
Then once connected to odin, click the PDA button and select the tar file you just downloaded. Then click start.
Once done it should auto reboot. Now reboot into recovery and try doing a factory reset there.
If you still can't boot after that, flash the other, deodexed rom from my T999L thread.
I've got to go for a bit but will try to jump back on soon to see how you're doing.
Sorry bout the he/she thing!
Sent from my SGH-T999L using xda premium
Did you get it working?
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
Did you get it working?
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
Yesssss!!!! thank you so much now maybe i can redo what i tried to do
Right on! Glad to hear you're back up snd running!
Let me know if you have any other problems with the T999L stuff.
Sent from my SGH-T999L using xda premium
Thanks Doc and Team T999L!!!
DocHoliday77 said:
Right on! Glad to hear you're back up snd running!
Let me know if you have any other problems with the T999L stuff.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
I just want to thank Mr. Doc and all who are working very hard to create roms for t999L. I had att s3 on tmobile network and got my phone exactly the way i wanted it when my son comes in the house with a tmobile s3 and wanted to swtich with me because he didn't want the color he got (white lol i had red) however I didn't know this phone was very new and the only thing I could do is root lol. I'm waiting patiently because I really love the LIquidsmooth rom so on that note Mr. Doc and team again I thank you for all your hard work!
recovery
imblessed68 said:
I just want to thank Mr. Doc and all who are working very hard to create roms for t999L. I had att s3 on tmobile network and got my phone exactly the way i wanted it when my son comes in the house with a tmobile s3 and wanted to swtich with me because he didn't want the color he got (white lol i had red) however I didn't know this phone was very new and the only thing I could do is root lol. I'm waiting patiently because I really love the LIquidsmooth rom so on that note Mr. Doc and team again I thank you for all your hard work!
Click to expand...
Click to collapse
Mr. Doc what I was originally trying to accomplish was creating a recovery for the phone. I think my phone is only rooted and I have no recovery or so i think for the phone. Can you help me understand lol. I know cwm is not available yet at least it wasn't couple days ago.
goo.im
imblessed68 said:
Mr. Doc what I was originally trying to accomplish was creating a recovery for the phone. I think my phone is only rooted and I have no recovery or so i think for the phone. Can you help me understand lol. I know cwm is not available yet at least it wasn't couple days ago.
Click to expand...
Click to collapse
Mr. Doc when I go into goo.im it tells me in order to flash roms i need an open recovery scrip compatible recovery then it says it can find one for me thats where im lost and getting confused about whether i have a recovery on the phone. but if im right that means i can't right?
Neither CWM or TWRP have added support yet, though it should be as simple as asking. Ill try to contract them in a bit.
You can manually install any of the latest recoveries for the T999 though. They have been confirmed working by several people.
Are you familiar with Odin? I suggest going to the Recoveries link in my sig and get TWRP version 2.5.0.0. The one you want has the .tar extension.
Then flash that in Odin.
If you aren't comfortable with Odin I can tell you another way using terminal emulator.
Your phone does currently have a recovery, but unless you've installed a custom one its still stock.
Also, you can flash any of the Roms posted for the T999. If the rom doesn't include a kernel, and it touchwiz based, you can flash one of the kernels in my T999L thread in development section. I'd try the MD5 kernel first so its matched with the Touchwiz rom you choose. (If you flash CM or AOSP based roms, do not use the kernels I just mentioned).
Hope that helps!
Sent from my SGH-T999L using xda premium
I used the Toolkit to flash mine: http://forum.xda-developers.com/showthread.php?t=1746682
Choose Device option 62 and then Flash custom recovery. It will automate the ODIN install if you are not familiar.
DocHoliday77 said:
Neither CWM or TWRP have added support yet, though it should be as simple as asking. Ill try to contract them in a bit.
You can manually install any of the latest recoveries for the T999 though. They have been confirmed working by several people.
Are you familiar with Odin? I suggest going to the Recoveries link in my sig and get TWRP version 2.5.0.0. The one you want has the .tar extension.
Then flash that in Odin.
If you aren't comfortable with Odin I can tell you another way using terminal emulator.
Your phone does currently have a recovery, but unless you've installed a custom one its still stock.
Also, you can flash any of the Roms posted for the T999. If the rom doesn't include a kernel, and it touchwiz based, you can flash one of the kernels in my T999L thread in development section. I'd try the MD5 kernel first so its matched with the Touchwiz rom you choose. (If you flash CM or AOSP based roms, do not use the kernels I just mentioned).
Hope that helps!
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
I am familiar with Odin i used that to get me up and running again using the sig you just mentioned. If I'm understanding you correctly you're saying I can flash a t999 rom to my t999L but use a different kernel? Also am I flashing the rom using Odin and if so do I use the same method to flash kernel? I think Im getting a clear understanding because I thought I could only root thorugh odin but install roms through cwm and twrp lol and basically I can use Odin to do it all right? I want to make sure I don't have to bother you all the time lol I should have kept my darn att s3!! thanks again Mr. Doc you truly rock!!!!
DJ_SpaRky said:
I used the Toolkit to flash mine: http://forum.xda-developers.com/showthread.php?t=1746682
Choose Device option 62 and then Flash custom recovery. It will automate the ODIN install if you are not familiar.
Click to expand...
Click to collapse
Thank you DJ have you tried any rome yet and you have t999L also?
I am trying to upgrade my Virgin ROM to the 9.12 build but get a fail upon trying to flash it. The background.... I'm using TWRP recovery and have tried the chainfire root method. Here are the results:
As you can see you can see some conflicting information... all shots were taken in sequence. I'm thinking the fail in twrp is coming from the system not having root but the info is telling me otherwise....
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Do you have the latest SuperSU version?
I'm a little lost at what you are saying.
You flashed a rom, and it said fail, and you think it has to do with Root?
If you have TWRP installed it doesn't matter if you are rooted or not. It's going to over right the system partition regardless if you have root or not.
So it's either a bad download or bad transfer for it to fail.
Sent from my SGH-M919 using Tapatalk 4
I do have the latest SU version by chain fire. And maybe I'm doing something wrong the because I am running the virgin gpe ROM now and that flashed in twrp with no issues. Now when I go to install (after wiping) and select the 9.12 update that I downloaded it hangs on trying to open the zip and fails... I haven't changed any twrp settings but in the write options of twrp what boxes should be checked because system is not by default... Thanks for the replies!
Sent from my GT-I9505G using xda app-developers app
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
You can give CWM a try, I've been using it for a while without any issues. Out of curiosity what version if TWRP you are using? I think most people recommend TWRP 2.5.0.2. I'm using the latest version of CWM.
Sent from my GT-I9505G using xda app-developers app
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
norml said:
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
Click to expand...
Click to collapse
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
th3h0ff said:
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
Click to expand...
Click to collapse
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
mrvirginia said:
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
Click to expand...
Click to collapse
Im going to give the twrp 2.5.2 a try as it seems most of my troubles keep happening on the 2.6.3 build. Hopefully that works either way its back to CWM for me as well. Thanks again for taking the time to help out and again sorry about hijacking the thread for a page... Your ROM is absolutely perfect so I appreciate the efforts and time!,
Andrew
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
th3h0ff said:
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
Click to expand...
Click to collapse
Good to know you are out of trouble
Sent from my Nexus 10 using xda app-developers app
See you shoulda said you were running 2.6.3 lol
word of advice (and to all who run twrp)
DO NOT RUN ANYTHING GREATER THAN 2.5.2!!!!!!!!!!!!!!
After ota 4.3 on stock att I747 Itried cf autroot and installed trp successfully. Somehow wiped the os off and now stuck n Samsung screen. I can get into download mode and recovery please help
You can load a custom recovery in Odin and flash a custom ROM.
Brandon136 said:
After ota 4.3 on stock att I747 Itried cf autroot and installed trp successfully. Somehow wiped the os off and now stuck n Samsung screen. I can get into download mode and recovery please help
Click to expand...
Click to collapse
Annoying, but not that hard to fix. You have two or three choices. If you made a backup, you can restore that from recovery mode.
You could go to download mode and flash a stock ROM onto the phone, then root it again.
Or you can go with a custom ROM as the poster above suggested. You generally need a custom recovery for that, so you'd go to download mode and install a custom recovery first. Followed by the custom ROM. If the custom ROM is a tar file, you'd also flash that with Odin in download mode. If it is a flashable zip file then the custom ROM would be flashed after you boot to the custom recovery mode first.
If flashing a stock image, ensure that it is a version 4.3 AT&T image. Trying to flash an earlier version will do bad things to your phone.
.
fffft said:
Annoying, but not that hard to fix. You have two choices.. you can go to download mode and flash a stock ROM onto the phone, then root it again.
Or you can go to download mode and install a custom recovery, followed by a custom ROM as the poster above suggested. If the custom ROM is a tar file, you'd also flash that with Odin in download mode. If it is a flashable zip file then the custom ROM would be flashed after you boot to the custom recovery mode first.
If flashing a stock image, ensure that it is a version 4.3 AT&T image. Trying to flash an earlier version will do bad things to your phone.
.
Click to expand...
Click to collapse
As far as I know, there is no stock 4.3 AT&T image available because one was never released by AT&T. However, I think there may be some 4.3 based ROMs that can be flashed.
Mobile Odin can also be used to flash an image since mobile Odin does not flash a bootloader or modem.
audit13 said:
As far as I know, there is no stock 4.3 AT&T image available because one was never released by AT&T. However, I think there may be some 4.3 based ROMs that can be flashed.
Mobile Odin can also be used to flash an image since mobile Odin does not flash a bootloader or modem.
Click to expand...
Click to collapse
It can be painful to be an AT&T customer at times. If a full factory 4.3 ROM wasn't released, the OP could still flash a properly formatted backup of someone's stock AT&T 4.3. But it would of course be easier to adopt a custom ROM as you suggested. One choice would be S3Rx 3.0.
.
Thanks for the help. However I tried to flash several 4.3 stock based roms and got nothing. I had an older s3 with a busted screen so I took the mother board out and put in this. I then flashed twrp and rooted. Im on the ota 4.3 and would really like a custom rom. Im currently on the hunt.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Brandon136 said:
Thanks for the help. However I tried to flash several 4.3 stock based roms and got nothing. I had an older s3 with a busted screen so I took the mother board out and put in this. I then flashed twrp and rooted. Im on the ota 4.3 and would really like a custom rom. Im currently on the hunt.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
You didn't give us nearly enough details to really know what you tried, let alone why it might have failed. AT&T is much more restrictive than most carriers and is locking their bootloader, so you have to be careful not to flash someone else's bootloader or a pre 4.3 version.
But since you have a rooted phone again.. installing a custom ROM wouldn't be hard to do.. I gave you a link to decent custom ROM that would work for you. Or you can browse other custom ROMs if you prefer. There are detailed instructions in the thread to guide you. Basically confirm that you have one of the listed AT&T bootloaders and modems, download the custom ROM to your phone, boot to twrp, do a "factory wipe", then install the custom ROM (flashable zip file) from the twrp install menu.
.
Try Philz Touch recovery instead of TWRP. If it doesn't work with Philz, let us know the error messages you're getting.
Can you post a link where I can find custom roms for att i747. Sorry for the noob question I have looked and cannot find one. Thank you. Im on rooted ota 4.3 with twrp currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Brandon136 said:
Can you post a link where I can find custom roms for att i747. Sorry for the noob question I have looked and cannot find one. Thank you. Im on rooted ota 4.3 with twrp currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
You can't find custom rooms cause you're blind or can't read. Backup out of the Q&A forum to the s3 page with all the forum listing then click on the forum that says AT&T galaxy s3 development. If you can't find one there you need to stop trying...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Brandon136 said:
Can you post a link where I can find custom roms for att i747. Sorry for the noob question I have looked and cannot find one. Thank you. Im on rooted ota 4.3 with twrp currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have had better luck flashing ROMs with CWM than TWRP.
There are lots of ROMs here: http://forum.xda-developers.com/galaxy-s3-att/development
Couldmyou point me in the direction to switch over. I have read alot on that same issue
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Download Philz Touch zip from here and flash in TWRP. Reboot into recovery and you should have CWM installed.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Sammobile.com has the stock images don"t they? Thats where i got my Fido factory image.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I know thats right. This is my first so needless to say its all new. I looked for just custom roms and not delelopment. Sorry, thanks for the help.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Brandon136 said:
I know thats right. This is my first so needless to say its all new. I looked for just custom roms and not delelopment. Sorry, thanks for the help.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Any luck?
Yes I have cwm and titanium back pro, busy box pro, and a few other goodies. So I made me a backup and flashed 4.4.2. I'm playing with it now. It seems really solid and way better customizations. I'm about to head over and give the developers thanks. Thank you as well for your advice.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Just was wondering if anyone has run into this issue. I have tried flashing zips Odin and apps to install recoveries. Any version of TWRP I install will just put the phone in bootloop til I Odin a diff recovery. I have tried googling around and only thing I could get is maybe my motherboard going out. I know when I was on Whomp 4.1.2 I had always used twrp before 4.3 came out. I still have no Knox boot loader and never have had Knox on phone either. Could this just be a sign that I have corrupt memory sectors ? Any help or tips appreciated. Just trying to get phone to last til note 4. Other things I've done is even unmod back to old firmware and let it ota all the way to mc2 so I don't get a knox boatloader. Thanks again
Shadowpaw said:
Just was wondering if anyone has run into this issue. I have tried flashing zips Odin and apps to install recoveries. Any version of TWRP I install will just put the phone in bootloop til I Odin a diff recovery. I have tried googling around and only thing I could get is maybe my motherboard going out. I know when I was on Whomp 4.1.2 I had always used twrp before 4.3 came out. I still have no Knox boot loader and never have had Knox on phone either. Could this just be a sign that I have corrupt memory sectors ? Any help or tips appreciated. Just trying to get phone to last til note 4. Other things I've done is even unmod back to old firmware and let it ota all the way to mc2 so I don't get a knox boatloader. Thanks again
Click to expand...
Click to collapse
If you want twrp you need one of the versions before 2.7. Thing is twrp does not handle selinux context so it wont work on tw 4.3-4.4.3 and aosp 4.4.+.
I would suggest philz 6.07.9 it handles everything perfectly. So give it a shot and still have problems let me know.
Sent from my GT-N7105 using XDA Premium 4 mobile app
jlmancuso said:
If you want twrp you need one of the versions before 2.7. Thing is twrp does not handle selinux context so it wont work on tw 4.3-4.4.3 and aosp 4.4.+.
I would suggest philz 6.07.9 it handles everything perfectly. So give it a shot and still have problems let me know.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've read doesn't work on new versions but I 1st had the issue start months ago on 4.1.2 whomp I rebooted to recovery one day after on same ROM over 2 months not a issue and boot loops started then and haven't been able to use twrp since. Last night I finally wanted to try a 4.4 ROM and thats why I just now was posting about it. I'm on philz currently. I'll just stick with what works. Thanks again!
Sent from my SPH-L900 using XDA Premium 4 mobile app
Shadowpaw said:
I've read doesn't work on new versions but I 1st had the issue start months ago on 4.1.2 whomp I rebooted to recovery one day after on same ROM over 2 months not a issue and boot loops started then and haven't been able to use twrp since. Last night I finally wanted to try a 4.4 ROM and thats why I just now was posting about it. I'm on philz currently. I'll just stick with what works. Thanks again!
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In case you dont already know philz can use you old twrp backups also.
Sent from my GT-N7105 using XDA Premium 4 mobile app