Database Develop

Unable to flash Anything else

i have done quite a few searches on this and yet have found nothing so i hope i dont get reamed for posting this.
if someone has a link for this answer id be very thankful.
if not then PLEASE SOMEONE EXPLAIN!!!!!!!
at the moment i am running drizzy hero rom. to do the update i did use the one touch root. on a second phone i did it manually. on both i added the hard spl and am running the RA v 1.2.1 recovery. I liked this ROM and wanted to see what bugs it had. after a few days i wanted to switch and try a different ROM I have dl most of the ROMs available and already have them on my sdcard once i did this no ROM would load except for Drizzy(new Vision v2.8). after trying a few things and accomplishing nothing i decided to redo EVERYTHING. unrooted my phone rooted again applied recovery made sure radio was to date and spl. and still nothing i cant even run the original jf1.5 that i was using before deciding to port. this issue is occuring on both phones. 1st phone was again done with one step root and the 2nd phone was done completly manually. I REALLY REALLY REALLY want to try these other roms SO PLEASE SOMEONE HELP. if you need more information on what i did with these phones ill gladly tell you step by step on what i did.
sorry for that.
I was using my G1 and also had a friends. On my g1 i used the one step root. I used the Instructions from The Unlocker.com. It uses flashrec.apk and also Amon Ra's recovery image. After that i went over to the How to Load a Custom ROM. same site. It asks you to check the Radio and the Spl. The radio is 2.22.19.26I and the spl used was the HARDSPL 1.33.2005.
Once i finished that i went and formated the sdcard to Fat32+Ext2+LinuxSwap also converted Ext2 to Ext3.Then I did-Move Dalvik Cache to SD. last 3 steps to speed up hero. after all of that I loaded 4 ROMS CyanogenMod ROM, jACXHeroSkiv Hero ROM v1.8, Drizzy’s NewVision TouchFlo ROM, and JF v1.5 Cupcake ROM. I have only flashed Drizzy's until last night.
I was unable to flash any other one and when i flashed back to drizzy I had problems loading it back but eventually loaded fully the issue was running the startup wizard it kept crashing. after a reboot it was ok.

Give us step by step on what you did and USE PARAGRAPHS
that whole thing looked like mumbo jumbo to me
put new lines where they belong to help separate out the steps you took

FIXED! thanks!

hobbitton said:
FIXED! thanks!
Click to expand...
Click to collapse
did you do a data wipe? you need to wipe going from hero to cupcake/donut

When I first did all of that I did. Am I supposed to data wipe everytime I switch the Rom?

hobbitton said:
When I first did all of that I did. Am I supposed to data wipe everytime I switch the Rom?
Click to expand...
Click to collapse
when your using hero rom's, yes.
if your upgrading cupcake roms (ie cyan 4.0.4 to 4.1.9.2 ), no
If its not working, WIPE
you cant go from hero to cupcake without wiping and not expect a lot of problems. they cause too many issues.
hero roms use the data partition differently

also remember to wipe /system/sd/ to clear all of that out. pull your /system/sd/ to your computer first though

thanks you guys it helped alot

Best way to wipe phone between roms

I have a rooted cdma sprint hero and i hear every once in a while that there are some left over stuff that may cause problems with new roms. Now i was wondering what would be the best way to wipe to make sure that there is nothing left over from previous roms.
This is what i do;
1 back up pics and music from sd card
2 format sd card
3 put new rom on sd
4 flash into recovery
5 wipe all that i can cache devalk (sp) etc
6 Run moduler remover
7 Falsh rom
8 Flash kernal
I was also wondering if doing this removes any kernal that i have put on there or am i just adding them on top of each other?
Sorry for such a noob question but i would really like to make sure that my phone is running how the guys making these roms intend them to run

You're being real thorough for sure! LOL! I just boot into recovery and wipe dalvik, cache and ext. I t really depends on how different the new ROM is, as incompatible files are the problem.

Sorry for putting in the wrong thread i wasn't where i thought i was and im not sure i am where i thunk i am. if this needs to be moved feel free

Switching between ROMs all you have to do is wipe data/factory reset and wipe dalvik cache. That's it. No need to reformat your SD card..

what about if you use ap2sd?

Looks as if wiping/resetting the device directly from Fastboot is starting to become fairly popular as well. May want to give that a go...
-Reboot to Fastboot
-Wipe/reset
-Reboot to Recovery
-Flash ROM/Kernel
-Reboot device

Neo31697 said:
what about if you use ap2sd?
Click to expand...
Click to collapse
If you use apps2sd, that's what wipe ext is for. I actually forgot to include that in my previous post.

wow didn't know that thanks

Just making sure, you're talking about apps2ext, right? Not the built-in froyo version aka apps2fat?

Yes I am not running froyo ... yet
Sent from my NFX-HERO

Since the topic is up I have a question on my own. Are all the wipes necessary when I flash one rom and then nand restore to another?

I just Nandroid, flash and pray the new ROM works I may do a Dalvik wipe now and again. Fingers crossed I have had no problems so far, except when I figured there would be one

Krazy_Talk said:
Since the topic is up I have a question on my own. Are all the wipes necessary when I flash one rom and then nand restore to another?
Click to expand...
Click to collapse
See my post above...Some do, I don't, and the last few days I have flashed, Nand, reflashed new ROMS, themes, etc while messing with CM6.1 and have not even done a Dalvik wipe...that's just my style though Is it necessary? I would say no, others would say yes...
However, I do have a collection of working ROMS on my SD from Nand all set up the same way that were done correctly (i.e. proper wipe, etc.) with different themes I can go back to if need be.

New recovery 3.0.0.5

Can this new recovery be used to flash CyanogenMod 6.1.1??? I just got the new recovery update on rom manager and was going to flash cyanogenmod 6.1.1 and just checking. I thought the new recovery was for flashing Gingerbread roms?? Any help would be appreciated.
Thanks,
Vinny

I don't see why not. You can try and if it don't work you can flash an older version in ROM Manager

vinnyjr said:
Can this new recovery be used to flash CyanogenMod 6.1.1??? I just got the new recovery update on rom manager and was going to flash cyanogenmod 6.1.1 and just checking. I thought the new recovery was for flashing Gingerbread roms?? Any help would be appreciated.
Thanks,
Vinny
Click to expand...
Click to collapse
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
EDIT: I successfully restore other custom roms using lower version of Clockworkmod. But the loop-reboot problem of MM's CM7 remains the same.

I guess I won't find out until I try. Newly rooted and going to give CyanogenMod a try. Know I am going to be happy as hell with it.
Thanks

The new recovery should be fine with flashing any roms. As for any standing problems with it, im am uncertain. You may want to wait 2 weeks or so to see if their are any problems from people using it. Personally I like Amon ra so i cant say.

ricky9237 said:
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
Click to expand...
Click to collapse
A full wipe is necessary to upgrade to gingerbread roms from any lower android versions. Did u full wipe? + Dalvik cache wipe?

mikeacela said:
A full wipe is necessary to upgrade to gingerbread roms from any lower android versions. Did u full wipe? + Dalvik cache wipe?
Click to expand...
Click to collapse
Yes. I did full wipe on everything. I even fix permission. No luck at all.

ricky9237 said:
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
EDIT: I successfully restore other custom roms using lower version of Clockworkmod. But the loop-reboot problem of MM's CM7 remains the same.
Click to expand...
Click to collapse
I used it to flash and install tonight's build successfully...

I have a "side question".
To flash any GingerBread flavor, do we need 3.x.x.x ou 2.5.x.x is working?
I haven't give CM7 a try yet, but I'm not sure if I need/want to upgrade to 3.x.x.x, 2.5.1.4 work well for me.

DumbUglyDragon said:
I used it to flash and install tonight's build successfully...
Click to expand...
Click to collapse
I got it too. No more crazy rebooting. I solve it by reformatting my SD card and recreating ext3. I guess 3.0.0.5 recovery messed up my ext3 partition. Now, MM CM14 is working pretty well. FYI, I am using 2.5.1.4 recovery.

Yeah it was working good till I try to do a restore, lets just say I;m up all night trying to restore my phone. I think my EXT partition messed up too as DTa2sd is giving me all kinda of headache.

doesn't work with MIUI for me!
don't understand that, but luckily its not a big deal flashing older versions!

baseballfanz said:
Yeah it was working good till I try to do a restore, lets just say I;m up all night trying to restore my phone. I think my EXT partition messed up too as DTa2sd is giving me all kinda of headache.
Click to expand...
Click to collapse
I hear you there! That was me last night! DON'T USE 3.0.0.5! The only fix I found to actually work was to completely format my SD card and then re-partition it, then use RA and a fresh install. What a pain in the arse!

Same thing here. Switched to 3.0.0.5, and the next thing, my ext was fried and I had to reformat the entire card. Could be coincidence, but...
Sent from my Nexus One using XDA App

[Q] Flashing GB 2.3 over and over......Devs?

This question is for the Dev's. As we all know, we have been conditioned to FTS(although I rarely did)before going from ROM to ROM. Now with GB out, there is allot of flashing not only from one dev's rev. to another, but to other dev’s altogether. Yet I haven’t heard of anyone specifically telling me to FTS. Is there something with GB that has made that practice obsolete? Also, if it should become practice again, is there going to be a new or updated one click Odin created so that everyone starts from the same square one?

That practice has been obsolete for MONTHS now, way before gingerbread. The roms wipe before they flash, no need to fts, unless there is a HUGE problem and thats your only out.
Flashed continuum 5 from firefly.
flashed perception 2 over that, flashed mosaic over that. Never once back to stock.
If you want to be careful before you flash wipe data/factory reset. Wipe cache partition, and wipe dalvik cache all from recovery then flash the rom...

How to keep data when flashing new ROM

I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?

R77 said:
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
Click to expand...
Click to collapse
you wipe cache and dalvik cache then you flash rom on top.

R77 said:
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
Click to expand...
Click to collapse
Titanium Backup Pro. back up your apps with data, run a batch command to restore them once youve properly installed the new ROM
bober10113 said:
you wipe cache and dalvik cache then you flash rom on top.
Click to expand...
Click to collapse
this has historically been known to cause issues. its always best to factory reset at least once, wipe caches, reboot into TWRP, install new ROM(and GApps, if needed), go into file manager within TWRP and delete the android folder (just for good measure), boot and restore your apps/data with a backup app used before getting into the installation process

youdoofus said:
Titanium Backup Pro. back up your apps with data, run a batch command to restore them once youve properly installed the new ROM
this has historically been known to cause issues. its always best to factory reset at least once, wipe caches, reboot into TWRP, install new ROM(and GApps, if needed), go into file manager within TWRP and delete the android folder (just for good measure), boot and restore your apps/data with a backup app used before getting into the installation process
Click to expand...
Click to collapse
lol nuke it from orbit each time because there's a new rom base for that particular custom rom. yeah sure...
5% of the time when there really is an issue with a new build i think i have enough insight to know what to do.
changing rom completely yeah for sure. but i did respond specificially to his question where he was referring on maintaining the team exykings rom from update to update.

bober10113 said:
lol nuke it from orbit each time because there's a new rom base for that particular custom rom. yeah sure...
5% of the time when there really is an issue with a new build i think i have enough insight to know what to do.
changing rom completely yeah for sure. but i did respond specificially to his question where he was referring on maintaining the team exykings rom from update to update.
Click to expand...
Click to collapse
more often times than not, the 5% you mentioned are unaware of what to do if an issue arises. i wasnt trying to tell you what to do, moreso just bring it up into conversation for those just-in-case situations

youdoofus said:
more often times than not, the 5% you mentioned are unaware of what to do if an issue arises. i wasnt trying to tell you what to do, moreso just bring it up into conversation for those just-in-case situations
Click to expand...
Click to collapse
If I were to go to advanced wipe when flashing a new build if I were to leave data option alone. Will that keep all of my data or not?

edit:
@R77
but that's what he says to not do. if you do so you maybe in the 5% and you just may have problems.(wiping all but data is considered a dirty flash)
but what i am telling you is that just wipe cache and dalvik cache and flash rom of the same dev. you should be fine. if you are not fine, and have weird stuff going on use regular factory wipe option in twrp wipe menu.
so one method is called: a clean flash.
the other called: a dirty flash.
on the same rom, dirty flash works fine 96 to 100% of the time. so dont worry about it.
if you flash an other rom from an other dev then clean flash is recommended for sure.
so its very simple as you can see. some have a tendency to make it appear difficult.

bober10113 said:
but that's what he says to not do. if you do so you maybe in the 5% and you just may have problems.(wiping all but data is considered a dirty flash)
but what i am telling you is that just wipe cache and dalvik cache and flash rom of the same dev. you should be fine. if you are not fine, and have weird stuff going on use regular factory wipe option in twrp wipe menu.
so one method is called: a clean flash.
the other called: a dirty flash.
on the same rom, dirty flash works fine 96 to 100% of the time. so dont worry about it.
if you flash an other rom from an other dev then clean flash is recommended for sure.
so its very simple as you can see. some have a tendency to make it appear difficult.
Click to expand...
Click to collapse
ive been flashing ROMs since the OG HTC Evo 4G and am keenly aware of the definitions and consequences of dirty flashing vs clean flashing. The android folder should be deleted irrespective of what youre flashing if we're being forward. I guess we are just going to overlook the hundreds of versions of various rom builds that REQUIRED a clean flash every time otherwise bugs were known to occur.

youdoofus said:
ive been flashing ROMs since the OG HTC Evo 4G and am keenly aware of the definitions and consequences of dirty flashing vs clean flashing. The android folder should be deleted irrespective of what youre flashing if we're being forward. I guess we are just going to overlook the hundreds of versions of various rom builds that REQUIRED a clean flash every time otherwise bugs were known to occur.
Click to expand...
Click to collapse
did i make it sound like i was replying to you?
guess i should have quoted him to make it obvious.
and again, if he's on rom A 1.0 and wants to upgrade to rom A 1.1 then no need to clean wipe or del android folder each and every time.
have you ever had an OTA ? samsung dosent wipe clean ure device just because u upgrade. so his question regarding a similar scenario would apply, dirty flash would work fine.
and again as stated before, if there is weird stuff happening then just clean wipe. no need to get nuclear each and every time.
btw various rom builds require clean flashes because they suppose people are coming from other roms. not saying that there aren't situations where continuously dirty flashing the same custom rom all along its progress wouldint eventually mandate ir benefit from a clean flash but i know of no one that clean flashes each time their rom dev updates/increments a build. they/we only do it incase of issues, this is of some sorts an unwritten law so to speak. devs even state it when users ask if they can do as such.