Help! Can't flash any touchwiz roms after cm10.2 - AT&T Samsung Galaxy Note II

I can't flash any TW ROM after flashing cm10.2 I can only flash AOSP ROMs. any advice would help. When I flash TW ROMs it gets stuck on bootloop and yes I do full wipes of everything.
Sent from my SGH-I317 PACMAN 4.3

Jonnyaces187 said:
I can't flash any TW ROM after flashing cm10.2 I can only flash AOSP ROMs. any advice would help. When I flash TW ROMs it gets stuck on bootloop and yes I do full wipes of everything.
Sent from my SGH-I317 PACMAN 4.3
Click to expand...
Click to collapse
Did you flash the downgrade zip in the op of the cm10 thread?
Sent from my SGH-T889 using xda app-developers app

kintwofan said:
Did you flash the downgrade zip in the op of the cm10 thread?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
No. I didn't know there was one. Thanks for the info. I'm going to check now.

kintwofan said:
Did you flash the downgrade zip in the op of the cm10 thread?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Do you have a link for that ZIP? I'm running into a similar problem after flashing CM10.2 and can't flash a TW Rom on my S4.
Thanks!

10.2 sucks
the same thing happened to me, but i am using the stock firmware and using a tutorioal on how to unroot unbrick note 2 i hope that brings my phone to normal. and then refalsh and load jedi x 17. ALSO AT ONE POINT I DONT KNOW WHAT I DID WRONG BUT THE PLAY STORE WANTS INCLUDE IN THE 10.2 ROM THAT I INSTALL AND THE WEB PLAY STORE WOULD RECOGNIZE MY DEVICE AS NEXUS 7, BUT IT IS A NOTE 2. THAT WAS WEIRD.

@BB said:
Do you have a link for that ZIP? I'm running into a similar problem after flashing CM10.2 and can't flash a TW Rom on my S4.
Thanks!
Click to expand...
Click to collapse
First page look for restore sd-downgrade.
http://forum.xda-developers.com/showthread.php?t=2105917

downgrade.zip will NOT do ANYTHING to help your issue; all it does it change the files system back to the way it is in 4.12
something else is wrong, but you have to post more info; what rom you flashed, what recovery/version you are on, what the error message/code is when you try to flash, etc...

jon3sh said:
First page look for restore sd-downgrade.
http://forum.xda-developers.com/showthread.php?t=2105917
Click to expand...
Click to collapse
Thanks for the reply ...
wase4711 said:
downgrade.zip will NOT do ANYTHING to help your issue; all it does it change the files system back to the way it is in 4.12
something else is wrong, but you have to post more info; what rom you flashed, what recovery/version you are on, what the error message/code is when you try to flash, etc...
Click to expand...
Click to collapse
Thanks even more for letting me know that this won't do the trick. I should start by reiterating that I have a S4 on Sprint and not a Note 2 on AT&T, so I before I get flamed for being in the wrong forum, just wanted to check if I should go further on what I'm running and the "error" I'm experiencing to see if you can help. I'd really appreciate it if you could but don't want to break any rules ...

its not so much about breaking the rules, as it is about giving you advice that could harm your device, since its not the same as this threads'
I would take it to the s4 threads, just to be sure
good luck

So still no luck with this for me. Someone please help. I can only flash non touchwiz ROMs. I am running pacman nightly 4.3 9-7-13 version. I just flashed devil kernel to see if it would fix the issue. No luck but definetly a nice kernel. I try to flash jedix17 16 and even a nandroid I had from 16 no luck. Tried several other tw ROMs but it just gets stuck on bootloop. Hellllllllllp I like pacman but I was flashing roms everyday and I'm going nuts. I brick my gs3 backup phone so I have to be very careful now with only one phone. Advice?????
Sent from my sgh-i317 using pacman nightly

Okay. ....do you show correct IMEI Number ?
And do you have data ?
If yes. ..then let's try this. ..(deep breath)..(make a backup)...then the following:
First. ...boot to recovery and wipe data, caches, and internal storage. ..
Basically everything without touching your external card. ..and just to be sure. .take it out and set it aside. .(make sure to unmount it in settings first !!!)
Next. .turn off the device and boot into download mode. ..(ready for Odin)
Then using only your PC...download Mr. Robinsons rooted UCAMA4 build from his thread. .. (in the development section)..
Next. ..push the image you just downloaded to the device via Odin. ..(use the PDA box...and don't change any Odin settings)...
Next. ..wait for the image to automatically boot the device once completed. ....(unplug the device)..
If the device fails to boot. ..pull the battery. ..wait 30 seconds. ..then replace it and boot into the newly flashed 3e recovery and wipe cache and data 2 times each. ..then reboot.....
If the device boots normally then move to the next step. ..and if not. ..repeat the flash process again using Odin and the rom you downloaded. ..
If after two unsuccessful flashes, and wipes using 3e recovery, and battery pulls. ..you still don't get a successful boot. ..you may have partition damage. ..in which case a repair may be needed. ..but for the sake of your phone we'll wait until the above has failed. ..
Next. ...If boot occurs using the above method. ..enter your wifi password and log into the play store and download triangle away if you want your counter reset. .
If not. ..skip the play store after entering the wifi password and move into your settings/about phone/software update. ..
Push the update button and wait for ATT to offer you the update to UCAMC3..then take it. ..
If desired you can then clear the flash counter and unroot...
Let's get that far before worrying about anything else. ..
Please record any errors or messages you get. ..especially while using Odin. ..as this tells us the device partition state. ..especially when PIT files are involved. .
Sorry for the long post. ..but it was necessary. ..I hope. .
Please post back. ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app

Related

[Q] CWM Recovery on i317M

Hi,
I'm having issues installing CWM Recovery on my Rooted GN2. It's the Canadian variant, SGH-I317M.
It does go through the process of flashing the recovery, but never gets to saying PASS in ODIN. When I try to get into the Recovery, it still has the stock Samsung Recovery. It does, however trip the flash counter.
I'm followiing the instructions here: http://forum.xda-developers.com/showthread.php?t=1988785
This is what I get after flashing in ODIN.
Maybe a bad download? Have you checked to see if it installed? I dont usually recommend this but koush's Rom Manager supports our device now, you can use the app to flash it if your already rooted:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
In your screen shot it shows the f-reset box checked I believe it should be unchecked.
Slff said:
In your screen shot it shows the f-reset box checked I believe it should be unchecked.
Click to expand...
Click to collapse
I tried it with the f-reset box unchecked, and I got it to say PASS, but still no CWM...
cdshepherd said:
Maybe a bad download? Have you checked to see if it installed? I dont usually recommend this but koush's Rom Manager supports our device now, you can use the app to flash it if your already rooted:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
I've also tried to download the file again, and still... No dice...
BlueBagodah said:
I tried it with the f-reset box unchecked, and I got it to say PASS, but still no CWM...
I've also tried to download the file again, and still... No dice...
Click to expand...
Click to collapse
Try rom manager?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Try rom manager?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
ROM Manager doesn't have a Recovery for the Rogers i317M...
http://forum.xda-developers.com/showthread.php?t=1988785
Sent from my SAMSUNG-SGH-I317 using xda premium
twanskys204 said:
http://forum.xda-developers.com/showthread.php?t=1988785
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks,
I've been following that thread, and it doesn't work. It will trip the flash counter, but doesn't actually install the recovery. It appears that I'm not the only one having this issue after the most recent OTA update...
Can u try and flash a kernel
Then try flashing cwm ...just a hunch
Sent from my SAMSUNG-SGH-I317 using xda premium
BlueBagodah said:
Thanks,
I've been following that thread, and it doesn't work. It will trip the flash counter, but doesn't actually install the recovery. It appears that I'm not the only one having this issue after the most recent OTA update...
Click to expand...
Click to collapse
I'm also having problems after the OTA update. Before OTA update, I was able to flash CWM without problems. Following exact same procedure as before when it was working. Only variable that changed is the OTA update.
wiser212 said:
I'm also having problems after the OTA update. Before OTA update, I was able to flash CWM without problems. Following exact same procedure as before when it was working. Only variable that changed is the OTA update.
Click to expand...
Click to collapse
I was able to install CWM by following this post: http://forum.xda-developers.com/showpost.php?p=36201055&postcount=54
But I'm starting to think that it may have been my fault the whole time...
While doing the 3 button combo to try to boot into Recovery, I was using Vol-DOWN, instead of Vol-UP. So I was going into download mode. I'm going to try flashing the CWM through ODIN again and see if I was just an idiot the whole time.
***EDIT***
It looks like I was just an idiot the whole time...
*facepalm*
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
.. so ROM manager doesnt work to insall cwm recovery after rooting on the i317m? i tried it and didnt succeed. i guess flashing is my only option but i dont want to lose anything on my phone. just install the bootloader/ recovery with no other changes. i want to start flashing some roms... jedi first.. skynote after.. any thoughts or help would be great!!
Clean rom I would suggest its awesome battery life I have a universal theme flashed over clean rom and a custom blue keyboard if I find the link to the themes ill post em on here
Sent from my sgh-1317 aka MY BLUE DEVIL using xda premium
Dewaynelives said:
Clean rom I would suggest its awesome battery life I have a universal theme flashed over clean rom and a custom blue keyboard if I find the link to the themes ill post em on here
Sent from my sgh-1317 aka MY BLUE DEVIL using xda premium
Click to expand...
Click to collapse
I thought of cleanROM but it is pretty stock. I feel if im going to flash any rom i might as well go with something modded and tweaked rather then stock, while keeping most of the note 2 and s-pen features. If i start finding them being a little buggy or draining my battery or anything, ill settle with cleanROM and just flash some custom mods.
i flashed my CWM through MobileODIN. worked like a charm. then i ran into issues with backing up to extSD, which ended up working after i formatted it but i took way longer then onto internal SD.
i know its off topic for this thread..Any suggestions or thoughts on the JEDI X9 and SKYNOTE roms will be great guys. Im all backed up and ready to flash pretty quick here.
I guess you have custom ROM. You must root and rename recovery restore files before you boot to android or stock recovery will be restored.

.com.android.phone MD5 Videotron

Am I the only one with videotron that is getting the error when trying to flash any of the new MD5 rom. Did a FW and tried all of the new rom's and no matter which one I install I'm getting the error process.android.phone FC. Even went back to stock and nothing is working
Thanks
rener78 said:
Am I the only one with videotron that is getting the error when trying to flash any of the new MD5 rom. Did a FW and tried all of the new rom's and no matter which one I install I'm getting the error process.android.phone FC. Even went back to stock and nothing is working
Thanks
Click to expand...
Click to collapse
Perhaps this T999 4.1.2 firmware update was not meant for your videotron phone.
It looks like you will need to get a hold of the stock Odin flash rom for your phone
and Odin flash it before you can do anything else.
Here is the link for the Odin Flash stock Videotron firmware for your phone in case you want
to flash it and start over again: http://www.androidfilehost.com/?fid=9390225151984927270
Misterjunky said:
Perhaps this T999 4.1.2 firmware update was not meant for your videotron phone.
It looks like you will need to get a hold of the stock Odin flash rom for your phone
and Odin flash it before you can do anything else.
Here is the link for the Odin Flash stock Videotron firmware for your phone in case you want
to flash it and start over again: http://www.androidfilehost.com/?fid=9390225151984927270
Click to expand...
Click to collapse
I did that and I still got the error :s
re: fc
rener78 said:
I did that and I still got the error :s
Click to expand...
Click to collapse
Try this:
Go into CWM or TWRP recovery and "Fix Permissions" then reboot.
If you still have the problem go into CWM or TWRP again and do a
factory reset/wipe cache/wipe dalvik cache but do not wipe system.
After doing that fix permissions again and reboot the phone.
Thanks alot but I give up I've tried what you told me and I still get the error. I guess it's just not ready as you said...Thanks alot again
Misterjunky said:
Try this:
Go into CWM or TWRP recovery and "Fix Permissions" then reboot.
If you still have the problem go into CWM or TWRP again and do a
factory reset/wipe cache/wipe dalvik cache but do not wipe system.
After doing that fix permissions again and reboot the phone.
Click to expand...
Click to collapse
Are you just trying to flash the firmware? If so is there any you can flash so that its back to normal and working? You mentioned the error happened when trying to use the vtron fw is why I ask.
If you can get it working, flash jovys stock rom instead of the firmware. I dont see why this wont work if your up and running beforehand.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Are you just trying to flash the firmware? If so is there any you can flash so that its back to normal and working? You mentioned the error happened when trying to use the vtron fw is why I ask.
If you can get it working, flash jovys stock rom instead of the firmware. I dont see why this wont work if your up and running beforehand.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried to flash Jovy's stock MD5 rom and got the FC error, so I decided to go back to rooted stock and then flashing back Jovy's and other MD5 rom and still getting the FC. Will now try Jamieson rom and see from there again. Will post the results.
EDIT Still a no go under Infamous as well. Freaking mad
Thanks
Thats odd. It should work. Let me know how the other goes. Im out until a little later tonight so may not reply for a bit. Good luck!
Sent from my SGH-T999 using xda premium
I'm with Videotron I did get that error, try an original AOSP or CM ROM... Sometimes other ROMS implements T-Mobile features that our SIM i'snt compatible like the Mobile HotSpot App. And dont forget to fully wipe and factory reset it after !
Do you happen to have mobile odin pro? If so, try flashing the root66 firmware that way. Deselect the modem and flash.
Be prepared with a backup and with odin and your stock firmware though, just in case.
The more I think about it, the more I wonder if its a kernel issue. Youre still using your vtron 4.1.1 kernel with tmobiles 4.1.2 system. Before trying the fw, try flashing the kernel that comes with md5. If you cant find it ill post it up in a while.
I dont know how likely this is the prob, but may be worth trying...
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Do you happen to have mobile odin pro? If so, try flashing the root66 firmware that way. Deselect the modem and flash.
Be prepared with a backup and with odin and your stock firmware though, just in case.
The more I think about it, the more I wonder if its a kernel issue. Youre still using your vtron 4.1.1 kernel with tmobiles 4.1.2 system. Before trying the fw, try flashing the kernel that comes with md5. If you cant find it ill post it up in a while.
I dont know how likely this is the prob, but may be worth trying...
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks again I have tried with a 4.1.2 kernel and it's still not working, I couldn't find anywhere the kernel coming with MD5. Looked in [Baseband] ALL T999(V) Modems! w/ MAP and Data Tweaks! and couldn't find it aswell.
Cause I used multi-carrier rom 4.1.2 before, Sprint, AT&T, Verizon but for some reason this one is giving a hell of a time.
Even tried an AT&T port of this T-mobile update and it wasn't working
Thanks alot again I really appreciate it
Well there's an update. None of the MD5 rom is working for me I always get the error. But 4.1.2 ports from other carriers are working. Really strange. So I guess I just need to wait for the official update.
**Edit** Well stockorama is actually working.. Weird
Is there anyone with a videotron sgs3 running an MD5 rom?? Cause I can't, only stockorama 2 other than that I cannot..

[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

Help!!!!!!

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?

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

Categories

Resources