Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
Please try to enter the bootloader mode in a bright room as it is very difficult to see in poorly lit environment. Till you enter the bootloader mode your device will not be recognised. Perhaps one of the three keys is getting released..the light button is the usual culprit. Once you are in the bootloader you can reflash.
Thank d_ranade for your answer.
I am sure the screen is 'all black' and I've tried to press the buttons several times.
I think the main problem now is how to enter the Bootloader.
I sometimes find it takes several goes to get into Bootloader mode. If not, have you tried a hard reset?
I've tried whatever i can do. Hard reset is useless too.
quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
I have sent you a pm, it should help you.
-Jwrightmcps
Thank Jwrightmcps for your help, but i can not enter the Bootloader ,so can not use mtty to do more.
Unable to start/see bootloader
I seem to have the same problem with my upgraded universal which was working fine for about ten days. Then I installed TomTom on it and again it was all working that evening.
Then, when I turned it on the screen went blank (white), so I re-flashed it, but, part way through the screen went black, so I left it connected for further hour and nothing. I have since been unable to get it to do anything, it is not recognised by activesynch, it will not charge (either from the mains or the USB on either of the batteries) nor will it turn on or respond in any way.
I have unset ‘allow usb connections’. I have tried solidly for +/-10 minutes doing the backlight + on/off button and reset bit - repeatedly, with my wife helping to ensure all buttons were being pressed. All I got was a message from MicroSoft telling me that ‘One of the USB devices attached to this computer has malfunctioned and Windows does not recognize it’. The only positive thing is that every time I do it and depress the reset, the red LED flashes (provided I leave the USB cable in) but at no point have either of us been able to see any writing on the screen.
Any guidance (apart from where to take it for recycling) would be welcome…
It happened to me several times too. Even in the old ROMS. But had learned many things out of it. I removed the battery. Wait for several seconds or maybe minute before placing it back. And after placing it back wait again for some time before doing the "power + light + reset" (bootloader). At some point when I am in the bootloader mode already and reflashing, connected to the PC already, the screen went blank again. So I'm sure that something went wrong again. I repeated the procedure again (removing battery, placing it back etc...) and the reflashing continued. It takes patience (maybe).
After having experienced this so many times, I'm beginning to assume that it is not because the battery is "bad" or there is a problem on the ROM being reflashed. It is on how it (the battery) is connected to the unit. The reason why it does not turn on, charge even if connected to the charger, does not hard reset, does not react to anything... I just don't know.
One thing more, the procedure I said above sometimes does not work at once. But at least I managed to "resurrect" my device several times.
This I am sure, it is not in the ROM that is being flashed or the update...
Hope this helps,
Lelen
lelen, Thanks for your assistance. I tried last night, but it still could not enter the bootloader mode...
I have the same problem =( and i don't know what to do, someone told me that i have to change motherbord to resolve this problem, i hope there are some other solutions.
Dead Uni
I too had this problem. With the device not responding at all and not able to enter bootloader stops mtty from working.
Only way i could get it to work was to take it to an O2 shop to send it away for repair (luckily the O2 XDA range has a 2 year warranty and because its completely dead they cant tell the OS has been modified).
Unfortunatly like the previous post i think it can only be fixed by replacing the mainboard.
Hi all, i found this thread http://forum.xda-developers.com/showthread.php?t=291097&page=6
so many people have the same problem , and nobody found a solution? i can't believe that on all this universals died motherboard, and there is no way to fix it with some special cable or some programm.
yes,i post the last reply of the thread you mentioned above, but nobody can resolve it.
I recommend you remove the battery and leave it over night. Put the battery back on, ensure it is properly mouted and try booting it.
It worked for some, no idea why though. I'm actually suspecting a bad battery mounting, which results in the motherboard unable to detect a battery is iserted, thus refusing to boot.
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
coolbeans252 said:
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
Click to expand...
Click to collapse
i guess thats what i will have to end up doing
anyone goten repairs done in north america?
( i live in western canada)
got the same problem
sofene said:
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
Click to expand...
Click to collapse
hi..please let me know if your device is fixed and how you managed to fix it. my email id is [email protected]
http://forum.xda-developers.com/show...6&postcount=52
Related
Hello everyone, my first experience of upgrading the firmware is sadly failed and now my beloved m5000 is only a beautiful paperweight!!!
No key combination could start the bootloader nor soft or hard reset works.
When I connect it to mains charger, the right led goes red for few seconds and then goes off...
In the service manual I have read that this signal means hardware failure but because the fault is the consequence of a failed upgrade I don't thing that it is really broken.
I already tried to contact htc and orange for repairing but in Italy where I live it seems that the warranty isn't valid and services are very scarce.
Someone have an hint?
Thanks.
Try to do a hard reset, many manage to get that white screen.
Thank you for the suggestion but it doesn't work The phone is completely dead, except for the red led. Any key combination including hard reset simply doesn't work.
I suspect that the only way to resurrect it is to reflash using a jtag interface.
But unluckily I don't own the pinout!!!
take a look here: http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen for instructions on how to use the mtty utility to bring your device "back to life"
There's additional information on the mtty utility in this thread: http://forum.xda-developers.com/showthread.php?t=259003
hope this helps
If you are on the bootloader menu...
Try to flash again a complete rom + extended rom + Radio
SOmetimes it can work again
sigh... thanks to everyone but I can't reach the bootloader menu: the uni is bricked!
My only hope is to find the jtag pinout...
Try holding down Light + power for at least 5sec. and while still pressing, do a soft reset.
If you dont go to BootLoader then try to increase the Hold down Light + Power some more.
This worked for me, could again get it active on usb and ran my original rom upgrade while it was in BootLoader mode.
If that dossent work, try the bootloader upgrade version at
http://wiki.xda-developers.com/inde...tion On How To Upgrade with Bootloader method
You can do the same with the two - - buttons, holding for more than 5sec. then soft reset. Should bring up the Reset with 0 or X to cancel.
But it just reverted to a brick every time for me with this.
BTW. do this with USB or Power Cable plugged in!!
another possibility is that your battery is low enough not to allow booting but is still able to light up the LED. it happened to me a few times that i was thinking it was completely gone and it was just low bat. remember that if you have a non booting device it may not even charge the battery anymore so you'd better ask a friend to lend you a charged one, just to be sure.
cheers!
Ill Buy The Brick!
au$200.00 in your paypal account upon a sale +50 to Australia.
Let me know...
Simon
Still Charging
I have 2 wizards and a universal... By mistake, i have tried to upgrade the G3 wizard but pluged the G4!!!!!...... So now i have abricked G4 wizard. Now when i plug the G4 it does NOTHING, it is completly dead, BUT is still charging the Battery!!!! I am sure of this because i have tested the battery in the other device.. So try the same on universal plug it in and wait a few hours it may charge the battery.
anyway, if you can't unbrick it, do me me know if u're selling it.
need some spare parts.
Suggestion
What you can also try is remove Activesync from your desktop, Restart your desktop, install Activesync again and connect your device.
It's word a try! Has something to with rapi.dll!
Cheers...
Leo
My failure...
Hello everyone, I've tried all yours suggestion one by one and step by step but without success.
My last chance to not consider this phone a complete loss is to sell it as spares/repair...
Does someone is interested?
P.S.: notwithstanding the phone is bricked it still charge the battery
Try holding the the two - softkeyes for longer/shorter time before you softreset while still holding them down.
Also try different intervals with the softbuttons while holding the Power + Light down, also with soft+Light & soft+power & power+light
all with different intervals.
Look closely at the screen after each try, to se if it goes to bootloader mode.
And remove SD card and Sim also.
I Hate Bootloader!
I have tried ALL of these power+light+reset suggestions and I STILL can't get into the damn bootloader menu! I just gave up and rip apart my JasJar every time I want to update it. For some reason the only way I can access this menu is by pulling the main battery and disconnecting the smaller(watch battery) one in the upper right hand corner and letting it sit for a couple of hours.
Come to think of it, when I use even the factory updates I don't even get a report on the update screen telling me what my current config is! So then I hit update anyway, the unit turns off, I lose my USB connection, it no longer charges, and I have to take the battery out. Almost like the PROGRAM can't even get it into the loader! This is probably how I learned to just yank the batteries when I want to upload.
Unless there is something different because I have an earlier model... I have no clue. Does the unit need to be running or something when I do this? I think this is a fairly elementary task but it just doesn't work. Has this happened to anyone else?
Yes, all my buttons are in working order = )
BTW after my last tear-down I have -
Bootloader: 1.01
Rom version: Ivan-2.60.00WWE
Rom date: 12/20/06
Radio version:1.14.00
ExtRom version: Modified
http://forum.xda-developers.com/showthread.php?t=247440&page=14 I think someone already suggested this, but just in case...
No chances
Well, today I've verified my battery and it works like a charm in the uni of a friend. Then the last possibility is gone.
Someone knows how to go ahead any further?
Hello,
I have a strange problem with my HTC Artemis (O2 XDA branded, bought in Germany, no lock)
It behaves unstable and indeterministic.
Unstable means that it crashes/stucks or turns off.
Indeterministic means that it happens when i plugg it to charger, when i'm syncing, when a phone rings, when using applications/tomtom or just i arrive to work and i find the device off.
When it crashes or i find it off, the biggest problem is to boot the device. It takes me typically 10mins, when i'm always trying to press the power button, push the reset button or unplugg the battery for a while in random order until i bring it to work.
After first crach, the device also often crashes or stucks again during the boot process.
Once, the device was so dead, that it took me two days to bring it into bootloader mode and then i could at least flash the ROM.
All these was happening with ARTEMIS TOUCH 4.01 WWE - LITE NO CUBE.
Yesterday, i switched to ARTEMIS TOUCH 4.02 WWE - LITE NO CUBE (burned FW twice) without installing any other applications and the problems are still here
My personal feeling is that it is getting every week worser.
When i bought the device (eBay), there was original FW with Win Mobile 5 on it, i immediately flashed to ARTEMIS TOUCH 3.01(?) WWE - FULL WITH CUBE, i can only remember that that time I had a problem with gsm radio - from time to time i found it stucked/off - to bring it to work i had to reset the device. So i flashed to 4.01 and this issue was away, but approx 2months ago, the above described behaviour has started and nowdays i'm fighting with it 2-3x a day.
so, can anybody help?
GiZMo
Similar here
I have a similar problem, what's really strange to me is, that as far as i can recall it started happening 2 months ago or so also!! weird huh...
my device simply reboots from time to time! even while i'm making a call.
the weird thing about these reboots is that when it comes back to live i do not have to enter my pin to enable the phone! everytime i perform a manual reboot (by software, using the pin or remove battery) i have to insert my pin to able to make a call...
i have upgraded from 3.01 full touch to 4.02 full touch about the time it started, i have now 4.02 vanilla touch but problem still occurs from time to time.
any ideas?
Im another one to join this boat!
Bought an MDA C 3, two days ago, bought of someone from gumtree.com.
Worked fine for the first hour, and then locked up - nothing on the screen, no LED. Only way to get it going was to remove battery and then press power button.
I upgraded the ROM from the original t-mob UK WM5 to mechles fine release: http://forum.xda-developers.com/showthread.php?t=371182
The lock-ups / crashes have now become rarer, on average every 4 hours (before was every 1 hour).
There is no pattern to them either, although I have saw the screen trun all corrupted just before it happens. The last one was caused when I pressed the 'start' button.
I'm on a T-Mob contract, and lost my Kaiser, got ripped of when I tryed to replace it by a tosser on here for $375 Thief on the loose thread, and was hoping my luck had changed when I bought this one!!
It is T-mob branded and I wonder if there isn't a fix on here, would T-Mob repair it under warranty??
same "issue" with no entering of PIN after reboot. But not always
GiZMoSK said:
ARTEMIS TOUCH 3.01(?) WWE - FULL WITH CUBE, i can only remember that that time I had a problem with gsm radio - from time to time i found it stucked/off - to bring it to work i had to reset the device.
Click to expand...
Click to collapse
here i found a good description of that issue:
"
Originally Posted by lasertony
I've got the same problem as !Novy, but nobody seems to have noticed his question. Are there any other guys out there with this strange problem ? I have been using this rom for a while and sometimes, without any visual warning the phone freezes up. This is particularly ennoying because there is no way to check wether it is working or not. Every other function or software keeps working ! The phone is just not receiving any calls or sms. So you can miss an entire day of calls and sms without knowing... Only when trying to call somebody the dialer says 'Dialing...' and nothing happens. No connection.
A soft reset is needed to get the phone working again.
"
btw, now i'm again trying to turn the device on, it's again stuck. grrr
Hello,
i had a few weeks ago a similar strange behaviour.
After changing the sd-card I had problems to turn the device on. After a hard reset it began to boot but hang.
The I flashed back to original O2 ROM. Then I had a unpredictable behaviour. Somtimes no sound. Sometimes I cound not be called. Sometimes Error message "no sim card". After every reset i had an other error.
Hard reset and flashing was no solution. Removing battery for less than 4 hours has no effect.
Then I wanted to send it back for repair. I took of the battery. The next day I wanted to try a last time and surprise: The device works fine without an error. Its hard to believe, but the removal of the battery for more than 8 hours was the solution.
Now I use it for 5 weeks without a problem.
regards
Andre
It is Happening to my device too!!
It stucks every 2-3 hours!Tried many of the cooked ROMs but nothing.Also tried all the radio roms for 1-2 days.still the same!
It stucks with no particular reason.SOmetimes in s2u2 sometimes when am receiving a call.... etc.
Had the pin problem too for 3-4 times!
I will try your sugestion ANDRE and we will see!
Also i will try flashing the original rom,cid unlock and then flash the cood rom twice!
Fingers crosed....
Andre1210 said:
Its hard to believe, but the removal of the battery for more than 8 hours was the solution.
Now I use it for 5 weeks without a problem.
Click to expand...
Click to collapse
didn't help
happy u
now, i will try to flash back original german o2 rom
I think mine is sorted now, thanks to a new battery.
Installed it on Wednesday and hasn't died/crashed once since then.
I did notice before that the battery was getting warm, and I stuck the handset on the vent of my AC in the car, and this seemed to make the phone more stable.
Got one from Deal Extreme or try the XDA shop.
It worked for me!!
bricked or not?
did my device get bricked?
last friday i wanted to change firmware and during step1-cid unlocking (device should never been cid locked) pda got stucked. So i unplugged it and since then i cannot turn it on or get it into bootloader mode.
the only proof of life is when I take away battery and plugg it to power supply, then the red diod turns on and off for 1/2sec.
any idea what to do?
Vinnie1 said:
I think mine is sorted now, thanks to a new battery.
Installed it on Wednesday and hasn't died/crashed once since then.
I did notice before that the battery was getting warm, and I stuck the handset on the vent of my AC in the car, and this seemed to make the phone more stable.
Got one from Deal Extreme or try the XDA shop.
It worked for me!!
Click to expand...
Click to collapse
I thought it was a battery problem too, but I've 2 batteries and both are died in the same time? I think it's too strange...
My P3300 have this problem from when it is returned from assistence and with original firmware (without other applications).
dude i think u bricked ur device i am sorry to convey such a message!
now its time for CPR go to xda wiki and try the SD flashing get ur device back to life man
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
GiZMoSK said:
did my device get bricked?
last friday i wanted to change firmware and during step1-cid unlocking (device should never been cid locked) pda got stucked. So i unplugged it and since then i cannot turn it on or get it into bootloader mode.
the only proof of life is when I take away battery and plugg it to power supply, then the red diod turns on and off for 1/2sec.
any idea what to do?
Click to expand...
Click to collapse
jahrami said:
dude i think u bricked ur device i am sorry to convey such a message!
now its time for CPR go to xda wiki and try the SD flashing get ur device back to life man
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
Click to expand...
Click to collapse
but i cannot get into bootloader mode so no flashing from SD card or PC
bricked device
so my device ist still dead
is there any possibility to hard flash bootloader (when corrupt)? or the only way is to change the mainboard?
GiZMoSK said:
so my device ist still dead
is there any possibility to hard flash bootloader (when corrupt)? or the only way is to change the mainboard?
Click to expand...
Click to collapse
the good sign are the leds that means you have a very good chance...the guy made the piont...check the wiki
random crashes are often caused by hardware malfunction...sometimes the connection on the motherboard stuck,get broken or make a short-circuit...so check the hardware
I was updating my Dash the other day to Ookba's latest rom when I received an error message. It gave me instructions on how to fix it (loading it in bootloader etc.), and I received a message saying it was successful and the rom would continue updating. I received another error message saying the rom was corrupt, and the program shutdown. My phone will not power up now. It was at(or near) full charge while reflashing, but will not turn on regardless of the button combination I hold while attempting to power it on.
Any ideas? Thanks!
what rom did you attempt to load in the bootloader? it should have been the factory rom..if not, then that is probably the root of the problem....as far as it not powering on now...I leave that open to the forum...cuz' I have no relevant advice on that one....
when trying to do the gold card method to unbrick my phone, it say Invalid certificate ..? wats this and how to fix it.
I was trying the "[ROM][EXCA][WWE][* 3VOLUTION SERIES *][WM6.5 STD 21854][Build 3VO.3.00.112509]" when it locked up on me, and still hasn't been able to power up.
Today when plugging it in after a week of letting sit, a red led light showed where the normal orange/green led would normally light up when charging/charged. The light stayed on for a few seconds, then shut off. Nothing else though. Any other suggestions?
allthrottle said:
I was trying the "[ROM][EXCA][WWE][* 3VOLUTION SERIES *][WM6.5 STD 21854][Build 3VO.3.00.112509]" when it locked up on me, and still hasn't been able to power up.
Today when plugging it in after a week of letting sit, a red led light showed where the normal orange/green led would normally light up when charging/charged. The light stayed on for a few seconds, then shut off. Nothing else though. Any other suggestions?
Click to expand...
Click to collapse
Red light my friend means your battery is gone, probably your phone is not bricked maybe it just needs a battery replacement
I am having the same issue, except that I can place the battery in another Dash and it boots up just fine, so I am assuming it is not the battery. I will buy another one to double check. My problem is the same as which is stated above. Can anyone help? Thank you.
Just an update to see if I can get anymore suggestions. Hadn't touched the phone since the last post. Bought a new battery for it this weekend and it's still dead as ever. Won't boot at all. Not into bootloader, nothing. I get absolutely no response holding power+cam or softkeys+power.
Any advice? I don't absolutely need the phone as I've picked up a G1, but it would be nice to have this working, or at least trash it if it's junk.
Thanks!
Everyone else stumped too?
Have you connected to the wall charger to see if you get some response with your new battery?.
Just unbricked mine after being dropped again by the girlfriend. Try this, plus usb cable into device, press the camera button only. See if that gets you into the bootloader screen. If so, flash the oem build and go from there.
Tried it plugged into a wall charger for 3-4 hours, car charger for another hour, and computer/usb for another hour. No response anytime.
I'll try the camera only method when I get home later.
Thanks!
Just tried plugging it into the computer and holding only the camera. Didn't work. Tried that, tried holding power+cam, power+soft keys etc.. What's weird is I had the battery cover off while doing this, and the battery slipped out while I was holding cam+pwr, it actually loaded into the multicolor(bootloader?) screen twice, but would shutoff within a few seconds. Now I'm back to no response from it.
Finally got it to stay on the boot screen without turning off, but can't get it to establish an activesync with the computer so I can't flash it. The computer is obviously detecting it though, because I see an icon that says "remove smartphone usb sync".
The phone's FINALLY working again! Thanks again guys! I was a couple of days away from junking the thing! I couldn't get Ookba's rom to flash it, so I went back to the unbricking tutorial and saw that he recommended grabbing the factory rom to flash it. I did, it worked, and I just flashed it again using Ookba's rom.
Took quite a few months, but it's back! Thanks!
pls help me ..i lost connection ugrading to a new rom...now my xda exec universal is dea...even cant get into bootloeader..onmy soft reset and when i press the O for factory defoulds .still does nothing just goes to its dark screen
put it in to bootloader and flash a new rom.
universal dead
thanxs for the replay ..the universal dont even gets in bootloader. when i press the 3 keys for geting in the bootloader ,it does not .what else can i do???
Please read the wiki before posting:
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
I think what dekyprio is saying is that the Uni does nothing while powered on. I have the same issue on my side, so for now my Uni is waiting in a box for the process to bring it back to life :-(
Any help would be appreciate.
Regards
hey,
i have the same problem. I got a looking new universal, I tried to updaty the system, but my battery is very broken, and it crashed while updating. Now, when I try to get in the bootloader, it's crashing.
I hope you can help me!! And I never worked with a windows phone, and I never tried to flash one, so I don't know sth. about doing this...
ebi
There is no backlight in bootloader mode. Go to bootloader, put the screen under a direct light source and see if it says SERIAL or USB (it will be very faint). If it doesn't, the device is almost certainly bricked. Make sure the battery isn't dead and try this while connected to USB or AC charger.
You could also try the mtty method in the stickied topic and see if the device responds at all. It could be a screen problem (long shot though).
Don't forget to remove SD and SIM cards before trying to flash.
Don't think my device is broken, as I successfully updated the ROM, then played with it, forget it more than 2 weeks on my desk. and then never wake up again.
So when battery is dried down, and the internal backup battery (I think it's a supercapacitor), are fully empty, then there is no way to bring it back to life. As the battery only start charging when at least we passed the bootloader sequence, how could we bring it back to life in that case ?
Just in addition to this, I already tried to replace the battery by an external power supply, taking care of the polarity. But without success.
Please advise.
Regards
me too,i put my device in bootloader but led not light(not light screen)
billounet said:
Don't think my device is broken, as I successfully updated the ROM, then played with it, forget it more than 2 weeks on my desk. and then never wake up again.
So when battery is dried down, and the internal backup battery (I think it's a supercapacitor), are fully empty, then there is no way to bring it back to life. As the battery only start charging when at least we passed the bootloader sequence, how could we bring it back to life in that case ?
Just in addition to this, I already tried to replace the battery by an external power supply, taking care of the polarity. But without success.
Please advise.
Regards
Click to expand...
Click to collapse
You would need a fully charged battery when flashing even if you had it on a charger while flashing, the charger will do nothing while theres a ROM being updated.
atl_luan said:
me too,i put my device in bootloader but led not light(not light screen)
Click to expand...
Click to collapse
There would be no lights when in bootloader mode nor lights on the screen but you will see SERIAL at the top and V2.01 or lower at the bottom but you would need to look closely as there are no lights.
i have a a100 with the latest flexreaper rom installed and im stuck with a pretty serious issue:
a couple of days ago the tab was acting real slow and sluggish and getting bad battery life didnt think nothing of it so i just rebooted a couple times and left it alone . all was good untill the battery hit 10% and i plugged it up using the factory ac adapter. the next day (maybe 6-7 hours later) i went to turn it on and nothing no vibrate no screen flash nothing; other than the power button turning blue as i pressed it and it would stay on for a couple hours but still no other response from the tablet.
im at my wits end on what could be wrong and now i got my wife with her foot on my neck till i get it fixed. can anyone help me?
ive tried to do a hard reset with the reset button tried to boot into recovery /bootloader no dice
(also my home button flashed a couple time i pressed the power button) dont know if its relevant but wanna get as much info out as possible
wondering if anyone can help me...
frenize said:
wondering if anyone can help me...
Click to expand...
Click to collapse
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
pio_masaki said:
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
frenize said:
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
Click to expand...
Click to collapse
Yeah I know that sound it means USB connected but error for some reason. Its been shown if this thing dies all the way down it wont read the battery correctly and probably needs to be sent in. Before that I personally would unplug it open it up and remove the battery for awhile, maybe an hour then put it back and plug it in. But thats me, not the advice I'm giving. If you have warantee on it use that.
The batteries on a lot of devices and laptops etc have something of a fail safe, if the voltage drops below a certain point it trips to prevent cell damage, however it renders the battery useless.
I haven't searched out much past that if a reset is possible by us, but it seems the pack is trash after or needs sent in.
Since this is a sealed unit you void warranty opening it (well unlocking the boot loader did too) so you can't send it in for repairs without paying for it.
I hope someone can jump in and help figure this out, and prove me wrong.
Tapatalked from my Galaxy S II.
Weird, This exact same thing happened to me. Used it in the morning and now after work it won't turn on. I had already tried disconnecting the battery, but hadn't thought to leave it disconnected for an hour. My tablet has been running the leaked ICS since it came out and The last factory reset it had was about a month ago. It was working fine up until this. The power button seems to be responding correctly, the issue is that after the LEDs light up, there is no vibration or display. I hope someone can help us with this issue.
EDIT:
It won't connect in ADB mode. It will only appear on my computer as an APX device and since there is no vibration I am unable to boot into fastboot. Any help or suggestions? All the threads I have found have involved booting into fastboot.
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
same thing here.
max69power said:
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
Click to expand...
Click to collapse
I have been using ICS the leaked one, and last night I was goint to check my email and it did not turn on, I though the battery died. I plugged to the charger and this morning I tried to turning it on but it failed. I did the reset pin but nothing. I connected to the computer and it was recognized as a APX device and installed a driver ACER Picasso USB recover but i cant access anything. I am a nob. Thanks
A100 blackscreen
i am also having this problem. last night. just a black screen it turns on or the home button dose but nothing comes up on the screen. :crying: Help!!!!!!
Has anyone tried holding the power button for a while? Laptops do this too, if someone felt ventures, try taking the battery out and hold the power button. No promises, might work.
sent from my ICONia
same here
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
If the screen is blank while powered on its in failsafe mode, in other words is bricked, has to go to Acer.
Tapatalked from my Galaxy S II.
This just happened to me a few weeks ago as well. If you are still under warranty send it in to Acer, thats what I did. I just got an email saying they had fixed it and were sending it back for free!!
At the time I was on the 9/02 JB build. I wonder if this issue is caused by faulty hardware or if it is an issue that was made by rooting and unlocking it? I don't know enough about this stuff to answer that though, but it does make me think whether I should root/unlock it when I get it back or leave it stock.
Also thanks Pio_masaki for helping me a few weeks back wasn't sure if I was even going to send it in until you said they most likely won't be able to tell.
I highly doubt they even CARE when sending these in. They will void for physical damage most likely.
tshm55 said:
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
Click to expand...
Click to collapse
Ohmygod,
Same here, but it's 3 years ago. Sorry for digging the topic. Still no hope? I still keep the tablet and have just buy another refurbished mainboard to replace but still no vibrate and blacksreen still there.