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.
Ok apparently in my futile attempts to OC the Pure Hero 1.0 Rom I've totaly got something hosed up. The phone works but features that others have working flake out on me. Is there a way to wipe fully the whole thing and reset back to the rooted 2.1 Rom as we did before the Recovery image.
If it is as simple as just flashing the original developers Rom please don't flame me..I did search.
I do a factory wipe then Dalvik Wipe then Ext Partition wipe before flashing an image.
I currently can't get Wifi to work on Punk.Kaos Rom nor on the Pure Hero (I think that was an issues though)..
Thanks for all the hard work you guys do....
copy a rom you want to use to your sdcard. then go into recovery, wipe the phone, then flash zip from sdcard. done!
That is what I have been doing and some of the settings are still flaking out and the Kaos rom is V15 he fixed wifi in v2. I can't even get Jamezelle's sensable rom to even flash with out a boot loop at animation.
Thanks for the help.
No nandroid backup?? I know before flashing the first Rom on the phone I made a nandroid back up on my wifes and pretty much do everytime before flashing a new rom. These things are priceless
Follow the the original root procedure.
*Suggestion*, when phone boots.... open setcpu and adjust the CPU OC setting.... maybe...
id say go to the downgrade to 1.5 from 2.1 root thread and do that and then re upgrade and reinstall the recovery image.
I agree with doing a full downgrade to 1.5 and rooting again. I had problems similar to yours and this solved the problem. Good luck.
-------------------------------------
Sent via the XDA Tapatalk App
Thanks I just wanted to confirm that should be the process of going to 1.5 thne to 2.1 and restoring the Recovery. One last question and then a Mod can close this thread. The Rom Manager in the Market will that work for us or is that a Droid only thing?
Thanks for the great advice.
Forgot to answer the nandroid backup yes did it before every new flash of a Rom they would come back weird also. Secondly how do I get my SD card back to full Fat32 and not the ext+Fat partition for A2SD mode? I never could get the A2SD to work fully.
Hi guys,
I've tried using unrevoked 3.3 on my wildfire, with android 2.1, didn't work - so I tried 3.2 and I got the ClockworkMod Recovery v2.5.0.1 on there, I can boot into that now,
But still not knowing how to root it,
Can someone give me some advice from here, I get the "Internal error" message and can't go any further, but I assume you can manually do it, since I've got the clockworkmod recovery on there,
Toby =)
Soulquarian33 said:
Hi guys,
I've tried using unrevoked 3.3 on my wildfire, with android 2.1, didn't work - so I tried 3.2 and I got the ClockworkMod Recovery v2.5.0.1 on there, I can boot into that now,
But still not knowing how to root it,
Can someone give me some advice from here, I get the "Internal error" message and can't go any further, but I assume you can manually do it, since I've got the clockworkmod recovery on there,
Toby =)
Click to expand...
Click to collapse
if you have clockworkmod recovery then that means you rooted it, just put a custom rom onto your sd card, boot into recovery and install zip from sd card. do a nandroid backup of your rom first.
When I try using Titanium Backup, I get a failed message...
Sent from my HTC Wildfire using XDA App
Okay, I installed busy box and it says it rooted, does the clockworkmod matter what version you have?
Sent from my HTC Wildfire using XDA App
Soulquarian33 said:
Okay, I installed busy box and it says it rooted, does the clockworkmod matter what version you have?
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Nope, you should be fine.
Thank you, I'll let you know how it goes, is Wildpuzzle rom trustworthy? It's been around for awhile right? =)
Yeah wildpuzzle is good, I used to use it.
I had abit of a freak out, I wiped my phone then couldn't load any custom rom =( But now its loading, hoping it works...
I don't know if the rom is loading or not, the screen with the android symbol coming out of the box showed up now and white backgroud with the "HTC quietly brilliant" animation seems to be sitting there forever,
I installed the SUnAaBh v1.1** rom from sc card,
Does this seem right?
First boot takes 10 to 15 min.
You should have done a nandroid backup of your stock rom first, oh well.
If it doesn't boot, do a full wipe, wipe data/factory reset and wipe cache in recovery and flash again.
After like 2 or 3 minutes, the screen goes black then the HTC logo screen comes back on and loads again, makes me think its in a loop and no installed right =\
Do a full wipe and try flash again. If it doesn't work, try a different rom.
Yeah, I did a back up with nandroid then moved the files to my computer incase, they was in a folder called orangeworkmod folder?,
Wipe cache?
Soulquarian33 said:
Yeah, I did a back up with nandroid then moved the files to my computer incase, they was in a folder called orangeworkmod folder?,
Wipe cache?
Click to expand...
Click to collapse
Yes, you should wipe data and cache before installing a new rom. They are all there in recovery.
Okay, yeah - its all good, was just taking time, does wildpuzzle rom have overclocking feature, or is that a application?
hey guys im having a big and really annoying problem i cant fix hopin in can get some help...
i have the iced glacier 1.1.6 with clockwork 3.0.0.5(rom managerv3.0.1.0). i want to make a backup nanDroid.. so i do and it completes and everythings fine... until i to the restoring part. after it "successfully" restores(yes, i did wipe cache, wipe dalvik, and even wiped eveything in everyorder possible. i restart my phone and it freezes on the mytouch 4g bootup logo. everytime. no matter what. it does let me reinstall the fresh ice glacier rom...
note: when i wipe the dalvik, its almost instantaneous wipe, like it doesnt do it?
there is an error about e:/ not mounted (sd-ext) or something close to that. but still says it worked.
things ive tried...
renaming the file.
moved the file.
reformatted SD.
wipe data...etc twice in a row to make sure it wiped.
any ideas?
You have to revert back to older Recovery 2.5.1.2 or you can install the new 3.0.0.6 as normal CWM won't able to handle it. This same issue has been covered many times. Read the quote below to better understand if you still have problem well then post back ill help.
jggimi said:
you are using the wrong version of Recovery to install the new kernel. I'm guessing #2, because it's very common for people to assume a higher number is better, and use CWM Recovery 3.0.0.5 with Froyo-based ROMs and hose things up really well.
Restoration options, if you are using CWM 3.0.0.5:
a) Restore from the Nandroid backup you made before overlaying your kernel. Oh, yeah, you can't, you didn't make one, otherwise you'd have already done that and wouldn't have posted....
b) Flash the appropriate CWM Recovery (2.5.1.2 for Froyo-based ROMs) using adb from your PC. Reboot into it, find the kernel you wanted to use, and reinstall it.
c) Install a Gingerbread-based ROM, such as CM7.
Pick a,b, or c. If you have any specific questions, please ask.
Click to expand...
Click to collapse
i did the 2.5.1.2 first but it didnt work so i thought id try the newest one...but 3.0.0.6? where do i get 3.0.0.6? its not in rom manager. ( i really hate rom manager it never works for me...) and ive never done adb? or anything on my pc. everything ive done is on my phone...
drpepper4lf said:
i did the 2.5.1.2 first but it didnt work so i thought id try the newest one...but 3.0.0.6? where do i get 3.0.0.6? its not in rom manager. ( i really hate rom manager it never works for me...) and ive never done adb? or anything on my pc. everything ive done is on my phone...
Click to expand...
Click to collapse
Sorry I was asleep but if you still looking for the solution.
http://forum.xda-developers.com/showthread.php?t=952433
Go to option's thread and follow his instructions on howto install 3.0.0.6 as it works also.
Ive got the following on the HBOOT screen
GLACIER PVT ENG S-OFF
HBOOT=0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14
Clockwork v3.0.0.6 (using this method http://forum.xda-dev...ad.php?t=944681 )
Okay so with that for reference, I'd like to find out why I can't flash CM7 without the blue Andy bootloop. I understand that a fresh install takes time to load, I gave it 30mins before a battery pull, I then returned the battery, hit the top power button and let that sit for another 20. Before I flashed the ROM (through recovery) I made the following wipes in this order; wipe data/factory reset and then wipe cache partition. I've flashed other ROMs that have flashed without issue (Ice Glacier 1.1.6 themed and Royal MIUI) but, lets face it CM owns. Any help would be appreciated. Thank you for reading this.
DHSdrone said:
Lets face it CM owns.
Click to expand...
Click to collapse
No, Sense owns.
With that out of the way, the only thing I can think of is a corrupt download. Try re-downloading the zip to your PC and copying it to your SD. My other thought was a bad recovery, but since you've successfully flashed other ROMs, that doesn't seem likely.
you didn't wipe dalvik in advanced, do that and bootloop will stop...
darinmc said:
you didn't wipe dalvik in advanced, do that and bootloop will stop...
Click to expand...
Click to collapse
Little known fact, if you wipe data, you already wiped dalvik.
option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Mmmhmm, the only thing it could be is bad download or some other mysterious gremlin lol
Sent from my HTC Glacier using XDA Premium App
option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Well then I retract my statement...
when you say bad or corrupted download I assume your talking about the recovery. I thought the same as well, Ive tried both versions of what was posted as the correct, best, and or easiest method of clockworkmod recovery. Im not sure if both versions were in fact the same recovery.img but they both worked for the roms Ive flashed except for cm (nightly 29, cm7-rc2, rc3,and rc4). The fact tjat I cant get this to work, only makes me want it more.
DHSdrone said:
when you say bad or corrupted download I assume your talking about the recovery.
Click to expand...
Click to collapse
No, I mean the CM7 download. The actual ZIP file that you flash.
As far as recovery versions, only 3.0.0.5 and 3.0.0.6 can flash CM7.
Ive tried flashing several different versions of cm7, starting with rc-2 through rom manager. When that gave me my first boot loop I went back to the method I was more familiar with. With trying the different versions I don't see how they were all currupt or broken downloads. I haven't tried any of the cm froyo roms yet.
As far as my earlier statement of "cm owns" I mean no disrespect of any of the other rom developers (including those that did work properly the first time). Ive just came from the G1 and cm is the only rom I ran. Sense may be the best way to go, it's not something Ive given much consideration or time.
I have had the same issue except mine seems to be all 2.3 (Gingerbread) based roms, they all go to bootloop. I have no problem however flashing any of the 2.2 based roms. I also have cwm 3.0.0.6
I had the same issue everytime with different nightly releases. After wiping everything and formatting boot and system still would do it. I found if you wipe then install cm7 only the phone boots fine then reboot setup wifi if your using it the go back into recovery install gapps and it works fine.
Sent from Teh retardarded duc using XDA Premium App
Im unable to get a full boot. After reading several similar sorties I've always turned off all wireless radios. Will post a logcat later today.
Ok so was able to get mine to Boot completely Finally!!! I am somewhat of anoob so sorry if it seems confusing.
1.From recovery wipe data/ factory
2. Wipe cache
3.Advanced > wipe dalvik
4.Mounts>format boot
5.Mounts>format system
6.Advanced> partion SD card (I believe I used 256) No swap partition(dont know if it matters)
7.Mount USB and transfer cm7 and Gapps
8.Flashed cm7 only not apps.
9.Reboot phone (should boot all the way up)
10.Go back to recovery and flash Gapps
11.Reboot phone
My phone booted up very quickly. I hope this helps anyone else out there with the same issue
no more loop da loops
After searching google, and then to various forums, and finally giving up and posting to 2 separate forums, Ive come to say THANK YOU !!! You are all evil geniuses of the highest degree and I bask in your greatness. Ive been overlooking one thing, that is the "if things go bad, try the sd-card format" well I did and it worked. Now that the derp has left my head, and the panic has subsided I can see now that my problem was in fact like many others, and the answers were right in front of me. Again thanks for being patient and coming together as a community to help me out.