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.
Was wondering which recovery everyone likes and why. Been using Ra since my G1 and I love it. (searched around for one of these and didnt see it. Mods delete if there was already one of these polls)
Amon all the way
Sent from my EVO using the Earths core to power my death ray
So...since this brought up...I see that some ROMs don't work with some recoveries? Is that correct? I swear it seems some ROMs only work with clockwork...but then I read all over that clockwork is buggy...or doesn't seem to work for everyone...or something.
I was thinking Amon Ra was the way to go.
I'll follow the answers to this one as well.
sablesurfer said:
So...since this brought up...I see that some ROMs don't work with some recoveries? Is that correct? I swear it seems some ROMs only work with clockwork...but then I read all over that clockwork is buggy...or doesn't seem to work for everyone...or something.
I was thinking Amon Ra was the way to go.
I'll follow the answers to this one as well.
Click to expand...
Click to collapse
Thats true. As far as I know, there have been issues with Clockwork not wiping correctly(I know someone like that)and causing bootloops after flashing. I dont know of any roms that dont work with Ra, but I believe Rom Manager will only work with Clockwork.
Clockwork since it is compatible with ROM Manager.
Clockwork since it has a back option in the menus. It's also updated frequently.
I've been running clock on the evo. I tried putting amon in but I guess I'm too stupid cause when I tried following the directions, I borked the phone good and it took me awhile to get everything back into working order. I could flash it now with rom manager but I'm kinda afraid after the last fiasco.
Sent from my PC36100 using XDA App
I've found that using both have worked for me the best. If I'm running Fresh Rom I will use Amon Ra's but I'll use clockwork for cm6. Its so easy to jump back and forth between recoveries using rom manager its never really an issue. Either way both developers are awesome and their recoveries both have good things to offer
anyway to switch back to Amon? not feelin the Clockwork im too use to it...
seriousblack25 said:
anyway to switch back to Amon? not feelin the Clockwork im too use to it...
Click to expand...
Click to collapse
Use ROM Manager to "flash alternate recovery."
another poll
dglowe343 said:
Was wondering which recovery everyone likes and why.
Click to expand...
Click to collapse
i was wondering the same thing exactly!! So a few days ago i asked the question on the Cyanogen forums... I got a lot of good responses and summarized the comments on the first post... check it out here: http://forum.cyanogenmod.com/topic/2562-best-recovery-for-evo-to-use-with-cm6/
I haven't had one single problem with clockwork recovery.
I like the recovery originally included with toastcfl's root found here. it's very similar to Armon's (don't know if things have to be signed or not), but you use the power button to go back instead of the double-press volume (which I find annoying to do).
I just don't like clockwork as much as the other two, that's just the way it is.
Using Amon Ra because I think it's the only recovery fully compatible with DamageControl.
Not sure of the actual "differences" between it and Clockwork - can anyone clarify?
oblivion0 said:
Using Amon Ra because I think it's the only recovery fully compatible with DamageControl.
Not sure of the actual "differences" between it and Clockwork - can anyone clarify?
Click to expand...
Click to collapse
I'm using clockwork with Damage Control I've had zero problems so far.
I hate Amon recovery... always have to move my ROM downloads to the root of the SD card... forget it 90% of the time and have to reboot to fix it... and that doesn't work so well if I borked my ROM.
I use Clockwork and have zero issues unless I'm trying to autoflash theme updates and such so I have to do those manually. Otherwise no complaints. And no signing issues with Clockwork either.
Amon_RA's recovery FTW!
Well, since rooting 24 hours ago, I've been using Clockwork via recovery boot (not through ROM Manager) and it's worked flawlessly so far. Backed up my rooted stock setup, flashed Fresh, DC, CM6, and then back to Fresh, wiped between every flash, and I've had no problems. Even flashed some Fresh Tweaks in the recovery boot. I actually flashed Amon Ra to see how I liked it . . . and I didn't. Mostly just navigating was a pain with the volume up+down thing, everything else seems like a wash. My only question is whether the Dalvik cache is really being wiped by Clockwork, since it takes half a second to complete when I select the option. I'm going to test it in a few minutes here.
Going to give Baked Snack a run for a while, we'll see how that holds up.
I have wondered that for awhile, silver. It may sound stupid but at least a confirmation in the log messages below would be nice.
Sent from my PC36100 using XDA App
herbthehammer said:
I have wondered that for awhile, silver. It may sound stupid but at least a confirmation in the log messages below would be nice.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Okay, I decided to test. Fired up ADB and booted into recovery from Android. Mounted /data and looked inside /data/dalvik-cache. There was a long list of .dex files. Then I unmounted /data and used the Clockwork menu to wipe the Dalvik-cache (this option is located under the "advanced" menu, NOT just the "wipe cache" option). Re-mounted /data and looked inside . . . and the dalvik-cache directory was gone. It took *slightly* longer than normal when I actually hit the button to wipe it (more like .7 seconds instead of .5), but it does appear that my Clockwork v2.5.0.1 is wiping dalvik just fine. And, of course, when I rebooted back into Android (rooted .6 stock at the moment) it took a long time to boot at the 4G screen, as the cache was being rebuilt. Once I was back in, I checked the /data directory again and dalvik-cache was back and full of .dex files again.
So there. No more speculating, just science.
And if you're ever worried about it, you can just use ADB to wipe the dalvik-cache yourself:
Code:
adb shell
mount /data
rm -rf /data/dalvik-cache/*
Then you can use the Clockwork menu to wipe everything else and flash your ROM. These three commands actually just delete everything inside the dalvik-cache directory, whereas Clockwork appears to remove the directory entirely. Doesn't really matter either way, the system will replace the directory if it gets deleted.
Mmm . . . terminal code.
Hey guys, I'm very much a newbie here so bear with me. I upgraded to the 2.21version about a month ago when some upgrade came out. Thinking it was an official upgrade I did it. I flashed the phone and it seemed to work ok. The problem is the camera doesn't work rendering my bar code not to work either. It seems ok other than that item, but would really like to get the camera up and running, and since Samsung doesn't seem to have the real 2.2 upgrade any time in the near future, I would like to fix this without flashing it again. What can I do to fix? Phone info is Model number sph-d700 baseband version s:d700.0.55.dk28 kernel version 2.6.32.9 fyoyo.dk28
Thanks in advance
Mike
mazspeed said:
Hey guys, I'm very much a newbie here so bear with me. I upgraded to the 2.21version about a month ago when some upgrade came out. Thinking it was an official upgrade I did it. I flashed the phone and it seemed to work ok. The problem is the camera doesn't work rendering my bar code not to work either. It seems ok other than that item, but would really like to get the camera up and running, and since Samsung doesn't seem to have the real 2.2 upgrade any time in the near future, I would like to fix this without flashing it again. What can I do to fix? Phone info is Model number sph-d700 baseband version s:d700.0.55.dk28 kernel version 2.6.32.9 fyoyo.dk28
Thanks in advance
Mike
Click to expand...
Click to collapse
well, are you rooted? i would suggest you follow this guide to get back to stock
http://forum.xda-developers.com/showthread.php?t=773032&highlight=brick
and also, this thread will get moved because it is placed in the wrong section, just a heads up in case you come back and cant find it! it will be moved to the general section
Wow, lot to try and decipher. I'm not sure how or what I should do. everything works but the camera. Is this a bad build or bad software download?
mazspeed said:
Wow, lot to try and decipher. I'm not sure how or what I should do. everything works but the camera. Is this a bad build or bad software download?
Click to expand...
Click to collapse
well, are you rooted? it might just be the build. there are alot of different 2.2.1 builds out there for the epic. if you are rooted, you can just flash another rom, it will fix the issue. if you arent rooted, you will have to follow that guide to get back to stock. and i know its alot to decipher, but just take it ONE STEP AT A TIME. i would search for youtube videos on how to do it too, thats what helps me the most.
Ok, sorry for the dumb question, but how do I know if I am rooted?
mazspeed said:
Ok, sorry for the dumb question, but how do I know if I am rooted?
Click to expand...
Click to collapse
download the app "superuser" from the market, then download "android terminal emulator" from the market, open the terminal emulator, type "su" hit enter, and if you are rooted, a pop up will come up and say "blabbity blah is asking for superuser permission, accept? hit accept. if it worked, you should see this in the terminal emulator now "#" without the quotes, that is how you know if you are rooted. if nothing happens in terminal emulator, you are not rooted.
If there is a newer version, I would not mind going to that, if there is. I did do this about a month ago.
mazspeed said:
If there is a newer version, I would not mind going to that, if there is. I did do this about a month ago.
Click to expand...
Click to collapse
even if there is, you would have to go back to stock and then flash it through odin man
It said "not found" in the blue screen of su. I can only post every 5 min, bear with me, and thanks again for the help. What's next? Ok, going back to stock would be fine till samsung finally goes to a new version. If I go back to stock, will I lose everything? I did download Ti backup and it doesn't work. It says "please verify if the rom is rooted". And then it doesn't work. I guess I could have checked there to see if it was rooted.
he does not have to "go back to stock" to flash a different 2.2 build through odin, im sorry but that made entirely no sense
Check this link
Here this link should give you a better understanding of how to go back to stock.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700#Odin_Stock_Flashing
Look under the section for odin stock flashing. And btw DK28 is not officially by samsung. It is a leaked build and they do recommend against not installing it since it is not finalized. The current most official kernerl is DI18 so you should grab the tar.md5 for that rom version and flash back to stock using odin. If you still want to try unofficial froyo roms make sure you use the one click root and recovery method to make sure you are rooted after going back to stock DI18. Then you are free to flash any froyo roms you want. Hope this helps man.
Zeinzu said:
he does not have to "go back to stock" to flash a different 2.2 build through odin, im sorry but that made entirely no sense
Click to expand...
Click to collapse
my understanding of odin is that in order to update builds, you have to downgrade. like 3/4's of the roms here make you unroot/downgrade, then re-root in order to install them.
oshizzle1991 said:
my understanding of odin is that in order to update builds, you have to downgrade. like 3/4's of the roms here make you unroot/downgrade, then re-root in order to install them.
Click to expand...
Click to collapse
I have been flashing for a while and never had to downgrade to update builds. If you have already flashed to the leaked stock DK28 you can install as many DK28 based roms as you want through clockwork mod as long as you wipe data/cache. You are definitely right in regards that he should odin back to stock Eclair DI18 since he is having camera issues because that definitely might help as it has helped me many times.
Ok, is there a newer build than what I have now, and if I can run it, how do I do that? Thanks again guys for all the help. I really do appreicate it.
I don't mind trying newer builds, and since this build is well over a month old, I would think there would be newer ones, maybe?
Please post questions in General section.
mazspeed said:
Ok, is there a newer build than what I have now, and if I can run it, how do I do that? Thanks again guys for all the help. I really do appreicate it.
I don't mind trying newer builds, and since this build is well over a month old, I would think there would be newer ones, maybe?
Click to expand...
Click to collapse
Okay i think you may be a little confused. There is no newer build. There is ONE stock DK28 leaked build which is what i assume you have. Now there are custom roms BASED on that leaked build which have various customizations and whatnot. You are more than welcome to flash a custom rom of your liking but they are not "newer builds", just customized roms based from the ONE leaked DK28 build.
Your best bet is to go back to di18 and wait on the ota. Stay there a little bit and do some more reading and learn a little more before you start doing this stuff. Learn about rooting and flashing roms. If you didn't know if you were rooted or not then most likely you were not. Use Odin to go back to di18. I know ut sucks losing all your data but in doesn't take that long to set your phone back up. Good luck.
hgvidal said:
Okay i think you may be a little confused. There is no newer build. There is ONE stock DK28 leaked build which is what i assume you have. Now there are custom roms BASED on that leaked build which have various customizations and whatnot. You are more than welcome to flash a custom rom of your liking but they are not "newer builds", just customized roms based from the ONE leaked DK28 build.
Click to expand...
Click to collapse
This guy is right. What you have is most likely the stock version of the DK28 build. That version is known to have many issues. Being on that stock build of DK28 according to the info you posted, you are welcome to flash a customized DK28 ROM that has addressed these issues.
Again, you will not be required to downgrade your build in order to flash any customized ROM based on the same build (DK28)
For practical purposes, to flash (install) a custom ROM you WILL be required to be "rooted" and install a program onto your phone that gives you the ability to flash. The program that is universally used is called "ClockworkMod Recovery" and employs a simple "one-click" method to install onto your phone. This one-click method also gives you the root access on your phone that is required to flash a ROM. You can find the program and instructions on how to install it here:
http://forum.xda-developers.com/showthread.php?t=770388
Customized ROMs can be found in the Epic 4G Android Development section of this forum. Note that you will ONLY be looking for ROMs based on your DK28 build. ALL of these ROMs will require you (on your stock DK28 build) to do a complete wipe of the data from your phone. Your data can and should be backed up however, and the ClockworkMod Recovery mentioned above allows you to do both the data backup and data wipe.
Instructions on how to install ROMs are often included in their post. They should look something like this:
1. Download the DK28 ROM you want (it will come in .zip format) and move the .zip file to main (base/root) folder of your phone's SD card.
2. Using ClockworkMod Recovery, BACKUP your data by selecting "Backup and Restore" and then "Backup"
3. Using ClockworkMod Recovery, WIPE your data by doing ALL of following:
a. Select "wipe data/factory reset". Do this three times (3x)!
b. Select "wipe cache partition". Do this three times (3x)!
c. Select "advanced" and then "wipe dalvik cache". Do this three times (3x)!
4. Using ClockworkMod Recovery, FLASH (install) the ROM you downloaded by selecting "Install zip from sdcard" and then selecting the ROM's .zip file in the root folder of your sd card.
5. Using ClockworkMod Recovery, select "reboot system now" and WAIT for phone to boot. This will take longer than a normal boot up.
I find these ROMs work well for me:
http://forum.xda-developers.com/showthread.php?t=878944
http://forum.xda-developers.com/showthread.php?t=861367
http://forum.xda-developers.com/showthread.php?t=869295
http://forum.xda-developers.com/showthread.php?t=856715
timothylaws said:
This guy is right. What you have is most likely the stock version of the DK28 build. That version is known to have many issues. Being on that stock build of DK28 according to the info you posted, you are welcome to flash a customized DK28 ROM that has addressed these issues.
Again, you will not be required to downgrade your build in order to flash any customized ROM based on the same build (DK28)
For practical purposes, to flash (install) a custom ROM you WILL be required to be "rooted" and install a program onto your phone that gives you the ability to flash. The program that is universally used is called "ClockworkMod Recovery" and employs a simple "one-click" method to install onto your phone. This one-click method also gives you the root access on your phone that is required to flash a ROM. You can find the program and instructions on how to install it here:
http://forum.xda-developers.com/showthread.php?t=770388
Customized ROMs can be found in the Epic 4G Android Development section of this forum. Note that you will ONLY be looking for ROMs based on your DK28 build. ALL of these ROMs will require you (on your stock DK28 build) to do a complete wipe of the data from your phone. Your data can and should be backed up however, and the ClockworkMod Recovery mentioned above allows you to do both the data backup and data wipe.
Instructions on how to install ROMs are often included in their post. They should look something like this:
1. Download the DK28 ROM you want (it will come in .zip format) and move the .zip file to main (base/root) folder of your phone's SD card.
2. Using ClockworkMod Recovery, BACKUP your data by selecting "Backup and Restore" and then "Backup"
3. Using ClockworkMod Recovery, WIPE your data by doing ALL of following:
a. Select "wipe data/factory reset". Do this three times (3x)!
b. Select "wipe cache partition". Do this three times (3x)!
c. Select "advanced" and then "wipe dalvik cache". Do this three times (3x)!
4. Using ClockworkMod Recovery, FLASH (install) the ROM you downloaded by selecting "Install zip from sdcard" and then selecting the ROM's .zip file in the root folder of your sd card.
5. Using ClockworkMod Recovery, select "reboot system now" and WAIT for phone to boot. This will take longer than a normal boot up.
I find these ROMs work well for me:
http://forum.xda-developers.com/showthread.php?t=878944
http://forum.xda-developers.com/showthread.php?t=861367
http://forum.xda-developers.com/showthread.php?t=869295
http://forum.xda-developers.com/showthread.php?t=856715
Click to expand...
Click to collapse
does he still have to flash the DK28 modem?? i am totally new to odin, im coming from 4 HTC devices, so ODIN is like new territory to me.
oshizzle1991 said:
does he still have to flash the DK28 modem?? i am totally new to odin, im coming from 4 HTC devices, so ODIN is like new territory to me.
Click to expand...
Click to collapse
He does not have to flash the DK28 modem because he's already on it. This is indicated by his baseband version being S:d700.0.5S.DK28
Where can I find the download link for the new gb.
Dinc
I'm not sure what you're asking for. Honeycomb 3.0 (which is not available for the Incredible) or Gingerbread with Sense 3.0?
Sent from my awesome sauce Incredible uisng Miui
I think gingerbread with sense 3.0. Sorry.
Dinc
There are several roms with what you are looking for in the development forum.
Oh ok. And do these install the same way. I'm still using the old clockwork recovery.
Dinc
Yes they should install like normal. Check the OP's for the ROM though. All require hboot .92 and CWM 3.0.0.x.
I recommend giving JoelZ's kingdm rewind 3d a go. very smooth
Yeah I'm still using the old cwm and I have never messed with cwm3 so how do I install the new newest cwm.
Dinc
You can use rom manager or you can flash the recovery manually in hboot. Files at www.dougpiston.com
RE: Multiple wipes
http://www.cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache
Not trying to start a big debate, just pointing out that wiping multiple times isn't doing anything but adding more time to your flashing process. Hopefully this helps.
I only wipe everything once, flash vr superwipe, then flash rom. Works fine on all.
sent from whatever damn rom im using this hour!
k_nivesout said:
Not trying to start a big debate, just pointing out that wiping multiple times isn't doing anything but adding more time to your flashing process. Hopefully this helps.
Click to expand...
Click to collapse
You obviously need to wipe three times and then flash the ROM twice. And reboot about 4 times. One each is not enough. Pull your battery a couple of times as well.
Is installing the new cwm the same as flashing a radio.
Dinc
If you take the time to read what I linked, it explains everything. When you're telling your recovery to wipe, it is a routine run within code. Doing a secondary wipe or even a third is just running the same exact command again. Logically, why would CWM run the same exact command differently, necessitating multiple wipes to get the same result?
There's no "randomness" built into the recovery that would result in the command not being run, or run differently, when you select it.
Its not like a physical action, where the more you wipe, the "cleaner" it gets. Again, it is a routine run within code, and it is not variable or random.
If there was any perceived benefit to the wiping procedure that you mentioned, I'm willing to bet that its due to wiping the /system and /boot partitions, which isn't done when you wipe data/factory reset and wipe cache in the main menu. This is something that should be, and usually is, included in the rom's updater script, but may be forgotten by the dev. Some people have mentioned that recovery version 3.0.0.8 does not work well with AMOLED incredibles. I can't speak for that myself, but in the event that there is a problem, the resolution would be using the 3.0.0.7 recovery, not wiping multiple times.
And I don't think you're correct in assuming that "all the devs" recommend the multiple wipe approach, I think you'll see that plenty do not, including the cyanogen dev who wrote the article I linked to (BTW, he is the one that got CM7 on the Droid X, a phone with a locked bootloader, so I'm assuming he might know what he's talking about.)
That is all..
snapper915 said:
Is installing the new cwm the same as flashing a radio.
Dinc
Click to expand...
Click to collapse
They are totally different, CWM is a recovery, radios are well, radios. They are flashed the same way though (in bootloader).
Awesome. Thanks. I don't have to rename any thing.
Dinc
cvbcbcmv said:
you mean like PB31IMG.zip? No, nothing like that.
Click to expand...
Click to collapse
Sweet. Thanks for everyone's help.
Dinc
Hi, I used the paid version of ClockWorkMod Recovery to backup, then download the 'Cyclonic Rom'. Well, it rebooted to a 'Cyclonic Rom' startup screen (animated lettering) - but that's it. I'm wary to unplug the battery if it's actually flashing, but this has been going on for 20 minutes or more. Can I pull the battery and see what happens? How long does a new ROM take to install, this is my first one. Thanks.
BTW: These CAPTHCA's are getting tough! This will be the 4th try!
fixed it
I unplugged the battery and did a factory reset/format in ClockWorkMod. I rebooted and all seems well so far.
20 minutes is a looong time for Cyclonic to boot. Is it still working ok? As far as CW goes, I only use Rom Manager to downlod what I want/need. When it comes to flashing I wipe everything manually and flash from recovery. I don't trust the app. But thats me.
Sent from my PG06100 using xda premium
+1 to that. I always use the same Method for Flashing Roms ( The one linked in my Sig ) . Clear everything Manually. I try to never deviate from that. Reason being, after Flashing literally hundreds of times I've found it to be the most reliable way to Flash a Rom. Meaning the least amount of possibilities for issues later on down the road .
alarmpro said:
Hi, I used the paid version of ClockWorkMod Recovery to backup, then download the 'Cyclonic Rom'. Well, it rebooted to a 'Cyclonic Rom' startup screen (animated lettering) - but that's it. I'm wary to unplug the battery if it's actually flashing, but this has been going on for 20 minutes or more. Can I pull the battery and see what happens? How long does a new ROM take to install, this is my first one. Thanks.
BTW: These CAPTHCA's are getting tough! This will be the 4th try!
Click to expand...
Click to collapse
Flash newsense.
And don't forget to wipe dalvik.
I have been searching (as in using the 'search' function) for a solution or answer to this, but couldn't find anything. This seemed to be the best thread to dig up instead of starting a new one.
Within Clockworkmod, whenever I try to go into recovery (either trying to 'reboot into recovery' or installing a ROM from SD card), it always throws me into Android System Recovery 3e instead of CWM recovery. Of course the stock recovery doesn't recognize my downloaded ROM.
I've also noticed that trying to update a ROM in HBOOT via a new PG06IMG.zip file on SD root is not working, except to wipe all my system and apps data, and then returning me back to rooted 2.2. HBOOT seems to read the new zip file fine, but when I reboot nothing has changed.
I've read wiki and lots of other stuff, but I can't seem to find an answer except that MAYBE that I need a new kernel first??? Okay, let the flaming begin.
jdjohn said:
I have been searching (as in using the 'search' function) for a solution or answer to this, but couldn't find anything. This seemed to be the best thread to dig up instead of starting a new one.
Within Clockworkmod, whenever I try to go into recovery (either trying to 'reboot into recovery' or installing a ROM from SD card), it always throws me into Android System Recovery 3e instead of CWM recovery. Of course the stock recovery doesn't recognize my downloaded ROM.
I've also noticed that trying to update a ROM in HBOOT via a new PG06IMG.zip file on SD root is not working, except to wipe all my system and apps data, and then returning me back to rooted 2.2. HBOOT seems to read the new zip file fine, but when I reboot nothing has changed.
I've read wiki and lots of other stuff, but I can't seem to find an answer except that MAYBE that I need a new kernel first??? Okay, let the flaming begin.
Click to expand...
Click to collapse
You need to flash recovery first, it is the first option in ROM Manager. You can't update a ROM with PG06IMG.zip, nor can you do it in the bootloader. Flash the recovery, wipe everything (data, cache, dalvik cache, system, sd-ext) then flash a ROM.
Did you get this sorted?
bilgerryan said:
You need to flash recovery first, it is the first option in ROM Manager. You can't update a ROM with PG06IMG.zip, nor can you do it in the bootloader. Flash the recovery, wipe everything (data, cache, dalvik cache, system, sd-ext) then flash a ROM.
Click to expand...
Click to collapse
Chad The Pathfinder said:
Did you get this sorted?
Click to expand...
Click to collapse
No, still having trouble. I have flashed ClockworkMod Recovery (version 5.0.2.0) in the ROM Manager app, but when I 'reboot into recovery' within the app, it goes to the Android System Recovery. I'm also confused about the 'apply sdcard:update.zip' option in ASR...seems like that would update something if the file was set up properly.
I guess I need to search for a tutorial on how ASR and HBOOT work. Sorry to bother you guys with the basics.
Try this onehttp://forum.xda-developers.com/showthread.php?t=1663531
bilgerryan said:
Try this onehttp://forum.xda-developers.com/showthread.php?t=1663531
Click to expand...
Click to collapse
Will check it out, thanks! I'm leaving town today, so not sure if I will be able to experiment before I go, but I will not give up!
The only thing I use Rom Manager for is to get the recovery. The way I go into recovery is to turn my shift completely off (do a battery pull to make sure its completely off) then hold the volume down and power buttons at the same time until the bootloader screen comes on. (While there see if it says S-off near the top) then using the volume buttons highlight the recovery option and push the power button. Then when you're there use the volume buttons to navigate through the various fields and hit enter to select. I hope this is helpful to you. Good luck!
Edit: by the way, when you first get to the bootloader screen, it will automaticly do a check showing a few green lines. Thats ok. Just wait until its finnished then go into recovery the way I stated.
jdjohn said:
Will check it out, thanks! I'm leaving town today, so not sure if I will be able to experiment before I go, but I will not give up!
Click to expand...
Click to collapse
How did you root? It seems as if you have a locked bootloader and/or S-ON if the custom recovery is not taking
Sent from my PG06100 using xda premium
CNexus said:
How did you root? It seems as if you have a locked bootloader and/or S-ON if the custom recovery is not taking
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
jdjohn said:
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
Click to expand...
Click to collapse
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
bilgerryan said:
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
Click to expand...
Click to collapse
Was thinking that myself. Will have to wait til I get back, though...headed out of town. Thanks guys!
jdjohn said:
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
Click to expand...
Click to collapse
Hmm, never mind then, it seemed as if your bootloader was still locked if the recovery wouldnt flash
bilgerryan said:
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
Click to expand...
Click to collapse
Yeah, just do what bilgerryan said (make sure that you download the one that says "flash through bootloader" or something along those lines)
Before flashing, download some md5sum tool and make sure it matches the one given on there
Sent from my PG06100 using xda premium
Finally got back to this and was able to install and use Dread's CW-Enhanced. So far I have only flashed the Speedy Rooted OTA 2.77.651.8 (bascially 2.3.4 rooted). GB had some features I was wanting, but missing, after rooting back to Froyo.
But before continuing on to other ROMs, I was wondering how you guys handle restoring basic apps and data each time you flash a new ROM. Or, do you only use extra play phones for new ROMs and not your daily user? It would seem that every time you flash, you need to restore SuperUser, Titanium, ROM Manager (ClockworkMod, then probably Dread's enhanced image file), Terminal Emulator, etc. And of course contacts and messaging history and other stuff like that.
So far, after flashing a ROM, I usually download Titanium (or MyBackup) and restore apps and data from backups before continuing. Do you just keep certain APK files on your SD card and install from ADB instead of re-downloading from Google Play Store each time?
I flash ROMs on my dd. Usually when I falsh a new ROM (not a nandroid) I fresh install my apps through the play store. Especially if switching between GB, ICS and JB! Some apps work well if carried over by tb but not all. You'll just have to experiment to see what works with your shift and what doesn't.
Also, the recovery only ever needs to be flashed once
What I used to do is backup my current rom with all my data and settings and then wipe + flash a new rom. If i liked it, then I would move my full box of apps and data to the new rom, but restoring data can go wonky so I always made a backup before doing that too. If i didnt like it, I would either restore my original backup for a bit or keep flashing new roms until I either found one I liked or got tired and restored my backup lol