Hi All
I have recently tried to install Team EOS, and CM (Everest, stables and nightlies) on my MZ-601. Both have the same issue - it gets past the 'Motorola Dual Core' logo to either the EOS or CM boot logo, and just stays there, cycling through. I left it go overnight and both were still there in the morning. I eventually had to restore the backup stock 4.0.4. Anyone have any ideas?
Thanks
Sorry, should have also mentioned that it's a Telstra Australia MZ-601. Not sure if that makes any diff.
Related
On my Samsung galaxy S3, I installed an experimental Cyanogenmod update which was 10.(?). I had previously been running my phone on what I believe was 10.0.1. (But I'm not entirely sure about any of the update numbers because my phone will currently not boot) After I installed the update, I didn't like the results, so I updated back to 10.0.1(?) which was what I had originally.
After it finished updating, it attempted to boot up, but then it just stuck on the Cyanogenmod booting gizmo indefinitely. I've tried removing the battery and booting into CW recovery (Yes, it will boot into recovery mode), but it still only does the same thing. I need to use my phone tonight, so any help would be greatly appreciated!
On my Samsung galaxy S3, I installed an experimental Cyanogenmod update which was 10.(?). I had previously been running my phone on what I believe was 10.0.1. (But I'm not entirely sure about any of the update numbers because my phone will currently not boot) After I installed the update, I didn't like the results, so I updated back to 10.0.1(?) which was what I had originally.
After it finished updating, it attempted to boot up, but then it just stuck on the Cyanogenmod booting gizmo indefinitely. I've tried removing the battery and booting into CW recovery (it will boot into recovery mode), but it still only does the same thing. I need to use my phone tonight, so any help would be greatly appreciated!
cadeunderwood said:
On my Samsung galaxy S3, I installed an experimental Cyanogenmod update which was 10.(?). I had previously been running my phone on what I believe was 10.0.1. (But I'm not entirely sure about any of the update numbers because my phone will currently not boot) After I installed the update, I didn't like the results, so I updated back to 10.0.1(?) which was what I had originally.
After it finished updating, it attempted to boot up, but then it just stuck on the Cyanogenmod booting gizmo indefinitely. I've tried removing the battery and booting into CW recovery (it will boot into recovery mode), but it still only does the same thing. I need to use my phone tonight, so any help would be greatly appreciated!
Click to expand...
Click to collapse
Wipe it then flash a new rom. Confirm the MD5 checks out on it as well.
(backstory) Hi, ive had an Asus TF300T, for about 3 years now, unlocked, rooted it pretty early on... cycled between cyanogenmod and omnirom quite a bit, without really any major issues. Until today, i was running Cyanogenmods latest nightly build (CM11 Nov 5 2014), it worked just as any other nightly does a few bugs here and there, but nothing major and i hadn't done any major flashing or modding to the device. On my home from university, I turned my tablet off. And when i got home i plugged in the charger, and just as always the tablet turned on, showed the stock Asus screen, then changed to the Android boot animation... the animation then suddenly froze, and the device went into a boot loop... continuously... I dont know whats weong with it... tried to do a factory reset, i tried reinstalling the ROM, tried installing omnirom, but that got stuck on the OmniRom animation...
Im running Asus build 10.6.1.27.5
I had TWRP v2.7.0.1 installed but have now no longer works
id really hope there is a solution for this!
Thanks!
Edit: I dont know why, but when i try using fastboot or adb, the device isnt recognized. It doesnt show up on device manager either. I dont know if its the cable cause i bought it new, it says its can sync data, or a faulty charge/sync port....
razr9622 said:
(backstory) the tablet turned on, showed the stock Asus screen, then changed to the Android boot animation... the animation then suddenly froze, and the device went into a boot loop... continuously... I dont know whats weong with it... tried to do a factory reset, i tried reinstalling the ROM, tried installing omnirom, but that got stuck on the OmniRom animation...
Im running Asus build 10.6.1.27.1 (I know that theres a newer version 10.6.1.27.5, but when i try to flash it, the recovery says error and fails)
I have TWRP v2.7.0.1 installed but have now no longer works
id really hope there is a solution for this!
Thanks!
Click to expand...
Click to collapse
^THIS!
I was just to open a similar thread, then i saw your post. I join your request for help!
A month ago i have done a favor to a friend by unlocking his tf300t and installing CM11 on it. A few days ago he comes to me with this problem. I've tried anything but still no success:
- restore a backup done before flashing CM11 --> restore ends correctly but the problem remains
- flash a rom (CM11 and OmniRom) --> flash ends correctly but the problem remains
- flash the stock firmware found on asus website (WW_epad-user-10.6.1.27.5.zip, the SKU is correct for my version) --> the flash process stuck (i had to force restart the tablet after almost 2 hours of "flashing")
Since the boot animation changes according to the rom, i suppose the flashing process works. But the problem remains: after a few seconds the animation freeze and the device restarts, in loop.
Informations on the system:
- build 10.6.1.27.5
- TWRP v2.7.0.1 (working!)
- adb works (i managed to set /data as rw and push the .zip file to flash)
- fastboot should work
Please help! I feel a bit responsible for bricking my friend's device
SOLVED!
Finally!
I had already tried this method, before requesting for help, but the first time didn't worked... I don't know why this evening the tablet decided to collaborate:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
That worked for me! :victory:
A couple weeks ago I messed up my phone trying to flash a custom ROM. I'm just know fixing it and I just flashed my models ROM. (S4 US Cellular)
Here's my problem:
I installed CyanogenMod via SD Card, I flashed it, when I rebooted it flashed CyanogenMod and had the logo with arrows spinning around it, that moment of hope and pride lasted a mere 6 seconds as the screen turned off immediately. I tried booting it into recovery mode but all it does is show "Samsung Galaxy S4" and it turns off after a while. When I boot into Download Mode and hit "Restart" it does the same. I need help, thanks in advance!
I have an htc one s (rooted) ville
I installed cm nightly about 6 months ago as well as gapps.
I have been trying to update ever since, but no matter what I do, it boots up to the blue android logo, then saiys android is starting (optimizing apps) then restarts back to the blue screen and over again.
Ive tried to update and ive also tried installing after a factory reset and wipe but I still get the same problem