Related
Hi all
can't flash my desire hd anymore
and the phone boot only to the recovery.
after a full wipe,i try to flash a new rom, up to 80% and the progress bar does not move.... meaning that the flash does not complete:-(
my phone is s-off and root
I flashed different rom before and all worked
could someone help me please?
thx in advanced
Hi bassjam
bassjam said:
Hi all
can't flash my desire hd anymore
and the phone boot only to the recovery.
after a full wipe,i try to flash a new rom, up to 80% and the progress bar does not move.... meaning that the flash does not complete:-(
my phone is s-off and root
I flashed different rom before and all worked
could someone help me please?
thx in advanced
Click to expand...
Click to collapse
What Rom is it you are trying to install?
Is there any error message showing when it stops?
At a guess It sounds as if you are trying to install a Corrupt Rom, you need to check the MD5 Checksum that come with the Rom to make sure they are not corrupt on download, before you try to install them.
What you need to do is download the Rom again, check it's Checksum With this MD5 Check 2.1 tool.
Then delete the bad Rom that on your SD Card, and replace with the new download [Checked with MD5 Check] Rom, and flash it.
Take Care
TheQuest
Agree with I'm TheQuest. That's maybe because of bad download. redownload back the rom and put back to your SD card. Do the nandroid restore (but if you dont have nandroid backup before, this also can be done by taking out your sdcard and put into your laptop/card reader).
Thx for your answers
The problem appeared with the cynanogen RC4
this rom was installed since a week and i was on RC3 before
one day, I powered off the phone, then powered it on, and the phone boot only to the recovery.
I tried to flash the last leedroid but nothing
After that I knew it was not from the cyanogen rom.
For the moment, to solve the problem, i flashed (on bootloader) the last official WWE ruu(1.72), flash ok but the phone was very very sloooowwww
especially to install the sence, after unlocking simcard, I have a white screen with htc logo during 20 min. and only after that, I can start the configuration.
so i decided to back to ruu 1.32 to root / S-off the phone again
After that I try to install the cyanogen rom again
What do you think about that?
Hi bassjam
bassjam said:
Thx for your answers
The problem appeared with the cynanogen RC4
this rom was installed since a week and i was on RC3 before
one day, I powered off the phone, then powered it on, and the phone boot only to the recovery.
I tried to flash the last leedroid but nothing
After that I knew it was not from the cyanogen rom.
For the moment, to solve the problem, i flashed (on bootloader) the last official WWE ruu(1.72), flash ok but the phone was very very sloooowwww
especially to install the sence, after unlocking simcard, I have a white screen with htc logo during 20 min. and only after that, I can start the configuration.
so i decided to back to ruu 1.32 to root / S-off the phone again
After that I try to install the cyanogen rom again
What do you think about that?
Click to expand...
Click to collapse
If you Change ROM's you are always advised to do a FULL WIPE.
Moving to Cynanogen RC4 from RC3 should not have caused your problem, but even when Updating a Rom you are advised to wipe the Cache Partition and the Dalvik Cache
Take Care
TheQuest
My problem is not yet resolved
actually I download rommanager to get the recovery
my phone is so slooooowwwwwww...
after that I will try to flash new rom with a full wipe before ;-)
if it doesn't work --> the phone will go on "after sales service" :-(
Hi bassjam
bassjam said:
My problem is not yet resolved
actually I download rommanager to get the recovery
my phone is so slooooowwwwwww...
after that I will try to flash new rom with a full wipe before ;-)
if it doesn't work --> the phone will go on "after sales service" :-(
Click to expand...
Click to collapse
Yes do a full wipe, it should help with the speed, good luck.
Let us know how you get on please?
Take Care
TheQuest
is the first time such a problem that happens
I had a htc magic, hero, desire and windows mobile phone before
with each phone, I had at less similar problem
for the first time, I wonder if this is not a hardware problem like writing speed of the processor...
for the moment i finished radio s-off, eng-off, and i put the recovery with fastboot( problem to get recovery with rom manager)
It's time to full wipe, about 30 minutes to wait if not more...
edit: full wipe ok after 15 min, i'm going to wipe with fastboot to be sur!?
redit edit: flash the phone with cyanogen rc4...
thx
something in recvory or perhaps on i didn't see it before
I actually use CWM 2.5.1.2
i have in the recovery screen:
E: can't mount CACHE: recovery/command
E: can't mount CACHE: recovery/log
E: can't open CACHE: recovery/log
Could someone explain me what does it mean?
thx
Hi bassjam
bassjam said:
something in recvory or perhaps on i didn't see it before
I actually use CWM 2.5.1.2
i have in the recovery screen:
E: can't mount CACHE: recovery/command
E: can't mount CACHE: recovery/log
E: can't open CACHE: recovery/log
Could someone explain me what does it mean?
thx
Click to expand...
Click to collapse
You should try to updating CWM to 3.0.0.6, and that should clear that. [hopefully ]
Take Care
TheQuest
amazing!! it works!
flashed leedroid rom with CWM 2.5.1.2 and all is ok( it was impossible to flash cyano with this recovery)
i can now upgrade to cwm 3.0.0.6 and flash cyanogen rc4
very big thx
For those who have the same problem, read the previous post ;-)
Hi bassjam
bassjam said:
amazing!! it works!
flashed leedroid rom with CWM 2.5.1.2 and all is ok( it was impossible to flash cyano with this recovery)
i can now upgrade to cwm 3.0.0.6 and flash cyanogen rc4
very big thx
Click to expand...
Click to collapse
Glad to hear you have managed to get it fixed.
Take Care
TheQuest
bassjam said:
amazing!! it works!
flashed leedroid rom with CWM 2.5.1.2 and all is ok( it was impossible to flash cyano with this recovery)
i can now upgrade to cwm 3.0.0.6 and flash cyanogen rc4
very big thx
For those who have the same problem, read the previous post ;-)
Click to expand...
Click to collapse
Yes CWM 2.x can't write the ext4 partitions required by Gingerbread so you require cwm 3.x, you could have flashed this from Fastboot without first flashing a new ROM. If you didn't have CWM 3.x in the first place this was probably the source of your problems.
I don't believe it!
phone works during 5 five with cyanogen rom, I put the wifi on, and then bootloop( recognized problem on RC4)
i pull out the battery then restart the phone, and the phone has not started and the stay blocked to htc logo
PB: I have no recovery, impossible to to flash another rom. When I launch recovery, phone blocked on htc screen!
I tried to flash ruu 1.32 or 1.72 on fastboot mode... but phone still blocked on htc screen...
I don't know what to do
pls help
thx
Hi,
So i have a HTC Desire flashed to CM7r2 Hboot (just moved from stock) and i have tried flashing all possible custom roms from xda (BlissMod007, AceS, Starburst, RevolutioN Aurora, LeeDroid etc etc....) NONE of them work on my desire.. I checked my hboot...checked my root everthing is fine...i even have a 1GB ext partition on my card that the ROM's want...Majority of the ROM's are stuck on the lockscreen others freeze after some time ..
I really want to know whats wrong! I CANT live with the original froyo bc that gives me only 25mb of free internal memory.
SOMEBODY PLEASE HELP ME!!
rappersup said:
Hi,
So i have a HTC Desire flashed to CM7r2 Hboot (just moved from stock) and i have tried flashing all possible custom roms from xda (BlissMod007, AceS, Starburst, RevolutioN Aurora, LeeDroid etc etc....) NONE of them work on my desire.. I checked my hboot...checked my root everthing is fine...i even have a 1GB ext partition on my card that the ROM's want...Majority of the ROM's are stuck on the lockscreen others freeze after some time ..
I really want to know whats wrong! I CANT live with the original froyo bc that gives me only 25mb of free internal memory.
SOMEBODY PLEASE HELP ME!!
Click to expand...
Click to collapse
So you flashed the CM7r2 HBOOT and used every rom but CM7? If those roms aren't designed to fit on the CM7 HBOOT you'll end up with half a rom flashed on there.
Did you wipe everything between flashes (including dalvik cache)?
Last thing, try flashing back to the stock HBOOT partition layout and see how that goes. Might've got a corrupted partition file (you should always an MD5 checker on stuff like this).
yes when i flashed the CM7 hboot i flashed the CM7 ROMs for which i wudnt get past the white screen with htc in green
and when i had the stock hboot the ROMs wud get flashed the first boot would go smooth (wud take some time obviously but thats normal right?)
and yes everytime i flashed i wiped everything including dalvik cache.
and i also dont understand what with the MD5 how is that important... because i completely ignored it before.
From your posts looks like you did not read the tutorials carefully.
EXT partition made correct?
What Recovery do you have?
What version did you download from the ROM?
MD5 Checksum is fine?
i had this problem aswell before so all i did was flash the alpha rev downgrader hboot then on the phone click on restart bootloader then just flash the cm7 hboot..
then just wipe everything and flash the rom ..
also some sense roms take up to 15 mins to boot and some of the sense roms resarts the fone three times so just wait for a maximum of 20 minutes
yes ext partition is correct i had a 2GB ext4 previously but then i read on the forums that not all ROMs were compatible with a ext4 so then changed it to a 1GB ext 3
Clockwork Mod Recovery 2.5.0.7
Whats this MD5 Checksum ?? How do i verify it ?
Also whats the alpha rev downgrader ? do you have to downgrade the hboot ?
Because i moved from CM7 to stock just by reflashing it and on my bootloader i saw the change just fine.
I have 10MB free internal memory WT*
rappersup said:
...
Clockwork Mod Recovery 2.5.0.7
...
Click to expand...
Click to collapse
Use Amon ra recovery. CMR didn't work for me either.
Is that true could it be CMR ??
And how do i get amon ra ? i got CMR by default like when i rooted using unrevoked.
If CWM 2.5.0.7 doesnt work at all, it may be because you have a PVT 4 erase size 40,000 device.
Not sure why my guide is one of the only guides that mentions this, but there you go.
rappersup said:
Is that true could it be CMR ??
And how do i get amon ra ? i got CMR by default like when i rooted using unrevoked.
Click to expand...
Click to collapse
Some people have trouble with clockworkmod. Normally they solve it by switching to another recovery so it may be the reason to what you are experiencing now.
To get AmonRa recovery, download AmonRa recovery here. Then plug your phone into the computer and use this utility to flash the recovery.
itachi1706 said:
To get AmonRa recovery, download AmonRa recovery here.
Click to expand...
Click to collapse
Actually, I think the test 2.0.1 is better (for SD-ext backup), which you can get here for a limited time only:
http://db.tt/z7hzdp34
No mine is a pvt 3 atleast that's what it says in my bootloader
I think I'll try amon ra
Hey Guys,
So i flashed AmonRa and then flashed a ROM and it works fine so far.
Thanks alot will get back on how its performance is in the long run.
Thanks a lot
okay no as soon as i rebooted it got stuck on the lockscreen and froze....rebooted again same story....rebooted again same story done that about 5 times now
sorry false alarm its like the problem never went...back to the same old situation...
can someone please help me out..
also is there a way to go back to cmr ??
Try changing to a different kernel. It may be a problem with the kernel. What Rom are you using now?
Sent from my HTC Original Desire using Tapatalk
Well I tried RevolutioN - http://forum.xda-developers.com/showthread.php?t=1300224 which worked for 30 mins before it froze
and then i tried ReflexS - http://forum.xda-developers.com/showthread.php?t=1054435
which worked for about 15 mins and then froze.
which kernel should I flash ? thats the only thing left to flash now
And now i have switched back to CMR as i had a CMR backup of the stock ROM.
So im running the stock ROM now.
Try snq 111005 or gingercakes 0.6d. They are the stablest kernels for sense roms for me. Use the search function to find the kernels.
Sent from my HTC Original Desire using Tapatalk
im sorry but i cant find either of those kernels
i found gingercakes 0.8f and many other versions that were 0.8d/e/etc etc
can u post a link or something like that....also i dont know how to flash a kernel is it just like a rom zip thru clockworkmod ??
rappersup said:
im sorry but i cant find either of those kernels
i found gingercakes 0.8f and many other versions that were 0.8d/e/etc etc
can u post a link or something like that....also i dont know how to flash a kernel is it just like a rom zip thru clockworkmod ??
Click to expand...
Click to collapse
Can't help you with finding the kernels I'm afraid. But to flash one just do it through recovery like you would a rom. No need to do all the wipes, just wipe your dalvik cache before you flash it.
Installed Andromadus 4.0 beta on my wife's G2. When I got home from work my wife said that the phone had restarted and would now only boot into clockworkmod recovery v5.8.1.0. Tried factory reset and wiping the caches and reflashing. Also tried flashing CM9 unofficial but the phone just shuts off in the middle of the flash and reboots back into clockwork. Tried to flash stockmod but I get a "can't open error". Currently the phone boots into Clockwork mod, stays on for 60 secs, then reboots itself back into clockwork mod. Help please!
maybe try to reflash your recovery, boot into fastboot and try...
When you say 'tried to flash stockmod' do you mean a PC10IMG?
Cause those are made to be flashed in hboot mode, not recovery.
-Nipqer
Nipqer said:
When you say 'tried to flash stockmod' do you mean a PC10IMG?
Cause those are made to be flashed in hboot mode, not recovery.
-Nipqer
Click to expand...
Click to collapse
Well that must be why that option didn't work. I'm pretty new to all this. Have a MyTouch I rooted a couple weeks ago that works great. But I am having fits with this one, and worse, it's my wifes phone Any other suggestions?
wipe everything in recovery, then flash a superwipe.zip (also fastboot -w is good but if your new dont worry) no flash a stable rom in recovery. i suggest elite mod, its a cm7 based rom that i personally like. all files will be found in the development threads along with any instructions needed. if you have troubles ask here again but make sure you
1 wipe all
2 superwipe.zip
3 flash rom (elitemod or whatever)
Sent from my HTC Vision using xda premium
demkantor said:
wipe everything in recovery, then flash a superwipe.zip (also fastboot -w is good but if your new dont worry) no flash a stable rom in recovery. i suggest elite mod, its a cm7 based rom that i personally like. all files will be found in the development threads along with any instructions needed. if you have troubles ask here again but make sure you
1 wipe all
2 superwipe.zip
3 flash rom (elitemod or whatever)
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
It worked! Thank you so much!
great to hear! if you used and like the rom i suggested make sure to thank the developer, it doesnt seem that too many use this rom any more but it is still one of my favorites for the g2 and the dev deserves great credit
Not really working!
demkantor said:
great to hear! if you used and like the rom i suggested make sure to thank the developer, it doesnt seem that too many use this rom any more but it is still one of my favorites for the g2 and the dev deserves great credit
Click to expand...
Click to collapse
I tried installing superwipe, and all sorts of different android operating systems but I cant seem to get my phone to get out of clockworkmod v5.8.1.0 and I can get to fastboot or hboot but it wont go passed the HTC screen. Every time I try installing an updated OS or a different OS or even doing the superwipe.zip it just says installation aborted and i can't get it to work! Any tips?
For future reference, don't go blindly flashing "Stock" images and such via the bootloader you tend to get yourself into more trouble that way (bricking, or making it difficult to get back to rooting).
Also if you're frequently using ICS roms I recommend using 4EXT Touch Recovery instead of ClockworkMod. A lot more useful tools in the recovery itself especially for wiping or formatting specific partitions.
When you get a chance check out which eMMC is used on that phone (click the eMMC name in my signature to see the poll thread which tells you how to check). Good for future reference if something acts up again.
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
Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:
DroidUser_Wind said:
Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:
Click to expand...
Click to collapse
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
DUDE.THANK YOU so MUCH FOR REPLYING.Ill try what you told me tonight,and ill let you know how it goes down.thanks again chills.:good:
chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
What OP wrote applies to me as well. I am looking for something better than aerovan's CM9 (which has been my DD), and thought I would give Viper a try. Without fail, bootlooping (which I could have guessed since I did tacoroot and this seems to be an issue with sense based roms).
That said, I tried steps 1 through 4 and the bootlooping stopped in Viper - it goes through startup and just shuts down before leaving the boot screen. One strange thing that I noticed is that the ICS Firmware/radio with Viper (which I loaded in CWM), wouldn't load in 4ext. Maybe I'll give paranoid a go if I can't resolve this bootlooping issue in Viper! I hope OP has better luck.
U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app
I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.
Jasonp0 said:
I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.
Click to expand...
Click to collapse
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.
gtdtm said:
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.
Click to expand...
Click to collapse
Good call. When chilly said you don't flash kernels in recovery I hit my head. I flashed the radio, but now my challenge is getting back into recovery since I renamed the file and bootloader always finds it and wants to reboot or I load CM9 which stays on flash screen. I'll figure something out, maybe with adb. Thanks.
Power down, pop the sd out, boot to recovery, rename file, profit.
gtdtm said:
Power down, pop the sd out, boot to recovery, rename file, profit.
Click to expand...
Click to collapse
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.
digitalshepard said:
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.
Click to expand...
Click to collapse
good lucking going back to aosp lol
almost thesame problem
chillybean said:
U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
i made a stupid mistake of flashing radio in recovery, in fact the radio is for Samsung at&t and now my phone vibrates it doesnt show htc quietly brilliant, only vibrates and orange light with black screen untill i pull out the battery... i was able to return to stuck and it can only boot if its connected to power, it doesn't read sd card while android is booted and in recovery to, only in bootloader it reads sd... error in mounting if i try to... i flashed RUU.exe 2.3.3 and 2 other RUUs for my droid inc 2 but it keeps vibrating... please help me!!! thanks
I made the same mistake when i first gained s-off for my dinc2. the thing with the venom rom tho is if you ever want to go back to aosp ull need to gets chill's anti-venom zip and flash it through recovery because doing a normal wipe wont do the trick. also a helpful trick that worked for me with roms if i ever start getting boot loops i go into recovery from the bootloader menu and i wipe the dalvik cache under advanced and then wipe the chache under mounts and storage and it always works like a charm for me. but ive also learned that you have to be careful which kernel you flash with the rom of your choice because not only will it cause lags if you happen to get past the boot animation to the main screen but in some cases it can cause breaks in your framework like your wifi data etc. im not an expert tho those are just suggestions that im familiar with because theyve already happened to me before. hope this helps in any way.