Hello,
I successfully installed cyanogenmod 7.2 on my Motorola Defy MB525 using the instructions from the cyanogenmod wiki "Install CM for jordan" (can't post link yet).
After a while, I wanted to install gapps, so I installed it from Bootmenu. After this, the phone was always booting to boot menu and I didn't know how to make it boot into the system, so I changed the "Boot" option default to something like "Normal", I think.
Now when starting the phone, all I see is the Google logo which stays there indefinitely.
I can still boot to BootMenu and tried a number of times to wipe data/factory reset, wipe cache, wipe dalvik cache, and re-install the cyanogenmod7.2 zip, but it still can't get out of the infinite loop.
I found out that a posible solution would be to flash an image with RSD Lite, but it seems kind of tricky and I would rather leave it as a last resort.
Any ideas?
Thanks
I managed to unbrick my phone eventually.
Tried to use RSD Lite with several images, but it would give an error and then the application would crash and leave my bootloader corrupt. I tried all the schemes I could find including: loading the image from root of C:, disabling UAC, etc., but nothing worked.
Then I tried sbf_flash on Linux with the same image, and it worked like a charm, no errors, and my phone was up and running again.
So for anyone else who may encounter this problem, I warmly recommend using sbf_flash, it is incredibly simple to use.
sltrv said:
Hello,
I successfully installed cyanogenmod 7.2 on my Motorola Defy MB525 using the instructions from the cyanogenmod wiki "Install CM for jordan" (can't post link yet).
After a while, I wanted to install gapps, so I installed it from Bootmenu. After this, the phone was always booting to boot menu and I didn't know how to make it boot into the system, so I changed the "Boot" option default to something like "Normal", I think.
Now when starting the phone, all I see is the Google logo which stays there indefinitely.
I can still boot to BootMenu and tried a number of times to wipe data/factory reset, wipe cache, wipe dalvik cache, and re-install the cyanogenmod7.2 zip, but it still can't get out of the infinite loop.
I found out that a posible solution would be to flash an image with RSD Lite, but it seems kind of tricky and I would rather leave it as a last resort.
Any ideas?
Thanks
Click to expand...
Click to collapse
Related
I rooted my G2 via the instructions and download in this thread:
http://forum.xda-developers.com/showthread.php?t=928160
I did not flash the hboot.
Phone seemed to work fine after that. But then I downloaded ClockWorkMod Rom Manager and downloaded CM7. When I installed it, my phone comes up to the boot screen, runs for a second, then reboots.... it just keeps rebooting.
Using the factory reset, I can get back into the recovery, so I tried to install CM6.1 from my sd card, but the exact same thing happens (endless boot screen reboots).
What can I do? Thank you for any help.
Fixed.
All I had to do was clear the dalvik cache.
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
dwl99 said:
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
Click to expand...
Click to collapse
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
DigitalMD said:
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
Click to expand...
Click to collapse
Thanks but Odin cannot see the tablet to re-flash the recovery.
Downlods mode
Then flash new firmware
sembre said:
Downlods mode
Then flash new firmware
Click to expand...
Click to collapse
That's the problem - I cannot access download mode
UPDATE - it just started in download mode! I can manage from here!!
Just for the record you can install adb on the pc and run the command 'adb reboot recovery'. This will force the tablet to reboot in recovery mode.
Sent from my GT-I9300 using xda app-developers app
Jeez, this has taken up most of the day to fix. I came across many problems I have not previously experienced:
1. When the tablet was stuck at the boot animation and I tried to turn it off by long-pressing the power button it immediately restarted. The only way I could get it to turn off was by long-pressing the power button whilst it was connected to my PC.
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
3. Flashing CWM with Odin caused the tablet to reboot into the stock ROM which would not load, in the end I had to untick the "reboot" button in Odin, power it off then manually restart with the Vol- & power buttons.
4. The only way I could get a bootable ROM was by flashing CM10 with CWM. I tried to restore 2 previous CWM backups but on each occasion there was an error restoring the Data partition and I got stuck at the scenario at (1). The backups were made to the external SD card with CWM Touch - is the Touch version unreliable?
I would be really interested if anyone could shed any light on any of this stuff!
For how long did you let it install during the first reboot? It happened to me too, and it took about 10 minutes, maybe even more...
Also, did you try in the "Mount and storage" cwm menu the options "format system", "format data", "format cache" and "format preload" options, prior to re-flashing a ROM? I have read somewhere that for a clean install it's better to do this, as it really clears everything that could mess up the system between two different bases ROMs (like CM and stock).
What I do everytime is using in CWM these 4 "format" options, plus "wipe" system, cache and dalvik, then immediately after this I flash with cwm the new "zip" copied on the card. Then the first reboot is much longer than usual, as at this stage it installs the files, rebuild the dalvik cache etc.
Good luck
dwl99 said:
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
Click to expand...
Click to collapse
I think I gave it a good 20 mins to boot. When I got up this morning there was an error message saying that there was no room to install any more apps even though I had very few installed. Settings -> Storage would not calculate the space available so I figured that the partitions had become corrupted. I did the step by step format you described and reflashed & it all seems to be OK now.
Hi All,
I have the Telstra HTC One XL, and have just recently attempted to install CM10 ROM - however have run into some problems that I would appreciate some advice to rectify. I had recently updated to Jelly Bean OTA.
I followed the guide on these forums - http://forum.xda-developers.com/showthread.php?t=1859478
I Successfully unlocked bootloader by following the steps at HTCdev.com
I Successfully installed TWRP Custom Recovery
I Downloaded CM10 as per - http://forum.xda-developers.com/showthread.php?t=1790032. I transferred this as well as Google Apps onto my phones storage.
When attempting to install CM10, I created the Nandroid backup as recommended, and proceeded to wipe the mentioned items using TWRP (a guide I saw said to wipe everything). This is when my Nandroid back-up got wiped. TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe? I proceeded to try and install CM10 and gapps from internal storage (I had to re load these back on after I wiped everything), and the install of CM10 displayed as successful.
Upon rebooting to system, the HTC screen comes up first and then goes to the CM10 animation. The phone then stays on this animation (rotating circle) for up to 10-15 minutes.
I have read thread after thread with people experiencing similar issues, and have tried rectifying my problem with various versions of roms and different guides out there. I can still boot into recovery (TWRP) mode via bootloader, and this means I can still mount my phone's storage onto my PC and have access to the storage directory. As I have deleted the Nandroid backup though, and because the ROM's won't install, I am stuck in no man's land.
There must surely be a way to have a ROM installed (even if its back to stock Telstra) from the position I am in, it would be greatly appreciated if someone may be able to point me in the right direction.
Thanks,
Robbie
maybe yall need to "fastboot flash boot boot.img" now
robbie.d said:
TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe?
Click to expand...
Click to collapse
Why do people keep doing this??? Just because TWRP gives you all those options, doesn't mean you should use them.
Sometimes, people will say to do a "full wipe" when flashing a ROM. But that term is a bit misleading. Factory reset (from TWRP, never from hboot), wipe Dalvik and wipe cache is all that is technically required when flashing a new ROM. Some people like to wipe more "just in case". But if you aren't completely confidant in what you are doing, keep in simple and don't make it more complicated than it needs to be.
I don't know if wiping everything is the cause of your woes, but it certainly didn't help, and caused you to do some extra steps.
Flash boot.img via fastboot as previously suggested. Otherwise, just try to re-download and flash the files agin. Its seems that some people are having troubles booting after flashing CM10 (even after doing the correct wipes and flashing boot.img). Doesn't seem to be much rhyme or reason, but just flashing again has fixed the problem for at least one person.
Thanks so much, such a simple fix! That has me booted up into CM10.
I have installed cm-10-20130107-NIGHTLY-evita and cm-10.0.0-evita , however with both of these versions, my touch screen is not working once it boots up. I can function with the volume up/down, and with the power buttons, but cannot get past my SIM card lock screen.
I noticed this thread http://forum.xda-developers.com/showthread.php?t=2083314 (no solution yet)...
Does anyone have a solution to this issue that seems a common one?
Alternatively, more than happy to get an alternative ROM on my phone in the interim...Can someone recommend me a ROM?
Again, I really appreciate the quick response to my problem, very happy my phone is in operation!
Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
So I was in the process of manually installing CWM Touch via Rashr Flash Tool, and when I successfully got it installed, the app asked if I wanted to reboot into recovery. So I pressed yes, and it did.
Unfortunately, whatever that app wrote into the androids system, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS. Even when I explicitly chose "reboot to bootloader" in CWM, it would still reboot to recovery. I've even went to a totally stock restore, and it still kept happening. Cleared cache, data, davik cache, same result. What can I do?
I currently have 2 restores. One of cyanogen, where i used Rashr's tool, and the other a V6 stock restore.
CartoonmanPDC said:
Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
So I was in the process of manually installing CWM Touch via Rashr Flash Tool, and when I successfully got it installed, the app asked if I wanted to reboot into recovery. So I pressed yes, and it did.
Unfortunately, whatever that app wrote into the androids system, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS. Even when I explicitly chose "reboot to bootloader" in CWM, it would still reboot to recovery. I've even went to a totally stock restore, and it still kept happening. Cleared cache, data, davik cache, same result. What can I do?
I currently have 2 restores. One of cyanogen, where i used Rashr's tool, and the other a V6 stock restore.
Click to expand...
Click to collapse
Yes, restoring the last working nandroid backup would be an option.
Alternatively you may have to flash another recovery.
I found this guide to flash CWM recovery on a similar device: How to flash cwm recovery on the lg spectrum 2.
But I am not sure if it wil work for your device too.
So better ask in the General discussion > Questions and Answers forum.
Thread closed and thank you.
So I unlocked, rooted and installed Euphoria ROM on my Moto G today, and now I'm perplexed to find that when I select the "Reboot" option either in Android or TWRP, I immediately get shoved back into TWRP. Rebooting to Bootloader works as expected, rebooting to Recovery works as expected, but the normal reboot doesn't.
Also, when my phone is offline and I plug it in, it immediately lights up and boots directly into TWRP. I don't know why this is, but I'd like to fix it since it's hit and miss trying to boot into the ROM normally.
Can anyone help me pin point the problem? In all my years with Android I've never seen an issue with boot priority such as this.
Things I have done:
-I tried to decide on a recovery so I flashed PhilZ, CWM, and TWRP in that order from the fastboot commandline
-wiped system, data, cache, dalvik cache, and flashed Euphoria ROM
Thanks!
One thing I would suggest is to flash the stock recovery and try rebooting, even i had encountered this problem. Later you can flash twrp again and everything will work fine.
Are you getting any errors while wiping partitions
sjandroiddeveloper said:
Are you getting any errors while wiping partitions
Click to expand...
Click to collapse
I'm having the same problem here. Wiping works alright, no errors at all. Although the built-in TWRP file manager is unable to see any files in the system folder.