Related
I have no clue what has hapened. I have my phone for some days and today I rooted my phone. After that I made my SD able for Apps2SD and in the end I thought of flashing the Radio. Something happened and now my phone gets stuck on the white screen with the HTC green letters. I don't know what to do. I reflashed with the some radio, reflashed with an older radio, searched on USB Bricked phone but from what I understand a USB bricked phone has nothing to do with my situation because you can actually start a USB bricked phone. I am so desperate and I have no clue what to do. PLEASE HELP!!!
Does it boot into bootloader mode?
Just do a factory reset and wipe cache if you can enter the recovery and ofc flash a rom.
Sent from my HTC Desire using XDA App
Yes it loads in bootloader mode and in recovery. I have tried to wipe the cache and to do a factory reset. Nothing worked.
Tried a new rom?
Sent from my HTC Desire using XDA App
Trying now, but the thing is that I didn't touch anything on the rom.
What exactly did you flash? Radio? Kernel?
Sent from my HTC Desire using XDA App
Mmm this sounds familiar.... you have to do a wipe for the ext partition in your sd card, try to power on without sd
I had this exact same issue when I made an EXT4 partition for Apps2SD. Despite the fact that the kernel in MCR, and the UVOC kernels apparently support EXT4, if you have an EXT4 formatted card, it won't boot. Format the Apps2SD partition back to EXT2 or EXT3 and it should work.
Also, you need the FAT32 partition at the beginning of the card, and the EXT partition at the end.
Tried powering on without the sd, no luck. The problem was created when flashing the Radio. I downloaded the official WWE ROM but in what mode should I bee for the installation to get the required information to continue?? Bootloader, fastboot, or recovery???
Get the rom.zip file from the update, and put it onto the root of your SD card named as PB99IMG.zip, and then boot into bootloader mode, with volume down and power. The phone should automatically detect the presence of the zip file and prompt you to flash it.
Did you try my other tip about formatting the A2SD partition?
I put it ni fastboot mode and it was recognized through the USB so new ROM is on its way and about the App2SD I tried to boot without the card to see if its that and it would still not boot
Guys that was fast... My phone is BACK!!! THANX EVERYONE... YOU ARE AWESOME!! One last question... now that I flashed with the original ROM does it mean it has been unrooted???
Most rooted roms have a superuser apk pre-installed.. have a check in the menu.
Sent from my HTC Desire using XDA App
Probably. I'd recommend you download the latest R6 risk free root from Modaco, it's far less likely to give you issues like that, as it omits the steps that caused the potential bricks.
Shane2 said:
Probably. I'd recommend you download the latest R6 risk free root from Modaco, it's far less likely to give you issues like that, as it omits the steps that caused the potential bricks.
Click to expand...
Click to collapse
Exactly what I did but still after trying to update the radio through the rooted phone my Desire was dead
An update to what has happened.
So, I have installed the original ROM " RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2 _release_126984_signed.exe" and have managed to get my phone back.
And then I rooted it again using the prementioned R6 risk free root from Modaco and all was OK. I turned it on and everything was fine. The, I wanted to push the Apps2SD and I followed the steps and then the phone wouldn't start again. (The SD was wiped cleaned just to be sure it was not a matter of the SD).
I did this 2 times to replicate the results and see where it actually gets stuck. So, I concluded that putting the Apps2SD to the rooted ROM of Modaco doesn't work.
Am I correct or am I doing something terribly wrong and I don't know about it???
HI there
i have the same problem like it switch on and white screen with htc logo while updating maybe i made something wrong\, this guide will work for m i think but can someone explain in detail cos i am not good in computer programing and zip and other things i really appreciate if some one help me in understanding language
the problem is same as this thread
thanks in advance and if someone can help me in messenger i will pay for the time which will take to fix this problem
So the radio Rom was not the issue?
Sent from my HTC Desire using XDA App
Shane2 said:
Get the rom.zip file from the update, and put it onto the root of your SD card named as PB99IMG.zip, and then boot into bootloader mode, with volume down and power. The phone should automatically detect the presence of the zip file and prompt you to flash it.
Did you try my other tip about formatting the A2SD partition?
Click to expand...
Click to collapse
I`v got the same problem with Desire. Where can I this "rom.zip" file ?
My phone-brand 2.2 froyo - rooted.
So my phone now will only reboot up to the HTC Incredible white screen. I'm not even sure what the issue is, all i did last before it got stuck was erase data on an old sd card i had in the phone. Then I just did a reboot and it froze on the white screen.
I'm running GB evervolv 2.3.2 with 2.6.37.4 incredikernel.
I can get into HBOOT but when i click on recovery it takes me into fastboot everytime.
What can i do to fix this????
Sorry please move this thread to the Q&A section, i thought that's where I was posting it, my bad.
Go to the Clockwork Recovery thread and download the update for a different version and try getting that to flash via bootloader. That way you can at least get into recovery if you need to flash new. Just to clear it up, did you use your phone to delete stuff off the old card, by using Astro or ES file explorer? I know ES file explorer has root access so is there a chance you could've deleted a system file on accident? All it takes is a click of the SD card icon and you're in root instead of SDcard. Also this is probably a thread more for the Q&A subforum, just an fyi
i deleted an old sd card that i don't even use for my phone, i was just putting it in there to clear out whatever was left on it. so i could use it new.
And it still bootloops even when you put your normal SD card back in?
yup, i dunno what it's deal is.
I remember an older version of cm7 on the nook color warned against formating sd cards because it accidentaly formats the boot partition, this may be a bug that exists in the rom your using.
at least you can get into hboot, you should be able to download ruu image and flash it in hboot. this would get you back to stock, then root and install clockwork, and then restore your latest nandroid.
Flash this recovery in hboot
http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
It should at least give you a working recovery.
i have to rename things as update.zip in order for hboot to flash them right??
facedown41 said:
i have to rename things as update.zip in order for hboot to flash them right??
Click to expand...
Click to collapse
NO leave it PB31IMG.ZIP.
hboot can only see that name. if you rename it hboot will not see it at all.
also make sure your card is formatted as FAT32
got it into recovery so i'm just wiping and restoring, thanks for the help!
ok now i'm getting a bootloop on the cm7 boot screen...i just went to flash that new instead of my nandroid because the nandroid was from an older rom.
Did you wipe everything? Davik, Cache, Data, etc?
wiped data and cache...didn't do davik because i've never had to in the past. but i'll give it a try.
would i need to update CMW from version 2.0+ to 3 in order for cm7 to work? because it's still bootlooping
THIS IS EXACTLY WHAT JUST HAPPENED TO ME!
i was on MIUI 1.3.25 (the newest GB release) and i was formatting an sd card and when i restarted my phone i got stuck at the splash screen! i have been able to boot back into cwm recovery but even when i wipe and flash, nothing works.
i booted into recovery and tried to restart from there - failed
i reflashed 3.18 (wiped cache/dalvik) - failed
i wiped all data and reflashed 3.18 - failed
wiped all, flashed 3.25, fixed permissions - stuck at splash screen again
restored an old MIUI (v1.1.15) - stuck at splash screen
pleaseee let me know if you figure this out
edit:
i ran the RUU and got stock to start working. i'm about to root and try flashing something
JWorth said:
THIS IS EXACTLY WHAT JUST HAPPENED TO ME!
i was on MIUI 1.3.25 (the newest GB release) and i was formatting an sd card and when i restarted my phone i got stuck at the splash screen! i have been able to boot back into cwm recovery but even when i wipe and flash, nothing works.
i booted into recovery and tried to restart from there - failed
i reflashed 3.18 (wiped cache/dalvik) - failed
i wiped all data and reflashed 3.18 - failed
wiped all, flashed 3.25, fixed permissions - stuck at splash screen again
restored an old MIUI (v1.1.15) - stuck at splash screen
pleaseee let me know if you figure this out
edit:
i ran the RUU and got stock to start working. i'm about to root and try flashing something
Click to expand...
Click to collapse
Are you getting errors when you wipe?like when you wipe data does it say error can't mount or anything like that.... I have a feeling you may have to flash an Ruu and then reroot
Sent from my Incredible using XDA App
no, no errors. but i flashed the RUU and rerooted and everything works just fine. I flashed MIUI again and it worked perfect
thanks!
I figured that's what you would have to do glad you are back running
Sent from my Incredible using XDA App
I always mount my sdcard in a linux and format/fix/repartion, or at least let Clockwork Recovery do it. I have never found a Sense, Vanilla, or AOSP ROM that handled SD partition operations very well, without at least a little tragedy.
Sent from my ADR6300 using XDA Premium App
rynosaur said:
I always mount my sdcard in a linux and format/fix/repartion, or at least let Clockwork Recovery do it. I have never found a Sense, Vanilla, or AOSP ROM that handled SD partition operations very well, without at least a little tragedy.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
This tends to be things go as far as ROMs partitioning my sd, always back it up externally and format/partition before transferring stuck back over to it while in phone.
Hi I'd apprecite assistance here.
It happened to me already before.
I did simple ROM backup of Andromadus B4 using ROM manager and from that time, device does loop reboot. It reboot itself until PIN is requested and than it loops reboot.
I had this twice before and what helped was to install again stock ROM with Goldcard, but this time i dont want to do it as i would loose root and have to go thru process again. Once they even changed my board in HTC service but it started to do same thing again after wihile.
What more i can try before start recovery with stock ROM.
advises appreciated.
Thansk.
Wipe everything, super wipe, fastboot -w
Then flash a new rom, something not beta and stable
If bthis doesn't work there may be something wrong with your emmc partitions, going stock may fix...
Sent from my HTC Vision using xda premium
And make sure you have the correct HBoot for certain ROMs.
- Sent from my POS G2
Thanks, i did superwipe with http://forum.xda-developers.com/showthread.php?t=1044992 flashed again Andro B4 and voala it works again, no loop reboots anymore.
So marking this as solved
Hi.
I'm hoping someone can help. I've just fastboot flashed the Alpharev Stock Hboot back to my phone as I've previously been using cm7r2.
Now however when I flash 'sense' Roms or 'JB' roms all is well until I reboot into recovery and then I get the ATTN. Recovery is in safe mode this is because the following partition is not accessible "System" etc.
This only happens with the two types of roms mentioned!
If I flash 'Froyo' or 'GB' aosp roms all is well! I can reboot into recovery as many times as I like without trouble??
Any ideas?
Thanks in advance:good:
myarse said:
Hi.
I'm hoping someone can help. I've just fastboot flashed the Alpharev Stock Hboot back to my phone as I've previously been using cm7r2.
Now however when I flash 'sense' Roms or 'JB' roms all is well until I reboot into recovery and then I get the ATTN. Recovery is in safe mode this is because the following partition is not accessible "System" etc.
This only happens with the two types of roms mentioned!
If I flash 'Froyo' or 'GB' aosp roms all is well! I can reboot into recovery as many times as I like without trouble??
Any ideas?
Thanks in advance:good:
Click to expand...
Click to collapse
I had this with some roms aswell, all you need to is wipe all except sdcard and reboot recovery and then its fine
Sent from my HTC Desire using xda app-developers app
sywats said:
I had this with some roms aswell, all you need to is wipe all except sdcard and reboot recovery and then its fine
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Hi, thanks for the reply.
Yes I agree that works in as much as there is no lasting problem. However the problem I have is rebooting to flash extras onto the rom, this cannot be done as I have to wipe system and hence the rom is useless.
Any other ideas
Just delete the 4ext folder off your SD-Card and reboot into recovery and all will be fine.
Same thing happens to me and this resolves the issue every time.
Thanks for your replies.
I did try deleting the 4ext folder but it didn't make any difference.
However I did try rebooting recovery without wiping anything and that seems to have done the trick!:fingers-crossed:
Thanks again.
Hi,
I have problem with my HTC Desire Z (Vision). I have S-OFF by this tutorial - Cyanogenmod Install CM for vision and when I install any rom I have bootloop, after configuring my device...
I tried all tricks but the problem is still on my htc...
Can anybody help me?
which roms specifically have you tried?
write down everything on boot loader screen (yes everything)
can you get a logcat of boot loop?
does it boot to os then at reboot you get a boot loop?
if so what specifically did you do before reboot?
give as much information as possible and help will be better
This has happened to me, what i did was re flash cwm touch through Odin. I was using cwm 6.0.2.9 touch when it started to boot loop.
Sent from my SCH-I535 using xda premium
ace000724 said:
This has happened to me, what i did was re flash cwm touch through Odin. I was using cwm 6.0.2.9 touch when it started to boot loop.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
which isnt an option for anyone using an htc phone....
demkantor said:
which isnt an option for anyone using an htc phone....
Click to expand...
Click to collapse
Yup... But, I back to my stock rom couse I need phone not zombie and I can't write any informations...
I remember that I have hBoot - 0.84.2000 and nothing more... ;/
EDIT:
A yo..
I have backed to custom rom, and it's similar problem.
My info:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.18_M3
eMMC-boot
Sep 8 2010, 15:56:38
and ClockworkMod Recovery 5.0.2.7
Odp: Bootloop on Custom Rom
Anybody can help me?
Sent from my Nexus 7 using xda app-developers app
Try a full wipe, fastboot -w, superwipe script, whatever, just make sure phone is fully wiped. Then download a known working rom like cm7, flash that and then the gapps from recovery, reboot and let it sit a few minuets. What happens then
Sent from my MyTouch 4G Slide using xda premium
I used SuperWipe script, and I have the same problem...
I have installed MIUI and this rom have too problems... ;/
Any ideas? I don't want use old stock rom... ;/
it sounds like your doing everything right, can you pull a logcat to look at? for now read over these
HOW TO FLASH YOUR FIRST ROM
and
BOOTLOOP OR BRICK?
demkantor said:
it sounds like your doing everything right, can you pull a logcat to look at? for now read over these
HOW TO FLASH YOUR FIRST ROM
and
BOOTLOOP OR BRICK?
Click to expand...
Click to collapse
LOL, I can't do anything on Andromadus with ADB...
I try ext4 and I post here if problems with custom rom ends..
EDIT:
I have ext4 and I have the same problem...
This is link to my logcat from stock android with 1.34 version: Logcat
If this help - I have phone with chip from Sandisk
Well, I think that nobody can help me? I think that I need back to old, lag stock rom...
EDIT:
I got it!
Well I do this steps:
I have rooted my device with this tutorial: Install CM for vision and I have install 4ext Recovery on stock Android 1.34.
Next step is format all your partition to ext4 and install custom rom.
Now is very important step - BACKUP your custom rom to your SDCARD. Again install stock rom (1.34) and root system.
Again format all partitions on phone to ext4 with 4ext Recovery. RESTORE your Custom Rom and s'il vous plaît très - ENJOY YOUR CUSTOM ROM!
That's steps help me to install Custom Rom without any bootlooping. But now I have problem with SDCARD, but I think this problem is becouse Andromadus is testing version.
wow be patient a little, be happy people are wiling to help when they have time
first off the logcat was for a rom that booted, that is hard to help figure out why something didnt boot. having the sandisk emmc is good but you werent showing signs of a fried emmc so no biggie either way
first of lets just do this step by step quick ok
flash THIS or THIS in recovery, then reboot recovery
now flash THIS ROM
when finished flash THESE GAPPS
now reboot
wait even ten minuets to load
if not get me a logcat of this NOT booting
edit
i see you got things settled, good
but just so you know there is no need to back up and restore your stock rom before flashing a custom one
i figure the reason why it worked for you this time was the formatting of partitions to ext4 (needed for jb roms)
or just the fact that your formatted completely wiped your partitions something i dont think was happening before
either way im glad you go it handled, but from now on just do complete wipes between flashed and youll be fine
Odp: Bootloop on Custom Rom
Hey, thank u for your help With my problem!
Sent from my Nexus 7 using xda app-developers app