I have flashed the new CyanogenMod and the Cyanogen Recovery 1.4 and when I wipe everything and flash, it'll load up and I can use the phone 100% perfectly, but once I reboot my phone, or turn it off and on, it never goes past the green boot screen. Anyone have any solutions/reasons why it does that? It's with every single Cyanogen mod too, i've tried several of them.
Probably because you have a lot of apps?
If not, reflash it.
tmc_adio07 said:
I have flashed the new CyanogenMod and the Cyanogen Recovery 1.4 and when I wipe everything and flash, it'll load up and I can use the phone 100% perfectly, but once I reboot my phone, or turn it off and on, it never goes past the green boot screen. Anyone have any solutions/reasons why it does that? It's with every single Cyanogen mod too, i've tried several of them.
Click to expand...
Click to collapse
what do you actually flash and what is the actual process, you shouldnt have any issues after it boots up the first time, wipe everything and make an exterior partition meaning get rid of your cyanogen recovery 1.4 and get amon ra's latest... look in the dev section and read up on cyan's page on how to flash the rom
mt3g said:
what do you actually flash and what is the actual process, you shouldnt have any issues after it boots up the first time, wipe everything and make an exterior partition meaning get rid of your cyanogen recovery 1.4 and get amon ra's latest... look in the dev section and read up on cyan's page on how to flash the rom
Click to expand...
Click to collapse
Thanks for help man, right now I'm running dwang's rom 100% perfect w/ no issues at all. it can reboot and everything just fine. I'm just a little worried on going back and trying to flash cyanogens.
When I installed it, I first did the root process, downloading the .apk file and going through all that part smooth, then I downloaded and flashed the Cyanogen Recovery 1.4, and from there I downloaded the two files (DRC83_base and the latest cyan's rom, i forgot the version #) and applied update from SD, first doing DRC83 and right after doing the rom itself, without rebooting the phone. It loads up A-OK and I can installl the apps and go about my business, but once I need to restart my phone, it just never turns back on. I'm puzzled completely...I even did the whole unroot and reroot thing and STILL i'm not having any luck.
K I got confused in there some where did you flash a cyan rom at all in there I read that you flashed the drc83 zip file but sounds like you just flashed that and booted the phone lol... never tried that but.... any way it seems like you are doing everything correct onlything I could suggest is make sure you have the correct htc base image, and make sure you wipe and repair everything!!!!! and also try a differant download of cyanogen as you might have gotten a bad one or something I have never had any issues with a cyanogen rom except maybe a FC back on 4.0xx or something
兄弟，估计你刷成砖了。同情ing。。
Related
Hi Peeps,
I have searched in vain for a guide to changing from cm 4.2.15.1 to super d stable, but I cant seem to find one.
can someone advise me what to do so I dont brick my phone, and is it really worth moving to super d I hear its faster.
I am running cyanogen 4.2.15.1 H&E red I have the ra-dream 1.5.2 recovery, I have ext2 partition on sd card and I have a PVT board
Also I am worried about the ext2 partition because I have heard you have to remove it first and there is a certain way to do it??
Thanks in Advance
I was able to flash SuperD over Cyanogen without wiping or repartitioning. This is with an sdcard partitioned the usual way, fat32 and ext2.
The only issue I ran into was the battery meter - had to remove /data/system/batterystats.bin. Not sure of the exact procedure, so I did that from the recovery console and then booted up with a full charge.
Works great and really is a lot faster.
I would always wipe when moving from one rom to another. You never know what's could be hanging around.
I go thru this same process every time and never had problems:
1. Nandroid or Bart backup
2. Copy backup from SDcard to PC just in case SD card gets corrupted somehow
3. Wipe
4. Install new rom
5. Fix apk mismatch
6. Reboot
7. Check to see if Gapps are working, namely market, talk, sync, and of course google voice
nmw407 said:
I would always wipe when moving from one rom to another. You never know what's could be hanging around.
I go thru this same process every time and never had problems:
1. Nandroid or Bart backup
2. Copy backup from SDcard to PC just in case SD card gets corrupted somehow
3. Wipe
4. Install new rom
5. Fix apk mismatch
6. Reboot
7. Check to see if Gapps are working, namely market, talk, sync, and of course google voice
Click to expand...
Click to collapse
5. When you say "fix apk mismatch"....what do you mean?
7. I did the same thing (went from Cyanogen to SuperD) and I can boot into SuperD fine, but it won't connect to T-mobile's network and I am missing the Market. Any help?
shuboy00 said:
5. When you say "fix apk mismatch"....what do you mean?
Click to expand...
Click to collapse
It's an option in Amon_RA's recovery
shuboy00 said:
7. I did the same thing (went from Cyanogen to SuperD) and I can boot into SuperD fine, but it won't connect to T-mobile's network and I am missing the Market. Any help?
Click to expand...
Click to collapse
Wipe, Flash the DRC83_Base_Defrangled, the flash SuperD. Since both are legal, they need to pull the google apps from the base. And you would probably be fine without a wipe from SuperD to CM since they are similar donut builds. Wipes are recommended if you go from eclair to donut (and donut to eclair, elcair to sense, sense to dount.....). Cyanogen fixed it so you don't need to wipe as in the olden days...
mejorguille said:
It's an option in Amon_RA's recovery
Wipe, Flash the DRC83_Base_Defrangled, the flash SuperD. Since both are legal, they need to pull the google apps from the base. And you would probably be fine without a wipe from SuperD to CM since they are similar donut builds. Wipes are recommended if you go from eclair to donut (and donut to eclair, elcair to sense, sense to dount.....). Cyanogen fixed it so you don't need to wipe as in the olden days...
Click to expand...
Click to collapse
I see. So I am already running the DRC83_Base_Defrangled. Here is what I am doing:
I am currently running Cyanogen 4.1.99. My build number is DRC83. But my model number says "Android Dev Phone 1" <-- could that be why I don't have the Market in my roms?
So anyways this is what I do from Cyanogen 4.1.99: I backup, wipe, flash the DRC83, flash SuperD, then flash the 26I radio. Like I mentioned, rom boots up fine, just no market and no network access. Am I doing something wrong?
Absolutely no reason to flash the radio. The only thing that I can think of is that you have a bad download? Download this. Go to recovery, backup, flash the base, flash the rom. That should be all you have to do. Also, try CM 4.2.15.1 if SuperD isn't working for you. You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
mejorguille said:
You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
Click to expand...
Click to collapse
i believe he said that he is running latest cyan rom. try backing up your fat32 partition and reformat, that should do the trick
b0ricuaguerrero said:
i believe he said that he is running latest cyan rom. try backing up your fat32 partition and reformat, that should do the trick
Click to expand...
Click to collapse
I was referring to the poster above my post
mejorguille said:
Absolutely no reason to flash the radio. The only thing that I can think of is that you have a bad download? Download <removed>. Go to recovery, backup, flash the base, flash the rom. That should be all you have to do. Also, try CM 4.2.15.1 if SuperD isn't working for you. You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
Click to expand...
Click to collapse
K. Did what you said. Downloaded the base you provided. Flashed. Then flashed the SuperD rom. Booted up. First I see is "!Sorry - The process com.google.process.gapps has stopped unexpectedly. Please try again." Still no network and still no Market. Urgh. Frustrating!!
Also, I tried CM 4.2.15.1 after the SuperD didn't work and it hung on the G1 screen. IDK why 4.1.99 works but not 4.2.15.1.
i guess it didnt hung, you just have to wait a bit longer.
So every time I load a 2.2 ROM, My phone starts to wig out and so random things when I am trying to type or anything else. I am rooted and have the ota 2.x radio installed. I keep having to go back to a 2.1 ROM with hydra kernel and everything is stable. I do a factory reset every time but still no go. any ideas?
tlevash said:
So every time I load a 2.2 ROM, My phone starts to wig out and so random things when I am trying to type or anything else. I am rooted and have the ota 2.x radio installed. I keep having to go back to a 2.1 ROM with hydra kernel and everything is stable. I do a factory reset every time but still no go. any ideas?
Click to expand...
Click to collapse
a factory reset is not the same as a wipe from recovery menu afaik (if you mean a factory reset from bootloader (white screen))
boot into clockworkmod recovery and perform a wipe data/cache there, then flash it
some even experience problems with running the wipe from rom manager, so do it in the recovery menu instead
Thanks for the help. I tried what you said above and downloaded Sky raider 2.0 again. renamed it to update.zip then rebooted into clockwork. I did the wipe data/cache but sadly, I get the same results. I cant even get through the setup after the rom is installed. screen is unresponsive to my touch, but seems to have a mind of its own. I had best luck with CM 6 test 8 i downloaded from ROM manger, that ran for a day before starting to screw up.
So i tried to flash a rom like a normally do and i get stuck on the green screen.
I noticed now when flashing a rom is takes alot longer to flash then it usually did , i wiped pulled battery multiple times and still the same results. If i try to flash a froyo rom it will stay on the mytouch screen for a few secs and reboot to recovery mode on its own. every other rom just gets stuck and will not move. im limited to only recovery mode and Fastboot , are their any simple fixes that can be done and thanks in advance.
fabolous02000 said:
So i tried to flash a rom like a normally do and i get stuck on the green screen.
I noticed now when flashing a rom is takes alot longer to flash then it usually did , i wiped pulled battery multiple times and still the same results. If i try to flash a froyo rom it will stay on the mytouch screen for a few secs and reboot to recovery mode on its own. every other rom just gets stuck and will not move. im limited to only recovery mode and Fastboot , are their any simple fixes that can be done and thanks in advance.
Click to expand...
Click to collapse
Have you tried fixing apk uids? I've also heard you can use the bootloader to do a more thorough wipe.
If I were in your situation I would apply sappimg to unroot and start over.
Phateless said:
Have you tried fixing apk uids? I've also heard you can use the bootloader to do a more thorough wipe.
If I were in your situation I would apply sappimg to unroot and start over.
Click to expand...
Click to collapse
im fairly new so i only know how to flash roms . outside of that im pretty much clueless. I tried flashing a new radio & when it tells me to reboot to complete installation it says no more room or somthing like that. it does it really quick so i cant tell. Also how would i go about unrooting?
EDIT .. ok unrooted the phone and it seemed to have done the trick.
fabolous02000 said:
im fairly new so i only know how to flash roms . outside of that im pretty much clueless. I tried flashing a new radio & when it tells me to reboot to complete installation it says no more room or somthing like that. it does it really quick so i cant tell. Also how would i go about unrooting?
EDIT .. ok unrooted the phone and it seemed to have done the trick.
Click to expand...
Click to collapse
Glad you're still operational. Now you can retrace your steps and figure out where you went wrong. I also had to unroot and go back to Cupcake before I successfully completed my first rooting.
If you're just flashing ROMs, I would stay away from updating the radio unless the developer specifically says you should.
I tried to use SuperOneClick to root my phone and it seemed to work. The program came back saying I successfully rooted my phone.
I then went to ClockworkMod to install cyanogen and clicked on the appropriate boxes to begin the download process for cyanogen 6.0 stable mod and ran it.
My phone rebooted and started to run some scripts.
Now, the phone just reboots to the green mytouch screen and continues to loop like that and I have no idea what to do.
I can get into fastboot on the mt3g and when I do, my pc makes the sound that states that the phone is connected but when I try to get into the mytouch, using adb, my pc cant access it but when I plug up my G2, I can see the serial number and such showing that it is connected.
I tried to follow the fastboot driver installation page but it didn't seem to work.
Bottom line is I would really enjoy a functional MT3G in either the regular form or cyanogen (which is why im in this predicament now )
For the the record,
I was running 1.6 but got the OTA update for 2.2 before I ended up blowing up my phone.
Thanks for reading this and any aid would be greatly appreciated.
UPDATED:
I found something called SAPPIMG.NBH that allowed me load Android 1.5 onto my phone. I now am back to a functioning device but still, I am super stuck on trying to get cyanogen onto my device. Any helpful hints? From what you read above, did I miss something?
Thanks again.
... Sadness... I have been bashing my face against this mt3g and haven't been able to get cyanogenmod on this phone for the life of me. I have tried all of the builds from 5.08 up to RC1 of 6.10 and I just get the infinite loop at the cyanogen boot up screen. I even tried to flash 2.23.XXXX radio to see if it gets past the boot loop and it does not. Anybody have any insights into my issue?
Thanks,
You must go into recovery mode(boot up by holding down home + power). That will get you to Clockworkmod recovery(I am assuming since you said you downloaded using Clockwork app). From there you need to wipe cache, and anything else you can wipe. Then try installing Cyanogenmod after that. Without wiping the there is not enough space to install and it causes a bootloop.
I'm in the same boat, I'm stuck in a boot loop and I cannot get any ROM to fully load in. I'm using clockwork recovery Radio 2.22 32B.
I tried wiping everything but that still doesnt seem to work. I noticed when I try wiping Davlik cache I dont see any message on the bottom. I thought it would normally give me some sort of message stating that it is wiping davlik or something so maybe it isnt actually wiping it?
Is there some other way to make sure davlik is wiped? Or something else I can do. I just want the phone to boot up at this point. I can get into recovery but thats it.
I know I shouldve done a backup but dumb me was such in a rush I completely forgot, I know im a idiot...
Het I found that same .img file and also reverted back to 1.5 then just went up to 2.2 not sure what was wrong but Rom I put on just went into a boot loop. Maybe it was clockwork recovery.
Sent from my ADR6300 using XDA App
the padawan becomes the master... Sort of...
The problem is that you cannot go directly to 2.2 from 1.5. You have to do the incremental upgrades that take you from 1.5 to 1.6 then 1.6 to 2.2
Everytime i tell it too boot into recovery it just shows the little android guy with a triangle and exclamation and then reboots. I've installed bootstrap and run clockwork recovery. What am i doing wrong? last time i did this and was able to manually go into recovery but when i flashed a rom i just got stuck at motorola bootscreen and had to use sbf. Please enlighten me someone.
Ok.. i tried skipping clockwork and just booted into recovery through bootstrap.. Works. I try and flash a rom and the orange bar comes up and says it's installing. The bar never fully goes across but it says the installation is complete. When i try and reboot to try the rom i get stuck at the boot screen. Any ideas what is going on?
boredmug said:
Ok.. i tried skipping clockwork and just booted into recovery through bootstrap.. Works. I try and flash a rom and the orange bar comes up and says it's installing. The bar never fully goes across but it says the installation is complete. When i try and reboot to try the rom i get stuck at the boot screen. Any ideas what is going on?
Click to expand...
Click to collapse
are you using 2.2? what ROM? you need to run the bootstrap once for it to work, and it will say clockworkmod installed is version 2.5.0.7 in ROMManager thats the bootstrapped version of clockwork mod.
then download the ROM, and don't touch anything after you hit the ok button on the screen that asks to backup current ROM and wipe user data. just let it work.
The system info says 2.1update1. I did as you described. I just used bootstrap to boot to recovery and tried flashing a rom and it does the same thing. Just sits at the motorola bootscreen. I'm gunna try my nandroid recovery to go back to the rooted stock rom.. I really don't know what to do from here though because neither way is working for me.
Also, my clockworkMod Recovery is v2.5.0.6 not .7. Maybe this is the issue? when i used rom recovery it said i had the most recent version. I'm Nandroiding right now which seems to be working.
boredmug said:
The system info says 2.1update1. I did as you described. I just used bootstrap to boot to recovery and tried flashing a rom and it does the same thing. Just sits at the motorola bootscreen. I'm gunna try my nandroid recovery to go back to the rooted stock rom.. I really don't know what to do from here though because neither way is working for me.
Also, my clockworkMod Recovery is v2.5.0.6 not .7. Maybe this is the issue? when i used rom recovery it said i had the most recent version. I'm Nandroiding right now which seems to be working.
Click to expand...
Click to collapse
you should update to version 2.2
check http://rootzwiki.com/ it has the files you'll need
ok. Thanks. Maybe this is the problem? I'm trying to flash a 2.2 rom and currently have 2.1 on my phone? So i've already done sbf back to 2.1 once last night. I'm assuming this procedure is pretty much the same. I'm guessing i will have to reroot my phone. Can i use the same method as 2.1 or is there another method for the droid x with 2.2? Thanks for the help!
boredmug said:
ok. Thanks. Maybe this is the problem? I'm trying to flash a 2.2 rom and currently have 2.1 on my phone? So i've already done sbf back to 2.1 once last night. I'm assuming this procedure is pretty much the same. I'm guessing i will have to reroot my phone. Can i use the same method as 2.1 or is there another method for the droid x with 2.2? Thanks for the help!
Click to expand...
Click to collapse
just check the website i posted, it has guides for everything you need
well.. Now i have 2.2 on my phone but no root. adb can't find my phone.. WTF
Thanks for pointing me in the right direction. Was finally able to get it all working. Now I have a working 2.2 custom Rom and can proceed with flashing this thing to cricket. Kinda sucks because I'm doing all this for a friend and using this phone I've kinda come to the conclusion that its a better made phone than my evo. Colors look better on the lcd, camera takes better pictures and the aluminum case is certainly nice too. Only drawback I see is the dev. Much more development for the evo, but then again it is an older phone.
boredmug said:
Thanks for pointing me in the right direction. Was finally able to get it all working. Now I have a working 2.2 custom Rom and can proceed with flashing this thing to cricket. Kinda sucks because I'm doing all this for a friend and using this phone I've kinda come to the conclusion that its a better made phone than my evo. Colors look better on the lcd, camera takes better pictures and the aluminum case is certainly nice too. Only drawback I see is the dev. Much more development for the evo, but then again it is an older phone.
Click to expand...
Click to collapse
I like my DX and it does have a few advantages over the EVO (e.g. battery life and build quality). However, I would gladly trade it for an EVO, since that device has 4G access, a front camera, cyanogenmod support, more accessible bootloader, etc.