Related
I am completely stuck as of now, tried everything! No idea what else I could try. I basically can install any rom just fine, Dwang 1.12 works fine, Cyanogen Mod 4.2.5 works fine too. I am not able to install the latest ones by either though, what could be the issue?
I have rooted MyTouch 3g.
What do you have on your phone right now, and what methods have you tried? What have your steps been?
I have 2 MyTouch 3g phones actually, one is my roomie's and I can install dwang's 1.13 just fine on it, weird .
For dwangs:
Backup
Wipe
Install
Reboot and get stuck on the MT3G boot screen
For Cyanogens:
Backup
Wipe
Install rooted Base
Install Cyanogens
Reboot and get stuck at MT3G boot screen.
It is my understanding that Dwang's latest is based off Cyanogen's 4.2.6, thus I can see why both of them won't work. But why?
I am on Cyanogen's 1.4 recovery tools, I've had Amon RA 1.3.2, as well as RA 1.4.
HBOOT: 1.33.0006 (SAPP30000)
Radio: 2.22.19.26I
anybody?
afive720 said:
anybody?
Click to expand...
Click to collapse
Sorry i can't help, but just to add on... I'm having almost the same issue, but with a G1. Although i can install any of Dwang's versions, including 1.13, but as far as cyanogen goes, 4.2.5 works great, but 4.2.6 and 4.2.7.1 i get stuck at the g1 logo when trying to flash. If anyone can help my set up is
SPL 1.33.0006
Radio 2.22.19.26I
Amon_RA recovery-RA-dream-v1.2.3.img
have you both done thorough wipes through the console?
Are you flashing the signed developer zip file before trying to flash the rom itself?
The process should be...
Wipe
flash signed dream developer zip
NO REBOOT
flash the rom zip on top of the previous zip
Reboot
you can find links to the signed dream dev zip here
http://forum.xda-developers.com/showthread.php?t=593626
Since the first guy has a mt3g, you'll need to find that primary file. The dream one wont do it for you.
check cyanogen's wiki over at cyanogenmod.com
I've had a similar problem. I follow all the instructions correctly, but Dwang's 1.13 works and CM doesn't. For CM I did everything, wiped, flashed 1.6, flashed CM, rebooted, and then it would go back into Recovery for some reason. I'd reboot again and it'd hang on the Rogers screen for me. I couldn't fix it so I wiped, flashed Dwang's, and his worked fine. No clue why CM wouldn't work for me since that's the ROM I actually wanted.
DiSTroy3d said:
For CM I did everything, wiped, flashed 1.6, flashed CM, rebooted, and then it would go back into Recovery for some reason. I'd reboot again and it'd hang on the Rogers screen for me.
Click to expand...
Click to collapse
Yes the first reboot writes the radio files. The second boot writes the cache.
You will have to hit reboot when the cache writing stops. (reboot will become an option in the recovery)
This is the first boot of a brand new OS as far as your phone is concerned and it will take a few minutes. The boot process will take a while. The phone is writing and moving the entire android OS.
I have had mine hang for about 10 minutes before. Sometimes it is 5 minutes.
Mine normally hangs for about 2-5 in the G1 boot screen and another 3-5 in the cyanogen logo.
Ok, I'm guessing I misunderstood something. I'm a "noob" so bear with me...
here's what I did.
I was running cm v 4.2.9.1 and decided to try and upgrade to the latest version. I wiped and reflashed and got 4.2.14.1 running, but I felt it was slow (the reason I didnt use any other new version), so I came here looking to see any new roms.
I decided KiNgxKxlicK AOSP 2.1 rom looked cool, so I downloaded it and flashed it (yes I wiped first). I'm guessing this is where it went wrong. The rom took 30 mins to finally boot to home (longest ever) but the sweet nexus screen made it easier to bear. I DID NOT do anything with an spl or any radio (that part still kinda confuses me to be honest). I'm guessing this is why I am in the predicament that I am.
The KiNgxKxlicK AOSP 2.1 rom loads fine, but was VERY slow. I decided I'd just go back to cm v 4.2.9.1. I went to wipe and reflash, but the G1 screen never disappeared. I let it load for about 30 minutes and decided that was a bit ridiculous before removing the battery (mind you, it never got past the T Mobile G1 screen). I was, however, able to reflash KiNgxKxlicK AOSP 2.1 rom and run it. This is all I am able to do. When trying to reflash cyonagen it just hangs on the G1 screen.
I'm a noob so I don't know what went wrong or what I missed.
Can someone PLEASE help me out here and tell me what I need to do to fix this. Thanks
Additional Notes:
Can't get to settings running KiNgxKxlicK AOSP 2.1 AT ALL, and a lot of programs Force Close on the rom.
Thanks for any help/input you guys can provide.
Thanks
Do you have Amon Ra recovery?
No I do not believe so, as I am not exactly sure what that is?
UPDATE: I should also note I checked my SPL and Radio, both were very old (as I realized I followed an OLD guide when I rooted my phone)
I upgraded to the latest radio and SPL and still have the same problem...except King's rom doesn't force close when I go to "settings".....thats about the only difference (still slow/laggy, lots of programs still FC)
When you boot into recovery (holding home+power) it should tell you what recovery image you are using. (i.e. mine says v1.5.2 down at the bottom of the screen) I ran into a similar issue when I attempted to jump between roms without taking all the appropriate steps; all I did was reformat my sd card, wipe the phone, and reflashed my rom and it worked great after that.
I tried reformatting my sd card, even re-partitioned it and I'm still having the same problems:
CM wont get past g1 screen after flash, King's rom still pretty slow....
What do you gys recommend I do next? This is getting really frustrating
1st: Check if youre Formatting is correct
2nd: Wipe EVERYTHING
3rd: Re-Format
4th: Try downloading the ROM again. It could be an issue with the ROM's
5th: Check you have proper radio and SPL (1.33.2005 and 26I)
6th: Pray
Try them all hope one of them works for you dude.
why is it that that 99% of newbs are on cyanogen
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Here's what i suggest you do:
1> Download Amon_RA's recovery from here
here is a link to his thread
2> Transfer the file you just downloaded to the root of your sd
use this code to mount your sdcard from recovery console itself if needed
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
3>Disconnect usb and reboot to recovery (keep home pressed while powering on) or just type
reboot recovery if you are already in recovery console
4> Flash Amon's recovery:
Code:
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
when complete, reboot to recovery again
5>Partion your sd using amon's recovery (All data on SD will be lost so backup if needed)
[Alt+P] then [Alt+0] or scroll down using the trackball or the volume keys
follow the prompts, set your swap-size to 96 MB (use the vol keys) and 512 MB ext2. when done use the back button to go back and reboot
The above step will give you the partitions required to run any rom. Please make sure you meet the radio and SPL requirements before flashing a rom.
6>Transfer the latest CyanogenMod rom to your SD and flash it.
I would suggest that you try bbuchacher's SuperD rom (it requires Haykuro's Danger SPL)
make sure you flash the radio first and then the SPL if you dont already have it
P.S. When anyone says full wipe, they mean doing a factory reset, wiping your ext partition and wiping the dalvik-cache. These are the first 3 options in Amon_RA's recovery's wipe menu
what i would do....
make sure you flash the HTC recovery files first before you flash the CM rom
go for the defanged version of HTC
so...(once u have amon ra's latest recovery installed)
wipe everything
flash htc / defanged (DO NOT REBOOT!!!)
flash cm latest rom
ALLOW IT TO LOAD FULLY
reboot (personal preference)
create a nandroid backup for future **** ups
enjoy ur rom!!
j.
airmcnair06 said:
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Click to expand...
Click to collapse
1: Go to recovery console and type parted. A list will show up with your fat32,ext2/3/4,linux-swap settings.
2: Yes it does but you can never be too sure.
4: ok
thanx guys I followed the instructions MrBurrito and cqms13 gave and am now running the Super D rom just fine.
Thanks again!
very quick question..
did you wipe dalvik-cache?
Firerat said:
very quick question..
did you wipe dalvik-cache?
Click to expand...
Click to collapse
After installing the RA recovery, yes. I was running CM Recovery though when I began this thread, which is why I was not able to wipe dalvik
I rooted my Sprint Hero and have been able to successfully flash and operate Fresh 2.3.3 but CANNOT figure out how to get CM6 to boot. I wiped prior to attempting the flash but all that happens is a lockup on the HTC boot screen. I have attempted to flash it twice, and waited about 20 minutes the first time and 45 the second time with no progress, eventually having to pull the battery and reboot in recovery mode. I was only able to wipe the data but when I tried to wipe the delvik cache, it told me I needed to do it via ADB. I tried to partition my SD card but it ended up cutting the available memory in half, and erasing my backup, and I had to use an external card reader to reload Fresh so that I could actually use my phone (which IS fully functional now). Should I be wiping EVERYTHING on the phone (including the battery and rotate info)? What am I missing?
I have heard nothing but great things about CM6 and am very disappointed that I cannot get it to work. Can anyone help?
Sprint HTC Hero
Firmware version: 2.1-update 1
Software version: 2.27.651.6
try wiping your ext partition
I wiped everything that the recovery menu would allow me to prior to the first attempt at flashing and it wouldn't load. I pulled the battery and rebooted to the recovery menu then partitioned the SD card, wiped just prior to the second attempt at re-flashing, re-flashed and it still locked up at the HTC screen.
I like to think I'm pretty computer savvy but I just can't figure this out. Why would Fresh 2.3.3 load without a hitch, but CM6 not?
make sure you recovery is 1.6 or 1.7 to be able to wipe dalvik i had same prob
My recommendation would be flashing the recovery in this thread here.
This the recovery I used while I was using Fresh 2.3.3, and when I upgraded to the CM6 Nigtlies.
I say Flash The Custon Amon_RA 1.7 in Darchdroid thread->NANDROID!!!!->Wipe Data->Dalvik->sd-ext(if using apps2sd)->Flash RC1 or Latest Nightly (your choice)->Flash Optionally Google Apps->Optionally Flash Uncapped Kernel and/or Battery Tweak(I use the uncapped Kernel, and not the battery tweak, and I get 24 hours+ with average use)
Try that out.
Funny, im running into the same problem after flashing the wrong blackmod... wiped, reflashed cm and now it wont go past the htc white boot screen
It did boot before though which is odd
Edit: Wiped, wiped dalvik and ext part, flashed rom and gapps, working just fine now... will flash batt tweak, bm and round clock in a min, hopefully it doesn't break it
jUgGsY,
Thank you for being so thorough in your response, it all makes sense! My only issue now is trying to re-flash the recovery image. I downloaded the RA-Darchstar image but I'm not sure if it's correctly being pushed to the SD card (all I get is a long list of ADB commands, no particular confirmation) and when I try to flash the image, I get a message telling me that it can't find the partition. What does this mean? Is the recovery image really that important to the updated ROM? How come there is no specific recovery image recommended on the CM forum?
EDIT: I found directions from the Unlockr on the youtubes. Gonna give it a try and see how it goes after that...
So it was decadence#7 kernel that was screwing up my boot... removed it and using stock darchstar
Ok... this is getting ridiculous.
*I flashed the RA-Darchstar (1.7) recovery image
*NANDROIDed
*Wiped data, cache, Dalvik and sd-ext
*Flashed RC1
*Flashed the google addon
*Rebooted
Been waiting for the damn thing to boot for almost 30 minutes now, still stuck on the HTC screen. Can anyone tell me what is going on?
jordanjackthomas said:
Ok... this is getting ridiculous.
*I flashed the RA-Darchstar (1.7) recovery image
*NANDROIDed
*Wiped data, cache, Dalvik and sd-ext
*Flashed RC1
*Flashed the google addon
*Rebooted
Been waiting for the damn thing to boot for almost 30 minutes now, still stuck on the HTC screen. Can anyone tell me what is going on?
Click to expand...
Click to collapse
Are you flashing RC1 or one of the nightly ones? I had the same issue with RC1. I could not get it to boot past the HTC screen. However, the nightly ones flash just fine. I would suggest flashing a nightly. I now see you said RC1, lol. Try the latest nightly.
It looks like I will have to go with a nightly. Are there any that you recommend? The most recent or one from a few nights back?
jordanjackthomas said:
It looks like I will have to go with a nightly. Are there any that you recommend? The most recent or one from a few nights back?
Click to expand...
Click to collapse
The latest one seem to be very good. 8/22 but make sure you download the latest google apps for it also.
For some reason, I couldn't get any variation of CM to load on my phone (CM6 or the Vanilla variant). I went with Darch's LegendROM and it is excellent - much better than stock 2.1 for the Hero! Really fast and has some neat extra features. I noticed, though, that my reception is kind of bad now and I usually have excellent coverage at my house. I already downloaded the most up-to-date Sprint radio (2.42.01.04.27) but was just curious: do I need to wipe and re-flash the image FIRST or can I just flash the radio image over the already installed ROM?
AND: Please excuse my inexperience with all of this, but I'm about to ask two already answered questions: I'm not looking for long-winded answers but if someone could point me to a relevant thread, it would be GREATLY appreciated.
1) I keep getting a "process com.google.android.googleapps has stopped working" error when I try to sync with my gmail account. How do get this to work?
2) I remember reading that there was a known MMS issue with Darch's DroidROM, not any issue with the LegendRom, but I just received a "generic network failure" message when my wife tried to send me picturemail. Is there a workaround for this?
Thank you all for your patience!
hopefully this is where this goes. >_> if not, please guide me to where i need to be.
OK. so what is going on:
-right now i am using a STOCK version of 2.2.1 FRG83D, that i rooted with superoneclick.
-i used rom manager to flash RA recovery, because somehow i can't flash roms with clockwork anymore. errors out every time, regardless of version
-i can flash new custom roms using RA, etc etc, but cannot flash roms and restore to old backups
-if i try to USE a custom installed rom, no matter which it is (i have tried a few gingerbread, nxsense, and some 2.2.1 roms), they will ALWAYS reboot after using them for a few seconds, regardless of what i am doing (setting up, using market, or just letting it sit and do nothing)
what i have done before this happened:
-i was using nxsense perfectly fine. great rom, ran great.
-updated rom manager, and clockwork recovery
-tried to flash a new boot animation, but noticed that the new clockwork won't install older .zips that use assert-scripts(?)
-tried to downgrade clockwork, and it randomly restarted the phone during the downgrade
-wanted to try gingerbread, so i flashed the new(er) hboot 0.35.0017 even though i think i had it already, and installed the rom succesfully.
-the rom wouldn't let me download from the market, as it restarted when i tried to download anything.
-i thought the problem was with the new hboot, so i went through a tutorial to revert it back to 0.33.0012 and went back to eclair, so i updated up to frg83d (and obviously got the 0.35.0017 hboot back through updating) and rooted.
the rom i am using now (stock with root) runs fine. haven't really found any real problems.
i just have NO clue why i can't use custom roms. i would absolutely LOVE if someone could help me on this.
I also had similar problem two days ago. I upgraded my clockworkmod recovery to 3.0.0.5 and tried to flash MM CM7 v14. All the problem began. I cannot restore any custom roms except the stock froyo and MM CM7 restarts like crazy whenever I try to install any apps from the market. After that, I also tried RA recovery. No luck. Luckily, I finally find out that the latest recovery messes up my ext3 partition. So, I backup and format my SD card, recreate ext3 partition, restore the SD card, downgrade clockworkmod to 2.5.1.4, wipe everything, fix permission and install MM CM7. It finally works. Hope this help.
PS: as long as I downgrade the clockworkmod, I can restore any custom roms.
Never flash now you will brick it soon
Sent from my Nexus One using XDA App
Latest ClockworkMod was known to have some problem, perhaps.
Use Amon_Ra's, if you want to be sure, and wipe everything (data & dalvik-cache) when going from ROM to ROM. Use Titanium Backup for restoring the apps.
ricky9237 said:
I also had similar problem two days ago. I upgraded my clockworkmod recovery to 3.0.0.5 and tried to flash MM CM7 v14. All the problem began. I cannot restore any custom roms except the stock froyo and MM CM7 restarts like crazy whenever I try to install any apps from the market. After that, I also tried RA recovery. No luck. Luckily, I finally find out that the latest recovery messes up my ext3 partition. So, I backup and format my SD card, recreate ext3 partition, restore the SD card, downgrade clockworkmod to 2.5.1.4, wipe everything, fix permission and install MM CM7. It finally works. Hope this help.
PS: as long as I downgrade the clockworkmod, I can restore any custom roms.
Click to expand...
Click to collapse
omfg thank you so much!!! <3 worked like a charm
kevvibot said:
omfg thank you so much!!! <3 worked like a charm
Click to expand...
Click to collapse
You're welcome. Glad to know my experience can help solving yours too.
Definitely a problem with Clockwork 3.0.0.5! I just went through madness trying to figure out WTF was up as well. The only fix was to completely format and re-partition my card then use RA instead of CW, works great now and I don't know if I will use CW again! What a pain...kinda regret having paid for ROM Manager now after this latest fiasco.
Greetings fellowmen!!
Recently i thought of rooting my nexus 1. So i did some research and found out that the easiest way to do it was by unlocking the bootloader installing a custom recovery (I did Amon Ra) and then wiping the data\factory settings and flashing the cm 7.1 zip. So i did all the above and there you go....I had an n1 running cm 7.1 smoothly but then after a few hours it starts to piss me of. The problem is that whenever i lock the homescreen with the power button and wake it up again it just displays the main homescreen and does nothing i cannot navigate to the left or right homescreen cannot open app drawer in short it just hung up there doing nothing. I had to take out the battery atleast 15 times. I rebooted my device and it kept on giving me the same problem.
So then i reflashed cm 7.1 by wiping the data and factory settings and installing it again. But still it gave me the same problem. So then i thought of flashing 7.0.3 version instead and surprisingly that works like a charm. So is it the mod thats buggy or is it my phone.
One more question. I have the stock 2.3.4 gingerbread rom which i got from here!!
Code:
http://forum.xda-developers.com/showthread.php?t=1061648
This one in particular-
GRK39F OTA (stock vanilla - odexed, unrooted):
MD5: 35C8B4B9FD22DD4CA19C5D026E74411D
So to install this rom do i have to install it the same way i did cm by wiping data/factory settings and then installing flash from zip or is there any other way to do it ?
Thanks in advance for taking out valuable time and reading my long problem!!
I am running the latest version of CM 7.1 that was released within the last week or so without any issues. Got it from here. http://download.cyanogenmod.com/?type=stable&device=passion
Before that I was running the RC for 7.1. One thing to try it wiping multiple times before flashing. I assume you are running Amon RA 2.2.1, which is the latest. I have never had a problem with that recovery, however I flashed my ROM with this recovery. So far I think I like it better than Clockwork and Amon.
http://forum.xda-developers.com/showthread.php?t=1291970
As for installing other ROMs yes you do flash them the same way you flashed CM.
So are you saying that it was the recovery that was causing the problem?
Yes I am using the latest Amon Ra 2.2.1 version.
I also got the rom from that link.
And can you explain whats the difference between all these recoveries?
Thanks for replying!
I am not saying it is the recovery, I highly doubt that is the problem. I was just comparing differences. There does not seem to be much difference in the recoveries for what you are trying to do. The recovery I am running is a fairly new one that I just wanted to test out. I do think I like it better than the others.
First thing I would do is wipe 3, 4 or 5 times before flashing. I have had rare occasions where a single wipe would not do it for me. Also have you verified the Checksum of the CM download? Does recovery say it installed successfully? I have also had error installing a ROM in recovery but then had the phone still load the ROM.
Yes i did check the md5 checksums and they match perfectly. Though i did wipe it out only one time so maybe that could be the problem. I think i should get clockworkmod and wipe it through that and then flash cm 7.1. Amon RA doesnt really give us the option of wiping the system partition. right?
Correct Amon Ra does not have an option to format system partition. It's recommend you also wipe system when coming from a different ROM.
Try this file by temasek's, format-signed.zip
http://www.mediafire.com/?8vbd13b440coxx6
just flash it in recovery and it will clean everything, now you can flash CM7.1 again
Are you sure you can't wipe the system with Amon? I remember having that option, but it's been several months since I have used that recovery. Kind of makes me want to flash it to find out.
Before flashing a different ROM I always wipe system, cache and dalvik cache. It is definitely important to wipe the system before flashing a new ROM. I'm sure that is where your problem lies.
No, ClockworkMod has it, but Amon_RA doesn't. Supposedly it is in the works for the next version, but that was a long time ago when I heard that (probably back when v3 for clockworkmod came out).
I did a nandroid backup and flashed the format zip file and then flashed cm 7.1 and its giving me the same problem!!
I had to restore and go back to 7.0.3
Why is this happening
Edit: I also wiped the dalvik cache and factory reset it also but still it just freezes!!
Any advise?
Have you tried downloading the file again maybe form another location I doubt this is the problem but sometimes it's something you don't expect.
You could try from here http://wiki.cyanogenmod.com/index.php?title=Latest_Version
But how does it matter I checked the md5 checksum and it matches!!
Why not stay on CM7.0.3 theres not much difference between the 2
if you dont want to i suggest to try to flash Clockwork recovery and do a full wipe then reflash CM7.1
But still I want to see how 7.1 is!
The main point here is to upgrade and not taking the alternative of staying at the older version!
Please guys any help would be appreciated!!
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
thealphamale05 said:
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
Click to expand...
Click to collapse
Make no different if you use amon Ra or CWM. I would definitely stay away from cwm 3.x or higher if you're using sd-ext
Looks like Ill have to stay with 7.0.3 there doesnt seem to be a solution!!