Hey guys
I just got the motorola Defy + and wanted to update the android to 4.1.1
Managed to root it, install 2nd init and bootmenu, but CWM recovery wouldnt install properly. I speared through and updated the android without it. It KIND OF worked, but it's been acting really buggy, slow, freezing in the cyanogen blue title screen sometimes and I can't download anything from google play (Error [RPC:AEC:0]).
I'm terrified and I just want it back to the way it was (pre-root, pre-everything!) and start from scratch. I tried factory reseting it, but I still have the 4.1.1 version, not the factory one.
Help!
Hi,
Try to flash the stock .sbf with RSD Lite, which can be found here http://forum.xda-developers.com/showthread.php?t=966537
Related
Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Well, unfortunately with the screen cracked, you can't return to Motorola. I had a goof with my Atrix when I first got it because I accidentally did a SBF flash to the wrong version and it bricked the phone and fried the motherboard and Motorola replaced it because I said the Gingerbread update messed it up. Ha.
Anyways, since returning to Moto is not an option for you, I would just go ahead and try to install a custom ROM, maybe try Neutrino ROM 2.2 or 2.5?
Do you have ROMRacer Recovery or CWM Recovery installed? Will it let you get into it? If so, put a custom ROM on your SD card, do a wipe data and cache and install it.
I'm no expert, but I have noticed no one else replied and just trying to help.
Hope all works out for you!
Boot loop issue - at&t Android 2.3.6
Thanks andreww88 for your reply. I read in one of the forums that once the phone is updated with 2.3.6 don't try to go back to older versions especially lower than 2.3.4. That would make the phone to be hard bricked. That is why I didn't try any other ROM other than NottachTrix 4G because it is built on 2.3.6. I could be wrong. That is why I need some guidance to try any other custom ROM.
i had the same issue. What i did was get the Atrix Fastool and whipe the phone. Then i extracted the sbf for 141 and then flashed 59 60 and 61 smg files from fastboot. After that everything worked properly. To then unlock my bootloader i used the flashing script and i was set. This is recoverable not easy but you can recover.
Thanks Moneyman1978 for your reply. Can you be more detail what you did to resolve this issue. Can you send me the links or point me to Fastool and 141 .SBF file also SMG files. Thanks again.
gpr789gpr said:
Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Click to expand...
Click to collapse
Well, I had a similar issue. I did the 4.5.141 (OS 2.3.6) OTA update and then it would just bootloop. I'm on stock, rooted, locked BL. I then ran the OTA update again via recovery and that didn't help. I then did a full factory reset, then update via recovery and still didn't fix anything (good thing I had TiBu backup). After calling AT&T they finally admitted that Moto recalled the 4.5.141 build update since there was WIDESPREAD boot-loop issues with many Atrix users. Great.
They're sending me a new phone. Luckily, mine is in good condition.
Any one please have any suggestions for me. Do you think it is a hardware issue or can it be fixed by fixing the software??? Any help is appreciated.
If any of you has any ideas about how to fix this issue I would appreciate if you can share it here.
I install nightlies of CM10 onto my nexus 7 original 16GB every time one is released (which is probably not a good thing but there you go) and i upgraded from the release on 15/12/2012(4.1.2) to the release on (4.2) (I missed a day) but when i had installed i couldn't open Google Play Store which was strange and my favorite live wallpaper 'Microbes' wasn't on the device so i tried to downgrade back to the nightly from 15/12/2012 which was still downloaded on my device. This went smoothly until it came to the first boot where it has been stuck at the CM10 boot animation which is spinning but doesn't stop.
Does anybody know what has happened that could help me? I think it might be something to do with downgrading from 4.2 to 4.1.2. Also i use the CM Downloader that is built into Settings > About
Thanks in advance
DecDuffy
EDIT: I fiddled around with the buttons and managed to get it to restart booting but it is in the never ending boot animation again
EDIT2: I booted into recovery and then installed the nightly from 17/12/2012 and it is working to the same extent that it was before i tried to downgrade
DecDuffy said:
I think it might be something to do with downgrading from 4.2 to 4.1.2. Also i use the CM Downloader that is built into Settings > About
EDIT2: I booted into recovery and then installed the nightly from 17/12/2012 and it is working to the same extent that it was before i tried to downgrade
Click to expand...
Click to collapse
From these and from what i've found when fastboot flashing, i suspect that the either the bootloader changing when upgrading to 4.2.1 from 4.1.2 or the kernel changing caused you the trouble when trying to go back. if you want to check, you could try going into fastboot and see what bootloader version you have, and then try going back to the 4.1.2 build and checking that again. next, compare these with the bootloaders for stock 4.2.1 and 4.1.2. I suspect that in order to move back you would need to do what you did to move back to 4.1.2, then use fastboot to flash the older bootloader to allow it to work. But i'm not certain on that.
and you tried wiping data(factory reset) and reflaahing?
Hi, I've searched my problem but came up only with "regular" reboot answers. Let me explain:
I was using the newest CM10 builds by Quarx as they were coming, and once in a while my phone rebooted/freezed. I was using nightlies so I was ok with that kinda of thing. But after flashing the last nightly (07/03), my phone was rebooting whenever I pushed him harder than opening the app drawer.
After wiping data, cache and everything else without any results, I've decided to flash an official SBF - Then the phone rebooted in the middle of the RSD flash process. I've started it again and it went ok... but now my phone is rebooting at the Moto logo, when I try to wipe the cache or factory reset through bootloader. I can't do anything with him.
Can someone give me any expectation? Something new to try? Or, hell, even a confirmation that my Defy is dead and there's nothing I can do?
SBF
Hi,
draw the battery,
wait a time,
put the battery inside,
start the steps to flash sbf,
after the flashing is finish make a factory reset in stock recovery,
install 2ndint ( i wrote something on the beginning like: After install 2ndinit restart, deactivat usb debug,and restart again),
Then install one of the beautiful CMs here.
cardosy said:
Hi, I've searched my problem but came up only with "regular" reboot answers. Let me explain:
I was using the newest CM10 builds by Quarx as they were coming, and once in a while my phone rebooted/freezed. I was using nightlies so I was ok with that kinda of thing. But after flashing the last nightly (07/03), my phone was rebooting whenever I pushed him harder than opening the app drawer.
After wiping data, cache and everything else without any results, I've decided to flash an official SBF - Then the phone rebooted in the middle of the RSD flash process. I've started it again and it went ok... but now my phone is rebooting at the Moto logo, when I try to wipe the cache or factory reset through bootloader. I can't do anything with him.
Can someone give me any expectation? Something new to try? Or, hell, even a confirmation that my Defy is dead and there's nothing I can do?
Click to expand...
Click to collapse
You just have to flash another rom using RSD lite, It will work.
Or just flash the official ROM which u had before installing the CM 10
Thanks for the attention, but I have tried flashing both his original SBF (Retail 2.3.7 from Brazil) and the Chinese one, both causing reboots when I try to wipe data/cache in recovery. If I let it turn on normally it reboots in the first steps (wifi and account configuration), so I can't even install 2ndinit or wipe data through the system. Any other ideas?
Hello,
I will try to keep this short. Was running 4.1.1 and rooted with moto2fail and installed safestrap recovery then I made a stock backup.
One day, my camera quit working (camera screen loads then a box pops up saying unfortunately, the camera has stopped) Anyways, I cleared data, rebooted same results. I didn't want to mess around with any files, so I decided to update to 4.1.2.
After the update, i get message that the update failed but everything seemed to be fine. AND the camera started working again.. Ending up losing root in the process, motochopper appears to install fine, but I get an error message when trying to update supersu. So, I reverted back to my 4.1.1 backup through the rp(?) tools in the stock recovery.
So now I'm back to 4.1.1 with full root, but no working camera. I can update to 4.1.2, but I think I'm gonna have problems with rooting again.
I did try reinstalling the stock MotCamera.apk from a stock razr m 4.1.1 rip. but it still fails. How can I fix the camera issues without having to mess around rsd lite?
Sorry about the confusion, just trying to lay out my issues and I will answer questions as I can.
i'm having the exact same issue, after failing to update to 4.1.2, i restored to 4.1.1 backup i had, but the camera just force closes. i'm on stock room.
bobross82 said:
Hello,
I will try to keep this short. Was running 4.1.1 and rooted with moto2fail and installed safestrap recovery then I made a stock backup.
One day, my camera quit working (camera screen loads then a box pops up saying unfortunately, the camera has stopped) Anyways, I cleared data, rebooted same results. I didn't want to mess around with any files, so I decided to update to 4.1.2.
After the update, i get message that the update failed but everything seemed to be fine. AND the camera started working again.. Ending up losing root in the process, motochopper appears to install fine, but I get an error message when trying to update supersu. So, I reverted back to my 4.1.1 backup through the rp(?) tools in the stock recovery.
So now I'm back to 4.1.1 with full root, but no working camera. I can update to 4.1.2, but I think I'm gonna have problems with rooting again.
I did try reinstalling the stock MotCamera.apk from a stock razr m 4.1.1 rip. but it still fails. How can I fix the camera issues without having to mess around rsd lite?
Sorry about the confusion, just trying to lay out my issues and I will answer questions as I can.
Click to expand...
Click to collapse
It could be that the Update has updated the firmware of the Camera itself, causing it to now be incompatible with the older 4.1.1 drivers baked in.
Typically when I get into these types of scenarios, I always feel best doing something along the lines of an RSDlite wipe and start fresh. Do the update straight, then customize afterwards.
I would unlock your bootloader prior to guarantee you have a back door into the phone afterwards.
I can't rsd back to 4.1.1, i get a preflash verification error, the only thing that works is matt's new utility that flashes to 4.1.2, the camera works after that, but i want the camera to work on the backup I did when i was on 4.1.1 before the update.
cybrnook said:
It could be that the Update has updated the firmware of the Camera itself, causing it to now be incompatible with the older 4.1.1 drivers baked in.
Typically when I get into these types of scenarios, I always feel best doing something along the lines of an RSDlite wipe and start fresh. Do the update straight, then customize afterwards.
I would unlock your bootloader prior to guarantee you have a back door into the phone afterwards.
Click to expand...
Click to collapse
I ended up booting in stock recovery by trying to get into fast boot, then selecting ap or rp tools(can't remember which). Truthfully, didn't even realize what it was. It loaded up what to me looked like the recovery menu with safestrap. Which I thought I uninstalled. From there, i restored the 4.1.1 backup I had. Then updated superuser and supersu from the play store. read in another thread to check and uncheck temp unroot in voodoo ota. twice.
Then I took the 4.1.2 update, was then able to install the supersu binary once it was finished and checked, and it kept root through the update. Camera works also. I still received a update fail message afterwards. But all appears to be okay, camera works, root checker says I have root, so all appears to be good.
I did make a backup of this in safestrap, and updated my backups in titanium, and froze a bunch of apps. Everything seems to be working just fine. I haven't unlocked the bootloader because I don't really feel like flashing any roms to this phone. Stock rom and rooted seems to be be good enough for me. For now.
If you still have a locked bootloader, you can't revert back without having issues. Once you've installed 4.1.2 and its boot.img, you shouldn't be able to restore a 4.1.1 ROM. If you are unlocked, then it's a different story.
For the OP, the best solution is to use Matt's Utility 1.20 and fastboot flash to 4.1.2. This utility does not require the use of RSD. After you flash, boot up the phone and just do basic setup, then use the Motochopper function in the utility to get root access. After you get root, then continue set up on the phone.
Hi,
I have a rooted nexus 6p, all was well until it decided to reboot and boot-loop when I opened my music app. I get as far as the white Google logo then the phone restarts and I'm back to the normal warning then Google logo then reboot.
I have managed to get into the recovery screen (with the android laying down) but when i choose recovery mode the phone just starts boot-looping again.
I am wondering if I have somehow managed to hard brick it?
I have tried to flash the latest OS onto my phone but it said no signature.
I did managed to wipe the device also.
Thanks for any help.
Are you on Nougat or still on MM? Since you're rooted, it means you didn't receive an OTA. Did you flash it yourself, originally?
istperson said:
Are you on Nougat or still on MM? Since you're rooted, it means you didn't receive an OTA. Did you flash it yourself, originally?
Click to expand...
Click to collapse
When my phone started playing up I was still on MM 6.0.1, I tried to flash N after the boot-looping started.
Thanks