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

Root Nexus 4 Suicide

The option to mount sdcard is there, but unfortunately it does not appear to be working. I select it and it still reads mount sdcard.

That's what I was afraid of. Exit out of this cmd session altogther. Then reboot recovery. Open a new cmd prompt and then retry the options in recovery to install zip from sdcard, choose zip from sdcard. Try actually navigating to /sdcard/0 this time, then stop without selecting anything.

Now again, try adb devices command from the new cmd prompt.
 
That's what I was afraid of. Exit out of this cmd session altogther. Then reboot recovery. Open a new cmd prompt and then retry the options in recovery to install zip from sdcard, choose zip from sdcard. Try actually navigating to /sdcard/0 this time, then stop without selecting anything.

Now again, try adb devices command from the new cmd prompt.

Still no output.
 
The rom you just reverted back to, is it a 4.2 rom? If it is, you will definitely need to update your adb files, if the files are from a pre 4.2 release.
 
The rom you just reverted back to, is it a 4.2 rom? If it is, you will definitely need to update your adb files, if the files are from a pre 4.2 release.

And have you ever had adb working on this machine with this phone? drivers are the other possible hangup.
 
Where could I find updated adb files. I'm confident my files are ancient.

Android SDK | Android Developers

jc63MYs.png


Under SDK Tools Only download the RECOMMENDED .exe files.
 
Downloading wugs root toolkit is the most foolproof option. It downloads the latest adb and can do an sd card pull and get all your info off. It will also help you install the proper drivers if that is the hang up.

Nexus Root Toolkit v1.6.3 | WugFresh

Banished...I would download this utility to ensure everything is properly installed even though I linked you to the Android Developers website, this utility will automate a lot if not all we are attempting manually.
 
I booted into the bootloader, but it wouldn't let me boot TWRP.

Now before I download the new sdk-tools should I delete my old sdk-tools folder?
There is no reason to download the whole sdk again, it's only 4 files that need to be updated. We have the mini adb around here somewhere if you aren't going to use wugs toolkit.

Here's the mini adb, all the latest files you need
http://androidforums.com/5389081-post2.html
 
Banished...I would download this utility to ensure everything is properly installed even though I linked you to the Android Developers website, this utility will automate a lot if not all we are attempting manually.

There is no reason to download the whole sdk again, it's only 4 files that need to be updated. We have the mini adb around here somewhere if you aren't going to use wugs toolkit.

I downloaded the sdk-tools and then it told me to download the JDK.. I'm going to just scrap this installation and use the kit. Will report back!
 
Hmm.. The toolkit wants to know what version of android I am running. Since I restored a backup from February i'm not entirely sure anymore..

My options are:

Custom ROM
4.2.0
4.2.1
4.2.2
Any build

Should I just go with any build?
 
Hmm.. The toolkit wants to know what version of android I am running. Since I restored a backup from February i'm not entirely sure anymore..

My options are:

Custom ROM
4.2.0
4.2.1
4.2.2
Any build

Should I just go with any build?

Was the restore of a custom rom or of a stock build of android?

based on what it is you choose custom rom or any build.
 
Was the restore of a custom rom or of a stock build of android?

based on what it is you choose custom rom or any build.

I honestly don't know what build of Android I was running a month and a half ago when i made the backup. I don't even remember making the backup.
 
I honestly don't know what build of Android I was running a month and a half ago when i made the backup. I don't even remember making the backup.
I don't know what to tell you. I would say any build would be the safest bet. Is it likely that it was a backup you made after rooting your phone for the first time?
 
I don't know what to tell you. I would say any build would be the safest bet. Is it likely that it was a backup you made after rooting your phone for the first time?

I rooted the phone/unlocked the bootloader the day I got the phone back in November. I ended up just going with any build and I downloaded the latest TWRP recovery. What should I do with the toolkit now that it's set up?
 
I rooted the phone/unlocked the bootloader the day I got the phone back in November. I ended up just going with any build and I downloaded the latest TWRP recovery. What should I do with the toolkit now that it's set up?
EDIT: Do what sdrawkcab25 said in the post above. Then...

I would Backup your sdcard to your PC. Then I would lock then unlock the bootloader. Then I would have it install a fresh 4.2.2. Then root that. then have it flash TWRP recovery permanently. once you've done all that, boot her up into recovery and put some of the files you want back on the phone. It is my understanding that this tool can help with adb pushes. You could then flash a rom and gapps if you want, or you could see if everything is all bueno. Then boot into your fresh install. First thing after going through setup that I would do is ensure you have USB Debugging enabled
 
Under "advanced utilities" Click the radio button, that says the phone is in "fastboot-bootloader" mode. And obviously boot the phone into the bootloader. click the "list devices" command...

If that is succesful, (from the same screen) you can do a pull command to retrieve everything off the sd card.

Then go back to the main screen, and you'll see the "back to stock" option, check the radio button that says it is soft bricked, and let it run.
 
Back
Top Bottom