Hello Guys,
i have a big problem with my Nexus 7 2012 3G 32GB (Tilapia).
I unlocked my bootloader and flashed a CWM Recovery for GROUPER. It really couldn't mount anything in CWM. After i noticed that it was the wrong Version i flashed the right CWM for Tilapia. But after i had installed a Rom, the Touchscreen didn't responsed. I have flashed a custom rom, factory images of 4.4 and 5.0 but the Touchscreen won't come Back. So everything is working only without Touch!
tilapia
bootld.ver.:4.23
I can still access Bootloader and Recovery.
Please help me
Greeding Maxi
Did you solve this?
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!
I had stock Android 4.3 and wanted to get USB OTG to have more space using powered USB.
I first downloaded and installed Nexus root toolkit 1.6.6 and Unlocked the boot loader and then rooted the phone (pre -requisites for loading ziddey-otg-r165-07291101. zip)
All went well.
I am at Android 4.3 and rooted and then I went to recovery (TWRP) and then selected Install and selected the .zip that I downloaded from XDA.
Boom!
I tried to reboot the phone and ever since stuck in the start up screen just displaying the google icon for nearly 15 minutes. Did i just manage to brick my phone? Please help!
Also I am currently using the same toolkit to re-install factory stock Nexus 4 Android 4.3
Will the ziddey-otg-r165-07291101.zip not work at android 4.3? Please help any suggestions are welcome.
Thanks,
Sandy
This zip is not supported with Android 4.3.
Tell me if you need help in restoring your device to stock.
Sent from my Nexus 4 using Tapatalk 4
3 solutions
You can ether re flash stock 4.3 kernel
Or 2 you can flash any rom or stock android version and u can install the ROM from side loader in recovery
3 you can try to wipe data factory reset from recovery and cache partition vs dalvik cache
Just keep flashing Roms don't stop trying
Solved
Thanks guys. I was able to re-load stoc 4.3 and all looks good now. Still awaiting the OTg for the 4.3 and following ziddey's thread for the hack.
OTG not workin
I am running on CM10.2 with my Nexus 4. I have bought an OTG Y cable and flash kernel from Ziddey and... constant bootloop
Hi,
me and my friend recieved a N4 about 2 Days ago, and I flashed mine straight away with cm10.2 .
Now my Friend came to me and asked if I could flash cm for him too.
So I did push all files via adb to the Device, and unlocked the bootloader.
After flashing cwm I found the first difference that the Screen went black.
After a hard reset, I could boot into cwm, but unfortunatly cwm isn't able to mount the sdcard partition neither the Data partition,
so I took the way and tried to install cm10.2 through sideload, which wasn't a good Idea as there is no working android Version on the Phone now.
After trying to find out what wen't wrong, I found out that my friend installed the latest OTA Update 4.3, which I didn't.
What can I do now? Do I have to wait till Koush releases a new cwm Version which might works with the "new?" Partition Table of Android 4.3?
Any help appreciated.
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!!!!
I Got a GS4 GPE today, and after updating to 4.4.2 I went right to rooting it. I unlocked the bootloader, fastbooted CWM 6.0.4.4, and adb sideloaded SuperSU 1.93. I booted up and it was all working great! But the CWM recovery didn't stick from the fastboot, so I downloaded the manager to install it that way. After doing that, I now can only boot to CWM recovery (I can get to Android Default recovery and the bootloader, but no matter where I try to reboot from it keeps taking me to CWM. I'm guessing part of my stock ROM is corrupted? If anyone has any ideas I'd appreciate it greatly... I wiped dalvik and did a factory reset from within CWM, but it didn't help. Does anyone have a stock (maybe rooted) ROM that I could install in case this is actually corrupted? Thanks!