Related
So I was on my moto g which I see the update icon. Two minutes later a image came with update. I clicked no thanks and didn't mange to read it fully anyone else had this
It's an update to fix some 4.4.2 bugs. I got it on my UK Moto G.
Sent from my XT1032 using XDA Premium 4 mobile app
rec71 said:
It's an update to fix some 4.4.2 bugs. I got it on my UK Moto G.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tesco?
King p1n said:
Tesco?
Click to expand...
Click to collapse
No. SIM free from Amazon UK.
Sent from my XT1032 using XDA Premium 4 mobile app
King p1n said:
Tesco?
Click to expand...
Click to collapse
Yeah mine is Tesco Moto G and I just got the update alert and have installed it.
spannerz said:
Yeah mine is Tesco Moto G and I just got the update alert and have installed it.
Click to expand...
Click to collapse
Thanks mine should come through soon
Can't force search keep getting crap about data connection
Sent from my XT1032 using Tapatalk
Just got my phone updated, now the phone keeps rebooting every 10 seconds when its loaded to GUI.
Tesco phone 8GB with stock image
Had recovery modified to gain root access
Can anyone shed some light please? :crying:
I've got CWM installed, and wonder if there is any patch that can fix the reboots issue?
kket said:
Just got my phone updated, now the phone keeps rebooting every 10 seconds when its loaded to GUI.
Tesco phone 8GB with stock image
Had recovery modified to gain root access
Can anyone shed some light please? :crying:
Click to expand...
Click to collapse
I think mines abut slower. . Stuff this stupid update
Krisshp said:
I think mines abut slower. . Stuff this stupid update
Click to expand...
Click to collapse
Damn, mine is updating right now :s
Can't notice any difference regarding performance. Will try the incall volume soon. My Moto G was one of the affecteds...
kket said:
Just got my phone updated, now the phone keeps rebooting every 10 seconds when its loaded to GUI.
Tesco phone 8GB with stock image
Had recovery modified to gain root access
Can anyone shed some light please? :crying:
I've got CWM installed, and wonder if there is any patch that can fix the reboots issue?
Click to expand...
Click to collapse
Having literally the exact same problem. Would love some help
Mine is 16gb from Meteor, rooted
Had the same problem my solution is during the reboot plug in the usb cable press volum down power to get into the motorola bootloader thingy (unsure what it called)
Then use fastboot on my computer to erase the update since for me the update was in the cache I just use
fastboot erase cache
reboot and it solve the problem
dptran said:
Had the same problem my solution is during the reboot plug in the usb cable press volum down power to get into the motorola bootloader thingy (unsure what it called)
Then use fastboot on my computer to erase the update since for me the update was in the cache I just use
fastboot erase cache
reboot and it solve the problem
Click to expand...
Click to collapse
I can confirmed that dptran method worked fine on mine!
I've used CWM to clear/wipe cache, and reboot.
Thanks! :good:
kket said:
I can confirmed that dptran method worked fine on mine!
I've used CWM to clear/wipe cache, and reboot.
Thanks! :good:
Click to expand...
Click to collapse
So do we need to unroot + stock recovery to update? Kinda a hassle for me since I'm busy with work and school >.<
Sent from my XT1034 using xda app-developers app
dptran said:
Had the same problem my solution is during the reboot plug in the usb cable press volum down power to get into the motorola bootloader thingy (unsure what it called)
Then use fastboot on my computer to erase the update since for me the update was in the cache I just use
fastboot erase cache
reboot and it solve the problem
Click to expand...
Click to collapse
Cheers buddy
Go to cache with root explorer and remove the update file
Yep, u hav to hav stock recovery, stock kernel to not go into bootloop
Sent from my Moto G using XDA Premium 4 mobile app
They accidentally sent me lollipop.
kket said:
I can confirmed that dptran method worked fine on mine!
I've used CWM to clear/wipe cache, and reboot.
Thanks! :good:
Click to expand...
Click to collapse
CWM wipe cache worked fine on me.
poweroff phone before it starts booting then power+vol down and went to cwm to wipe
Hello guys,
Is there anyway that to disable the update message reminder keep pooping up every an hour?
or
Is there an easy way to update the phone without wiping the phone (unroot + stock image) and install the update... ?
Thanks
Anyone having similar problem issue? and how did you go about it?
I think my nexus 5 is hardbricked doing a paanodandroid ota update
This happened on latest paranoid android + latest franco kernel + TWRP
I wanted to update pa gapps (first 2 downloads md5 checksum failed, third time it worked) and when the phone booted afterwards, systemui failed and I couldn't do anything. I Thought this wasn't a big problem since the phone managed to boot. I long pressed the power button to shut it down so I could boot into recovery to restore my backup I had recently made. When I tried to boot into recovery it wouldn't do anything. Not boot into recovery and not into fastboot. How is this even possible by simply flashing gapps?
What should I do?
I've tried all the button combinations for more than 15 seconds.
michaelsplus said:
I think my nexus 5 is hardbricked doing a paanodandroid ota update
This happened on latest paranoid android + latest franco kernel + TWRP
I wanted to update pa gapps (first 2 downloads md5 checksum failed, third time it worked) and when the phone booted afterwards, systemui failed and I couldn't do anything. I Thought this wasn't a big problem since the phone managed to boot. I long pressed the power button to shut it down so I could boot into recovery to restore my backup I had recently made. When I tried to boot into recovery it wouldn't do anything. Not boot into recovery and not into fastboot. How is this even possible by simply flashing gapps?
What should I do?
I've tried all the button combinations for more than 15 seconds.
Click to expand...
Click to collapse
Have you tried powering it on again mine sometimes won't bit straight away after long pressing power button but works after 5-10 mins
Sent from my Nexus 5 using Tapatalk
kevtrysmoddin said:
Have you tried powering it on again mine sometimes won't bit straight away after long pressing power button but works after 5-10 mins
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes I've tried it a few times already the last 45 minutes
michaelsplus said:
Yes I've tried it a few times already the last 45 minutes
Click to expand...
Click to collapse
I take it that it doesn't respond in any way to the charger or p.c.
Sent from my Nexus 5 using Tapatalk
kevtrysmoddin said:
I take it that it doesn't respond in any way to the charger or p.c.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Indeed it doesn't . The pc only recognizes it's an unknown usb device
michaelsplus said:
Indeed it doesn't . The pc only recognizes it's an unknown usb device
Click to expand...
Click to collapse
You could have a faulty memory issue
Sent from my Nexus 5 using Tapatalk
So, at this point it doesn't boot at all? Do you have a link to the gapps you flashed?
Sent from my Nexus 5 using XDA Free mobile app
michaelsplus said:
Indeed it doesn't . The pc only recognizes it's an unknown usb device
Click to expand...
Click to collapse
If you plug the N5 when he's off, do you see any led?
jd1639 said:
So, at this point it doesn't boot at all? Do you have a link to the gapps you flashed?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't boot at all no.
It was downloaded through the paranoid android OTA app. It was the 20140531 version: http://goo.im/devs/paranoidandroid/roms/gapps
OverSpeed301 said:
If you plug the N5 when he's off, do you see any led?
Click to expand...
Click to collapse
No. No activity whatsoever.
michaelsplus said:
It doesn't boot at all no.
It was downloaded through the paranoid android OTA app. It was the 20140531 version: http://goo.im/devs/paranoidandroid/roms/gapps
No. No activity whatsoever.
Click to expand...
Click to collapse
I think it was just a coincidence that it failed after flashing gapps. I'd RMA it. Sounds like the emmc went bad. It's happened on a few n5's.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I think it was just a coincidence that it failed after flashing gapps. I'd RMA it. Sounds like the emmc went bad. It's happened on a few n5's.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Will they help me out when the bootloader was unlocked and a custom rom and kernel installed?
michaelsplus said:
Will they help me out when the bootloader was unlocked and a custom rom and kernel installed?
Click to expand...
Click to collapse
If it doesn't boot who will know? Google's pretty cool about RMA's
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If it doesn't boot who will know? Google's pretty cool about RMA's
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That's a bit good news . Thank you
As i mentioned I managed to boot once into the (not working) rom after the (corrupted I think) gapps package had been installed, does that mean that the gapps file cannot have messed up the bootloader since I already managed to boot once after installing the package?
michaelsplus said:
That's a bit good news . Thank you
As i mentioned I managed to boot once into the (not working) rom after the (corrupted I think) gapps package had been installed, does that mean that the gapps file cannot have messed up the bootloader since I already managed to boot once after installing the package?
Click to expand...
Click to collapse
I just think it was a coincidence that your memory went bad after you flashed. Out would have happened even of you didn't flash the gapps. That's my theory anyway
Sent from my Nexus 5 using XDA Free mobile app
michaelsplus said:
I think my nexus 5 is hardbricked doing a paanodandroid ota update
This happened on latest paranoid android + latest franco kernel + TWRP
I wanted to update pa gapps (first 2 downloads md5 checksum failed, third time it worked) and when the phone booted afterwards, systemui failed and I couldn't do anything. I Thought this wasn't a big problem since the phone managed to boot. I long pressed the power button to shut it down so I could boot into recovery to restore my backup I had recently made. When I tried to boot into recovery it wouldn't do anything. Not boot into recovery and not into fastboot. How is this even possible by simply flashing gapps?
What should I do?
I've tried all the button combinations for more than 15 seconds.
Click to expand...
Click to collapse
Don't send it to an RMA follow this guide. BSOD/NoBootloader
This is a guide I created following the exact same issue you had. If THIS doesn't work then send it in to RMA
wolfirotisha said:
Don't send it to an RMA follow this guide. BSOD/NoBootloader
This is a guide I created following the exact same issue you had. If THIS doesn't work then send it in to RMA
Click to expand...
Click to collapse
Saw your guide, and thanks for it. But if the device doesn't boot it won't get into the alternate bootloader
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Saw your guide, and thanks for it. But if the device doesn't boot it won't get into the alternate bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Does the PC detect it when plugged in? If so then its not hardbricked.
If you have hangouts I can try to help better.
---------- Post added at 02:14 AM ---------- Previous post was at 02:02 AM ----------
And should my guide fail there is always this one. LG FlashTool
wolfirotisha said:
Does the PC detect it when plugged in? If so then its not hardbricked.
If you have hangouts I can try to help better.
---------- Post added at 02:14 AM ---------- Previous post was at 02:02 AM ----------
And should my guide fail there is always this one. LG FlashTool
Click to expand...
Click to collapse
Thank you. I tried both these guides but none of them worked. I can't get any life in the device.
The PC ony recognizes it as 'unknown usb device'
so i was on cataclysm from the beginning and everything worked great. I flashed stock 4.4.4 cause i want to use just xposed with a nice vanilla rom. everything works great except i cant get or place calls. i have sprint lte full bars, can get data and everything send texts/mms, go on facebook, dl stuff, just no calls. wifi or not doesnt matter either. everytime i try to place one it just sits on dialing and i lose all bars and then says can t make call, no connection. once i hang up the bars and lte come back.
I have noticed my network ends up on global sometimes instead of LTE but even when i switch it to LTE it still doesnt work. i have updated prl and profile too. Any ideas? thanks
EDIT: yeah i still cant seem to fix it. I was going to go back to a 4.4.2 rom but for some reason it fails in twrp everytime now... :/ but this is the exact problem i am having in this thread https://productforums.google.com/forum/#!topic/nexus/Or6_6zCtBwc
seems like it might be sprints fault
Did you wipe?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Did you wipe?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yep cache, dalvik, data. never had this problem with any other roms before? might it be a 4.4.4 issue? cataclysm was 4.4.2
fergdizzle9090 said:
yep cache, dalvik, data. never had this problem with any other roms before? might it be a 4.4.4 issue? cataclysm was 4.4.2
Click to expand...
Click to collapse
did you update the bootloader and radio?
Zepius said:
did you update the bootloader and radio?
Click to expand...
Click to collapse
no i did not, just twrp. would that be the problem?
possibly. you should do it to be safe.
Zepius said:
possibly. you should do it to be safe.
Click to expand...
Click to collapse
do you have to do it when you upgrade android versions? is there any quick link you can post to help me out with it? im not all that familiar with updating those. Ill search around and see what I can find. thanks for the suggestion though
Im thinking about RMAing my nexus 5 though because the power button is very loose and rattles loudly when i tap the screen, dont want a crappy refurb in place of my mint pristine nexus though :/ lol
Rma is always new
Sent from my Nexus 5 using Tapatalk
rootSU said:
Rma is always new
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
oh i didnt know that. well great thanks. Ill give the updates a shot and consider the rma more now i know ill be getting a new phone. just dont want to be without it for a while lol
yeah i still cant seem to fix it. I was going to go back to a 4.4.2 rom but for some reason it fails in twrp everytime now... :/ but this is the exact problem i am having in this thread https://productforums.google.com/fo...ce=footer#!msg/nexus/Or6_6zCtBwc/j5CP8vy4jGAJ
Install 4.4.4 using fastboot. And after make sure you are using the latest version of twrp.
Lokke9191 said:
Install 4.4.4 using fastboot. And after make sure you are using the latest version of twrp.
Click to expand...
Click to collapse
ill have to look up some stuff on fastboot and recovery updates. been a while since ive done anything out of recovery
fergdizzle9090 said:
ill have to look up some stuff on fastboot and recovery updates. been a while since ive done anything out of recovery
Click to expand...
Click to collapse
Section 3 #1 and Section 4 #1
[Resource] All Guides and Info Threads
Lethargy said:
Section 3 #1 and Section 4 #1
[Resource] All Guides and Info Threads
Click to expand...
Click to collapse
oh yeah ok thanks. so you are suggesting just completely restarting and rerooting from absolute stock?
fergdizzle9090 said:
oh yeah ok thanks. so you are suggesting just completely restarting and rerooting from absolute stock?
Click to expand...
Click to collapse
Personally I would flash the factory images again just to rule out software being the issue, if it still happens then I guess RMA or whatever.
Lethargy said:
Personally I would flash the factory images again just to rule out software being the issue, if it still happens then I guess RMA or whatever.
Click to expand...
Click to collapse
yeah i'll give that a try. weird thing is this happened only after i flashed 4.4.4 from cataclysm 4.4.2. i am waiting to hear if an RMA fixes the issue since someone else is already going that route. it sounds to me like it might be sprint
fergdizzle9090 said:
yeah i'll give that a try. weird thing is this happened only after i flashed 4.4.4 from cataclysm 4.4.2. i am waiting to hear if an RMA fixes the issue since someone else is already going that route. it sounds to me like it might be sprint
Click to expand...
Click to collapse
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Lokke9191 said:
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Click to expand...
Click to collapse
thanks ill try it out when i got a spare moment. now that im thinking of it this all happened after i updated twrp, so could that be the root of all this you think? because i used the twrp app to update it instead of flashing, and i noticed it has been acting extremely weird lately.
You might check your APN settings. I had issues with MMS after flashing 4.4.4.
hsas.69 said:
You might check your APN settings. I had issues with MMS after flashing 4.4.4.
Click to expand...
Click to collapse
ill look into it. people who have this problem said its not the apn though because i get data just fine and i can recieve calls. its only when i am placing a call it goes crazy and disconnects me
EDIT: so anyone know how to get to apn for sprint? its not under mobile networks. is it buried in a dialer menu or something?...
Lokke9191 said:
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Click to expand...
Click to collapse
well full reflash of 4.4.4 stock from google through fastboot didnt work :/ i noticed also that it hasnt been connecting during initial setup, i have to connect to wifi. think my phone might be borked :crying:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Mystical_Titan said:
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
rootSU said:
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
Click to expand...
Click to collapse
Thanks for the fast response. :good:
Mystical_Titan said:
Thanks for the fast response. :good:
Click to expand...
Click to collapse
No probs. Sounds like the update got stuck at the bootloader flash and corrupted. It's probably not a fatal NAND issue, rather corrupt partition or two but it usually means sending it in.
You can try the LG flashtool as a last resort before doing so though, as you never know...
You can find a link to it in the sticky thread in my signature. Best to stay away from actual "toolkits" though and either use fastboot manually or LG flash tool, although fastboot probably cant help you here - just saying for future ref...
Mystical_Titan said:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
BruKnowsBest said:
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
Click to expand...
Click to collapse
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Mystical_Titan said:
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Click to expand...
Click to collapse
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
BruKnowsBest said:
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
Click to expand...
Click to collapse
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Mystical_Titan said:
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Click to expand...
Click to collapse
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I completely forgot that you mentioned the LG Flashtool, I feel like such an idiot. I'll try that tomorrow as a last resort.
No worries
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
BruKnowsBest said:
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
Click to expand...
Click to collapse
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
rootSU said:
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
Click to expand...
Click to collapse
oh ok, I misunderstood
rootSU said:
No worries
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It speaks about a KDZ file. What is it and where would I find it?
Mystical_Titan said:
It speaks about a KDZ file. What is it and where would I find it?
Click to expand...
Click to collapse
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
rootSU said:
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
Click to expand...
Click to collapse
Well, that's that. This phone is done.
Yup. RMA
Sent from my Nexus 5 using Tapatalk
Hello xda forum
I had got my nexus 5 off contract from California, USA and am using it in Delhi, India. I dont know if this fact is causing the problem or not, so thought i'd mention it..
So ..my device wasnt receiving the lollipop ota update so i did the clear google framework app data trick and got the update..
When the system reboots to install the lollipop it shows "error" like after 10-15℅ of completion. This was yesterday. So now i got the ota update without the clearing the data of google framework and the same problem persists. It just shows 'error' and i have to restart the phone by pressing lock and volume up key..
Help. Please.
Thanks in advance
Also it was earloer rooted with towelroot. But i did unroot it with superSu a couple of weeks before ..
What error is it giving you?
_MetalHead_ said:
What error is it giving you?
Click to expand...
Click to collapse
It just says error. But after a little digging i came to find that this is probably because i tweaked a few system files when i was rooted. Like the mixer_path... Now i cant seem to remember the changes i made neither can i find the oroginal file for nexus 5 stock on the net.. Could you or anyone please help.. Any advise
rahul9five said:
It just says error. But after a little digging i came to find that this is probably because i tweaked a few system files when i was rooted. Like the mixer_path... Now i cant seem to remember the changes i made neither can i find the oroginal file for nexus 5 stock on the net.. Could you or anyone please help.. Any advise
Click to expand...
Click to collapse
Google nexus factory images. Just to be sure flash the recovery, system, and boot images in fastboot from 4.4.4
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Google nexus factory images. Just to be sure flash the recovery, system, and boot images in fastboot from 4.4.4
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Will i have to unlock my bootloader for all this? As i rooted my phone with towelroot i didnt have to unlock it earlier
rahul9five said:
Will i have to unlock my bootloader for all this? As i rooted my phone with towelroot i didnt have to unlock it earlier
Click to expand...
Click to collapse
You do need an unlocked bootloader. Get bootunlocker from the play store it'll unlock without wiping the device.
Sent from my Nexus 9 using XDA Free mobile app