Develop Bugs

Why is that I can't use OTA to update my Nexus 7 2013?

I just got a message that I have an update for 4.4.4 on my nexus 7 2013 but when I updated and installed, i'm still 4.4.3.
I rooted by using Nexus Root Toolkit by WugFresh.
This happened for 4.4.3 as well from 4.4.2.

omgsy said:
I just got a message that I have an update for 4.4.4 on my nexus 7 2013 but when I updated and installed, i'm still 4.4.3.
I rooted by using Nexus Root Toolkit by WugFresh.
This happened for 4.4.3 as well from 4.4.2.
Click to expand...
Click to collapse
What does the error say? Unexpected contents somewhere in the system? Basically, being rooted has nothing to do with whether the OTA fails or not. It usually is due to the system being modified (having Xposed Installed, system apps deleted, etc.). When it's trying to update, it will tell you why it failed.

charesa39 said:
What does the error say? Unexpected contents somewhere in the system? Basically, being rooted has nothing to do with whether the OTA fails or not. It usually is due to the system being modified (having Xposed Installed, system apps deleted, etc.). When it's trying to update, it will tell you why it failed.
Click to expand...
Click to collapse
when it rebooted, it just took me to TWRP recovery mode screen and i just rebooted and nothing came up. Just 4.4.3 still.
I did delete system apps such as google plus and stuff like those and have Xposed installed.
Do i have to use factory images and flash it that way?
I did it that way for 4.4.3 from 4.4.2

omgsy said:
when it rebooted, it just took me to TWRP recovery mode screen and i just rebooted and nothing came up. Just 4.4.3 still.
I did delete system apps such as google plus and stuff like those and have Xposed installed.
Do i have to use factory images and flash it that way?
I did it that way for 4.4.3 from 4.4.2
Click to expand...
Click to collapse
Well, even if you were stock/rooted with TWRP recovery, it would fail if you try to update the normal way within Android because it is expecting to boot into stock recovery. Since you have a custom recovery, it doesn't do anything more than boot into recovery. You could flash the OTA zip using TWRP, but it would fail as you have deleted system apps and have Xposed installed. Xposed isn't that big of a deal, as you can just uninstall it from with the Xposed Framework installer, then update, then re-install Xposed without losing any settings. Since you deleted system apps, you could reinstall them individually. HOWEVER, it looks like the easiest thing to do is to flash the factory image like you did going from 4.4.2 to 4.4.3 (I assume you didn't flash userdata). Another thing to do would be to just flash the system image from the 4.4.3 factory image, then flash the OTA zip in TWRP. It's really just a matter of your preference. But any of those ways would work.

How to unlock bootloader ?

I want to flash cm 12 so I need to unlock the bootloader first. I tried the freegee apps but it said my device was not supported.
Sent from my LG-E988 using XDA Free mobile app

unlock e-980 bootloader
enricosr said:
I want to flash cm 12 so I need to unlock the bootloader first. I tried the freegee apps but it said my device was not supported.
Sent from my LG-E988 using XDA Free mobile app
Click to expand...
Click to collapse
Me too,
How do I get bootloader unlocked?

enricosr said:
I want to flash cm 12 so I need to unlock the bootloader first. I tried the freegee apps but it said my device was not supported.
Sent from my LG-E988 using XDA Free mobile app
Click to expand...
Click to collapse
If you're coming from stock KitKat, Freegee won't work; you need GPRO_Recovery.apk (can be found somewhere around forums) and root access; Install that recovery, reboot and update it immediately, via Freegee or by flashing newer TWRP (there is a thread for that too).
You can also return your phone back to Jellybean and start from there, Freegee will work without any problems and you'll get a healthy base (not prone to hardware wakelocks) to start from. I prefer doing that.

I have done it and my phone is currently using TWRP. But when I try to open the freegee app, it said "error! Exception thrown waiting for command to finish" and "error! Your aboot is not supported by loki on software version: e98820c"
Sent from my LG-E988 using XDA Free mobile app

enricosr said:
I have done it and my phone is currently using TWRP. But when I try to open the freegee app, it said "error! Exception thrown waiting for command to finish" and "error! Your aboot is not supported by loki on software version: e98820c"
Sent from my LG-E988 using XDA Free mobile app
Click to expand...
Click to collapse
Because it won't work on stock KitKat software without previously flashed recovery from the APK file, I don't know if it will work if you have flashed any other recovery after that because I never used KitKat as flashing base for my device (well, I did once and APK recovery + Freegee + updated recovery, PhilZ back then, worked). Also, if you have manually flashed any recovery other than Freegee's or from APK, you have newer version than that one available in those two apps.
If you already have TWRP, you're ready to roll

On JB, rooted & Freegee installed with which I installed CWM Recovery.
Does this mean the Bootloader is unlocked? How do I verify BL is unlocked? Can I verify with a command in Terminal Emulator? If so kindly post the command. Thanks

zapjb said:
On JB, rooted & Freegee installed with which I installed CWM Recovery.
Does this mean the Bootloader is unlocked? How do I verify BL is unlocked? Can I verify with a command in Terminal Emulator? If so kindly post the command. Thanks
Click to expand...
Click to collapse
Optimus G Pro has a "bypass", not an unlock. If you can boot into CWM, you're okay. Also, you should get "Secure boot error: Bootloade unlock" or something like that on logo screen.

Yes TY. I am ok & fooling around with CM-12.1. I think I flashed the wrong Gapps. I think I should have flashed arm64 instead of arm.
So at
https://forum.cyanogenmod.org/topic/78601-unfortunately-android-keyboard-aosp-has-stopped-problem/
I'm trying this now.
By HimalayanCoder
Reboot into recovery
Wipe Cache
Factory Reset
Wipe Dalvik Cache (under advanced)
Install zip from sdcard
chose CM 10.0.zip
reboot & first run
checked my keyboard and it was working fine
Rebooted into recovery again
Install zip from sd card
Installed gapps-jb-20121011.zip (check compatibility version here http://wiki.rootzwiki.com/Google_Apps)
Rebooted and life was normal again

zapjb said:
Yes TY. I am ok & fooling around with CM-12.1. I think I flashed the wrong Gapps. I think I should have flashed arm64 instead of arm.
Click to expand...
Click to collapse
Um, ARM64 is for 64bit CPUs, Optimus G Pro is 32bit

Yeah lol. Now that I'm remembering how to do this again. I just have to find a good ROM. Like to find the latest official 5-5.1? e980 ROM. I've looked. Everything seems to be tweaked.

So far only ROM running well (so far) or even installing is Cyanogen 10.2. So be it for now.

[Resolved]was stuck on sprint screen, then it got worse. any help please?

[RESOLVED THANKS SAMEP!!]
hello
Initially the phone was on 5.1.1 and rooted. I put TWRP on and it stopped at sprint spark screen. I pulled the battery then it wouldn't stop bootlooping. I went into TWRP and cleared cache, still looping, then i cleared dalvic cache, still looping. I tried to restore back to my backup, still bootlooping, then I did a factory reset, still bootlooping. Then I wiped everything and tried to flash a factory rom with TWRP but it will not read from a sd card I inserted and ODIN will not recognize it.
Is there anything I can do to recover this disaster? Thanks for any help.

mohamie said:
hello
Initially the phone was on 5.1.1 and rooted. I put TWRP on and it stopped at sprint spark screen. I pulled the battery then it wouldn't stop bootlooping. I went into TWRP and cleared cache, still looping, then i cleared dalvic cache, still looping. I tried to restore back to my backup, still bootlooping, then I did a factory reset, still bootlooping. Then I wiped everything and tried to flash a factory rom with TWRP but it will not read from a sd card I inserted and ODIN will not recognize it.
Is there anything I can do to recover this disaster? Thanks for any help.
Click to expand...
Click to collapse
Have you install the usb Samsung drivers on your computer?
Sent from my SM-N910P using JellyBombed Tapatalk 2

Possible explanation is that you rooted with Chainfire Auto Root then installed TWRP which promptly told you it didn't detect root and asked you allow TWRP to install SuperSU.
If that happened, it most likely happened again when you restored the backup. If that's happening, is the TWRP backup the rooted ROM that you just applied before TWRP? If both are true, try the backup again but don't allow TWRP to install SuperSU.
When restoring a backup to TWRP, it has to follow a directory to path similar to this using your recognized serial number:
/storage/extSdCard/TWRP/BACKUPS/117bdxxx/(specific-individual backup folder) but your TWRP folder can also be in internal memory.
If none of the above applies, reply with method used to root and which ROM or kernel and SuperSU you used to root.
Being that you applied TWRP after root, I'm guessing you rooted with CFAR which uses systemless root and TWRP currently doesn't detect it and thinks you're not rooted but following the prompt will mess it up. Chainfire says not to allow TWRP to install SuperSU if that applies... it's the option closer to center of TWRP recovery, not the bottom one.
Sent from my SM-N910P using Tapatalk

GhostAssassin said:
Have you install the usb Samsung drivers on your computer?
Click to expand...
Click to collapse
Thanks I should have included in my post that I have Kies 3 installed, which detected my phone before this problem. But now says it's a unsupported device.

samep said:
Possible explanation is that you rooted with Chainfire Auto Root then installed TWRP which promptly told you it didn't detect root and asked you allow TWRP to install SuperSU.
If that happened, it most likely happened again when you restored the backup. If that's happening, is the TWRP backup the rooted ROM that you just applied before TWRP? If both are true, try the backup again but don't allow TWRP to install SuperSU.
When restoring a backup to TWRP, it has to follow a directory to path similar to this using your recognized serial number:
/storage/extSdCard/TWRP/BACKUPS/117bdxxx/(specific-individual backup folder) but your TWRP folder can also be in internal memory.
If none of the above applies, reply with method used to root and which ROM or kernel and SuperSU you used to root.
Being that you applied TWRP after root, I'm guessing you rooted with CFAR which uses systemless root and TWRP currently doesn't detect it and thinks you're not rooted but following the prompt will mess it up. Chainfire says not to allow TWRP to install SuperSU if that applies... it's the option closer to center of TWRP recovery, not the bottom one.
Click to expand...
Click to collapse
That's exactly what happened. I rooted with something else, which showed SuperSU. But after I installed TWRP, I made a backup with TWRP of the stock rom that I rooted with Chainfire. TWRP said I wasn't rooted, so I clicked to root. That's when the problems started now that I'm thinking about it.

mohamie said:
That's exactly what happened. I rooted with something else, which showed SuperSU. But after I installed TWRP, I made a backup with TWRP of the stock rom that I rooted with Chainfire. TWRP said I wasn't rooted, so I clicked to root. That's when the problems started now that I'm thinking about it.
Click to expand...
Click to collapse
I think you can restore that backup and ignore the TWRP prompt by selecting the option mid-screen. It should boot.
Sent from my SM-N910P using Tapatalk

samep said:
I think you can restore that backup and ignore the TWRP prompt by selecting the option mid-screen. It should boot.
Click to expand...
Click to collapse
I wiped things to start over and now that backup is gone.

mohamie said:
I wiped things to start over and now that backup is gone.
Click to expand...
Click to collapse
You can flash a rooted ROM or flash the stock tar in Odin and root again.
Depends on your goal. With what you had, it appears your goal was staying mostly stock and possibly retaining OTA update capability with full un-root. Is that your goal? If so, you need to Odin OK1 stock which brings you back to ghost's question: can you Odin a stock tar?
Sent from my SM-N910P using Tapatalk

samep said:
You can flash a rooted ROM or flash the stock tar in Odin and root again.
Depends on your goal. With what you had, it appears your goal was staying mostly stock and possibly retaining OTA update capability with full un-root. Is that your goal? If so, you need to Odin OK1 stock which brings you back to ghost's question: can you Odin a stock tar?
Click to expand...
Click to collapse
You're very insightful I appreciate it. Yes I mainly wanted to stay close to stock but I wanted to try a couple roms. It doesn't matter to me if I have OTA update capability,
Odin says it's a unrecognized device.

mohamie said:
You're very insightful I appreciate it. Yes I mainly wanted to stay close to stock but I wanted to try a couple roms. It doesn't matter to me if I have OTA update capability,
Odin says it's a unrecognized device.
Click to expand...
Click to collapse
Are you sure you're not talking about KIES not recognizing your device?
I think you should consider trying those pre-rooted ROMs. Download to PC, place on extSdCard and flash with TWRP. You still have TWRP, right?
Sent from my SM-N910P using Tapatalk

samep said:
Are you sure you're not talking about KIES not recognizing your device?
I think you should consider trying those pre-rooted ROMs. Download to PC, place on extSdCard and flash with TWRP. You still have TWRP, right?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I'm sorry you're correct. Kies says it's an unsupported device. Odin does nothing when I plug the phone into usb. I tried putting a rom on a sd card and flashing it via TWRP but it will not read off of the sd card.

mohamie said:
I'm sorry you're correct. Kies says it's an unsupported device. Odin does nothing when I plug the phone into usb. I tried putting a rom on a sd card and flashing it via TWRP but it will not read off of the sd card.
Click to expand...
Click to collapse
At the top of the TWRP directory, you can scroll up and tap the top selection to to move up to upper directory like root. You're looking for ext_sdcard I believe. That should be where the ROM is unless you put the ROM in sub directory like download. Can you find it?
Sent from my SM-N910P using Tapatalk

samep said:
At the top of the TWRP directory, you can scroll up and tap the top selection to to move up to upper directory like root. You're looking for ext_sdcard I believe. That should be where the ROM is unless you put the ROM in sub directory like download. Can you find it?
Click to expand...
Click to collapse
Mine is external_sd, and when i click that it doesn't show anything. I tried sdcard as well but I think that is phone storage. Neither one shows anything in them.

mohamie said:
Mine is external_sd, and when i click that it doesn't show anything. I tried sdcard as well but I think that is phone storage. Neither one shows anything in them.
Click to expand...
Click to collapse
If you have your PC USB driver installed, boot into recovery, connect USB to PC, goto mounts on TWRP and enable MTP. Then you should see phone and card folders to move your ROM to.
If you use phone folder, don't wipe internal memory before flashing ROM.
Sent from my SM-N910P using Tapatalk

samep said:
If you have your PC USB driver installed, boot into recovery, connect USB to PC, goto mounts on TWRP and enable MTP. Then you should see phone and card folders to move your ROM to.
If you use phone folder, don't wipe internal memory before flashing ROM.
Click to expand...
Click to collapse
I only see a button that says Disable MTP

mohamie said:
I only see a button that says Disable MTP
Click to expand...
Click to collapse
I believe that means that MTP is enabled. It's a toggle.
Sent from my SM-N910P using Tapatalk

samep said:
I believe that means that MTP is enabled. It's a toggle.
Click to expand...
Click to collapse
So I should disable MTP?

mohamie said:
So I should disable MTP?
Click to expand...
Click to collapse
I enabled it and it auto clicked microsd, now I see the zip

mohamie said:
I enabled it and it auto clicked microsd, now I see the zip
Click to expand...
Click to collapse
I ticked the "verify zip" and it came back failed. Should I flash it withouth verifying?

mohamie said:
I ticked the "verify zip" and it came back failed. Should I flash it withouth verifying?
Click to expand...
Click to collapse
I believe that's checking for md5 hash in zip which most likely isn't there. You should check md5 with a md5 checker on your PC, most likely not TWRP. None of the ROM zips I'm aware of have the md5 included in the zip.
I believe you should uncheck that option in TWRP. Let it check checksum in for backup restore only.
BTW, I checked recovery for USB MTP on my PC. If I go toggling buttons like mount system and enable MTP and disable MTP, it eventually appears on PC USB devices. It's just slow to pop-up. Give it time. The toggle will display as disable MTP; that is the enabled indication.
Sent from my SM-N910P using Tapatalk

March 2016 Updates Bug

My recent apps button is no longer working. And when I go to Developer Options, I see Developer Options are not available for this user. Anyone else seeing that?

I installed MHC19J first and that was the incorrect version. I then flashed MMB29V and then the problems above started. I couldn't access quick menu, the recent apps button didn't work, and Developer Options showed as not available for this user. I just did a factory data reset and that seemed to get everything working again, but always a pain to have set everything up again! Damn Google! :-/

Probably due to you flashing the wrong image before flashing the correct one. Had no such problems after flashing this morning
Skickat från min Nexus 5X via Tapatalk

I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V

granets said:
I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V
Click to expand...
Click to collapse
Only do that if you are not rooted etc. If you use TWRP recovery and are not prompted for a password when booting into recovery, then you have the right image. It does work, the problem is trying to use Custom Recovery to flash SuperSU. Check that thread below.
https://www.reddit.com/r/nexus5x/comments/49e0ij/601_mhc19j/

I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.

no issues here on 19J. modified boot image here

bobby janow said:
I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.
Click to expand...
Click to collapse
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?

mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
I'm sorry I don't know. I haven't decrypted in quite some time now. I also haven't used xposed in a long time either. I don't ever format userdata or flash the userdata.img unless I absolutely have to. I'm encrypted, systemless, 2.68 SU and twrp 3.0. I'm leery to do anything now until twrp gets fixed for the J build. Although I might flash a J kernel via OTG if there comes one.

mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?

mickey4mice said:
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?
Click to expand...
Click to collapse
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk

i had some trouble so i clicked the flash all batch file. Anyone know how to root this build? i cant get super su zip file i transfer to show up in twrp. The file is there but twrp doesnt see it.

SlimSnoopOS said:
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.

Bump

Dominicano2 said:
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.
Click to expand...
Click to collapse
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu

Dominicano2 said:
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu
Click to expand...
Click to collapse
Sweet, glad you got that figured out

How is the new update in terms of making the phone better?

gvsukids said:
How is the new update in terms of making the phone better?
Click to expand...
Click to collapse
Seems like the lag pulling down the notification window that happened time to time is gone. Feels a little snappier but will need a week of up time to know for sure.
Notice that the "keep WiFi on during sleep" setting for "never" still doesn't work on the 5x. Also still have an audio bug that duplicates the source a second behind on Bluetooth when a notification is received which is disappointing.

Failed install of Android 7.1.2 - boot stuck on "Android"

I had CWM Recovery and an older cyanogenmod rom installed and I wanted to upgrade to 7.1.2 from here: https://forum.xda-developers.com/lg.../rom-android-7-0-nougat-20161008-r16-t3476750
I copied the rom to internal memory, rebooted into recovery, selected the rom file to install. It showed some messages about patching, then in a couple of minuted erred with smth like "Erro loki-ifying because of incompatible aboot image".
I then rebooted and now it boots and shows "ANDROID" and is stuck on it - looks like it partially updated the ROM and failed somewhere.
I am not sure what to do now - I tried to boot into recovery (Power off -> Hold Power + Vol down till menu shows) but it doesnt work - it keeps booting onto this stuck boot.
Any ideas?

As I understand it, being an amateur ROM flasher, all those 3rd party ROMs need a TWRP recovery to work. Provided your bootloader is unlocked, I'd flash the stock on via RSDlite, flash TWRP 3.1.1.0 (my best experience), THEN install whatever ROM you like in TWRP. This'll start you from a clean slate and wipe ALL data from the phone. I'm guessing you forgot to wipe dalvik and cache before restarting, to. Someone of more experience may chime in, soon.
Sent from my XT1254 using Tapatalk
Crap. Sorry. Disregard. Thought this was a Droid Turbo thread.

Einsteindks said:
As I understand it, being an amateur ROM flasher, all those 3rd party ROMs need a TWRP recovery to work. Provided your bootloader is unlocked, I'd flash the stock on via RSDlite, flash TWRP 3.1.1.0 (my best experience), THEN install whatever ROM you like in TWRP. This'll start you from a clean slate and wipe ALL data from the phone. I'm guessing you forgot to wipe dalvik and cache before restarting, to. Someone of more experience may chime in, soon.
Click to expand...
Click to collapse
But how do I flash anything if I can't get into recovery?

andreyl79 said:
But how do I flash anything if I can't get into recovery?
Click to expand...
Click to collapse
You missed my edit update. I got confused as to which thread I was replying to.
Sent from my XT1254 using Tapatalk

Einsteindks said:
You missed my edit update. I got confused as to which thread I was replying to.
Click to expand...
Click to collapse
Nevertheless you gave me the idea to try looking for a similar LG recovery tool and I just found one. Flashing stock at the moment - fingers crossed

Ok, I installed LineageOS and it worked fine. Must be an issue with the latest AOSP ROM here

andreyl79 said:
Ok, I installed LineageOS and it worked fine. Must be an issue with the latest AOSP ROM here
Click to expand...
Click to collapse
The reason the flash failed is simply the fact you put the ROM on the internal storage, flashing from there wiped the ROM before it gets written. If you had stored the AOSP on an external SD, it would have worked.
As Lineage is based on AOSP, it should have failed also...