Has anyone else had bad experiences with CWM Touch? I started to use it in place of TWRP since it would work with Rom Manager (which is still kind of useless compared to what it was on the OG Droid) but it has screwed me over twice. The first time was I was switching ROMs so I made a backup and when I went to restore it later it said MD5 sum mismatch so I was pretty much screwed. Just now I went to try and make another backup since I had just installed Paranoid Android and had everything setup and I wanted a backup before I flashed Clemsyn's elite kernel. Knowing that I didn't have much space left I selected clean nandroid space assuming it would get rid of the previous backups, after it finished it said it was done but never brought back the UI so I had to do a hard reboot.
Upon boot up it just hung at the Google screen, I did a few more reboots and got the same thing. I went into the bootloader via the three finger method (which to my surprise worked without connecting to a USB port, so I'm assuming this is a problem with the 3rd party recoveries and not the device itself?) and selected recovery but i was stuck at the Google screen again.
Time to switch back to TWRP!
TL;DR CWM Bricked my Nexus and the backups don't work
Related
Hi all,
I'm having a little problem. I have researched but everything I've found leads me back to square one...
So I followed this guide to installing CM7 on my M2. Please note that I have in the past successfully rooted my phone, installed the Argenstone ROM and one other basic Great Britain Rom. So I'm not a total nub. However at this stage I have a phone that's is useless to me...
My phone is rooted. I have Droid2Bootstapper installed and I managed to get the CWM 3.X installed. I downloaded the all-in-one.zip file from the CM7 ROM thread (the zip is actually called EndlessCM7-110901-nightly_build.zip - hope that's not an issue?)
I booted into CWM and applied the EndlessCM7-110901-nightly_build.zip and after (without a reboot) wiped everything (I had backed it up previously).
I rebooted the phone and...well I get the Google logo with the Motorola M and the Cyanogen bot as the 2 'O' characters. Then after a while a 3D rotating 'square' and the android writing and logo 'shimmering' in and out but that just goes on forever. I left it for an hour at one point and just gave up.
Now I can't even get past the Google logo. I've tried restoring my previous back up but that won't work either. I can't boot into the OS to actually use RSD lite to flash a known working ROM over the top.
When the LED turns blue and I hit the volume key it displays "Android BootMenu <v1.0.3>" which is different to the CWM 3.X that I was getting prior to applying the EndlessCM7-110901-nightly_build.zip file.
From here I can select to recover the last 'latest recovery' which when done loads into CWM-based Recovery v4.0.1.6-defy.
Basically I'm at this point where I seem to be able to load just about every boot menu under the sun and do everything but actually launch the damn OS.
How can I get out of this hole? Preferably I'd like to get everything back to the stock ROM the phone came with so that I can start from scratch again.
Any bodies help would be more than appreciated.
Cheers,
- Matt
EDIT: I have even used CWM 4.X+ to try and restore the Argenstone ROM. it goes through the whole process of checking the MD5 sums, restoring the system and boot images etc and seems to work without any issues. I then wipe all data and reboot. Nothing - still the same cyanogen Google logo and the only thing I can do is boot into all the CWM menus.
*sigh*
Argh feel like a true idiot now. It took me about an hour of searching earlier but I've only just found/remembered how to get RSD lite to see my phone (pwr+volume+camera) and I'm wiping the whole thing to the factory (vodafone) ROM. Might take the opportunity to take it to Vodafone and tell them it never gets a damn 3G connection lol...provided this flash works (touch wood).
The last few days I had an experience that I want to share. Maybe it helps somebody else.
Last week I upgraded my Defy from Quarx's CM10.2 to CM11 version 20140724.
It ran for about two days. It was stable and the performance looked better than before.
Then, when I was outside, my battery was empty. I always have another battery with me, so I exchanged the battery.
Then, two seconds after I inserted the battery, a black screen with the following white text appeared spontaneously, without pressing a button:
Bootloader
09.10
Code Corrupt
Ready to Program
connect USB
I could not enter recovery, or anything else.
So, I decided to go back and flash the original Motorola Android 2.2 version.
On earlier occasions this worked perfectly when I bricked my phone, but this time, after flashing the SBF with RSDlite, the phone hang while booting with the android logo on the screen. Only after a few hours of trying different SBF systems, the idea popped up, that the problem was not in the SBF, but in the combination of the old Motorola system and the new CM11 data partition. So, I entered recovery and wiped the data partition.
Then the system booted normally and I could proceed with rooting the system, installing custom recovery and restoring the backup.
Everything is back to normal again.
Now, I wonder what could have caused this problem.
I am a bit suspicious about the backup method I used. I create backups with the online nandroid app. The CM11 system installed the TWRP 2.7 recovery. The first time I tried to restore a backup, I noticed that the TWRP recovery had a problem with the old (CM10) and the new (CM11) backups, because they contained files for partitions and-sec and recovery, that it could not handle. In later attempts to restore the backup I unticked these partitions and the restore seemed to work well. I rebooted it several times. Could it be that these attempts damaged the system in such a way, that only when inserting a battery, the corruption was detected?
Or should I assume that there was a hardware glitch when the battery was replaced?
F.Zwarts said:
.
Then, when I was outside, my battery was empty.
Click to expand...
Click to collapse
iirc this was one of the bugs of cm11. if you let the battery runs completely down, it may not boot again. not sure if this has been fixed with the latest cm11.
My G2 has been acting really funky lately, hanging on boot and not being able to "hold" recovery flashes. I'll start from the beginning of my little story.
On Saturday, I wanted to do a nandroid backup from TWRP (not sure which version, an older one but not terribly old). It failed several times. I went back into the OS (CM 12.1) and backed up all apps and app data to an OTG USB via Titanium Backup. This was successful. I tried to go back into TWRP a second time. Nothing. Recovery is not even there, I get a security error from what I believe is fastboot. I went back to CM and tried to re-flash TWRP. Now I get a security error on the LG screen. Nothing would boot, no recovery mode, I did have download mode although I had no PC with me so I didn't know this at the time. I was away last weekend so I had to go without a phone for a day... which was actually... kind of pleasent. Don't ask me why I carried two 32GB USBs and an OTG adapter on my keychain but no laptop, because I have no idea why I would do this, lol.
Came home Sunday afternoon and decided to nuke the whole phone with a TOT flash. Since I always wanted to try CloudyG2 since we all know AOSP-based ROMs don't do the camera justice, I went ahead and TOT flashed, re-rooted, re-AutoRec, etc. Everything worked wonderfully; I did a full wipe in TWRP, flashed in Cloudy, then the KK radio, then Xposed. Played around with things like XCam and a few Xposed modules. Everything was working awesome, so I did my restore in Titanium. Took a few hours, but Titanium says everything went fine (sans for a few CM apps which did not restore by design I guess). I checked out a few apps, all my data is there, wonderful. Titanium told me to restart so after poking around a bit, I went for the restart. Hang on boot. For several hours. Tried to go to recovery, fastboot security error. Seems it can't "hold" recovery or something else that I'm flashing?
Clearly I am doing something incorrect here with flashing and all that, but I can't figure out what. I'm not new to flashing and modding, and I've flashed regular CM updates and other goodies onto this G2 for quite a while with no issues. I'm going through the same steps I would normally with CM, and I've had plenty of success with that. Any ideas what I am doing wrong here?
Had same issue and know I hard bricked it trying to get it fixed ... Off to a different phone I guess .. Not sure why it wouldn't hold a recovery either after a few hours ... I gave up .. Good luck
Sent from my SCH-I535 using XDA Premium 4 mobile app
Sorry for the long post! As a bit of background, I was running stock rom with sytemless root, EX Kernel, TWRP and I had just enabled xposed (the only new variable in my setup). So I plugged my 6P in at the gym before I play some ball. Phone proceeds to random "reboot" a few seconds later, no huge deal I thought. Then it enters The Indestructible Bootloop (IBL). It won't boot past the animated colored dots. Play for a couple hours, phone still not booted; slight to moderate anxiety setting in. I figure, worst case scenario, I have to flash a factory image when I get home. So I try to reboot it a couple times by booting into the bootloader (holding power and down vol), then recovery then reboot. I also flashed the xposed uninstaller and deleted /data/data/de.robv.android.xposed.installer/conf/modules.list: neither worked to solve the IBL. Then I just waited til I got home and tried to plug it into my Win 10 PC. Nothing. Device manager doesn't even recognize it as anything plugged in; moderate to high anxiety setting in. Note that I could previously connect it just fine and device manager doesn't see ANY kind of device connected, so I don't believe it's a driver issue or anything like that. So, through TWRP, I look to see what's on the device storage: I have an old nandroid ( I believe stock unrooted) and a custom rom, Chroma as well as some GApps and a couple custom kernels. At this point I wanted to preserve my text messages so I did a new nandroid then tried restoring the old nandroid as well as flashing Chroma without wiping data. Nothing, still won't get past the colored dot IBL. So then I tried doing a full wipe before trying the old nandroid and Chroma again. Nothing. Figured it may have been a malicious file on my sd card so I deleted a few files that I didn't immediately recognize in TWRP and tried all the above steps again. Still nothing. So I just called Google and they offered to replace it. However I would like to have my phone for the weekend and not have to have a $650 hold on my account. I'm on Project Fi so I can't use a temporary burner phone. I figure I'm probably screwed but hopefully one of you geniuses could help me out. Thanks in advance!
tl;dr: Phone randomly rebooted and entered indestructible bootloop. Windows device manager won't recognize it at all. Tried everything I can, including clean flash of custom rom and an old nandroid: phone still won't get past bootloop.
At this point I have completely run out of options. I AM CALLING UPON THE XDA COMMUNITY TO PLEASE HELP ME. Little bit of background info, nexus 6p was rooted and modified through xposed. Had some modules installed, mostly quality of life and visual/theme modules, as well as the latest version of SuperSU.
These past few days my Nexus 6P has completely stopped responding at times. Extremely laggy and could not do **** with it, systemui kept restarting over and over and over again for no reason. Had to keep force rebooting (holding down the power button for 10 seconds) multiple times over and over again, to the point where it suddenly stopped booting into the OS, it just kept giving me the boot animation loop, i could only access the TWRP recovery i had installed. Before all of this **** went down, I had created a TWRP backup because it would be my safety net if i could somehow miraculously get it to work. Now i have a backup of my TWRP BACKUP FILE on my desktop.
I have wiped caches more times than i can count, have tried factory restoring and formatted the data, and tried flashing the stock google image (the same one that i originally flashed at the time that I got the phone when i started to root) as well as flashed the old TWRP version i had, as well as the current latest version of TWRP, and then transferred the backup i made back onto the phone's internal storage. Tried restoring the old backup from TWRP, and each time it restores, it just reboots without reaching 100% and once it reboots, it still gives me a bootloop, this time, no boot animation, it just gets stuck at the Google text with a little "unlocked" logo at the bottom. I have completely run out of options, and have A LOT of EXTREMELY IMPORTANT information i have saved on the phone.
I will say it again. I am EXTREMELY DESPERATE to get my data back, to the point where i am even willing to offer a cash reward for any help to get my phone working back to the way it used to, or even at least to extract the information through the backup, if at all possible.
Additional information about the files and images I used:
angler-mdb08k is the name of the google image i had back when i had the phone and have flashed again
twrp-2.8.7.2-angler is the TWRP version i had back when i had the phone originally at the time
I had flashed and followed guides online through adb method.