1. Are you ready for the Galaxy S20? Here is everything we know so far!

Not sure if I should be worried

Discussion in 'Android Devices' started by ahdrom, Aug 8, 2012.

  1. ahdrom

    ahdrom Newbie
    Thread Starter

    Hi all!
    I recently picked up a Nexus 7 and been lurking here ever since. Before this post, I've been hanging out in the EVO 4g section.

    Anyway, not long after I brought home my new "shiny" (N7), I decided to dive in and unlock and root it. After spending an hour trying to get Wug's toolkit to work right on one PC, I switched to another and everything went smoothly. My N7 is unlocked, rooted and I installed TWRP recovery. Or so I thought. I mainly did this so I could use Stickmount. At this time, I don't see myself trying different ROMs but I wanted the recovery anyway, just in case I decided to go down that road later on.

    And that's the rub, my N7 IS unlocked and rooted but I don't have recovery. I'm sure I have it installed but I can't cold boot into recovery and Goo Manger (which I have installed) freezes as well :(. I have tried plugging it into a PC and tried both ways, no luck. I even plugged it into the PC I was successful with the unlock/root and got the same results.

    If I "install" TWRP through Goo (it takes a couple of attempts too), I can get into recovery but it doesn't stick. I've used ES File Explorer and looked for the "stock" recovery file to rename. Only to find it doesn't exist?!?

    So, I'm now wondering, am I in trouble? Is there a way I can get A recovery installed and have it stick? Any help would be greatly appreciated.

    I should point out, my N7 seems to work just fine (except for the "missing" recovery).
     



    1. Download the Forums for Android™ app!


      Download

       
  2. cammykool

    cammykool Android Expert

    Stock will automatically try to rewrite the stock recovery. And no one can seem to cold boot to recovery. Reflash twrp and flash the stock unsecured ro,m from xda
     
  3. Atma

    Atma Extreme Android User

    Look in your /system folder for a file named recovery-from-boot.p. It will cause your recovery to be overwritten. If it is there, rename it to something like recovery-from-boot.pbak of whatever.

    To boot to recovery, use the Quick Boot app.
     
    ahdrom likes this.
  4. idic

    idic Well-Known Member


    What do you mean no one can boot to recovery? Hold power, up & down at startup and recovery loads just fine for me...

    As to finding/renaming the file - have you tried doing it via adb? I'm not sure it will work while the device is powered up. It may do, I've jut always done it while in recovery immediately after it's installed for the first time before rebooting.
     
  5. ahdrom

    ahdrom Newbie
    Thread Starter

    Thanks. I tried that quick boot app and got nothing. It hung on the Google screen.
    Also, I have looked for that file, only to find nothing in the /system folder except for a bin folder, which is empty.

    Just for giggles, I held the vol up/down and power buttons and noticed the word fastboot is a red color. Question, is that normal?
     
  6. ahdrom

    ahdrom Newbie
    Thread Starter

    I used Wug's 1-click, could I still do what you suggest using the ADB method? Also, what do you guys think would happen if I ran the ADB method from the state my N7 is in now. I'm only asking as it seems like I don't have fastboot install, as I said in the post above, the word fastboot is red in color, which has me thinking something went wrong, ie, user input error *sigh*
     
  7. Atma

    Atma Extreme Android User


    I'm pretty sure Wug's Nexus Toolkit install Fastboot for you. If I remember right the fastboot screen you see, fastboot is in red letters. Have you tried using the Nexus Toolkit again to install a recovery? You can follow this guide. If you download these PDAnet drivers and install the one for your system, it will help using the toolkit.

    You could also use the toolkit and tell it to go back to stock and start over if you need to.
     
    ahdrom likes this.
  8. ahdrom

    ahdrom Newbie
    Thread Starter

    Thanks Atmazzz :)

    I wish I had seen that guide sooner. After reading through it, I realized it is very well written and very clear on what to do at each step.

    I restarted reading Wug's post over on xda, to see if anyone there is seeing what I'm seeing and also in the hope that I can fix this without having to go with the "nuclear" option. I have a couple trips coming up and really don't want to muck anything up prior to those trips. But this is something I want to have working, so I will continue to research this.
    I might even give that ROM Manager a try too :)
     
    Atma likes this.
Loading...
Similar Threads - sure should worried
  1. Jimmy Recard
    Replies:
    4
    Views:
    350
  2. rickjohnson78
    Replies:
    1
    Views:
    588
  3. kevinmac1
    Replies:
    22
    Views:
    2,688
  4. markdoc
    Replies:
    1
    Views:
    543
  5. Brïïzy
    Replies:
    12
    Views:
    856
  6. Oneechan69
    Replies:
    6
    Views:
    2,348
  7. Milo Williamson
    Replies:
    43
    Views:
    2,112
  8. BettySpaghettiAndReady
    Replies:
    4
    Views:
    1,316
  9. royh
    Replies:
    0
    Views:
    713
  10. Hank Harwell
    Replies:
    4
    Views:
    2,491

Share This Page

Loading...