• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Black sceen after powering up.

H

hilts

Newbie
I have an unlocked and Rooted Nexus. My PC would not recognise my Nexus after I updated it to 4.2.2 so i thought I'd flash it back to Jellybean using Rom Manager. Now when I power the Nexus up it loads the Google screen but then goes black, it is still powered up as you can see a faint illumination. I can access TWRP but i wiped the Nexus and have no backup to restore "Doh" Is the any way to restore another Rom while the Nexus is in this state ?

Thanks in advance.
 
El Presidente said:
Does the PC register the Nexus when you're in the bootloader?
Click to expand...

The Nexus shows up in Devices and Printers under unspecified when in TWRP but not in my computer. I tried the soft bricked option on Nexus root toolkit but it's saying that the drivers are not installed.
 
Ok, you'll probably be able to sort yourself out then. :)

First up, try the driver install procedure in the Root Toolkit. I'm not sure which version you're using, but Wugs details what you need to do. It's a little involved, but it does work: http://www.wugfresh.com/nrt/

If that works, you should be able to use the toolkit to reflash one of the stock binaries either manually or using the toolkit.

If that fails, we can try pushing a ROM zip to your tablet via ADB.
 
Have tried the driver install but still says that they aren't installed. Will give it another go and let you know how I get on.
Thanks .
 
Struggling here. I have tried again and again to update the drivers following the Nexus root toolkit but it still says no ADB device found. I don't know if the USB debugging is on as I can't turn on the device. It shows up in devices as nexus 7 but not in Explorer.
Help please before it end up in small pieces lol.
 
Can you use/are you familiar with ADB?

If you reboot to recovery, connect to your PC, then head to Advanced -> ADB Sideload, can you get ADB to talk to it with the adb devices command?
 
El Presidente said:
Can you use/are you familiar with ADB?

If you reboot to recovery, connect to your PC, then head to Advanced -> ADB Sideload, can you get ADB to talk to it with the adb devices command?
Click to expand...

OK i have done as above then swiped to sideload but it just sits there.
Not to sure if this is what you meant.
 
ADB is a program you can use to talk to your device with your PC. You can also use it to send files to your tab/phone which is what we'll try to do with yours.

Download it from here: http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/#post-5389081

Boot in to TWRP, head to the ADB Sideload option again and connect to your PC. Once connected, open up the ADB program and type "adb devices" (minus the quotations) and see if your tab is recognised.

If yes, we're cooking on gas. :)
 
El Presidente said:
ADB is a program you can use to talk to your device with your PC. You can also use it to send files to your tab/phone which is what we'll try to do with yours.

Download it from here: http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/#post-5389081

Boot in to TWRP, head to the ADB Sideload option again and connect to your PC. Once connected, open up the ADB program and type "adb devices" (minus the quotations) and see if your tab is recognised.

If yes, we're cooking on gas. :)
Click to expand...

Right then. I take it you mean the Mini SDK ? I have downloaded that and unzipped that to C:\sdk-tools but when it try and open the ADB application it opens then closes down.

Sorry about being a bit thick here lol.
 
Ha, no, you're not being thick - I am (and I imagine that will instil you with a tonne of confidence!).

Once unzipped, hit open a command prompt (Start -> cmd), then navigate to the sdk-tools folder using the command prompt. Once opened, type cd\ (press enter) then type cd\sdk-tools.

Once you've done that, boot the tab to recovery, advanced -> ADB sideload -> connect to PC, then typw adb devices and see if it will connect.
 
I opened the ADB folder and Shift right clicked to open command window here and did what you said but came up with this -
List of devices attached
015d24a8174c1813 recovery

are we on the right track ?
 
Any rom really. I'm want to get the Nexus 7 up and running properly so I can sell it to help fund a Nexus 9.
 
Cool, I forgot to ask, do you have the 3G or the WiFi version?

For the WiFi version, try this: http://forum.xda-developers.com/nexus-7/orig-development/official-cyanogenmod-12-0-t2996413

For the 3G version, try this: http://forum.xda-developers.com/nexus-7/3g-development/rom-unofficial-cm12-0-tilapia-t2974800

(They're both Cyanogen, not the best ROMs out there, but they'll at least get you back up and running).

Download the zip file, place it in the sdk-tools folder, navigate to the folder via command prompt, reboot the tab to recovery, advanced, adb sideload, connect to PC then enter the following command -

adb push <name of file here.zip> /data/media/0/ (that's a zero and when you type the command, omit the <>. That should push the zip file to the tablet ready for you to flash.
 
This is becoming a pain in the ass :mad: when I type adb devives I get this
adb server is out of date. killing...
ADB server didn't ACK
* failed to start deamon *
error:

Only doing what I did yesterday !!!!
 
So found that the HTC sync that I had installed for my phone was causing conflict , so uninstalled that and now typing adb devices always finds the Nexus Just having a problem now with command prompt reading the zip file , it says error or no file . Will re download it and have another go.
Getting there slowly lol.
Thanks for you patience .
 
No bother! If there's one thing I've learned in messing about phones/tabs etc, is that things rarely work properly first time.

Try renaming the zip file, see if that works? Also remember that ADB is for all intents and purposes a Linux command shell so it will be case sensitive. If the filename as an uppercase letter in it, your command will need to have an uppercase letter in it too.
 
Ye Ha.... We have success . Managed to salvage my Nexus and now by sideloading the new rom and Gapps is fully working.
Thanks very much for your help. Its easy when you know how lol.
Now I'm back to the original problem that my Nexus doesn't show up in File Explorer. Any ideas or have you had enough now lol.
 
Yep, I'm done :p.

Which version of Windows are you using and have you tried another USB port/cable?

You could also try the driver install again?

Alternatively, if you're just looking to transfer stuff off the tab, look at something like Airdroid which can do it via Wifi. Is that an option?
 
@hilts maybe a bit late, but I had same problem. Drivers can be so picky, but it really annoyed me that it wouldn't work so I spent time trying stuff. For me turned out I had to uninstall all S3 drivers and N7 drivers, reboot then installed N7 drivers again first, then the S3 drivers second. If you can be bothered you'll probably have to do the same - substituting S3 for your other device drivers.
 
You must log in or register to reply here.
Back
Top Bottom