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

Root Nexus 4 Suicide

Banished Angel

Banished Angel

Android Enthusiast
I'm running the newest version of Paranoid Android (3/28 build) and the newest Franco kernel (r116). Earlier I was in the middle of a text message and my phone just shut off. I turn it back on and it sits at the PA loading screen for 10 minutes so I force another reboot and it gets past the PA screen and says optimizing apps. It optimizes the Google apps, 12 of them to be exact, and then says starting apps. Once again it gets stuck. I've restarted it a couple more times and it won't get past the starting apps page.

Any advice would be much appreciated. I have it plugged into the charger now as it is nearly dead at this point.
 
Banished Angel said:
I'm running the newest version of Paranoid Android (3/28 build) and the newest Franco kernel (r116). Earlier I was in the middle of a text message and my phone just shut off. I turn it back on and it sits at the PA loading screen for 10 minutes so I force another reboot and it gets past the PA screen and says optimizing apps. It optimizes the Google apps, 12 of them to be exact, and then says starting apps. Once again it gets stuck. I've restarted it a couple more times and it won't get past the starting apps page.

Any advice would be much appreciated. I have it plugged into the charger now as it is nearly dead at this point.
Click to expand...
First thing I would do is boot into recovery and wipe cache, dalvik cache and fix permissions. Then if it boots, reset your kernel settings to default of you've changed anything. Let us know if that helps any.
 
Okay I left it on the charger for an hour, booted into recovery, wiped cache/dalvik cache and fixed permissions, rebooted, and once again after 5 minutes of "starting apps" nothing has happened (although it upgraded 121 apps this time instead of 12).

Round 2. Booted into recovery, wiped cache/dalvik cache, flashed the PA ROM zip and the PA gapps, and rebooted (I didn't even flash Franco's kernel this time). I got past the PA loading screen and my phone has been "starting apps" for the last 10 minutes. Still going as I write this.

Any more ideas?

EDIT: Still says: "Android is upgrading... Starting apps" after 25 minutes. Finally killed the phone as I highly doubt it needs more time.
 
Banished Angel said:
Okay I left it on the charger for an hour, booted into recovery, wiped cache/dalvik cache and fixed permissions, rebooted, and once again after 5 minutes of "starting apps" nothing has happened (although it upgraded 121 apps this time instead of 12).

Round 2. Booted into recovery, wiped cache/dalvik cache, flashed the PA ROM zip and the PA gapps, and rebooted (I didn't even flash Franco's kernel this time). I got past the PA loading screen and my phone has been "starting apps" for the last 10 minutes. Still going as I write this.

Any more ideas?
Click to expand...
Well, if you have a nandroid that is recent enough that you wouldn't lose much data going back to it, I would do a full wipe: system, factory reset, cache and dalvik cache in recovery. Then fresh flash ROM and GApps. See what happens.

Now this is just speculation but you may have some data corruption going on. Before you fresh flash, you may want to boot into recovery and do an adb pull command to get all data copied yo your computer.

In terminal, CD to your platform-tools folder. This is where your adb and fastboot utilities live. Then, while the phone is connected and in recovery, type sudo adb pull /sdcard/0/ /your directory of choice to copy these files/

Now if you want to ensure that you have no data corruption, type sudo adb reboot bootloader

Now you should be in the bootloader with a Big Android laying on his back and your device info in the bottom left corner. Now lock and unlock the bootloader to wipe the sdcard. Type sudo fastboot oem lock
Now type sudo fastboot oem unlock

Volume up once and power button to unlock the bootloader. Now we need to reflash your recovery. Make sure you have a recovery image downloaded (I really recommend using TWRP; find it on goo.im) and in your platform-tools folder. For ease, name it recovery.img Use this command: sudo fastboot flash recovery /recovery.img

Now you can volume up a couple times and you should see recovery in red at the top right. Hit the power button to boot into recovery. Now in recovery, copy back ROM, GApps and a su.zip file. Make sure you have each file in your platform-tools folder, so you may need to copy those over from where you saved the contents of your sdcard earlier.

Use these commands:

sudo adb push /su.zip /sdcard/0/Download
sudo adb push /name of ROM file.zip /sdcard/0/Download
sudo adb push /name of GApps file.zip /sdcard/0/Download

Now flash the su file first. Now do a full wipe. Now flash ROM, then GApps.

If this doesn't work, I'd be amazed. I've had to do this before so I know it will work. Let me know if you run into any problems or have questions.

jmar
 
I got into the sdk-tools directory where fastboot and adb are located through the command prompt no problem. Whenever I try to use an adb command it says:

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
 
Banished Angel said:
I got into the sdk-tools directory where fastboot and adb are located through the command prompt no problem. Whenever I try to use an adb command it says:

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...

Hmm. Your fastboot and adb tools should be in platform-tools. Mac, Linux or Windows BTW?

I have a feeling that USB debugging is not on.
 
Banished Angel said:
Windows, and they're definitely in a folder named sdk-tools.
Click to expand...
Okay, it would seem then that USB Debugging is not enabled. Do you have a nandroid backup that you can flash which had USB Debugging enabled? If so, we may not need to be able to boot it as long as USB Debugging was enabled in that nandroid.

Gonna call in some reinforcements to lend some more expertise.

I'm thinking of a couple other scenarios we may be able to try if the above is not available/doesn't work.

Gonna log on to AF from my PC as well.
 
I have CWM as my recovery at the moment. If I go into backup & restore and then restore I have a file from February 12th. I still want to copy my phone's contents to my computer before I nuke it. What are my options?
 
Banished Angel said:
I have CWM as my recovery at the moment. If I go into backup & restore and then restore I have a file from February 12th. I still want to copy my phone's contents to my computer before I nuke it. What are my options?
Click to expand...
I think you should definitely restore that backup, because we can't run the adb pull command from within recovery unless we are working with a ROM install that has USB Debugging on. When you flashed over the install that wouldn't boot, it is likely that the install came by default with USB Debugging off.

Flash the nandroid, then reboot your recovery session. Then cd to your sdk-tools and type sudo adb devices to see if your device is recognized. Then we'll go from there.
 
I flashed the 2/12 backup and rebooted recovery.

I don't believe sudo is necessary on Windows in the Command Prompt as I get:

'sudo' is not recognized as an internal or external command, operable program or batch file.

When I type just adb devices it says:

List of devices attached

But nothing else. Apparently it's still not recognized
 
Banished Angel said:
Not sure what you mean.
Click to expand...
While the phone is in recovery type: adb devices

You should get an output that shows your serial number followed by the word device.

EDIT: Boot into recovery.

Select flash zip. Don't flash anything, as this will mount your device. Now type: adb devices. This should do the trick.

Thanks IBT!
 
jmartino5920 said:
While the phone is in recovery type: adb devices

You should get an output that shows your serial number followed by the word device.
Click to expand...

While the phone is in recovery I typed: adb devices

Command prompt then says:

List of devices attached



There is no more output. No serial number. No device. It is not recognized by adb.
 
jmartino5920 said:
See edit of my last post above please.
Click to expand...

I selected flash zip and still no output, however CWM has an option to mount.. I can mount:

/system
/data
/cache
/sdcard

Currently data and cache are mounted, but system and sdcard are not. Should I mount both system and sdcard and try again?
 
Banished Angel said:
I selected flash zip and still no output, however CWM has an option to mount.. I can mount:

/system
/data
/cache
/sdcard

Currently data and cache are mounted, but system and sdcard are not. Should I mount both system and sdcard and try again?
Click to expand...

try going into recovery, then choose options to install zip from sdcard, then choose zip from sd card...then don't choose anything. That should mount internal storage. see if adb devices works then
 
jmartino5920 said:
try going into recovery, then choose options to install zip from sdcard, then choose zip from sd card...then don't choose anything. That should mount internal storage. see if adb devices works then
Click to expand...

I chose install zip from sdcard and then choose zip from sdcard. I typed adb devices again and still no output.
 
iowabowtech said:
Dang, I thought that might work. Didn't know you had a working option to mount /sdcard via cwm however. Try that and then adb devices. Don't mount system for now.
Click to expand...

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.

EDIT: Still no output from adb devices
 
You must log in or register to reply here.
Back
Top Bottom