Develop Bugs

Stuck on black "Google" with open lock screen

I tried using the franco kernel app to install the kernel on my rooted Galaxy Nexus. There was the "download the .zip" option and the "we'll flash it for you" option. Of course I took the easy option which was probably stupid on my part. My phone downloaded the kernel and then rebooted. Now that it has rebooted... it wont get beyond the black screen that says "Google" and has the little open lock image at the bottom.
Questions:
Has anyone seen this?
Did I brick this thing (I really hope not)?
What steps can I do to try to get it back working?
Or does it just take a long time 20+ minutes to download/install/whatever once it reboots?

patriot95 said:
I tried using the franco kernel app to install the kernel on my rooted Galaxy Nexus. There was the "download the .zip" option and the "we'll flash it for you" option. Of course I took the easy option which was probably stupid on my part. My phone downloaded the kernel and then rebooted. Now that it has rebooted... it wont get beyond the black screen that says "Google" and has the little open lock image at the bottom.
Questions:
Has anyone seen this?
Did I brick this thing (I really hope not)?
What steps can I do to try to get it back working?
Or does it just take a long time 20+ minutes to download/install/whatever once it reboots?
Click to expand...
Click to collapse
i think that flash a new rom would solve this

patriot95 said:
I tried using the franco kernel app to install the kernel on my rooted Galaxy Nexus. There was the "download the .zip" option and the "we'll flash it for you" option. Of course I took the easy option which was probably stupid on my part. My phone downloaded the kernel and then rebooted. Now that it has rebooted... it wont get beyond the black screen that says "Google" and has the little open lock image at the bottom.
Questions:
Has anyone seen this?
Did I brick this thing (I really hope not)?
What steps can I do to try to get it back working?
Or does it just take a long time 20+ minutes to download/install/whatever once it reboots?
Click to expand...
Click to collapse
I did this last night to see, and it didn't work. I had to pull the battery, and reboot. I then just downloaded the new zip, and rebooted into Recovery to flash it as I normally would.

I wanted to do this... but with my root toolkit it looks like my phone doesn't have usb debugging on (which it was before I tried to flash this kernel). And I can't turn my phone on to turn it on... so hmm.

RMarkwald said:
I did this last night to see, and it didn't work. I had to pull the battery, and reboot. I then just downloaded the new zip, and rebooted into Recovery to flash it as I normally would.
Click to expand...
Click to collapse
This is what I want to do. Is I pull the battery and restart... I'm still stuck at the same screen though.

patriot95 said:
This is what I want to do. Is I pull the battery and restart... I'm still stuck at the same screen though.
Click to expand...
Click to collapse
Pull the battery, hold Vol Up/Vol Down/Power to get into Recovery. Do you have the ROM zip file or another kernel on your SD card? You could just re-flash the ROM zip file over your existing installation, which would leave your data alone and install the ROM's kernel. Wipe /cache and Dalvik Cache before flashing.
EDIT: When you get into the bootloader, hit Vol Up until Recovery shows up, then hit the Power button to boot to Recovery.

RMarkwald said:
Pull the battery, hold Vol Up/Vol Down/Power to get into Recovery. Do you have the ROM zip file or another kernel on your SD card? You could just re-flash the ROM zip file over your existing installation, which would leave your data alone and install the ROM's kernel. Wipe /cache and Dalvik Cache before flashing.
EDIT: When you get into the bootloader, hit Vol Up until Recovery shows up, then hit the Power button to boot to Recovery.
Click to expand...
Click to collapse
This is KIND of what I'm doing. I can't access my phone from the computer because of the damn usb thing... but I'm going to try to flash back to stock and see if that works.

It's booting now and it's been on the start screen for a minute or two. How long should it take on a stock flash? Just curious how long to wait before yanking the battery and trying again.

How did you flash stock, using fastboot or a zip? These are the stock images correct?

I boot into Recovery Mode and did the factory reset.
I also have a su.zip on my sdcard that I think is the rooted image that was used when I used the WugFresh root toolkit. But I'm not sure.
Shouldn't the Factory Reset... do a Factory Reset?
Edit: I see it's just data not an actual factory reset as I am thinking.

patriot95 said:
I boot into Recovery Mode and did the factory reset.
I also have a su.zip on my sdcard that I think is the rooted image that was used when I used the WugFresh root toolkit. But I'm not sure.
Shouldn't the Factory Reset... do a Factory Reset?
Edit: I see it's just data not an actual factory reset as I am thinking.
Click to expand...
Click to collapse
If you don't have a ROM or kernel zip file on your SD card, you'll want to put one there. Factory Reset already reset any data you have, so you'll want to flashing a ROM would be recommended here.
You can use ADB to push files to your SD card. You'll need to get into Recovery, mount /data (which is under Mounts and Storage menu), then open a command prompt window and change directories to your Android SDK folder, specifically Platform-tools. Then use ADB to push the zip files to your SD card:
adb push <name of file>.zip /data/media
EDIT 2: You'll want to download and put the zip file in your SDK - Platform-tools folder before you use ADB to push it there.
You can then flash the ROM via Install file from SD card.
Does this make sense?
EDIT: The su.zip is just to get root access, not a full ROM zip.

RMarkwald said:
If you don't have a ROM or kernel zip file on your SD card, you'll want to put one there. Factory Reset already reset any data you have, so you'll want to flashing a ROM would be recommended here.
You can use ADB to push files to your SD card. You'll need to get into Recovery, mount /data (which is under Mounts and Storage menu), then open a command prompt window and change directories to your Android SDK folder, specifically Platform-tools. Then use ADB to push the zip files to your SD card:
adb push <name of file>.zip /data/media
You can then flash the ROM via Install file from SD card.
Does this make sense?
EDIT: The su.zip is just to get root access, not a full ROM zip.
Click to expand...
Click to collapse
It makes sense... but I'm a little new so I will try this. Might take me a while.
By the way... these captcha images suck.

Thank you for the help... I am re-rooting my phone now. I was able to get back to stock.

Good job, glad to help!

RMarkwald said:
Pull the battery, hold Vol Up/Vol Down/Power to get into Recovery.
EDIT: When you get into the bootloader, hit Vol Up until Recovery shows up, then hit the Power button to boot to Recovery.
Click to expand...
Click to collapse
I LOVE YOU!
(I did the same thing with the auto-flash kernel and was stuck. I totally forgot that you had to hold BOTH up/down with the power button.)
Franco's app SUCKS!
Thanks my man!!! :good:
BTW...Jelly Bean rocks!

Hello guys i have tha same problem with patriot95 (black screen Google and one small lock lower) ... my device is optimus 3d p920 and i cant reboot it .
can you help me ? PLz

This is a problem with the toolkit...
Do you have any adb and fastboot downloaded? No? Download it. There's more than enough instructions on that.
You didn't need to factory reset AT ALL. All you needed to do was just re-flash your ROM and you would've been good to go.
Next time learn how to use adb and fastboot command please. Then, there will be less chance of messing it up and not being able to fixing it.

Hi, sorry this thread is kinda old already but I don't really want to start new thread about same problem. So, similar to OP, I stupidly use the 'autoflash' option from franco app, and I'm stuck now. But I can still have access to CWM recovery. I was using the stock 4.2.2 takju before. I already tried to re-flash stock kernel -> fail. Tried re-flash stock rom - fail. Tried wipe cache and dalvik then flash deodexed 4.2.2 -> also fail. Please help me, I really need to use my phone right now.

Are you flashing a 4.2.2 kernel with a 4.2.2 ROM?
What ROM and kernel?
Sent from my Galaxy Nexus using xda premium

I flashed the stock 4.2.2 rom from the google website but it doesn't work. Then I tried the stock 4.2.2 from this link,
http://forum.xda-developers.com/showthread.php?t=1737849 but also failed.
I also flashed the stock kernel from this link
http://forum.xda-developers.com/showthread.php?t=2151154

[Q] Came across problem upon flashing AOKP

I unlocked and rooted my GSM Galaxy Nexus using the pocketnow.com guide and flashed ClockworkMod, made a Nandroid and then tried to flash AOKP maguro build 28. As soon as I try to flash the ROM, it boots me into recovery mode and then immediately Andy pops up, laying on his back with an exclamation mark in a red triangle on his chest.
I was scared I bricked my phone, so I pressed the three buttons all at once and I got to system recovery. I had the option to either wipe the phone or to reboot.
How do I fix this? I don't want Andy on his back, I want him on his feet feeding me with messages of how he is installing the ROM.
Thanks bunches in advance.
cws

search around, if u don't remove the file inside /system named recovery-from-boot.p, everytime u reboot ur phone it reflash the stock recovery overriding ur cwm recovery...remove the file (backup it somewhere on ur sdcard/pc), and flash the recovery again..this time it should stick and u can flash roms

I found the file in the cwm backup folder, thats hardly it. But I wouldn't know where else to look for it. Where should the system folder be?

clockworkstop said:
I found the file in the cwm backup folder, thats hardly it. But I wouldn't know where else to look for it. Where should the system folder be?
Click to expand...
Click to collapse
u have to brwose ur phone with root explorer (or some other file browser with root capabilities), mount the /system folder as R/W and delete/move the file recovery-from-boot.p

Done. Still the same problem.

clockworkstop said:
Done. Still the same problem.
Click to expand...
Click to collapse
di u reflashed the cwm recovery after removing/move that file?

Yes, in fact I did.

Maybe I'm missing the fastboot file?
Sent from my Galaxy Nexus using xda

NEED HELP cant access CW Recovery

I just rooted my phone everything seemed to go the way its supposed to. I have superuser and have downloaded titanium backup and it works fine. I wanted to back up my phone so I can have a stock back up but when I went into fast boot and tries to access clockwork I got the android on his back with the red exclamation mark. I'm not sure what happened. I was able to access it once. Maybe a reboot did something. I'm not new to rooting but I'm new to the galaxy line. Thanks so much for any help its appreciated geeatley.
I rooted using the dev kit v7.0 I'd that helps any.

cyaiphone said:
I just rooted my phone everything seemed to go the way its supposed to. I have superuser and have downloaded titanium backup and it works fine. I wanted to back up my phone so I can have a stock back up but when I went into fast boot and tries to access clockwork I got the android on his back with the red exclamation mark. I'm not sure what happened. I was able to access it once. Maybe a reboot did something. I'm not new to rooting but I'm new to the galaxy line. Thanks so much for any help its appreciated geeatley.
I rooted using the dev kit v7.0 I'd that helps any.
Click to expand...
Click to collapse
Nexus line.
have you tried reflashing cwm recovery via fastboot?

flash CWM via fastboot.
and why do you need a backup of stock? You can always re-flash the stock images to go back to completely stock. Restoring a rooted nandroid backup won't put you back to stock anyways...

OK makes sense. Is there a how to and link to the cwm download? On HTC you used to just download the file rename it pc86img and reboot into fast boot and let it update. Is it the same for the nexus?

cyaiphone said:
OK makes sense. Is there a how to and link to the cwm download? On HTC you used to just download the file rename it pc86img and reboot into fast boot and let it update. Is it the same for the nexus?
Click to expand...
Click to collapse
Similar, except you put it in a folder on your PC and flash it over USB with the command line.

martonikaj said:
Similar, except you put it in a folder on your PC and flash it over USB with the command line.
Click to expand...
Click to collapse
Crap is there a how to any how to do this? I've never used adb or command prompts.

cyaiphone said:
Crap is there a how to anywherebonnhow to do this? I've never used adb or command prompts.
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/showthread.php?t=1529058
And look for the "Setting up ADB for our device:" then "Obtaining Root Access and Custom Recovery:".

Can you boot into the OS? If you can, download Rom Manager from the Play Store and use that to install CWM Recovery.

Did you delete recovery-from-boot.p from /system? I had to do this to "permanently" install the recovery. My first Samsung phone, my first Nexus device, so not sure if this has been a regular thing ... never had to "permanently" install a recovery up until then. That fixed my issue as my recovery was only sticking once per boot ... was blowing my mind for a couple hours.
Not sure if root via toolkit solves this, but I did a manny root and had to do this. Hope it helps.
edit-
- remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
- rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak
(note: you could delete it, but renaming is much safer since its easily reversible)
Click to expand...
Click to collapse
Could also, apparently, rename it. I just reinstalled recovery, deleted, and haven't had a single problem since.

What bleedblue said; now go into fastboot, and reflash cwm.
Sent from my i9250

cant go into recovery mode with custom rom

i ve recently rooted my phone, it was on 4.0.2; everything works perfectly fine.
i just wanted to try jelly bean and when i tried to install it, after selecting whether to erase cache and backing up, phone rebooted and when it opened up i got this screen with a droid laying down on the ground with an exclamation mark on it.
whenever i try to restore my phone with clockwork or galaxy nexus root toolkit, i get stuck on that screen.
if i plug the battery out and start my phone, it openes up without any problems.
what did i do wrong?

kallshak said:
i ve recently rooted my phone, it was on 4.0.2; everything works perfectly fine.
i just wanted to try jelly bean and when i tried to install it, after selecting whether to erase cache and backing up, phone rebooted and when it opened up i got this screen with a droid laying down on the ground with an exclamation mark on it.
whenever i try to restore my phone with clockwork or galaxy nexus root toolkit, i get stuck on that screen.
if i plug the battery out and start my phone, it openes up without any problems.
what did i do wrong?
Click to expand...
Click to collapse
similar problem even i had but in my case when the screen with android excamn mark use to come it had some thing to do with enable/ disable when i press power button it use to show to cwm screen and last two line says recovery mode disabled etc and if i wait it says its enables after it says enables button use to work just try that not very sure in your case myte work

actually i couldn't fully understand what you meant

no one knows anything about this problem?

Using Root explorer, go into system/ and after you do Mount R/W, rename the file recover-from-boot.p to recover-from-boot.p.bak or delete it.
Then go into Rom Manager and Flash CMR and reboot into recovery.
From then on, you will never see that red triangle again when you boot into recovery, neither do you have to flash CMR everytime you have to boot into recovery.
Hope this helped.

rename (or delete) this file: /system/etc/install-recovery.sh.
This will prevent the ROM from overwriting CWM with the stock recovery. If you want to have the stock recovery so that future updates will install automatically, leave the ROM as is.

brealorg said:
rename (or delete) this file: /system/etc/install-recovery.sh.
This will prevent the ROM from overwriting CWM with the stock recovery. If you want to have the stock recovery so that future updates will install automatically, leave the ROM as is.
Click to expand...
Click to collapse
so if i rename or delete this file, in future i cant get stock updates then?

kallshak said:
so if i rename or delete this file, in future i cant get stock updates then?
Click to expand...
Click to collapse
considering you're wanting to overwrite the stock recovery with CWM, you wouldnt anyways.

another question, is this action reversible?
i mean, if i ever want to bring my phone back to unrooted and stock state?
i ve tried to look it up with search but couldnt find the answer

you didnt search very hard then.
http://forum.xda-developers.com/showthread.php?t=1626895

might've missed some key words on search. thx for your help

[Q] Restore TWRP nandroid from PC

I'm a newbie and I am in trouble. I have a rooted Nexus 7 2013 and I have a TWRP Nandroid backup which I had copied to my WIndows PC.
Now my Nexus 7 crashed and won't go beyond the X on bootup. The Nandroid and Titanium backups are on my windows PC.
How do I restore the Nexus 7 to working status by restoring from the Nandroid backup and data I have copied to the PC?
Please help. Thanks.

Guys, someone please help.
I don't know how to get out of this mess. I'm still stuck on X.
I can power off the Nexus 7 and power to the recovery screen where I find Teamwin's menu.
I restored (several times) the nandroid backups I found on this menu (they were all done after the last reset) but rebooting then just gets me back to the X screen and no further.
I have a good nandroid backup on my PC but no way to get it into the tablet so TWRP can restore from it. Is there a way to transfer a file to or from the tablet when it will not boot completely?
The advanced screen of the Teamwin recovery menu lets me access a file manager. Is there any way I can use it to move files on or off the tablet to "anything" else?
The last time the boot froze on the X screen, I was able to go to the recovery screen with the android on his back and an X and from there to a reset. But this time I cannot get there and the recovery screen gets me to the Teamwin recovery menu. This has a wipe option. Will this reset the Nexus if selected. Will it remove root? I don't want to go through rooting it all over again.
Essentially I just want to do 2 things:
a) extract data from the stuck Nexus 7
b) reset and restore the nandroid backup I have on my pc.
Please help.......

Bill235 said:
Guys, someone please help.
I don't know how to get out of this mess. I'm still stuck on X.
I can power off the Nexus 7 and power to the recovery screen where I find Teamwin's menu.
I restored (several times) the nandroid backups I found on this menu (they were all done after the last reset) but rebooting then just gets me back to the X screen and no further.
I have a good nandroid backup on my PC but no way to get it into the tablet so TWRP can restore from it. Is there a way to transfer a file to or from the tablet when it will not boot completely?
The advanced screen of the Teamwin recovery menu lets me access a file manager. Is there any way I can use it to move files on or off the tablet to "anything" else?
The last time the boot froze on the X screen, I was able to go to the recovery screen with the android on his back and an X and from there to a reset. But this time I cannot get there and the recovery screen gets me to the Teamwin recovery menu. This has a wipe option. Will this reset the Nexus if selected. Will it remove root? I don't want to go through rooting it all over again.
Essentially I just want to do 2 things:
a) extract data from the stuck Nexus 7
b) reset and restore the nandroid backup I have on my pc.
Please help.......
Click to expand...
Click to collapse
Just choose the wipe option in twrp.
That should allow you to start android.
Then copy your backup from PC to virtual sdcard, reboot to twrp, and restore.
You can copy files while in recovery but it is more involved so I would try this first.

sfhub said:
Just choose the wipe option in twrp.
That should allow you to start android.
Then copy your backup from PC to virtual sdcard, reboot to twrp, and restore.
You can copy files while in recovery but it is more involved so I would try this first.
Click to expand...
Click to collapse
But will it remove the root I worked so hard to get?

If you worked hard to get root on a Nexus device you did something wrong. It should be as simple as unlocking the bootloader (already done), flashing a custom recovery (already done), and flashing the SuperSU ZIP file (this is the only step you'd need to repeat).
That said, doing a factory reset should not remove root. Even if it does, it would be restored when you restored your rooted Nandroid.

raptir said:
If you worked hard to get root on a Nexus device you did something wrong. It should be as simple as unlocking the bootloader (already done), flashing a custom recovery (already done), and flashing the SuperSU ZIP file (this is the only step you'd need to repeat).
That said, doing a factory reset should not remove root. Even if it does, it would be restored when you restored your rooted Nandroid.
Click to expand...
Click to collapse
Easy for an expert. I'm a newbie. I used the WUGfresh toolkit and it took multiple frustratng attempts and forever for it to finally download the correct adb drivers that would recognize the Nexus 7. Then all went smoothly.
But back to the present. I'm all fine now (till the next time the Nexus 7 crashes on me). For other newbies like me who run into this problem and need simple instructions here is what I did.
The first time this crash with the boot stuck on the X screen happened, going to the recovery screen (Power button + Volume up simultaneously) showed me the android on his back with a red triangle. Pressing power button and briefly volume up gave me the option to reset the tablet without removing root. Because I was traveling and did not have my TWRP backups with me (they were on my laptop 1,000 miles away) this removed all my data and I had to re-install all my apps and everything again.
The second time this happened, the recovery screen took me to the TWRP recovery screen. TWRP recovery had apparently survived the crash. I needed to save my data before reseting the tablet again. By trial and error I discovered that the TWRP menu has under the Advanced Tab a file manager. also discovered that if you connect a flash device to the tablet's usb port the TWRP file manager could read and write to it (!!!) in a folder called usb-otg (but not to my windows laptop). I copied what I wanted to save to the flash drive. Then I used the "wipe" tool to return the tablet to android.
I installed a free app, Recovery Manager, to reinstall TWRP recovery. Copied my previous TWRP nandroid backup to the tablet and restored everything as it was.
Easy as pie if you know how. I hope this helps some other befuddled user.
sfhub and raptir: Do you know what can be done to prevent this from happening again? Could Google Play being conected to in Europe after it was used to being to conected to in the US cause the problem? Both times the crashes happened shortly after I used the tablet in Europe and the the second time after I used it for the first time in the US.

Bill235 said:
sfhub and raptir: Do you know what can be done to prevent this from happening again? Could Google Play being conected to in Europe after it was used to being to conected to in the US cause the problem? Both times the crashes happened shortly after I used the tablet in Europe and the the second time after I used it for the first time in the US.
Click to expand...
Click to collapse
I can't say for sure what is happening in your case, but in my experience getting stuck on X means your user data got corrupted. The cases I've seen fall into 2 categories:
1) faulty EMMC flash memory. Sometimes if you wipe a couple of times the bad blocks get locked out and you don't see the problem anymore. Other times, they keep coming back. In the latter case, return/exchange/rma the unit
2) android crashes (random reboot) and unfinished writes are not completed corrupting the user data. They put in code in the latest ROM to mitigate this so if you think you are suffering from this type of corruption, install the latest ROM if you haven't done so already.

Thank you for the excellent and clear reply. I'll hope the 2 wipes I did may have gotten rid of my bad blocks.
I'll update to the latest stock rom too.
Thank you.

Bill235 said:
Thank you for the excellent and clear reply. I'll hope the 2 wipes I did may have gotten rid of my bad blocks.
I'll update to the latest stock rom too.
Thank you.
Click to expand...
Click to collapse
The updating part got me in trouble.......
I accepted the system update and am now running android 4.3 but lost root.
So I went back to the WUGfresh Nexus Root kit. Updated everything, am now on version 1.7.3 of the toolkit, followed all the instructions (uninstalled and re-installed driveers) and got stuck on the same problem I had the first time I tried rooting: the adb : step3 of the full driver test. adb device not found .
I did reboot twice, am using the oem asus cable, etc. What a pain!!
Unfortunately I am dependant on the toolkit because I do not know enough to root manually.
Suggestions? Thanks.

Bill235 said:
The updating part got me in trouble.......
I accepted the system update and am now running android 4.3 but lost root.
So I went back to the WUGfresh Nexus Root kit. Updated everything, am now on version 1.7.3 of the toolkit, followed all the instructions (uninstalled and re-installed driveers) and got stuck on the same problem I had the first time I tried rooting: the adb : step3 of the full driver test. adb device not found .
I did reboot twice, am using the oem asus cable, etc. What a pain!!
Unfortunately I am dependant on the toolkit because I do not know enough to root manually.
Suggestions? Thanks.
Click to expand...
Click to collapse
So you're stock 4.3 now? Rooting manually isn't hard bud, setting up the toolkit is harder IMO.
You just need to download and install the Android SDK. Then download a custom recovery .img file, and a SuperSU flashable zip. Put the SuperSu flashable zip on your /sdcard. You'll then boot into the bootloader, open a command prompt and change directories to your Android SDK (Ex. mine is at C:\sdk\platform-tools) and run the command: fastboot flash <name of recovery file>.img
Then reboot into recovery, flash the SuperSU zip, reboot, done. You're rooted. There are plenty of How To's stickied in the General Forums for the N7 here.

RMarkwald said:
So you're stock 4.3 now? Rooting manually isn't hard bud, setting up the toolkit is harder IMO.
You just need to download and install the Android SDK. Then download a custom recovery .img file, and a SuperSU flashable zip. Put the SuperSu flashable zip on your /sdcard. You'll then boot into the bootloader, open a command prompt and change directories to your Android SDK (Ex. mine is at C:\sdk\platform-tools) and run the command: fastboot flash <name of recovery file>.img
Then reboot into recovery, flash the SuperSU zip, reboot, done. You're rooted. There are plenty of How To's stickied in the General Forums for the N7 here.
Click to expand...
Click to collapse
Will look into your suggestions later because I am rooted again. It was the adb drivers again. The universal ones just would not work for me. The Samsung signed drivers on the other hand worked smoothly and then the toolkit ran smoothly and I am rooted. But it wiped out my TWRP recovery so I will re-install that next.
Thanks for the help.
About your advice, than you. But as a newbie I need clearer instructions. "download and install the Android SDK". Where? to the pc or the tablet? etc.
I need to learn more so I don't keep getting into these ridiculous binds!

Bill235 said:
Will look into your suggestions later because I am rooted again. It was the adb drivers again. The universal ones just would not work for me. The Samsung signed drivers on the other hand worked smoothly and then the toolkit ran smoothly and I am rooted. But it wiped out my TWRP recovery so I will re-install that next.
Thanks for the help.
About your advice, than you. But as a newbie I need clearer instructions. "download and install the Android SDK". Where? to the pc or the tablet? etc.
I need to learn more so I don't keep getting into these ridiculous binds!
Click to expand...
Click to collapse
Review the General forum for the N7 2013 here, as there are threads stickied to the top of that forum which has write-ups and video how to's that'll explain it all. I suggest to review those FIRST before you try doing things just so you can get a picture of what's going on. It may seem like a lot, but once you do it, it really is not.
The Android SDK is installed on your computer.