Database Users

Updated OTA - Now my tab seems broken

Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.

GaresTaylan said:
Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.
Click to expand...
Click to collapse
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Things I have tried:
*MD5 Post-update*
*Wipe Data/Cache via stock recovery*
*Re-flash MD5*
I am now in the process of locating a UEALGB recovery/kernel. If any member has a link to it or can help its certainly appreciated.

vanillanesquik said:
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Click to expand...
Click to collapse
Are you just having OTA update issues or is your screen not responding properly to touch as well?

GaresTaylan said:
Are you just having OTA update issues or is your screen not responding properly to touch as well?
Click to expand...
Click to collapse
No touch, no pen input. Its worst-case.

vanillanesquik said:
No touch, no pen input. Its worst-case.
Click to expand...
Click to collapse
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.

GaresTaylan said:
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.
Click to expand...
Click to collapse
The update restored touch function but the pen functions are completely derped.
A pre-rooted full package is being uploaded by entropy in the next 2 hours so I am crossing my fingers that this will fix it.

I have the same issues I\m trying all things to get it to work just like you are to no avail, Samsung update now things are all screwed up

Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS

vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
top link is dead, btw i lost touch functions LOL
anyway i will fix it

I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2

I had the same issue and flashed this via Odin: http://forum.xda-developers.com/showthread.php?t=1847706
Fixed it and now i'm running the latest update.

I lost touch and pen and now i have them back. Heres how:
1. IM AWESOME!
2. Rebooted my computer.
3. Wiped everything.
4. ODIN root injected original firmware.
5. Kies update.
6. ODIN Clockwork Recovery
7. Flash Superuser.
Boom, everything works.
** DISCLAIMER - There is a strong possibility this worked only due to #1. YMMV.
Sent from my GT-N8013 using Tapatalk 2

-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk

BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
I took the OTA via Kies because it was listed in the OTA update thread that it was ok to do so? And that root was working fine afterward?

BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
Because we are dangerous, exciting and chicks dig us.
Sent from my GT-N8013 using Tapatalk 2

-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
The root method 2 specified that OTA was viable with stock recovery. I flashed stock recovery and the OTA failed. We were then forced to update via KIES and touch/pen functions were then bugged. The best way is my method above.

vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
I tried this method and when my note boots up s note keeps crashing every 15 seconds or so without my even opening it.

BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
In many cases, if you ONLY have added su and Superuser.apk - you can safely apply an OTA. However if you've touched anything else in /system - boom

Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.

mi7chy said:
Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.
Click to expand...
Click to collapse
OK so o tried vanillas order and kies froze or disconnect me or something so I odined the md5 tar of the new update and back to no touch screen but like 5 mins so I shut it off and resume later.
What is the best thing to do to get all fixed up?
Sent from a Baked Black Jelly Belly

[Verizon]OTA Droid Maxx update info + Download File

Verizon Droid Maxx XT1080
-Camara application
-Google Drive 50GB Promotion
-Mophie Juice pack compatibility
- Wireless charging has been improved to support faster connections
- 4G LTE performance has been improved to support faster connection
- Motorola Assist has been improved for better stability
- Google Voice now returns cards with audible feedback when location setting is enabled
- The lastest version of NFL Mobile has been added
- Viewdini has been removed as a preloaded application
^^Thank you for reminding me supreme!
Make sure you have a TWRP backup before installing!
This update can cause issues on rooted phones!
Download Link:
Blur_Version.12.7.7.obake-maxx_verizon
Presumably you can drop the .zip into your /cache folder (where it was located on mine) and update

I wonder if the ultra will also receive this
Sent from Ahjee's Ultra which is likely better than your phone

Make sure you have a backup in TWRP before running this as it does not take kindly to root. I had a "Shutdown" loop after installing on rooted device.

Could you please extract and post the Google Drive Apk?
Sent from my Nexus 5 using Tapatalk

Kickbut101 said:
Verizon Droid Maxx xt1080
Camera update
Google Drive 50GB Promotion
Mophie Juice pack compatibility
Just to note: As far as I know I am not part of any pre-release test groups/soak tests.
Click to expand...
Click to collapse
I installed the update while rooted and 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.

Well I unrooted by fxz save data then installed the pwnmymoto apk took the update and got root back all is normal but I can't access touchless control it wont allow me to check the box. google search works but not touchless control. Can we fxz back with this update or will it brick our phone.
Ok I unistalled and then updated the app but now I get to the training screen but it doesn't activate it's like it can't hear me.

bigv5150 said:
Well I unrooted by fxz save data then installed the pwnmymoto apk took the update and got root back all is normal but I can't access touchless control it wont allow me to check the box. google search works but not touchless control. Can we fxz back with this update or will it brick our phone.
Ok I unistalled and then updated the app but now I get to the training screen but it doesn't activate it's like it can't hear me.
Click to expand...
Click to collapse
You have to update it from the play store. I had that problem before the update. Could you tell me the exact process you used to root the update? I'm about to try and upgrade, but can't survive without root lol
Sent from my XT1080 using XDA Premium 4 mobile app

needshelp101 said:
You have to update it from the play store. I had that problem before the update. Could you tell me the exact process you used to root the update? I'm about to try and upgrade, but can't survive without root lol
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did an fxz save data with house of moto which restores to stock but keeps data. Then I re-installed pwnmymoto but did not run it. rebooted to recovery and installed the update from my sdcard. everything went fine but no touchless controls I installed the update and still it would not let me past the training screen. So I said **** it and installed the stock recovery did a factory reset and now I am good I will just juse the new root method.
If you use my method above when you reboot after the update pwnmymoto will automatically run and install root it cycles 3 times so don't worry you are not in a bootloop with it shutting on and off.

The adb root method? By jcase? I'm a little hesitant to use that one. Since I have no prior adb experience
Sent from my XT1080 using XDA Premium 4 mobile app

needshelp101 said:
The adb root method? By jcase? I'm a little hesitant to use that one. Since I have no prior adb experience
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
PwnMyMoto was an apk you download http://forum.xda-developers.com/showthread.php?t=2444954
Super super easy to do.
Glad to hear someone was able to use this as a new ota root method. But I haven't heard of many others doing this. It's still a little early to hear all the news.

starose
Kickbut101 said:
Verizon Droid Maxx XT1080
Camera update
Google Drive 50GB Promotion
Mophie Juice pack compatibility
Make sure you have a TWRP backup before installing!
This update can cause issues on rooted phones!
Moved the downloaded file to /cache. Fastbooted the stock recovery and temp un-rooted. Every time I try and update though, it tells me that my device is up to date.
Thoughts?
Click to expand...
Click to collapse

Can anyone confirm if SafeStrap is working with the updated build? After the new root exploit, that is.

offeldn
killboredom said:
Kickbut101 said:
Verizon Droid Maxx XT1080
Camera update
Google Drive 50GB Promotion
Mophie Juice pack compatibility
Make sure you have a TWRP backup before installing!
This update can cause issues on rooted phones!
Moved the downloaded file to /cache. Fastbooted the stock recovery and temp un-rooted. Every time I try and update though, it tells me that my device is up to date.
Thoughts?
Click to expand...
Click to collapse
Booted to recovery and applied update from SD. failed with "set_perm: some changes failed" Rebooting and it says "Android is upgrading." We'll see I guess.
---------- Post added at 01:08 AM ---------- Previous post was at 12:49 AM ----------
killboredom said:
killboredom said:
Booted to recovery and applied update from SD. failed with "set_perm: some changes failed" Rebooting and it says "Android is upgrading." We'll see I guess.
Click to expand...
Click to collapse
Brilliant! Booted to system version 12.15.15. So...followed these directions to maintain root:
http://forum.xda-developers.com/showthread.php?t=2466191
To apply the "OTA" I booted to stock recovery and updated from SD. This failed, but booted to 12.15.15.
Then in the above directions, used fastboot to install the new baseband from the modem drivers from another thread in this forum.
profit!!!!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Just to help anyone out I am part of the soak test. If you try to update by hiding root and then flashing stock recover you will get error from trying to install from stock recovery or if you where able to do an ota it will fail. It will show afterwards that you are on the version but you are lacking some things. Anyways The way That I got everything to work without a single error including the baseband coming from the ota .
used fastboot to flash recovery back to stock recover . Flashed stock system to system in fastboot. After that then I installed that I backed up after download from verizon through stock recovery from sd card. after I came back online. I used adb and the RockMyMoto Root and walla everything good to go.
Hope this info helps some !!

I've downloaded it and placed it in cache but my phone still says it's up to date? Any thoughts?

Sorry, what do you mean under
Make sure you have a TWRP backup before installing!
Click to expand...
Click to collapse
?
Is there a boot-loader unlock option for XT1080Mto flash TWRP? Where is TWRP for XT1080M?

I installed it in reocovery. It did say that it was aborted and that some files did not update however after rebooting it says Android is upgrading Optimizing apps xxx of 131.
Did it update or not?

bluh5d said:
Just to help anyone out I am part of the soak test. If you try to update by hiding root and then flashing stock recover you will get error from trying to install from stock recovery or if you where able to do an ota it will fail. It will show afterwards that you are on the version but you are lacking some things. Anyways The way That I got everything to work without a single error including the baseband coming from the ota .
used fastboot to flash recovery back to stock recover . Flashed stock system to system in fastboot. After that then I installed that I backed up after download from verizon through stock recovery from sd card. after I came back online. I used adb and the RockMyMoto Root and walla everything good to go.
Hope this info helps some !!
Click to expand...
Click to collapse
Interesting... How do you determine the you are missing stuff? How did you flash the stock system?
Things seem to be running fine through my method, but the update did fail and I certainly haven't tried everything.
Sent from my XT1080 using Tapatalk

Cincybearcatfan said:
I installed it in reocovery. It did say that it was aborted and that some files did not update however after rebooting it says Android is upgrading Optimizing apps xxx of 131.
Did it update or not?
Click to expand...
Click to collapse
It appears at least some things were updated. When I rebooted, I got the "moto camera" update from the market and when I check build number it is the 15.15.15 update so it looks like that went through. I'm just curious as to what "failed" and what made it through.

For those that failed halfway through, you most likely don't have the new baseband (95). You'll be unable to take future updates until you get everything squared away.
Sent from my XT1080MDEV.

[Q] Updates working?

I've been using Omni since roughly the middle of December. I've been making use of the opendelta updates...but these have stopped working since 2014-02-17. I check for updates and it tells me Your system is up to date
My phone is a N7100 (Note 2)...note sure what other information is relevant here.
Anybody else experiencing this?

cavaliersa said:
I've been using Omni since roughly the middle of December. I've been making use of the opendelta updates...but these have stopped working since 2014-02-17. I check for updates and it tells me Your system is up to date
My phone is a N7100 (Note 2)...note sure what other information is relevant here.
Anybody else experiencing this?
Click to expand...
Click to collapse
Hmm, possibly the removal of the 2/18 nightly screwed up the system.
Try manually updating to see if it restarts.

I know that the Xperia ZL updates don't automagically flash... (they download on the internal sdcard drive, but attempt to flash from the external sdcard drive...)
That doesn't seem to be the issue you're describing though...

scifan said:
I know that the Xperia ZL updates don't automagically flash... (they download on the internal sdcard drive, but attempt to flash from the external sdcard drive...)
That doesn't seem to be the issue you're describing though...
Click to expand...
Click to collapse
Browse to the internal in TWRP and they should autoflash then.
I need to look into fixing TWRP's default search path when flashing via a script.

Entropy512 said:
Browse to the internal in TWRP and they should autoflash then.
I need to look into fixing TWRP's default search path when flashing via a script.
Click to expand...
Click to collapse
I browse to them, and flash them manually and it works... but it doesn't work automatically...

scifan said:
I browse to them, and flash them manually and it works... but it doesn't work automatically...
Click to expand...
Click to collapse
I had success going into TWRP Recovery mode and unchecking the zip file signature verification box. Once I did that, the autoupdates started to work again.

Entropy512 said:
Hmm, possibly the removal of the 2/18 nightly screwed up the system.
Try manually updating to see if it restarts.
Click to expand...
Click to collapse
After updating to 2/22 manually the next updates (2/23) was picked up...when prompted to Flash Now I did so but now the update did not go through automatically as it had/has been for the previous month or so. Browsing to the update and selecting to install it manually worked.
excaliber88 said:
I had success going into TWRP Recovery mode and unchecking the zip file signature verification box. Once I did that, the autoupdates started to work again.
Click to expand...
Click to collapse
I'll have a look at this when 2/24 comes out today.

Have the same problem "updates not working issue" when I did rollback to quickly solve the wifi issue on 18 feb.
See also my thread
http://forum.xda-developers.com/showthread.php?t=2652796
I see stil see the
omni-4.4.2-20140218-n7100-NIGHTLY.zip.md5sum
file.
Can somebody remove this md5 file so i don't have to do a manual update?
This will resolve the update not working issue.
Sent from my GT-N7100 using xda app-developers app

help
cavaliersa said:
After updating to 2/22 manually the next updates (2/23) was picked up...when prompted to Flash Now I did so but now the update did not go through automatically as it had/has been for the previous month or so. Browsing to the update and selecting to install it manually worked.
I'll have a look at this when 2/24 comes out today.
Click to expand...
Click to collapse
can you please tell me how to manually update omnirom, thanks

Sorry for not answer hichem but at least I see you came right.
To report back though...update went through smoothly last night.
A small (related) thing that has been bugging me though with Opendelta updates is that sometimes it takes a few Check now presses before it finds something...then it will stop and report that your system is up to date after having verified the update file you presently have and downloading the update file...press Check now again and it now patches the file before reporting that there is an update and you can flash.
Any reason to this behaviour?

hichem jerbi said:
can you please tell me how to manually update omnirom, thanks
Click to expand...
Click to collapse
Just download the lastest version from
http://dl.omnirom.org/
and go into recovery mode to install the update omnirom you just downloaded
Sent from my GT-N7100 using xda app-developers app

Ancientsthe said:
Just download the lastest version from
http://dl.omnirom.org/
and go into recovery mode to install the update omnirom you just downloaded
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
thx man

Ancientsthe said:
Just download the lastest version from
http://dl.omnirom.org/
and go into recovery mode to install the update omnirom you just downloaded
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thanks man,,it's done.
But after installing 24/02 update manually,,today's update 25/02 couldn't be installed automaticly !!! Any idea how to fix it ??
Resolved ,, just set install from internal storage in install mode of twrp

Lollipop 5.0.1 Incoming

Per Droid-Life:
http://www.droid-life.com/2014/12/02/android-5-0-1-headed-to-aosp-as-build-lrx22c/

I'm ready!

I've got five candles lit and Kenny G on in the background, plus I'm wearing my fancy silk robe.
So yeah, I'm ready ☺

SilkyJohnson said:
I've got five candles lit and Kenny G on in the background, plus I'm wearing my fancy silk robe.
So yeah, I'm ready ☺
Click to expand...
Click to collapse
I laughed way to hard for that.

SilkyJohnson said:
I've got five candles lit and Kenny G on in the background, plus I'm wearing my fancy silk robe.
So yeah, I'm ready ☺
Click to expand...
Click to collapse
Lmao!
This is why we get "Nexus". We are the bleeding edge

I just get my device today and then rooted it immediately to find out there is an update coming out. I wonder how the OTA is going to do when I'm rooted????

tee00max said:
I just get my device today and then rooted it immediately to find out there is an update coming out. I wonder how the OTA is going to do when I'm rooted????
Click to expand...
Click to collapse
Lollipop checks to see if ANY system files are modified. If yes, it fails. Before, you could just put stock recovery back on and pretty much call it a day. I will just flash the factory image, boot up and take the OTA - then immediately go back into fastboot and put recovery, root and an unencrypted kernel right back on. Lollipop's app restore functionality I kind of like, so I can be back up and running pretty quick.
Or you could try to restore only data through recovery, but that's risky when jumping versions. I won't do it.

P.S. I think any proper Nexus owner should always have the latest stock image downloaded to their computer. If you ever need to save your ass it's just a click away. Plus, come downgrade time you're ready to go when you get off work ?
P.P.S. use Google Remote Desktop and leave your home computer on the developer page. That's what I did on the N5 when our images got released. That puppy was downloaded and ready to go the second I walked in the door.

tee00max said:
I just get my device today and then rooted it immediately to find out there is an update coming out. I wonder how the OTA is going to do when I'm rooted????
Click to expand...
Click to collapse
If you have a custom recovery you'll have to do a system wipe before you can flash the OTA.
Sent from my Nexus 6

Looks like factory images are starting to go up:
"Update: *And just like that, Android 5.0.1 factory images have gone live for a handful of devices, including the Nexus 9, Nexus 7 (2013) WiFi, and Nexus 10. Basically, we are looking at the WiFi devices. *You can grab individual image fileshere."
-per Droid-Life

SilkyJohnson said:
Lollipop checks to see if ANY system files are modified. If yes, it fails. Before, you could just put stock recovery back on and pretty much call it a day. I will just flash the factory image, boot up and take the OTA - then immediately go back into fastboot and put recovery, root and an unencrypted kernel right back on. Lollipop's app restore functionality I kind of like, so I can be back up and running pretty quick.
Or you could try to restore only data through recovery, but that's risky when jumping versions. I won't do it.
Click to expand...
Click to collapse
Can we only flash boot.img and System.img? would this fix root and replace any modded system files?

iboj007 said:
Can we only flash boot.img and System.img? would this fix root and replace any modded system files?
Click to expand...
Click to collapse
Hey, I'd give it a try! In theory I'd say it could.

SilkyJohnson said:
P.S. I think any proper Nexus owner should always have the latest stock image downloaded to their computer. If you ever need to save your ass it's just a click away. Plus, come downgrade time you're ready to go when you get off work ?
P.P.S. use Google Remote Desktop and leave your home computer on the developer page. That's what I did on the N5 when our images got released. That puppy was downloaded and ready to go the second I walked in the door.
Click to expand...
Click to collapse
For Sureeee. It seems i have had a few more issues with this phone in which having the factory images and fastboot have been a godsend.

crashercarlton said:
For Sureeee. It seems i have had a few more issues with this phone in which having the factory images and fastboot have been a godsend.
Click to expand...
Click to collapse
Agreed.
I can't get ADB to work after unlocking, but fastboot works like a champ and that's all I really use. I use ADB to reboot into BL ? I haven't cared or missed it enough to troubleshoot and fix.
Just refreshed the Dev page and it seems everything recent has been updated, minus the N5/6.
I have faith ?

jbdan said:
Lmao!
This is why we get "Nexus". We are the bleeding edge
Click to expand...
Click to collapse
Yup. I feel like I did when I first got my Galaxy Nexus and updates were fat and furious.
Sent from my Nexus 6

SilkyJohnson said:
Lollipop checks to see if ANY system files are modified. If yes, it fails. Before, you could just put stock recovery back on and pretty much call it a day. I will just flash the factory image, boot up and take the OTA - then immediately go back into fastboot and put recovery, root and an unencrypted kernel right back on. Lollipop's app restore functionality I kind of like, so I can be back up and running pretty quick.
Or you could try to restore only data through recovery, but that's risky when jumping versions. I won't do it.
Click to expand...
Click to collapse
rlh445 said:
If you have a custom recovery you'll have to do a system wipe before you can flash the OTA.
Sent from my Nexus 6
Click to expand...
Click to collapse
Right now I am running stock recovery. All I have is the bootloader unlocked and have root access.

I'll wait for a TWRP flashable zip :fingerscrossed:

tee00max said:
Right now I am running stock recovery. All I have is the bootloader unlocked and have root access.
Click to expand...
Click to collapse
It'll fail with root now.

looks like they're posting wifi only for now

indianajonze said:
looks like they're posting wifi only for now
Click to expand...
Click to collapse
Typical Googs.

Trying to change emoji's - having issues

At first, they all disappeared...... Then I finally got them to change, but return to stock with every reboot?
Forgot to do a backup before starting this..... So I'm stuck with what ever I end up with

tele_jas said:
Of course, I forgot to make a backup before doing anything.....So, is there any way I can get my emoji's back?
Click to expand...
Click to collapse
you have an idea where's the emoji's location?
i can pull those files and upload them for you or anyone else
P.S. Dude, Always Backup.....first rule while messing with root,system changes, etc :cyclops:

DrakenFX said:
P.S. Dude, Always Backup.....first rule while messing with root,system changes, etc :cyclops:
Click to expand...
Click to collapse
Yeah, I've been doing this for 4 years..... I just got over-excited and did a stupid thing
I think I know where they're located and I've replaced them with a different set, then rebooted and tried the emoji switcher again and I now have the "Emoji One" emoji's :highfive:
[EDIT] But every time I restart, the stock emoji's return?
Also flashed a different font

tele_jas said:
Yeah, I've been doing this for 4 years..... I just got over-excited and did a stupid thing
I think I know where they're located and I've replaced them with a different set, then rebooted and tried the emoji switcher again and I now have the "Emoji One" emoji's :highfive:
[EDIT] But every time I restart, the stock emoji's return?
Also flashed a different font
Click to expand...
Click to collapse
awesome dude,
P.S. you are show quiet the info there (phone number) just FYI LoL

DrakenFX said:
awesome dude,
P.S. you are show quiet the info there (phone number) just FYI LoL
Click to expand...
Click to collapse
Yeah, I realized that after I posted it....Was editing it when you replied

To have your changes persist you need to disable system write protection:
Code:
adb shell reboot disemmcwp
As discovered here:
http://androidforums.com/threads/zte-write-protection-for-zmax-and-other-zte-phones.1040331/
originally for other ZTE phones but works with the Axon 7 too.

Nameless One said:
To have your changes persist you need to disable system write protection:
Code:
adb shell reboot disemmcwp
As discovered here:
http://androidforums.com/threads/zte-write-protection-for-zmax-and-other-zte-phones.1040331/
originally for other ZTE phones but works with the Axon 7 too.
Click to expand...
Click to collapse
Awesome, that did it! Thank you!!

tele_jas said:
At first, they all disappeared...... Then I finally got them to change, but return to stock with every reboot?
Forgot to do a backup before starting this..... So I'm stuck with what ever I end up with
Click to expand...
Click to collapse
It's been a while since I've rooted. Do you have a file or file link to the emoji one emoji for the whole system and also a font package zip?
Sent from my ZTE A2017U using Tapatalk

osmosizzz said:
It's been a while since I've rooted. Do you have a file or file link to the emoji one emoji for the whole system and also a font package zip?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I'm using "Emoji Switcher" from the play store (Root required). I don't have the actual .ttf file. There is a "write protection" on the system, once I rebooted, they came back (to stock)..... After I removed the write protection, I was able to successfully change my emoji's using the app. :good:
The font I got here off of XDA, I only have the "China Cat" font .zip

tele_jas said:
I'm using "Emoji Switcher" from the play store (Root required). I don't have the actual .ttf file. There is a "write protection" on the system, once I rebooted, they came back (to stock)..... After I removed the write protection, I was able to successfully change my emoji's using the app. :good:
The font I got here off of XDA, I only have the "China Cat" font .zip
Click to expand...
Click to collapse
Awesome man. Thanks. I used to use that app but stopped because it stopped working on Samsung devices after MM. Going to give it a try when I get a chance. Haven't unlocked my bootloader because I don't want spend 3 hours setting up the phone again. Maybe I'll wake up early Saturday and get it done
Sent from my ZTE A2017U using Tapatalk

osmosizzz said:
Awesome man. Thanks. I used to use that app but stopped because it stopped working on Samsung devices after MM. Going to give it a try when I get a chance. Haven't unlocked my bootloader because I don't want spend 3 hours setting up the phone again. Maybe I'll wake up early Saturday and get it done
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Backup your phone (system and apps) to your SD card using the WeShare app included on your phone..... It will cut your restore time down quite a bit!
It's not perfect, but sure saved me a lot of time setting back up.