Develop Bugs

just rooted need help/advice

So i just did the 3 step root and im at the clockwork mod recovery screen
There is different stuff to choose and i have no clue what to select?
Can someone please direct me to what to do next this is my first android phone and i have no idea how to load a rom or what i should be doing next
thanks in advance

Well are you hoping to flash a custom ROM? If so, you'll need to download the ROM and copy it to the root of your SD card. Then when you boot to recovery, choose the options to wipe data, wipe cache, and then install a zip from SD. If you want to back up your phone, choose the Nandroid option.
You got pretty far without knowing how to complete your journey.

so if i click nandroid that will back up what my phone is set at now?
what is a good custom rom to use ?
I would like to have wifi tether but do not have 4g and probly wouldnt use it very often, i read something that there was a stock rooted rom? I also do not want to lose my camera?

Start here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Evo_ROMs
Then just read up on the dev pages/threads for the popular ROMs. I use Fresh 1.0.1 with the netarchy 3.7.3c Fresh-compatible kernel (haven't switched to the new one that just came out today). Camera works great, wifi tether app is built-in. If you want that, download both (just search here), put them on your SD card, reboot to recovery, and flash the ROM, then the kernel. You don't have to flash a new kernel or even radio if you don't want to, but everything is installed the same. Usually reading a couple of pages for each ROM will tell you if there are an problems. Other options are the stock rooted ROM, DamageControl, Baked snack, or there are a couple of new ones for Froyo as well, but they have some features left out (like 4G, wifi, MMS . . . depends on the ROM).
Nandroid (or, inside Android, ROM Manager) will make a system image for you, saving everything exactly as it is. To restore, boot to recovery and choose the correct options for that. Should be pretty self-explanatory.
Always wipe data and cache before flashing, and it's a good idea to search Google for Cyanogen's recommendations for recalibrating your battery (it's on his wiki). Just don't flash a stock, non-rooted ROM or any OTA updates that Sprint tries to push on you. Always get something that the devs here say is safe for rooted phones.
Hope that clears some things up for you.

[Q] I just rooted my evo and need help updating because im new to this stuff

Hello and sorry for the inconvenience. I'm new to rooting and updating my evo. I have 2.2 android version since i rooted my evo and i rooted it with unrevoked 3. Now i keep getting updates from my phone but cant install them because im rooted. I was wondering how can i update my evo to the latest android version which is 2. something and how can i also update the latest fota version that's 3.70.
I don't know if i need to install a new ROM or get the update online. Your help would be grateful and thanks in advance.

You have to flash updated roms to keep your phone updated...thats the only way AFAIK

Any custom rom will get rid of the update notifications, and all are based on the newest OTA by now. I think the only 2.3 gingerbread rom is the CM7 nightly, which is very stable and very nice
Before you flash a new rom you will want to make sure you have one of the custom recoveries, RA for example is what i use for my flashing.

What Radio and software are you running?

software 2.2 and what do you mean by radio, basebad or kernel

Have you checked your phone to be sure you have S- off? There is a Rom in the developers section that has the latest OTA 3.70... but I do concur with the guys above in that you need to flash a custom Rom.
Go to the market and download Rom Manager. By using unrevoked I believe you now have clockworkmod as your custom recovery. And I'm pretty sure it would b version 2.6.0.1 which is the good one. By using Rom Manager you can flash a custom Rom directly through the app. My favorite is by far Cyanogen 6.1.2. The only downside is 4g isn't currently working. But the upsides by far outway that issue.
Sent from my PC36100 using XDA App

thanks and as we speak im doing a nandroid back up and want to know out of
myn's and calk's
which one is the best and if both of them work with 4g and i wanted to know if i do a nandroid backup will all my apps and contacts be deleted?

Both are good ROMs but every time I go try out a new ROM, I always go back to Calk's. I like it best but that's just my personal opinion. Once you feel comfortable flashing try them all out. I would reccomend using titanium back up to back up all of your apps though so when you flas a new ROM you can easily recover all your apps.

thanks and will it erase all my contact when i flash a new rom?? cause i already did an nandroid backup. and i want to download calks. SO whats my next step here. does calk work with 4g since i have htc evo 4g. sorry because im an amateur and dont know that much about this

Yes your contacts will be erased but once you log back in with your google acct they will resync. Yes, Calk's Rom supports 4G.
Download Calk's format all (not necessary but just something I personally use) & install it to root of the SD card
http://www.mediafire.com/?ikylelx99c49133
Same with the ROM, DL it to SD card root
reboot into recovery (vol down & power)
Factory wipe
Wipe Dalvik
Install zip from SD Card
Calk's format all
EViO v1.8
After it's done installing the phone will appear to hang a the splash screen This is normal for a first boot after a flash just let it do it's thing. It will eventually come up, I promise.
Enjoy your new ROM

one more thing and sorry to bother you how can i make sure all my contacts are with my gmail account

chotero said:
one more thing and sorry to bother you how can i make sure all my contacts are with my gmail account
Click to expand...
Click to collapse
by logging into gmail on your computer and checking "contacts". based on your questions, perhaps you should wait and research more before you dive into something that you can't get out of. you've been warned, just sayin. good luck though

Need to reinstall stock rom(maybe flashing a custom one)

Hello all,
I am running stock rom rooted, version .5.
Due to some FCs happening I want to reinstall the stock rom.
How should I do it?
I don't really remember..
My phone was unbranded when I bought it.
Just running the RUU of the latest stock rom will do the work?
Or do I have to unroot it firstly?
Also, I have created a partition (ext3 - 512MB) at my sd (8GB - Class 6)..and I would like to be able to install apps there...I think it's called A2SD..
How can I do that?
I am taking a backup with TB and will backup contacts and anything else I need.
Should I take a nandroid backup too?
Additionally, in order to decide which rom would be better for me, is there any way to try custom roms, such as running a virtual android device at my pc?
Thank you for your time!

To use the A2SD+, you need to be rooted.
So you can either run a RUU (unroots your phone - then root it again) or search the Android developement for stock rooted ROMs with A2SD+.
If you choose the 2nd one, just boot into recovery wipe everything and then flash the ROM and then restore everything with Titanium.
Here's a stock rooted one:
http://forum.xda-developers.com/showthread.php?t=773997
Nandroid is always good, does not hurts when you have a backup

Thank you for your reply!
To start with, I haven't flashed through recovery any rom yet and haven't wiped data, and thus I am really inexperienced with these.
So I could download this ->"2.29.405.2/5 INIT.D ROM v3.0 | v3.1 - NEW!"? (The version .5) with init.d so that I can install the script of A2SD+ ("A2SD+ (1.4) - v3 compatible", right?
Do I have to flash a radio too?
I think I've read here somewhere that if the radio you're having is working properly then stick with it..If I wipe everything will I still have to install a radio?
So if I download this version what are the steps that I should follow?
1)Backup everything I need with TB and nandroid.
2)Copy the file into the root of sd.
3)Boot into recovery.
4)Wipe everything->wipe data/factory reset + wipe cache partition?
5)And then which option is to flash the rom? The "install zip from sdcard"?
After this procedure what else do I have to keep in mind?
What about this "Additionally, in order to decide which rom would be better for me, is there any way to try custom roms, such as running a virtual android device at my pc?" ?

Yes, that's the ROM, and you will be able to use A2SD+ with the init.d ROM.
Radio is not needed. Even if you wipe everything, it remains, because it is on a different partition. So wiping everything is safe, radio remains.
The steps are good, but before flashing ("install zip from SD Card") make sure you toggle verification off (it's in the same menu) - just in case.
Altough I strongly recommend to run through those custom ROMs, you'll not regret it (If you choose a stable one from a well known dev).
Yeah, the virtual android emulator. Wanted to write about it, but forgot it after searching for the ROM I Know it is possible, never tried it.
Here are some links, tough:
http://forum.xda-developers.com/showthread.php?t=525930
http://android.modaco.com/content/general-discussion/289928/testing-getting-an-emulator-up-and-running-a-full-rom-with-the-market-etc/
http://android.modaco.com/content/general-discussion/289928/testing-getting-an-emulator-up-and-running-a-full-rom-with-the-market-etc/
http://androidcommunity.com/forums/f4/test-rom-before-flash-31617/

I have flashed the one with the init.d..but into Settings > data I can only see as internal memory 120+MB...
TB though shows the free data on the sd extern..
How can I be sure what is correct? :S
Also I tried leedroid and cyanogen mod for a little..but leedroid was partially tranlsated to greek and cyanogen mod does not have sense which I seem to have got used to it..
Also, about the emulation..I was stuck at a part where I have to create a system.img file of the rom...:S

1. try to do the three wipes.. wipe factory settings, wipe cache, wipe dalvik and then reboot. perhaps you won't have fc's after that.
2. if you run a stock ruu again - you will lose root and s-on will return. this is the way to unroot essentially. check unlockr for details on that. you can use a universal ruu from htc to do that if you have to. but if you try 1. first, then you won't have to do this. i would suggest NOT unrooting just for a few fc's.
you will solve the problem by installing a different rom. now onto that issue about app2sd...
if you want app2sd.. i would suggest looking into data2sd. i'm on rcmix-hd or rcmix-s-w.1.1 and it's very nice. if you want to use data2sd you can also add this feature. pm me about that. one proviso, your sd-card must be a class-6 or higher to really enjoy data2sd ... i have a class-4 and the speed is not bad. but as the card becomes fragmented, i am sure the speed will suffer.
good luck enjoy your desire.

I have done the 2 wipes except the dalvik cache before installing the rom.
I haven't used a stock RUU.
I have downloaded the v3 from here http://forum.xda-developers.com/showthread.php?t=773997 with init.d support.
I will stick with app2sd because I read that the sd wears off with all that writing :S
About the roms:
Yesterday I checked Leedroid but the thing that I didn't like was the partial localization..
I am using greek language.
Is there any way to solve that?
Also which other roms are more stable and worth the try?
Additionally, at the thread of the ROM I installed it says "Note that framework-res is already deodexed in this ROM".
This means that I can flash any notification bar icon I want and also the super cicle battery mod?
Thank you for your replies!

Anyone please? :S

pspuser007 said:
Additionally, at the thread of the ROM I installed it says "Note that framework-res is already deodexed in this ROM".
This means that I can flash any notification bar icon I want and also the super cicle battery mod?
Thank you for your replies!
Click to expand...
Click to collapse
With a deodexed rom you can apply global themes, fonts and mods.
With an odexed rom this is not possible, unless the mod is appropriately altered.

[Q] Update firmware on my rooted phone

Hello all this is my first post and im new to android so please excuse me as im a total noob!
I have a desire hd which is rooted, which was done by the guy i bought the phone off. It is running on Android 2.2.1, id like to update it to the newest firmware, but im not sure how I go about it. Ive been told I can't update from my phone because it's rooted?
Thanx in advance

IThere's loads of guides...if your rooted already...download rom manager,then open it..flash clockwordmod recovery at the top of the app choose your model.then go to android development section to look through the roms you want,download there zip file..for instance if its android revolution there's a download link for the Rom. When its download press on the item...then it'll ask how you want to open it,it'll take you to Rom manager..if you have data already on there just leave the wipe davlik and cache checked...it'll reboot and flash the Rom.
Remember there's sense and asop not worth flashing over the top of each..I'd flash sense for the meantime...eg. arhd,erebus runnydroid etc etc
Easy..
What he means by not being able to update is to official roms released by HTC...your better rooted anyway
As dn41 said you'll lose root by upgrading
Not advisable lol
It's a minefield to begin with bit worth it
If your on group or gingerbread and happy stick to roms with sense 3.0 like leedroid etc
Runnydrood etc runs sense 3.5 ported from sensation etc...( my opinion better but this differs amongst everyone)
There is miui as well but learn what's cracking first
Sent from my Desire HD using XDA Premium App

You're still able to receive updates but if you apply them, you will loose root permissions.
Why not flashing a costum ROM like ARHD?
Keep an eye on that, I really recommend flashing it
DN41

Thanx for the replys. Now i have some idea im going to nip on youtube and have a look at rom manager.
Thanx again
Liz

Just to clarify a few points made.
Your system partition has been modified, by rooting. Any and all OTA (Over The Air) updates will fail and possibly leave you stuck in a state of "soft-brick".
Here is the very latest Stock ROM from HTC. It has root but nothing else.
[ROM][DEC 8] Official RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1 STOCK ROOTED - The last post has a download link.
Give that a whirl for now.
To "update" to this firmware you will need to flash it via a custom recovery. There are a few available for the DHD. ClockworkMod Recovery (CWM) or 4EXT (Touch or Classic).
Always, always backup before you flash/wipe.
As you are coming from Android 2.2 to 2.3 I'd suggest you perform a full wipe.
Format /system , /data , /cache , /dalvic-cache - You can do this from within the custom recovery. Then install the ROM from the .zip. Be careful not to format your /sdcard!
Once you get to grips with what you have done, try the other ROMs available. Same procedure. Backup, wipe, flash.
I almost forgot, welcome to XDA!

Andy....thankyou
My phone has ClockworkMod installed, do I do the backup from that?
I hate being a newb lol, I've got loads to learn. I've switched from iPhone to android, I used to jailbreak my iphone which seemed a lot simpler lol
Liz

andyharney said:
Just to clarify a few points made.
Your system partition has been modified, by rooting. Any and all OTA (Over The Air) updates will fail and possibly leave you stuck in a state of "soft-brick".
Here is the very latest Stock ROM from HTC. It has root but nothing else.
[ROM][DEC 8] Official RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1 STOCK ROOTED - The last post has a download link.
Give that a whirl for now.
To "update" to this firmware you will need to flash it via a custom recovery. There are a few available for the DHD. ClockworkMod Recovery (CWM) or 4EXT (Touch or Classic).
Always, always backup before you flash/wipe.
As you are coming from Android 2.2 to 2.3 I'd suggest you perform a full wipe.
Format /system , /data , /cache , /dalvic-cache - You can do this from within the custom recovery. Then install the ROM from the .zip. Be careful not to format your /sdcard!
Once you get to grips with what you have done, try the other ROMs available. Same procedure. Backup, wipe, flash.
I almost forgot, welcome to XDA!
Click to expand...
Click to collapse
+1 lol...that's how my response should have looked
Sent from my Inspire 4G using XDA App

HTC G2 White Screen with Andromadus ROM 1.1.2

Hi All, let me start with a warning…
total Android n00b here, doing his first ROM flash on a newly rooted T-Mobile G2. I’ve read and searched a bit in the forum threads to see if I could solve this on my own, but I do need help.
VISION PVT SHIP S-OFF
HBOOT - 0.82.0000 (PC1010000)
MICROP - 0425
RADIO - 26.02.01.15_M2
eMMC - boot
Aug 20 2010, 16:51:01
This is from using the instructions in Strawmetal’s PDF guide to Downgrading from Gingerbread to Froyo and Root. I am working with a G2 phone that was set to Factory Reset before rooting, so there is no user data to backup or worry about.
1. I downloaded the Andromadus Mimicry 1.1.2 ROM image, and verified the md5 checksum on my sdcard using the AFV Legacy application. The Gapps image also was verified as well.
2. Using ROM Manager 5.0.0.8 from the Google Market, I ran Clockwork Recovery to install the Andromadus image. I left all settings on defaults and the installer ran fine.
3. When it restarted, I was left stuck at the white HTC screen for ages… the longest I left it was 20 mins. After that, I pulled the battery and restarted. Same white HTC screen.
4. I tried using Volume (+) key and Power On to get back to Clockwork Recovery, but the phone vibrated (buzzed) 3x times quickly, and the Power LED lamp pulsed an amber color. Again, yank battery, restart, same white HTC screen.
5. finally I decided to read more of the help for adb, and found the command “adb reboot-bootloader”. This let me get into the default Recovery mode, and it proceeded to find the PC10IMG.zip I still had on the sdcard from doing the Froyo downgrade. Recovery checked it out, ran it and restored the stock Froyo image and my phone did a proper restart. WHEW.
After that, I had to run adb to install the hboot recovery image file, and the busybox checksums were valid according to Strawmetal’s PDF instructions to get permanent root back after restoring the stock Froyo image.
I have done this process about 4 times, and am really good at typing inside adb now
But I’m lost…
-did I pick a ROM that doesn’t work with the G2? Other posters to the forum thread appear to be using the HTC Vision or G2.
-is ROM Manager not a good way to install a ROM?
-when I tried to get back into Recovery, what do the 3x buzzes/amber power LED mean?
-I never got to install the Gapps image; was I supposed to install that first, then the ROM image?
I imagine I did something wrong (duh!), but I can’t spot it. If someone can help me through this, I’d appreciate some advice very much.
thanks!

Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).

Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium

Hi Nospin,
Thank you very much for your suggestions!
I will revise my root and remove Clockwork, and switch to 4EXT instead.
I appreciate the idea of "superwipe"; I will look for that as well today.
If I understand everything right...
-replace CWM with 4EXT
-place superwipe.zip, Gapps.zip and the Mimicry ROM.zip on the top level of the sdcard first.
-reboot the phone and run 4EXT recovery
-select superwipe to run first, then the ROM and then Gapps
-then restart the phone
When I used CWM before to install the ROM, it rebooted on its own before I could install Gapps. Will 4EXT let me do each install right after each other or do I have to return to 4EXT for each separate install?
regards,
motionmonk
Nospin said:
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Click to expand...
Click to collapse

Hi blk_jack,
I went back to the Mimicry page and re-read the FAQ section.
I think what I got out of it the first time was that if the ROM flash failed, it could be a corrupt ROM image. I will definitely use 4EXT to repartition before I try again with a ROM flash.
I guess I am still getting used to the terms for everything; can 4EXT do the nandroid backup? or is there a better process for setting that up?
thank you!
motionmonk
blk_jack said:
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Yes, you should be able to flash the rom and then GApps without rebooting. Give me a few and I will send you a PM with a few links....

Shot you a PM.

Thanks! I'll check it out :good:
Nospin said:
Shot you a PM.
Click to expand...
Click to collapse

Update-not working
Ok...
I re-flashed back to stock Froyo, and did a permanent root.
Installed 4ext Recovery (instead of Clockwork), and got a copy of SuperwipeG2+ext4;
I copied new checksum'd copies of Mimicry 1.1.2 ROM and GApps to my sdcard.
Booted into 4ext Recovery and installed from .zip the SuperwipeG2+ext4 file.
System, data and cache are all converted to ext4 partitions.
Wiped the system and data and cache partitions.
Installed from inside Recovery the Mimicry ROM and then the GApps archives.
No errors reported.
Upon reboot, I still get the white HTC screen. UGH.
I've left it on in that state for 30 mins... I had to yank the battery after that in shame...
I have tried to make sure that I read up on background steps, and I feel I do understand the overall process, but something is still getting in the way. I am doing this as I mentioned in an earlier post on a factory reset G2 with a clean erased SD card (has the stock Froyo image, Andromadus Mimicry ROM and GApps only). There is no SIM card installed either, wifi is off (to avoid OTA upgrade requests).
Are there other things I can try, or info I can supply that would help? I think I'm so close to getting this done... I must be overlooking something obvious.

I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium

Hi amogil,
Just to be sure I understand, are you saying you are swapping between Andromadus and CM9 beta on your phone?
Did you flash CM9 first? and then Andromadus?
or just carrying the CM9 beta image and running Andromadus?
Sorry, I'm all sorts of confused here lol
thanks
amogil said:
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....

It's definitely a thought, and I believe that's what amogil is telling me too...
Ya, I can try a different ROM and report back.
I guess I should go back to stock Froyo and then start from CM7.2, and if that boots, try Mimicry again?
-from the Andromadus FAQ, it says it if a different ROM is based on ICS9, you shouldn't have to wipe. But with CM7, I'd have to wipe the Dalvik cache, yes?
-since CM7 is obviously not based on ICS9, would being able to launch into that show some details I can't see at present? Just was curious.
Or, do you think it better to go stock Froyo and then the older Mimicry ROM?
Either way, I'll make sure that I use the Superwipe to set things to ext4 first.
thanks guys for the ideas,
motionmonk
Nospin said:
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
Click to expand...
Click to collapse

The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium

SUCCESS!
Woohoo!
It works!
Since I had an ICS9 ROM already in place and was planning to wipe back to stock anyways, I tried flashing the older Andromadus 1.1.0 ROM.
What a surprise and treat to see the startup animation!
After poking around for an hour inside it, I then tried Recovery to reflash to the newest 1.1.2 ROM.
YAY! It works!
OMG, having a new ROM is like having a new phone-- there are so many improvements to the UI and it's quick and speedy versus GB. Dang, I'm happy now :victory:
Observations:
1. I did notice that inside Recovery, my touchscreen was barely functional when I tried to update from 1.1.0 up to 1.1.2-- I had to use the Volume +/- and the d-pad button to make selections. After the flash, the touchscreen is as responsive as ever.
2. it's got me thinking, that there must be a setting that is expected in the v1.1.2 ROM that the v1.1.0 ROM installed. Or could something else be the issue? I mean absolutely no disrespect to the developers... but on the technical side, I'm just curious what possibilities exist that might lead to this situation.
3. backup question... when I use MyBackup Pro, I know I can make an archive of the apps I've installed, and an archive of the data (documents, music, settings). Is a nandroid backup different from that? when I see the backup/restore options inside of 4ext Recovery, what are those doing that's different from what I get from MyBackup Pro?
thanks for all the help and encouragement. I have a new ROM installed! :good:

strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Oooh, a possibility. We will see if he can boot a different rom.
Whenever you switch roms (even if they are using the same Android version as a base) I suggest a full wipe. (Wipe all user data + Dalvik Cache + Cache, or just flash the superwipe zip). When upgrading the rom you are currently on (say upgrading CM Nightlies or going from Mimicry 1.1.1 to 1.1.2) you only need to really wipe cache and dalvik cache. Unless the dev states otherwise of course.

Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Thank You All!
A big shout out to:
Nospin
blk_jack
amogil
strawmetal
for taking the time out to help a total n00b stumble through his first ROM flash.
I really appreciate the points you guys made, and the help provided.
Thank you!
I hope that one day I can help someone else out with a problem and pass the kindness forward.
Yay! I have a working ROM!
motionmonk

motionmonk said:
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
Click to expand...
Click to collapse
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.

WOW. i just realized there is SO MUCH I need to catch up on!
I'll have to look up some of these guides later today... but the RUU is the ROM upgrade, right?
Did you ever find a reason why you got the false S-OFF flag? It's clear that the way I was looking at the failed fre3vo exploit as proof of S-OFF isn't always going to be true... but how would you separate a false S-OFF flag from lets say a wrong hboot image?
BTW, your PDF on downgrading and rooting the G2 was a godsend. Very very helpful and clear.
One of the reasons why I took so long to try rooting was that I was confused by the different methods and the replies of X not working, Y is a better way... going through your guide and the info here on xda cleared alot of things up. :good:
strawmetal said:
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
Click to expand...
Click to collapse