Related
First, this is not for people whom cannot boot into the recovery at all. If your recovery does not load, or you can't get past the "white screen", there are other threads and options for you (e.g. installing the recovery though fastboot or Unrevoked).
PROBLEM: You boot into the CWM3 recovery fine. You can install compatible zips fine. However, when trying to backup, the recovery locks up at some point during the backup process.
Solutions I tried: RUU to stock. Downgrading to 2.5.0.5 and back up to 3.0.0.5. Deleting the clockworkmod folder on the sdcard. reinstalling ROM Manager. wiping cache/dalvik before backing up. None of these things worked.
Solution that seems to have worked: swap out sdcards, doing battery pulls on the phone inbetween and booting back into recovery, until you find one that allows the backup to complete. Once a backup completes fully, you will be able to swap back to your original sdcard and CWM3 should work as intended.
Specifically here's what I did:
Step 0: Flash 3.0.0.5 through ROM Manager.
Step 0.5: Turn progress bar off in ROM manager settings. I do not believe this is important. But for completeness, I did do this.
Step 1: Boot into recovery
Step 2: run backup with Transcend 8gb class 6: No luck. Battery pull, back to recovery
Step 3: Sandisk 1.0gb class unknown: no luck, battery pull, back to recovery
Step 4: Sandisk 512MB class unknown: worked twice in a row!
Step 5: Back to 8gb class 6: backup works now. Still in testing, but I believe this (obscure, weird) solution works.
I just used ROM Manager to download CM7 #40 nightly, backup and install apps through CWM3 and it worked.
Let me know if this works for you.
EDIT: Well, its not perfect, because I cannot restore a backup because I get the MD5 mismatch error. At least there's progress.
EDIT2: There are deeper problems here. Please post your success or lack thereof.
I can't believe that simply getting a backup to work once fixes the problem. I just can't see the recovery caring that it finally got one right, so now it works from now on. Recovery doesn't know what it has done in the past.
Perhaps repeatedly inserting and removing the cards, just that act itself, somehow was the fix.
not impressed with cwm 3 at all, seems real buggy. Sometimes have problems with it not doing a clean wipe/factory wipe. When I install a rom, it has some wierd stuff going on. Stuff like loading a live wallpaper from the previous roms setting. I never use it to download roms anymore. I might switch over to ra amon recovery. Or maybe back to the 2. series
it seems @koush and @dougpiston had a twatt on the twitter about cwm3 borking on the dinc. you can read the full conversation over there, but the gist is that we should enable "erase recovery" option w/in rommanager settings, reflash recovery.
I guess the recoveries are best flashed clean, rather than over one another. ???
okay. the above fix has been confirmed to work by myself and one other user on the htc incredible cm7 nightly thead, AdhvanIt.
So you want to load cwm through rom manager after you enable "erase (previous) recovery" in settings and it will be puppies and rainbows from now on.
Sent from my dinc using XDA App
Regarding the erase recovery, I had tried it for the backup will not finish problem and the weird fix above is the only thing that worked, but will give it another try for my broken restore issue.
Wow I find odd that I have no problems what so ever with cwm 3
Sent from my Incredible using XDA App
tdiman said:
Regarding the erase recovery, I had tried it for the backup will not finish problem and the weird fix above is the only thing that worked, but will give it another try for my broken restore issue.
Click to expand...
Click to collapse
After going back to 2.5.1.2 with erase recovery enabled, and then back to 3.0.0.5 I'm back to square 1 with not being able to complete a full backup.
I'm going with 2.5.0.5 until either I get a new SD card or someone else comes up with a fix.
tdiman said:
After going back to 2.5.1.2 with erase recovery enabled, and then back to 3.0.0.5 I'm back to square 1 with not being able to complete a full backup.
I'm going with 2.5.0.5 until either I get a new SD card or someone else comes up with a fix.
Click to expand...
Click to collapse
bummer. keep us posted. I too have 16gb sandisk. had many issues with cwm3 but they seem to have stablized with the erase recovery fix... fricking variables...
Sent from my dinc using XDA App
burnmatoaka said:
bummer. keep us posted. I too have 16gb sandisk. had many issues with cwm3 but they seem to have stablized with the erase recovery fix... fricking variables...
Click to expand...
Click to collapse
There were some changes pushed to CM7 a couple of nights ago for the recovery management, as well as the new ROM Manager update, that got me to try again. This time I deleted all partitions on the sdcard and repartitioned it with a large FAT32 partition and a small ext4 partition after it. I deleted my unused swap partition. ROM Manager recognizes both partitions as it is able to format them, so thats good.
I used ROM manager and installed Amon-Ra, then installed 3.0.0.5. Same hang-on-backup problem as before. Back to 2.5.0.5
erase recovery has been on the whole time...
you have a gremlin in there! I assume you've tried full-wipe and all. Maybe install cwm3 from HBOOT with a fresh download and/or md5verified copy of the recovery?
hit up @clockworkmod on the twitter. I know he can be kind of a flake, but he does invite feedback when he drops an update... it was how we found out about the erase recovery thing.
you aren't having any other weirdness with other ROMs, are you? worst, worst case, your hardware is "circling the drain." sucks, but you know plenty of used dincs be hitting the market when Thunderbolt finally drops. See what Koush says though--be persistent, and it wouldn't hurt if you happen to have a RM premium license
good luck, and again, keep us posted.
sent from my dinc using xda app,
burnmatoaka said:
you have a gremlin in there! I assume you've tried full-wipe and all. Maybe install cwm3 from HBOOT with a fresh download and/or md5verified copy of the recovery?
Click to expand...
Click to collapse
In the spirit of the title of this thread, I do believe I have an actual working fix over in the DEV forum. I recompiled CWM3 from source. Please see
http://forum.xda-developers.com/showthread.php?t=970032
and let me know your experiences over there, those of you that may or may not still be following this thread
@clockworkmod just dropped a new version of the inc recovery that supposed to fix "wiping /datadata issue from ROM Manager" Has this been our problem?
sent from my dinc using xda app,
I do not believe that was my original issue as the problems I had were independent of ROM manager, but 3007 fixes whatever my issue was as well as the wipe issue, which is great.
3007 also has the option to power off, thanks Koush!
Has anyone tried the 3.0.0.8? Just flashed and hoping it works better.
phaze one said:
Has anyone tried the 3.0.0.8? Just flashed and hoping it works better.
Click to expand...
Click to collapse
Fast scrolling is back.
zero issues with 3.0.0.8 for me. SLCD.
Sent from my ADR6300 using XDA Premium App
unable to get 3.0.0.7 to boot, though. no big thing, just looking for that mythical multi-touch fix. <sigh>
(and ZOMG my post#10 means i can talk in the grown-folkxx forums. sorry for the fluff)
Sent from my ADR6300 using XDA Premium App
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.
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
Ive always been running CM roms since I got the phone nearly two years ago, but recently have been reading too many good things about ICS roms. My phone has been laggy as of late, and honestly after nearly 2 years, I wanna see and try something new. I've been reading some stuff about updating 4EXT or something like that. Can someone link me or explain in great details how i do this? What is it? And if I do that, will i still be able to run my old CM rom if i decide the ICS roms arent for me? I dont want to be unable to roll back.
Whats the best ICS roms out there right now?
Many thanks!
___________________
SOLVED AFTER A STEP BY STEP INSTALLATION WITH KB!! MANY THANKS
Sent from my T-Mobile G2 using xda app-developers app
mapheG2 said:
Ive always been running CM roms since I got the phone nearly two years ago, but recently have been reading too many good things about ICS roms. My phone has been laggy as of late, and honestly after nearly 2 years, I wanna see and try something new. I've been reading some stuff about updating 4EXT or something like that. Can someone link me or explain in great details how i do this? What is it? And if I do that, will i still be able to run my old CM rom if i decide the ICS roms arent for me? I dont want to be unable to roll back.
Whats the best ICS roms out there right now?
Many thanks!
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
Depends on your definition of best, personally I like EliteMod ICS (in my signature) but you may want to try out Andromadus Mimicry 1.3.0, it's pretty nice out of the box and has a graphical installer (aroma).
Just be aware that due to the fact that the Desire-Z/G2 does not have an official ICS release, that some things such as hardware drivers have their limits.
1) Camera drivers are not fully available, so the camera won't function as well as it would have on a GB rom.
2) No Wireless-N, also due to drivers, but Wifi-B/G are available.
and a number of other smaller issues which are mentioned varying on the roms, but the two above are the most common complaints, something to keep in mind before you start updating the thread about lack of it.
4EXT Recovery is just another recovery, like ClockworkMod is another recovery.
I personally prefer 4EXT Touch Recovery ( http://www.4ext.net/ has the app to install it ), but both ClockworkMod (what you may have now) and 4EXT can create backups, and restore your backups to the phone (just make sure you do a factory-reset/wipe cache, when you're flashing a brand new rom on, and when you wish to restore a backup.)
So i can flash ics roms with clock work mod and not use 4ext?
Sent from my T-Mobile G2 using xda app-developers app
mapheG2 said:
So i can flash ics roms with clock work mod and not use 4ext?
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
You can, they're both recoveries and will both apply a rom zip. I just find 4EXT to have quite a bit more features that pertain to ICS (i.e.: the ability to convert some of your partitions from the older ext3 filesystem to the ext4 filesystem which is better, but not all roms support it, most ICS roms do though), as well as the ability to do tar-based backups (compresses, smaller backup size), and the paid version of the app lets you configure a number of settings in 4EXT (much like the paid version of Rom Manager).
Just don't flash roms via the app, always do that from the actual recovery, or you risk causing problems.
Generally speaking: Reboot into recovery (you can do this from the power menu in CM7.2)
1) Perform a backup of your currently installed Rom to the SD card
2) (toggle USB storage and copy over the rom zip if you haven't already done so)
3) Perform a Factory Reset/Wipe and wipe cache
4) Goto Apply zip from SD Card and select the new ROM
5) Flash any additional zips you want on top, google apps, wifi calling, etc (note the thread for any specifics, for example Mimicry doesn't come with Google Apps so need to flash the ICS google apps if you want them, where as EliteMod includes a custom set of google apps already)
6) reboot and enjoy.
If you decide you don't like it, just repeat the above steps, just do a restore at #4 and reboot.
Both of the ones I mentioned (mimicry, elitemod) by no means require a swap partition or sd-ext partition, but you can partition the card via either clockworkmod or 4EXT, just skip the sd-ext2 option (since elitemod doesn't support a secondary one [and not much point either). And don't set a sd-ext size less than 1.5GB (no sense in making it smaller than your /data partition).
For both though, skipping an SD swap is advised, I only have SD swap on mine cuz no other rom I know of supports dataswap and I'd rather have my SD Card partitioned already to test out other roms than to re-do the SD Card each time (since you gota make sure to back up the content of the SD Card to the PC). 4EXT though will let you repartition the SD card without erasing the FAT32 partition, where as clockworkmod will always wipe the whole card before repartitioning (it's just easier to partition from scratch though).
Yeah the whole partition and swapping was the confusing part. But good to hear I don't have to do any of that. I did see the gapps zip included in the mimicry thread, but where can I find a wifi calling apk to install? Also +1 thanks to u for the detailed reply! Thanks!
Sent from my T-Mobile G2 using xda app-developers app
mapheG2 said:
Yeah the whole partition and swapping was the confusing part. But good to hear I don't have to do any of that. I did see the gapps zip included in the mimicry thread, but where can I find a wifi calling apk to install? Also +1 thanks to u for the detailed reply! Thanks!
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
In Mimicry the Aroma installer will actually let you pick that option during the graphical install. It's one of those roms that presents you with a nice installation menu after you select the zip to be applied. Just bear in mind though you need the 26.13.04.19 radio in order to use the T-Mobile Wifi calling app (and course be on T-Mobile). EDIT If you're one of those people who end up getting no WIFI at all after flashing the Wifi calling app from the aroma installer and have the 26.13.04.19 radio, in the first post of the mimicry thread there's a mention of a Wifi-Fix app you can install that might be able to fix that.
For EliteMod ICS, you would apply it by downloading the zip in my signature (for the wifi calling) and flashing that after flashing the rom. But again, needs the 26.13.04.19 radio, as the app won't work with an old radio (26.03.*)
The thread on applying the radio is also linked from my signature , if you're on a T-Mobile G2, you can just grab the first 26.13.04.19 zip file, rename it PC10IMG.zip just like the instructions say there, put it on the SD Card, reboot into the boot loader and apply the radio. Also if you're planning on flashing either mimicry or Elitemod immediately after flashing the new radio, both roms already Clean your EFS partition for you when you install them in recovery, so you don't have to run the EFS wipe zip (something you normally need to flash in recovery after changing a radio).
KB suggested EliteMOD to me a few days ago,...... Gota say it is running vnice at the moment, highly recommend it. w/ SD EXT, no swap.
I downloaded the zip file from the Andromadus thread, and proceeded to flash the ROM. It says the flash was successful, however upon rebooting, I would see the HTC screen but it would never make it to the boot animation. I would just get a black screen. I tried flashing through ClockWorldMod v5. I cleared all data and caches, and then flashed the ROM.. still not working?
mapheG2 said:
I downloaded the zip file from the Andromadus thread, and proceeded to flash the ROM. It says the flash was successful, however upon rebooting, I would see the HTC screen but it would never make it to the boot animation. I would just get a black screen. I tried flashing through ClockWorldMod v5. I cleared all data and caches, and then flashed the ROM.. still not working?
Click to expand...
Click to collapse
What's the exact details of your phone, i.e.: hboot information and radio version.
I flashed the radio from your signature. Hboot information: 0.82.0000
blkjack said I needed to do a superwipe. If that is the case, how would I perform one?
mapheG2 said:
I flashed the radio from your signature. Hboot information: 0.82.0000
blkjack said I needed to do a superwipe. If that is the case, how would I perform one?
Click to expand...
Click to collapse
hboot in my signature is a 0.84.2000 which is a desire-z engineering hboot.
0.82.000 would be an S-ON hboot which you wouldn't be able to change much at all. (which would be odd if you managed to get the 26.13.04.19 radio flashed, while S-On since it wouldn't normally allow you to).
May want to reboot into the boot loader mode and verify all your hboot information.
kbeezie said:
hboot in my signature is a 0.84.2000 which is a desire-z engineering hboot.
0.82.000 would be an S-ON hboot which you wouldn't be able to change much at all. (which would be odd if you managed to get the 26.13.04.19 radio flashed, while S-On since it wouldn't normally allow you to).
May want to reboot into the boot loader mode and verify all your hboot information.
Click to expand...
Click to collapse
I flashed a radio in the past. And it clearly says I have S-OFF on the top. I had the (26.03.02.26) radio before. And it did successfully flash the radio linked from your signature. HBoot says 0.82.0000. Where to go now?
EDIT: I found this link (http://forum.xda-developers.com/showthread.php?t=1044992) but dunno if this is outdated or not. If not, which of the three files do I want?
mapheG2 said:
I flashed a radio in the past. And it clearly says I have S-OFF on the top. I had the (26.03.02.26) radio before. And it did successfully flash the radio linked from your signature. HBoot says 0.82.0000. Where to go now?
EDIT: I found this link (http://forum.xda-developers.com/showthread.php?t=1044992) but dunno if this is outdated or not. If not, which of the three files do I want?
Click to expand...
Click to collapse
I think, the -=SuperWipeG2+=-.zip should be the right one, but as I'm not sure, I did a quick Google search for you and found this:
EdKeys said:
I recently flashed the new 4EXT Mod of ClockworkMod Recovery. The 4EXT Recovery is based off of Koush's CWM Recovery but offers additional power options, one of which is the ability to show the file system format your partitions are formatted in. To my surprise my system was formatted in the Ext 4 format and my data and cache partitions were formatted in Ext 3. The new 4EXT Recovery offers the option to convert the format without deleting any of the data. Your ROM will stay intact after the conversion. I selected that option and changed my data and cache partitions to ext 4 to match my system, rebooted, and notice quite an improvement in speed and smoothness in my current CM7 Nightly. After looking into it further I found out that the SuperwipeG2 that many of us have been flashing is formatting our partitions in the Ext 3 format. The reason only my system was formatted in ext 4 is because I used ClockworkMod Recovery the last time I did a full wipe to first flash the Superwipe, and then I immediately formatted system again with ClockworkMod Recovery. If you've used SuperwipeG2 to do a wipe, more than likely your system, data, and cache partitions are now Ext 3. You might want to check with your ROM developer to see if your ROM will run on the Ext 4 format. If its a CM7 based ROM, it will.
You can find more information about the Ext 4 format here.
Tsubus has since modified SuperwipeG2 so that it now formats the partitions into ext 4 when you flash it. I've used it and it also includes the EFS wipe. You can find it here. As I said, if there is no reason to wipe right now the new 4EXT Recovery can convert your partitions if you choose if they are in currently Ext 3. At the very least you can see what format they're currently in with 4EXT. I highly recommend it. You can always flash back to CWM Recovery if and when you choose. The partitions will remain Ext 4 once you choose to convert.
UPDATE: Several users have reported that checking partition information with Terminal Emulator is not reliable.
Click to expand...
Click to collapse
This one should definitely be the right one.
Besides that, the problem might also be a bad download, as your symptom fits a known issue in blk_jack's thread:
blk_jack said:
...
Q) After flashing I'm stuck at the HTC logo screen!
A) This is likely the result of a bad download. Check your downloaded md5sum hash against the one listed next to the download link above....
Click to expand...
Click to collapse
I thought it was a bad download too, so I downloaded from one of the mirrors. Still the same problem.
mapheG2 said:
I thought it was a bad download too, so I downloaded from one of the mirrors. Still the same problem.
Click to expand...
Click to collapse
So you did not check the MD5 hash?
Im a bit of a noob and all of this wasnt around when I was flashing CM roms ages ago. How do I do that? Would that fix my issue??
Sent from my T-Mobile G2 using xda app-developers app
mapheG2 said:
Im a bit of a noob and all of this wasnt around when I was flashing CM roms ages ago. How do I do that? Would that fix my issue??
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
An MD5 hash is something like a fingerprint of a file and it was definitely there when you first flashed CyanogenMod ROMs. The MD5 hash/sum is used to compare two files because it is possible that a downloaded file is slightly different from the original file due to mistakes that could have happened during transfer. So "checking the MD5 hash" means using a program to calculate that "fingerprint" of your downloaded file and comparing it with the "fingerprint" mentioned in blk_jack's thread. If the file you have downloaded is slightly different, its MD5 hash will be different from the MD5 hash that it should have and thus will be unusable and lead to a phone being stuck at HTC boot logo.
By the way, downloading a file from two different mirrors doesn't exclude the risk of getting a corrupt file.
I ran "md5 update.zip" from my Mac's desktop where the file is located. I was returned MD5 (update.zip) = 2a314e5f1361825c83a354aea38c6c4b .. which matches the md5sum of what was given. What next?
And I noticed you have the same H-Boot information that KB was talking about earlier, so I guess that can't be the problem either. Should I just try to Superwipe?
mapheG2 said:
Ok, so if it is a bad download, how do you remedy it? Because there are only so many options to download the ROM right. And what program are you referring to
Click to expand...
Click to collapse
There are actually lots of programs to calculate an MD5 hash. If you are on Linux it usally is as easy as typing md5sum <path to file> in a shell and reading the output. If you are on Windows, I'd recommend a Google search for "md5 generator" or something like this. Maybe even your recovery is able to calculate a file's MD5 hash - I'm using 4EXT and it definitely is, though I don't know if ClockwordMod is.
You can't remedy a bad download except trying to download it again, hoping that the file will be transferred right.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
mapheG2 said:
I ran "md5 update.zip" from my Mac's desktop where the file is located. I was returned MD5 (update.zip) = 2a314e5f1361825c83a354aea38c6c4b .. which matches the md5sum of what was given. What next?
And I noticed you have the same H-Boot information that KB was talking about earlier, so I guess that can't be the problem either. Should I just try to Superwipe?
Click to expand...
Click to collapse
Oh, sorry - didn't update the thread's page before submitting my reply.
Just try it, there should be nothing wrong with it.
Okay, I read that I should manually clear all the data and cache first and THEN run the superwipe, followed by installing the ROM right? And I will be downloaded from the thread I listed because I still have ext3 I guess and don't want to deal with a ext4 change right now.
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.