Develop Bugs

[Q] Help! Stuck on white HTC screen after installing root!

So I installed CWM recovery, and installed the rmk root setup zip. Before I installed it, I wiped the cache but not the Dalvik cache. When I rebooted, it hung on the white HTC screen. I went back into recovery and wiped dalvik cache, cache and even data and settings, then installed the zip again and it still hangs. can somebody help me? Honestly at this point I just want to be able to use my phone again.
Thanks in advance

Did you install the root zip that included the froyo stock kernel? I made the same mistake. Just have to adb a compatible 2.3 kernel into your sdcard and flash it.
Sent from my Incredible 2 using XDA App

http://forum.xda-developers.com/showthread.php?t=1160745
i'm pretty sure this is the zip i used. if thats what you're talking about, then how do I fix it?

You cant use that .zip because it uses the Froyo kernal which is incompatible. You have to push jcase's GB kernal to your sd card then flash that.

I'm sorry for the stupid question, and thank you so much for your help, but where can i find that? and what commands do I use to push the kernel to the phone?

Have no fear as long as you can get into CWM then you are still good.
How long does it hang, sometimes it takes a few minutes for that HTC screen to go away, especially if you wiped data. you might want to wait, a little bit.
You can always download a stock rom(jcase plainjane rom), get into CWM, and then mount your USB to be able to install from your computer, and then flash the new rom.
Did you make a backup before you flashed the update, you can always recover.

DalekCaan said:
I'm sorry for the stupid question, and thank you so much for your help, but where can i find that? and what commands do I use to push the kernel to the phone?
Click to expand...
Click to collapse
If you can get into CWM, look for Mounts/Storage and mount your USB so you can access your Phones SD card from your computer, then transfer the file from your computer to your phone.
or use adb if you are familiar with that.

you did get S-Off first right?

yes i have s-off, no i did not make a recovery (i wasnt aware i could do that before i rooted but i have come to terms with the fact that I lost a bunch of data).
okay, so i put the file on my sd card and... what? is it a zip file? where can i find it?
just so i understand, once I get this rooted kernel, i will be rooted and i will be able to install the cwm app and go from there?

and i don't necessarily want the stock rooted... i guess i could go from there but for right now could i download a 2.3 kernel with a different rom? are kernels bundled with roms or do i need to install them separately?
sorry, i'm a new user so i keep having to wait 5 minutes...

Kernels, can be rom specific or bundled but currently for the dinc2 there arent a lot so make sure it doesnt say it belongs to a specific rom otherwise it might not work.
Jcase has a stock kernel and rom he put up a while back for gingerbread.
They will be a .zip file and all you have to do is using recovery choose zip file and run it, since you already deleted everything.
When you install a rom, it will add su and busybox, and root your phone. You need your phone rooted to be able to do anything, after S-off.
if you have recovery installed then you have CWM and really what you want is Rom Manager to do backups.

can i flash the tiamat kernel? do i still have an OS? will that fix things?

DalekCaan said:
can i flash the tiamat kernel? do i still have an OS? will that fix things?
Click to expand...
Click to collapse
tiamat kernel is an AOSP kernel. for CM7/MIUI/OM(F)GB
you'll get bootloops if you flash it on a sense rom.

so should i flash that, then flash something like MIUI? can i do that? and do i have to wipe data/cache/dalvik before the kernel AND before i install MIUI?
thanks

DalekCaan said:
so should i flash that, then flash something like MIUI? can i do that? and do i have to wipe data/cache/dalvik before the kernel AND before i install MIUI?
thanks
Click to expand...
Click to collapse
I would get a Rom working first which is your OS, the kernel jut says how it should run.

but apparently i have a froyo kernel installed right now? how should I fix that?

http://forum.xda-developers.com/showthread.php?t=1191836
here is a link for a gingerbread kernel...try that first

dj_wires said:
http://forum.xda-developers.com/showthread.php?t=1191836
here is a link for a gingerbread kernel...try that first
Click to expand...
Click to collapse
If you install a new rom, it will overwrite whatever kernel you have, so you might just want to install this....
http://forum.xda-developers.com/showthread.php?t=1161411
this is the first gingerbread rom i used...not a lot to it.

I'll try that thank you so much! i just have to go to "install zip from sd card" once i put it on my sd card?

DalekCaan said:
I'll try that thank you so much! i just have to go to "install zip from sd card" once i put it on my sd card?
Click to expand...
Click to collapse
Yup!
Good Luck!

[Q] Need help with CM7

So im planning to go back to 2.1 or 2.2 and sense, so how im going to do this? ( I have #203 Nightly)
After that, will i need to root again, and is it possible to overclock stock wildfire ROM and how? (Install new kernel??)
If youre asking why go back to sense, I just happen to need stableness for next 4 weeks and want to see how much I can tweak Sense. Going back to cm7 in november probably
Mipe

Just install like a new ROM. One such stock rooted Froyo can be found here:
http://forum.xda-developers.com/showthread.php?t=877977
The only different thing is that this will have to be flashed in Clockworkmod 2.x. (I guess you must know how to flash Radio's in CM7, so its not a big issue)
And yes, to OC, you will have to install a custom kernel like this one:
http://forum.xda-developers.com/showthread.php?t=995301

3xeno said:
Just install like a new ROM. One such stock rooted Froyo can be found here:
http://forum.xda-developers.com/showthread.php?t=877977
The only different thing is that this will have to be flashed in Clockworkmod 2.x. (I guess you must know how to flash Radio's in CM7, so its not a big issue)
And yes, to OC, you will have to install a custom kernel like this one:
http://forum.xda-developers.com/showthread.php?t=995301
Click to expand...
Click to collapse
I also found that i have cwm backup from original rom that I can restore. Does this also restore previous radio or kernel or do I have to do it manually?

it will not touch the radio, but it will restore the stock kernel. (Or whichever kernel you had installed when you took that backup)

3xeno said:
it will not touch the radio, but it will restore the stock kernel. (Or whichever kernel you had installed when you took that backup)
Click to expand...
Click to collapse
I got a problem. I want to get original Sense by restoring backup from CWM. Mine works, but has a pattern that i dont remember and a email wich i dont remember either. Does anyone happen to have a backup of a wildfire without password or could someone advice something else? I tried RUU but my win7 x64 is causing trouble, or the drivers.

Just flash the stock froyo ROM I listed in the first post I made in this thread (http://forum.xda-developers.com/showthread.php?t=877977). If you don't know how to get Clockworkmod 2.5.0.x, then:
- Download this attachment, place on your SDCard:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
- Flash the zip (update1.zip) using your existing Clockworkmod 5.0.2.0
- Device will reboot and will start Clockworkmod 2.5.0.7
- Perform Data Wipe and Choose Install Zip from SDCard, select the ROM Zip file, and let it install.

3xeno said:
Just flash the stock froyo ROM I listed in the first post I made in this thread (http://forum.xda-developers.com/showthread.php?t=877977). If you don't know how to get Clockworkmod 2.5.0.x, then:
- Download this attachment, place on your SDCard:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
- Flash the zip (update1.zip) using your existing Clockworkmod 5.0.2.0
- Device will reboot and will start Clockworkmod 2.5.0.7
- Perform Data Wipe and Choose Install Zip from SDCard, select the ROM Zip file, and let it install.
Click to expand...
Click to collapse
For the rooted ROM it says No Hboot | No Radio, what does that mean?

jediknight111 said:
For the rooted ROM it says No Hboot | No Radio, what does that mean?
Click to expand...
Click to collapse
Just what is says. It does not include the Bootloader (HBoot), and it does not include the baseband (Radio). So, for these two components, what you are having on your device at this moment will remain. (ie - They will not be updated when you flash the ROM)

3xeno said:
Just what is says. It does not include the Bootloader (HBoot), and it does not include the baseband (Radio). So, for these two components, what you are having on your device at this moment will remain. (ie - They will not be updated when you flash the ROM)
Click to expand...
Click to collapse
I Installed the Rom from recovery, but all I get is the HTC logo and the startup tone then it switches off and I get the same thing again. Help please!
Edit: It's working now but I cannot force move apps like I could do before. Why is that?

jediknight111 said:
I Installed the Rom from recovery, but all I get is the HTC logo and the startup tone then it switches off and I get the same thing again. Help please!
Edit: It's working now but I cannot force move apps like I could do before. Why is that?
Click to expand...
Click to collapse
Because it is a Completely Stock HTC Factory ROM with no support for it.

[PROBLEM] Desire isn't loading ROMs

Hi to all, I am new into this and need some help
I admit it, I am a noob
So, this is my phone state.
I have rooted my HTC Desire with Revolutionary and I have ClockworkMod 5.0.2.0. on it. I had official Gingerbeard update before I rooted my phone.
My problem is that I can't install any roms. The only one that works is CyanogenMod 7, and I wish to use other rom. I can't install official roms from my computer too, because of custom is currently installed (I think that is the reason).
Everything looks good when I try to flash roms. Wiping cash & factory reset is going well, then I select install .zip from SD, that goes well too. I wait some time and it says that flashing was successful.
Problem starts when the phone should load rom. It goes up to HTC animation, and then the animation is constantly repeating, and it won't load rom. I made a huge mistake when I forgot to make Gingerbeard nandroid backup, and now the only thing I can run is CyanogenMod.
Any help is welcome

bundo111 said:
Hi to all, I am new into this and need some help
I admit it, I am a noob
So, this is my phone state.
I have rooted my HTC Desire with Revolutionary and I have ClockworkMod 5.0.2.0. on it. I had official Gingerbeard update before I rooted my phone.
My problem is that I can't install any roms. The only one that works is CyanogenMod 7, and I wish to use other rom. I can't install official roms from my computer too, because of custom is currently installed (I think that is the reason).
Everything looks good when I try to flash roms. Wiping cash & factory reset is going well, then I select install .zip from SD, that goes well too. I wait some time and it says that flashing was successful.
Problem starts when the phone should load rom. It goes up to HTC animation, and then the animation is constantly repeating, and it won't load rom. I made a huge mistake when I forgot to make Gingerbeard nandroid backup, and now the only thing I can run is CyanogenMod.
Any help is welcome
Click to expand...
Click to collapse
go to mounts and storage and format everythign apart from sdcard. then flash again.

That finally solved my problem
Thank you very, very much

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

[Q] Need Help, Phone stuck on boot up

I have had Cyanogenmod 7 for some time now, but ever since yesterday it is stuck on the Cyanogenmod boot screen and does nothing. I can get into Clockworkmod Recovery, but I am scared to do anything past that for fear of messing something up. Do you all know something I could try to get my phone back working (It is an HTC Inspire on AT&T)
Thanks

Ellimistopher said:
I have had Cyanogenmod 7 for some time now, but ever since yesterday it is stuck on the Cyanogenmod boot screen and does nothing. I can get into Clockworkmod Recovery, but I am scared to do anything past that for fear of messing something up. Do you all know something I could try to get my phone back working (It is an HTC Inspire on AT&T)
Thanks
Click to expand...
Click to collapse
Do you remember anything that happened/changed between when it was working and when it wasn't? S-ON or S-OFF?
Since you can get into CWM, I would just flash a new ROM. In fact, I would first dirty flash the same ROM over the one you've got first to see if that fixes it. If that doesn't work, clean flash a different ROM.

bananagranola said:
Do you remember anything that happened/changed between when it was working and when it wasn't? S-ON or S-OFF?
Since you can get into CWM, I would just flash a new ROM. In fact, I would first dirty flash the same ROM over the one you've got first to see if that fixes it. If that doesn't work, clean flash a different ROM.
Click to expand...
Click to collapse
What's the easiest way of going about this, I haven't ever done anything past the initial root and flash

Just put the ROM to be flashed on the SD card, it's a zip - and then choose to "install from zip" and navigate to it in Recovery. You could find a superwipe .zip file - which cleans all caches etc - on this forum, and that will give you the assurance that your phone is squeaky clean for when you flash the ROM zip file.
Just make sure your phone is - preferably - fully charged. The only thing that can go wrong is the battery running out while flashing .
If for whatever reason it still doesn't get past the bootloop, re-flash or try flashing a different ROM.
There are plenty of really good ROMs for the HD in the ROM sub-forum, for a rock-solid alternative, look at the Android Revolution ROMs.

Ellimistopher said:
What's the easiest way of going about this, I haven't ever done anything past the initial root and flash
Click to expand...
Click to collapse
Download the ROM (make sure it's the exact same version as the one you first flashed) onto your computer. Get the ROM onto your phone, either by using an sdcard adapter or by booting into CWM and mounting the sdcard on the computer. In CWM, wipe cache and dalvik, then install the ROM zip. Reboot. (If you're S-ON, say so; there are a couple extra steps.)
If that doesn't work, do it again with a different ROM. Also, instead of wiping only cache and dalvik, also wipe system and data. You will lose all your installed apps and saved data.
Sorry, but I can't give exact step-by-step CWM instructions because I don't use CWM.

So all I did was reflash the exact same file that I already had on my SD card, and that worked. Cleared the data/caches and I'm back online. Thanks for the help.