So I just installed the CM10 nightly ROM from the original development thread, and after rebooting after starting up the ROM once, it won't let me boot up.
It sits at the CM boot screen and loops until it's battery is dead. I also cannot get into recovery. I can get to the bootloader, but I can't adjust anything past the start in the top right. I also can't connect it to my computer anymore due to the fact that ADB isn't on.
What do I do??
Fastboot flash stock imgs?
Clear your /data and to be safe wipe system cache and dalvik then reflash cm10. It happened to me too...
If all fails flash back to stock as suggested above.
Sent from my Nexus 7 using xda app-developers app
Related
I tried to install CM nightly off the official CM mirror network.
I already had my phone rooted with Liberty ROM installed, so I simply rebooted into clockwork, did a backup, wiped the phone, and then installed the cm_droid2_full-21.zip from SD card.
Something is really buggy with the ROM and it FC's upon loading the home screen and then automatically reboots. I cannot get into clockwork by pulling the battery or holding down camera and power, or power and volume down---nothing works. I'm stuck in this bootloop and as of now my phone is useless....please help!!
Sounds like you have no option but to boot the phone in bootloader mode and flash froyo build back on your phone.
U try to get into stock recovery and wipe cache and data? Its usually the cache
Sent from my DROID2 using XDA App
Hello.
Just yesterday, I installed CM 7.1 on my Defy, which was on stock froyo. It started up normally, and was working perfectly, until I had to reboot it, in order to get the google apps, when it went into boot loop.
I've tried going into stock recovery and wiping the data/ factory reset and wiping the cache, but even then it's stuck on boot loop on the CM 7 logo. What should I do?
Ps. It's the Indian Defy, which is without Blur, if that makes any difference.
EDIT: Just got it to work, I flashed the stock Froyo SBF using RSD lite. I think my mistake was installing Clockworkmod on it, because it has it's own custom recovery. Can anyone tell me how to get into it?
Ya installing CWM on top of CM7 will screw up the pre-installed Custom recovery. While the phone is just starting to boot watch for a blue LED to flash at the top of the phone. Right when it flashes blue, press volume down. From here use your volume rocker to select recovery, use the power button to make your selection. Next choose custom recovery.
Thanks mate
Though sadly, after rebooting it, it keeps on showing the message - process com.android.phone has stopped working, and I get no network. What do I do?
Wipe data and install the zip again...
Sent from my MB525 using xda premium
First, I searched and read all relevant threads concerning this issue. The five threads that showed up in the search did not help me solve my issue.
So on to my problem. I can no longer flash any rom onto my device. I attempted to flash the first official CM10 nightly (which I recently found out was not flashing properly for others) and had no success. I simply got a black screen and nothing more. I eventually got back into TWRP (v2.2.1.4) to try and Nandroid restore, but I noticed that /data was not formatting and the restore failed. Every time I would slide the bar across to confirm the restore TWRP would reboot itself. I then flashed CWM (v6.0.1.0) and the same problems were there. After that I flashed an earlier version of TWRP and successfully restored the backup. I'm not 100% sure how it was successful. So I decided to try flashing another ROM and no go. Same problems. Anyone have any ideas? When I was using CWM I got the error message below.
Code:
E: unable to locate volume information
E: unable to open ums lunfile '/sys/devices/platform/usb_mass_storage/lun0/file'
E: unable to format data
I'm running Bugless Beast with Motley #219
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
aznxk3vi17 said:
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What rom did you attempt to flash?
elementur said:
What rom did you attempt to flash?
Click to expand...
Click to collapse
So do I.I attempted to flash the first official CM10 8.18 nightly and had no success. I just got a black screen.Even more I boot into bootloader and choose to boot into recover but just stay at google logo.I try to flash recover once more,but just can't boot into recover!!
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Shano56 said:
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Click to expand...
Click to collapse
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
phiracle said:
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
Click to expand...
Click to collapse
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
android1234567 said:
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
Click to expand...
Click to collapse
Thank You Very Much!!!
I am having much the same problem as the OP. I finally rooted my Nexus 7 using WugFresh's Nexus Root Toolkit. It seemed all went well. I chose to use TWRP in a first attempt to install a ROM (I was on rooted stock), and following the instructions for installing my chosen ROM I went into it to wipe cache, Dalvic Cache and data. Both cache and dalvic cache wiped without issue, but when I attempted to wipe /data TWRP simply reported that it failed. With that failing, I did not attempt to install a rom. I was still able to boot out of recovery, but even with repeated attempts wiping data always failed. Is any one aware of any solution or have any suggestions. Thank you!
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 appear to be bricked. I flashed a recovery via flashify. Phone gets stuck on fastboot. This is coming from Houstonn's excellent PA rom. Tried to go to recovery. Goes back to fastboot. It just shows udc start. Tried connecting to my PC to flash another recovery via fastboot and it's a no go. Just shows wating for fastboot. Booting doesnt work either. Bootloop. So I figured game over and I'll flash to stock. To my horror, the restore process stops at 49%. Apparently, you have to come from a stock based kernal for it to work. Am I bricked for good?
Hello you must flash a stock Rom in the download mode.
Sorry... I don't saw that the flash stops
Then you must install twrp and costumrome again
Sent from my LG-D802 using xda app-developers app
Thanks for trying to help. I got it fixed without losing data. I got it to boot into the rom after shutting it down for an hour. Apparently it was overheating thats why it didn't boot. But if for stuck at the starting apps screen. So used adb to flash recovery again. Booted into recovery and reflashed rom after clearing data. Running like a champ now.
Sent from my LG-G2 using XDA Premium 4 mobile app