Previously I had no problems booting up. Today, I S-offed my phone and did a lot of messing around (like flashing partition tables and stuff), but every time I was able to boot up without any issues.
This is my second time booting up after installing GingerVillain, and I'm stuck at the Why So Serious screen. That's really weird, because previously I was able to reboot (because Android Market website couldn't detect my device).
Ugh. Any ideas?
Check if your hboot (I assume you flashed another one because you're s-off) has enough space for gingervillian.
TouchPaled from Oxygen with Transparent XDA App
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Related
I've recently rooted (unrevoked) and flashed my HTC Desire with Cynogen 6.1.
This worked for the first couple of days until my phone suddenly turned off. Now I cannot get it to boot past the white HTC bootscreen, unless I flash it again with a custom rom (tried Cynogen again, OpenDesire and Miui) with a complete factory reset. Then it will boot once into Android, but after a reboot the same problem occurs.
I've been reading numerous topics on this and similar problems and it seems I have to unroot my phone. Is this correct? On some sites there are warnings you should not root/unroot with a certain hboot version. Is this still the case?; because the unrevoked method states that it rootes no matter what the hboot version is.
So I'm planning to go back to stock now by following the unlocker.com unroot tutorial and flashing a htc europe stock rom (I have the HTC Desire from T-Mobile Dutch).
I'm posting this topic to double check, because I do not want to brick my phone completely
Thanks in advance.
You are right, just flash a stock rom and start rooting again. It doesn't matter anymore which boot version you are using. You have a go
Ok, thank you, will do and will post my results here ;-) I understand from you answer that unrooting and rooting again may fix this issue?
It's possible, you could also try a different SD card. Maybe that is also causing the problems, but unroot first and if that doens't solve it, try switching your sd card. Make sure you use at least a class 4.
Hi all, long time lurker, first time poster!
I've just installed the InsertCoin v20 on my S-OFF, CM7 Hboot HTC desire, and it has been stuck on the htc screen for ages now.
I've reflashed it many times, including the radio (32.44.00.32U_5.09.05.30_2), the recovery (clockwork v3), and the rom. nothing seems to be working.
I have a feeling it might have been the bootscreen I flashed - I flashed the original HTC boot screen from alpharev website.
Does anybody have any ideas! I did a full wipe before flashing this rom (I came from Cyanogen 7)
8ball2253 said:
Hi all, long time lurker, first time poster!
I've just installed the InsertCoin v20 on my S-OFF, CM7 Hboot HTC desire, and it has been stuck on the htc screen for ages now.
I've reflashed it many times, including the radio (32.44.00.32U_5.09.05.30_2), the recovery (clockwork v3), and the rom. nothing seems to be working.
I have a feeling it might have been the bootscreen I flashed - I flashed the original HTC boot screen from alpharev website.
Does anybody have any ideas! I did a full wipe before flashing this rom (I came from Cyanogen 7)
Click to expand...
Click to collapse
Does the rom fit the cm7 partition table? If it's too big then the phone won't boot, though Iffr think recovery should still work in that scenario.
Also check the md5sum of the boot image file - search on Google for a free tool for doing this.
Are you able to boot to bootloader?
stringer7 said:
Does the rom fit the cm7 partition table? If it's too big then the phone won't boot, though Iffr think recovery should still work in that scenario.
Also check the md5sum of the boot image file - search on Google for a free tool for doing this.
Are you able to boot to bootloader?
Click to expand...
Click to collapse
Insertcoin should work on CM7 hboot, so they say, so it's some other problem he's experiencing I guess. Maybe he forgot to make an ext partition on the SD card...
CSharpe you hit the nail on the head...I completely forgot to make the ext3 partition on my SD card. It was driving me mad last night, I only wish you had told me sooner, I was up until 6am sorting it out!
Thank you!
Hi guys,
I've got a Problem with my Desire: It won't boot up, it's simply stuck at the HTC screen, but I can access the Recovery though. I did a full wipe but still the same problem.
Any idea what's wrong with my phone? This whole thing started when I wanted to reboot it due to connectivity issues with my WiFi network. I used the reboot command from the advanced power menu.
Technical details:
Amoled Desire, Running InsertCoin Nightly A2SD, S-OFF using Alpharev, Stock H-Boot, 8GB Sd-Card.
Many Thanks in advance
Please use the Q&A Forum for questions Thanks
Moving to Q&A
camille93 said:
Hi guys,
I've got a Problem with my Desire: It won't boot up, it's simply stuck at the HTC screen, but I can access the Recovery though. I did a full wipe but still the same problem.
Any idea what's wrong with my phone? This whole thing started when I wanted to reboot it due to connectivity issues with my WiFi network. I used the reboot command from the advanced power menu.
Click to expand...
Click to collapse
I'd try reinstalling kernel or rom, or restoring /system and boot from backup if you have one. It looks to me that something is wrong with kernel modules stored on /system partition (more likely) or with kernel itself (less likely)
Thank you
Reinstalling the rom did indeed the job
I rooted my phone a couple of months ago (HTC Desire) running version 7 of Cyanogenmod and decided it was time to have a look around at other roms. So i downloaded LeeDroid on ROM Manager on my phone and selected all the additional extras and it downloaded and installed itself (or I thought it did). Then the phone rebooted and it ran through script about the phone making some weird R2D2 sound in the process, but it kept looping around, i left it for an hour and it was still going. So i removed the battery and tried again and it won't start now. If i boot it up, it boots up to the flashing Android screen and if i boot it into boodloader and try fast boot it does exactly the same. Any ideas?
LeeClark93 said:
I rooted my phone a couple of months ago (HTC Desire) running version 7 of Cyanogenmod and decided it was time to have a look around at other roms. So i downloaded LeeDroid on ROM Manager on my phone and selected all the additional extras and it downloaded and installed itself (or I thought it did). Then the phone rebooted and it ran through script about the phone making some weird R2D2 sound in the process, but it kept looping around, i left it for an hour and it was still going. So i removed the battery and tried again and it won't start now. If i boot it up, it boots up to the flashing Android screen and if i boot it into boodloader and try fast boot it does exactly the same. Any ideas?
Click to expand...
Click to collapse
which hboot are you using? make sure to use htboot which has enough space in /system partition for the ROM you are trying to flash. also check the md5 of the downloaded file with the one provided in the website.
providing more details will help people in the forum to guide you in right direction.
Hello everyone,
First, I would like to thanks everyone who can contribute or help out with this issue that I've been dealing with all day (literally spending the past 7 hours on forums browsing and searching - wish I can say that this is an overstatement)...but in the end, I still have yet to find a solution so now I turn to you guy....and if not obvious already, I'm a super noob at all this as well as any attempt to use the adb/sdk program
Here's the problem: (I'll try to make it as simple and put the most relevant info on here)
I have a Inspire 4g/Desire HD rooted with S-off that was working fine w/ CM7 until last night...phone just started to act up and restarting by itself and ended up being stuck on the endless blue loop CM7 flashscreen
due to my carelessness and having a old back up, I was just decided to format everything format data/cache, re-flashed the cm7 rom and then recover with the old back up (all done in recovery)
however...here's where the problem starts: (i'm guessing it's likely d/t my bad back-up)
on restart, I am "stuck" at the white/htc screen - I have to hard reset (battery out) everytime
HBOOT is still functional - so I know i haven't bricked my phone yet...so...i tried going back to recovery, but this time i passes the white/htc screen, but briefly goes into the green circle with a down arrow and then permanently to the red caution triangle with the exclamation mark....so I was thinking the recovery must of crapped out on me....(factory reset via hboot was non-functional either, similar result: green circle --> resets to htc/white screen)
Thus, I tried doing an "Clean" recovery using STOCK ATT roms renamed to PD98IMG.ZIP on my SD card (found here: http://forum.xda-developers.com/showthread.php?t=1191959&highlight=Stock+Rom)...however, it always fails to unzip the system portion (tried with various other "clean stock" roms also, same unzipping problem) - this led me to do some more forum hunting in which that I might have a faulty CWM
So it led me to the discovery of the Android Flasher utility application where I have attempted to flash a new CWM to the phone - however, android flasher doesn't "detect" my device - so I followed the instruction here: http://forum.xda-developers.com/showthread.php?t=737728 to have my phone recognized by my computer...i attempted to flash CWM again onto the phone via android flasher...but no luck, I'm still getting a "device not plugged in or driver not installed" message...
I am now exhausted and out of ideas...(not to mention angry/mad at myself)
Thanks again for all your helps/comments, I really appreciates it.
Hi mate, wrong forum, this is DESIRE, not DESIRE HD one. Been reported to move to right one, you maybe get more help there
kotag82 said:
Hi mate, wrong forum, this is DESIRE, not DESIRE HD one. Been reported to move to right one, you maybe get more help there
Click to expand...
Click to collapse
Either you're mistaken or it's been moved