Related
First I had nothing but boot loops for an hour, then by some miracle, ICS finished installing. However, now i keep getting "refresh failed", and the tablet will lock up and restart itself. Should I drain the battery and let it die? What should I do to try and fix this?
mine is locking up and restarting too but only once every 30 minutes on average.... lol this is lovely.
This is driving me insane. My prime was perfect before this update. Right now it won't even boot, just bout boot loops. Already tried factory wipe too.
Sent from my Galaxy Nexus using Tapatalk
did you update via the OTA file some posted or did you download the update from asus directly through the tablet?
Directly through the tab, and I had a serial number too.
Sent from my Galaxy Nexus using Tapatalk
Getting the same thing.
Well someone from Asus development just sent me a pm asking for my serial number so they can look into it. I didn't contract them first. Hopefully something can be done. I love this tablet, but I have no use for a $500 paper weight
Sent from my Galaxy Nexus using Tapatalk
for now
just to help,
what you could do for now is downgrade by following the first part of this thread:
http://forum.xda-developers.com/showthread.php?t=1426280
I hope this will at least get it back to a working state.
let us know what happens
Hello there,
As my Prime doesnt receive OTAs I waited for the official Asus zip. I restored my original build.prop, deleted the modified one and did a factory reset (I didnt remember the wipe option). Then I just updated to JB, but when it reboots to start JB for the first time, it gets stuck on the new Asus screen. I cant get past it and I cant even shutdown the tablet, it powers on by its own.
My tablet wasnt unlocked (I cant unlock too) and I cant even go into recovery. I tried with the reset pin to no avail; I tried the following:
Pushing Power + Vol Down: It restarts, vibrates and gets stuck on the same screen
Pushing Power + Vol Up: It restart, vibrates and screen off
Pushing reset pin + any of the previous: same effects.
Now I am starting to fear I have in my hands a 600$ paperweight (imported from USA, dock included). Anything I can try to make it boot?
Thank you all!
Can you try this. Hold just volume down and keep holding it. Then push reset hole. Keep holding the volume down for another 3-4 seconds. Tell me what you see after.
aznmode said:
Can you try this. Hold just volume down and keep holding it. Then push reset hole. Keep holding the volume down for another 3-4 seconds. Tell me what you see after.
Click to expand...
Click to collapse
I just get the same ASUS screen -_-
I'm sorry, I dont know how else you can do it without fastboot access.
Sent from my Transformer Prime TF201 using Tapatalk 2
Same thing happened to me today. Update to JB, played around with it, ran the unlock tool, and it never booted again. :/
I sent a message to Gary Keys in hopes that we can find a fix.
Would you be up for doing the same, anything to try and get a response!
It sucks to have a $500 paperweight that I didn't even get to play around with. :/
i'm interested to resolve same issue.
thanks
kwineon said:
Same thing happened to me today. Update to JB, played around with it, ran the unlock tool, and it never booted again. :/
Click to expand...
Click to collapse
I'm the same boat except I never made it past the ASUS logo. Not unlocked, not rooted. I'm also one of the victims of the no serial number problem (no OTAs). I wonder if it's related.
Same problem here. Trying to open an RMA as I have never been able to unlock either.
Same issue here for me http://forum.xda-developers.com/showthread.php?t=1918102
kwineon said:
Same thing happened to me today. Update to JB, played around with it, ran the unlock tool, and it never booted again. :/
Click to expand...
Click to collapse
The Unlock Tool on Asus' Site, v6 dated Feb 22, 2012, states three times in the description that it's only for Ice Cream Sandwich (ICS). I haven't heard that it works for JB. This might be the cause of the brick.
Sent from my VS910 4G using Tapatalk 2
Well, se ser a lot. Also Serial not found problem, tried to unlock many times but couldnt un the day. I will try to get an RMA but I think they will make me pay. If not, time for a Nexus 7 (ASUS again, dammit!)?
Bait-Fish said:
The Unlock Tool on Asus' Site, v6 dated Feb 22, 2012, states three times in the description that it's only for Ice Cream Sandwich (ICS). I haven't heard that it works for JB. This might be the cause of the brick.
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
I didn't realize this. :/ Sucks to be me I guess. You would figure they would update the tool if required when releasing new OTAs. :/
Any way to reload the boot loader without having created the NVFlash files?
Sent from my SCH-I500 using Tapatalk 2
crimsomshadow said:
Well, se ser a lot. Also Serial not found problem, tried to unlock many times but couldnt un the day. I will try to get an RMA but I think they will make me pay. If not, time for a Nexus 7 (ASUS again, dammit!)?
Click to expand...
Click to collapse
Same problem (stuck in ASUS Logo), not rooted or unlocked. I did have the serial number issue that I never care about because it just meant I had to manually update. But It seems that this serial issue is what have caused this brick for some of us.
There are a lot of primes bricked by the update to Jelly Bean. And it appears to be a hard brick. I am waiting for them to respond my support request. Probably an RMA is the only solution.
Hi guys,
I recently bought my Moto 360 2nd gen. After 4 weeks, it started to fail pushing messages through. In the beginning, unreliable, now, nothing except for. My step count....
I restart my watch everyday, disconnect and connect with my phone, factory restarted it several times. Only for 15 min, it tends to work, than, the same described above.
Now, I found out, when I wake up my phone it push messages through, and music toggles are working. Messages which are received by my phone before I picked it up will not be pushed through though.
Does anyone can help me with this issue, before I go to ask my money back from Motorola, because I start to get frustrated!
I bought it to leave my phone in my pocket, now, I have it in my hands even more:crying:
Delete
Samsung galaxy s5
Delete
I changed it, I'll let you know if it worked!
Do you have other possible solutions?
Thanks. Very much!!
Hey rocketSauce83, I've been using it for a couple of days now. I can confidently say that it is up and running how it supposed to be! Super smooth! Thanks a lot for your help and a happy new year!
same problem
RocketSauce83 said:
Delete
Click to expand...
Click to collapse
hey.. i have the same problem with my moto 360 2015. i dont have any idea what you mean by delete. i have tried everything except phone reset. i tried pairing my watch with my old tablet and everything is working fine. i think it started after the latest security patch on my phone. BTW my phone is note 4 still on lollipop(no marshmallow yet) and not rooted. i need help solving, thanks in advance
update:
I have just found the cause of the problem. It was the new app optimization feature that samsung installed on my device after the latest update. i just disabled the optimization on my AW app.
I never thought I would be coming here for this issue. This incident is no less than surprise to me.
I tried everything to save my phone from getting hard brick like I downgraded very carefully, became choosy about kernels and custom roms I was flashing but yesterday my phone hard bricked itself magically, yes I am not a freak to make that statement but my moto e which was running fine till date got hard bricked on it's own.
I used it normally, everything was normal but yesterday night when I unlocked my phone to see time and then locked it and then unlocked it after a second to set alarm and guess what, the screen didn't turn on. I waited for a minute but no luck, then I pressed power button for 10-12 seconds expecting a restart but it didn't show up, it gave no response (also the battery was 71% I checked few minutes before) I was out of my mind and then after few minutes I decided to connect my phone to pc and the moment I connected it showed up "qhsusb_bulk" drivers installation, OMG! What the hell did just happen, I lost all of my valuable data in phone memory and also lost my phone in an instant... that too forever ?? :crying:
I spend lots of hours today trying every possible step which could bring my moto e to life but no luck again, I am still wondering what went wrong. Did this happen to anyone out there?
Can any expert on xda answer me what could have went wrong ?? and is there any solution hidden out there?
I don't think even if the Motorola company can itself answer the question.
Little bit more:
I had no internet, no wifi, bt turned on.
Running Stock 4.4.4
Just rooted and used GravityBox (it was running very smoothly till date)
Installed Es File Explorer only, nothing else.
How can it be?
I am really shocked and feeling very low, I can't see my moto e dead anymore.
PS: I found no thread of moto e magically getting hard bricked so mods plz, mercy.
Bootloader is the key.
Even if fastboot mode isn't turning on then there's no hope.
This is very unusual though.
Did you downgraded from 5.1 to 4.4.4?
No I didn't do anything but today did postmortem
-z3r0- said:
Bootloader is the key.
Even if fastboot mode isn't turning on then there's no hope.
This is very unusual though.
Did you downgraded from 5.1 to 4.4.4?
Click to expand...
Click to collapse
I did not downgrade or install some app, tweak,kernel or anything, I was on 4.4.4 since 3 months.
And I agree with you, the bootloader has corrupted itself (weird like hell) and screen won't show anything (no fastboot or anything)
Also today morning I disassembled the dead moto e to look if I could find anything but no luck, every component is working like battery, lcd, speaker and everything, except ya bootloader. So postmortem reports say that it was a suicide, the phone killed itself. The soul (bootloader) has left the body of moto e. Yes that sounds funny but that's what it is. I felt very bad for a day but now accepted the fact that some events occur without leaving a trace of cause. Moto E was the only phone I had after selling all the phones I had. Will buy new after few months but I am sure my next phone won't be from Motorola. I will remember this event.
Thread is still open to question asked in post 1 and also I ask what should I do with that dead moto e can I make few bucks out of it so that I can buy new phone soon.
Thank you everyone who came this far.
This issue had been reported on Motorola's forums a few times. Motorola's reply was "It's against forum rules to talk about unlocked phones/modding the phone."
No help from Motorola, the device wasn't meant to last more than a year or two.
Afaik the international variants of the Moto e don't have the power button issue, battery issues, or the sudden death issue.
Sent from my XT1022 using Tapatalk
DNALogic said:
I did not downgrade or install some app, tweak,kernel or anything, I was on 4.4.4 since 3 months.
And I agree with you, the bootloader has corrupted itself (weird like hell) and screen won't show anything (no fastboot or anything)
Also today morning I disassembled the dead moto e to look if I could find anything but no luck, every component is working like battery, lcd, speaker and everything, except ya bootloader. So postmortem reports say that it was a suicide, the phone killed itself. The soul (bootloader) has left the body of moto e. Yes that sounds funny but that's what it is. I felt very bad for a day but now accepted the fact that some events occur without leaving a trace of cause. Moto E was the only phone I had after selling all the phones I had. Will buy new after few months but I am sure my next phone won't be from Motorola. I will remember this event.
Thread is still open to question asked in post 1 and also I ask what should I do with that dead moto e can I make few bucks out of it so that I can buy new phone soon.
Thank you everyone who came this far.
Click to expand...
Click to collapse
Sorry to hear about the incident, but blaming motorola ain't gonna fix it. Motorola won't care if one of its phones is dead, it has a hell lot of customers buying their phones everyday. And also, motorola is right. They guarantee no life of the device after we unlock it. Still best of luck buying your next phone...:good:
Regards,
PoseidonKing
Ahish.s said:
This issue had been reported on Motorola's forums a few times. Motorola's reply was "It's against forum rules to talk about unlocked phones/modding the phone."
No help from Motorola, the device wasn't meant to last more than a year or two.
Afaik the international variants of the Moto e don't have the power button issue, battery issues, or the sudden death issue.
Sent from my XT1022 using Tapatalk
Click to expand...
Click to collapse
PoseidonKing said:
Sorry to hear about the incident, but blaming motorola ain't gonna fix it. Motorola won't care if one of its phones is dead, it has a hell lot of customers buying their phones everyday. And also, motorola is right. They guarantee no life of the device after we unlock it. Still best of luck buying your next phone...:good:
Regards,
PoseidonKing
Click to expand...
Click to collapse
Thanks for reply, And after research I have found thousands of dead moto e owners and still no support from Motorola anyways
If Motorola won't care I won't freaking care either, I am thinking of getting Xiaomi Redmi Note 3 (Snapdragon Variant) soon.
You know I use to suggest people to get Motorola and was so damn moto fan that would convince every person I met to get motorola next time but no more motoism. Goodbye Motorola.
P.S. Thread still open for people who could figure out how could I get the suicide note written by my moto e (to find cause of death/hard brick) or if you have an idea of what could have went wrong.
P.P.S. Sorry if posts are more personal and artistic and feelings are overflowing but that's the way I am .
DNALogic said:
Thanks for reply, And after research I have found thousands of dead moto e owners and still no support from Motorola anyways
If Motorola won't care I won't freaking care either, I am thinking of getting Xiaomi Redmi Note 3 (Snapdragon Variant) soon.
You know I use to suggest people to get Motorola and was so damn moto fan that would convince every person I met to get motorola next time but no more motoism. Goodbye Motorola.
P.S. Thread still open for people who could figure out how could I get the suicide note written by my moto e (to find cause of death/hard brick) or if you have an idea of what could have went wrong.
P.P.S. Sorry if posts are more personal and artistic and feelings are overflowing but that's the way I am .
Click to expand...
Click to collapse
I also used to do the same....Motofan... Moto this and moto that, but no more... I am also looking forward to buying note 3.... Which one r u buying?
32GB 3GB RAM or 16GB 2GB RAM? If it's 32GB then send me a link in a pm..
Regards,
PoseidonKing.
Kindly go through this thread http://forum.xda-developers.com/moto-e/help/blank-flash-plzzz-t3153660/post66122497#post66122497
I am also gearing up to do it. Need a donor with 5.1 to backup and upload the image
Yea, something similar just happened to my phone and it's driving me nuts. About a week ago i flashed stock 5.1 and it was working fine so far, (except for the camera that was constantly crashing for no reason when I opened it, but that didn't really bother me that much) but suddenly stopped responding when i tried unlocking it. I can't access the bootloader either...
The only response i got was from the little white led when i tried pressing the power button for a bit longer and when i unplugged it from my PC.
The only apps I had installed were the Facebook messenger, Whatsapp and Instagram. Is there any hope to save it? ;-;
That sounds like hard bricked moto e
Kaio Oliveira said:
Yea, something similar just happened to my phone and it's driving me nuts. About a week ago i flashed stock 5.1 and it was working fine so far, (except for the camera that was constantly crashing for no reason when I opened it, but that didn't really bother me that much) but suddenly stopped responding when i tried unlocking it. I can't access the bootloader either...
The only response i got was from the little white led when i tried pressing the power button for a bit longer and when i unplugged it from my PC.
The only apps I had installed were the Facebook messenger, Whatsapp and Instagram. Is there any hope to save it? ;-;
Click to expand...
Click to collapse
Sorry Bro, but by what you said I really feel like your moto e has been hard bricked. No fastboot and white LED blink when plugged into charger is pure sign of hard bricked moto e, then too you can connect to pc and if it's device manager detects it as QH-USBBULK and installs drivers then it's hard bricked for sure and no hope till now. I have been able to get just one guy who claims to bring his hard bricked moto e to life after following some tutorial. You should check this link right now. After reading 2-3 pages you can too try to get your moto e to life. Do reply there or here when you successfully unbrick it. All the best. :fingers-crossed::good:
Mine died suddenly today during a reboot, apparently there's no trace of an unlocked bootloader when it's bricked like ours, I'm gonna send it in as I'm still a few months in warranty. Has anyone got any experience regarding this?
Benzy1 said:
Mine died suddenly today during a reboot, apparently there's no trace of an unlocked bootloader when it's bricked like ours, I'm gonna send it in as I'm still a few months in warranty. Has anyone got any experience regarding this?
Click to expand...
Click to collapse
Please let us know what the service center did for this issue.
Sent from my Moto E using Tapatalk
DNALogic said:
I never thought I would be coming here for this issue. This incident is no less than surprise to me.
I tried everything to save my phone from getting hard brick like I downgraded very carefully, became choosy about kernels and custom roms I was flashing but yesterday my phone hard bricked itself magically, yes I am not a freak to make that statement but my moto e which was running fine till date got hard bricked on it's own.
I used it normally, everything was normal but yesterday night when I unlocked my phone to see time and then locked it and then unlocked it after a second to set alarm and guess what, the screen didn't turn on. I waited for a minute but no luck, then I pressed power button for 10-12 seconds expecting a restart but it didn't show up, it gave no response (also the battery was 71% I checked few minutes before) I was out of my mind and then after few minutes I decided to connect my phone to pc and the moment I connected it showed up "qhsusb_bulk" drivers installation, OMG! What the hell did just happen, I lost all of my valuable data in phone memory and also lost my phone in an instant... that too forever ?? :crying:
I spend lots of hours today trying every possible step which could bring my moto e to life but no luck again, I am still wondering what went wrong. Did this happen to anyone out there?
Can any expert on xda answer me what could have went wrong ?? and is there any solution hidden out there?
I don't think even if the Motorola company can itself answer the question.
Little bit more:
I had no internet, no wifi, bt turned on.
Running Stock 4.4.4
Just rooted and used GravityBox (it was running very smoothly till date)
Installed Es File Explorer only, nothing else.
How can it be?
I am really shocked and feeling very low, I can't see my moto e dead anymore.
PS: I found no thread of moto e magically getting hard bricked so mods plz, mercy.
Click to expand...
Click to collapse
same happened with me I was running cm14.1 with BlackMWhite logo (downloaded from here:-http://forum.xda-developers.com/moto-e/themes-apps/boot-logos-motorola-boot-logos-moto-e-t3216857)working fine from 2-3 days even rebooted several times but yesterday when I wake up it was dead (looks like hard bricked as it's not even charging) when I connect it to PC it installed some drivers and in device manager shows "RELINK HS-QDloader 9008 (COM 3)" have you tried http://www.droidsavvy.com/unbrick-qualcomm-mobiles/ ??? :crying:
My moto e is also not turning on.I think mine also got hard bricked.
Incident: I was opening shareit to share something but when I clicked on SEND my moto got switched off.This had happened with me some days before also but it was fixed by just connecting the charger but idk how it got fixed. But this time I tried everything but all is worthless.
Can anyone help me and others regarding this issue. :crying::crying:
Has anyone of you guys tried QFIL ?
What is this QFIL???
Kaymas said:
What is this QFIL???
Click to expand...
Click to collapse
Qualcomm Flash Image Loader
I have seen a mechanic un-bricking Chinese smartphones. He dis-assembles the phone, removes the battery. After couples of minutes connects the battery back. Then 'Qualcomm HS-USB Diagnostics' in PC is able to recognize the Phone.
Last night the phone randomly restarted out of nowhere mid-text message with my friend. It kept restarting in a loop then I pulled the battery and tried it again and I did get the phone going enough to send one text then it crashed again. Now it wont start at all. It's stuck on the bootloader unlocked screen. Help?
I'm running twrp and android 5 from siraltus
Same has happened on 17 of my company v10s.
Should be a recall on these phones. LG knows there is a problem.
You got the curse, I did too, if there's no Phys. damage and you are qualified, you can request an overnight wnty replacement... I just got my second V10, hopefully it wont die on me too until T-Mo gets a decent device for me to jump to...
Same happened to mine..
Did anyone notice seemingly random vibrations before the phone died like that? I keep thinking mine is vibrating for no reason every now and then. Maybe mine will be next to go lol.
Sent from my LG-H901 using XDA-Developers mobile app
It did happen, I got the self-brick last night!!
Apache0c said:
Last night the phone randomly restarted out of nowhere mid-text message with my friend. It kept restarting in a loop then I pulled the battery and tried it again and I did get the phone going enough to send one text then it crashed again. Now it wont start at all. It's stuck on the bootloader unlocked screen. Help?
I'm running twrp and android 5 from siraltus
Click to expand...
Click to collapse
Did you just take an update for Superuser? I noticed that when updates for superuser comes out alot of phones get bricked. My lg g4 just did it also so got to use unbrick procedure.
---------- Post added at 02:25 AM ---------- Previous post was at 02:20 AM ----------
Here is the link for the lg g4 procedure which helped me out.
http://forum.xda-developers.com/tmobile-g4/help/cyanogenmod-13-longer-boots-stock-t3468427
Mine bricked yesterday 2 weeks out of warranty. 99 dollars for a replacement and about 2 weeks without the phone through square trade. Last LG phone for me. Clearly they know there is a problem. Unfortunately I"m still stuck in my Jump on demand contract with this thing and don't want to jump right now. Maybe to the S8. Mine was vibrating randomly too sometimes although I don't know if that had anything to do with it. Completely stock phone. First phone I haven't rooted in years.