Hi everyone, I'm planning on buying a bricked moto x because it's cheap and it's new. In the past I already bought a bricked phone and made it work, however I'm not sure I will be able to this time so I wanted to know if you guys can help me understand:
-IF it can be unbricked/fixed, I don't care if it's difficult but I need to know if it's possible first.
-if the above is possible then what procedures should I follow
I'm probably asking for too much, sorry, but from what I tried to investigate it looks like it has more than one single problem so im not sure if all of them have a solution.
What the seller said:
The old owner sold it with the bootloader unlocked, I didn't knew that, so I updated via OTA (in the phone) and ended like that.
Looks like it can't have an unlocked bootloader if OTA updating, I don't even know please help me.
*since I still don't own the phone I can't test anything, I just need to know if those errors shown above have a solution, or at least are not a death declaration so I can still try something if I buy it.
Sorry for the bad quality of the images but that's what the guy selling it uploaded.
brurhh said:
Hi everyone, I'm planning on buying a bricked moto x because it's cheap and it's new. In the past I already bought a bricked phone and made it work, however I'm not sure I will be able to this time so I wanted to know if you guys can help me understand:
-IF it can be unbricked/fixed, I don't care if it's difficult but I need to know if it's possible first.
-if the above is possible then what procedures should I follow
I'm probably asking for too much, sorry, but from what I tried to investigate it looks like it has more than one single problem so im not sure if all of them have a solution.
What the seller said:
The old owner sold it with the bootloader unlocked, I didn't knew that, so I updated via OTA (in the phone) and ended like that.
Looks like it can't have an unlocked bootloader if OTA updating, I don't even know please help me.
*since I still don't own the phone I can't test anything, I just need to know if those errors shown above have a solution, or at least are not a death declaration so I can still try something if I buy it.
Sorry for the bad quality of the images but that's what the guy selling it uploaded.
Click to expand...
Click to collapse
You'll be rolling the dice on that one. MAYBE it can be fixed using the de-bricking procedures, but if anyone tells you that it can FOR SURE be fixed...well...I'd question their source.
If its cheap enough that you don't mind throwing that amount of money down the drain....give it a shot. Your call.
brurhh said:
What the seller said:
The old owner sold it with the bootloader unlocked, I didn't knew that, so I updated via OTA (in the phone) and ended like that.
Looks like it can't have an unlocked bootloader if OTA updating, I don't even know please help me.
Click to expand...
Click to collapse
I call BS on that account of what happened... The bootloader is LOCKED STATUS 0. That device was never bootloader unlocked. (and having an unlocked bootloader doesn't interfere with taking an OTA)
It could be that someone used one of the older procedures to root and disable write protection, took and OTA (losing root/write protection) and later tried to downgrade to root & disable write protection again, thus causing the brick.
It could be as simple as flashing the latest ROM (4.4.4) using mfastboot. I could be as complex as using -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 ... or it could just be a brick that can't be recovered.
Either way, like @samwathegreat said... its a roll of the dice. There is no way of knowing until after you buy the phone and try.
KidJoe said:
... or it could just be a brick that can't be recovered.
Either way, like @samwathegreat said... its a roll of the dice. There is no way of knowing until after you buy the phone and try.
Click to expand...
Click to collapse
I'll try, after all it's almost new, even if I need to replace something it would be cheaper than buying an used one, I'm worried about that CID stuff because I read that it has something to do with a unique file that has to be backed up and without that file there is nothing you can do to unbrick.
brurhh said:
I'll try, after all it's almost new, even if I need to replace something it would be cheaper than buying an used one, I'm worried about that CID stuff because I read that it has something to do with a unique file that has to be backed up and without that file there is nothing you can do to unbrick.
Click to expand...
Click to collapse
I'd be worried too. There's a great chance the device can't be fixed... And you're simply out X amount of dollars.
I'd pocket your money and add a bit when you can and buy a used fully working device. At least the money won't be wasted... Potentially.
For all you know he fastbooted a rom or firmware for another device entirely. If so, you're done. Paperweight. He could have brought it somewhere and already been told it's unsalvagable.
You just don't know.
KJ said:
I'd be worried too. There's a great chance the device can't be fixed... And you're simply out X amount of dollars.
I'd pocket your money and add a bit when you can and buy a used fully working device. At least the money won't be wasted... Potentially.
For all you know he fastbooted a rom or firmware for another device entirely. If so, you're done. Paperweight. He could have brought it somewhere and already been told it's unsalvagable.
You just don't know.
Click to expand...
Click to collapse
Thanks, what the seller says doesn't match with the fastboot screen thats my fear, I guess he don't know or perhaps doesn't want me to know how the phone really ended like that, this phone is amazing, I just got excited about getting it so cheap, i guess i'll wait more thanks again
brurhh said:
Thanks, what the seller says doesn't match with the fastboot screen thats my fear, I guess he don't know or perhaps doesn't want me to know how the phone really ended like that, this phone is amazing, I just got excited about getting it so cheap, i guess i'll wait more thanks again
Click to expand...
Click to collapse
I don't blame you!
There's some bricks you can recover from, and some you can't.
Your odds are the same if you just go to the casino and put your money for the phone on red or black at the roulette table. If you lose you lose... But if you win... You can buy a working phone. ?
Related
I am in California so I have 30 days from the day I received the phone in order to return it. So I am thinking should I return it ?....If I root my phone, can I still return it without any repercussions from rooting ?...
If you are asking why do I want to return it: IDK honestly, just feel kind of stupid/bad for spending so much on this phone especially when some of its tech is already phased out (the touch screen sensor)...but it is not on a contract and I guess I can always buy another phone and even try to sell this one....
any ways..if you have any ideas/comments on any of these issues then please advise me. The main thing here is I want to know if I can return it if I root it ?
Don't think so, you void the warranty when you unlock the bootloader. I would have to imagine that your right to return it goes with the warranty as well.
I understand what you are saying, but returning and warranty are two different things, they would not necessarily be linked...
any other insights ?
Tech is phase out???? example touch sensor?
You coming from which century? year 3010?
Well if you go buy anything and void your warranty don't expect them to refund you lol
You should be able to return it unless the seller of the phone powers it on to inspect it.
buyers remorse
just return it. if you feel like it's outdated, that's a cop out. if you feel like it's defective, clear conscience.
If you root it you will never WANT to return it
erebusting said:
I am in California so I have 30 days from the day I received the phone in order to return it. So I am thinking should I return it ?....If I root my phone, can I still return it without any repercussions from rooting ?...
If you are asking why do I want to return it: IDK honestly, just feel kind of stupid/bad for spending so much on this phone especially when some of its tech is already phased out (the touch screen sensor)...but it is not on a contract and I guess I can always buy another phone and even try to sell this one....
any ways..if you have any ideas/comments on any of these issues then please advise me. The main thing here is I want to know if I can return it if I root it ?
Click to expand...
Click to collapse
I've been hearing you complain about the phone being outdated all over the place, can you hurry and do whatever you're going to do and go to the HTC Incredible section, if there is one.
Have you already rooted it? if not, don't until you are sure you don't want to return it.
Eclair~ said:
I've been hearing you complain about the phone being outdated all over the place, can you hurry and do whatever you're going to do and go to the HTC Incredible section, if there is one.
Click to expand...
Click to collapse
So what? There are other members who want insight and all I see is "yes its worth it, just keep it etc..." I mean I understand they are writing in the Nexus One section, but that does not mean they should only read/get the positive replies about the phone -there are others like me who have gripes about it and I will share my opinion as long as they are asking...why don't you just ignore everything I say since you seem so upset that I am offending your phone simply by bringing up truths and opinions WHEN ASKED mind you. Did I say the PHONE WAS OUTDATED? NO (which is beside the point any ways)- I said some of the tech is outdated/being phased out already such as the Multi Touch Sensor...now if that hurts your feelings or makes you upset then take it up with google -I for one feel that I would like to have been able to have the new MaxTouch sensor included in the Nexus, but since that is not the case then it is definitely something which makes me second guess if I should keep it or wait for another phone to arise with the MaxTouch tech.
Now why would you reply such a way to this topic when I am asking if I can return it if it is rooted, you reply has nothing to do with my topic...is it really bugging you that much? Do you really care about what I am doing/saying so much?(thanks BTW haha )
LMFAO - Look at what I found:
http://forum.xda-developers.com/showthread.php?t=650854
Looks like ~Eclair was in the same concerned position as I am....You just happen to talk about the same thing as me also -the tech being outdated...it just so happens that it HAS already been outdated (with regards to the touch sensor that is) and that is what I was unsure about...So why are you all of a sudden coming back at me like you never had the same concerns about the phone..I am sure we are not the only ones who have these same concerns and others may want to hear it -if not they can overlook it, simple.
Put simply: just stop and either please try to be helpful or don't reply at all..seems reasonable, doesn't it ?
That was funny finding that thread you made though and you are here coming after me about the same thing you created a thread about...
imo, if you didn't want this to happen you shouldn't have posted why you wanted to return it. Just simply stating the question would do.
and I also believe that rooting would cause the phone to be non-returnable. But since they can relock the bootloader, there's also not much reason why not.
yea I wish someone had some definite insight into this topic...
Call htc then?
liam.lah said:
Call htc then?
Click to expand...
Click to collapse
yeah I guess that would give me the most official answer....
[Tutorial][Bell Atrix]What need to be done before Warranty Service?
It applies all the Bell Atrix, doesn’t matter you have Orange FR 2.1.1 or UK 2.2.3 on the phone or whatever
Simple Version:
Make sure you have CWM Recovery on it(http://forum.xda-developers.com/showthread.php?t=1019143)
Download the stock system.img (http://www.multiupload.com/T6L5RS2WH1), if you have the backup by nandroid, you can skip this step
Enter CWM Recovery to restore system.img only, then do Wipe out Data&Cache, or Force Close will be with you!
Install GingerBreak to root your phone, you can download from here: http://forum.xda-developers.com/showthread.php?t=1044765
Install CMW Recovery again, but this time, choose CHARGE MODE in order to uninstall the custom recovery
Use GingerBreak to un-root the phone
Do a factory again, then you are ready to throw this phone to any Bell Retail Store for repair
Just remind that Bell will take 4~6weeks to get your phone fixed, if you need a loaner phone, it’s $25+tax, ask before borrow since some store doesn’t even have smartphone to lend…
Full Detail Version coming soon...
Thanks, good tut to have.
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?
Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk
hoodlikegaza said:
Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Because there is no Bell SBF available (to date)
scorneil said:
Because there is no Bell SBF available (to date)
Click to expand...
Click to collapse
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.
thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
You are right, however stock system.img(from original bell firmware, not 2.1.1 or 2.2.3) already has the right prop file and bell bloatware, comparing 2.1.1 or 2.2.3, im too lazy to look for bloatware and changing by root. this seems the easiest way for me.
other than the radio version, i dont think motorola could find out this is flashed Atrix but anyway, I am still waiting for my atrix back
ks2hot4u said:
With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?
Click to expand...
Click to collapse
better do a factory reset and unroot
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
But thats the thing if you brick your device, this guide won't help as the phone is a brick.
As for hardware issues, this is the exact reason for this thread IMHO, something useful to me as my fingerprint reader is slightliy off physically which results in the device thinking that fast swipes are taking place when they are not. now I can use this when I am ready to take my device in without being harrassed about software.
With my N1 even with the bootloader unlocked they still took in the device if it was proven to be a hardware defect (again had a problem with my power button - just my luck i guess) Doubt bell would do the same.
binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
who would use this for anything other than a hardware issue? anyone who can follow this guide can also follow a SBF flash instruction to solve their software issues
binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
QFT, but......we are referring to hardware isssues here, not software.......and rooting has nothing to do with that.
Sent from my Blue Myst GladiAtrix on Bell using the XDA Premium App.
I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.
binary110 said:
I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.
Click to expand...
Click to collapse
since no one seems to be able to replicate this issue (to my knowledge) that would imply that it IS hardware related and not software
Rediculous
binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !
binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !
Click to expand...
Click to collapse
I never said the phone was not capable of being defective. I said that when someone brings it in for an issue that they caused themselves. The phones are more often screwed up by a customer, than they are actually defective.
90% of the charger issues are from using a charger different than the motorola one that came with the phone. Especially the ones with the screen response. I noted it on my atrix as well. I also have replaced a customers phone for this.
This IS a valid reason to replace the phone.
But this is also easily noticeable BEFORE you go through the process of rooting/modding the phone. and as such, you should take it up with the place your purchased it before modding it.
Its like buying a car, ripping the engine apart right away. only to find that it runs like crap after you've ripped it apart... You probably should have done a test drive before purchasing. Do you understand what i mean?
Furthermore, your friend has a legitimate issue, I'm talking about people who brick their phones and play stupid. As well, I can tell you're a part of the generation who feels they're entitled to everything under the sun from the carrier you deal with. Yet, no cable company fixes your damn television. And especially not if you screw it up yourself.
Its not apples to apples, in the sense that the cable company doesn't subsidize your tv. but even if you got a tv as a promotion through them, they'd send you to the manufacturer. Which is what i'd prefer to do with people who do stupid stuff and want it fixed.
Don't act like my time isnt worth money just because youre a needy consumer. What i'm saying is just man up, tell us you screwed it up, and we will do everything we can help.
For you to be trolling the way that you are, its obvious that this ISNT THE FORUM FOR YOU.
Thank you.
By the way, Watch your language on the forums.
seven2099 said:
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.
Click to expand...
Click to collapse
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.
Be nice guys... We are all Canadian, we love peace, don't we?!
In my case, my touchscreen's digitalize is 100% broken, it's either hypersensitive or non-sensitive at all... It happened on Bell Stock rom but I was trying to flash sfb to see if it could be fixed...
Unfortunately, i got my repair back today and still the same issue, i asked the bell staff to try the touchscreen and she said the phone is not boot up properly...
Oh well, after 90s, I ask her to try again, she clicked "BACK" 10 times in order to get back, and 5 times to run Bell Self-serve
well, I really unsatisfied with the result and I had to left the phone there and waiting for another 2 weeks, AGAIN!!!
I have 3yr contract with Bell so it has to waste time and money to get my phone fixed cuz its carelessness and impatience are wasting my money and time... The $30 loaner phone sucks and cannot even been changed...
well, looks like a little away from the topic but I've just out of the store...
even according to the repair menu, the bell stock sbf has been applied on and change of the part which i know its not the digitalize, the phone is still unusable...
AT&T users are lucky since they have their own stock sbf to flash when they wanna a repair but poor Bell users they have to use those tutorials like mine to do repair, OR UNLOCK THE BOOTLOADER AND I WONT ASK FOR WARRANTY
btw, maybe that's the reason why Apple is cool, they can get your iPhone replaced in maximum 60min not 60days even there is just a dust in screen
NFHimself said:
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.
Click to expand...
Click to collapse
see what you caused?
jk
I understand where binary was coming from but again this thread isn't for that reason. At the same time I bet we can all say we wish carriers like bell and rogers were completely full of staff like you that come with the line we will do whatever we can to help. most times reps come off as just going through the motions or looking for whatever reason to close the case.
So...I bought my HTC One in July of 2013 for retail price due to not having an upgrade and at the time being financially capable. I unlocked the bootloader, rooted it and used custom ROM's until a week ago when I got the unresolvable issue it not being able to charge anymore unless it was turned off. Now, today, it no longer charges when it's turned off and if I'm extremely lucky it's able to charge while being off for about 20 minutes before it stops.
My HTC One is absolutely useless now. I've called HTC and they told me that I still have 20 days of manufacturer warranty and that I could send in my phone if I paid shipping and they'd repair it for me, however I know they'll find out that I rooted (even though I'm back to 100% stock now) based off of the reports I've read about others. They end up making you pay for a motherboard which costs $200+ in repairs. Not only that, but I simply can't go 7-10 business days without my phone at work.
I called AT&T and the warranty there is gone now, so they refuse to help me in anyway as well. I can't sell the phone on Craigslist because it's broken and I can't even get a good deal at Best Buy I imagine for even $100 because of it being broken. I imagine they'll offer me like $40 for it.
$600 down the drain and 1 year later and I have a piece of junk in my pocket right now. I'm without a phone and do not have an upgrade to do anything about it unless I want to pay retail price for a new phone. My only option now I guess is to look into a cheaper Nexus 5 but even that is just not affordable for me.
Has anyone been in this situation? What the hell can I do?
Leather Sock said:
So...I bought my HTC One in July of 2013 for retail price due to not having an upgrade and at the time being financially capable. I unlocked the bootloader, rooted it and used custom ROM's until a week ago when I got the unresolvable issue it not being able to charge anymore unless it was turned off. Now, today, it no longer charges when it's turned off and if I'm extremely lucky it's able to charge while being off for about 20 minutes before it stops.
My HTC One is absolutely useless now. I've called HTC and they told me that I still have 20 days of manufacturer warranty and that I could send in my phone if I paid shipping and they'd repair it for me, however I know they'll find out that I rooted (even though I'm back to 100% stock now) based off of the reports I've read about others. They end up making you pay for a motherboard which costs $200+ in repairs. Not only that, but I simply can't go 7-10 business days without my phone at work.
I called AT&T and the warranty there is gone now, so they refuse to help me in anyway as well. I can't sell the phone on Craigslist because it's broken and I can't even get a good deal at Best Buy I imagine for even $100 because of it being broken. I imagine they'll offer me like $40 for it.
$600 down the drain and 1 year later and I have a piece of junk in my pocket right now. I'm without a phone and do not have an upgrade to do anything about it unless I want to pay retail price for a new phone. My only option now I guess is to look into a cheaper Nexus 5 but even that is just not affordable for me.
Has anyone been in this situation? What the hell can I do?
Click to expand...
Click to collapse
if your 100% stock, and locked in the bootloader, not relocked or unlocked, and the tampered flag has gone, then just un-root it and send it to HTC, they will never know.
Seanie280672 said:
if your 100% stock, and locked in the bootloader, not relocked or unlocked, and the tampered flag has gone, then just un-root it and send it to HTC, they will never know.
Click to expand...
Click to collapse
I'm "LOCKED" in the bootloader, S-On, not rooted and I'm using the stock RUU thing. I'm completely stock. However, I read that HTC has some sort of program or something that can see how many times your phone has been unlocked/locked or something and they end up wanting you to pay for that motherboard repair.
I mean, I guess I could try, I just hope they don't pull some sort of "Pay or we won't give your phone back" sort of deal.
Leather Sock said:
I'm "LOCKED" in the bootloader, S-On, not rooted and I'm using the stock RUU thing. I'm completely stock. However, I read that HTC has some sort of program or something that can see how many times your phone has been unlocked/locked or something and they end up wanting you to pay for that motherboard repair.
I mean, I guess I could try, I just hope they don't pull some sort of "Pay or we won't give your phone back" sort of deal.
Click to expand...
Click to collapse
I know that Samsung have some sort of counter hidden inside them which can be read quite easily and shows how many times its been flashed and rooted etc,, but im not aware of HTC having it, personally, in its current status, I would send it, if they question it, tell them your brought it off a friend and don't know what he did with it before you got it, also if they do pick up on it, then just request they send it back rather than repair it.
Seanie280672 said:
I know that Samsung have some sort of counter hidden inside them which can be read quite easily and shows how many times its been flashed and rooted etc,, but im not aware of HTC having it, personally, in its current status, I would send it, if they question it, tell them your brought it off a friend and don't know what he did with it before you got it, also if they do pick up on it, then just request they send it back rather than repair it.
Click to expand...
Click to collapse
Yeah, I'm doing that now. I guess I'll find out if I have the luxory of a replacement that will last me one last year, or if I'm out of a $500 phone. If I get the replacement, I can at least sell that thing on Craigslist when I get a new phone or trade it in towards my new one. This current one is just a piece of metal in my pocket.
Seanie280672 said:
I know that Samsung have some sort of counter hidden inside them which can be read quite easily and shows how many times its been flashed and rooted etc,, but im not aware of HTC having it, personally, in its current status, I would send it, if they question it, tell them your brought it off a friend and don't know what he did with it before you got it, also if they do pick up on it, then just request they send it back rather than repair it.
Click to expand...
Click to collapse
I forgot about the HTCDev Unlock Token thing I just read in another thread. I used that when I unlocked my bootloader. Isn't that owned by HTC and they can see that I requested to unlock my HTC One? God damn it. This has me down as hell.
Leather Sock said:
I forgot about the HTCDev Unlock Token thing I just read in another thread. I used that when I unlocked my bootloader. Isn't that owned by HTC and they can see that I requested to unlock my HTC One? God damn it. This has me down as hell.
Click to expand...
Click to collapse
In theory yes, but I nerver heard htc refusing to honor the warranty of a M7 if the phone returned with a stock rom, locked and s-on. Send the phone, i'm 99% sure they will repair it at no cost.
alray said:
In theory yes, but I nerver heard htc refusing to honor the warranty of a M7 if the phone returned with a stock rom, locked and s-on. Send the phone, i'm 99% sure they will repair it at no cost.
Click to expand...
Click to collapse
I'm really, really hoping so. I even paid the $19.00 to get my phone back 3-5 days faster because I NEED it for work.
Leather Sock said:
I'm really, really hoping so. I even paid the $19.00 to get my phone back 3-5 days faster because I NEED it for work.
Click to expand...
Click to collapse
You should be alright, should they question you, which I severely doubt, just act like you don't know ****. But definitely let us know how it goes.
Ajxx16 said:
You should be alright, should they question you, which I severely doubt, just act like you don't know ****. But definitely let us know how it goes.
Click to expand...
Click to collapse
If I get a replacement I'll probably kiss the guy who posted the return to stock guide. He'll save me $350 for a Nexus 5 that will become obsolete in October and drop $150 and make me feel even worse while the Nexus 6 rubs it's nose in my face.
Just brought my phone to UPS to be sent back to HTC. I guess we'll find out in 2-3 days whether or not they're going to quote me for stupid repairs, or if I'll get a refurb phone for replacement with no charge. If I have to pay for repairs, I won't and I'll just get the phone back, sell it to Best Buy and buy a Nexus 5 I guess.
Crossing my fingers :/
Ajxx16 said:
You should be alright, should they question you, which I severely doubt, just act like you don't know ****. But definitely let us know how it goes.
Click to expand...
Click to collapse
alray said:
In theory yes, but I nerver heard htc refusing to honor the warranty of a M7 if the phone returned with a stock rom, locked and s-on. Send the phone, i'm 99% sure they will repair it at no cost.
Click to expand...
Click to collapse
Ah...and the stress is relieved. I just received a shipping notice via email saying I'll have my HTC One on Monday. Gosh that was painful.
I had this exact problem (would only charge when powered off) about a year ago. I returned everything to stock, sent my phone to HTC and they fixed it, no questions asked. Maybe others have had difficulty, but it all was fine for me.
Does any one knows a possible solution to this?
The Amazon fire stays with black screen all the time. It is impossible to turn it on, nor recovery neither Fast Boot...
It is completily dead!!
From what I've heard, any downgrade from 5.1.1 or higher to 5.0.1 = total paperweight. Someone will probably come by and explain the mechanics of it, by my assumption is that something changed relating to the Recovery/System partitions between those revs. and thus tossing on the older software just destroys any low level communication ability the thing has.
As a rule of thumb I think you're not really supposed to be putting any older FireOS on from the latest that's been on there. I guess people may be fudging that with the last few minor revs though because the ability to root it is getting more and more impossible.
You may be able to talk someone at Amazon into giving you an exchange for a new one. Not sure the best thing to try and tell them to talk them into it. I mean I am also assuming you're out of your initial warranty period, so you'd need a creative story. Perhaps someone here will have tips on that.
snark.shark said:
From what I've heard, any downgrade from 5.1.1 or higher to 5.0.1 = total paperweight. Someone will probably come by and explain the mechanics of it, by my assumption is that something changed relating to the Recovery/System partitions between those revs. and thus tossing on the older software just destroys any low level communication ability the thing has.
As a rule of thumb I think you're not really supposed to be putting any older FireOS on from the latest that's been on there. I guess people may be fudging that with the last few minor revs though because the ability to root it is getting more and more impossible.
You may be able to talk someone at Amazon into giving you an exchange for a new one. Not sure the best thing to try and tell them to talk them into it. I mean I am also assuming you're out of your initial warranty period, so you'd need a creative story. Perhaps someone here will have tips on that.
Click to expand...
Click to collapse
I called Amazon for the warranty and they have already replace it for a new one without asking anithing. Really happy with the Amazon warranty.
Now I need to send the bricked one back to them in a month time, but I was wondering if I can bring it back to life in the meantime...
dihablo said:
I called Amazon for the warranty and they have already replace it for a new one without asking anithing. Really happy with the Amazon warranty.
Now I need to send the bricked one back to them in a month time, but I was wondering if I can bring it back to life in the meantime...
Click to expand...
Click to collapse
@snark.shark is 100% correct. Device is toast. Never roll back unless specifically advised it is safe to do. Forums are your friend. Read before acting. Amazon won't replace it again; one time courtesy exchange.
My Fire is dead
Davey126 said:
@snark.shark is 100% correct. Device is toast. Never roll back unless specifically advised it is safe to do. Forums are your friend. Read before acting. Amazon won't replace it again; one time courtesy exchange.
Click to expand...
Click to collapse
I am currently suffering from the same issue except the warranty expired plz help :''(
OpalDragon said:
I am currently suffering from the same issue except the warranty expired plz help :''(
Click to expand...
Click to collapse
Nothing can be done.
Please help me, how can I root my LG G4? Version is ZVF. What I need to do to successfully root my device? Thanks
nov0 said:
Please help me, how can I root my LG G4? Version is ZVF. What I need to do to successfully root my device? Thanks
Click to expand...
Click to collapse
there is not root no downgrade without hard brick and no fix for said hard brick only method to root is to get another phone
TheMadScientist420 said:
there is not root no downgrade without hard brick and no fix for said hard brick only method to root is to get another phone
Click to expand...
Click to collapse
I came here with the same question as the OP. What is the deal with the LG G4 and rooting? I've had this phone for two years now and not once has there been a root option for it. I've never had this issue with any devices I have owned previously. And I'd hate to have to buy a new device just so I can finally have control over what I own. Especially since I just paid off this one. Sorry for my frustration nothing personal to you but I'd really like to know why we don't and never have had a root available.
StoneRyno said:
I came here with the same question as the OP. What is the deal with the LG G4 and rooting? I've had this phone for two years now and not once has there been a root option for it. I've never had this issue with any devices I have owned previously. And I'd hate to have to buy a new device just so I can finally have control over what I own. Especially since I just paid off this one. Sorry for my frustration nothing personal to you but I'd really like to know why we don't and never have had a root available.
Click to expand...
Click to collapse
Cant root mm without a unlocked bootloader because to root mm u have to modify the kernal which messes with the secure boot chain. And gives secure boot errors.
Anti roll back prevents u from downgrading to a rootable version. Making hard bricks. Its sad but true. U need a diffrent device to root.
I actually put my g4 up again. Its having some issue
Im sure a really good dev like chainfire or someone of that knowlege could root it but theyve all moved on to more worthy devices
The g4 died well becore its time.
Only reason i got root is mine never bootlooped. And at the rates its goin never will.
Ive atempted so many diffrent methods and ideas to root mm on emulated mm roms on pc. Nothing.
Ive atempted some many methods of downgrading and nothing but bricks. Never boots. Always boot errors. I wish i could update. Being stuck on lolipop with no hope for mm or nougat if i want root.
But again. It is most def better to get a root friendly phone
Had I know this was going to be the outcome I would have gone with something else maybe even waited longer to upgrade. I bought this one on the promise it was rootable with a matter of time. I won't do that again. I simply can't afford to spend $500+ every two years to make sure I have a rootable phone when it should have that control stock. Just hidden toggle for it so morons don't do stupid stuff.
StoneRyno said:
Had I know this was going to be the outcome I would have gone with something else maybe even waited longer to upgrade. I bought this one on the promise it was rootable with a matter of time. I won't do that again. I simply can't afford to spend $500+ every two years to make sure I have a rootable phone when it should have that control stock. Just hidden toggle for it so morons don't do stupid stuff.
Click to expand...
Click to collapse
i know its dumb i learned a valuble lesson in the g4 one dont buy the newest unless its confirmed rootable.
and 2 do my research and make sure what i want to purchase is rootable.
i know how u guys feel now my g4 is about dead i just like skulking around the threads still
i got mad and threw it. busted and bent almost in half.
well i put a old cracked lcd on it i dont have wifi any more thn 5 foot from my router.
my earpiece is dead. ir ports gone. rear camera also but it still makes and recieves calls and data
i got a zte max x 2 i think it is but im in the same boat crippled fastboot and bootloader
on mm with absolutly no root in sight no stock firmwares to fix it even if i brick it in testingroot methods
Hi!
Still no luck in rooting ZVF? :/
maxrusakoff said:
Hi!
Still no luck in rooting ZVF? :/
Click to expand...
Click to collapse
no this is one of those things id put my g4 on a shelf and get a rootable device i know easier said than done but will save u a lot of headache if u quit on it now
this thing prob wont be rooted anytime soon
ive tried everything i know and ofcoarse all in sdk simulation and all leads to hard bricks
it sucks i have mines still on zv6 rooted but the mother board is damaged and i have very little wifi signal and no mi crophone
ive tried to update a zv6 rom into thinking its zvb and higher but no luck anywhere
im def no developper but i really dont think the real devs even trying to do anything with this device which i cant blame them moved on to better devices
It sucks. I have been using my g4 for two years and am pretty happy and dont have plans to upgrade, since newer phones do not offer much as compared to g4. I was hoping that someone will eventually find a way to root it again, whats wrong with people, no one has time to make this happen?
nitagro said:
It sucks. I have been using my g4 for two years and am pretty happy and dont have plans to upgrade, since newer phones do not offer much as compared to g4. I was hoping that someone will eventually find a way to root it again, whats wrong with people, no one has time to make this happen?
Click to expand...
Click to collapse
Nothing to do with time It has been tried and tried again Its lg and sprints locked bootloaders and anti rollback to rollback to rootable versions