Safe to install custom ROM with broken CWM or how to fix it? - Moto G Q&A, Help & Troubleshooting

Hi, really in the need for help, sorry if i get any concepts wrong but I've abandoned this kind of tech knowledge years ago.
XT1032, never rooted or anything, only installed OTA updates.
About a month ago it bricked (permanently stuck at Motorola loading screen). Tried to do a factory boot but CWM shows a dead android with a ! symbol on top of it. Too lazy to study and fix it myself i got it to a technician to fix it.
Everything got back to normal but it has been starting to slug just like before it brick'd.
Been thinking that rooting and installing a custom ROM could fix it? Thing is, I'm afraid to do it with CWM in such state.
Any ideas or tutorials to redirect me? Tried to google but only got specific cases of such issue with CWM for other phones

up?

last up

Related

Is it possible to get back my A510 in the manner I got it?

Hi,
I think flashing a ROM has been the biggest mistake I could make. I guess I just got greedy for a lil more performance that I decided to take the risk .Anyway, lots of things have gone wrong ever since.
To cut the story short, how can I reset my tablet to the way I got it? Locked bootloader, no cwm...how? I have restored via Nandroid, and did a factory reset...but still I can find traces of nothrills A700 ROM on my system. I wan't to get rid of all this.
Thanks!
PS: My device now shows up as "Acer A510 (registered November, 2012)" on Google Play. Previously, it showed up as "Acer A510 Tegra 3".
Please, don't start this conversation in multiple threads because people aren't answering your problems fast enough. You want to get back to stock because of problems (that have nothing to do with your flashing, but still) and people are already trying to help you with that in other threads.

[Completed] [Q] failed update on HTC Sensation

I had some time available today for a change and so attempted to do a long overdue update to jelly bean. Catastrophe! I dont know really where to start trying to solve the problem though I have spent my entire day off (sic) (NOT SICK!) prior to an all night 12 hour slog at work...not happy...no phone and I'm on call...ooops So now you know what a bit of a prat I am perhaps someone out there in XDA land can forgive me and point me in the direction of help pages or suggestions to get me communicating again.....please...
I rooted and unlocked my phone a long time ago and have not been back to change things for ages so anything I knew back then isn't worth knowing. I've been trying to resolve a boot loop after trying to follow :
http://www.android.gs/update-htc-sensation-cm10-1-rc2-jelly-bean-4-2-2/
i followed these instructions carefully and the only issue I had with the files to install was that the CM10.1 file wasn't available so I went with 10.2
so the first question would be....is this file incompatible. I assumed it was just the next release with some improvements?
I have ClockworkMod Recovery installed and have tried endless times to get this thinkg to work but even dropping back to an earlier version of cyanogen mod 9 my phone loops shortly after loading the cyanogen screens....
Any pointers from you guys would be a great help. I'm sure you're going to want more information from me so I'll stop here and hope someone responds
all the best and thank you in antcipation
Hi,
As a general rule recoveries that work with cm9 do not work with cm 10.1.
Ensure that you have the proper recovery version and should you still have the issue, please ask here
All the best !!

Oppo N1 Problems. Please, Please help

I recently bought an Oppo N1 off of Swappa. I just got it today and its been one problem after another. Heres the story...
Rooted with Towelroot and installed Super SU/binary. Rebooted. The phone was running the stock Cyanogen 10.2 but it told me that CM had an update, so I figured id go ahead and update that aswell. It downloaded and installed but when it rebooted, the phone is just stuck on the OPPO screen. I can get into the recovery but I have absoutley no idea where to go from here. I've tried installing other versions of CM11 but it just says installiation failed. Still stuck on boot. It is also getting stuck and staying black and im having to leave it sit for awhile before it will boot. I'm literally begging anyone to help me out here. I'm lost. I will be closely monotoring this thread
After some research, apparently CM11 needs a custom recovery installed which i do not have. Is there a way i can install TWRP, or possibly revert the N1 back to 10.2???
Please, somebody help me

[Completed] LG G2 Boots into TWRP Every Time I try to boot after Update

Alright, so before I say anything, I have not visited this site nor have I conducted any business with roms, TWRP, etc in the past year let's say. I used to be an avid visitor, flashing a bunch of roms, but was tired of the amounts of bugs and problems that I found. So I restored my back to stock on my G2 from TWRP. Been using it for about 1 year now, just so I didn't have to deal with problems... until now.
So a few days ago I saw an update in my notifications, but for the love of God I cannot remember what it said. All I know was that it needed to update something about the phone, not for example an app. Today I decided just to update it, and suddenly the phone rebooted into TWRP. I thought that was weird so I rebooted it again, and back into TWRP I was. I tried restoring some old backups to see if they would maybe boot into it, but once again it keeps bringing me to TWRP. Now I am stuck in a position where I am unable to use my phone and am not sure what to do next. I haven't visited these forums in a while either so Im not sure where to post this xD.
Honestly if someone can suggest something or help me in any way, it is appreciated. If there is anything I can do to help, just say the word.
I am using the Canadian Variant of the LG G2, from wind. I believe it is a D801 but not an actual D801, as I remember being told to only flash D803 roms as it was basically a D803. Not sure if that helps. Im planning on getting a new phone so I just need this one to hang on a little bit longer.
Thread closed / Duplicate

GT-I9100 Nand r/w corruption suspected

Hello people of XDA!
I know that this thread may be repetitive, but I unfortunately didn't find any help in all threads regarding GSII's NAND r/w problem.
So in short, I will explain what happened to this device
I bought this GSII brand new as my 1st flagship device, and I am kind of sentimentally connected to it, if not I would've thrown it in trash a long time ago.
So here is the thing
I had stock firmware on this device (4.1.2 JB) , and after some time decided to flash CM 11 on it when it came out, and had it on my phone for 4-5 weeks but I instantly noticed that my device was overheating with that ROM so I decided to get back on stock firmware, unfortunately thing is that i flashed android 4.0.3 ICS (Movistar Mexico) then my device got bricked (I had a really bad knowledge back then about roms and things that I SHOULD and SHOULDN'Tdo), anyway I tried fixing the mess I made by flashing my original android 4.1.2 JB rom (Telenor Serbia) hoping that will solve my bricked device, but unsuccessfully. Then I tried flashing again standardly for maybe 4-5 times with no success and decided to explore more functions that odin provides, so I checked NAND erase all last time I flashed and I guess made a huge mistake, but still I couldn't boot my device, I tried hard resetting it (I lost my power button while replacing the screen of my phone, so I couldn't boot into recovery to check if device is soft bricked or really hard bricked, but download mode works just fine). Still I tried, I flashed custom kernels hoping they would fix this brick but nothing happened, I would really like to get this thing working again, I had no success at finding a good mainboard to replace the old one, and doing it in official repair shops and non-official ones costs more than the phone itself. Sorry for asking the same old question I guess but I would be really thankful if I could get this working again!

Categories

Resources