Hi
Recently i decided to install Autodroid rom on my nexus 2012,no luck.Then i tried 2 of slimkat roms,Nothing worked.
It always keeps on booting the custom roms for infinite time(waited 20 minutes) and then reverted back to stock lollipop.
Here is what i did
I unlocked bootloader
rooted device
did factory reset from TWRP,
flashed rom zip
cleared dalvik cache.
reboot
Am i missing anything.Please help me .I am new to nexus 7 custom roms.
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!
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
ifonuser78 said:
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
Click to expand...
Click to collapse
This happens with many including me some time with many diffrnt files chainging and overwriting causes the same
Best option as u said above flash stock firmware
Then u can try what I feel will work better in ur case
Root the phone with CF root method
Flash Philz Recovery
wipe cache / dalvik / ix perm and reboot and go ahead with ur Rom flashing
Ok, flashed the stock ROM which was not rooted, then rooted using CF's method and flashed PhilZ. I couldn't find the option to fix permissions in PhilZ recovery, and went ahead with the installation of Omega 9 after wiping. I couldn't even get Omega to boot, previously it worked on the first boot and then no longer after a restart.
I don't know whats going on here.
I'm flashing the pre-rooted MGA now.
ifonuser78 said:
I'm flashing the pre-rooted MGA now.
Click to expand...
Click to collapse
Pre-rooted MGA works fine, but no other custom ROM.
I ran TriangleAway to reset the counter, but that didn't help either. No third party custom ROMs for me. :crying:
Flash latest Philz recovery.
Go to mounts and storage.
MAKE SURE YOU HAVE A ROM ON SD CARD.
Format system, cache, data and preload.
then just to be sure everything is gone I go to wipe /data factory reset and choose the wipe to install a new rom.
Then go to install zip and flash rom.
Once it's flashed you should be good to reboot.
If you're still in a bootloop then go to wipe/data factory reset but choose first option not the one to install rom.
Now reboot again, good to go!
Just a thought, if you're still having trouble flash a AOSP kernel in Philz as you might be trying to boot an AOSP rom with a TW kernel installed
Sent from my GT-I9505 using XDA Premium HD app
I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
No suggestion, but I just flashed SlimBean on mine from a full wipe, and I'm having the same issue.
I tried SlimBean again, and it worked. Here's what I did:
1. Updated my bootloader. Mine was still 4.13, and it looks like the most recent version is 4.23. I flashed the img from this post using NRT.
2. Went back to unrooted stock with NRT. (I had to update my bootloader to do this.)
3. Let it boot back into unrooted stock, wept with joy, made a nandroid from NRT.
4. Flashed the SlimBean 1.9 weekly and minimal gapps from NRT's advanced area.
5. Watched in amazement as it boots obediently. Let sit about 10 min, and rebooted.
I'm essentially lazy, so yes I used NRT instead of manually pushing everything with ADB. ADB was plan B. It was briefly plan A, but I got tired of trying to convince the Android SDK that I did in fact have the Java JDK installed.
Mhhhh....
PatrickMac said:
I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
Click to expand...
Click to collapse
Well I have the same problem with booting Ubuntu touch.... Either it's stuck on white Google Logo or stuck on Cyanogenmod Logo... Have flashed it with TWRP and MultiROM...
Hi, I have a nexus 4 JWR66Y 4.3 rooted and unlocked with cwm touch 6.0.4.3 installed and when I flash a custom roms and reboot it just show me a black screen that loop. I also tried TWRP but it did the samething.
P.S: I alway wipe data/factory reset before flashing the custom roms and the gapps.
What I have to do?
Thank you !
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!!!!