Database Info

Droid maxx update failure?

So I took the Droid Maxx update, while I had PwnMyMoto installed. After the reboot I got a message that read "system update failed". However if I go into settings>about phone and check my version of the software, it's the same as the update.
Also there was a Google Play update for the camera app that was not available to me before the software update. Can anyone provide any insight into what might be going on?
Sent from my XT1080 using Tapatalk

blue26 said:
So I took the Droid Maxx update, while I had PwnMyMoto installed. After the reboot I got a message that read "system update failed". However if I go into settings>about phone and check my version of the software, it's the same as the update.
Also there was a Google Play update for the camera app that was not available to me before the software update. Can anyone provide any insight into what might be going on?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I had the same issue, but now my phone is power cycling and I can't get it to stop. My fault for not unrooting, I know, but if anyone has insight on how to fix this, it'd be appreciated.

gamerman623 said:
I had the same issue, but now my phone is power cycling and I can't get it to stop. My fault for not unrooting, I know, but if anyone has insight on how to fix this, it'd be appreciated.
Click to expand...
Click to collapse
You may have to FXZ via means of HouseofMoto
It'll bring you back to stock though, but sometimes you can keep data
HouseofMoto

Kickbut101 said:
You may have to FXZ via means of HouseofMoto
It'll bring you back to stock though, but sometimes you can keep data
Click to expand...
Click to collapse
Thank you so much! Problem resolved! I used HouseofMoto and kept all my data. Worked like a charm. You're my hero.

Yeah I was working and it auto updated didn't give me an option and bam power cycles non stop, doing the House of Moto deal now, hopefully I can fix it. Rather annoying.

... And bootloops for all!
My wife and I have Maxxs. We both received the update overnight and, like dummies, went for it without unrooting. Now it's bootloop city for both of us.
Time to head on down to HouseofMoto for some help. D'oh!
---------- Post added at 05:24 AM ---------- Previous post was at 05:08 AM ----------
chewybang said:
My wife and I have Maxxs. We both received the update overnight and, like dummies, went for it without unrooting. Now it's bootloop city for both of us.
Time to head on down to HouseofMoto for some help. D'oh!
Click to expand...
Click to collapse
Can someone post the HouseofMoto files here or private msg me a link to them? I can't seem to register to HouseofMoto right now (already tried twice)
Thanks in advance!

What's the word on having root after the November update? Broken? Have to reinstall Pwn?
fat-fingered and Maxx-ed out.

Luckily I happened to glance down at my phone and see that it was downloading (I was driving home from work). I threw it into airplane mode, got home, and after some poking around on here, froze Updater and MotorolaOTA which stopped it (still shows "downloading" within the System Updates menu).
Now to wait a few days to see if there's an easy method to take the OTA, keep root while not somehow causing the death of small children or worse, me having to flash this thing completely and lose all my settings, etc.

TacticalFats said:
Luckily I happened to glance down at my phone and see that it was downloading (I was driving home from work). I threw it into airplane mode, got home, and after some poking around on here, froze Updater and MotorolaOTA which stopped it (still shows "downloading" within the System Updates menu).
Now to wait a few days to see if there's an easy method to take the OTA, keep root while not somehow causing the death of small children or worse, me having to flash this thing completely and lose all my settings, etc.
Click to expand...
Click to collapse
Your wait is over.
HouseofMoto will allow you to flash FXZ, keep settings and data and if you DL pwnmymoto BEFORE you accept the OTA, you can install it after the OTA. I haven't done the pwnmymoto trick but I hear it works and is easier than the rockmymoto process.

redddog said:
Your wait is over.
HouseofMoto will allow you to flash FXZ, keep settings and data and if you DL pwnmymoto BEFORE you accept the OTA, you can install it after the OTA. I haven't done the pwnmymoto trick but I hear it works and is easier than the rockmymoto process.
Click to expand...
Click to collapse
Thanks!

Reboot Cycle
Yeah, I ran into the same issue as I was rooted and accepted the OTA update which caused the reboot cycle. I didn't have Titanium Backup (like an idiot) but, through a number of reset cycles, I was able to download and install it in the 20 or so seconds I had before restart. I finally got back in and was able to disable/delete the OTA apk.

4.4 (V2) root still work using Jcase method?

Hey guys,
I apologize for making a new thread about this but I think some others may have this question too. So I received the second 4.4 OTA today and I'm curious if the Root exploit SlapMyMoto from Jcase will work with this new OTA? I do not know if it it is the same update as all it says it "Kitkat ... update (19.5.3.en.us)" nothing about 4.4 or 4.4.2. Thanks in advance for any input

it should...the actual OS update is the same as what we got in December.

dano1282 said:
it should...the actual OS update is the same as what we got in December.
Click to expand...
Click to collapse
for the VZW non Developer Edition right? I'm reading up on MotoWpNoMo and it references an unlocked bootloader.
Also can I do this method if I did RockMyMoto before MotoWpNoMo to gain root?

Have you already installed 4.4? If so, you're out of luck. The Moto X can be downgraded back to 4.2.2 but the DROID line can not.
Don't attempt to FXZ 4.2.2 or you'll have issues.
Sent from my XT1080 using xda app-developers app

If you follow jcase's instructions for SlapMyMoto I can verify it works. Did it this morning on my Maxx, but as stated earlier, you can not root if you've already updated to 4.4, and you can not go back to 4.2.2. If I'm remembering correctly, the basic process was: from 4.2.2, root, permanently remove write protection, go back to stock 4.2.2 (after camera update), then SlapMyMoto.

osucowboy96 said:
If you follow jcase's instructions for SlapMyMoto I can verify it works. Did it this morning on my Maxx, but as stated earlier, you can not root if you've already updated to 4.4, and you can not go back to 4.2.2. If I'm remembering correctly, the basic process was: from 4.2.2, root, permanently remove write protection, go back to stock 4.2.2 (after camera update), then SlapMyMoto.
Click to expand...
Click to collapse
here's what i've done so far. rooted using RockMyMoto AFTER camera update. Still on 4.2.2 I do not know how to remove the Write protection because I tried using MotoWpNoMo and I keep getting a "1". Also, What do you mean by "go back to stock" after removing Wp?

Carrzy said:
here's what i've done so far. rooted using RockMyMoto AFTER camera update. Still on 4.2.2 I do not know how to remove the Write protection because I tried using MotoWpNoMo and I keep getting a "1". Also, What do you mean by "go back to stock" after removing Wp?
Click to expand...
Click to collapse
keep hammering it with MotoWpNoMo. You have to get that to work and must get write protection off (0). Took several tries on mine to get it to work. Make sure you are running it with admin priv and all your antivirus etc is off and are following directions exactly.
back to stock means after you have done the above, reflash 4.2.2 camera update (15.15) to REMOVE root and get it back to a stock build.
Then do the SlapMyMoto steps 1-3, then take 4.4 update, then finalize Slap steps.

jkhouw1 said:
keep hammering it with MotoWpNoMo. You have to get that to work and must get write protection off (0). Took several tries on mine to get it to work. Make sure you are running it with admin priv and all your antivirus etc is off and are following directions exactly.
back to stock means after you have done the above, reflash 4.2.2 camera update (15.15) to REMOVE root and get it back to a stock build.
Then do the SlapMyMoto steps 1-3, then take 4.4 update, then finalize Slap steps.
Click to expand...
Click to collapse
In addition, when I did MotoWpNoMo the first time, I noticed it was asking for root access on my phone and I had to unlock my phone and give it access. The first time failed, I believe, due to not immediately having root access (I got a line with like 4-5 "T"s followed by either a bunch of dashes or asterisks, then next line was "Press Enter to exit" or something similar). The second time I ran it, since it now had root access, it ran like a charm.
To get back to 12.15.15 after removing write protection, I used HouseOfMoto, keeping data. Some prefer a full wipe.
Good luck, and if you run into any other issues I'll help any way I can. No expert, but I'll offer what limited advice I can.

osucowboy96 said:
In addition, when I did MotoWpNoMo the first time, I noticed it was asking for root access on my phone and I had to unlock my phone and give it access. The first time failed, I believe, due to not immediately having root access (I got a line with like 4-5 "T"s followed by either a bunch of dashes or asterisks, then next line was "Press Enter to exit" or something similar). The second time I ran it, since it now had root access, it ran like a charm.
To get back to 12.15.15 after removing write protection, I used HouseOfMoto, keeping data. Some prefer a full wipe.
Good luck, and if you run into any other issues I'll help any way I can. No expert, but I'll offer what limited advice I can.
Click to expand...
Click to collapse
I gave it root access but I still get the T's and asterisks. I'll keep trying tho and I appreciate the help guys

Alright so I was able to disable Write protection successfully but now I don't know how to to create and FXZ file for House Of Moto (steps, 3,4 & 5)

[Q] Unable to get back to stock

I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.

Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.

Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
If s off you can use the newest one. You don't need to the one below. Use the newest ruu and use the SD card method/option.
jsaxon2 said:
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Click to expand...
Click to collapse

TWRP & Flashify work with this?
Sorry for my noobie question, but I rooted back in April with WeakSauce & TWRP and also installed Flashify. I am fuzzy on what I did and now, I am afraid of bricking my phone through ignorance.
Can I use these files to upgrade to 4.4.3 on my Verizon HTC One M8? If so, what is the most straightforward way to do this? Can I use Flashify or TWRP to load the OP6ZBIMG.ZIP file?
Thanks

I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-return-htc-one-m8-verizon-to-stock-s-on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.

nraines said:
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.

dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.

nraines said:
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
Click to expand...
Click to collapse
Do not take ota. What was the sunshine prob?

dottat said:
Do not take ota. What was the sunshine prob?
Click to expand...
Click to collapse
It force closes during the initial check.

nraines said:
It force closes during the initial check.
Click to expand...
Click to collapse
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?

dottat said:
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
Click to expand...
Click to collapse
Incoming PM

back to stock
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks

empty_cups said:
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
Click to expand...
Click to collapse
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.

unroot
dottat said:
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
Click to expand...
Click to collapse
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?

empty_cups said:
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
Click to expand...
Click to collapse
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845

not working
dottat said:
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
Click to expand...
Click to collapse
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?

Done
empty_cups said:
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Click to expand...
Click to collapse
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.

empty_cups said:
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
Click to expand...
Click to collapse
Since you are s off you can take the ota and then flash twrp and flash su. Easiest way...

nraines said:
I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.

jkeirnan87 said:
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
Click to expand...
Click to collapse
You are s on too right? If so I don't have an option for you yet. Your system files are write protected which means the most you can do is clear data for the app or factory reset. Are you using an SD card and if so does it make a difference which storage location you use?

AT&T H910 Update

My phone just got updated. Not sure what changed. I couldn't find any info online.
View attachment 3998431

Probably the security patch.

Taken from my 920

It brings us up to 10i where T-Mobile is currently at.

Ant way to block updates on a non rooted phone?

Could we possibly finally get a stock KDZ from this?

I froze that

jetracer said:
Ant way to block updates on a non rooted phone?
Click to expand...
Click to collapse
I installed FOTAKill.apk and have not been prompted about any update.
No root needed, just install like any other apk. I've been using it since I had my Epic 4G.....LoL...... I hate the pushy notices.
Edit: It failed this time.....I just got the update prompt

monke30butt said:
I installed FOTAKill.apk and have not been prompted about any update.
No root needed, just install like any other apk. I've been using it since I had my Epic 4G.....LoL...... I hate the pushy notices.
Click to expand...
Click to collapse
Can you link the apk. Can only seem to find old ones

haris163 said:
My phone just got updated. Not sure what changed. I couldn't find any info online.
View attachment 3998431
Click to expand...
Click to collapse
I got the notification for that but I haven't updated yet.
Did you willingly install the update or did it happen automatically? Can anyone confirm?
I need to know if I should be freaking out or not. I haven't rooted yet but now I think I'm running out of time and need to get it over with.
I have "Automatic system updates" turned off in Developer options. Am I safe?

ubergeek77 said:
I got the notification for that but I haven't updated yet.
Did you willingly install the update or did it happen automatically? Can anyone confirm?
I need to know if I should be freaking out or not. I haven't rooted yet but now I think I'm running out of time and need to get it over with.
I have "Automatic system updates" turned off in Developer options. Am I safe?
Click to expand...
Click to collapse
I willingly let it install.

AT&T Forced this update on my phone
And am currently bootlooping into TWRP. ****. Anyone have any ideas?
---------- Post added at 04:36 PM ---------- Previous post was at 04:34 PM ----------
haris163 said:
I willingly let it install.
Click to expand...
Click to collapse
I'm currently on the NotSoStock modded rom with ATT variant, everytime the update goes to install it gets to the point where the phone goes to reboot and then boots into TWRP. Any ideas on what I should do?

mmarsie said:
I'm currently on the NotSoStock modded rom with ATT variant, everytime the update goes to install it gets to the point where the phone goes to reboot and then boots into TWRP. Any ideas on what I should do?
Click to expand...
Click to collapse
Sorry I don't know about that. My phone is pure stock.

mmarsie said:
And am currently bootlooping into TWRP. ****. Anyone have any ideas?
---------- Post added at 04:36 PM ---------- Previous post was at 04:34 PM ----------
I'm currently on the NotSoStock modded rom with ATT variant, everytime the update goes to install it gets to the point where the phone goes to reboot and then boots into TWRP. Any ideas on what I should do?
Click to expand...
Click to collapse
You should stop trying to install it
I've run into this before on other devices. Basically, the phone assumes you have the stock recovery installed, and attempts to run a command very specific to that recovery. Since you have TWRP, such a command is not compatible, and therefore nothing happens. If you were to look at the terminal output in TWRP, you should see something indicating that flashing the update failed.
But as a general rule of thumb, you should stay away from OTA updates when rooted. They are generally not compatible with or safe for rooted devices and custom ROMs. Even if the update were successful, it would unroot your device and patch the update that allowed you to obtain root, and you'd be stuck without root indefinitely.
So in your case, you need to freeze/uninstall "System Update" app (or whatever it's called) and wait for the maintainer of your ROM to include the changes in the next ROM update.
If you're still bootlooping, in TWRP's file manager, try looking for the update and deleting it. I think it may be in the /cache folder, but please do some research before you go deleting stuff at random. You may also try connecting it to adb, restarting in root mode, and running "adb uninstall com.lge.lgdmsclient," or "adb hide com.lge.lgdmsclient." Basically, you need to find a method of preventing the update from initiating automatically upon boot.

ubergeek77 said:
You should stop trying to install it
I've run into this before on other devices. Basically, the phone assumes you have the stock recovery installed, and attempts to run a command very specific to that recovery. Since you have TWRP, such a command is not compatible, and therefore nothing happens. If you were to look at the terminal output in TWRP, you should see something indicating that flashing the update failed.
But as a general rule of thumb, you should stay away from OTA updates when rooted. They are generally not compatible with or safe for rooted devices and custom ROMs. Even if the update were successful, it would unroot your device and patch the update that allowed you to obtain root, and you'd be stuck without root indefinitely.
So in your case, you need to freeze/uninstall "System Update" app (or whatever it's called) and wait for the maintainer of your ROM to include the changes in the next ROM update.
If you're still bootlooping, in TWRP's file manager, try looking for the update and deleting it. I think it may be in the /cache folder, but please do some research before you go deleting stuff at random. You may also try connecting it to adb, restarting in root mode, and running "adb uninstall com.lge.lgdmsclient," or "adb hide com.lge.lgdmsclient." Basically, you need to find a method of preventing the update from initiating automatically upon boot.
Click to expand...
Click to collapse
I initally declined the update when the notification came up, it is currently being forced down my throat lol. thank you for the info, I really hope i can get around this incredibly annoying issue.

mmarsie said:
I initally declined the update when the notification came up, it is currently being forced down my throat lol. thank you for the info, I really hope i can get around this incredibly annoying issue.
Click to expand...
Click to collapse
Did you have Developer Options enabled, and did you have "Automatic software updates" set to OFF in developer options?
I'm not rooted yet. I'm seriously scared right now that I'm going to auto update on next reboot. I'm doing everything I can to backup all my stuff and somehow safely do DirtySanta without being at risk of updating.

ubergeek77 said:
Did you have Developer Options enabled, and did you have "Automatic software updates" set to OFF in developer options?
I'm seriously scared right now that I'm going to auto update on next reboot. I'm doing everything I can to backup all my stuff and somehow safely do DirtySanta without being at risk of updating.
Click to expand...
Click to collapse
yes and yes to both your questions. this was a 100% forced update even though dev options and auto update was set to off

mmarsie said:
yes and yes to both your questions. this was a 100% forced update even though dev options and auto update was set to off
Click to expand...
Click to collapse
This is terrible.

ubergeek77 said:
This is terrible.
Click to expand...
Click to collapse
yeah I'm lived right now, currently with out a cellphone untill i test some of the above options another user posted. Here's hoping

Does anyone know whether a phone with this update can still use the dirtysanta exploit to root, or is that also broken by the security update?

[HELP?] Factory Reset on nougat now no keyboard

So, i got accepted to the nougat beta but i decided to hold off until later to install it. I finally decided to take the plunge and just to be sure i wiped my device and then installed it just to be sure that no problems arose.
After it installed i was greeted with the usual startup procedure but when it came to signing in there was no keyboard, only google voice typing which doesn't work for passwords. As a result i am now left with a phone with an unlocked bootloader and factory reset protection on without any way to get past setup (unless anyone knows a glitch/bug)
Any advice on the situation??

colliflower1107 said:
So, i got accepted to the nougat beta but i decided to hold off until later to install it. I finally decided to take the plunge and just to be sure i wiped my device and then installed it just to be sure that no problems arose.
After it installed i was greeted with the usual startup procedure but when it came to signing in there was no keyboard, only google voice typing which doesn't work for passwords. As a result i am now left with a phone with an unlocked bootloader and factory reset protection on without any way to get past setup (unless anyone knows a glitch/bug)
Any advice on the situation??
Click to expand...
Click to collapse
It happened the same to me!
I had to rollback to b131 and do the update again.
Check my thread here

ViCioPT said:
It happened the same to me!
I had to rollback to b131 and do the update again.
Check my thread here
Click to expand...
Click to collapse
Thank you SOOO much!!! It worked

colliflower1107 said:
Thank you SOOO much!!! It worked
Click to expand...
Click to collapse
No problem, just thank me pushing Thanks button on the thread
Enviado do meu FRD-L09 através de Tapatalk

That is strange. I wonder if this is due to a software issue.

ViCioPT said:
It happened the same to me!
I had to rollback to b131 and do the update again.
Check my thread here
Click to expand...
Click to collapse
Isn't it easier to just download an APK for a keyboard (E. g. Google keyboard, Swiftkey) and install that via ADB or push it to the phone and install it?

FreeLineTM said:
Isn't it easier to just download an APK for a keyboard (E. g. Google keyboard, Swiftkey) and install that via ADB or push it to the phone and install it?
Click to expand...
Click to collapse
I just installed a keyboard apk and it fixed that issue for me.

Similar issue
Just encountered a very similar problem, (sorry if I don't explain well enough, I'm a newbie with this stuff) with a uk L09 model.
I recently had to reinstall an app using adb due to compatibility issues preventing me from using it. due to a misunderstanding on my part, I believed I needed to install it to an external sd card, rather than the /sdcard/ directory, this came up with some errors that I'm still unsure of, specifically it claimed the sd card was read-only despite me still being able to conventionally copy a file onto it and then play it back, so I went about looking for how to make it writeable, all solutions to this pointed to rooting the phone, so I decided to try that, I got as far as unlocking the bootloader, and failed to flash, after much frustration, I re-read the original advice for the app and managed to install it successfully. because the original issue was resolved, I decided not to finish rooting as It turns out, I didn't need it.
The next day I went about trying to re-lock the bootloader, this worked, but when I hard reset it, it directs me through the login process, at which point, I cannot proceed because there is no keyboard available. I still have the default recovery, I can use fastboot but not regular adb, and I cannot get to settings. I tried unlocking again through fastboot, but it returned command not allowed, reading other guides, it seems my only option involves the rollback, but I don't currently have a microsd adapter to put files directly onto it without using the phone, I've ordered one, but I'm unsure if it will allow me to considering even fastboot continue returned (Remote: Command not allowed). so far I've had no luck in flashing anything, so I'm incredibly nervous that my phone's effectively bricked.
Thank you for reading

Rommco05 said:
If you have relocked bootloader can't fastboot and adb. Try download this zip. Make dload folder in root of your internal storage. Unzip files and pu to dload. Turn phone off and turn on with holding vol+/vol-/on,off buttons, this can may help
Click to expand...
Click to collapse
I can't access my phone's internal storage because it defaults to charge only, and does not allow me to change the access to enable file transfer because I cannot get past the login due to the lack of keyboard.

Rommco05 said:
So, anyway you will need sdcard
edit: u can't skip all settings?
Click to expand...
Click to collapse
No, it requires a google account which was previously synced, which I can't input, sadly. microsd reader has been ordered, will have to wait a little while though.