Related
Hello,
I followed step-by-step this thread.( http://forum.xda-developers.com/showthread.php?t=1982982 )
Since I ve been a listener and this is first time caller, Im not allowed to reply in Developer section until 10 post are made.
This is my first post and need help.
Everything works just as the DEV explained. The bugs are the known ones, and it works...fine.
But, things like the camera bug (3rd party apps cant use it, like instagram, guess Skype, Google Now, etc...), screenshots and auto-rotation made me want to go back. (I could manage the APN thing by following one of the replier's advices)
So, question is: Is out there a more stable CM10 ROM? (I know the link I related isnt from actual CM10, yet a modified one. But after reaserch I found that the original CM10 also have this same known issues). If there isn't. Is there a way to go back to a bug-free ICS version?
If there is, I would need a step-by-step guide.
Thanks in advance for all replies.
______
Motorola Atrix 2 - CM10/MagicMod ROM
WaltLlanos said:
Hello,
I followed step-by-step this thread.( http://forum.xda-developers.com/showthread.php?t=1982982 )
Since I ve been a listener and this is first time caller, Im not allowed to reply in Developer section until 10 post are made.
This is my first post and need help.
Everything works just as the DEV explained. The bugs are the known ones, and it works...fine.
But, things like the camera bug (3rd party apps cant use it, like instagram, guess Skype, Google Now, etc...), screenshots and auto-rotation made me want to go back. (I could manage the APN thing by following one of the replier's advices)
So, question is: Is out there a more stable CM10 ROM? (I know the link I related isnt from actual CM10, yet a modified one. But after reaserch I found that the original CM10 also have this same known issues). If there isn't. Is there a way to go back to a bug-free ICS version?
If there is, I would need a step-by-step guide.
Thanks in advance for all replies.
______
Motorola Atrix 2 - CM10/MagicMod ROM
Click to expand...
Click to collapse
Sure you can go back to stock ICS.
Find the FXZ file for your region here: http://sbf.droid-developers.org/edison/list.php
Follow The noob guide on how to flash FXZ here: http://forum.xda-developers.com/showthread.php?t=1396650
HELP!!
Waiting4MyAndroid said:
Sure you can go back to stock ICS.
Find the FXZ file for your region here: http://sbf.droid-developers.org/edison/list.php
Follow The noob guide on how to flash FXZ here: http://forum.xda-developers.com/showthread.php?t=1396650
Click to expand...
Click to collapse
I followed the steps to flash the SBF and give my Atrix 2 the stock ICS version again.
I did the whole process and clicked START
After a while, several minutes, it showed
"FAILED FLASHING PROCESS, FAILED FLASHING PROCESS. 5/20 REBOOT-BOOTLOADER -> NO ARRIVAL MESSAGE NOTIFICATION; PHONE DISCONNECTED"
And in the result column it shows FAILED
I made sure the battery was full before begin the process, and I haven't touched the phone at all since it started.
What do I do? It's still plugged and the screen's off (Don't sure if the phone is off). I havent touched a thing.
This is the SBF I downloaded:
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip
from here: http://sbf.droid-developers.org/edison/list.php
EDIT:
When still plugged in, I pressed the POWER button, and nothing happened, Thought it was off.
I closed the RSD and unplugged the phone from PC and tried to turn it on. NOTHING HAPPENED.
No LED light, No Moto logo, nothing.
Removed battery, tried again....nothing...at all. ¿Dead?
Is it totally screwed? Nothing to do about? PLEASE HELP ME!. Im about to die.
WaltLlanos said:
I followed the steps to flash the SBF and give my Atrix 2 the stock ICS version again.
I did the whole process and clicked START
After a while, several minutes, it showed
"FAILED FLASHING PROCESS, FAILED FLASHING PROCESS. 5/20 REBOOT-BOOTLOADER -> NO ARRIVAL MESSAGE NOTIFICATION; PHONE DISCONNECTED"
And in the result column it shows FAILED
I made sure the battery was full before begin the process, and I haven't touched the phone at all since it started.
What do I do? It's still plugged and the screen's off (Don't sure if the phone is off). I havent touched a thing.
This is the SBF I downloaded:
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip
from here: http://sbf.droid-developers.org/edison/list.php
EDIT:
When still plugged in, I pressed the POWER button, and nothing happened, Thought it was off.
I closed the RSD and unplugged the phone from PC and tried to turn it on. NOTHING HAPPENED.
No LED light, No Moto logo, nothing.
Removed battery, tried again....nothing...at all. ¿Dead?
Is it totally screwed? Nothing to do about? PLEASE HELP ME!. Im about to die.
Click to expand...
Click to collapse
If your phone is ATT version MB865, then you used the wrong SBF. The one to flash is
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip md5=2BF9CCD528C05D26523ACC5B38AC76C6
I believe your phone is soft bricked with a dead battery. Find a way to charge your battery and try to RSD again.
Waiting4MyAndroid said:
If your phone is ATT version MB865, then you used the wrong SBF. The one to flash is
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip md5=2BF9CCD528C05D26523ACC5B38AC76C6
I believe your phone is soft bricked with a dead battery. Find a way to charge your battery and try to RSD again.
Click to expand...
Click to collapse
Actually, I think he is, sorry to say, super-hardbricked. Take a look here, it has all the proper explanations about bricks:
http://forum.xda-developers.com/showthread.php?t=1937112
If he was on ICS and an AT&T phone and flashed a non-AT&T firmware, he is most likely screwed. We have seen this way too many times, sorry to say, but to the OP, Please read more before trying these type of things and use search and not get too antsy before attempting things. This phone even though it has a bootloader lock, you can still very easily hard brick it.
The OP, just might get lucky and be able to charge his phone with an external charger, but I am pretty sure that will not do it.
I would go on ebay or craigslist and buy a working A2 with a cracked screen (much cheaper this way), and change out the board with your screen and such, and you should be back in business.
@Waiting4MyAndroid, next time you try to help someone ask them for more information, so you/we can be of better help, this guys is obviously a noob, and if we knew which region he was from and which phone he has, we/you could have given him the EXACT link to the correct file, and then walked him through what and what not to do. I am not trying to be a jerk. I am just saying that most people do not search or read these forms, they ask in a dire need and even when you give a link to read something, they are in panic mode and still do not read, and just do what they think is the thing you just mentioned, even though it may not be the right thing. I know this has been covered so many times, but I have learned that no matter what people do not read or search no matter what you mention, that is why we see soooooooo many of these types of posts over and over.
jimbridgman said:
Actually, I think he is, sorry to say, super-hardbricked. Take a look here, it has all the proper explanations about bricks:
http://forum.xda-developers.com/showthread.php?t=1937112
If he was on ICS and an AT&T phone and flashed a non-AT&T firmware, he is most likely screwed. We have seen this way too many times, sorry to say, but to the OP, Please read more before trying these type of things and use search and not get too antsy before attempting things. This phone even though it has a bootloader lock, you can still very easily hard brick it.
The OP, just might get lucky and be able to charge his phone with an external charger, but I am pretty sure that will not do it.
I would go on ebay or craigslist and buy a working A2 with a cracked screen (much cheaper this way), and change out the board with your screen and such, and you should be back in business.
@Waiting4MyAndroid, next time you try to help someone ask them for more information, so you/we can be of better help, this guys is obviously a noob, and if we knew which region he was from and which phone he has, we/you could have given him the EXACT link to the correct file, and then walked him through what and what not to do. I am not trying to be a jerk. I am just saying that most people do not search or read these forms, they ask in a dire need and even when you give a link to read something, they are in panic mode and still do not read, and just do what they think is the thing you just mentioned, even though it may not be the right thing. I know this has been covered so many times, but I have learned that no matter what people do not read or search no matter what you mention, that is why we see soooooooo many of these types of posts over and over.
Click to expand...
Click to collapse
Jim your advice to me is well taken. Usually I do ask more questions before I offer advice. In this case the OP "seemed" knowledgeable due to the fact his phone was on CM10/MagicMod. I guess everyone should be treated as a NOOB until proven other wise! Hopefully the OP can still recover his phone with a charged battery.
Sent from my MB865 using xda app-developers app
Waiting4MyAndroid said:
Jim your advice to me is well taken. Usually I do ask more questions before I offer advice. In this case the OP "seemed" knowledgeable due to the fact his phone was on CM10/MagicMod. I guess everyone should be treated as a NOOB until proven other wise! Hopefully the OP can still recover his phone with a charged battery.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
No worries. I was going by his join date of Dec. 2012, and only having posted five times, for noting that he was a noob. I have found that a lot of people can talk the talk well in here, but have maybe used another phone that is not like the A2 and tend to easily mess it up. Especially if this is their first android.
Waiting4MyAndroid said:
Jim your advice to me is well taken. Usually I do ask more questions before I offer advice. In this case the OP "seemed" knowledgeable due to the fact his phone was on CM10/MagicMod. I guess everyone should be treated as a NOOB until proven other wise! Hopefully the OP can still recover his phone with a charged battery.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Thanks VERY MUCH for your help. And yes, this is my first Android, and first time flashing, and as you supposed, noob.
:/ I want to believe it is the battery and with a charging will revive, but I don't know. The "super-hardbrick" thing makes more sense to me.
IT WAS FULLY CHARGED, it can't drain 98% in a few minutes, can it?...
Aaaaanyways, I will see if by charging the battery and trying it will show a light.
(Will it charge the battery in this state? or I'll have to make it by other means?)
Thanks @Waiting4MyAndroid and @jimbridgman for replying.
EDIT: When I plug it in the wall, nothing happens. No LEDs, no Moto logo, just black screen. It doesn't shows life signals. Same happens when plugged to the PC.
WaltLlanos said:
Thanks VERY MUCH for your help. And yes, this is my first Android, and first time flashing, and as you supposed, noob.
:/ I want to believe it is the battery and with a charging will revive, but I don't know. The "super-hardbrick" thing makes more sense to me.
IT WAS FULLY CHARGED, it can't drain 98% in a few minutes, can it?...
Aaaaanyways, I will see if by charging the battery and trying it will show a light.
(Will it charge the battery in this state? or I'll have to make it by other means?)
Thanks @Waiting4MyAndroid and @jimbridgman for replying.
EDIT: When I plug it in the wall, nothing happens. No LEDs, no Moto logo, just black screen. It doesn't shows life signals. Same happens when plugged to the PC.
Click to expand...
Click to collapse
If that is the case then you will have to try either the Macguvyer method:
http://forum.xda-developers.com/showthread.php?t=892026
Or find someone with a similar phone that works, that will let you use their phone to charge your battery with (another A2 or a bionic).
Those are just so you can see if it is a battery issue, but at this point, I am thinking you are hardbricked.
Do you have an AT&T branded phone (there will be an at&t logo at the bottom front of the phone under the capacitive buttons)?
jimbridgman said:
If that is the case then you will have to try either the Macguvyer method:
http://forum.xda-developers.com/showthread.php?t=892026
Or find someone with a similar phone that works, that will let you use their phone to charge your battery with (another A2 or a bionic).
Those are just so you can see if it is a battery issue, but at this point, I am thinking you are hardbricked.
Do you have an AT&T branded phone (there will be an at&t logo at the bottom front of the phone under the capacitive buttons)?
Click to expand...
Click to collapse
Yes, its an AT&T device. I'll try to charge the battery.
/In the case its hardbrick, there's nothing we can do, right? AT ALL?/
WaltLlanos said:
Yes, its an AT&T device. I'll try to charge the battery.
/In the case its hardbrick, there's nothing we can do, right? AT ALL?/
Click to expand...
Click to collapse
You can try and get AT&T to exchange it for a refurb, just tell them you charged it overnight and woke and it was like this. The only thing is that you must have, had the phone less than a year to qualify for this, and you MUST be in the US.
Otherwise you can buy an A2 on ebay or craigslist with a broken screen and put your good screen on that phone and be back in action. There is a thread in the general section that is a sticky on how to exchange your screen with the phone you get that has a broken one. This will be only if you are out of the year warranty or bought this phone and use it outside the US.
http://forum.xda-developers.com/showthread.php?t=1746094
jimbridgman said:
You can try and get AT&T to exchange it for a refurb, just tell them you charged it overnight and woke and it was like this. The only thing is that you must have, had the phone less than a year to qualify for this, and you MUST be in the US.
Otherwise you can buy an A2 on ebay or craigslist with a broken screen and put your good screen on that phone and be back in action. There is a thread in the general section that is a sticky on how to exchange your screen with the phone you get that has a broken one. This will be only if you are out of the year warranty or bought this phone and use it outside the US.
http://forum.xda-developers.com/showthread.php?t=1746094
Click to expand...
Click to collapse
I'm out of US, so I guess the warranty thing won't work. (Damn, I guess if I get out of this, will NOT ever try to handle upgrades, and flashing and this stuff) I bought the Atrix 2 from e-bay..Its (was) pre-paid.
Thank you so much for everything. And well, sorry for the inconveniences.
By the way, can you explain to me, what did I do exactly to the phone? I mean, what I understand is that I took out the "software" that ran everything in the device (including powering on) and didn't replace it with the new one since the process didn't complete. So in the end, I took the "soul" out of it, leaving just the dead "body". Does it make sense?
WaltLlanos said:
I'm out of US, so I guess the warranty thing won't work. (Damn, I guess if I get out of this, will NOT ever try to handle upgrades, and flashing and this stuff) I bought the Atrix 2 from e-bay..Its (was) pre-paid.
Thank you so much for everything. And well, sorry for the inconveniences.
By the way, can you explain to me, what did I do exactly to the phone? I mean, what I understand is that I took out the "software" that ran everything in the device (including powering on) and didn't replace it with the new one since the process didn't complete. So in the end, I took the "soul" out of it, leaving just the dead "body". Does it make sense?
Click to expand...
Click to collapse
What you did was flash a non AT&T firmware to the device, which causes the phone to "hardbrick" AT&T has some checks built into the hardware that will make the phone "die" if this is done. So if you do get another one, just make sure that you ONLY flash the proper AT&T FXZ file on the SBf-droid.com site, they say which ones are AT&T.
You can flash all the "ROMS" you want, you just can not use a firmware (FXZ) that is not AT&T based, so if you bootloop or softbrick, you need to make sure you use this FXZ file for AT&T ICS:
334.7 MiB 2BF9CCD528C05D26523ACC5B38AC76C6 ATT US InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip http://sbf.droid-developers.org/edison/InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
My guess is that you did not use this file before, and RSD lite began to flash the bootloader, then went to reboot, and the checks happened and saw that the wrong bootloader was flashed and that set off an efuse that "bricked" the phone.
warrenty
Check to see if u have warranty still with motorola. Just give some lame excuse. Dont mention anything about roooting or roms or ull be f'ed. I sent then 2 hard bricked phones so on my 3rd A2 now. Just pay for shipping and it will be back in ur hands in hopefully less than 2 weeks.
Cant enter link cause im newb but motorola com go to service look for a2 and
Its on the bottom left column just enter imei#
widekyle said:
Check to see if u have warranty still with motorola. Just give some lame excuse. Dont mention anything about roooting or roms or ull be f'ed. I sent then 2 hard bricked phones so on my 3rd A2 now. Just pay for shipping and it will be back in ur hands in hopefully less than 2 weeks.
Cant enter link cause im newb but motorola com go to service look for a2 and
Its on the bottom left column just enter imei#
Click to expand...
Click to collapse
That only works, if Motorola warranties the phone in the Country that you live in.
jimbridgman said:
That only works, if Motorola warranties the phone in the Country that you live in.
Click to expand...
Click to collapse
I live in Colombia, and I bought the device on April 2012 on ebay, had it shipped internationally with USPS.
Do you think I can claim warranty for Motorola directly? Obviously not mentioning anything about ROMs, flashing, and anything. But what can I say?
WaltLlanos said:
I live in Colombia, and I bought the device on April 2012 on ebay, had it shipped internationally with USPS.
Do you think I can claim warranty for Motorola directly? Obviously not mentioning anything about ROMs, flashing, and anything. But what can I say?
Click to expand...
Click to collapse
Nope, you can not get moto to warranty it. You are better buying another phone. I would buy one that will be warrantied in your country, just in case something like this happens.
Hi All,
Just purchased a great new htc one mini(black).
When I went into about and looked for software updates it is not visible.
Also, at the bottom of about it says this is a test device in red.
I checked with store model today and everything is exactly the same except the store has software updates and mine does not and red says something else.
Can anyone share how to update to kit-kat as I am on 4.2.2 jelly bean.
It seems genuine but missing these critical options.
Any ideas?
TIA
Personally, i would be concerned that a brand new phone said it was a "test device" especially if you haven't done anything to it yet. To me it sounds like either someone has messed about with it previously to unlock from a particular network OR possibly its a refurbished phone. (i could be wrong, these are just my thoughts)
As it says its a "Test Device" You wont be able to receive/download/apply OTA updates, it should say something to that effect in the "red" text
you have the option to unlock bootloader, root and install a custom rom from xda. ( you can get all this info on these threads but you will void warranty)
I would take it up with where you bought it from before starting the rooting process.
*what does it say when you boot into bootloader*
Thnx for the quick reply.
I got it at an incredible price and it runs superbly.
Really happy and keeping it.
Antutu I got 15k scores whereas default HTC one mini is around 10k.
I just hope I can root it. Any recommendations ?
By the looks of it, it seems that you've bought a 2nd hand phone and most likely have a custom rom on it, just go and check it out in About - Software Information.
By the looks if it the software version is all legit for 4.2.2 jelly bean.
Not sure why update software is not visible though.
Phone runs brilliantly.
Very happy.
xlr8me said:
Not sure why update software is not visible though.
Click to expand...
Click to collapse
I explained why software update was not visible in my first reply
Yeah I went into the bootloader and it says S-off and locked.
So not sure what it all means but thanks for the replies.
xlr8me said:
Yeah I went into the bootloader and it says S-off and locked.
So not sure what it all means but thanks for the replies.
Click to expand...
Click to collapse
please read this entire forum.. if you want to now about your device..
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked so apparently it's all my responsibility, not their's at all for pushing a corrupted file...
Basically stick to 4.4.2 as long as you can. If anything, 4.4.4 is a downgrade, at best a side-grade. Much like 4.4.x all together really - really wish i'd stayed on 4.3
So I there anything i can do to unbrick it? I'm buying a new one anyway, but might use the "bricked" one for testing ROMs or something but if I can't get to fastboot there's nothing much I can do.
Moto G will not power up
Plug it into the charger
Hold the VOL DOWN key
While still holding the VOL DOWN key, press and hold the POWER key
Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
After holding the keys down for more than two minutes, release them.
The Flash Boot screen will display, and the Normal Reboot option will be highlighted
Press the VOL UP key and the device will start a normal reboot.
If you have tried the above and it didn't work, try this:
Plug in the phone for 15 minutes.
Proceed to Step 2 above.
Source: https://forums.motorola.com/posts/3d5eadc25d
Broken_motoG said:
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked
Click to expand...
Click to collapse
If the bootloader has mysteriously become unlocked, then clearly you did modify the phone and they are entitled to decline a refund. This is made perfectly clear when the procedure to unlock is executed.
That's why you should be careful of anything you do with the phone once the bootloader is unlocked.
Broken_motoG said:
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked so apparently it's all my responsibility, not their's at all for pushing a corrupted file...
Basically stick to 4.4.2 as long as you can. If anything, 4.4.4 is a downgrade, at best a side-grade. Much like 4.4.x all together really - really wish i'd stayed on 4.3
So I there anything i can do to unbrick it? I'm buying a new one anyway, but might use the "bricked" one for testing ROMs or something but if I can't get to fastboot there's nothing much I can do.
Click to expand...
Click to collapse
Hi, DO NOT take that from Motorola, because you live in the UK which is in Europe (Thats important) Motorola are legally obliged to help you as unlocking the bootloader/loading custom ROMs on to your device is seen as a legitimate practice and not a voiding act of your statuary warranty.
As long as you don't alter hardware they are NOT entitled to decline a refund/replacement under the circumstances, however they can refer you to the retailer you purchased it from but the rules still stand that they have to help you get a new/refurbished phone or a refund
Use this to prove it to them and make them pay up: http://fsfe.org/freesoftware/legal/flashingdevices.en.html
Hope this could be of assistance to you and I'm sorry if its off-topic but it needs to be made clear to all EU Motorola owners
TechMinerUK said:
Hi, DO NOT take that from Motorola, because you live in the UK which is in Europe (Thats important) Motorola are legally obliged to help you as unlocking the bootloader/loading custom ROMs on to your device is seen as a legitimate practice and not a voiding act of your statuary warranty.
As long as you don't alter hardware they are NOT entitled to decline a refund/replacement under the circumstances, however they can refer you to the retailer you purchased it from but the rules still stand that they have to help you get a new/refurbished phone or a refund
Use this to prove it to them and make them pay up: ht tp:// f sfe.org/f reesoftw are/legal/flash ingdev ices.en.html
Hope this could be of assistance to you and I'm sorry if its off-topic but it needs to be made clear to all EU Motorola owners
Click to expand...
Click to collapse
Thanks for that - didn't realise that law existed, but that will be really helpful :laugh::laugh::laugh::laugh:
Broken_motoG said:
Thanks for that - didn't realise that law existed, but that will be really helpful :laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
No problem, I checked on it before I installed CM on my Moto G last week
Hope I could help and good luck with the phone
Good luck with unbricking your phone, but oh no, I've already downloaded the 4.4.4 update!
Oh wait, my phone works just fine...
And if it immediately bricked your phone, how do you know that "If anything, 4.4.4 is a downgrade, at best a side-grade."?
startersorders said:
Good luck with unbricking your phone, but oh no, I've already downloaded the 4.4.4 update!
Oh wait, my phone works just fine...
And if it immediately bricked your phone, how do you know that "If anything, 4.4.4 is a downgrade, at best a side-grade."?
Click to expand...
Click to collapse
I don't want to get off-topic but if an update bricked your phone its a pretty BIG downgrade as it went from a phone with many uses to a paperweight (allbeit a pretty paper weight) as it has lost functionality and its the softwares fault.
Its personal opinion
OP needs to establish if he has simply not encountered the ''Moto G won't turn on' issue. I included instructions above. It could all be just bad timing.
Broken_motoG said:
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked so apparently it's all my responsibility, not their's at all for pushing a corrupted file...
Basically stick to 4.4.2 as long as you can. If anything, 4.4.4 is a downgrade, at best a side-grade. Much like 4.4.x all together really - really wish i'd stayed on 4.3
So I there anything i can do to unbrick it? I'm buying a new one anyway, but might use the "bricked" one for testing ROMs or something but if I can't get to fastboot there's nothing much I can do.
Click to expand...
Click to collapse
I don't think this is anything to do with the update. If it was we would have heard about it from more that just you.
After all mine works perfectly fine after the update and I'm UK Tesco.
dethrat said:
I don't think this is anything to do with the update. If it was we would have heard about it from more that just you.
After all mine works perfectly fine after the update and I'm UK Tesco.
Click to expand...
Click to collapse
Same here and plenty of subtle improvements (get rid of the Carrier name woo-hoo) and bug fixes in 4.4.4 - (several features of my Automation app - MacroDroid suddenly work when they didn't before), not to mention one or two security patches. Slightly better battery life and noticeably smoother animations are a nice bonus too. New Dialler is a big improvement - the old one was ugly.
neu - smurph said:
Same here and plenty of subtle improvements (get rid of the Carrier name woo-hoo) and bug fixes in 4.4.4 - (several features of my Automation app - MacroDroid suddenly work when they didn't before), not to mention one or two security patches. Slightly better battery life and noticeably smoother animations are a nice bonus too. New Dialler is a big improvement - the old one was ugly.
Click to expand...
Click to collapse
It depends, my friend who has a Moto G update to 4.4.4 lost all functionality of his apps and his clock stopped working. It just depends as his phone wasn't rooted with no bootloader unlock
TechMinerUK said:
I don't want to get off-topic but if an update bricked your phone its a pretty BIG downgrade as it went from a phone with many uses to a paperweight (allbeit a pretty paper weight) as it has lost functionality and its the softwares fault.
Its personal opinion
Click to expand...
Click to collapse
Of course a bricked phone is useless, but something obviously went wrong with the OP's phone, and its probably a coincidence that it happened while updating. It's the absurdity of the comments "DO NOT download the 4.4.4 update" and "4.4.4 is a downgrade" that got me to post, because its pretty clear that many people have updated without any issue.
Not besmirching the OP's problem, and like I said, I wish him well in getting his phone working.
Also, depending how old the phone is and where you bought it from, isn't it an option just to return it to the seller for an exchange. Just tell them it stopped working and you want a replacement phone?
Ok, so I happened upon an LG G4 H810 AT&T variant at a pawn shop a few weeks ago, they couldn't get it working because of the boot loop issue (person that pawned it probably did so knowing it was defective and had it working just long enough to demo it to get the cash). I took a look at it, great shape overall, no damage noted, plain old "ceramic" back cover, battery had a date of January 15 2016 on it so it's tough to say if the battery was just newer or the device itself since I couldn't get it to boot. Date code was 508 so obviously one of the well known defective models.
Long story short: got it for a pittance because they couldn't get anyone else to buy it, got it home, registered it at LG's website on my account, waited 2 days then chatted their support up and got them to accept it for RMA, shipped it out last week and it should be back tomorrow. I'm not sure if they repaired it or replaced it - the limited info I have says they "Swap Board (Main/RF)" so I'm guessing the entire motherboard was swapped for (hopefully) a newer one made this year that might not fail but probably will.
So, I had a question or two and I've done quite a bit of research the past few days and never found specific answers so at this point I'm just going to ask them and be done with it:
1) There's apparently no working root at all for the H810 that I've been able to find. I'm going to assume that the unit I'll be getting tomorrow or Tuesday will have been upgraded to Marshmallow unfortunately but that's just how it goes so there's no rolling back as I understand things. If there's a working root I'd be interested in knowing which one that happens to be. Also with no root there's probably no recovery either but I will keep researching to find out more as I'm able.
2) There's apparently no custom ROMs available because of the locked bootloader which will never get unlocked obviously as well. I've read that the PR (Puerto Rico) ROM could be installed on an H810 that was still running Lollipop with the v2 rollback but if this repaired board is Marshmallow that means it's been upgraded to v3 rollback and so that's dead in the water too.
3) I'm also going to assume that if the board has been replaced and hopefully is one made in 2016 (with a 6xx serial number) then it could last a while but there's no guarantee of it. I've seen people say the 6xx versions have not failed but then I find a post or two from someone that claims to know someone with a 6xx model and it failed at least once on them but I can't get any actual verification on it, that's just hearsay to me if there's no direct proof so all I can do is continue hoping it's a 6xx revision board and that it's not going to fail anytime soon.
This will be my second G4, had a Sprint variant last year and never had problems with it, sold it to a gent from Australia when he visited Las Vegas and as far as I know he's still using it, who knows.
If anyone can offer some info related to those questions I'd be grateful so thanks in advance if anyone can.
Have fun, always...
EDIT:
Seems that if I get very lucky and the replacement board comes with H81020n on it - the original Marshmallow build - there's a chance I can roll it back to H81010o using the TOT method from the other thread for it, that would at least get me root potential I suppose. Guess I'll find out tomorrow if the replacement arrives. Can't find any absolutely verified info about later builds, looks like the very latest patch build is H81022b from September and I'm going to assume if that happens to be on the board then all hope is lost, basically. Ugh...
br0adband said:
Ok, so I happened upon an LG G4 H810 AT&T variant at a pawn shop a few weeks ago, they couldn't get it working because of the boot loop issue (person that pawned it probably did so knowing it was defective and had it working just long enough to demo it to get the cash). I took a look at it, great shape overall, no damage noted, plain old "ceramic" back cover, battery had a date of January 15 2016 on it so it's tough to say if the battery was just newer or the device itself since I couldn't get it to boot. Date code was 508 so obviously one of the well known defective models.
Long story short: got it for a pittance because they couldn't get anyone else to buy it, got it home, registered it at LG's website on my account, waited 2 days then chatted their support up and got them to accept it for RMA, shipped it out last week and it should be back tomorrow. I'm not sure if they repaired it or replaced it - the limited info I have says they "Swap Board (Main/RF)" so I'm guessing the entire motherboard was swapped for (hopefully) a newer one made this year that might not fail but probably will.
So, I had a question or two and I've done quite a bit of research the past few days and never found specific answers so at this point I'm just going to ask them and be done with it:
1) There's apparently no working root at all for the H810 that I've been able to find. I'm going to assume that the unit I'll be getting tomorrow or Tuesday will have been upgraded to Marshmallow unfortunately but that's just how it goes so there's no rolling back as I understand things. If there's a working root I'd be interested in knowing which one that happens to be. Also with no root there's probably no recovery either but I will keep researching to find out more as I'm able.
2) There's apparently no custom ROMs available because of the locked bootloader which will never get unlocked obviously as well. I've read that the PR (Puerto Rico) ROM could be installed on an H810 that was still running Lollipop with the v2 rollback but if this repaired board is Marshmallow that means it's been upgraded to v3 rollback and so that's dead in the water too.
3) I'm also going to assume that if the board has been replaced and hopefully is one made in 2016 (with a 6xx serial number) then it could last a while but there's no guarantee of it. I've seen people say the 6xx versions have not failed but then I find a post or two from someone that claims to know someone with a 6xx model and it failed at least once on them but I can't get any actual verification on it, that's just hearsay to me if there's no direct proof so all I can do is continue hoping it's a 6xx revision board and that it's not going to fail anytime soon.
This will be my second G4, had a Sprint variant last year and never had problems with it, sold it to a gent from Australia when he visited Las Vegas and as far as I know he's still using it, who knows.
If anyone can offer some info related to those questions I'd be grateful so thanks in advance if anyone can.
Have fun, always...
EDIT:
Seems that if I get very lucky and the replacement board comes with H81020n on it - the original Marshmallow build - there's a chance I can roll it back to H81010o using the TOT method from the other thread for it, that would at least get me root potential I suppose. Guess I'll find out tomorrow if the replacement arrives. Can't find any absolutely verified info about later builds, looks like the very latest patch build is H81022b from September and I'm going to assume if that happens to be on the board then all hope is lost, basically. Ugh...
Click to expand...
Click to collapse
I haven't kept up with root, but I doubt anything MM latest or not you won't be able to root it. Also never flash wrong model firmware like the PR version. In the past that was a last resort firmware (before we got a back to stock for the actual AT&T model. You could get lucky but chances are you'll get a board with the latest or just the last previous firmware especially if it has a newer serial.
Pretty much the AT&T G4 is a device you want if you don't tinker with the device. I honestly love the G4, until certain apps even new apps ran worse on the G4 than they do on my G2.
Sent from my iPhone using Tapatalk
Just got the H810 back, checking on the board info here in a bit (if I can even detect anything) but it's running H81022b so I'm guessing that means I'm stuck with it as is but that was somewhat expected. I'm not going to even bother attempting a rollback at this point, will just wait for the yellow leather cover to arrive in the next few days then I'll put it up for sale on craigslist I suppose and go from there.
I have to wonder exactly what they did because the board info that I can detect using the LG Info tool from the Play Store still lists the same info for board date/etc (January 2016) so I don't know what the hell they actually did.
Kinda sucks but it's how things go sometimes.
So I had an interesting thing happen today. My phone's audio stopped working entirely. Any app that had or used sound causes my device to lock up entirely. Went through the standard steps, all the way to flashing back to stock, with the same issue. Called Google, and they informed me that it is 100% a hardware issue, and I need to RMA. Great. So I am in need of some advice. Since I have to send this to Google, I will want to be stock. I know that locking the bootloader is problematic, and will ultimately cause me to not be able to unlock. Should I lock the bootloader? It is going back to Google, but if they see it is a Verizon device with an unlocked bootloader, they may not like it. Also, while I know the people on XDA aren't mindreaders, maybe someone else will have dealt with this. What are the odds of getting a device with an exploitable build? Has anyone gotten a replacement from Google, and if so, what build was it running? I know I shouldn't expect to be able to unlock, but I can hope.
You have to wipe the device anyways and send it in. So why not just take the extra minute to lock the bootloader as a precautionary step?
dymmeh said:
You have to wipe the device anyways and send it in. So why not just take the extra minute to lock the bootloader as a precautionary step?
Click to expand...
Click to collapse
The only thing I am worried about is if something happens before locking. I know that locking the bootloader has been heavily advised against by beaups, and I just don't want anything to happen during the locking process.
stompysan said:
So I had an interesting thing happen today. My phone's audio stopped working entirely. Any app that had or used sound causes my device to lock up entirely. Went through the standard steps, all the way to flashing back to stock, with the same issue. Called Google, and they informed me that it is 100% a hardware issue, and I need to RMA. Great. So I am in need of some advice. Since I have to send this to Google, I will want to be stock. I know that locking the bootloader is problematic, and will ultimately cause me to not be able to unlock. Should I lock the bootloader? It is going back to Google, but if they see it is a Verizon device with an unlocked bootloader, they may not like it. Also, while I know the people on XDA aren't mindreaders, maybe someone else will have dealt with this. What are the odds of getting a device with an exploitable build? Has anyone gotten a replacement from Google, and if so, what build was it running? I know I shouldn't expect to be able to unlock, but I can hope.
Click to expand...
Click to collapse
Dealing with this exact problem right now on my wife's Verizon Pixel.
It was bootloader unlocked and rooted, but still auto updated for the Feb update. Soon after, audio broke just as you described. I was able to get it back working for a little bit after a couple factory image flashes, but it broke again for good.
I contacted Google and they set me up with an RMA. I flashed an exploitable factory image, relocked the bootloader, and sent it in last Wednesday. The replacement should be delivered tomorrow. I'm really hoping it was on the shelf at Google since launch and depixel. The phone was useless otherwise, so I had no choice but to send it back. I wish they'd just send me a non-Verizon.
"Your replacement Pixel Phone Silver 32 GB (Verizon) was shipped on February 20, 2017 via FXG"
I'll try to update after the replacement comes tomorrow.
jsbeagle said:
Dealing with this exact problem right now on my wife's Verizon Pixel.
It was bootloader unlocked and rooted, but still auto updated for the Feb update. Soon after, audio broke just as you described. I was able to get it back working for a little bit after a couple factory image flashes, but it broke again for good.
I contacted Google and they set me up with an RMA. I flashed an exploitable factory image, relocked the bootloader, and sent it in last Wednesday. The replacement should be delivered tomorrow. I'm really hoping it was on the shelf at Google since launch and depixel. The phone was useless otherwise, so I had no choice but to send it back. I wish they'd just send me a non-Verizon.
"Your replacement Pixel Phone Silver 32 GB (Verizon) was shipped on February 20, 2017 via FXG"
I'll try to update after the replacement comes tomorrow.
Click to expand...
Click to collapse
I went ahead and did the same thing. Let me know what build your replacement is. I still have my fingers crossed.
They all say they're Verizon models but almost everyone on this forum who has done this got a Google Play edition (it just has a Verizon SIM).
When I went through it, they said locking the bootloader was not necessary. Also, I got a brand new device with all accessories but they told me not to send the accessories in since I'd only be getting a phone back. Great experience for me. Props to Google for great service.
stompysan said:
I went ahead and did the same thing. Let me know what build your replacement is. I still have my fingers crossed.
Click to expand...
Click to collapse
YES!!!!!
Replacement Pixel just delivered. Appears to be brand new. All accessories included (they told me to only return the phone)
Verizon SIM was installed (I removed before booting it up).
Android Version 7.1
October 5 security patch
Build NDE63P
OEM unlocking toggle was greyed out until I connected to wifi, then I was able to toggle it to allow the bootloader to be unlocked. It does appear to be a google play edition in every way except the sim card that is included.
This is awesome. I'm now jealous of my wife and her non Verizon version. (We both still have the old grandfathered unlimited data and used the best buy trick to get Pixels on subsidized upgrades)
PsiPhiDan said:
They all say they're Verizon models but almost everyone on this forum who has done this got a Google Play edition (it just has a Verizon SIM).
When I went through it, they said locking the bootloader was not necessary. Also, I got a brand new device with all accessories but they told me not to send the accessories in since I'd only be getting a phone back. Great experience for me. Props to Google for great service.
Click to expand...
Click to collapse
jsbeagle said:
YES!!!!!
Replacement Pixel just delivered. Appears to be brand new. All accessories included (they told me to only return the phone)
Verizon SIM was installed (I removed before booting it up).
Android Version 7.1
October 5 security patch
Build NDE63P
OEM unlocking toggle was greyed out until I connected to wifi, then I was able to toggle it to allow the bootloader to be unlocked. It does appear to be a google play edition in every way except the sim card that is included.
This is awesome. I'm now jealous of my wife and her non Verizon version. (We both still have the old grandfathered unlimited data and used the best buy trick to get Pixels on subsidized upgrades)
Click to expand...
Click to collapse
You have no idea how excited this makes me. I have been extremely worried, but looks like I didn't need to be. Thanks!
stompysan said:
You have no idea how excited this makes me. I have been extremely worried, but looks like I didn't need to be. Thanks!
Click to expand...
Click to collapse
For the record, the only person who got a Verizon model still was able to unlock the bootloader (it was a new device with old 7.1 software) using dePixel8 so I think you're set regardless! Google is good!
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
UnusualSuspect said:
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
Click to expand...
Click to collapse
I got a Verizon version in January and it had an issue I haven't seen too many have, but it was audio related and apparently a hardware defect: mine had awful sound through the headphone jack only. Sounded like hissing and scratching beneath all the music. As if you didn't have the connection tight (but I did). Got the replacement and all is well!
UnusualSuspect said:
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
Click to expand...
Click to collapse
Mine was ordered through Verizon on November 12, and shipped the next day. I am going to assume that it was a launch device.
Mine was purchased from bestbuy.com in mid November. It actually shipped from a local Best Buy store.
I believe there is a bad batch of pixels. I'm currently on my second one.
A couple weeks ago my pixel crashed and shutdown and well never turned on again. Basically the phone was bricked. Idk how or why. I was running perfectly and I only had the bootloader unlocked.
Long story short. I contacted my provider (Project Fi) and they sent me a new one. Received it the next day. (Great customer service!!)
So yes I believe there is a bad batch of pixels out there.