Database Users

stuck on white htc screen

So i have a desire hd from Three, which is unlocked and unbranded, i rooted the phone via the visionary method, got s-off, used rom manager to install clockwork mod recovery which was 2.5.1 something rather, then i created a backup, upgraded to clockwork 3.0.0.1, tried to install the cyanogenmod 6.1.3 via rom manager but didnt work, so i downloaded the zip file manually and tried to update via clockwork mod recovery now in 3.0, restarted, and am now stuck at the main HTC screen. Pulled the battery, then went back into clockwork recovery, tried to recover the backup i made, rebooted, but still stuck on htc white screen... dont know what to do help!

You could try flashing a RUU to go back to stock 1.32 would be best or you would need to downgrade to root, or you could try getting another rom image on your SD card isnt clockwork 3 4 ginger bread nightlies?
Just throwing ideas out there. Personally I would go woth the RUU.

Thanks for the reply, i remember finding some links with ruu's but i'm not sure which one i need and how to use it ?

Sorry just thought the other thing is how long did you leave it. I have read about people leaving for 30 mins and then it boots..

Start downloading this. Its the RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26 .03.02.26_M_release_155891_signed
http://www.multiupload.com/N333WKVW6M
while downloading leave your phone to boot it might surprise you..

I left it for a while but maybe not long enough, perhaps 15 minutes at one point? i'll try again, should i wipe data in clockwork and then reflash the cyanogenmod again? is it ok to keep the phone plugged into the computer via usb?

Sorry, once downloaded just run the EXE, it will walk you through the steps.
The Dev section has a lot of useful stuff in it for this sort of thing the 1st post http://forum.xda-developers.com/showthread.php?t=936214 is pretty usefull.

djamorpheus said:
I left it for a while but maybe not long enough, perhaps 15 minutes at one point? i'll try again, should i wipe data in clockwork and then reflash the cyanogenmod again? is it ok to keep the phone plugged into the computer via usb?
Click to expand...
Click to collapse
Worth a go whilst downloading, I would wipe 1st. Its good you still have your recovey partition (clockwork) so you should be fine. Use the RUU as the last resort as it will wipe recovery part and loose SOFF etc.. But should fix the phone.

Right so i've wiped data/factory reset and cache partition and dalvik cache, then went to choose zip from sd, chose update-cm-6.1.3-DesireHD-signed.zip, says Welcome to CyanogenMod-6.1.2-desireHD (strange?) completed. Now went to Reboot system now and waiting, still on HTC screen.

is it possible to put another rom on the sd card? i dont have a computer that i can plug the mini sd into, possible in recovery mode?

djamorpheus said:
is it possible to put another rom on the sd card? i dont have a computer that i can plug the mini sd into, possible in recovery mode?
Click to expand...
Click to collapse
yes, but i dont know how of the top of my head, i will have a look in the dev forums, i think you use fastboot and u can push files. Hopefully someone with a bit more knowledge will see this post soon. I will have a look though.

so its been 30 minutes, and it's still at the htc screen... what should i do? should i try the RUU ? i dont want to brick my phone...

from what i can find fastboot will not push files, adb but may not connect on splash screen. You could just try pulling the battery and leaving it again to boot for a bit, mine has hung before like that. The Ruu should go through and connect to phone and go through flashing. Do you have another phone that could take the SD card? im gonna boot my phone to recovery and try to push a rom to it or file.

ok i am reading this post,http://forum.xda-developers.com/showthread.php?t=558812
what i would do is goto recovery mode,
he command is:
adb shell mount /sdcard
adb push c:\******.*** /sdcard
exemple with g:\update.zip :
adb push g:\update.zip /sdcard
usefull when wrong rom flashed and no sdcard reader ^^

So i downloaded a cyanogenmod 7 nightly build, installed with with clockwork 3.0.0.5, and it worked, booted in, but had a continuous logo loop, going to try leedroid

Good luck, Leedroid rocks, thats what i use. I would say if it is still looping try the ruu and then start again. The RUU will esentially factory reset.

Installed the latest Cyanogen nightly build #23, and it works perfectly now should i keep it? or should i try leedroid? i kind of want to keep using htc sense, as i have all my contacts on it..

Up to you really. I went back to leedroid because it seems faster and more stable for me and I like some of the sense widgets.
Sent from my Desire HD using XDA App

[q] excited to see twrp 2.0 recovery on our beloved nookcolor!

Ok. Let me start by saying, I'm obviously not an expert on hacking/developing and stuff like that. I just love to tinker stuff so I learn in the process. So definitely not an expert. Just posted this thread hoping that someone whose possibly a lot more knowledgeable than I am would notice it and hopefully shed a light on this question.
Is TWRP 2.0 which can be seen here, working/compatible/available/will be available on our beloved NookColor?
All we are using right now is the ClockWorkMod Recoveries, right? Which I believe the latest is 3.2.0.1. I'm not saying at all that CWM is not sufficient enough to do whatever it needs to do, I just thought it would be awesome to be able to get your recovery things done THAT MUCH COOLER, navigating the device via the touchscreen rather than hardware buttons.
Hope this sparks more awareness!

+1 - I would like to see TWRP on our devices as well, BUT ... I would definitely miss the convenience of being able to install the nightlies directly from ROM manager.
OK, saying that, I also just had a perma-brick on my Nook and am getting a replacement due to an issue that occurred in recovery. I was stuck in the infamous CWR boot-loop, so did a restore, when I went to reboot, screen itself would never come on again - not after charge, not after holding buttons, nothing.
Is it related, I don't know, maybe not, but makes you think.

majorpay said:
+1 - I would like to see TWRP on our devices as well, BUT ... I would definitely miss the convenience of being able to install the nightlies directly from ROM manager.
OK, saying that, I also just had a perma-brick on my Nook and am getting a replacement due to an issue that occurred in recovery. I was stuck in the infamous CWR boot-loop, so did a restore, when I went to reboot, screen itself would never come on again - not after charge, not after holding buttons, nothing.
Is it related, I don't know, maybe not, but makes you think.
Click to expand...
Click to collapse
Oooh, that's too bad. And scary. Makes you worry about doing something that's not tried on the NookColor before. I wont dive in unless the devs really says that it's safe.
Hey, about your NC being bricked. I had something pretty similar happened to my NookColor before. Got stuck into a boot loop. Now before, I had my TitaniumBackup folder stored in the eMMC and I didn't want to do anything that would delete it. What I did is, I had another microSD card and created a bootable CWM. I installed a CM7 nightly on the microSD. Upon booting to the microSD build, I went and have adb wireless transfer my eMMC files to my PC. Now that I've recovered my TitaniumBackup folder, I formatted everything on my NC using the bootable CWM. Then what I did is I flashed the stock NC Rom which was 1.2 version. I did a factory reset. After that I had everything back to normal again. I flashed the nightly build on the eMMC again and from then on, had my TitaniumBackup folder on the microSD. Have you tried creating a bootable microSD?

A little late...
Did you try a formatted bootable sdcard? The nook is near indestructible. I had the same issue and recovered.

fr4nk1yn said:
Did you try a formatted bootable sdcard? The nook is near indestructible. I had the same issue and recovered.
Click to expand...
Click to collapse
Same here, I put together a nookie froyo card, and got bootloops.I took the memcard out and still got bootloops. I put a cwm card in, and STILL got bootloops. Then I made a new cwm card, and it booted just fine.

Half bricked Transformer

Hey there,
I have trouble! I was playing with chrooted ubuntu, busybox, and so..
Than, I started getting error in terminal apps:
sh: applet not found
WiFi stopped working.
I tried cold boot.. Did not help.
SDCard is not accessible. I decided to wipe it. In recovery I choosed Wipe Data/Factory reset.
But after that, still no WiFi. I can see networks, I can click on them, but it is still getting IP address..
I would like to flash the ROM, but how? Recovery cannot mount /sdcard!
What should I do? Thank you
(asus transformer, sbkv2, B80)

i just got over the same exact issues caused by the same exact thing.
The only way to fix it was to flash either stock or a modified rom. What do you mean recovery cant mount sdcard. If you have cwm installed just put a rom on your microsd and use cwm to flash it. If you dont have cwm yet then you can take the stock firmware off the asus website, put it on the internal or external sdcard boot the transformer like normal, and you will see a little exclamation mark next to the clock in the bottom right corner, click it and it will take you through the motions of upgrading then reboot and reflash. o you probably lost root access too, I know i did, so reroot when done if you want.

There's no such thing as "half-bricked". It's dead or it's not. Yours fortunately still does stuff so you can keep trying.
Could it be this sdcard is moody? Tried a different sdcard?
Alternative ways could be using nvflash while connected to a PC with the USB cable. There are many guides on this forum.
Good luck.

Blaskovic said:
Hey there,
I have trouble! I was playing with chrooted ubuntu, busybox, and so..
Than, I started getting error in terminal apps:
sh: applet not found
WiFi stopped working.
I tried cold boot.. Did not help.
SDCard is not accessible. I decided to wipe it. In recovery I choosed Wipe Data/Factory reset.
But after that, still no WiFi. I can see networks, I can click on them, but it is still getting IP address..
I would like to flash the ROM, but how? Recovery cannot mount /sdcard!
What should I do? Thank you
(asus transformer, sbkv2, B80)
Click to expand...
Click to collapse
You do have an external micro sd card correct?
You can try Team Rouge's CWM recovery, it work with internal sd card.
There's a modified RecoveryInstaller here that will flash Team Rouge's recovery
http://forum.xda-developers.com/showpost.php?p=22359727&postcount=218

After 2 days of trying, I did it
I rebooted it about 2 milions times. He did not see the SD card. But then he finally mounted it and I quickly installed ROM.. uhh..
So, it was my Asus Transformer's PMS or something
Thanks you guys. It was a fight

So.. I'm about to start tinkering with ubuntu on my TF101... I did this on my Droid 4 with no issues, the Tablet is next on the list... What exactly did you do to hose the tablet?
I just want to try to learn from your mistake.
Thanks.

[Q] Need HELP with bootloop

I cannot seem to find this problem anywhere else here but forgive me if it is. I have a TF101 I believe pre B70 although I can't find anything that says that but I bought it in Aug of 2011. I have CWM 5.8.3.4 which was installed with the rom manager first mistake as it can't access my ext SD card. I had JB and wanted to go back to Revolution Rom as I was having some SOD issues and decided to use Super wipe. I think Super wipe froze as I was using it and after waiting 15 minutes after the 3rd format I rebooted. The CWM problem which existed before is that in order to not boot into CWM I had to hold the Vol down button and then when I got to WIPE DATA or ANDROID screen I could chose android and it would boot into the rom. I tried NVflash and ADB in APX mode and although device manager says it is in APX mode in I cannot get it to react to any commands. I have tried deleting and reinstalling the drivers from google and asus but nothing seems to work. I am not sure if I could use odin although I don't think it is recognized there either. I tried another computer and nothing. One thing I did do in CWMR is format everything but now I can't get it to mount /data. Any help would be appreciated

Try this advice from baseballfanz.......
http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3

Cant mount sd card
scottyf79 said:
Try this advice from baseballfanz.......
http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3
Click to expand...
Click to collapse
Thank you for replying but
I cannot put anything on the sd card because
1 it won't mount
2 can't push anything to it because the computer won't see it (although device manager has it as APX)

jonnygee said:
Thank you for replying but
I cannot put anything on the sd card because
1 it won't mount
2 can't push anything to it because the computer won't see it (although device manager has it as APX)
Click to expand...
Click to collapse
Im selling mine :laugh:
bad joke but hey :silly:

Got it
So I tried on a third computer and finally got the drivers to work in NVflash which took it back to Honeycomb. Wow what a relief.

[Q] Bootloader Ics v3.14.8 + Recovery Twrp v2.1.3, after you hit install?

Hey all! I've been lurking around XDA for years for various devices. I'm good with computers but newer to Android/Linux. And I don't have much of a programming background. I have done some installing of custom ROMS on a phone of mine and even dabbling in a kitchen some. So it's not totally foreign to me.
I've been reading about custom ROMS on and off for a few months thinking about installing a custom ROM. And then actually reading and researching it the last day or two. Since we're not going to get Jelly Bean I decided finally to update to a custom Jelly Bean ROM. I am finding all the information very unorganized and very spread out. And not very comprehensive. Which is making it hard to get a good grasp of everything. Things like what SKBs are and APX mode. And exactly what processes you need to take to install which ROMS. If you need to install a kernel or it does it automatically ect. Very confusing! I thought I had figured out enough to do it.
On my A500 I had the latest Acer ICS OTA update but rooted. I want to install the CM10 Jellytime ROM. I did a factory reset. Using AfterOTA v1.09 I installed first "Bootloader Ics v3.14.8+Thor v1.7.3". Then after that I changed to "Bootloader Ics v3.14.8+Recovery Twrp v2.1.3. It seemed to work fine. I got into the bootloader. I have the Jellytime ZIP file on my external SD card. The first time I think I just clicked install, picked the ZIP and did the swipe to install. Which brings me to my big question. What is it supposed to do after that? It just went back to the Recovery boot animation and back into the recovery without seemingly doing anything. If I rebooted holding the Vol-, it would just go into Recovery and not flash anything. If I just let it boot it would boot the factory ROM. The Thor recovery did something similar.
I then did the wiping/formatting of all of the cache, factory resets and system. And when I tried to install it again basically the same results. Except now it won't boot into the factory ROM since I wiped the system. Which will also not let it connect over USB and to the AfterOTA. If I turn it on holding the Vol+ and get the boot menu and pick the fastboot it tries to do the fastboot but just hangs on the Fastboot notification.
I've been searching and reading but can't figure out if I didn't do something I should have or missed a step. Any help would be appreciated.

Ah! I figured it out! I didn't realize that even though you're using a custom recovery program that you still have to name the ROM file "update.zip". I thought that might be the case but couldn't connect the tablet to the computer via USB and didn't have an SD adapter to connect the card to the computer and change the name. I ended up getting a card adapter. After I changed the name it worked.

briwayjones said:
Ah! I figured it out! I didn't realize that even though you're using a custom recovery program that you still have to name the ROM file "update.zip". I thought that might be the case but couldn't connect the tablet to the computer via USB and didn't have an SD adapter to connect the card to the computer and change the name. I ended up getting a card adapter. After I changed the name it worked.
Click to expand...
Click to collapse
great, thanks for posting your solution