I have tried CM 10.2.0 and Calkulin's Nexus 4 v1.5 on my Nexus 4. I tried with both CWM 6.0.4.6 and TWRP 2.6. CWM wouldn't install the Calkulin ROM at all (Status 7 error), but TWRP would. However, when booting Calkulin's ROM for the first time it would hang at "Starting Apps"
CM 11.2 failed to flash through TWRP. CM 10.2.0 flashed successfully, but then would hang during bootup with the arrow circle loading screen.
I eventually had to go back to CWM and restore a backup (THANK GOODNESS FOR BACK UPS! )
Can anyone offer any clues to what might be going on?
Thanks.
Download GooManager and MAKE SURE you have the LATEST TWRP which supports SELinux
Sent from my Nexus 4 using XDA Premium 4 mobile app
Related
Device Model: Google Nexus 7 16GB
ROM: PARANOIDANDROID 2.99 PIE3.1 (4.2.1)
Recovery: Clockworkmod Touch Recovery 6.0.1.9
I installed this ROM at the root of my SD card and wiped the dalvic cache. When I try to boot it, I'm stuck at the "X" boot screen. I've already reflashed my device 3 times and this bug is still there. I was just curious if anyone has seen this issue and if there were any workarounds?
I'm able to flash my device back to Stock but I really want to get this ROM working so a little help would be appreciated!!
wesc16 said:
Device Model: Google Nexus 7 16GB
ROM: PARANOIDANDROID 2.99 PIE3.1 (4.2.1)
Recovery: Clockworkmod Touch Recovery 6.0.1.9
I installed this ROM at the root of my SD card and wiped the dalvic cache. When I try to boot it, I'm stuck at the "X" boot screen. I've already reflashed my device 3 times and this bug is still there. I was just curious if anyone has seen this issue and if there were any workarounds?
I'm able to flash my device back to Stock but I really want to get this ROM working so a little help would be appreciated!!
Click to expand...
Click to collapse
First of all, that's not a brick. Not at all. You need to read the installation instructions, which would have told you that wiping data is a must.
Re: [Q] PARANOIDANDROID 2.99 - Bricked Device
You don't need a workaround. About a million purple have installed PA. What ROM did you try and flash over and are you sure you had the right file for your android version?
Sent from my N7 using XDA Premium
Dirty AOKP 3.2 & m-kernel+ a33
Re: [Q] PARANOIDANDROID 2.99 - Bricked Device
Not a brick. If you can flash something else it's not a brick.
Sent from my Galaxy Nexus using xda app-developers app
Before I flashed anything, I was using Stock 4.2.1 but once I started flashing ROMs, I've been stuck at a boot loop even though I've wiped the data and dalvik cache. I seriously can't figure out what's going on.
ROMS flashed: CM10, LiquidSmooth, ParanoidAndroid, MIUI, SmoothROM
Recovery Tools: CWM 6.0.1.9, TWRP 2.3.2.1 (I have tried both recovery tools for each ROM when performing installation)
Each time I've been stuck at the boot, I had to reflash the Stock Image to recover. After I flash the stock image, I would try to flash another ROM. It's not like I have any data on here either so wiping the data isn't really helping as suggested...
The steps that I've followed:
1. Unlock bootloader
2. Root Device
3. Flash ROM using either CWM or TWRP.
4. Wipe Data + Dalvik Cache
5. Reboot System.
Is there something wrong with the steps I'm using? I've been using the Nexus 7 Toolkit 4.0.0 to make things quicker but it seems like I should just use the adb shell and manually trace it step by step.
Nevermind, I figured it out. I did a factory reset before the flash and then wiped all the other stuff in order for my Nexus 7 to boot properly. Thanks for the feedback!
Hey, hope everyone is having a good long weekend. I have a Bell S4 that refuses to boot any 4.3 ROM. I have tried at least 6. I made sure they were all jfltecan (jfltexx ROMs also work), wiped everything, flashed the ROM, flashed 4.3 gapps, wiped cache and dalvik and rebooted. It shows the Galaxy S4 screen then just goes black. Anyone else experiencing this?
What recovery are you using. There are new versions to flash 4.3
I'm using PhilZ Touch 5 because TWRP takes anywhere from 1-3 minutes to pass the TWRP opening screen.
Use TWRP 2.5.02
Sent from my SGH-I337 using XDA Premium 4 mobile app
TWRP won't even go passed the Teamwin screen anymore. It will sit there till I turn it off.
I was having the same issue earlier. Just installed Philz recovery because TWRP 2.6 was taking so long to come on or flash anything. Received the same black screen after flashing multiple roms. I had an old TWRP 2.5 flashable zip file and flashed it from Philz, pulled battery, rebooted to TWRP again, flashed 10.2 nightly and Gapps and it worked.
If you are still having the same problem, let me know and I'll upload the file for you for the TWRP flashable zip.
Thanks & good luck!
I recently got a nexus 7 2012. I unlocked it and installed the custom recovery (CWM) according to the guides given in the forum and elsewhere. The problem comes when I install a custom ROM like CM10.2, It installs fine, but the boot does not resume after the CM animation. I tried another rom like AOKP and even TWRP as recovery, still the problem persists. My bootloader is 4.23 and flashing back to stock ROM works as normal. Please help.
What recovery you use. And what tool you use to root. For I use WUG toolkit. And install TWRP. And install CM 10.2 with no problem. Maybe you not really root. Update your superuser before that
Sent from my Nexus 7 using XDA Premium 4 mobile app
Stupid question: are you sure you are flashing grouper ROMs?
Tried a lot of combinations with ROMs and recoveries finally I solved it. CWM wasn't working with its wipe options and tried TWRP and gave the full wipe of all partitions before flashing CM and gapps and it worked!!!!
Hello!
So Ive followed the install process listed here using CWM: http://forum.xda-developers.com/showthread.php?t=2020336
When booting up I cant get any mobile network.
Any ideas on how to fix this? Ive redone the install about 5 times now.
Announcement from molesarecoming: Latest CWM recovery appears to cause baseband issues when flashing. Use version 6.0.3.6 or switch to TWRP
Sent from my Nexus 4 using Tapatalk
Welp...I was on the KVT49L CM Edition ROM (http://forum.xda-developers.com/showthread.php?t=2763102) and I was running OUDHS CWM recovery 1.0.3.4. Decided to try to get F2FS running, so I downloaded the custom TWRP that ktoonsez had made to enable F2FS and zip flashed from inside OUDHS 1.0.3.4, and then when I tried to install KVT49L, it gives me status 7. So, I decided to roll back and re-flash the OUDHS 1.0.3.4 .zip, which worked; but it now also now gives me Status 7, even for CM11. The only rom I can successfully install is http://www.slimroms.net/index.php/d.../10761-slim-jflte-4-4-2-build-5-official-4050
Any help would be appreciated as I am in the dark.
Status 7 basically means that cwm thinks you are flashing something not meant for your device. Try flashing after deleting the assert scripts in the Rom zip
Sent from my HTC One using Tapatalk