Hi, my attempt to upgrade my Defy to CM10 failed (constant loop-booting). I've tried to wipe and reload CM7.1, but now it won't go past the initial CM logo (doesn't reboot, just stays there). When I do a factory reset, I get 'Error Mounting /Data'.
Can anyone assist? please
Right, well I've reflashed the SBF and it still loops, just now it's the Motorola 'M' that is in a constant reboot. I don't have a clue what to try next, HELP!
aSystemOverload said:
Right, well I've reflashed the SBF and it still loops, just now it's the Motorola 'M' that is in a constant reboot. I don't have a clue what to try next, HELP!
Click to expand...
Click to collapse
Well after flashing my defy three times it finally came back to me. Just re-rooted it and getting ready to put 7.1 back on it. Would appreciate any feedback as to what might have gone wrong
Related
So like the title says, I SBF'd my phone yesterday to start from scratch, and now the damn thing is boot looping. I was running LB .5 on .595, and flashed the VRZ_MB810_2.3.34_1FF_01.sbf file using RDLite 4.8 (same thing I've done before, just not while on GB).
I've tried SBF'ing it a few more times, and I've let it sit, trying to boot, for 20+ minutes. The SBF seems to go through successfully. The result says PASS, so then I reboot the phone, and then boot loop.
Anyone have any suggestions?
Well, nevermind...instead of doing those multiple SBF's, I should have just looked around. Found this on droidxforums.com, and it's going through the activation now.
http://www.droidxforums.com/forum/droid-x-rescue-squad/14548-bootloop-after-flashing-sbf-file.html
You always need to wipe data and cache a few times before SBF'ing or installing any new ROM from scratch. Only with incremental upgrades to existing ROMs where the ROM chef says you don't have to wipe, can you avoid doing so.
Well, I didn't think I needed to specify, but yes, I wiped data/cache/dalvik when I flashed the ROM. So I don't really know why I then had to boot into stock recovery and do it again.
How many times did you wipe them? It doesn't work like deleting regular files on a computer, you need to clear them at least 3 times each. I don't know the details as to why, but never clear data/cache fewer than 3x. I do 5x.
weird.... mine usually works and on the pc just stops on 99% eventhough it's done and working. And once it bootlooped after installing a custom ropm and coudn't access both clockwork or original recovery so sometimes it may work, sometimes it may not work.
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 have been running the kanged builds of CM9 for a while, but it began to get bogged down recently and would freeze up almost daily forcing a hard shutdown and reboot.
Sometime yesterday, it began to boot only into recovery no matter what option I tried in the Cyanoboot menu. From there I tried a factory reset and wipe dalvik to hopefully get back into CM9 and here's where the strangeness really kicked off.
Clockwork (which was running off emmc) would freeze in the middle of the factory reset just like it would when CM9 was running (the graphics would degrade slightly upon inspection of the screen).
So, I grabbed my old sdcard with clockwork recovery on it to boot from sd, and I run into the same problem again. Freezing before a wipe, factory reset, or install from sd can complete.
Now, after each failed attempt in clockwork (sd and emmc) it sticks at a backlit black screen and after a hard shutdown refuses to boot (sd or emmc) for about an hour, only to repeat the madness again.
Does anyone have any ideas what I can try from here or familiar with a similar situation?
My sd clockwork version is 3.2.something and I've also tried 3.0.1.something.
UPDATE: For reasons unknown, my Nook seems to be booting regularly as of this morning. However, I am still unable to get a successful flash out of any rom. The closest I've gotten to success is stuck in a boot loop. I think from here I'll likely be able to figure it out, but just as before...
Any help is welcome and appreciated!
I had the same problem with the black screen when trying to install different roms on mine. I just kept clicking the power button and after a few minutes it would kick back on every time.
There is an entire thread specifically on this
http://forum.xda-developers.com/showthread.php?t=949699
As far as CM9 I can't help you much there. I would just try to install a different rom, and hope that works.
Thanks!
I had seen that thread, but I thought my experience was a different; either way, I've managed past that problem using a method similar to yours.
If this helps any, I have been trying to to 7.2 RC1 for a while as well, but it will not get me any further than the stuck boot screen same as the CM9.
Have you tried to follow the tread on returning it to stock ?? I would reformat and repartition it and return it to stock ... then make sure it runs. After that I would try to reinstall the new roms ...
Just my 2 cents
Tinpau
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 all,
I installed this ROM on my phone: http://forum.xda-developers.com/galaxy-s3-neo/orig-development/rom-cyanogenmod-12-1-s3-neo-t3099384
Notably I used the 20151111 version. Everything worked fine. I did however decide to try to encrypt the phone. Everything looked ok, but now the phone is stuck at booting. Notably, at the "Starting apps" stage of the boot process. Unfortunately this is too early to get a logcat. I already tried wiping the cache partition, doing a factory reset and reinstalling the image.
Any ideas on how to unbrick the phone?
x2b said:
Hello all,
I installed this ROM on my phone: http://forum.xda-developers.com/galaxy-s3-neo/orig-development/rom-cyanogenmod-12-1-s3-neo-t3099384
Notably I used the 20151111 version. Everything worked fine. I did however decide to try to encrypt the phone. Everything looked ok, but now the phone is stuck at booting. Notably, at the "Starting apps" stage of the boot process. Unfortunately this is too early to get a logcat. I already tried wiping the cache partition, doing a factory reset and reinstalling the image.
Any ideas on how to unbrick the phone?
Click to expand...
Click to collapse
Reinstall stock rom via Odin btw encryption screws up the phone in every aspect I recommend not doing so