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!
Related
For two months I have tried to install Cm6 and currently shadow rom. Every time after install from clockwork or nandroid I get the same bootloop splash htc screen. I have installed other roms with no problem....there must be a common issue with cm6 & shadowrom. I have wiped full, cache, davlik and even formated system cache etc. I have a 2.x radio kouche kernel and newest hboot. I've tried changing sd cards etc. No avail......any suggestions would be appreciated.
SamuraiXDroid
I would try wiping dalvik/cache before the flash, flashing, then wiping dalvik/cache again before the first boot of the new rom. I would also suggest trying kings kernel or koush's test kernel by flashing them from cwm recovery directly after the rom.
Aside from that, I could only guess that you might have a corrupt area preventing a full install of your rom/kernel which isn't too uncommon but which I have no experience with. I've heard there are ways to get around this by building the kernel manually or by restoring it from another nandroid (say king's on a ruby nandroid? though I'd venture to guess Ruby would have the same problem), but it seems fairly difficult.
I'm not a developer, but I hope my suggestions can hope point you in the right direction. I'm using the latest nightlies of CM6 and they are awesome. I hope you get the chance to try it.
Thanks jaguox for such a quick reply. So I tried this.method on both cm6 and shadowrom. Wiped full wiped cache wiped davlik. Installed rom and gapp and kernel. Tried koush and kingkernal....wiped davlik...cm6 boot loop.....shadowrom brings me to android touch screen initial setup. I try to touch screen but my phone dosnt respond....screen freeze. Sussesful installs I've had are sky raider virtuous most.sense roms...the only froyo I have that works is ruby...my fav right now. I would love to have cm 6....I've posted on this forum a few times as well as cyanogen forum. I hope im not the only one with this.issue.......
SamuraiXDroid
Here are some more ways to potentially solve your problem. Again, I am not a developer so I am just mentioning a few solutions that might work, I am not entirely sure what is wrong with your device. I'm just trying to help you hammer away from all sides.
Are you wiping data manually too? People have noted success before where they had none before by wiping data/dalvik/cache twice before flash and once after. Not sure why this would solve anything but it is worth a try.
Try installing cyanogen without GApps (I do this anyways with the nightlies since it seems to be corrupt for some reason) and then installing them later if it boots correctly.
I use the Paid rom manager for the ease of use for nightlies, but here is a web link to the nightlies which you can try if you don't have paid: http://mirror.teamdouche.net/?device=inc They are more up to date and stable at this point than 6.0.2 was (for me at least). I am using build 100 and have tried the packaged in kernel, koush test 6, and adrynalyne's, and all work well.
Adrynalyne has another kernel for AOSP roms you can try: http://adrynalyne.us/?p=79
You can also try using the phone to reformat one of your SD cards just to eliminate that potential pitfall, though I don't think you would be getting that far anyways if it was not formatted correctly (Menu>Settings>SD card). This will wipe any data currently on your SD card.
Now, I would wait for someone else to provide confirmation that this should work since I haven't done it personally, but you could also try restoring boot.img from a Ruby Nandroid with KK1/2 installed (Install Ruby, install KK, make nandroid backup, install CM6 w/o Gapps, nandroid>advanced restore>select ruby nandroid>Restore boot). This should restore a working AOSP kernel for CM6/shadow to use however I am unaware if there are any other consequences. I also suggest KK or adrynalyne since I do not know what Ruby uses and KK and adrynalyne have both worked for me on CM6. The reason I think the kernel is not installing correctly is because your touchscreen is not working and AOSP roms use a different driver than sense roms for it. I could be completely off base however.
Also, out of curiosity, which radio version exactly are you using?
Hi Jaguox,
Thanks again for the help here is what I tried. I do own the market app ClockworkMod Revovery v2.5.0.5/rom manager. I came from Ruby 1.1.1 with the newest kouch Kernal and radio 2.15.00.07.28. I then wiped data, cache and dalvik twice. I then installed cm nightley 96&98/shadowrom (two seperate installs of course for each rom). I then installed Adrynalyne/Kingkernal kernals and wiped dalvik cache once more. I did not install gapps and let the rom boot. Interesting enough the roms bypassed the intial setup and booted to the home screen. But both roms with both kernals still would not let me have touch access to the screen. So I could see the roms but I couldnt touch them...aaaahhhhhhh the irony. I also tried a reformatted sd card.....same outcome. One time out of the hundred I have tried in the past two months allowed me to initiate my account in a cm nightly and access apps. I rebooted after a fix permission and got a boot loop. That was the farthest I have ever made it. Its strange that both these two roms that share the same dna give my phone the same effect. I appreciate anyones help in solving this mystery.
Thanks in advance!
?
SamuraiXDroid
Same issue on my Dinc. I have.wiped, rewiped and.still.the same out come on 2.1. I did not have this issue when I installed the first release of SR a while back. I have no other issues with other ROM's. Help?
Sent from my ADR6300 using XDA App
So shadow rom first release woked for you? There must be some common denominater for why our phones cannot take certain aosp roms? Ruby works but not cm6 or shadow......very strange.
So I think shadow rom found the fix to the issue I was having....hopefully this thread helps anyone in the same vote as me.
http://forum.xda-developers.com/showthread.php?t=808972
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
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
I'm having trouble installing any roms on my girlfriends desire. Installing roms seems to work fine, right up until i try to boot the phone, it just gets stuck at the HTC screen, I've pulled the battery and tried again, but nothing works. I've tried multiple roms, and with every one, the same problem.
The phone is rooted, HBOOT 0.93.0001, S-ON, Baseband 32.54.00.32U_5.14.05.17
Anyone know what's going on? It's been a while since I've played with android phones, so I'm not current with all the lingo. I'm currently a WP7 user
Thanks for the help!
I'm assuming then it would be a2sd Rom?? Your ext3 or 4 setup? ROM manager sucks for this, use gparted or minitools(I've never used this one) and preferably a card reader.
Sent from my HTC Desire
Ya, I tried ROM manager for the partition, I'll give gparted a shot. thanks!
Ok, formatted the sd card, and repartitioned to FAT32, and 512mb of EXT3 and the same thing happens, it just hangs at the HTC screen after installing a rom.
How long are you giving it before pulling the battery? It can take 10 or 15 minutes on first boot. I'm assuming you've tried a couple of different roms.
yes, I have tried a few different ones. I'd say the longest I waited was around 25-30 minutes. In my previous experience flashing hero roms, the most I had ever had to wait for those was about 5 minutes, so I assumed the 30 minutes was long enough, and decided that nothing was going to happen.
A Dustman said:
yes, I have tried a few different ones. I'd say the longest I waited was around 25-30 minutes. In my previous experience flashing hero roms, the most I had ever had to wait for those was about 5 minutes, so I assumed the 30 minutes was long enough, and decided that nothing was going to happen.
Click to expand...
Click to collapse
i'm a previous hero owner, same thing happend to me, desire is different.
on all desire roms the op will tell you what hboot is made for and then to flash the alignement zip even if your sdcard is partioned , you have to otherwise the will never bootup and then you flash the rom plus whatever updates they suggest .
i think your hboot is stock, same as mine, but you need to S-off your phone in order to flash any roms, follow this guide: http://forum.xda-developers.com/showthread.php?t=1016084
try cool sensation or what ever takes your fancy
1-download the alignement zip , the rom and the updates if there are any
2- put all of them on your sd card (mount it or use usb card adapter)
3- go to recovery and flash them in sequence, usually alignement zip first + the rom and then reboot should be about 5 to 10mn any longer you in a bootloop means something wrong.
just have a good read before flashing any rom , and follow what they say.from step 1 till the end.
you'll get there, don't worry it wont brick your phone
I was under the impression that S-Off wasn't necessary for all roms, for example insert coin cm7. I could not get my computer to successfully boot from my flashdrive to perform the s-off with alpharev, so I skipped that step
I also flashed the alignment zip, and still had the same problem.
A Dustman said:
I was under the impression that S-Off wasn't necessary for all roms, for example insert coin cm7. I could not get my computer to successfully boot from my flashdrive to perform the s-off with alpharev, so I skipped that step
I also flashed the alignment zip, and still had the same problem.
Click to expand...
Click to collapse
You don't need s-off to flash roms, I'm not and flashed many. Make sure your installing roms for the stock hboot, cm7 won't work. From what I've seen unless your having problems with your ext the alignment patches can be more trouble than good.
Sent from my HTC Desire
Thanks a lot! I found a rom that works with the stock hboot, and it worked perfectly!
What rom are you using with the stock hboot? I'm having same problem.
Also I'm assuming cm7 is cyanogenmod7, i thought it worked with the stock hboot?
Ok, so I'm having another issue now... The market is not working, I tap it, and it brings up a white loading screen for about half a second then disappears. I tried a reset, and I still have the same problem. Is there something I need to flash in order for it to work? The rom I'm on is cool sensation v6, and I didn't see anything there about anyone having market issues, so I'm not sure what the problem is.
Thanks again
EDIT: I notice that under accounts and sync, it says that sync is currently experiencing problems
EDIT EDIT: I just remembered that with my old hero, I had to first sync over 3g only, tried that, and it solved my problem.
Under Applications, find the market and try clearing the cache
A Dustman said:
I could not get my computer to successfully boot from my flashdrive to perform the s-off with alpharev, so I skipped that step
Click to expand...
Click to collapse
Did you create a bootable usb drive?
firepanda said:
What rom are you using with the stock hboot? I'm having same problem.
Also I'm assuming cm7 is cyanogenmod7, i thought it worked with the stock hboot?
Click to expand...
Click to collapse
It's a bit misleading, cm7 does not refer to cyanogenmod7 but cm7 partion table.
You will usually find 2 different versions of most popular ROMs.
1. A2sd
apps2sd, usually A2sd+. This requires the stock partion table. You do not need to be S-off to flash these ROMs
2. CM7
This refers to the CM7 partion table (custom Hboot). To repartion your nand you need to be S-off. These ROMs are data++ ROMs.
So, no you do not need to be S-off to flash custom ROMs, you do need to be S-off to resize your partion tables. More info in this thread:
This explains Data++ versus A2SD very well:
http://forum.xda-developers.com/showthread.php?p=14615477#post14615477
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