Root p600 boot loop thanks to recklessness

[mcspoon]

Hongkong-bought sm-p600 is stuck booting as far as the samsung boot screen, then infinite rebooting upon failure to access recovery.

Pure recklessness on my part. Having flashed stock recovery after rooting (via odin), and finding stock wouldn't help me install gapps, and then flashing twrp the same way, I then couldn't get the thing into recovery. Being an idiot I thought it was because of the game of twister you have to play with the hardware buttons, and tried to reboot into recovery through goomanager (the app wasn't able to install a recovery image, I gather because of server issues or something). So Presumably a piece of script is just running, failing, and rebooting it.
Good news is it can connect to odin, so presumably (ran battery down, didn't help so waiting for it to charge) adb connects too. Will check that.
However, I'm not too savvy with adb but I was hoping there is a command which might kill the script, maybe by uninstalling goomanager or whatever. But I certainly don't want to guess at what such a command might be.
Alternatively/also, I have downloaded a uk version of stock firmware (i'm from the uk and i understand the firmware should fit the same exynos cpu architecture) from sammobile.com which may/may not fix the problem if I flash it (?) The 'clean rom' also looks good...
So advice/ good links would all be appreciated. Didn't really even want to root the thing but it was the only way I could see to get gapps on it *sigh*

 

[Rukbat]

Good news is it can connect to odin, so presumably (ran battery down, didn't help so waiting for it to charge) adb connects too.

If you left USB debugging enabled.

However, I'm not too savvy with adb but I was hoping there is a command which might kill the script, maybe by uninstalling goomanager or whatever. But I certainly don't want to guess at what such a command might be.

You could run a terminal, ps to find the script's process, then kill it. (If you kill the wrong process and screw things up, just turn it off, turn it on and try again. Killing is like forced stop - it doesn't do permanent damage.)

 

[mcspoon]

update: took a while to come back to this. adb devices returns nothing, so... try to reflash twrp (i realise it's been updated recently) on odin?

though i have read about this and rooted/flashed a couple of phones before now, if anyone is willing to help on this the more precise any instructions are the better, i won't take it as condescension

Edit: Just went and flashed new recovery, fixed. Welcome to close the thread

 

[colchiro]

Glad you got it figured out.

 

[Deleted User]

update: took a while to come back to this. adb devices returns nothing, so... try to reflash twrp (i realise it's been updated recently) on odin?

though i have read about this and rooted/flashed a couple of phones before now, if anyone is willing to help on this the more precise any instructions are the better, i won't take it as condescension

Edit: Just went and flashed new recovery, fixed. Welcome to close the thread

I am having same problem, i got stuck with bootloop right now,
may i ask you which recovery file you used? thanks