Got a tablet from irulu for my birthday. Turns out it was refurbished. I tried to wipe the damn thing, it got stuck on 61% for hours. I force quit it. Then, almost instantly realized that it had deleted it's OS. I booted into recovery, to check and make sure before I did more damage. I was correct in my assumption. No OS for any language. Still boots to recovery. If I let it just go, it turns on, you could see the backlight, and theres like a cursor of some sort. I don't want to have to send it back, and the person who gave it to me is no longer with us (out of country, not dead, probably.). Please help, I don't know what to do, this is my first ever windows device.
Related
Hey guys,
I've done some searching on this issue, yet I can't find much besides battery problems, or people who have contacted T Mobile and got warranty replacements. I've had some issues with my G1. Over the past month or two, my G1 has been rebooting repetitively, and this week it's gotten BAD. I would open a SMS, and then BAM. Start dialer, and then BAM. Reboot. Hell, even in the middle of a reboot it would reboot. Cool huh?
Anyways I called T-mobile customer support and they said I'm out of warranty. Great. Well, it still turns on, and it still operates when it's happy, so maybe I can work with this for a little bit... I did some searching, and some people attributed it to a software glitch in the gyroscope... Most people called T-mobile and got a warranty replacement. I'm over the one-year
I'm not about to say this is because I had CyanogenMod on it, because I would wipe, and put it back to an older version and it would still reboot... even in the SPL, it would reboot. But regardless, I decided to follow this how-to to unroot my G1: http://forum.xda-developers.com/showthread.php?t=491350
After step 6 (6. Push Alt+S on your G1 to flash it with update.zip), it came up with an error about the splash... "Cant store hboot image."
Well anyways, before I could do anything about it, guess what happened?
Yeah, it rebooted.
It came up with the unboxing logo at first, I didn't know what to do. I had forgotten what this meant, so I heled the power button down ( I realize this may have been the misteak I made, however there was nothing visual indicating anything was being done).
It shut down, the screen went blank, the charge LED remained on....
I pressed power.... Nothing.
I unplugged the phone, took out the battery.... put the battery back in... Nothing. The screen stayed black. Now my phone will not power up, and there is no LED charging indicator.
Anyways, I'm lost. This is my second G1. I'm slightly pissed and I feel bad for the T-Mobile rep on the other end of the call I just had, but, really, I can't spend $1200 a year on a slow phone.
Do any of you guys have any suggestions?
Home+power does nothing.
Camera+power does nothing.
Putting in the cable lights up no LEDs...
It is literally a brick. An unresponsive brick.
Well, I ended up taking the mainboard out of my old phone and putting it in this G1.... Everything should be back to normal however I'm still looking for responses as to what might be happening.
WARNING: This might be redundantly long. But at least it's clear. I believe it to be a matter of wp7 and android. So it'd be inappropriate to paste it in either one of those. Enjoy reading!
I've scrolled around the forums for a possible answer, but I couldn't find any threads with exactly my problem. I'll organize the situation:
Problem: HD2 Won't turn on.
(That's about as helpful as saying 'I put gas in my car, put a key in it, and it won't turn on. Help?' right?)
What happened: I was following the thread http://forum.xda-developers.com/showthread.php?p=11097380 (Not slandering them, just using it as a reference to help the trouble shooting of what's going on.) And I followed it as it went. I tried flashing the radio leo rom 2.15.50.14. And it completed. But then my phone turned off, and hasn't come back on yet. It makes the "ba-dum" noise when I plug it into my PC though. Although, there is no faint vibration like I've read with other's problems.
Background info: I've stumbled through about 3 or 4 flashings of wp7 roms and such. As I've broken them all. This one managed to survive since July. And I wanted to try an android os, it's been a while since I've touched any android phones. Anyways, I had wp7 and all the appropriate downloadings/flashings onto it. I thought maybe I should start over, and just follow the guide's steps. Although! There's the problem that I can't use .xaps to my phone. I can sync with my zune library, but I can't xap anything to it. Essentially I'm saying it works, but it doesn't.
And finally, the reason why I did this: The screen progressively became unresponsive. It started as what seemed as if I had oil on my fingers, and it fixed itself within a few seconds. As the days went on, it became minutes, then it finally stopped working. I'd go on to take out the battery, then have to restart it. Also, like a past hd2 of mine, it's moved onto restarting itself at random times. Sometimes one boot up after the next, or just randomly. It was perfectly fine. Perfect.
P.S. Sorry for the length, I wanted to be completely clear to prevent questions like, "Need more info. What's exactly wrong?".
Thanks for anyone helping me! I really do appreciate it. I don't want to have to get ANOTHER one.
P.S.S I'm really terrified of it being bricked. Although, it didn't work at the moment anyways. But I was hoping to attempt to fix it. OH, and I called t-mobile about the screen being unresponsive. (Don't worry, they don't know what I've flashed to it ) They told me to hard reset it with vol up/down + red button. I tried that. The screen worked again. For a short while. And every now, and a thousand random reboots, the screen will proceed to work. But it doesn't show a history of texts during the duration it works. And it usually freezes, then boots down. Boots up, and stops working.
sorry to be the bearer but it sounds as though you're yet another victim of the digitizer hardware issue. its one of those things that simply cant be helped and seemingly comes out of nowhere!
you might, however, go back to basics. start by flashing a stock winmo 6.x rom. if that cures your screen troubles you will have a fresh base to start over (and more carefully) ... if it doesnt fix screen troubles and it stays unresponsive you will have it already ready to be shipped off to be replaced ( this way tmo or wherever you're sending it to wont be able to say YOU caused the screen issue)
in any case i wish you luck!
Hi everybody,
I didn't want to bother you with my problem, but considering that also in B&N forum they told me to try here well, you're my last hope! :fingers-crossed:
Now it's a week that my Nook Simple Touch is stuck on the "Your NOOK is starting up..." screen.
When it froze, the battery was at least 70% full, anyway I let it charge overnight, leds on, but nothing changed.
I tried every kind of recovery I could find browsing the internet (failing the boot 8 times, 20+2 sec, boot and press the L/R lower buttons) but nothing changed, just the screen flashing for 1sec while "booting" and then the starting screen again.
So I tried with some "brute force": the CWM recovery guide found somewhere on this forum (I can't find again the link, but it was here!).
Nothing new, after the recovery the device boots again and remains stuck to the same screen.
So I manage to let it discharge completely. When it died, I plugged it again via the cable to the wall-plug and after the recharging screen, telling me that the battery level was too low, as soon as it was good to start again, it froze...
I cleaned the screen and the borders with a Q-tip, just to be sure that I tried everything I (think I) could.
Now, removing the battery it's something I could do if I only find a guide to use but I don't think that with someone less practical than me in my same situation this option could be handy to do.
It's not rooted. I did it last September before realizing after 10mins it was useless for me, so I reverted it.
I bought it on August 2011, so I should have still the warranty, but I live no more in America. Now I'm in Japan...
So, is there anything I still can do to revive my Nook?
(Backup question: does anybody know if I can buy an "english softwared" ebook reader in Japan or I can find a way to revert a Japanese one in English? -.- )
Thanks!
Right I feel silly, knowing this I just couldn't resist trying to fix my "phone", so I've bought a S7 Edge from eBay from a trusted company with a 14 day refund which is good right?
We'll I couldn't rest as the phone was going into boot loops, i.e booting once every 5 times, going into the black screen of death with blue LED.(Had to wait for the battery to drain to 0%) https://youtu.be/K9T_UF-_5ho (Even though it booted at the end after a minute of use it crashed and went back into a boot loop and crashed and then it was fine for like an hour)
It would get stuck if I went to stock recovery, get this weird static line. I did boot into recovery once so I did a factory reset hoping it would fix something, which it did not. So I guess I was going to return the phone, I then had the stupid smart idea that it booting up fully and me activating it and then resetting it would be a good idea, and boy I was wrong. So it went to you know the usual "erasing screen" in which it would get stuck on, I did the hard restart maybe 4 times then it sorta worked the android guy kept spinning until IT JUST DIED.
And here we are now me typing this out, I feel like the company isn't going to accept it back due to it not being "functional".
Absolutely no sign of life now. Not even charging, this has happened before with it when I went into the recovery menu and it got stuck. I waited out an hour and then pressed ALL the buttons and the charging icon appeared but now, now I think it's different.
TLDR: Bad eMMC of phone, caused me to try to reset it and now it's bricked?
Well lesson learned? When things aren't working at the first place don't try to fix them just refuse outright.
Some say the phone can't be bricked but I feel like I really did it this time.
No the phone wasn't rooted, no I didn't flash with ODIN.
http://imgur.com/SxA0Q9b
http://imgur.com/QLLwhot
Just return it.
There is nothing else you can do and I see no reason why they wouldn't accept it unless there's a physical damage.
Sent from my SM-G935F using Tapatalk
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