Ok, I upgraded my Milestone to official APAC 2.2.1 ROM. Was using it for a while, got bored and decided to go a custom ROM. I had previously successfully flashed MIUI and CM7 ROMS back on Eclair. Did a nandroid with Androdiani OR 3.3 and flashed CM7. Bootloop at CM logo. Pulled battery, reboot back to OR and tried flashing MIUI (stable version). Boot loop again at MIUI logo. Turned off using power button. Tried HO!NO!. Bootloop at M logo. Reboot, wipe, flashed FroyoMod. Bootloop again at M logo. Reboot, full wipe, tried iceandfire 2.9. Bootloop again at M. Gave up. Reboot, restored nandroid and everything is fine again. No idea what I've screwed up. Any advice?
Thanks.
Try wiping caches (both) and data in open recovery, then restart custom rom. Most custom roms require data/cache wipes.
Tried that. Wiped dalvik, and factory-reset before rebooting after flashing the custom ROMs. None of it worked. Cracking my head on this one.
Try flashing the 2.2 VR from http://android.doshaska.net/rootable, re-rooting the phone and starting the custom ROM process over again.
skadude66 said:
Try flashing the 2.2 VR from http://android.doshaska.net/rootable, re-rooting the phone and starting the custom ROM process over again.
Click to expand...
Click to collapse
Thanks. Will give a shot when get home from work and see if this fixes things.
Ok, tried flashing the 2.2 SBF with RSDLite. Checked version, exactly the same as what's already on the device. Flashed anyway. Restart, bla... bla... boot into Androdiani OR. Flash CM7, bootloop... damn... Nandroid restore.
Oh no! I can't get into bootloader mode now. I tried the D-Pad Up + Power button and it just boots up. No bootloader. Help.
afadzil21 said:
Oh no! I can't get into bootloader mode now. I tried the D-Pad Up + Power button and it just boots up. No bootloader. Help.
Click to expand...
Click to collapse
That doesn't make any sense.. did you do power+dpad-up and not the reverse?
Sent from my Milestone using XDA Premium App
I think I did Dpad UP+ Power. Got it to bootloader mode this time. Updated RSDLite to 4.9 and it recognised the phone when I plugged it in. Reflashed CM7 RC13 and gapps. Rebooted and... CM7 booted and started up. Crashing randomly though. Trying MIUI next.
afadzil21 said:
I think I did Dpad UP+ Power. Got it to bootloader mode this time. Updated RSDLite to 4.9 and it recognised the phone when I plugged it in. Reflashed CM7 RC13 and gapps. Rebooted and... CM7 booted and started up. Crashing randomly though. Trying MIUI next.
Click to expand...
Click to collapse
Yes! After reflashing bootloader everything seems to work. MIUI crashed. FroyoMod running ok. Trying HO!NO! next.
CM7 based ROMs don't seem to work well except for iceandfire. HO!NO! and CM7 crash frequently. But at least I can flash now..
Sent from my GT-I9100 using Tapatalk
Related
I've got CM7 RC10 Installed on my MM. I tried to upgrade it to RC11 but the phone stuck at boot loader so I rolled it back with nandroid. Anybody knows the reason or can help me?
erfannf2 said:
I've got CM7 RC10 Installed on my MM. I tried to upgrade it to RC11 but the phone stuck at boot loader so I rolled it back with nandroid. Anybody knows the reason or can help me?
Click to expand...
Click to collapse
Your phone shouldn't be stuck at bootloader when you're flashing a ROM. Go into recovery and wipe both caches and apply the update then reboot.
Sent from my Milestone using XDA Premium App
I just used RSD Lite v4.9 to flash GOT 2.2.1 on my phone. It works fine and rooted with GOT's OR. Then I wanted to try and apply the cm7 update and I have gone though all the steps listed in all the various guides but when I reboot the phone it will first go strait into recovery mode, stock, and another restart will get me stuck on the M. Does this mean my sbf is bad? I have tried different cm7 .zip files for the milestone with no luck.
Thanks in advance for any help/advice.
Have you made factory reset?
I wanted to flash CyanogenMod 7.1 on my Samsung Galaxy S.
I flashed before a Froyo Bootloader (because I had Firmware 2.3.3) on it, copied the CM7.1 Rom on internal storage and tried to flash through Recovery.
While updating it shows me the install process till:
Checking state of BML/MTD
then it interruptes the install process and restarts the phone. But then it just shows me the Samsung logo and nothing happens (=freeze).
No chance to start the phone, altough I restart it several times.
Then I can flash again with Odin to the starting state again. The files for that I found here (german):
http://www.giga.de/smartphones/samsung-galaxy-s-i9000/tipps/samsung-galaxy-s-cyanogenmod-7-flashen/
EZodin
EZbase-CSC-XXJV1.tar.md5
EZbase-PDA-XWJS3.tar.md5
EZbase-PHONE-XXJVE.tar.md5
Ezbase.pit
How can I flash CM7.1 now..?
Sometimes the cm7 rom will need flashed twice....you should be able to flash from any gingerbread rom also as cm7 was updated a while back to allow this. Try again, and if the phone starts bootlooping-pull the battery, replace and get into recovery-then reflash rom.
Unfortunately i cant enter recovery after unsuccessful flash. I have to use odin and flash back to old froyo... then i tried to reflash again to cm7.1 but it was always the same.
Thx anyway for ur answer...!
Hmmmmm ;(
Gesendet von meinem HTC Desire mit Tapatalk
no ideas? it is urgent.. ;(
it's really strange. it happened to me and I solved like this:
I removed the battery
volume up key + power button + home button
in recovery,I wipe everything and reflash of the rom
If recovery doesn't work, you need to reflash a stock rom, and a kernel with root and CWM
puuhh, at least another one who had this issue...
ok i understood that if i cant flash to cm7.1 then i have to chosse another rom, maybe just a stock rom.
but can anybody recommend a custom rom which will work? it is just a file system problem here, isnt it?
Done it!
Trying to flash the stable Rom didnt work.
Then i tried the nightly (181) and it took a while then it restarted. but when it was starting for the first time i got a loop while booting.
but this time i could enter the recovery (after stable installation it wasnt possible anymore) and i could reflash it (nightly again). and this time it worked!!! yeah finally after over 8 hours of work....
i hope i could help somebody who has got same issues
Glad you got it -and cm9 is now an easy upgrade from the latest nightly
Hi all, my name is Daniel.
I am using a motorola Milestone A853 for the past one year and never faced any issue while rooting or installing custom roms right upto cm10.
from last two months the milestone has not been working properly. It so happened i had installed CM 9.0.1d and everything worked fine. but once the battery died the phone did not boot up and was stuck on moto boot logo and kept restarting from there. I tried to go into open recovery (fufu minimod) using the X+power key and it goes into recovery but after loading recovery it did not display any options and the other text was red in color and it showed the error failed to load menu.init. I replaced the update.zip file along with the open recovery folder, but still nothing worked. I then tried another open recovery but still open recovery never loaded. Then i SBF'ed the device and went back to stock and was able to use my phone again. But then when i try to root the device again i am not able to root using vulnerable SBF as it does not install though RSDLite shows pass. Then i used superoneclick to root and that did the trick. But still open recovery never installed or load. Luckily androidiani recovery which displayed an error cannot mount but still created the menu and i was able to install custom OS but only cm 7.2.4e and not cm9 nor cm10. I cannot reboot the phone as the phone never starts up. only after clearing dalvik and wiping cache phone boots up. After a certain time now i still cannot install cm7.2.4e as it does not load and gets stuck on custom bootscreen, so i installed MIUI rom which works and starts up but i still can never reboot my phone.
Errors Seen E: cant mount /cache/recovery/command
Kindly help as the phone is just barely working.
Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.
Tried Everything
Erovia said:
Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.
Click to expand...
Click to collapse
Thank you for your reply. I have tried flashing stock 2.2 and still I cannot reboot the phone without wiping cache and using the reset factory option in stock recovery. Using superoneclick I can root it and install androidiani recovery but I cannot use cm10 or cm 9. after installing cm9 the phone just restarts after cm9 boot screen and after installing cm10 the phone shows the stock android boot screen. cm 7.2.4e installs as well as miui but if battery dies or if I have to restart the phone if it gets sluggish and slow then I cannot...everytime for the phone to boot I have to wipe dalvik and cache for custom roms and for stock roms I have to wipe cache and factory reset.
SO basically I am stuck...have tried changing the sd card, repartitioning the sd card, but nothing worked
Open recovery cannot be used only andoidiani works after popping up some errors.
Kindly help.
Hi all,
Hoping someone knows how to solve this issue.
I have been running the CM10.2 nightlies and downloading and flashing manually without too much issue.
I decided to try the app 'CyanogenROM Downloader' aka CM Downloader.
It worked fine to download the latest nightly but when I used a future which booths the phone into CWM and flashes automatically it just started looping.
It loads CWM and starts flashing but only gets a quarter of the way through before the screen flickers and the flash starts from the beginning.
If I reboot the phone by holding power and volume up until it buzzes 3 times it still loads directly into CWM and attempts to flash again but gets stuck in the same loop.
Do I have to flash back to a stock ROM now using flashtool to fix this?
I have the same issue on PAC nightlies. Try to flash an older or custom (with twrp) kernel to use recovery and flash the newest cm over it.
Gesendet von meinem C6603 mit Tapatalk 4
ozzy lion said:
Hi all,
Hoping someone knows how to solve this issue.
I have been running the CM10.2 nightlies and downloading and flashing manually without too much issue.
I decided to try the app 'CyanogenROM Downloader' aka CM Downloader.
It worked fine to download the latest nightly but when I used a future which booths the phone into CWM and flashes automatically it just started looping.
It loads CWM and starts flashing but only gets a quarter of the way through before the screen flickers and the flash starts from the beginning.
If I reboot the phone by holding power and volume up until it buzzes 3 times it still loads directly into CWM and attempts to flash again but gets stuck in the same loop.
Do I have to flash back to a stock ROM now using flashtool to fix this?
Click to expand...
Click to collapse
so do a factory reset from the recovery and wipe devack chache
khamees_xi said:
so do a factory reset from the recovery and wipe devack chache
Click to expand...
Click to collapse
Thanks for the reply.
The issue was it wouldn't let me into the recovery menu.
All good now. I left it off for an hour and it booted fine. I manually launched CWM and flashed the ROM and it worked fine. I'll let the CM Downloader app devs know of the issue.
I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?
monkeny said:
I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?
Click to expand...
Click to collapse
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off
BACARDILIMON said:
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off
Click to expand...
Click to collapse
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.
monkeny said:
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.
Click to expand...
Click to collapse
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit
monkeny said:
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit
Click to expand...
Click to collapse
Which rom u trying
few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.
nosympathy said:
few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.
Click to expand...
Click to collapse
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.
monkeny said:
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.
Click to expand...
Click to collapse
I have not messed with CM since I had the Note 2, which was until the Note 3 came out. Was a different carrier too. Generally the rule was flash CM then boot then reboot and flash GAPPS. I haven't looked but I would assume it is still the same.
Glad it worked