[Q] I stuffed up. What do I do? - G2 and Desire Z Q&A, Help & Troubleshooting

Hi, first time posting here.
I have a bit of a unique problem or so I've heard. So I was an idiot and decided to flash a Virtuous ROM over the WiFi via ROM Manager on my Desire Z. Previous to this it was rooted and was running CM 7.1 RC1 and was all fine. When I flashed the Virtuous Sense Rom (Not unity, the one before it in ROM Manager), it flashed, what I thought was fine. However, when I actually got into the phone, it said everything was crashing and would go into a boot cycle. Then for some stupid reason I just reflashed the 1.3.4 or whatever ROM back onto (The one you're meant to downgrade to). At this moment in time, I can't do anything. When I'm in the bootloader of the phone itself, I can't scroll up or down to the recovery option, so I can't flash through that. I've tried re-rooting the phone (Or that process), hoping that it would work. At this point in time, it keeps popping up errors at /data/local/tmp/psneuter
Note: I was following the CM7 rooting guide thing.
Anyway, I hope someone'll be able to help me out of this stupid stupid thing that I've done.
THanks!
EDIT: Okay, well, going through the CM7 rooting guide a fourth time seems to have fixed it. It's all fine now. On another note, how do you change the Virtuous Unity lock screen to something else? I'm not really a fan of the Sense 3.0 lockscreen.

You should not need to re-root after flashing any custom ROMs.
Also, I would not do any more ROM flashing if clockworkmod is not properly installed, or you don't know how to use it.

Did you bother to wipe data and cache? You didn't mention it. If you didn't that's your problem
Sent from my HTC Vision using XDA Premium App

Related

[Q] Looping Boot Image

Heres the main question at hand before you read my large summary.
1) Why is my ROM's boot image looping constantly?
2) Do I have to NAND again if I revert to a nandroid backup that was made before I nand'ed my phone?
Time for the long, and mostly pointless, summary:
I'm pretty desperate to get things running on a Gingerbread ROM, if you didn't notice in my last topic 2 hours ago.
Anyways, I'm trying to get cyanogenmod7, Stock Gingerbread 2.3.1, or heck, even eVOKINGS-gingerbread ROM to work.
So far, i've tried Cyanogenmod7 and Stock Gingerbread 2.3.1 on my evo; none of which have worked past the boot screen.
Lets take stock gingerbread for example:
I downloaded the new cyanclockwork recovery rom off of rom manager and flashed it after a *long* process of nand'ing and rooting again.
Then, I powered down, booted up, and went straight into recovery in the bootloader. I went to install ROM from SD->chose the .zip .
after waiting for awhile, it said the upgrade was complete (upgrade?)
*notice: the installation bar didn't move at all durring the installation process, if that makes a difference
I rebooted, and was greeted by the HTC screen while it spelt out q-u-i-e-t-l-y-b-e-a-u-t-f-u-l
Nothing happens after that.
It just shows the HTC screen again, getting stuck at the B in beautiful. Pretty much just looping over-and-over again.
Same thing happened for Cyanogenmod7, I was constantly being looped through the skateboarding-droid figure.
I'm doing something wrong here obviously, because all these ROM's have screen captures from a EVO 4G.
Does it make a difference if I use Clockwork recovery 3.0.0.7/6/5? or 2.6.7?
Please help.
I know all my questions are rather long and complicated, but im sick of being ignored at every forum (ubuntu forums, black ops, etc.)
Or I'm impatent and overestimated your forums activenes. No disrespect to the forums or devs (I thought your forum was really active)
Edit: If I for some reason can't get a 2.3.1 ROM to work, would someone kindly point me to a stable Froyo ROM they think is the best?
Have you use amo-ra?
Sent from my evil evo!!
rsjc741 said:
Heres the main question at hand before you read my large summary.
1) Why is my ROM's boot image looping constantly?
2) Do I have to NAND again if I revert to a nandroid backup that was made before I nand'ed my phone?
Time for the long, and mostly pointless, summary:
I'm pretty desperate to get things running on a Gingerbread ROM, if you didn't notice in my last topic 2 hours ago.
Anyways, I'm trying to get cyanogenmod7, Stock Gingerbread 2.3.1, or heck, even eVOKINGS-gingerbread ROM to work.
So far, i've tried Cyanogenmod7 and Stock Gingerbread 2.3.1 on my evo; none of which have worked past the boot screen.
Lets take stock gingerbread for example:
I downloaded the new cyanclockwork recovery rom off of rom manager and flashed it after a *long* process of nand'ing and rooting again.
Then, I powered down, booted up, and went straight into recovery in the bootloader. I went to install ROM from SD->chose the .zip .
after waiting for awhile, it said the upgrade was complete (upgrade?)
*notice: the installation bar didn't move at all durring the installation process, if that makes a difference
I rebooted, and was greeted by the HTC screen while it spelt out q-u-i-e-t-l-y-b-e-a-u-t-f-u-l
Nothing happens after that.
It just shows the HTC screen again, getting stuck at the B in beautiful. Pretty much just looping over-and-over again.
Same thing happened for Cyanogenmod7, I was constantly being looped through the skateboarding-droid figure.
I'm doing something wrong here obviously, because all these ROM's have screen captures from a EVO 4G.
Does it make a difference if I use Clockwork recovery 3.0.0.7/6/5? or 2.6.7?
Please help.
I know all my questions are rather long and complicated, but im sick of being ignored at every forum (ubuntu forums, black ops, etc.)
Or I'm impatent and overestimated your forums activenes. No disrespect to the forums or devs (I thought your forum was really active)
Edit: If I for some reason can't get a 2.3.1 ROM to work, would someone kindly point me to a stable Froyo ROM they think is the best?
Click to expand...
Click to collapse
I'm pretty sure you will still have nand unlocked. The only way you wouldn't is if you unroot.
Sent using my EVO running AZRAL X V 3.1
klquicksall said:
I'm pretty sure you will still have nand unlocked. The only way you wouldn't is if you unroot.
Sent using my EVO running AZRAL X V 3.1
Click to expand...
Click to collapse
Thanks
I should face-palm myself. I just read the sticked post and I'm going to try some of his suggestions. He pointed out why cyanogenmod wouldn't work.
My whole consept of the framework went out of the window, and now I think of it more like a standard linux distro, in terms of kernel->ROM relationship.
I don't think I need to have a custom kernel for the Gingerbread beta-4, but i'll look it up just in case... Though I don't have a clear idea on how to flash that.
And to the person 2 above, im using Cyanclockwork. For whatever reason, I like its design verse RA recovery. I might try RA recovery just to see if it works better, as everyone has said it does.
I think i needed to clear all my caches and then load the ROM.
So I did a wipe of everything (data, darvik, cache) and trying to install the GB ROM. My boot screen is *still* looping. Do I need to get another kernel? Is it like flashing a ROM? Where are they at? I didn't see any in the software section...

[Q] Z based ROMs - prerequisites?

So my launch day Incredible bit the dust out of nowhere the other day, following some quirky behavior leading up to it (random reboots, inability to power up after battery pulls).
I get my warranty RMA yesterday, and figure that before I restore my Titanium backup, I'll play with some ROMs. I'm assuming I was lucky enough to get another AMOLED replacement, since by any method I can tell it appears to be AMOLED and not SLCD (part number is ADR6300VW, hardware version 0002).
At any rate - I figured I'd try one of the Desire-Z ROMs or a Gingerbread ROM. After I fully rooted and turned NAND S-Off. After confirming those worked fine, I rebooted and flashed a Gingerbread ROM from Clockwork. Rebooted, never got past the HTC Incredible splas screen.
Couldn't get it to work at all - after all sorts of wipes, I finally gave up and flashed Virtuous, figuring it's close to stock. Got back up and running, no problem.
Turned to a Desire-Z ROM - and the same happened again. Splash screen, nothing further. After the same tries, went back to recovery, flashed Virtuous and then SkyRaider, and again, up and running fine.
I'm on HBoot 0.92 with the 7.28 radio. Is there something I'm missing on these Z ROMs? I read through the threads, saw a few people report the same but no real conclusion as to why it was happening.
Thoughts?
Judging by what you posted, you only used ROM Manager to flash roms after booting into recovery correct?
What happens when you manually go into recovery, wipe cache/data/dalvik, and flash the rom from your SD Card? I was running Nil's Business Sense (Desire Z) rom quite fine after flashing it. Some people have issues with ROM Manager and others don't and I'm one of the people who do use ROM Manager to flash roms so I can't help you in that respect.
Sounds like you're using CWM3.
Try any older version.
dpwhitty11 said:
Sounds like you're using CWM3.
Try any older version.
Click to expand...
Click to collapse
This is wat it sounds like
Sent from my ADR6300 using XDA App
If you are using ClockWorkMod v3 and tring to do a fresh install with a cwm3 capable ROM it could be a problem. Seems like cwm3 acts a little funny. Or you could be on cwm-v2 and trying to install a cwmv3 ROM and that does not work.
So the key is use cwm 2.5.1.2 and a cwm-v2 Z ROM

[Q] Unable to flash stock

Ok, I have good information for you guys. I'm *fairly* noob, but not too bad. Here's exactly what I did:
I got a HTC Desire HD from Vodafone-Australia yesterday. I thought I'd root it, then consider cyanogenmod from there. I followed the instructions here: <cyanogenmod desire hd full upgrade guide from wiki> very closely.
I have never plugged a SIM into this phone. I've been using WiFi. Using my WiFi I downloaded ROMmanager and flash clockwork 3.0.0.5
I then did a backup. I didn't downgrade because the software number was 1.32.178.5.
I followed the instructions to get temporary, and then full SU access. This all seemed to work without a hitch.
I then flashed the engineering HBoot, specifically because it said it could help if I brick the phone.
I then flashed this radio: <radio in the wiki> Seemed to work, but don't know how to confirm.
NOW. This is where it went pear-shaped. I kind of liked the sense UI, but had been using cyanogen 6 on my nexus for ages. I wanted to see if I could flash Cyanogenmod while keeping the sense apps etc. So I told ROMmanager to flash, but NOT wipe the current ROM. I believe this was Cyanogen 6 (stable.) Can't remember full version number.
It rebooted, it flashed. Then went into a boot cycle. The cool Cyanogen loading screen would rotate a bit, then flicker, repeat. I figured "crap." And so went back into the bootloader -> backup and restore -> restored the latest backup.
I then got stuck on a white HTC screen. I figured, still stuck in a boot cycle... so I tried my other backup I'd taken when I first got the phone. White HTC screen again.
So I did a factory reset... still getting a White HTC screen. I start to panic. I tried variations on the theme of "format/wipe/flash" with no luck.
Eventually what I did was download Cyanogen 7 to the sdcard, then flashed that... and it worked!!!! PHEW. Not a brick at least.
Ok, so I figure - well now I have SOMETHING flashed, I can try flashing back my backups. No luck. Everything else leads to a white HTC screen - I've left it for hours at a time. It just won't boot.
So, ok, I have Cyanogenmod 7 running. However, my wifi now doesn't work. I turn it on, it stays on for about 10 seconds, then switches off. It never detects any wifi. In typing this, I figured I might have formated something to do with the radio... ? So I'll try reflashing the radio.
Anyway - can anyone help me? I'd really like to get back to stock if possible. In a pinch I'll settle for Cyanogenmod 7 with working wifi.
Why does only cyanogenmod 7 work? I've tried cyanogenmod 6, and several clockworkmod backups. Also this stock image <link stripped because I haven't posted enough. It was a link modaco.com>
Why does my wifi not work? Can I get stock back?
PS. I flashed the radio and it worked
PSS. I had to strip out all my links because I haven't posted enough on here.
I might have got it. I flashed Cyanogen 7, and as I said above that worked.
Now I have a working radio, I can download ROMmanager. I got ROMmanager to flash the stock ROM I downloaded -- and it worked.
Now all I have to decide is if I want stock ROM or cyanogen with HTC apps restored via titanium backup
dakuth said:
I might have got it. I flashed Cyanogen 7, and as I said above that worked.
Now I have a working radio, I can download ROMmanager. I got ROMmanager to flash the stock ROM I downloaded -- and it worked.
Now all I have to decide is if I want stock ROM or cyanogen with HTC apps restored via titanium backup
Click to expand...
Click to collapse
HTC Sense apps, in the main wont function without the sense framework which is missing from CM, so dont think you'll have much joy running them.
BTW your problem restoring your backups was due to the fact that you need cwm 2.x to flash pre-gingerbread builds and cwm 3.x to flash gingerbread builds

bacon-bits owned my phone few weeks ago, always wondered why

So... I seen baconbits shortly after rooting and flashing, I installed baconbits, phone booted, than right from start up I get forceclose on every app and process... than I tried to do a backup, I got an error on cwm so than I wiped data and tried to reflash fresh and start over, that would not work. So I recovered the stock froyo and fixed cwm than I flashed fire and ice cm7 rom.. everything has been fine since I fixed it.. it was still frustrating tho..
But when ever I go to my boot loader before recovery, I get this green font that says blah blah blah not found (its trying to locate files to install that stock froyo, but after it doesn't locate the file I'm free to access recovery or do whatever.. is there a way to delete that "cannot find" ****, it takes about 20 seconds from holding power and volume down to give me control.. that's why I want it gone its annoying.. even if I can't fix it, I guess its not a major setback..
melodicjunkie said:
So... I seen baconbits shortly after rooting and flashing, I installed baconbits, phone booted, than right from start up I get forceclose on every app and process... than I tried to do a backup, I got an error on cwm so than I wiped data and tried to reflash fresh and start over, that would not work. So I recovered the stock froyo and fixed cwm than I flashed fire and ice cm7 rom.. everything has been fine since I fixed it.. it was still frustrating tho..
But when ever I go to my boot loader before recovery, I get this green font that says blah blah blah not found (its trying to locate files to install that stock froyo, but after it doesn't locate the file I'm free to access recovery or do whatever.. is there a way to delete that "cannot find" ****, it takes about 20 seconds from holding power and volume down to give me control.. that's why I want it gone its annoying.. even if I can't fix it, I guess its not a major setback..
Click to expand...
Click to collapse
thats internal feature of Hboot... it looks for pc10img.zip on sd card.... not at all an error....
and it can be useful in a situation where you mess up your recovery and rom ... you would be able to save your phone via that ....
also its used to go back to stock rom and unroot when needed
+1 for hispeedword. Best possible answer right there - that's exactly what's going on. Use ROM Manager to reboot straight to recovery from now on and it will skip HBOOT so you don't have to wait through all of that. CM and most other roms also allow that option when you hold down the power button.
Now, you said "shortly after rooting and flashing" - what exactly did you flash? You do know baconbits is ONLY meant to be used with the stock rom right? The exact one that you rooted and that came on your phone. If you flash ANY other rom - even a 'stock rooted rom' then you run into tons of errors when flashing baconbits.
Dont flash baconbits, its not needed
Sent from my HTC Vision using XDA App
TheMod'sPolice said:
Dont flash baconbits, its not needed
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yeah I was being stupid, I didn't even know at the time when my phone messed up that it was from me flashing baconbits...until I did a back up, than flashed a different rom and reflashed baconbits, lmao..
so your saying to use baconbits if you rooted but didn't flash custom roms, than it works fine?
I'm thinking of switching to a sense rom, I don't even know why.. what are the pros/cons of sense? Thanks.
Assuming you've already answered your question up there, sense roms usually consume more battery life because of the plethora of constantly active widgets. However, if you're VERY social or buisiness, Id recommend it. The battery drain only cuts down on a few hours, depending on your usage, cpu governers and radio, and for that, you get a lot of functionality from the rom. Plus the new elegant blues ported theme for sense roms is just gorgeous. I also like the whole manual link to facebook in the contacts. Still hoping for a port for that xP try it out.
Sent from my HTC Vision using XDA Premium App

Can't flash custom roms

Hi all, I have a problem with my Desire Z. A few days ago I made root following instruction on wiki.cyanogenmod.com. Everything went fine until when I tried to flash custom rom. After each flash the phone will not boot and hangs at the boot screen. I tried MIUI, Virtuous Quattro RC1, RC2 and RC3, and even clean original rom from HTC. The only two roms I managed to install are ILWT CM7 and Virtuous Quattro Beta 9. Of course, I did full wipe before each flash. Can anyone help?
Flozik said:
Hi all, I have a problem with my Desire Z. A few days ago I made root following instruction on wiki.cyanogenmod.com. Everything went fine until when I tried to flash custom rom. After each flash the phone will not boot and hangs at the boot screen. I tried MIUI, Virtuous Quattro RC1, RC2 and RC3, and even clean original rom from HTC. The only two roms I managed to install are ILWT CM7 and Virtuous Quattro Beta 9. Of course, I did full wipe before each flash. Can anyone help?
Click to expand...
Click to collapse
I've got the same problem with the Virtuous Quattro roms, you can try JIBwitch, Andromadus or CyanogenMod 9 for ICS. Those roms worked on my Vision. Sadly I can't help you to get those other roms, I'm still trying to figure out why this happens, if I figure it out I'll post it here.
Thanks fo reply. I tried JIBwitch and Virtuous Unity and same result. Freeze during booting...
At loading a new rom, the first boot can take up to 10 minutes. But if do you an ADB logcat while booting you should see a constant flow of messages, if this isn't the case something is wrong indeed. I am now on CyanogenMod 9 pre-Alpha 2.5 and it works like a charm. Can you try that one, and look if your device is doing something upon boot, with logcat?
Thanks for reply again. I tried again flash JIBwitch with adb logcat and its working Anyway Virtuous roms (Unity and Quattro) still not working...
No problem, glad you can use your device with ICS.
Now to figure out why the Virtuous roms won't work, I tried so many things I can't remember what I've done anymore. The best I can think of right now is that it is an download error somehow. I'll try tonight if I can flash quattro rc3 with a copy downloaded at work, and a copy downloaded at home. I'll post my results here again.
As I thought it seems to be an download error, the file I downloaded at home wont boot, while the file I downloaded at work works fine. Can you try to download the Quattro rc3 over another network??
When you rooted you may have flashed the g2 engineering hboot. So, even though you have a desire z you have the bootloader from a g2. You need the desire z bootloader to run the virtuous stuff and almost all other sense roms. Anything 3.0 and above.
Sent from my HTC Vision using xda premium
There is information from my hboot screen:
Vision Pvt Eng S-off
Hboot-0.84.2000 (PC1011000)
Microp-0425
Radio-26.03.02.18M3
eMMC-boot
So I think, I have not hboot for G2 but for Desire Z. Or I am wrong?
I am going to try download Virtuous Quattro by another network and flash again. Anyway I tried check mdl5 sum for files that I used to download and its matched.
First off, hello!
That's actually a Desire Z Engineering HBOOT you have, and not the G2 one. Applying the G2 hboot on our phone can potentially brick the phone.
Now you are saying you're wiping before flashing, but do you use Superwipe? If not, it's strongly advised that you do. This tool erases the OS partitions and format them using the ext4 filesystem. In addition to that, it also cleans the "EFS Data". EFS data is temporary radio config data, and it is advised to wipe them every time you flash a new ROM, so the radio can reconfigure itself, which has proven to fix a lot of issues, mainly with GPS but not limited to that.
Anyways, I decided to upload a version of Superwipe I had found and used numerous times for easy access. Here is the link: http://www.mediafire.com/?iygmwd1a7zrfe9p (Don't be distracted by the "G2", it works the same for both phones!) Also, the MD5 is E0B0AF31F22EE06BDE7748195F8AE651
What recovery do you have? ClockworkMod or 4EXT? I presume you have Clockwork Mod 3, since you mentioned you used the cyanogenmod wiki, It is a good idea to switch over to 4EXT Touch which has a lot of bugs fixed over from CWM and is faster as well as safer in general. The 4EXT site is here:http://www.4ext.net/
All credit goes to madmaxx82 for his hard work!
With all that said, there have been several users who couldn't get VQ RC releases to boot on their devices, would always hang them on the white HTC screen. The reason is still unclear though, we'll have to wait for an update from the Virtuous DEV's. You, also might have the same issues, hence be uncapable of booting it considering that in your reply you mention you can successfully boot Beta 9 but none of the RC versions, which was the case for the people with the issue in question.
As far as MIUI is concerned...which MIUI distribution are you using? MIUIAndroid or MIUI.us? Or did you flash an ICS MIUI release found here, particularly cjward's one...it uses the Virtuous Quattro kernel, hence the reason it didn't boot on your device. If that's the case, anyway.
Thanks for all advices!
I used CWM Recovery v. 3.x.x.x and also 5.x.x.x (not exactly sure which versions...)
Today I was trying 4EXT and SuperWipe for flashing VQ RC3 downloaded over another than my home network. But with same results as past. Everytime booting pass over HTC screen and freeze on Virtuous logo. It's mystery....
About MIUI - I was trying to flash MIUI_Au 4.0.3. I think that uses Andromadus kernel or not?
Anyway I am really satisfied with Ice Cream JIBwitch rom!

Categories

Resources