Flashing Rom, Problems after reboot


Recommended Posts

I have a Nexus 4 running stock JB 4.2 Rooted with CWM Touch and Matrix kernel.

I finally decided to flash Paranoid ROM on it and everytime it reboots the start up wizard crashes and gapps crashes. Only thing I can do is reboot the phone.

I followed the Paranoid Forum Topic steps to flash, i've flash many androids before, so this is a first for me.

But I know many people running paranoid on the internet without issues, and since I dont have more then 10 posts on xda (old account is lost in oblivion. Really old email) I cant post in the thread asking for help. I created one but no one has been able to help yet.

I was hoping someone here can help. I tried googling a general "flashed rom now crashes" etc search to see if I can fix this issue some how but nothing.

I hope you guys can help!

Link to comment
https://www.neowin.net/forum/topic/1130448-flashing-rom-problems-after-reboot/
Share on other sites

Did you clear cache and dalvik cache in CWM after flashing the ROM ?

Also check that there is not a newer version of Gapps available, some ROMs need updated versions

This. I've had a few crashes on first boot on of new ROMs because the cache and dalvik cache hadn't been cleared. Also, make sure you're using the correct version of gapps; there are two versions for Jelly Bean (one for 4.1.x, one for 4.2.x), make sure you have the one for 4.2.x (20121212). If that fails, try wiping and reflashing both the ROM and gapps.

This. I've had a few crashes on first boot on of new ROMs because the cache and dalvik cache hadn't been cleared. Also, make sure you're using the correct version of gapps; there are two versions for Jelly Bean (one for 4.1.x, one for 4.2.x), make sure you have the one for 4.2.x (20121212). If that fails, try wiping and reflashing both the ROM and gapps.

See thats what I was wondering. But in the forum thead, the gapps that goes along with the rom is "gapps-jb-20121011.zip"

Should I still try the latest one?

See thats what I was wondering. But in the forum thead, the gapps that goes along with the rom is "gapps-jb-20121011.zip"

Should I still try the latest one?

Since you're installing a 4.2-based ROM, you need to use the 20121212 version of gapps. The 20121011 version is only for 4.1. There were enough changes in the Android codebase between versions 4.1 and 4.2 that they needed to compile a new version of gapps to account for the difference.

Ok ill definitely try that tomorrow. Sadly I assumed so but thought following the thread would be good instead of my own gut instinct.

If one method doesn't work it won't do any damage trying the other, just means you might have to re-flash something

I had problems trying to install it on my Galaxy Note.

I had to install the 10.1 Kernel first then go to advanced, reboot recovery, then flash the paranoid rom and 4.2.1 gapps straight after without rebooting to stop it crashing and locking up.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Everyone else has said it. I'm gonna say it - you don't know what you're talking about. I do. I have two laptops. One work, one personal. I have access to two more laptops - both personal. At home I manually update my personal laptop when I see on Neowin that there is an update - I carry on and only apply the updates when I am ready. My work one only updates when my workplace decides to send it - I carry on and only apply the updates (when they actually arrive, which is usually days after the release) when I switch off the laptop at the end of the day as usual. The two other personal laptops only get updated when I get to it which is rarely - the people who own them carry on using them until I get to it and update them. All of the browsers on all laptops are configured to restore the tabs when launched. Google and Microsoft have changed from 6 weeks to 4, and it looks like it's going to move to 2. None of these changes affect how any of these browsers on the laptops are used. Not one jot. My advice to you is stop panicking whenever you see an update. Just carry on with what you're doing. This even benefits you in a way - from your comment you sound like you don't like the changes or the frivolous new features - great - then carry on as before!
    • AMAZON needs to take total accountability for this.
    • Server Summit had a heap of announcements, ADCS changes are baller.
    • Nice, hope they *finally* fixed the issue with the NTFS driver where the system would completely brick during large file copies using the built in driver. It's been broken for years requiring me to use the older, slower, NTFS-3G FUSE driver.
    • Windows 11 KB5094126 BSODing, freezing, forcing BitLocker lockout, breaks OneDrive, and more by Sayan Sen Microsoft released Windows 11 KB5094126 and KB5093998 last week as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. While Microsoft has so far not acknowledged any major problems with the release, some users online are running into problems. These range from OneDrive and Dropbox access issues, BitLocker recovery lockouts, to blue screens and BSODs. The most common one seems to be happening with HP systems wherein affected users say they hit 0xc0430001 BSOD (blue screen of death) error code after the KB5094126 update. We wonder if this could be related to the recent bug we covered on HP devices wherein the ongoing Secure Boot certificate updates are leading to similar issues. While we are not certain, users affected by this issue likely need to ensure that the boot.stl file is included on the installation media (such as a USB installer or ISO), if the above-mentioned dynamic updates are deployed. If this file is missing, computers may fail to boot from the installation media and could display the error 0xc0430001. This STL file is used by Secure Boot to verify that the boot files are trusted, so it must match the same Windows version and system architecture. To ensure the file is included, Microsoft recommends using the Update WinPE script, which automatically updates the image and handles the required files. Alternatively, you can manually copy the boot.stl file from the Windows\Boot\EFI folder on a Windows device and place it in the matching folder on your installation media before deploying the updated image. Aside from blue screening some users also note their systems have been freezing following the update. This could be happening to Lenovo PCs specifically. In the case of the OneDrive and Dropbox access issues, a user figured out that there could be a conflict with UAC. He explained: "Okay, so I did some digging, and in our environment KB5094126 breaks OneDrive and Dropbox in Explorer. I went through all our GPOs and found out that the combination of disabling UAC and having my user being a local admin breaks OneDrive in Explorer. ... If I enable UAC again, then it works, even with KB5094126 still installed." Hopefully, Microsoft will look into these issues. Source: Microsoft forum (link1, link2, link3, link4), Reddit (link1, link2, link3, link4)
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      80
  • Tell a friend

    Love Neowin? Tell a friend!