Develop Bugs

[Q] Root question

Okay so my dumbass rooted my phone and didn't select a recovery menu >_> wasn't planning on installing anything because everytime i have my phone ends up running crappy even after going back to stock. anyway i just found out that there is a multi window mod but i have to flash it and a rom (Thanks to the guys who made them) do i have to flash to stock then go and re root or can i just run the root program again and this time select a recovery?

You didn't puy any recovery on? So that means you still have the stock one? If not I would say to go through ODIN and flash the phone back to stock, then re-root with TWRP. One of the devs here have a 1 click exe to recover stock through ODIN (saved my ass last night when I wiped the rom AND my recovery folder )

bl4ckllama said:
You didn't puy any recovery on? So that means you still have the stock one? If not I would say to go through ODIN and flash the phone back to stock, then re-root with TWRP. One of the devs here have a 1 click exe to recover stock through ODIN (saved my ass last night when I wiped the rom AND my recovery folder )
Click to expand...
Click to collapse
Oh god lol Can you link me to that real fast im helping my sister or would track it down. I didn't flash a recovery because i wasn't going to use a rom but found i need to have a recovery to flash the multiwindow mod... I guess back to stock i go even tho i'm already rooted bahaha

I did this last night.
http://rwilco12.androidfilehost.com...sung Galaxy Note II (SPH-L900)/LJC/ROM/Rooted
Download the exe. Put the phone in ODIN. Once the exe is running, plug in the USB and his start. About 20 minutes and you'll have a clean, stock rom on there. You'll need to re-root once done.

bl4ckllama said:
I did this last night.
http://rwilco12.androidfilehost.com...sung Galaxy Note II (SPH-L900)/LJC/ROM/Rooted
Download the exe. Put the phone in ODIN. Once the exe is running, plug in the USB and his start. About 20 minutes and you'll have a clean, stock rom on there. You'll need to re-root once done.
Click to expand...
Click to collapse
What do you mean by odin as in download mode? or do i need to download odin

Yeah, sorry Volume down, power and center button all at the same time.

bl4ckllama said:
Yeah, sorry Volume down, power and center button all at the same time.
Click to expand...
Click to collapse
Lol no problem you confused me im like wait my phone can enter odin huh XD you guys might refer to it as that ive been out of the scene for awhile lol thanks again bud

cant you just use odin to flash custom recovery if ur already rooted? Should just be able to download the appropriate tar file for whatever u choose our am I mistaken?
Sent from my SPH-L900 using xda app-developers app

goodpup420 said:
cant you just use odin to flash custom recovery if ur already rooted? Should just be able to download the appropriate tar file for whatever u choose our am I mistaken?
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure thats what i'm asking haha i'm already rooted i ran a program that rooted it for me (something QBking uses) and i did just a basic root so I didn't know if i had to restore it to stock then re root or if there was a way to just install my custom recovery

goodpup420 said:
cant you just use odin to flash custom recovery if ur already rooted? Should just be able to download the appropriate tar file for whatever u choose our am I mistaken?
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
kittyslasher said:
I'm not sure thats what i'm asking haha i'm already rooted i ran a program that rooted it for me (something QBking uses) and i did just a basic root so I didn't know if i had to restore it to stock then re root or if there was a way to just install my custom recovery
Click to expand...
Click to collapse
yes you can. just download a recovery image .img file, load odin and flash it with odin. and btw, this should be in the Q & A section

t3project said:
yes you can. just download a recovery image .img file, load odin and flash it with odin. and btw, this should be in the Q & A section
Click to expand...
Click to collapse
Where can i get the recovery image from?

kittyslasher said:
Where can i get the recovery image from?
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/t0ltespr/openrecovery-twrp-2.3.2.3-t0ltespr.img.tar

Hmm... you didn't read and follow the directions exactly? Not too much sympathy here. Sorry to be an ahole, but jeez, look before you leap. It literally takes 5 minutes to read and 2 minutes to follow directions.

monkey3ddd said:
Hmm... you didn't read and follow the directions exactly? Not too much sympathy here. Sorry to be an ahole, but jeez, look before you leap. It literally takes 5 minutes to read and 2 minutes to follow directions.
Click to expand...
Click to collapse
and even less time to reply but you did it anyway

Wrong section...need to be in Q&A

monkey3ddd said:
Hmm... you didn't read and follow the directions exactly? Not too much sympathy here. Sorry to be an ahole, but jeez, look before you leap. It literally takes 5 minutes to read and 2 minutes to follow directions.
Click to expand...
Click to collapse
I flashed not wanting to do roms thats why i didn't originally chose a custom recovery >_>

kittyslasher said:
I flashed not wanting to do roms thats why i didn't originally chose a custom recovery >_>
Click to expand...
Click to collapse
My question is y root at all? If there was no purpose its seems a little silly. Just my 2 cents.
Sent from my SPH-L900 using xda premium

I'm rooted and running stock right now. Waiting for something that works across the board for me. But I do like to try everything that comes out Also apps like Lucky Patcher need it and I installed the DPS audio manager.
Of course, as soon as CM10 starts rocking the BT streaming I'll be a downloading.

When I first rooted for some reason I couldnt get a custom recovery to stick. I tried multiple times with no luck so eventually I just downloaded goo manager and installed custom recovery script that way. Worked like a charm. Maybe you should try that. Would save a lot of time and effort.
Sent from my SPH-L900 using xda app-developers app

rbtrucking said:
When I first rooted for some reason I couldnt get a custom recovery to stick. I tried multiple times with no luck so eventually I just downloaded goo manager and installed custom recovery script that way. Worked like a charm. Maybe you should try that. Would save a lot of time and effort.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
That's because the file on stock roms called /system/recovery-from-boot.p will re-install the stock recovery at every boot. So the trick is to boot straight into recovery and delete that file. Or, flash the Superuser.zip in recovery, boot Android, use an app to delete /system/recovery-from-boot.p, then flash a custom recovery again and you'll be fine.

At a loss with cwm

Hello,
So I've been rooted for a while now, i was going to install a custom rom but decided not to a few months ago. Tonight, i decided to install aokp, however my phone would not go into cwm, only stock recover. I could have sworn it was installed, but fine, so i installed it once again with auto reboot in odin checked, and it still wouldnt enter cwm. I then tried to install it again with auto reboot checked off so i could see if i could enter it without the reboot. I ended up getting into it, but then when i was taking a NANDROID, it just froze on one of the first steps. Fine, reboot, try to enter cwm again. Nope, just stock android recovery. I am sure im installing it correctly and pressing the right button combos. I am at a total loss for what is stopping me from being able to enter cwm. I hope you guys know/help me find whats going on.
Thanks!!!
Zay

maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.

pcshano said:
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
Click to expand...
Click to collapse
Yes my phones rooted.
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..

Zay48 said:
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Click to expand...
Click to collapse
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951

pcshano said:
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
Click to expand...
Click to collapse
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks

Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
if you still want cwm then i guess you can try flash stock rom and root it again and see
since you're going to flash a custom rom which will delete all your data anyways

Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app

RPelham said:
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?

Zay48 said:
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Click to expand...
Click to collapse
Bump

what version of CWM are you currently running?

you could always try to download GooManager or ROM Manager from the Play Store.
then from one of those, install the custom recovery, GooManager for TWRP or ROM Manager for CWM.

xBeerdroiDx said:
what version of CWM are you currently running?
Click to expand...
Click to collapse
3.0.7

Zay48 said:
3.0.7
Click to expand...
Click to collapse
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app

CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).

zetsui said:
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
Click to expand...
Click to collapse
He's not having a problem restoring images, he's having a problem making his first nandroid.
Sent from my SGH-I747 using xda app-developers app

Zay48 said:
3.0.7
Click to expand...
Click to collapse
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
RPelham said:
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.

Download rom manager and update your cwm and then try making a nandroid again.
Sent from my SGH-I747 using xda app-developers app

CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
That said... If you insist in CWM, this is the guide I followed to get a successful CWM flash. (This was the CWM I was running successfully for the brief time TWRP disbanded.)
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
The above is for the ATT variant only. If you have a different variant and can't find the link, post back and I'll find it for you
Sent from my SGH-I747 using xda app-developers app

CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
apparently it's still around because new android users who want to root use those guides with outdated files

RPelham said:
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Preach brother!

HELP PLEASE t889V stuck on Samsung logo

Hi Guys need help bad. I hope I didnt screw my phone up.
I rooted my phone using the latest toolkit and installed twrp. Once i did that I backed up everything including efs on the external card.
Once i did that I flashed Jedi x rom but did not have much signal so decided to flash another rom which was liquid smooth. Once I flashed it again
my signal was almost non existent. I downloaded a canadian modem in the zip file and flashed it using twrp the same way i would flash a rom.
After i did that i wiped all the data and cache and the system. As I was rushing it siince its late at night i got a message saying that I am not rooted. I ignored it and rebooted the system and now its stuck on samsung logo. What can i do? Please help!!!!!
It appears that when I hold vol up plus home plus power I can get into download mode. I hope that helps.
Can someone give me some help how to get it back to life. I am pretty sure I have to use Odin at this point but dont know how

Ok i did some reading and I think the next step is to download stock image for the wind mobile turn on Odin and upload the image to the phone..
What settings should I use in Odin? What should be checked at the top and am I to use PDA only?

You can use odin or just reflash the ROM. You said tout wiped system after flashing the modern. That means you erased what ever ROM was on there. It's sticking at Samsung because there is no ROM to boot into.
Sent from my SGH-T889 using xda app-developers app

kintwofan said:
You can use odin or just reflash the ROM. You said tout wiped system after flashing the modern. That means you erased what ever ROM was on there. It's sticking at Samsung because there is no ROM to boot into.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Well I cant get into TWRP and dont know how to flash a ROM through ODIN? I am total newb at this.
Could you give me some pointers once I open up odin what do i need to do ? Thanks

Have you puked the battery. Put it back in then held volume+, home and power? Your recovery should still be there.
Also, odin is easy. Just open it and click the pda box and put your stock ROM there. Two things make sure you put your image in PDA and PDA ONLY and make sure it's your official stock Image
Sent from my SGH-T889 using xda app-developers app

kintwofan said:
Have you puked the battery. Put it back in then held volume+, home and power? Your recovery should still be there.
Also, odin is easy. Just open it and click the pda box and put your stock ROM there. Two things make sure you put your image in PDA and PDA ONLY and make sure it's your official stock Image
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Yup went back to ODIN and flashed stock image and everything is now working great. I assume that I need to root the phone again before attempting to flash any roms again. I guess it was late at night and like you said I wiped the rom and there was nothing to boot into. I am an idiot!
Thanks for your quick help !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

vseslija said:
Yup went back to ODIN and flashed stock image and everything is now working great. I assume that I need to root the phone again before attempting to flash any roms again. I guess it was late at night and like you said I wiped the rom and there was nothing to boot into. I am an idiot!
Thanks for your quick help !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Next time odin this http://forum.xda-developers.com/showthread.php?t=1975560 pre-rooted doesn't trip the counter,,,

deeznutz1977 said:
Next time odin this http://forum.xda-developers.com/showthread.php?t=1975560 pre-rooted doesn't trip the counter,,,
Click to expand...
Click to collapse
Ok so here's my next question.
In order to root again do i use the toolkit again or simply just download the pre-rooted rom and flash it with Odin? Which one would be better just
to get root again? Thanks!

vseslija said:
Ok so here's my next question.
In order to root again do i use the toolkit again or simply just download the pre-rooted rom and flash it with Odin? Which one would be better just
to get root again? Thanks!
Click to expand...
Click to collapse
Download the rom from the link i posted..flash in Odin Thats it pre rooted

deeznutz1977 said:
Download the rom from the link i posted..flash in Odin Thats it pre rooted
Click to expand...
Click to collapse
When I did this approach, I did it in two steps. I downloaded factory image of the firmware and flashed the device by using Odin 3.0.7.
Next, I used a tool package called "Galaxy Note2 ToolKit." Follow the instructions for how to root.
When I did the procedure, the software also had an option to include clockworkmod recovery
and busybox.
Gideon.

[Q] Failed Root Attempt. HELP!!!

Hi Guys,
So I have a Samsung Galaxy Note 2 that as of 5 hours ago was completely stock and running android 4.3 (the official one from AT&T). I got bored last night and decided I wanted to root my phone (something I hadn't yet done in the entire year I had my phone). So I looked up how to root, read the instructions all the way (I thought my research was complete). I rooted using the CF auto method. After doing that I flashed TWRP using ODIN. I also downloaded Titanium Backup, Rom Manager & My Backup Root. I tried to use all three of these applications to make a backup of my device so that I could flash the custom Rom I wanted without losing all my information. That is when my troubles began.
Whenever I tried to access any of these apps I got a pop up saying Unfortunately, SuperSU has stopped and a notification stating An attempt to access a secure area on your phone without authorization has been blocked. None of the apps would run either and just kept freezing or loading forever.Thinking I'd done something wrong I repeated the root process all over again. I still kept getting the same notifications though. I typed in the unauthorized access notification message into google and discovered about Knox. Doing some tinkering of my own I went to settings (more tab)>>security>>device administrators>> unchecked knox>>deactivate. After deactivating Knox I once again tried to gain root access and had no success. I followed the advice from previous threads and tried to change all Knox.apk files to knox.apk.bak using Explorer, I downloaded Android terminal and tried to delete knox via the command line su pm... That also did nothing. I went to the market and tried to download the SuperSU app by CHAINFIRE, it wouldn't work as it already says the app is installed but offers me no updating options. I also downloaded the Update SuperSU zip file and tried to flash it. My phone wont boot into recovery though so that hasn't gotten me anywhere. Downloaded Rom Manager and GooManager to try to get into recovery mode and still no success. later flashed philz_touch via ODIN as people who had similar problems had posted about it working for them. Didn't work for me. Flashed TWRP again using ODIN and am now just scratching my head trying to figure out how to fix this issue.
I'm personally not worried much about the warranty stuff but am more concerned with the fact that I can't root my phone. All I want is to be able to load a custom rom (MIUI v5) onto my phone. Any and all help would be greatly appreciated.... If you've seen someone else with an issue like mine please just redirect me to the proper thread then.
p.s. I also tried running the root verify app and it got stuck on a loading page.
When I power my phone off and boot into recovery mode (or whatever its called) my stats read as:
ODIN MODE
Product name: SGH-I317
Custom Binary Download: Yes (7 counts) - this is from all my attempts to reroot and flash different recoveries
Current Binary: Custom
System Status: Custom
Knox Warranty Void: 1
AP SWAEV: A2

Not sure if it matters but my phone still works fine and I can make and recieve calls, texts, etc so it doesn't seem like anything is "broken." Just no root access on a rooted phone.

Originally Posted by Ladyfinesse08
Thanks so much for your help. I tried doing what you said. When I go to SuperSU application under application manager it won't allow me to reomove it. All I can do is Turn it OFF. When If I go to the play market after turning it off the only option I get is to enable it again. Looking under App Info though it's showing that I'm on version 1.93 of SuperSu. I think from all the stuff I've been reading I'm supposed to be on version 1.95.
As for flashing it your TWRP I can't because I can't load into recovery mode with TWRP. The only thing thats working for me is ODIN. Not sure if there's a way to flash from ODIN or not but I personally don't know of one (I'm new to ODIN).
http://goo.im/devs/OpenRecovery/t0lt...lteatt.img.tar
Here's a copy to flash in ODIN. If you can't boot into recovery after this, there are other things we can try from ODIN.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

dicksteele said:
Originally Posted by Ladyfinesse08
Thanks so much for your help. I tried doing what you said. When I go to SuperSU application under application manager it won't allow me to reomove it. All I can do is Turn it OFF. When If I go to the play market after turning it off the only option I get is to enable it again. Looking under App Info though it's showing that I'm on version 1.93 of SuperSu. I think from all the stuff I've been reading I'm supposed to be on version 1.95.
As for flashing it your TWRP I can't because I can't load into recovery mode with TWRP. The only thing thats working for me is ODIN. Not sure if there's a way to flash from ODIN or not but I personally don't know of one (I'm new to ODIN).
http://goo.im/devs/OpenRecovery/t0lt...lteatt.img.tar
Here's a copy to flash in ODIN. If you can't boot into recovery after this, there are other things we can try from ODIN.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Fixed it. I was being special :angel:

Ladyfinesse08 said:
it's saying the file you've requested is not found. Do you have another link for the file or whats the name of it so I can search for it myself?
Click to expand...
Click to collapse
http://teamw.in/project/twrp2/124
Should be main TWRP ATT page
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 08:59 PM ---------- Previous post was at 08:47 PM ----------
Ladyfinesse08 said:
Fixed it. I was being special :angel:
Click to expand...
Click to collapse
fixed the link or completely whooped root's butt?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

dicksteele said:
http://teamw.in/project/twrp2/124
Should be main TWRP ATT page
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 08:59 PM ---------- Previous post was at 08:47 PM ----------
fixed the link or completely whooped root's butt?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the link. the tar file is the same one that I've been using though so not sure if it'll work or not. When flashing it should I still be under PDA or should I switch to phone, csc, etc?

Ladyfinesse08 said:
the link. the tar file is the same one that I've been using though so not sure if it'll work or not. When flashing it should I still be under PDA or should I switch to phone, csc, etc?
Click to expand...
Click to collapse
Yep PDA.
Which version of ODIN you using?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

v.3.07

Ladyfinesse08 said:
v.3.07
Click to expand...
Click to collapse
K. Should work.
2.6.3.0 will also.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 09:19 PM ---------- Previous post was at 09:16 PM ----------
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt
Philz ClockWorkMod recovery
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

I flashed the first recovery file but it still won't boot into recovery for me. When I try to boot into recovery it keeps taking me to the default recovery screen. Tried launching titantium backup and what not again and they're all still not working for me.
Got the philztouch one to flash. Still won't boot into custom recovery though.

Ladyfinesse08 said:
I flashed the first recovery file but it still won't boot into recovery for me. When I try to boot into recovery it keeps taking me to the default recovery screen. Tried launching titantium backup and what not again and they're all still not working for me.
Got the philztouch one to flash. Still won't boot into custom recovery though.
Click to expand...
Click to collapse
K. Try this. 69% sure it will work.
- Download from http://d-h.st/CDK
I317UCUBMK6-TZ-PARAM.zip
- Extract the .zip file to get to I317UCUBMK6-TZ-PARAM.tar.md5
- Put your Note 2 in Download Mode.
Entering download mode is very simple. First you will need to turn off your device. Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device.
Open ODIN and place the I317UCUBMK6-TZ.tar.md5 file in PDA and flash.
I know you know how to do all that's written there, I just copied and pasted from a post.

dicksteele said:
K. Try this. 69% sure it will work.
- Download from http://d-h.st/CDK
I317UCUBMK6-TZ-PARAM.zip
- Extract the .zip file to get to I317UCUBMK6-TZ-PARAM.tar.md5
- Put your Note 2 in Download Mode.
Entering download mode is very simple. First you will need to turn off your device. Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device.
Open ODIN and place the I317UCUBMK6-TZ.tar.md5 file in PDA and flash.
I know you know how to do all that's written there, I just copied and pasted from a post.
Click to expand...
Click to collapse
This didn't work for me either. Not sure exactly what's wrong with my note but I may just have to give up on gaining root access. maybe i'll try a different method to root.... I'm 100% sure I'm rooted though based on what the phone says when I boot into the default system recovery. Just don't understand why I can't gain root access and boot into custom recovery. Thank you for all your help though you've been an absolute doll. :angel:

Ladyfinesse08 said:
This didn't work for me either. Not sure exactly what's wrong with my note but I may just have to give up on gaining root access. maybe i'll try a different method to root.... I'm 100% sure I'm rooted though based on what the phone says when I boot into the default system recovery. Just don't understand why I can't gain root access and boot into custom recovery. Thank you for all your help though you've been an absolute doll. :angel:
Click to expand...
Click to collapse
No worries. I aim to please.
You aren't the first this has happened to. Just trying to remember what I did. I know what I did to fix it, I think it's this version though.
Download and try this one
http://d-h.st/OYC
It's the MK4 version of the earlier param/tz you tried.
That should have worked, clueless why it didn't.
...
ODIN this one, let it reboot back into ROM.
Power down, go into download mode and flash either one of the custom recoveries.
Let it reboot, power down, then try and go into recovery.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

dicksteele said:
No worries. I aim to please.
You aren't the first this has happened to. Just trying to remember what I did. I know what I did to fix it, I think it's this version though.
Download and try this one
http://d-h.st/OYC
It's the MK4 version of the earlier param/tz you tried.
That should have worked, clueless why it didn't.
...
ODIN this one, let it reboot back into ROM.
Power down, go into download mode and flash either one of the custom recoveries.
Let it reboot, power down, then try and go into recovery.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It seems my life has become a horrible case of Murphy's Law (as far as rooting this dang phone goes). So I used the 4.3param_tz.tar file that you posted previously. After being flashed via ODIN my phone automatically booted into Philz Touch recovery more. I initially decided that I was going to flash the SuperSU update then but decided to wait as I wanted to follow the instructions completely and flash TWRP instead. rebooted the phone. Turned it off again and booted back into recovery..... I was once again met with the default stock recovery (I thought my problems were solved and was already half way through writing a post to you confessing my love).
At this point I proceeded with some caution and tried to flash TWRP. Didn't work. ODIN/my phone kept getting stuck in recovery.img. Disconnected the phone after a couple minutes, pulled the battery and rebooted into stock recovery mode. Once again ODIN/my phone got stuck on recovery mode. Tried flashing 4.3param_tz.tar again and this time got stuck at param.bin.
Did some Google searching and people recommended re-installing the drivers, re-installed device drivers and rebooted into stock recovery mode. Went back to ODIN and flashed TWRP. It flashed completely and automatically rebooted the device. When I turned the device off again and tried to go to recovery mode I was again taken to the stock recovery mode page. tried to reflash 4.3param_tz.tar and it got stuck on param.bin again. Since then I've unplugged and rebooted into recovery mode countless times and tried flashing any and every thing and I keep getting stuck at either param.bin or recovery.img.
I have to go to class now so I'll probably come back sometime tonight and try to re-install the drivers and see if I can get param to flash again. If you give up completely I understand. The longer this takes the more convinced I am that it's a sign from above that I simply need to get my ass a new phone.

Ladyfinesse08 said:
It seems my life has become a horrible case of Murphy's Law (as far as rooting this dang phone goes). So I used the 4.3param_tz.tar file that you posted previously. After being flashed via ODIN my phone automatically booted into Philz Touch recovery more. I initially decided that I was going to flash the SuperSU update then but decided to wait as I wanted to follow the instructions completely and flash TWRP instead. rebooted the phone. Turned it off again and booted back into recovery..... I was once again met with the default stock recovery (I thought my problems were solved and was already half way through writing a post to you confessing my love).
At this point I proceeded with some caution and tried to flash TWRP. Didn't work. ODIN/my phone kept getting stuck in recovery.img. Disconnected the phone after a couple minutes, pulled the battery and rebooted into stock recovery mode. Once again ODIN/my phone got stuck on recovery mode. Tried flashing 4.3param_tz.tar again and this time got stuck at param.bin.
Did some Google searching and people recommended re-installing the drivers, re-installed device drivers and rebooted into stock recovery mode. Went back to ODIN and flashed TWRP. It flashed completely and automatically rebooted the device. When I turned the device off again and tried to go to recovery mode I was again taken to the stock recovery mode page. tried to reflash 4.3param_tz.tar and it got stuck on param.bin again. Since then I've unplugged and rebooted into recovery mode countless times and tried flashing any and every thing and I keep getting stuck at either param.bin or recovery.img.
I have to go to class now so I'll probably come back sometime tonight and try to re-install the drivers and see if I can get param to flash again. If you give up completely I understand. The longer this takes the more convinced I am that it's a sign from above that I simply need to get my ass a new phone.
Click to expand...
Click to collapse
Hmmm. Maybe it's my fault.
That's my last name for reals.
So the param/tz you flashed I previously posted, was the first one or second one?
Try flashing the first param.bin/tz.img combo.
Sorry for the run around.
My fault again. When i posted the Philz recovery I should have mentioned either one would have been fine.
For the custom recovery, it gets down to personal preference. Both versions are working fine. They both are touch. You are just going to have to play with both and see which one trips your trigger.
I'm getting lost where we are at.
Try flashing the original param file from the 4.3 OTA. Let's see if that completes successfully. Then we'll go from there.
I'm thinking
-Fix booting into stock recovery.
-Do chainfires CF-AUTOROOT in ODIN.
-Boot phone and try updating Supersu again
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

I'm in the same boat this person is in, and i was about to open a new thread. I hope you don't mine joining in for help. My husband was a ninny and accepted the full OTA when I only told him to swap over his cards into the new warranty exchange we just got in. So I didn't know about it until I started trying to root and running into problems. I ran the TZ.tar.md5 file in Odin. I tried this little method here mentioned here: http://forum.xda-developers.com/showthread.php?p=50532028. I can't get anything to happen other than watching the flash counter go up. I just want root so i can restore his app with Rom Toolbox from his other phone...... This Knox thing is BS......

whitetiger_0603 said:
I'm in the same boat this person is in, and i was about to open a new thread. I hope you don't mine joining in for help. My husband was a ninny and accepted the full OTA when I only told him to swap over his cards into the new warranty exchange we just got in. So I didn't know about it until I started trying to root and running into problems. I ran the TZ.tar.md5 file in Odin. I tried this little method here mentioned here: http://forum.xda-developers.com/showthread.php?p=50532028. I can't get anything to happen other than watching the flash counter go up. I just want root so i can restore his app with Rom Toolbox from his other phone...... This Knox thing is BS......
Click to expand...
Click to collapse
A ninny. Something my wife has never called me I'll have to admit. Don't think she's ever considered that, I'll have to confirm that.
Back to work.... what does can't get anything else to work mean?
So what have you did? Any of the steps listed above?
We haven't heard from LadyF so assuming she's good to go. No reason to open another can't root thread.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

dicksteele said:
A ninny. Something my wife has never called me I'll have to admit. Don't think she's ever considered that, I'll have to confirm that.
Back to work.... what does can't get anything else to work mean?
So what have you did? Any of the steps listed above?
We haven't heard from LadyF so assuming she's good to go. No reason to open another can't root thread.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for getting back to me. I tried the CF Auto Root file in Odin. I tried just flashing a custom recovery so I could flash SU to gain root. Those are the 2 main things I remember trying..the rest is a late night blur. I was going to just try and flash one of the rooted stock roms, however, and this is kinda' sad, I don't remember which spot to place it in Odin.

whitetiger_0603 said:
Thanks for getting back to me. I tried the CF Auto Root file in Odin. I tried just flashing a custom recovery so I could flash SU to gain root. Those are the 2 main things I remember trying..the rest is a late night blur. I was going to just try and flash one of the rooted stock roms, however, and this is kinda' sad, I don't remember which spot to place it in Odin.
Click to expand...
Click to collapse
Just PM'd you all the goodies.

dicksteele said:
Just PM'd you all the goodies.
Click to expand...
Click to collapse
I appreciate your time helping me. Things are up and running.

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