stuck on bootloader - X 2014 Q&A, Help & Troubleshooting

Hey guys..so my moto x gen 2 whent on the blink a month ago the same day google did there ota update..
called motorola and made me go thru tons of combinations to restore it..
it seems like there is a corrupt image..so sent it out for repaire..
telus says that there is a broken chip and charged me 150$...
so refused since the phone is almost new and looking new also..
sent it to a local ubreakifix...they say they scanned the phone has nothing broken at all it is firmware related but only moto can flash it...
so called moto and complained..lol they gave me a pre-paid pkg to there repaire center,,(furture tel)..
got the phone back not repaired saying tampered boot [email protected]#$%%
i know that the web site says the warrantie is voided when boot loader is unlocked..but even the 3 reps from moto and telus never mentioned it...
so long story short it is not repaired and woundering if there a way to recover,flash or what ever..
1-tried the volume up power combos.gets to recover recovers but does not reboot.
2 -went thru all features one by one and still does not reboot...

This is why I don't bother rooting mine. There seems to be too many issues with these phones that you just never know when you'll be required to return them for a warranty repair.

true never again..sticking to my Samsung...i just want to repair it for my son..

Related

Think I Bricked my phone somehow....

I rooted when the phone first came out, did the forever root method days ago, was using ROM manager to boot into recovery and BAM!!! phone went completely dead. I had just taken it off the docking station about 15 minutes prior, had a full charge, tried swapping with my original battery, nothing...took it to verizon store, they couldn't do anything and ordered me another phone to come on Tuesday. What do you guys think??? I haven't installed any roms, radio changes, NOTHING!!!... pulled the battery a hundred times, nothing comes on
Dude, first of all, if you mess up your phone by rooting it, DO NOT take it to Verizon. Cardinal rule #1.
Second, a quick view of the threads here and you would have found this:
http://forum.xda-developers.com/showthread.php?t=1279825
Do this and you'll be fine.
Sent from my DROID BIONIC using xda premium
That's the thing
I can't get to fastboot or any boot screen. Phone is completely lifeless, doesn't even show when plugged in, tried multiple chargers, batteries, everything...nothing.
Sorry bro, sounds like a hard brick to me. if you cant power it on and holding VolumeDown+Power or holding both volume buttons+power does nothing at all, you're hard bricked (you cant fix it)
You need to buy a new device. Tell verizon you lost it or somebody stole it or something, but DO NOT take it into verizon.
Happened to me too over the weekend. Was playing Greedy Spiders and the phone froze. Rebooted and got the dual core screen twice then kaput. Tried everything and it won't turn on. Did some research and this isn't a one off problem. Took it VZW and they replaced but I have to wait for it to ship. I love how if you are buying the phone, they have them at the store, if you BOUGHT the phone and need it replaced due to warranty you have to wait.
Of course because they make more money that way

Hard bricked HTC one

Hi Guys,
I've done enough research, couldn't really find a legitimate answer. I have a rooted htc one m7 GSM. Rooted with cwm and cm 11 snapshot feb installed. Everything was fine. A few hours ago, I randomly got a "com.google.gapps" has stopped working. I pressed okay and it went away. A few minutes later I got 2-3 of those messages one right after another, and my google applications stopped working. Couldnt send texts, and log on to the play store.
I tried a few fixes and nothing worked. I decided to update my gapps, and while I'm at it install the new cm snapshot from march 17th.
I went into cwm and did wipe davlik and cache partition. Then was installing cwm. It took a while and about halfway through the phone randomly turned off. I knew I had about 50% battery so thats not an issue. I tried turning it back on and it wouldnt. I plugged it into the computer, the computer made the sound as if I plugged something in but nothing populated.
Tried vol up and down, power button alone. Saw a suggestion on here that said to use a bright light under the proximity sensor. Tried that as well.
The phone shows up as "qualcomm" in device manager when plugged in.
I CANNOT take this to HTC or the carrier for many reasons (no it is not stolen lol)
Help?
BlackMamba08 said:
Hi Guys,
The phone shows up as "qualcomm" in device manager when plugged in.
I CANNOT take this to HTC or the carrier for many reasons (no it is not stolen lol)
Help?
Click to expand...
Click to collapse
QHSUSB_DLOAD = hard brick, not possible to fix, needs a motherboard replacement
BlackMamba08 said:
I CANNOT take this to HTC or the carrier for many reasons (no it is not stolen lol)
Help?
Click to expand...
Click to collapse
Unfortunately thats your only option
I'm in Canada. The phone was originally with bell, but I did not buy it from them nor am I on their services currently. Phones boot loader was unlocked and so was its IMEI. Using on a different carrier.
What are my options in terms of htc repair?
BlackMamba08 said:
I'm in Canada. The phone was originally with bell, but I did not buy it from them nor am I on their services currently. Phones boot loader was unlocked and so was its IMEI. Using on a different carrier.
What are my options in terms of htc repair?
Click to expand...
Click to collapse
contact them from here http://www.htc.com/ca/support/service-and-repair/overview.html
and ask how much it will cost to replace the motherboard.
or try this:http://mobiletechvideos.mybigcommerce.com/htc-one-m7/
don't know if they can jtag your device to repair the qhusb brick, ask them.

S6 edge auto custom binary?

Ok so this s6 i have had for less then 1 month is becoming a huge hassle. First it kept restarting by itself even during bootup. Sent in for repair samsung said nothing was wrng with it and sent it back... Got it back first startup it rebooted... Then after uaing it to 2% i charged it up and booted the phone, got a message "unauthorized att softwsre detected". Went to att they tried to reflash didnt help, told me to go to bestbuy samsung kiosk, they tried to reflash nothing... Told to call samsung and they would fix it, sent it in and they said thwy cant do anything cause its rooted. What can i do? And how did this even happen.
Did you buy it new, or used?
Brand new was orderd from att direct.
I actually have a video of the system saying it was custom then after i rebooted it went back to offical.
Actually starting to think samsung repair rooted the phone cause they couldnt repair it...
I'd contact Samsung again, explain the situation, and see if they'll replace it.
Tried they said cause its rooted they can't even touch it and since its rooted it voids the warranty and any connection to them... like WTF? My friend is on the phone with some manager at samsung right now :/. But my hopes are low. How does a company like this have such retarded policies. They can't even check the phone if its actually rooted...(they said they can't touch it cause the knox counter was tripped) I assume the binary somehow got messed up, hardware related? I bet if they just checked the software it would be official with chunks of code missing or something. I have video proof of it going from custom to official by itself without me having it plugged into anything. I have no clue who i can go to about this issue anymore, Phone is brand new (one month) and im still paying for it under ATT Next program...
Have AT&T check the serial and imei of the phone against your original order. Perhaps you got sent back the wrong phone from the repair depot? AoN
I checked the serial once i recieved it, it was the correct phone. I have video proof of it "rooting" it self. Basically the phone said it was custom then it a d it was offical after i rebooted it.(of course this was taken in two videos but u can see the time so no tampering could have occured.)
https://m.youtube.com/watch?v=WpxGI644OXA
https://m.youtube.com/watch?v=XJva5kmFLjE
So i figured out why it says i have a custom software... The BestBuy Samsung Rep flashed the wrong build to my device. They flashed "G925AUCU1AOE2" which i don't think is released yet or at least not pushed to my device. So any suggestions to what i can do? They cased my warranty to be voided and i still have the restarting issues.

Nexus 6 (rooted, stock rom) won't turn on anymore. Please help

Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!

Boot loop replacement phone

My phone finally got the boot loop error my phone mfg date is may 2015 but my concern is I've sent my phone to lg it's out of warranty and is rooted will lg just send it back since it's rooted or actually fix my phone. If anyone has this happens to them please let me know your end results thank you
Sent from my iPhone using Tapatalk
bleedingthru said:
My phone finally got the boot loop error my phone mfg date is may 2015 but my concern is I've sent my phone to lg it's out of warranty and is rooted will lg just send it back since it's rooted or actually fix my phone. If anyone has this happens to them please let me know your end results thank you
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
its unknown.. they may fix it they may not. sometimes with warranty and root no fix.
Ya it's been out of warranty for a year so I'm keeping my fingers crossed lol thanks for the reply
Sent from my iPhone using Tapatalk
i just got my second warranty replacement device TODAY(I am grandfathered into the original $10 per month Jump!/insurance program)
the first time was back in Oct, the G4 went into bootloop and would not fully power on. would at most show the LG boot logo and then repeat. I had an unlocked bootloader, a custom recovery, and a custom rom in place. there was no physical damage. phone worked fine until the bootloop.
result: tmobile warranty replacement. never heard anything regarding any software modification/rooting/bootloader unlocking.
the second time, phone started acting up and having random reboots and sometimes freezing. then it appeared to be stuck in a bootloop, but would sometimes attempt to load the boot animation, and once or twice actually loaded the custom rom I was running, but would then freeze within minutes of operation. Bootloader was unlocked, custom recovery, custom rom.
This time, because I was able to get it to boot long enough without tinkering with the device at all..... I was able to stay booted long enough to initiate a LGUP .kdz install which returned the device to stock. i was then able to adb reboot bootloader, and oem bootloader lock. so the phone had zero signs of ever being "tampered" with.
of course the thing turned on today while i was in store, loaded up as if it was a fresh install. I assured the customer serice rep that it was having issues, and that I would not be replacing the device under warranty if needn't be.
result: tmobile warranty replacement.
he laughed at me and smiled, as if i were a typical samdung, i mean typical Tmobile customer who didnt know anything abut my device.
ElfinJNoty said:
i just got my second warranty replacement device TODAY(I am grandfathered into the original $10 per month Jump!/insurance program)
the first time was back in Oct, the G4 went into bootloop and would not fully power on. would at most show the LG boot logo and then repeat. I had an unlocked bootloader, a custom recovery, and a custom rom in place. there was no physical damage. phone worked fine until the bootloop.
result: tmobile warranty replacement. never heard anything regarding any software modification/rooting/bootloader unlocking.
the second time, phone started acting up and having random reboots and sometimes freezing. then it appeared to be stuck in a bootloop, but would sometimes attempt to load the boot animation, and once or twice actually loaded the custom rom I was running, but would then freeze within minutes of operation. Bootloader was unlocked, custom recovery, custom rom.
This time, because I was able to get it to boot long enough without tinkering with the device at all..... I was able to stay booted long enough to initiate a LGUP .kdz install which returned the device to stock. i was then able to adb reboot bootloader, and oem bootloader lock. so the phone had zero signs of ever being "tampered" with.
of course the thing turned on today while i was in store, loaded up as if it was a fresh install. I assured the customer serice rep that it was having issues, and that I would not be replacing the device under warranty if needn't be.
result: tmobile warranty replacement.
he laughed at me and smiled, as if i were a typical samdung, i mean typical Tmobile customer who didnt know anything abut my device.
Click to expand...
Click to collapse
See what I'm worried about is my phone had. Been out of warranty since November of 2016 so I'm wondering if they are gonna charge me or even fix it since im rooted
Sent from my iPhone using Tapatalk
bleedingthru said:
See what I'm worried about is my phone had. Been out of warranty since November of 2016 so I'm wondering if they are gonna charge me or even fix it since im rooted
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
mine was only considered warranty replacement via Tmobile Jump!+Insurance(maybe thats why i pay the extra $12 a month?)
..... really cant comment on any other type of situations.
good luck

Categories

Resources