My moto g xt1063 keeps rebooting but I can't figure out why. Sometimes it goes to the home screen and works fine for a few minutes before rebooting again, most of the times it gets stuck on the bootloader warning screen and reboots. I can access recovery though.
I had planned to install cyanogenmod on it a couple of months ago but I got stuck on an "Error updater binary in zip" so I just gave up. The device is running Official Rom provided by Telcel (México) and has SuperUser on it too, I had a notification about the binary but updating didn't fixed the problem.
I have a backup on my computer (mac) but since I can't get the phone to sync by usb I was wondering how to copy it via recovery (clockworckmod v6.0.4.7) or if it's best to buy a micro sd and try to install from there.
Any help would be greatly appreciated.
First try a factory reset.
Use an sdcard yo retore backup
If fail return to stock rom
If you have a recovery installed try to make a backup from there and save it in some place like a sd card.
After that I suggest you install CM 12.1 21/05/2015 and look how it works.
Or if you prefer then reinstall the stock rom.
Related
Hi all,
Last night, i rooted by N7000 through PhilZ-cwm6-DDLSC-ODD-5.08.5-signed and was successful in doing that.
Later i wanted to update my device to 4.2.2. So i downloaded cm-10.1-20130727-NIGHTLY-n7000.zip file and kept in my external SD card.
Then in recovery mode,i wipe the factory data. There was option wipe data or wipe to install new ROM. I selected the latter one. Wipe for installing new om was successful. Then i went to update zip.file option. But since the file was in external sd card, it was not detected and i was not able to select the file. Then i rebooted the phone but only 'Samsung galaxy N7000' screen was coming and nothing was happening.
I rebooted my phone many times but same screen was coming. Then in morning i went in advance options. I selected Recovery Bootloader. Downloading screen was coming and nothing was happening. Then i switched my off and trying to start in recovery mode but its not starting.
I thin i have no checked USB debugging.
Kindly help soon as i am helpless without phone. Your early response will be highly appreciated.
With the option "install new Rom" you removed your old Rom from your device. So it is only logical that your device won't boot into it.
Next time follow the installation instructions given in the CM-thread exactly.
And of course you can choose a zip from external sd card in CWM. So take a look again.
Best thing to do for you: boot into download mode, install a stock Rom with PC Odin and use it without changing things.
Hey Thanks for the help. But now i am facing new problem.
I flashed my phone using odin with stock rom.
Later i rooted with PhilZ-cwm6-DDLSC-ODD-5.08.5-signed and then updated it with cm-10.1-20130727-NIGHTLY-n7000.
This time i was successful. My phone was updated to 4.2.2.
Then i used it for some time and switched it off for removing the external SD card. After that i tried to switch on my phone, its not working.
Nothing is appearing on screen. I charged it and then tried to switch it on but nothing is coming on screen.
When i try to switch on my phone in Recovery mode or in download mode a thin line on the screen appears and then disappears and then nothing comes on screen.
Help please. Last suggestion worked.Kindly advise
I was trying to install this: http://forum.xda-developers.com/showthread.php?t=2097731
because my tablet kept having soft reboots. I updated everything it told me to and now I have cyanoboot. I forgot to download the updated rom from:
http://forum.xda-developers.com/showthread.php?t=2063968
to my NookHD and I'm stuck at the bootloader like an idiot. I tried to adb-push the rom but no luck. I tried a tutorial but it wanted me to adb push to sdcard which I'm very sure it doesn't have enough space. I tried removing the micro sdcard to and see if it'll boot me back to stock but instead it tries to boot to cm which is not on the tablet anymore. Help me please.
So I was running a cm 10.2 nightly (late december) and today decided to try the new CM11 ones.
I download it and try to install it through the standard cm updater, when it reboots to CWM I get the famous "status 7" error.
I didn't think much of it and selected reboot now, then was presented with the "root permisions possibly lost want to fix now" message, I hit go back.
Ever since then, my device has been on a boot loop. After I re entered CWM I selected the option to fix the root permissions and after some attempts to start the phone again I did a factory reset&wipe cache which didn't help at all.
I have a backup on my computer of stock 4.1 rom but I don't know if/how I can use adb push while on CWM or bootloop to transfer it to the phone. I may be able to use a card reader to put it on the micro SD card and will try it tomorrow because I have to sleep now.
My CWM version is 6.0.3 and not 6.0.4, not sure if that caused the problem but I read that to update to CM11 you need the 6.0.4 version.
Any help to unbrick my phone would be greatly appreciated.
You've answered your own question as to the cause. People on here don't normally say things like "CWM v6.0.4.4 or newer required" just for fun.
As for getting the phone back, search and read.
Yeah I read that after I had bricked my phone, trying to load my backup to external sd right now.
Hi ! So a few weeks after succesfully unlocking/rooting/ROMing my phone, yesterday morning at exactly 830am, everything stalled. I had to force shutdown the device, and when I did, it encountered a bootloop. I could get into recovery mode, but TWRP would freeze on logo, and CWM would freeze on formatting /data. I had later realised that this was because neither of the recovery options could mount /Data or my SD card. I removed my SD card to check it's status on my computer, but now my computer can't detect it. Fast forward I put the SD card back into my phone and reboot, and now somehow I can't even get into recovery. TWRP keeps flashing the logo, and CWM brings me to an android logo that keeps reflashing as well. I'm not sure what type of situation I got myself into or how to get out of this, but if simple instructions are possible to be provided I doubt i'd have difficulties fixing the problem.
Post in wrong section, its 1st gen. Please move
So recently I decided to unlock my bootloader and flash CM12 on my Moto G 1st gen
Everything went fine till a friend told me to download and install Xposed. As I launched the app and hit frame work it mentioned creating a backup before installing so I did using TWRP. From there I rebooted the phone and thats where I ran into problems, it started to bootloop. After many hours (3 days to be exact) I still cant get it out of this state.
I thought I fixed it by reflashing, but apparently it just flashed it onto a seperate partition and the new ROM didnt work well (Notification bar didnt pull down right, no home button or multi-task). Since it didnt work I tried to wipe it and reflash but that apparently wouldnt boot, then I lost the ability to access recovery.
ADB doesnt find the device, I think usb debugging got disabled at some point.
I need some help on how to unbrick this, I'm 4 days in and still out of luck. Please!
Nobody?
You can´t access the recovery at all? When i get into a bootloop i need to do a little trick to enter recovery; hold down the power button for several seconds until it reboot, then as soon as the screen turns black hold the power button and volume down for 5 seconds to enter into bootloader. Then enter recovery from the bootloader, do a full wipe and install a stable rom. If you can´t connect the phone to the pc, take the sd card out and put it on another phone so you can connect it to a pc to transfer a stable rom for flashing on your phone.
Sorry this is late, completely forgot I post this. I can now get into recovery although some features dont work as the phone has nothing else on it. Got a USB OTG cable today and going to try mount cm12 that way.
Update : Using TWRP mount I now have files on the device (Data, boot, sys, system) which I didnt have before. Although I'm now getting a E:unable to mount '/system' but TWRP says Successful. Any thoughts?
Update 2 : Flashed it another 2 times, that seemed to fix it. Now no SIM detected.