Hi,
It's just like a nightmare...
My i780 had been bricked.
However, there is no problem to flash any rom,and no error occurs.
But, since I have to take a Hardware Reset after flashing, the nightmare starts...
It is frozen after I press "space" to have a hw reset! Nothing changed even after 1 hour!
Then I try to power it up, but it only shows the Samsung logo.
And it's more surprising that when I charge up. The red led shows up, and the screen shows that
"Formatting
Please wait just for a while"
It will never disappear.
So, ...anybody have ideas?
Whatever rom I flashed, it's successful, but fails to reset.
I think, since I can't apply a hw rest after flashing image, the image won't really be flashed. And it seems the hw reset trap into an endless loop. Now what should I do?
BTW, I found that there is someone similar to mine...
Just like http://forum.xda-developers.com/showthread.php?t=479819
Help! Help me out of the nightmare...
Related
Hello,
I finally had the nerve to flash to Black 2.5 with the latest hard spl. The issue I have had is when I do a soft reset, I would see the AT&T logo and it would just sit there. Sometimes I would have to soft reset it multiple times before it shows the Black 2.5 Splash Screen.
Any ideas? Bad flash? should I reflash?
Thanks!
Umm.. i guess reflash, i don't have this problem.
Well actually i did. I would soft reset and it'd get stuck in the beginning so i'd soft reset again then in get stuck in bootloader mode. I was on the road and was panicking. So i unplugged the battery and plugged it back in and it'd go straight to bootloader. Did this several times and gave up. Got home ready to reflash my device but something came up, So i just plugged it into the charger, took care of my business, came back 25 min later (still in bootloader) soft reset and it was back to normal. So my problem was low power.
fone_fanatic said:
Umm.. i guess reflash, i don't have this problem.
Well actually i did. I would soft reset and it'd get stuck in the beginning so i'd soft reset again then in get stuck in bootloader mode. I was on the road and was panicking. So i unplugged the battery and plugged it back in and it'd go straight to bootloader. Did this several times and gave up. Got home ready to reflash my device but something came up, So i just plugged it into the charger, took care of my business, came back 25 min later (still in bootloader) soft reset and it was back to normal. So my problem was low power.
Click to expand...
Click to collapse
had the same problem several times: startup takes about 3 minutes and after that my device is incredibly slow...
softreset again (and again sometimes) and the problems are gone.
did a hard-reset en restore, but this issue occurred again a few times.
now installed LVSW (23-04-2007) for a while to see if it's ROM related (I think is is). but Black still is my favorite...
firebird2k said:
Hello,
I finally had the nerve to flash to Black 2.5 with the latest hard spl. The issue I have had is when I do a soft reset, I would see the AT&T logo and it would just sit there. Sometimes I would have to soft reset it multiple times before it shows the Black 2.5 Splash Screen.
Any ideas? Bad flash? should I reflash?
Thanks!
Click to expand...
Click to collapse
This can be caused by allsorts of things, most likely a 3rd party app causing problems on startup.
What have you got installed?
The only app I have installed the latest version of Dashboard from snoopsoft and iLauncher that might affect startup. However, I had those installed with previous WM6 releases with no apparent issues.
Hi!
I had a quit similar problem. It was gone after cleaning up the root of my microsd. After moving the stuff into folders this behavior disappear.
It looks like if there are a lot of files in the root, I have problems booting up, and I have to softreset several times till it comes back to normal. Just my experience....
hi everybody..
i've got a serious problem..
here's the story..
i was trying to upgrade to the touch v7 by mr. gullum.
after downgrading my prophet to the no vendor id rom, i upgraded my device to the touch v7.
next i tried to hard reset my prophet, realised that i can't do it cuz my camera button is not working.
went to a phone repair shop and fixed the button..the solder was..loose? i mean, the thing was unconnected from the pcb.
fixed it and tried to hard reset again.
black screen of hard reset appeared, but when i released the comm button, it went straight to the white screen showing os ver and ipl, spl ver.
tried to hard reset again and failed, it entered the white screen where we can restore rom dumps..i immediately pressed the comm button and camera button again..and it started formatting the bnfs..thing?
still can't do hard reset, tried to flash the no vendor id again, and this is the problem..i get stuck on 95% and after that it jumps to 100% straight away.
tried to flash gullum's touch v7 but i got the message that no device detected...tried pv 5.0.0.0.5b, pv 4.00.0.6, nanoscopic all with same result...
anyone can help?
oh maybe this will help:
when i tried to flash the no vendor id again, what shows up is this..(see attachment) the from image version is blank..
on the 95% where i get stuck, the progress bar on my device turns red as when it happens on the 80%.
thank you, everybody...
progress..
hi there,
it's not that usual mistake people make..i think i've screwed my hardware too..
now, my previous problem was unable to hard reset because my camera button was not working..the solder was loose..
i've soldered it and the problem was after every succesful attempt to flash 'no vendor id' rom, it resets and goes to bootloader screen again (tricolor screen)..
late last nite, i tried to hard reset after succesful flash of 'no vendor id' rom (after it resets and enters the bootloader screen)..i succeeded to get into the black screen of hard reset but when i released the comm button, it went straight into the htc white screen without me being able to press any button at all..
everything went well though, and it went to the 'tap screen to set up your device'..at this point i tried to flash the 'nanoscopic' rom (last rom i use before i messed up this phone)..it went well!
after succesful attempt, i tried to hard reset again (no luck again), but after the htc screen shows up, the nanoscopic splash screen appeared!!!
whew, i thought i had my phone fixed already, but when i did a clear storage, it resets and enters into bootloader screen again! i tried soft reset via software and via manual way, and it enters the bootloader screen everytime!
now, i've fiddled some more and i now realise that just by pressing the comm button and doing soft reset can make me go into the bootloader screen..i'm guessing that the technician at the phone shop soldered wrongly...and now my comm button works as camera button too..
i think he accidentaly soldered some other button too to the comm button and that's why i always get into the htc white screen after i release the comm button in the black screen of hard reset..
i'm going to go back to the shop again after work today, but i'm still confused about the way my device enters bootloader after every reset (hard reset and soft reset)..
a friend gave an opinion that maybe, like in desktop, (there's the bios then there's the operating system), the 'bios' of my device is ****ed up?
any help greatly appreciated!
Hey!
Im new to this forum but there seems to be a lot of experts here so i thought i'd try and see if anyone could help me!
Yesterday i put my desire to charge and after one hour i came back and it was showing the boot screen! The white background with the 3 green letters HTC! so i took out the battery and put it in again and restarted the phone but it only gets to that screen vibrates like 10 times and then hangs there! tried waiting for it for 30 min but nothing...
So then i tried to hard reset it and cleared the storage! but afterwards still the same!
Also when in "recovery mode" i sometimes see some green text flashing by for just a sec saying something like "warning...no image...."
Everything is in its original state, i havent rooted or reflashed it or anything... but i am willing to do so if it can solve my problems since warranty matters in my case will take ages!
The phones language is Swedish btw!
Can anyone help me?? its first now that u realize how much the phone means to you Miss my desire!
it sounds like the firmware is somehow corrupted. If you can boot the phone by pressing power and volume down, this will take you to the bootloader. From here you should be able to root the handset by following any number of threads here or on modaco!
Then I'd go Here and install this recovery. From then on you can choose a custom or stock rom to install.
You need to know though that rooting will void your warranty.
Have you also tried booting the phone normally with the SD card removed?
I need a bit of help with a stock HTC One X. As of this morning it won't boot up. I have made no changes to the ROM, everything is stock.
Tried entering the recovery panel and turning fastboot on then restarting but every time the system stops at the "HTC One" page after making a startup sound. Sometimes the screen will go black and hitting the volume keys will bring up the volume changer but that is it.
There was no warning of an OTA update or anything like that.
When charging the screen stays on and dims, but stays on the "HTC One" screen.
Factory reset HOX and it booted, but next day same issues. This is 3 times I've had to factory reset now.
Every time I restart or cold boot it freezes on the "One X" screen.
This exact same thing has just happened to me! Just 10 minutes ago
I have no idea what to do.
I have not attempted root or anything like that everything is stock (Optus from allphones).
All I did was restart and now I cannot get into the phone.
I can get to those options (fastboot) by holding down the volume down button and the power button but restarting it or powering it off there does not help.
I havn't tried a factory reset yet as I'm scared about loosing all my data.
Can someone please help!
Please please
I'm suprised someone else is having the exact same issue what the hell is happening
Have you tried using the Recovery option from the Bootloader?
Yeah I tried that.
It didn't do anything. I've since done a factory reset. That worked but I've now lost everything
Now that's it's allw whiped I figure I might as well root it and install android revolution. I hope it's just a software thing and this will fix it.
Pyrope said:
Yeah I tried that.
It didn't do anything. I've since done a factory reset. That worked but I've now lost everything
Now that's it's allw whiped I figure I might as well root it and install android revolution. I hope it's just a software thing and this will fix it.
Click to expand...
Click to collapse
Fair enough, if you're thinking of Rooting and installing ARHD etc then feel free to use my Guide : The Stock to Custom ROM Awesomeness guide
It'll take you from Stock to having ARHD on your phone ok
(Shameless plug)
http://forum.xda-developers.com/showthread.php?p=30471180#post30471180
Took it into HTC last night and had the firmware flashed. No problems now... 12 hours with numerous restarts just to make sure.
It looks like it was a corruption in the software. I noticed HTC turned off the fast boot option before giving the phone back to me. Took 30 minutes in total.
If it happens again, try to hold the power button and the "Homepage" button at the same time. You should see a grey box saying "Continue holding to restart".
Thats a full restart rather than a shell restart.
That may help.
Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?
try to flash twrp with Odin and download mode. Then enter recovery, connect it to PC and make some space.
But I really doubt it, apps won't install even when you have 500Mb free, so I think it might be hardware problem