Develop Bugs

Stuck at boot screen, help please

I just installed cyanogen 6.1.1 for my first time on my phone everything went correctly and then when it went to boot up its stuck at the boot screen. What do I do???

Someone plzzz help idk what to do???

Sinistah_ said:
I just installed cyanogen 6.1.1 for my first time on my phone everything went correctly and then when it went to boot up its stuck at the boot screen. What do I do???
Click to expand...
Click to collapse
Sinistah_ said:
So I just installed cyanogen 6.1.1. And its stuck at the boot up screen... what do I do????
Click to expand...
Click to collapse
Please do not start new threads when people are trying to help you. Wait patiently for an answer before starting a new one. You have started 4 threads already about rooting your phone and the problems you have. Invest some time in reading, learning and understanding the wikis. Thank you.

Sorry. I'm just paniking for the fact my phone is stuck on the boot screen and I'm jusst trying to get help asap. And actually the other thread was about if my phone was rooted so this thread is on another topic.

Are you still able to boot into recovery? And if so, what is displayed in your screen?

So I took the battery out, put it back in.. held power and the volume button it took me to where it says s-off n did a system recover. It worked!!! Haha... now I wanna try again but can u tell me what I did wrong??? I downloaded the cyanogen 6.1.1 and just started it up with the google stuff. It rebooted did its thing n stayed at the boot screen... am I supposed to clear something?? I read somethin like that when I was on google with my gfs phone. (I'm out somewhere... made me panik more since I don't have access to a computer atm)
Sent from my T-Mobile G2 using XDA App

Which version of ClockworkMod are you using?
Since you trie to flash a CM6.1. rom (which is froyo, android 2.2 based) you must use a ClockworkMod 2.5.x or below (or compatible).
And did you install Engineering HBoot? Sorry for asking, but it's unclear to me what you exactly have been doing already.

I did the visionary/gfree root last night without the hboot. And I tried the cyanogen 6.1.1 which was suggested by another user on here in one of my threads.
Sent from my T-Mobile G2 using XDA App

Btw my clockworkmod says 3.0.0.5
Whatever version that was on the market is the one I downloaded.
Sent from my T-Mobile G2 using XDA App

Apart from the fact that it seems to me that you skipped a step (hboot), which you have to perform , you are also trying to flash a 2.2 rom with the wrong recovery. Try with the 2.5 version in the thread http://forum.xda-developers.com/showthread.php?t=898151

HLeenders said:
Apart from the fact that it seems to me that you skipped a step (hboot), which you have to perform , you are also trying to flash a 2.2 rom with the wrong recovery. Try with the 2.5 version in the thread http://forum.xda-developers.com/showthread.php?t=898151
Click to expand...
Click to collapse
First of all, flashing the engineering HBOOT is not required unless you want to use fastboot on your computer. Also, if you used ROM Manager to flash ClockworkMod Recovery, that version is supposed to support both 2.2 and 2.3 ROMs. It was only the beta version of the recovery that was on this forum that only supported 2.3 and not 2.2---unfortunately, it was also labeled 3.0.0.5 and caused lots of confusion).
As far as why you are stuck at the boot screen, did you wipe data/cache when you flashed the ROM? Whenever you switch to a completely different ROM (as opposed to simply upgrading one), it's a good practice to. Also, the first time you start a new ROM, it'll take longer to boot up since the phone will be rebuilding its dalvik-cache (on CM6.1, it's be at a CM animation).

Ahh yeahhh okay good. So u cleared it all up for me n now my phone is running great
Sent from my HTC Vision using XDA App

MIUI: Stuck on BOOT

Yesterday, I decided to flash a MIUI (beta) rom, but I am stuck on the 'shiny android boot loading screen'. Before flashing the ROM I had Wiped all user DATA/CACHE/DALVIK-CACHE/EXT and all other as well as formatting my SD card to the following:
HTML:
Swap Size: 0MB
EXT 4: 1GB
No matter what I do, whether it's pulling out the battery and leaving it or wipe cache again it just gets stuck on the same old boot screen doing nothing.
Here are my phone specs:
HTML:
S-OFF PVT1 Revolutionary
HBOOT-6.93.1002
RADIO-5.17.05.23
I know I dob't have USB Brick because it works fine and I can boot into Recovery and Bootloader/FastBoot. I don't understand why this has happened as I had flashed a MIUI ROM 2 months agao and everything went well, it could be that my H-BOOT is different or I have S-OFF.
Please help me resolve this issue.
Many Thanks.

Latest version happened to do the same for me.
I just flashed it a couple of times. It works now.
The strangest thing was, that it was no bootloop or any error - it just sat there for infinity.

Does the Rom require a different hboot? Or might it need an ext 3 partition?
Sent from my HTC Desire using XDA App

davebugyi said:
Latest version happened to do the same for me.
I just flashed it a couple of times. It works now.
The strangest thing was, that it was no bootloop or any error - it just sat there for infinity.
Click to expand...
Click to collapse
Yes, that is what is happening here, but I flashed it several times and no go. The setup seems so quick to be installed...it only lasts 40 seconds and says it's complete.
ste1164 said:
Does the Rom require a different hboot? Or might it need an ext 3 partition?
Click to expand...
Click to collapse
I have no idea, surely not?

I have alpharev sense HBOOT, but MIUI should work with all others (except for oxygen/oxygenr2)
I'd recommend to download the .zip again and check md5 sum - then flash again.

Which version of MIUI is it that you flashed?
Mine has to have an EXT3 partition or it wont work ..

EDIT:
/facepalm
I can't believe I expected the ROM to be installed just by flashing the 'Pack' which I didn't reliase is just an language pack. I thought the term 'Pack' meant everything including the ROM, lol.
ISSUE Ressolved. Thanks anyways guys.

Deeco7 said:
... Ressolved...
Click to expand...
Click to collapse
And this to your topic's name to help others.

Aha I'm glad you solved it.
Sent from my HTC Desire using XDA App

I am Desperate with this HTC Desire

Hello guys !
First of all i want to say that I've tried EVERYTHING around to resolve the issue, but it seems that nothing is working. So long story short :
My friend bought used HTC Desire since i own DHD and he liked it alot but didnt have the money to buy DHD ,so the day he got it he tried to root it , He said that it was sucessfully and he instaleld some custom rom and went to bed,when he woke up in the morning his Desire Display was flashing with the boot animation(the ROM one) over and over again.He treid to install other ROM and the effect was the same,stuck at animation repeating over and over again.So He called me,i got to his house and tried to solve the issue but i didnt have luck there ,so i got the phone with me at my home. I started digging where the problem was...i was sure it was the rom ,tried to install 5-6 oter roms - no luck . Tried to flash with RUU- no luck ,kept getting " The main version is older" error . So i kept digging and tried to install the RUU throught H-boot by making PB99IMG.zip file,got the same error.Tried to use the update.zip solution - still no luck.Tried to change the recovery from clockwork to any other recovery ,but didnt have luck since i cant access the android and i am getting errors if i try to archive the file to update.zip.
So i need some help if its possible,sorry for my english and if the info that i provided is not that good ask me whatever u like.
also in The H-boot menu it says :
BRAVO PVt4 Ship S-ON
H-Boot-0.93.0001
MICROP-051d
TOUCH PANEL - SYNT0101
RADIO-5.11.05.14
from what i got by reading is that i cant s-off cuz of the bravo pvt4 ..

Did you wipe data after flashing?

localh0st said:
Did you wipe data after flashing?
Click to expand...
Click to collapse
Full wipe + wipe from the advanced menu !

Lol, read thru the OP and same thing going over and over in my head "Did you wipe? Did you wipe? Did you wipe?"
When you start out with "I've tried EVERYTHING", make sure you actually did try everything, because it's pretty obvious you didn't.

Did it also display flash bootanimation over and over again after Ruu?
Sent from my HTC Desire using XDA

vladrak said:
from what i got by reading is that i cant s-off cuz of the bravo pvt4 ..
Click to expand...
Click to collapse
Have a read of this

localh0st said:
Did you wipe data after flashing?
Click to expand...
Click to collapse
You have to wipe BEFORE flashing, not after.
Some Roms store important parts on /data, which will be erased during the wipe.
Sent from my HTC Desire using xda premium

Tillus said:
You have to wipe BEFORE flashing, not after.
Some Roms store important parts on /data, which will be erased during the wipe.
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
This is true lol. If you install then wipe you prob won't be able to get further than the boot screen.
Sent from my HTC Desire using xda premium

Take it your mate didn't take a nandroid back-up before trying to flash, so he could restore it in case any issues occurred? Have you done full wipe then tried flash ROM from recovery then? Does the ROM need an ext partition - will boot loop if one doesn't exist.
Depending on the HBOOT version, using alpharev or revolutionary will S-OFF PVT4s - but this isn't the solution to your current problem unless you're trying roms that need non-stock hboots, in which case try something that doesn't first. S-OFF via AlphaRev also best done with rooted stock ROM, some custom sense ROMs also seem to work (don't know about revolutionary as i took alpharev route) - but get custom ROM running first before thinking about doing anything else.

JustAnotherCider said:
This is true lol. If you install then wipe you prob won't be able to get further than the boot screen.
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Dude i wiped all b4 installing any rom, anyways i finally fixed it,been trying for 2 days ,I'll explain in the next post !

beachcomber said:
Take it your mate didn't take a nandroid back-up before trying to flash, so he could restore it in case any issues occurred? Have you done full wipe then tried flash ROM from recovery then? Does the ROM need an ext partition - will boot loop if one doesn't exist.
Depending on the HBOOT version, using alpharev or revolutionary will S-OFF PVT4s - but this isn't the solution to your current problem unless you're trying roms that need non-stock hboots, in which case try something that doesn't first. S-OFF via AlphaRev also best done with rooted stock ROM, some custom sense ROMs also seem to work (don't know about revolutionary as i took alpharev route) - but get custom ROM running first before thinking about doing anything else.
Click to expand...
Click to collapse
Just saw your post. Too bad it's too late. Anyways the situation was kinda funny: So the HTC kept booting untill the "rom logo" (You know the logo after the HTC one), tried to install other ROM's (Full wipe before ofcourse) and it didn't work ofcourse, so I kept digging and i saw some threats where people were saying that clockwordrecovery wasn't working with my version h-boot, ah and trying installing RUU didnt work too(also trying to install PB99IMG.zip from sdcard didnt work too) ,was always getting "The main version is older" error! So we flashed AlphaRev, and finally the phone was S-Offed, after this i got my DHD's sd card since it was a gold card and i put it into the Desire , i had a PB99IMG.zip file from the previous day on it! So i started the bootloader, it detected the PB99IMG.zip file and I didn't get the "Main Verison is older" error, it asked if the file should be updated and i pressed "yes" and the phone gone off...guess what it was compleatly bricked,only vibrating and the screen didn't work....we were like OMG WTF ...so we installed SDK tools and started looking for adb commands/guides ...after 4 hours we were on about to quit and suicide ourselves cuz we didnt get anything and it was getting late...i was like " duh,lets blind try the PB99IMG.zip method again and rest till tomorrow" ,i downloaded the newest PB99IMG.zip from shipped-roms.com ,got it on my sd card and got the sd card back in the desire . Pressed Power + vol down,waited 2 mins and pressed vol up again,waited like 10 more mins,nothing happaned...we got all emo and mad ,2 more friends of us came to my mate's flat ( they are not into phones or anything ,complete noobs),one of them got the phone took of the baterry and the sdcard ,put the baterry back,pressed Power ON button and the phone ****ing started ....we all were like WOOOOOOOOT OMG OMG ,it was like magic xD ...so its fixed now and it has the stock rom and its unrooted...

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

Droid Incredible (CAN'T GET BACK TO STOCK!)

I have a Droid Incredible on CM7.2.0
Android Version: 2.3.7
Baseband Version: 2.15.00.07.28
Kernal Version: [email protected]
I am S-OFF now, I followed this: http://www.incredibleforum.com/foru...s/5723-how-get-back-complete-stock-s-off.html
Tried flashing the PB1IMG through bootloader, shows the blue loading bar on the right side, fills all the way up, then it disappears with no option of pressing volume up to update.
I then tried downloading the RUU and HTC Sync and doing it that way, and I got ERROR 155 every time I tried doing it.
I have to send the phone out to someone who bought it in the next couple days and I need it to be back to stock.
I have no Nandroid backups of the original ROM.
Is the fact that I have CM7 not allowing me to use the RUU?
I really need to get back to stock guys.
Please help me out!

ogkhaze said:
Tried flashing the PB1IMG through bootloader, shows the blue loading bar on the right side, fills all the way up, then it disappears with no option of pressing volume up to update.
Click to expand...
Click to collapse
That sounds like you have a damaged PB31IMG.zip. Try downloading it again and checking the md5sum before attempting to flash it.
Is the fact that I have CM7 not allowing me to use the RUU?
Click to expand...
Click to collapse
No.

musical_chairs said:
That sounds like you have a damaged PB31IMG.zip. Try downloading it again and checking the md5sum before attempting to flash it.
No.
Click to expand...
Click to collapse
Do you know where I can grab a stock..unrooted 2.3.4 to flash as a PB31IMG to get back to stock? This is pretty urgent.
Or, what would be causing the RUU to fail??

ogkhaze said:
Do you know where I can grab a stock..unrooted 2.3.4 to flash as a PB31IMG to get back to stock? This is pretty urgent.
Click to expand...
Click to collapse
There are a bunch of stock images here:
http://dinc.does-it.net/Stock_Images/

musical_chairs said:
There are a bunch of stock images here:
http://dinc.does-it.net/Stock_Images/
Click to expand...
Click to collapse
Thanks I'll try the 4.08.605.2 PB31IMG and report back here.

Tried that, the loading bar went up very slowly on the right side again, and the went away...
Says "No image or wrong image" then back to the bootloader screen...
WTF is going on!

ogkhaze said:
Tried that, the loading bar went up very slowly on the right side again, and the went away...
Says "No image or wrong image" then back to the bootloader screen...
WTF is going on!
Click to expand...
Click to collapse
You are on the original incredible right? Only other thing i could think of is there is an error on your sdcard. Use a pc to format it fat32 and then try again with this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.

cmlusco said:
You are on the original incredible right? Only other thing i could think of is there is an error on your sdcard. Use a pc to format it fat32 and then try again with this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.
Click to expand...
Click to collapse
I tried formatting my SD card today already and that didn't do the trick...
I'm starting to think I have the SLCD Incredible...
In that case, how do I get it back to the original state...if I still can?

cmlusco said:
You are on the original incredible right? Only other thing i could think of is there is an error on your sdcard. Use a pc to format it fat32 and then try again with this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.
Click to expand...
Click to collapse
Glad to see you still here helping folks out
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

wildstang83 said:
Glad to see you still here helping folks out
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Yeah guys, thanks for helping me out, I know all support / dev for this phone is pretty much shot.
Just gotta get it sent out sometime this week, and it's stuck on CM7.
I know AMOLED is 002 and SLCD is 003 but I can't find where you look for that number, I checked in about phone, and at bootloader.
I just find it odd that I can't use a image to flash through bootloader or use the RUU, hmm..

ogkhaze said:
Yeah guys, thanks for helping me out, I know all support / dev for this phone is pretty much shot.
Just gotta get it sent out sometime this week, and it's stuck on CM7.
I know AMOLED is 002 and SLCD is 003 but I can't find where you look for that number, I checked in about phone, and at bootloader.
I just find it odd that I can't use a image to flash through bootloader or use the RUU, hmm..
Click to expand...
Click to collapse
It dosent matter if your amoled or slcd, all ruu's since froyo 3.26.605.1 are compatible with both.
Have you tried reflashing hboot?

cmlusco said:
It dosent matter if your amoled or slcd, all ruu's since froyo 3.26.605.1 are compatible with both.
Have you tried reflashing hboot?
Click to expand...
Click to collapse
Roger, I'm downloading the image you linked me too and I'll give it one more shot.
Here's the information in in bootloader just incase I'm missing something here.
*** UNLOCKED ***
INCREDIBLEC XD S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.28
If that image file doesn't work, is there any sort of "last straw" methods I can use for getting this back to stock, or at least a Sense ROM that LOOKS stock. I can't even flash a different ROM without the phone being stuck at the white HTC Incredible splash screen...

ogkhaze said:
Roger, I'm downloading the image you linked me too and I'll give it one more shot.
Here's the information in in bootloader just incase I'm missing something here.
*** UNLOCKED ***
INCREDIBLEC XD S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.28
If that image file doesn't work, is there any sort of "last straw" methods I can use for getting this back to stock, or at least a Sense ROM that LOOKS stock. I can't even flash a different ROM without the phone being stuck at the white HTC Incredible splash screen...
Click to expand...
Click to collapse
The image i gave you should work. If it dosent you can fasboot flash cwm recovery, flash su thru recovery, do a full wipe thru recovery, and then flash the 4.08.605.15 stock odexed rom.

cmlusco said:
The image i gave you should work. If it dosent you can fasboot flash cwm recovery, flash su thru recovery, do a full wipe thru recovery, and then flash the 4.08.605.15 stock odexed rom.
Click to expand...
Click to collapse
Tried again with your image, did the same thing.
I have CWM still, do I still need to flash it through fastboot, I also have su.. and where can I get the 4.08.605.15 stock odexed rom?
If you could link me, or walk me through this that would be awesome, thanks again for all your help, sorry for being so nooby about this, it's just never happened to me, where I couldn't flash a ROM, and not having a Nandroid really puts a damper on things too.
I don't get why none of this is working.

ogkhaze said:
Tried again with your image, did the same thing.
I have CWM still, do I still need to flash it through fastboot, I also have su.. and where can I get the 4.08.605.15 stock odexed rom?
If you could link me, or walk me through this that would be awesome, thanks again for all your help, sorry for being so nooby about this, it's just never happened to me, where I couldn't flash a ROM, and not having a Nandroid really puts a damper on things too.
I don't get why none of this is working.
Click to expand...
Click to collapse
If you have cwm, go to it and to the mounts and storage menu and format everything except emmc and sdcard. Then flash the stock rom http://dinc.does-it.net/Stock_inc_4.08.605.15_deodexed.zip

cmlusco said:
If you have cwm, go to it and to the mounts and storage menu and format everything except emmc and sdcard. Then flash the stock rom http://dinc.does-it.net/Stock_inc_4.08.605.15_deodexed.zip
Click to expand...
Click to collapse
Formated all except emmc and sdcard, tried flashing through CWM, said Error (Status 7) Installation aborted. format () expects 5 args, got 2.
I've owned an Incredible before this one, 3 years ago, and it was never this difficult. Really stressin' about this now.

ogkhaze said:
Formated all except emmc and sdcard, tried flashing through CWM, said Error (Status 7) Installation aborted. format () expects 5 args, got 2.
I've owned an Incredible before this one, 3 years ago, and it was never this difficult. Really stressin' about this now.
Click to expand...
Click to collapse
Try this one http://dinc.does-it.net/Stock_inc_4.08.605.15_odexed.zip, or try to flash another rom just to see if any rom will flash.
I would try a different sdcard if you have one. Either there is an issue with the sdcard, your downloads are getting corrupted, or the file transfer from download location to sdcard is corrupting the files.

cmlusco said:
Try this one http://dinc.does-it.net/Stock_inc_4.08.605.15_odexed.zip, or try to flash another rom just to see if any rom will flash.
I would try a different sdcard if you have one. Either there is an issue with the sdcard, your downloads are getting corrupted, or the file transfer from download location to sdcard is corrupting the files.
Click to expand...
Click to collapse
I got TeamBLISS's ROM to install. Had it on my SD card from earlier today so I thought I'd try it after I had everything formatted.
Now should I try one of the other images you sent me, or try the RUU again to see if I can get back to stock?

ogkhaze said:
I got TeamBLISS's ROM to install. Had it on my SD card from earlier today so I thought I'd try it after I had everything formatted.
Now should I try one of the other images you sent me, or try the RUU again to see if I can get back to stock?
Click to expand...
Click to collapse
You could try an ruu again. Let me check the stock rom file and see if it flashes for me.

cmlusco said:
You could try an ruu again. Let me check the stock rom file and see if it flashes for me.
Click to expand...
Click to collapse
Tried this RUU: http://dinc.does-it.net/Stock_Images/3.26.605.1/
Got the ERROR [155]
The Rom Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
It get's all the way until it says something about sending signature.
I don't see any way I can get back to stock when none of this is working out
Is there any other stock GB sense ROM I can flash through clockwork just so it looks stock? All the links I find are dead.