1. Download our Official Android App: Forums for Android!

Root p600 boot loop thanks to recklessness

Discussion in 'Android Devices' started by mcspoon, Dec 26, 2013.

  1. mcspoon

    mcspoon Lurker
    Thread Starter
    Rank:
    None
    Points:
    5
    Posts:
    2
    Joined:
    Nov 1, 2013

    Nov 1, 2013
    2
    0
    5
    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*
     

    Advertisement

  2. Rukbat

    Rukbat Extreme Android User
    Rank:
    None
    Points:
    943
    Posts:
    10,391
    Joined:
    Jan 16, 2012

    Jan 16, 2012
    10,391
    2,897
    943
    Male
    Being retired and writing Tasker tasks.
    Fayetteville, NC, USA
    If you left USB debugging enabled.

    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.)
     
  3. mcspoon

    mcspoon Lurker
    Thread Starter
    Rank:
    None
    Points:
    5
    Posts:
    2
    Joined:
    Nov 1, 2013

    Nov 1, 2013
    2
    0
    5
    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
     
  4. colchiro

    colchiro Extreme Android User
    Rank:
    None
    Points:
    323
    Posts:
    8,886
    Joined:
    Jun 4, 2010

    Jun 4, 2010
    8,886
    1,784
    323
    Male
    Web developer/IT
    Glad you got it figured out. :D
     
  5. zzjunhozz

    zzjunhozz Newbie
    Rank:
    None
    Points:
    26
    Posts:
    17
    Joined:
    Jul 14, 2015

    Jul 14, 2015
    17
    6
    26
    Male
    I am having same problem, i got stuck with bootloop right now,
    may i ask you which recovery file you used? thanks
     

Share This Page

Loading...