Root Regardless Flash = Boot Loop

tom_allyn · Sep 20, 2013

I used root tool kit to unlock my bootloader and root my Nexus 7 Gen 1. Since then using TWRP I've attempted to Flash Franco Kernal and also Paranoidandroid, before each flashing I deleted dalvik cache and cache partition. 4 different times this has resulted in getting stuck in a boot loop and having to use TWRP to restore a nandroid backup.

What in *%^$ could be the problem? How do I fix this issue so that I can flash ROMs and/or Kernals?

saltire · Sep 21, 2013

If you want to flash a new ROM you need to do a full wipe in TWRP, that's the "Wipe" option in latest version. This will do a factory reset.

As you have done, do a full nandroid backup in TWRP and recommend you back up your user apps using Titanium Backup - get the pro version as you can do a batch restore, worth it if you have a lot of apps.

If you want to flash a different kernel, do it after you have flashed a ROM. I tend to flash a ROM then reboot to make sure it works, then take another nandroid in TWRP before flashing kernel. If you do that way then wipe cache and dalvick only before kernel flash.

tom_allyn · Sep 21, 2013

saltire said:
If you want to flash a new ROM you need to do a full wipe in TWRP, that's the "Wipe" option in latest version. This will do a factory reset.

As you have done, do a full nandroid backup in TWRP and recommend you back up your user apps using Titanium Backup - get the pro version as you can do a batch restore, worth it if you have a lot of apps.

If you want to flash a different kernel, do it after you have flashed a ROM. I tend to flash a ROM then reboot to make sure it works, then take another nandroid in TWRP before flashing kernel. If you do that way then wipe cache and dalvick only before kernel flash.

I chose backup when I flashed the ROM and GAPPS I also chose the backup option. So after doing a full wipe can I simply use the backup to flash both again?

WoohooGuy · Sep 21, 2013

I assume it's Wug's Nexus Root Toolkit you are using, it has a built in feature to checksum the factory images and recoveries it installs.

As you are using outside images, have you personally checksum the images against the provided values from the devs? Checksumming them will tell you if they are identical to what the developer released in case they were corrupted via download or storage.

WinMD5 is a easy to use tool for windows to verify the file checksum - WinMD5 Free - Windows MD5 Utility Freeware

WoohooGuy · Sep 21, 2013

I forget to mention the cable, responding to another post here reminded me.

The N7 can be very fickle with what USB cable you use, try swapping out the cable and make sure what you use has a tight fitting connection. Dont plug the device into a USB hub.

When possible you should always use the Asus factory cable or another high quality one if it's damaged.

tom_allyn · Sep 21, 2013

I've tried this several more times today, I'm stuck inside to rain, so nothing beter to do. With the same result I've even tried the stable CM Rom.

One thing I forgot to mention. I'm starting this process using Goomanager (GM) In trying to figure this out I've read a lot of stuff and several things have led me to believe that I'm using a bad version of GAPPS. The GAPPS that GM is giving me is a file gapps-jb-20121011-signed.zip which is supposed to be the latest GAPPS. That is regardless whether I've tried to flash Paranoidandroid or CM.

One of the videos I watched today instructed in GM find the correct GAPPS to use the search function upon doing so that particular GAPPS file didn't come up, but several others did. Two of them looked like they are specific to Paranoidandroid, but nothing from appearances looked specific to CM.

Is my issue with the GAPPS files? How do I fix it?

For Paranoidandroid should I use one of the GAPPS files that appears to be specific to that ROM such as pa_gapps-full-4.3-20130917-signed.zip?

WoohooGuy · Sep 21, 2013

If you dont know what may be causing the issue than it's probably best to "save n pave".

Make sure your important data is backed up and using a toolkit like Wug's or similar, or ADB if you have the skills than trigger a factory reset and then flash the tablet back to full locked n stock.

Once you start over fresh keep a log of exactly what changes you make and follow a simple protocol of not updating or installing apps until you have the tablet running the fresh installs of your desired kernel and rom.

Have you tried a new or different cable?

Root Regardless Flash = Boot Loop

tom_allyn

Member

saltire

Android Expert

tom_allyn

Member

WoohooGuy

Android Enthusiast

WoohooGuy

Android Enthusiast

tom_allyn

Member

WoohooGuy

Android Enthusiast

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads