Well, as the title suggests, I got the original Yu Yureka AO5510 phone yesterday and without even trying anything, apart from installing a few simple apps on it that I regularly use, I discovered that whenever I would make an outgoing call, receive a call, or try calling someone using Viber, or even initiating a Skype video call, the phone would reset itself.
Same thing would happen initiating a code in the dialer to stabilize the proximity sensor... the phone just resets itself immediately every single time.
I was barely able to unlock the bootloader (I think).
After that I tried installing a custom recovery, but it never worked.
In addition to that, I experienced major issues with drivers because I'm on Windows 7 x64.
I was able to somehow get the drivers operational by following an older method, and try installing CWM/TWRP through Fastboot, which seemingly worked from what Fastboot said, but when I actually tried getting into the recovery itself (Vol Up and Power button), the phone just went into normal boot (I also tried Vol down and Power button, and all three at the same time).
The phone arrived with 5.1.1.
I also tried the Yu yureka Tool Box. Followed the procedures to the letter, but again, nothing worked.
I tried manual installations through Fastboot on several occasions, and again nothing worked.
To find that a supposedly new phone cannot actually make phone calls of any kind is absurd... and I find it appalling that I had to go through 10 hours of continuous attempts at making an out of the box phone work - and failing on top of that.
Now, I could potentially live with that if I could get a custom recovery on the thing, but the device refuses to cooperate.
The only potential option available is pressing the Vol UP, Vol down and Power buttons simultaneously...
THAT however, gets me into Cyanogenmod Recovery, which is apparently limited, and I do not think is suitable for installation of new firmware.
Unless someone has an idea I could try implementing in the next 24 to 48 hours, I will be returning the phone and requesting a refund.
I've seen this before, it's a hardware fault. Send it back
Indeed? Most other sources seem to say it's a firmware problem. But given the difficulties I had with trying to put a custom recovery on the thing, I'm starting to think it could be a hardware problem as well. At any rate, a new phone shouldn't be doing that, and no one should go through 10 hours of attempts in trying to make it work in the first place (I can understand if you bought a phone, then bricked it yourself through meddling and then tried bringing it back to life - but not a new phone).
Oh well. Refund it is then. I might go for zenfone 2 instead
did you get it off ebay by any chance? as i know a guy who had the same problem, and sent it back to the ebay seller about 2 weeks ago
Yeah. Got it off e-bay.
No other reliable way of getting it from UK I'm afraid.
Related
Greeting
I ask someone for help. My Samsung E900 has worked perfectly until yesterday ... After changing the Regional Settings sought to be restarted to accept new settings. After that phone at the time of ignition appears LG logo and the fit is a few seconds the screen clears and the LG logo appears again, and so constantly ..
Any ideas?
Thanks
Update - Problem resolved
Hi
I resolved the problem ... means COOLD START is on the keys...
Hold down the VOLUME + - and the CAMERA button and turn the POWER button the phone ...
Phone back to factory settings
Samsung? LOL. And I think this will work even if you don't hold the camera button, but I must try it again...
LG
sorry LG not Samsung LOL
Reset want do the job
Any other ideas?
After a reset i have the same symptoms again.
thx anyway
That's weird!
solved?
did u solve the it?
i have the same problem, it freezes on the "LG" screen, nothing more happens....
i tried the cold boot thingy but then it just sais "cold boot" and then nothing happens...
any one knows if there is something that can be done to make it work?
lamanfluff said:
did u solve the it?
i have the same problem, it freezes on the "LG" screen, nothing more happens....
i tried the cold boot thingy but then it just sais "cold boot" and then nothing happens...
any one knows if there is something that can be done to make it work?
Click to expand...
Click to collapse
Pulling the battery for 10-30 secs and then boot seems to be the universal problem solver for WP7 phones.
/J
my phone was delivered without the battery inserted, it it was out for like a couple of days. Still gets stuck at the "LG" screen...
lamanfluff said:
my phone was delivered without the battery inserted, it it was out for like a couple of days. Still gets stuck at the "LG" screen...
Click to expand...
Click to collapse
Then return it as faulty as it should load unless borked somehow.
/J
Yes i Will return it on monday unless someone knows a way to restore it.
It's possible to start it in 3 modes.
1. Hold down the volume buttons + camera + power button. It then sais cold boot and then nothing more.
2. Vol down + camera + power. Then it sais emergency download, and my computer finds it
3. Camera + power. Shows a phone, cord and computer.
I tried the lg phone support tool and it sais the phone already are up to date.
Isn't there a way to load the windows phone 7 software onto the phone somehow?
Would really like to do it so I won't have to return it. I bought it of eBay, it is a customer return, so guess the guy before me tried messing with it to update it. And the company that sold it to me did not check if it was functioning before selling it to me..
lamanfluff said:
Yes i Will return it on monday unless someone knows a way to restore it.
It's possible to start it in 3 modes.
1. Hold down the volume buttons + camera + power button. It then sais cold boot and then nothing more.
2. Vol down + camera + power. Then it sais emergency download, and my computer finds it
3. Camera + power. Shows a phone, cord and computer.
I tried the lg phone support tool and it sais the phone already are up to date.
Isn't there a way to load the windows phone 7 software onto the phone somehow?
Would really like to do it so I won't have to return it. I bought it of eBay, it is a customer return, so guess the guy before me tried messing with it to update it. And the company that sold it to me did not check if it was functioning before selling it to me..
Click to expand...
Click to collapse
You could of course flash the phone with new firmware and see if it fixes the problem, sounds like someone managed to mess up with your set.
There are some information around here how to flash the phone if you feel up for it.
/J
Ok but do u think The firmware is The problem? The LG tool showed that it was up to date, isn't it just the windows phone 7 software that is missing? I am not sure, but wouldn't the phone not show the lg logo if the firmware was bad?
A reward of € 10 will be given to the person helping me with this, and makes it work as supposed to.
lamanfluff said:
Ok but do u think The firmware is The problem? The LG tool showed that it was up to date, isn't it just the windows phone 7 software that is missing? I am not sure, but wouldn't the phone not show the lg logo if the firmware was bad?
A reward of € 10 will be given to the person helping me with this, and makes it work as supposed to.
Click to expand...
Click to collapse
You could probably try a different version of the OS depending on what you have now (I bet you wrote what version you had, I just missed it).
There are a few threads about that under the WP7 hack and dev. And as far as the firmware goes it's hard to know if it's actually ok just because it loads to the logo, I don't know where in the boot sequence the logo appears etc. there could be problems with the firmware too.
My first step would be to see if it's possible to get a new version of the OS in and if not, I'd try some new firmware.
And if nothing works return it as faulty.
/J
jontatas said:
You could probably try a different version of the OS depending on what you have now (I bet you wrote what version you had, I just missed it).
There are a few threads about that under the WP7 hack and dev. And as far as the firmware goes it's hard to know if it's actually ok just because it loads to the logo, I don't know where in the boot sequence the logo appears etc. there could be problems with the firmware too.
My first step would be to see if it's possible to get a new version of the OS in and if not, I'd try some new firmware.
And if nothing works return it as faulty.
/J
Click to expand...
Click to collapse
I dont know what version there is on my phone, it received it like this, the only thing I see when trying to start it is "LG" and it shows right away.
I tried everything I stumbled upon when it comes to trying to put windows phone software in the phone, but Nothing works... I will send it back tomorrow monday if I cant find a solution to this.
I got the same problem before.
I just turn it off, and leave it for a night
Next day, all the things are ok
yeeaah well, nothing helped, whatever I did to it...
I received no less than 3 broken phones and now finaly I have a working one yaaaayyy
Congrats,
I just sent my phone to LG for the same problem....
My phone can boot up in very low rate...
Lg optimus e900 start issue
Hi,
I have the same issue, I can't restart my phone.
I can see only the logo and the LG caption.
Pls help,
Laszlo
I've got almost the same problem
I just bought this phone via local site, several days ago i'm so much happy with its smoothness but 2 days ago this problem appear, i spent several hours just to find it hanging on LG logo, i've waited for hour to hour just to see nothing happened that time. I left it for bed, and the next day the phone back to normal. But then, at least the device hanging 3 times a day, its just restarting itself and it seems the phone is unable to boot itself to the homescreen. Need help! I've done many way, from restoring, cold boot, softreset, upgrade(when it comes normal) etc but all don't work till now.
Unfortunately, this product doesn't release officially in my country, so i guess i won't be able to get replacement unit. I became so desperate cause i often use it, i need to get this phone back to normal, soon! Thankyou and sorry for my bad english
I have an unlocked AT&T Samsung Focus which I just got two weeks ago. And for some weird reason, the phone got bricked. It wasn't because of any update or anything.
What happened was I was just checking an app which I downloaded from the Marketplace, which got stuck (none of the buttons on the device were responding after several minutes). So I had to pull out the battery to restart the phone.
It now gets stuck in what appears to be an endless boot cycle. All I see is the Samsung logo which disappears after a while and then reappears. The phone doesn't seem to go beyond that.
I tried hard reseting the phone (Power + Volume DOWN + Camera), and even after formatting it several times, the problem is still the same.
I also read somewhere that if you leave the phone in Download Mode (Power + Volume UP + Camera) for a few minutes, it somehow *magically* restores itself. This didn't work for me either even after leaving it in the download mode for about an hour.
Now asking the excellent community of XDA for help is the last thing I can do because since I'm not in the USA, I can't even get a warranty claim on my Focus, and its nothing more than a paperweight right now.
So any ideas/tips/suggestions on what I should do?
Return it !
That's something I just can't do. Got it through a 3rd party in the US so I can't just return it. I'm not in the US, and I doubt that 3rd party company would have kept any records.
What I'm wondering is if the issue is in the hardware or the firmware. If it is the later, then is it possible to flash the ROM and see if it works?
Make a full hard Reset on it. If that not work. Your OS is screwed. You buy the phone unlocked so it have no warranty. If the hard reset don't work start praying to the hackers gods to start working on a ROM for all the Bricked Focus out of warranty out there.
I'm actually surprised there isn't any ROM/Hacking activity on the Samsung Focus yet. Its actually one of the top selling WP7 devices.
What I'm actually interested in knowing is that if it really is an OS/Firmware issue or a faulty NAND Flash which is causing the problems.
If its a NAND, then even a ROM wont be able to help. Any way to confirm this?
You could try to make a "jig" and force it into download-mode and flash a ROM, like I describe here. But I don't know if there is a ROM available.
I can get it into download mode. That's not the issue. The problem is the ROM. There aren't any available for Samsung Focus.
I've dealt with a few bricked phones in the past that have been a simple fix through ADB/Recovery, but this one really perplexes me.
So I get work, place my phone on the desk, and a few minuets into the day I see it re-boot out of the corner of my eye. It's not something to be expected but this has happened a few time over the 5 months I've had this phone so I think nothing of it.
But 5 minuets later its still looping on the Google logo. So hold down the sleep button to shut it down, still loops. The only thing I have done to this phone is unlock the bootloader through the command prompt and install a stock Nougat image straight from Google
Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android.
I have Googles Android USB Driver installed, Windows 10 chimes when I plug it in, It appears in Device Manager as "Android Bootloader Interface" but I have not been able to get it to show in the terminal with ADB. I have also tried on a Windows 7 and OSX Laptop.
I am completely dumbfounded, any help/ideas would be amazing!
Thank you
BrickOfNexus said:
I've dealt with a few bricked phones in the past that have been a simple fix through ADB/Recovery, but this one really perplexes me.
So I get work, place my phone on the desk, and a few minuets into the day I see it re-boot out of the corner of my eye. It's not something to be expected but this has happened a few time over the 5 months I've had this phone so I think nothing of it.
But 5 minuets later its still looping on the Google logo. So hold down the sleep button to shut it down, still loops. The only thing I have done to this phone is unlock the bootloader through the command prompt and install a stock Nougat image straight from Google
Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android.
I have Googles Android USB Driver installed, Windows 10 chimes when I plug it in, It appears in Device Manager as "Android Bootloader Interface" but I have not been able to get it to show in the terminal with ADB. I have also tried on a Windows 7 and OSX Laptop.
I am completely dumbfounded, any help/ideas would be amazing!
Thank you
Click to expand...
Click to collapse
Hi... There is no available fix for the moment. Check this thread. You are not alone
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page19
BrickOfNexus said:
... Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android....
Click to expand...
Click to collapse
Unfortunately @5.1 is right. The common denominator of the BLOD (many threads on this) is the inability to get into recovery mode by any means. ADB doesn't work unless in recovery. Without ADB you will not be able to pull anything off the phone. At least you are unlocked so you can try some tools and/or manually attempt to fastboot boot or fastboot flash a custom recovery and get ADB working, but chances are almost non-existent. Some ppl have been able to briefly get back into recovery on completely full charge, but it seems to start boot looping again shortly afterwards from recovery. Hopefully you were using Photos and synced recently. If you bought direct from Google, contact them even if out of warranty. If they won't help you or you didn't buy from Google, approach Huawei for an RMA.
I was in your situation and was able to flash the full stock image (flash-all.bat command) even though my device didn't show up on ABD--but maybe I just got lucky. I thought there was no chance it would work but it did. Some people reported getting out of the boot loop using Skipsoft's tool but most likely you will need to RMA the device if it's still under warranty from Huawei. Sorry to hear you have been added to this club. There are a lot of lemon 6Ps that die because of hardware issues (according to Google) and they clearly don't care because they never recalled the affected devices. I was hoping it was just the early generation phones but if yours is 5 months old that means the problem is persisting. None of these things might still be running in a couple years which is ridiculous for a premium phone. Makes you think twice about buying another phone from Google since they threw 6p owners under the bus rather than offering 6P owners a credit or something for their defective 6Ps. Good luck. At this point I think people need to create a class action suit against Google. That's the only way people got repairs or compensation from Apple the numerous times they pulled stuff like this with defective products. Why should Google get away with selling what they themselves admit is a defective phone?
Hi all,
Hopefully this wasnt covered before- I used the search function and it didnt return any results, at least not for my specific scenario.
I've had this 6p for about 18-20 months roughly. Been my best phone by far, and I've been very happy with it(normally i replace my phones every 8-12 mos because I need the latest and greatest lol).
About six months ago I threw PureNexus on there with I believe Flash kernel. Worked flawlessly, and I've been really happy with it.
About a week ago, it powered off on its own but i had it in my back pocket so I just assumed it was an accidental reboot. However, this morning, I woke up, threw it on the charger for about 30 minutes, got to about 60%, and unplugged it. While I was using the browser, it froze up for a minute then shut down. No bueno. Cannot get it to power back on. No power light while charging. I did what others have had luck with, holding power, and/or power/down for several minutes, still nothing.
I reached out to Project Fi, and they want a 500 dollar hold to send me out a refurb replacement. I know they release the funds in approximately 12 days but we had a recent death in the family and I just cannot afford to have 500 bucks locked up, especially right now. Spoke w a supervisor, apologized, but said nothing they can do.
On a whim, I plugged it into the pc, and it DOES detect it but its the dreaded QHSUSB_BULK under 'other devices'. So that tells me its at least got power, but, I'm unsure if just trying to use adb(i havent in a while, not since i did the initial rom install but im sure i can find instructions) to attempt to throw the base image back on there, will work, or which direction to go.
I found this but I dont think its for my specific phone but thought maybe there was a set of instructions for this particular phone similar to these:
https://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I have seen several reports of this error happening when flashing the wrong rom, or using the wrong image, but never just all of a sudden when its been running like a champ.
any thoughts? thanks in advance.
Nexus 6p is plagued with issues like shutting down at certain percentages and the dreaded bootloop of death. You could get in contact with Google heard even people out of warranty having success. Could also have a shop replace the battery in some cases that fixed the shutdowns.
If it doesnt boot up at all I can't help you. If you can get to bootloader, flash stock image, un-root, re-lock your phone. see if it boots. I had to do all this, this morning. Phone would just shut off at 80%, reset and hang at the google sign. I could only get to into the main system with a hard reset every time. then it would reset and lock up. So i reverted it to stock and we will see how it goes. So far its been 6 hrs and no random resets and its in full use.
Yea, the problem is, I cant. Its not even a boot loop. Just looks like its dead. Held the power button down for roughly 10 minutes out of desperation.
The odd thing is, if i plug it into my pc it shows how i mentioned in my initial post. So it must have juice even though the power light/etc isnt on and it doesnt show charging.
Last hope I think i have is to run it out of battery leaving it on the table, then hope somehow when i plug it into charge, that resets it somehow since it was dead, and maybe clears whatever the issue is. Very odd considering it was working fine until this.
Your phone is stuck in the EDL mode when its detected as QHSUSB__BULK. There are solution for this but i dont know if this solution is combined with data loss or not and i try to find that out recently. I also still dont know how to fix that with linux.
Here two howtos:
https://forum.xda-developers.com/nexus-6p/general/guide-how-to-bring-to-life-dead-nexus-t3581948
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Hello developers and my fellow xda members i would like to ask for your help on this matter my yureka plus has been hard bricked since 20 days now and no matter what i try it wont get unbricked.
how did it happen??
well even i dont know actually i had recently flashed an 8.1.0 oreo rom known as nitrogen os and it ran well for like a week till one fateful thursday i have a habit of cleaning my device with clean master and restarting it every week and i did that and the next thing i know my device wont boot up later on i found out for the very first time my device had hardbriccked with no mistake of mine.
link to the rom i used :: https://forum.xda-developers.com/yureka/development/rom-nitrogenos-t3701962
what solutions did you try??
well, many actually since this is the only device i have and i have been using it for a well over 2 years now i did the good ol google search accompanied by a youtube search to find out how to get my beloved device back.
these r all the methods that i used which ended up "successful" but my device refuses to boot up even though i have followed every one of these tutorials to revive my device perfectly even repeating the process 2-3 times thinking i did something wrong but to no avail the device still refuses to get unbricked.
links to the methods i tried :: https://forum.xda-developers.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112 (claims to have unbricked his device 3 times didnt work for me though)
https://www.youtube.com/watch?v=1n1qTpVvOZ0 (claims to have helped 10 other people get thier device back with this same method again didnt work for me)
what r the devices symptoms ??
well, let me see there r many although i have scoured the internet for the past couple of weeks i havent found a single person with the same symptoms as mine.
when the sd card (on which the emmc is still burned on) is out of the device no matter how long you press the power button the device will not show any signs just nothing.
when put on charging or connected to the laptop (without the sd card) though it just shows that dreaded little red notification light and thats all.
with the sd card in and emmc burned onto it the device when holding the power button will just flash the screen with nothing but just a black screen no text no logo just a plain black flashing screen until i let go of the power button.
when plugged in to a laptop or a charger with the emmc in though the device vibrates goes into the "fastboot mode" with all the lines automatically without me doing nothing just plugging it in and it doesnt stop there it keeps repeating the cycle of vibrating going into the fastboot mode then going off till i take the cable off.
but the laptop doesnt detect it as anything not as "qhusb bulk" not as "qloader 9008" not even as an unknown device even though i have installed all the drivers neccessary and more.
the device has been in this state since well over 20 days now and i cannot for the life of me am able to revive it so i ask for everyones help for i will b forever grateful if u help me get this device back.
also, i refuse to believe its any hardware problem since the device has never fell off from my hand ever since i bought it over 2 years ago.
I was having a similar problem what is ur model name was it android one or cyanogen one.
If it was android one then flash this file with ydgp tool
If it doesn't start then to try to boot using charger connected
If the booting process starts or it show yu logo after yureka plus logo that means it's your battery problem