Question about fonts - ZTE Axon 7 Questions & Answers

So i try to install a ttf file font and it disappears whenever i restart the device. Also my magisk manager app wont open now it crashes every time i try to run it. Rooted & unlocked BadBoys rom 2.0. Any help would be highly appreciated

Not 100% sure this is your problem, but sometimes you need to run the disemmcwp reboot (or something like that) terminal command to make your changes stick after reboot. This may be why you're having issues?
It's in a sticky guide by DrakenFX

tele_jas said:
Not 100% sure this is your problem, but sometimes you need to run the disemmcwp reboot (or something like that) terminal command to make your changes stick after reboot. This may be why you're having issues?
It's in a sticky guide by DrakenFX
Click to expand...
Click to collapse
I haven't tried that but I didn't have this problem when I was on the previous rom version (did a clean install update) I'll try it when I can get to a computer. Also don't know if that explains why magisk manager won't stay open.

Related

updating kernal

i was wondering if i could update my kernal to intersectRaven. will it delete the mod on my phone or just change the kernal? my mod version is CyanogenMod-5.0.6-N1. also, will it require me to re-do all my phone settings and install all apps? i guess its called a "wipe".
Hi - it wont remove the mod, you might want to take a look at my guide here
The updates are obtainable either in 'flash from recovery' or 'adb push' format.. either will work the same.
If you want more info, let me know.
i know nothing abot "adb push" and everytime i tried to learn i failed. i will try to do a flash recovery.
im running cyan 5.0.6 so u dont have to do an adb push. You can simply just flash this kernel in recovery as i am also running intersectravens last 33.3, just make sure wi-fi is turned off before flashing as it may break ur wifi. If it does then ull have to do a adb push. If you just flash i think there are downsides to it like not being able to revert back to other kernels unless u do a nandroid. I may be wrong so check his thread and read up on it.
Heres how i figured out how to use adb. Your rooted so Im sure u have the drivers installed. This link tells you how to hook up phone using ur androidSDK, check to see phone is detected, then adb push the commands they have in the thread for kernel. I use his last 33.3 CFS 800mV . http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
ahh i didnt turn off my wifi! seems to be working though...

Help with rooting my zenfone laser model ze551kl

Hello. I have a few questions on rooting this phone. (My first time rooting)
First off, Is this the same model as the ze550kl (I assume so but not 100% sure). I have attempted to root this phone through the instructions provided in posts on this website for model ze550kl but I must be doing something wrong with the programs ect. I have never rooted a phone and so this is my first try and I would really like a full in detail screenshot follow through if available to do with the programs once downloaded and any other programs you may need on windows 10 to get to where I need to be. I dislike the zenui so much that is my main reason to root the phone is to remove this and other bloatware as well as some of my friends have some apps that are pretty neat that I would like that are only available through root.. I have also tried other methods posted on YouTube but I think I'm doing something wrong on all of my attempts. I would also like to know if there is a way to make a backup of the original files prior to rooting so I can send my phone in because I have a 2 year warantee if something was to happen (dropped, broken, ect.). In relation to the screenshots if there is any files that have to be placed on the phones hard drive from something I download off the internet please state this specifically, I believe that one or 2 ways I have seen required this but it seems vauge and I don't think it was done correctly by me. I am great at following detailed instructions but I don't know what exactly it is I need to do as I have never done this before so if something has to have a specific name please note that.
Thank you for the help.
My ZF2L should be showing up any minute now, so I'll let you know when it gets here. I'm no expert, but I've been rooting my Android devices since 2009. I think I can help you out.
HampTheToker said:
My ZF2L should be showing up any minute now, so I'll let you know when it gets here. I'm no expert, but I've been rooting my Android devices since 2009. I think I can help you out.
Click to expand...
Click to collapse
Thank you, I think I'm just missing an important step. The zenui just isn't my style. Will be nice to be able to remove
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 02:07 PM ---------- Previous post was at 01:28 PM ----------
Yeah, I think you just need more comprehensive instructions. It happens from time to time. From what I can tell so far, it's a pretty straightforward process for those that are familiar with root, but to a beginner it can be a bit much. As soon as mah lazah is dunna chargin' I'll walk you through the steps I took to root it, install custom recovery, and make a backup of your entire system just in case you ever need to restore your phone to a stock-rooted-but otherwise unmodified state. I should have something up in the next couple hours ?
Updated, rooted, and installed custom recovery. I'll post a short write-up shortly.
First off, I'm going to answer your questions since I didn't previously.
Sorvas33 said:
First off, Is this the same model as the ze550kl (I assume so but not 100% sure).
Click to expand...
Click to collapse
No, they're different, but I'm not entirely sure by how much. I'm 100% sure that they're probably maybe 90% or so compatible, but there are differences. I just don't know them without checking. I wouldn't go flashing anything that doesn't explicitly state that it's for the 551 or is compatible or has had a 551 user test and report success. There are some things that are kind of universal (and we'll get into that a little), but for now let's just stick with using caution.
Sorvas33 said:
I would also like to know if there is a way to make a backup of the original files prior to rooting so I can send my phone in because I have a 2 year warantee if something was to happen (dropped, broken, ect.)
Click to expand...
Click to collapse
We'll make a backup using TWRP, but you'll have to be rooted. A TWRP backup (or nandroid backup) is like a snapshot of your current system. You can customize it and only backup certain parts of the system as well as restore certain parts, but I wouldn't worry about that. Most of the time you'll want a complete backup, anyway. But, to answer your question, no, you'll have to be rooted, but you can always unroot from the phone using the Supersu app. If the damage is physical an unrooted backup wouldn't matter anyway.
So, here's my (hopefully) brief write-up to acquire root, install recovery, make a backup, and ,optionally, install the Xposed framework. Before getting started be sure to have plugged your phone into your computer for Windows to download and install drivers for your ZF2L. Also, you will need to download and install adb in order to use command prompt to flash files to your phone. This link will take you to a thread here at XDA for Minimal ADB and Fastboot. This is the easiest way to install and use adb and fastboot on your computer. Once you have it installed you can proceed to the next steps.
First, you'll need to unlock your bootloader using the app found here. It's in a .zip files for whatever reason, so you'll need to use 7zip or WinZip or WinRAR or something on your computer to extract it and install to your phone. You can plug your phone in and place the extracted app on your external or internal storage or use a cloud storage app like Dropbox or Google Drive to transfer it to your phone. If you plug it in and place on your internal or external storage, then you'll need to use File Manager (it's a stock app) to find and install it. Once installed just run the app. It's extremely user friendly and straightforward. Your phone will reboot when it's done.
Next, you'll have to temporarily boot a modified boot.img using Minimal adb and fastboot. Once this step is completed and the phone boots up you'll need to go to the Play Store and install Supersu as well as Busybox if you want your root apps to work properly.
Go here on your computer and download the modified boot.img named boot_200007.img and place it in the Minimal adb and fastboot folder. As you can see in this screenshot:
my adb and fastboot folder is located at C:\Windows\Minimal ADB and Fastboot. Once you have the boot.img copied to the right folder go ahead and connect your phone, if it isn't already. Hold the power button and restart the phone. As soon as the screen goes off hold the volume up button until the phone boots into fastboot mode. If you have trouble with this, you can just turn the phone off, and then press and hold power and volume up until it boots into fastboot mode. Right click the Minimal adb and fastboot icon and select run as administrator. As long as it's installed correctly, the following commands shouldn't give you any error messages. Before we go further, let me briefly explain what we're doing at this point. We have two options: we can flash the boot.img which will physically write it to the proper partition on your phone, or we can simply boot the phone while the modified boot.img remains on your computer and unwritten to the phone, which is what we want to do in this case. To do this we enter the following command:
fastboot boot boot_200007.img
Your phone should reboot on it's own and once it does open the app drawer and check to see if Supersu is installed. If it isn't, open Play and install it, as well as Busybox. Open Supersu and make sure you have root. Once your done, open Busybox and install Busybox to /system/xbin and reboot when finished. At this point, you can disconnect your phone and ensure the Supersu does give you any errors. Test it by installing your favorite root apps, and since you're new to root, I'll give you some suggestions. You can do a google search to find Adaway. It isn't available in the Play Store because it's an adblocker and ads are Google's bread and butter, but it sure is nice to use apps without intrusive apps trying to sell you something no matter where you go. Root + Adaway have been solving that problem for years. Next we have Root Explorer which is my root file manager of choice. Another community favorite is ES File Manager. Both are great. Titanium Backup, Flashify (install it for the next step), and Viper4Android (not in Play search XDA) are all must have apps for root users. Install and open some of those (especially Flashify) just to verify that they work and let's move on the next step.
Download TWRP here and place it on either internal or external storage. Open Flashify and select Recovery Image and then find and select recovery551_200431.img. This will write the TeamWinRecoveryProject custom recovery to the recovery partition of your phone which will allow you to view, backup, restore, and modify all the relevant partitions that make up the Android operation system. At this moment, it's important to understand that you are now more than capable of completely and totally bricking your phone...but you're also capable of recovering from most problems that can arise from flashing mods and using root apps. This is where we'll make a complete backup for just that very reason.
After you've flashed TWRP using Flashify, you'll be prompted to reboot. Do so, and your phone will reboot into recovery. You'll see a message one the first run with a check box to disable modifications to system or something along those lines (can't remember exactly what it says lol), just don't check it. Leave the box uncheck and swipe the bar to allow modifications to system. Now, you should see the main menu. Select Backup and make sure that Boot, System, Data, and Cache are selected and rename the backup to something along the lines of "stock_rooted" or "stock_backup" if you wish and you're ready to create a nandroid backup. Swipe the button and give it a few minutes. Once done, just reboot and you're good to go.
Now to install Xposed, you'll first need to install the Xposed Installer .apk on your phone from here. To flash Xposed, reboot into recovery (turn off then hold power + volume down) and select Install then select the Xposed .zip package xposed-v80-sdk21-arm64.zip that you downloaded and placed on your internal (preferrably) or external storage beforehand. Once finished just reboot and you're done. Be warned that the first boot after installing Xposed will take a long time (approx. 5-10 minutes). Greenify, Gravitybox (LL), Youtube Adaway, Flat Style Bar Indicators, MaxLock, and NotifyClean are just a few of my favorite Xposed modules. Be sure to read the descriptions for these modules carefully and do not forget that Xposed modules can be tricky and cause problems if they're not compatible with your phone. Honestly, you should ask here before installing any modules that I haven't already mentioned.
Anyway, that's my brief write-up lol. Hopefully, that isn't too hard to follow. Don't hesitate to reply back if you encounter a problem, have any questions, or simply want to report your success and ask for tips. I'll leave you with this little tip: don't give up on ZenUI. It definitely doesn't hold a flame to stock Android, but if you use a third party launcher like Nova Launcher and use Developer Options to increase animation speed to .5 seconds (or turn them off entirely) it's really not so horrible, in my opinion. It's damn sure not TouchWiz.
HampTheToker said:
So, here's my (hopefully) brief write-up to acquire root, install recovery, make a backup, and ,optionally, install the Xposed framework. Before getting started be sure to have plugged your phone into your computer for Windows to download and install drivers for your ZF2L. Also, you will need to download and install adb in order to use command prompt to flash files to your phone. This link will take you to a thread here at XDA for Minimal ADB and Fastboot. This is the easiest way to install and use adb and fastboot on your computer. Once you have it installed you can proceed to the next steps.
First, you'll need to unlock your bootloader using the app found here. It's in a .zip files for whatever reason, so you'll need to use 7zip or WinZip or WinRAR or something on your computer to extract it and install to your phone. You can plug your phone in and place the extracted app on your external or internal storage or use a cloud storage app like Dropbox or Google Drive to transfer it to your phone. If you plug it in and place on your internal or external storage, then you'll need to use File Manager (it's a stock app) to find and install it. Once installed just run the app. It's extremely user friendly and straightforward. Your phone will reboot when it's done.
Next, you'll have to temporarily boot a modified boot.img using Minimal adb and fastboot. Once this step is completed and the phone boots up you'll need to go to the Play Store and install Supersu as well as Busybox if you want your root apps to work properly.
Go here on your computer and download the modified boot.img named boot_200007.img and place it in the Minimal adb and fastboot folder. As you can see in this screenshot:
my adb and fastboot folder is located at C:\Windows\Minimal ADB and Fastboot. Once you have the boot.img copied to the right folder go ahead and connect your phone, if it isn't already. Hold the power button and restart the phone. As soon as the screen goes off hold the volume up button until the phone boots into fastboot mode. If you have trouble with this, you can just turn the phone off, and then press and hold power and volume up until it boots into fastboot mode. Right click the Minimal adb and fastboot icon and select run as administrator. As long as it's installed correctly, the following commands shouldn't give you any error messages. Before we go further, let me briefly explain what we're doing at this point. We have two options: we can flash the boot.img which will physically write it to the proper partition on your phone, or we can simply boot the phone while the modified boot.img remains on your computer and unwritten to the phone, which is what we want to do in this case. To do this we enter the following command:
fastboot boot boot_200007.img
Your phone should reboot on it's own and once it does open the app drawer and check to see if Supersu is installed. If it isn't, open Play and install it, as well as Busybox. Open Supersu and make sure you have root. Once your done, open Busybox and install Busybox to /system/xbin and reboot when finished. At this point, you can disconnect your phone and ensure the Supersu does give you any errors. Test it by installing your favorite root apps, and since you're new to root, I'll give you some suggestions. You can do a google search to find Adaway. It isn't available in the Play Store because it's an adblocker and ads are Google's bread and butter, but it sure is nice to use apps without intrusive apps trying to sell you something no matter where you go. Root + Adaway have been solving that problem for years. Next we have Root Explorer which is my root file manager of choice. Another community favorite is ES File Manager. Both are great. Titanium Backup, Flashify (install it for the next step), and Viper4Android (not in Play search XDA) are all must have apps for root users. Install and open some of those (especially Flashify) just to verify that they work and let's move on the next step.
Download TWRP here and place it on either internal or external storage. Open Flashify and select Recovery Image and then find and select recovery551_200431.img. This will write the TeamWinRecoveryProject custom recovery to the recovery partition of your phone which will allow you to view, backup, restore, and modify all the relevant partitions that make up the Android operation system. At this moment, it's important to understand that you are now more than capable of completely and totally bricking your phone...but you're also capable of recovering from most problems that can arise from flashing mods and using root apps. This is where we'll make a complete backup for just that very reason.
After you've flashed TWRP using Flashify, you'll be prompted to reboot. Do so, and your phone will reboot into recovery. You'll see a message one the first run with a check box to disable modifications to system or something along those lines (can't remember exactly what it says lol), just don't check it. Leave the box uncheck and swipe the bar to allow modifications to system. Now, you should see the main menu. Select Backup and make sure that Boot, System, Data, and Cache are selected and rename the backup to something along the lines of "stock_rooted" or "stock_backup" if you wish and you're ready to create a nandroid backup. Swipe the button and give it a few minutes. Once done, just reboot and you're good to go.
Now to install Xposed, you'll first need to install the Xposed Installer .apk on your phone from here. To flash Xposed, reboot into recovery (turn off then hold power + volume down) and select Install then select the Xposed .zip package xposed-v80-sdk21-arm64.zip that you downloaded and placed on your internal (preferrably) or external storage beforehand. Once finished just reboot and you're done. Be warned that the first boot after installing Xposed will take a long time (approx. 5-10 minutes). Greenify, Gravitybox (LL), Youtube Adaway, Flat Style Bar Indicators, MaxLock, and NotifyClean are just a few of my favorite Xposed modules. Be sure to read the descriptions for these modules carefully and do not forget that Xposed modules can be tricky and cause problems if they're not compatible with your phone. Honestly, you should ask here before installing any modules that I haven't already mentioned.
Anyway, that's my brief write-up lol. Hopefully, that isn't too hard to follow. Don't hesitate to reply back if you encounter a problem, have any questions, or simply want to report your success and ask for tips. I'll leave you with this little tip: don't give up on ZenUI. It definitely doesn't hold a flame to stock Android, but if you use a third party launcher like Nova Launcher and use Developer Options to increase animation speed to .5 seconds (or turn them off entirely) it's really not so horrible, in my opinion. It's damn sure not TouchWiz.
Click to expand...
Click to collapse
Thank you man, I will try this when I get a chance (working 14 hour days ATM) but I will let you know how it goes.also what model member do you have. Because the box I have is we're I got my model number. I can't find the one listed on my box in the device itself.
Exact same model...ZE551KL.
In About Phone the model number is ASUS_Z00TD.
HampTheToker said:
Exact same model...ZE551KL.
In About Phone the model number is ASUS_Z00TD.
Click to expand...
Click to collapse
Exactly what I have. Sweet. I'll update you once I'm done. Thank you for your help and assistance. Any app advice? For uninstalling and cleaning hdd/ram. And theme?
Come on, bro...I gotta know if that's friendly enough to get you squared away...
HampTheToker said:
Come on, bro...I gotta know if that's friendly enough to get you squared away...
Click to expand...
Click to collapse
I should have time either tomorrow or next weekend all depending and I'll let you know then. Depends on how much I have to work. I check this post about once to twice a day. Thank you for your effort and time. I really do appreciate it.
Now I do have one more question on my mind. Does the Asus zenfone that we have keep a flash tracker? Meaning that it keeps track if a phone was rooted. The reason I ask is that I have a 2 year warantee and I know that this will "void" it unless I flash it back. But if they have a tracker then I need to make sure there is a way to reset that as well. From what I have read personally it is only Samsung that is keeping track in this way. Thanks for your help Mr.Toker
Yeah, that's mostly a Sammy thing. I'm coming from a Galaxy S4 that's been passed down to my six year old. I'm all too familiar with flash counters and KNOX security. Thankfully, I don't believe Asus has anything like that. That's one of the many reasons I chose this phone over anything Cricket had to offer. I don't care how good the hardware is, if it can't be unlocked and rooted, then I don't want it.
But, to answer your question more directly, no, I don't believe your warranty will be affected.
Also, I'm going to paste this warning from the developer that built TWRP for us.
Warning
Do not try to fix permission, if you do not know exactly what this is ?
Home > Advance > Fixpermission
Click to expand...
Click to collapse
Just figured I'd add that I believe I read unlocking your boot loader voids the warranty. As of right now, I'm pretty sure there's no way to root without unlocking it, and no way to re-lock it after unlocking.
Sent from my ASUS_Z00TD using Tapatalk
CKtheProblem said:
Just figured I'd add that I believe I read unlocking your boot loader voids the warranty. As of right now, I'm pretty sure there's no way to root without unlocking it, and no way to re-lock it after unlocking.
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
"oem relock bootloader" should do the trick, but I haven't tried it. Sure, technically unlocking your bootloader and rooting voids your warranty, but it's not like either sends a message to Asus in the background stating that you've voided your warranty. The only way they'd know is if you sent it to them for a claim while still rooted. Even then, if it's bricked, it's bricked. They still won't know. If it's not bricked and it's just hardware, then you should be able to unroot.
Honestly, rooting your device has always been a risk to your warranty, but I've yet to have any issues with it since I started rooting my devices in 2009.
HampTheToker said:
"oem relock bootloader" should do the trick, but I haven't tried it. Sure, technically unlocking your bootloader and rooting voids your warranty, but it's not like either sends a message to Asus in the background stating that you've voided your warranty. The only way they'd know is if you sent it to them for a claim while still rooted. Even then, if it's bricked, it's bricked. They still won't know. If it's not bricked and it's just hardware, then you should be able to unroot.
Honestly, rooting your device has always been a risk to your warranty, but I've yet to have any issues with it since I started rooting my devices in 2009.
Click to expand...
Click to collapse
Yeah you're probably right. Luckily, I've never had to send a phone I rooted back in for repairs so I can't say anything about the process.
Sent from my ASUS_Z00TD using Tapatalk
Thanks for those root/recovery instructions, just got this same phone and model number yesterday and just now found the files needed ! You rock! What roms do you suggest?
tmjm28 said:
Thanks for those root/recovery instructions, just got this same phone and model number yesterday and just now found the files needed ! You rock! What roms do you suggest?
Click to expand...
Click to collapse
at present we have only stock rom, no custom rom is available for zenfone laser.

[tutorial][root][xperia z][c6602][lb][lollipop][5.1.1]

NOTE: THIS IS MY FIRST POST ON XDA, HOPE YOU WILL ENJOY
NOTE: ALL THE FILES ARE ACTUALLY NOT MINE, AND ALSO I DONT KNOW WHO THEY BELONG, THIS POST IS ONLY FOR TUTORIAL
THIS TUTORIAL WILL SURELY WORK ON XPERIA Z C6602(MY DEVICE), IF YOU FOLLOW THE STEPS CORRECTLY
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY MISHAPPENING TO YOUR PHONE AND YOUR HEART
THIS TUTORIAL WILL HELP YOU TO GET ROOT USING KINGROOT AND THEN REPLACING KINGROOT WITH OUR BELOVED SUPERSU :laugh:
1. FIRST OF YOU WILL NEED KINGROOT APP. (LATEST ONE WILL BE BETTER)
(as I am a new user, I am not allowed to post outside links, so plz find uself on google)(its easily available)
2. INSTALL IT ON UR DEVICE.
3. OPEN AND LET IT BE PROCCESSED.
4. TAP ON "START ROOT", MAKE SURE YOUR DATA IS ON.
5. LET IT BE FINISHED, SOMETIMES IT FAILS BUT DONT WORRY TRY AGAIN, IT WILL WORK.
6. AFTER COMPLETION, DOWNLOAD "ROOT CHECKER BASIC" APP FROM PLAYSTORE(ITS FREE).
7. GET YOUR SUCCESS RESULT. :fingers-crossed::good:
8. NOW, IN ORDER TO GET "KINGROOT" REPLACED WITH "SUPERSU", DOWNLOAD
----> TERMINAL EMULATOR APP (FREE)(PLAYSTORE)
---->ATTACHED FILE(S)
9. UNZIP THE ATTACHED FILE INTO YOUR INTERNAL MEMORY(NOT IN ANY FOLDER).
10. OPEN TERMINAL EMULATOR APP
---->TYPE
Code:
su
---->GRANT PERMISSIONS
---->TYPE
Code:
sh /sdcard/mrw/root.sh
11. LET IT BE FINISHED. (DONT WORRY IF PHONE HANGS OR LAGS OR RESTARTS, DO A MANUAL RESTAR)
12. AFTER THIS UPDATE SUPERSU BINARIES USING NORMAL MODE(PREFFERED).
13. REBOOT ON SUCCESS, UNINSTALL KINGROOT IF ITS NOT GONE AUTOMATICALLY.
14. DONE, CHECK YOUR ROOTING RESULT USING ROOT CHECKER APP.
:good::good::good:
ALL THE VERY BEST...
YOU CAN ALSO GET THIS TUTORIAL IN THE FORM OF SEQUENCED IMAGES(BETTER TO UNDERSTAND), DOWNLOAD IMAGES ZIP FOR THAT.
IF YOU LIKE MY WORK PLZ DO NOT FORGET TO PRESS THANKS BUTTON, IT WILL NOT COST YOU MORE THAN YOUR HAPPINESS
NOTE: AS I AM A NEW USER, I CANT SHARE LINKS, PLEASE COPPY THE URL AND ADD "h" TO HTTPS
FILES:
----> ZIP ttps://drive.google.com/open?id=0B6JGe-_gG3ftX2JJU1pWd2xobDg
---->IMAGES ttps://drive.google.com/open?id=0B6JGe-_gG3ftazBsRHBsQ3E5dFU
AN IMPORTANT NOTICE.
This is only for stock.
It will not work on other custom roms.
A guy commented on the post, after trying this method on existence rom.
See below.
Anyways this method I personally tested by me, it works fine. :good:
http://forum.xda-developers.com/xperia-z/general/super-su-xperia-device-lollipop-easy-t3119006
http://forum.xda-developers.com/xperia-z/general/guide-how-to-root-xperia-z-android-5-0-t3151618
you really had to make new thread bout it ?
indycar said:
http://forum.xda-developers.com/xperia-z/general/super-su-xperia-device-lollipop-easy-t3119006
http://forum.xda-developers.com/xperia-z/general/guide-how-to-root-xperia-z-android-5-0-t3151618
you really had to make new thread bout it ?
Click to expand...
Click to collapse
Dear
The method of using "supersume", doesn't work surely. I tried it personally.
And the other link u provided is for replacing kingroot with supersu only.
I made this thread for people to get the whole procedure at the same place, no need to Google more.
Hope you understand ?
And ur question is really appreciated ?
Sent from my C6603 using XDA-Developers mobile app
Doesn't work for me. Did everything exactly like you said, but trying to update supersu binaries didnt work.
I then rebooted and got a soft brick until I wipe dalvik and cache from recovery.
Natschlaus said:
Doesn't work for me. Did everything exactly like you said, but trying to update supersu binaries didnt work.
I then rebooted and got a soft brick until I wipe dalvik and cache from recovery.
Click to expand...
Click to collapse
Bro now tell me, is that problem still exists.
If yes.
U can just flash system using Twrp backup.
And then follow the procedure again but with a new version of kingroot.
Bro this method is personally used by myself, and always works for me. You can check the images.zip file. That is my own phone.
No fake things, my only motive.
????
What do you mean does it still exist. I literally just tried it yesterday.
I used the newest version of Kingroot and still that happened, but then again I dont use stock rom so that is probably interfering with it.
I probably just stick with Kingroot, it doesnt seem so bad.
Natschlaus said:
What do you mean does it still exist. I literally just tried it yesterday.
I used the newest version of Kingroot and still that happened, but then again I dont use stock rom so that is probably interfering with it.
I probably just stick with Kingroot, it doesnt seem so bad.
Click to expand...
Click to collapse
As u wish bro.
And u can stick to kingroot.
Happy root to u btw.
And being an xz user, u can join WhatsApp group for xz, there u can find the solution (same as above, many people did like this only)
Or find another thread.
????
Tried this method. The phone was stuck at the bootanimation. I forced restart it and now it is stuck at the App Optimization page.
C6002, 5.1.1, Bootloader Locked, Completely Stock. Any help?
dj.adil said:
Tried this method. The phone was stuck at the bootanimation. I forced restart it and now it is stuck at the App Optimization page.
C6002, 5.1.1, Bootloader Locked, Completely Stock. Any help?
Click to expand...
Click to collapse
Bro try to wipe dalvik cache in twrp. Otherwise the method is sure shot.
If the problem still persits then tell me how you did, i will try to simukate the same to find best solution as possible.
Thanks

Root H830 running 20A and 20C [Nougat] AutoMagically (Custom Easy Recowvery Script)

I posted this as a reply originally. Then thought it probably should be a thread so it can help as many people as possible! Let's get the custom kernels and ROMs going for this beautiful device!
You will need to already have Android 20A (C should be fine as well) stock image installed, and the bootloader unlocked [Plenty of easy help via Google won't cover that here]
You can use the Recowvery Method on 20A (Nougat) (again this should be the same for 20C) with the H830. Below is the script I used with supersu and no-verity script included. Plug-in the device to your Windows machine. Install LG drivers, and remember to unlock screen and authorize the computer via the Device's screen so ADB commands can run (unnecessary tech note: you could open command prompt cd to where this is and use it's ADB to run adb devices (if you don't understand that no worries skip it)). After that just run the script and follow the menus. Answer yes when asked if you're sure you wish to continue, and done. I hope you find my work helpful .
I used this guy's script [Easy Recowvery ALL CREDITS TO THE AUTHOR I'M JUST SUPPLYING AN H830 SPECIFIC PACK WITH NEEDED FILES THAT I VERIFIED FULLY WORK. PLEASE GO RATE HIS THREAD AND CLICK THANKS IF THIS WORKS FOR YOU!]: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
DON'T FORGET
This should work granted you have the drivers installed, and Windows has finished installing them, you tapped the prompt on your device screen to allow the adb connection, and you run script as administrator, and you restart the computer if you run adb commands yourself and aren't comfortable checking task manager to kill any and all running adb instances (could also issue the stop server command too), but if unsure of any or all of that last statement, restart
Of note answer yes when it says this isn't a V20 are you sure you wish to continue?. Also, as stated in notes I had to actually run it twice for it to stick for me (I'm sure I rushed the first time or something).
I took the time to create an H830 package of the script version with the files that worked for me. Out of respect I changed nothing aside from adding the needed files and throwing quick notes in the readme.md (bottom of file) file. (PLEASE read it, if you have issues read it you missed something). You will also still need to type yes when it states this is not a V20; Do you wish to continue? <Yes>.
. I used this package to root my H830 after the Nougat OTA killed my root access so
SHOULD WORK ON ANY H830 RUNNING STOCK 20A (should work with 20C) [NOUGAT] Read the following paragraph if you skip the rest
Read the readme.md file found in root of archive (see bottom of file).
Start it up hit like 5 for TWRP and supersu (or there's another menu option for just supersu or just TWRP whatever you desire).
Answer yes to the prompt to continue.
Now wait for the magic (again not mine this is the authors work)).
Once done you can download a reboot to recovery app or widget (or root checker) and verify that you're good to go.
If it doesn't take the first time you may need to run it again. DON'T FREAK OUT, RUN SCRIPT AGAIN IT CAN TAKE MULTIPLE RUNS.
Don't forget to install BusyBox (Stericson installer recommended and I use /su/bin personally (/su/xbin should also be fine) Since we're talking stock here generally I like to minimize any changes to /system if it can be helped personally; so I haven't tried running BusyBox from any /system mount) as this is a stock ROM.
Kernel Adiutor works and yes I recommend leaving thermald enabled as your thermal governor unless you flash a custom kernel (not included)
Manual Boot to Recovery:
Start With phone off (pinch battery button and re-insert battery if you can't otherwise shut it down or are lazy like me )
Hold both Power AND Volume Down at same time
1-2 seconds in to seeing LG Logo release and hold power button while continuing to hold volume down the entire time...
Release once you see white screen prompting yes or no to wipe user data (don't freak) ¹
use volume key to highlight yes
Hit Power key (think enter)
¹(If you have factory recovery this WILL format all user data and settings you've been warned. Only way to boot to stock recovery is to use app, widget, or terminal/adb command (reboot recovery). I don't know of any manual physical button methods to access stock recovery directly.).
You should now see TWRP Loading and can release any keys if you're holding any down still (once white wipe screen is seen you should release the keys)
Sweet, the file is small enough to be attached to this post directly, Enjoy! Also it's a 7-zip archive. It's available for every OS. For Android if you use ES File Explorer the first time you try to use a 7z file it'll offer to download plug-in, and you're good to read/write 7z archives (best compression almost always imho).
It doesn't seem to work for me, it reboots and the little android says No Command. Any suggestions?
well I ran the script ,Im afraid what was happening earlier is happening here to,when the script tries to flash Supersu it reboots to Firmware Update screen,Im fairly certain thats not right...am I correct? Gonna try to pull out (lol) before that screen loads like I did with the other method...
Ahhh I miss being able to root without a PC. I don't own one ?
Can anyone confirm this works fine? I won't have time for troubleshooting if it doesn't..
Jonathanpeyton said:
well I ran the script ,Im afraid what was happening earlier is happening here to,when the script tries to flash Supersu it reboots to Firmware Update screen,Im fairly certain thats not right...am I correct? Gonna try to pull out (lol) before that screen loads like I did with the other method...
Click to expand...
Click to collapse
Sounds like your hope would be if someone made a tot with root for 20A
shaneg79 said:
Sounds like your hope would be if someone made a tot with root for 20A
Click to expand...
Click to collapse
unfortunatley, I think that may be the only way Ill ever get my oddball device to accept TWRP....
WiiR0cKz said:
It doesn't seem to work for me, it reboots and the little android says No Command. Any suggestions?
Click to expand...
Click to collapse
same issue i turned off integrety check and ran it again it worked fine
Alpha_wolf said:
same issue i turned off integrety check and ran it again it worked fine
Click to expand...
Click to collapse
Where did you find integrety check
Sent from my LG-H830 using Tapatalk
Hi, thanks you for this post. I tried to use this script and I got an error saying that I am missing files in the "exploit" directory...please see the attached screenshot. Any ideas? Thanks.
famous145 said:
Where did you find integrety check
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
hit 5 in the main screen it should be there
Can someone please help me unlock my bootloader now that I am running nougat! TIA fellow peeps!
Is this working for everyone / anyone? Most posts so far seem to have issues...
Alpha_wolf said:
hit 5 in the main screen it should be there
Click to expand...
Click to collapse
I did this but am still getting the no command issue
This method worked for me after about 5 failed attempts. The OP guide is not very clear, I might write my own and post it today.
aanonymoushuman said:
This method worked for me after about 5 failed attempts. The OP guide is not very clear, I might write my own and post it today.
Click to expand...
Click to collapse
Please!
When you say failed, did you get the no command issue as well,or something different?
Dumboguy03 said:
Please!
When you say failed, did you get the no command issue as well,or something different?
Click to expand...
Click to collapse
I did get the no command issue in recovery, the first time I did it, disabling integrity verification solved the problem when I did my next time, but I got some other issues before this solution worked.
My problem is, i am on Mac in parallels i can't list my phone in adb devices command. it shows as empty. Installed every possible app scenarios but still looks empty
Check out my guide on rooting Nougat, https://forum.xda-developers.com/lg-g5/how-to/guide-root-stock-n-using-jcadduonos-t3529093
Can confirm this does work. Took me 30 tries but it worked!

A2017G - Updates don't appear to be working. Still stuck on 6.0.1.

Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Neskobar said:
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Click to expand...
Click to collapse
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Choose an username... said:
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Click to expand...
Click to collapse
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Neskobar said:
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Click to expand...
Click to collapse
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
raystef66 said:
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
Click to expand...
Click to collapse
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Neskobar said:
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Click to expand...
Click to collapse
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
raystef66 said:
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
Click to expand...
Click to collapse
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
edit - I renamed the zip to "update.up" and couldn't get that to work either. It's not detected in the update section of settings, and I still get the same "Sorry, you can't sdcard upgrade" message.
edit #2 - I tried naming it to "update.up.zip" and it detected it this time, trying to run the update now.
Neskobar said:
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up, when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
Click to expand...
Click to collapse
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
raystef66 said:
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
Click to expand...
Click to collapse
Ah, I should have mentioned that. This is the message I'm getting when I try that:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Click to expand...
Click to collapse
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Neskobar said:
Ah, I should have mentioned that. This is the message I'm getting when I try that:
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Click to expand...
Click to collapse
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
raystef66 said:
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
Click to expand...
Click to collapse
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
raystef66 said:
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
Click to expand...
Click to collapse
Ok, I attached it to this post, hope it works.
Neskobar said:
Ok, I attached it to this post, hope it works.
Click to expand...
Click to collapse
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
raystef66 said:
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Click to expand...
Click to collapse
Yes, that's what I was concerned about. The very first update i tried to install was N-B09, and everything else has been an older update after that, so maybe it won't overwrite the newer files, or something? Or possibly something else went wrong in the first update, so everything else just wouldn't work because of that?
I'm putting N-B01 onto my SD card right now, so I'll test that, and if it doesn't work I'll wipe the phone and start again. If I do need to wipe the phone, however, which update would you recommend trying first? N-B09? That might confirm if it was just bad luck on the first try, or whatever.
RobboW said:
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Click to expand...
Click to collapse
Agreed, that sounds like a possibility to me. I'll probably end up wiping and starting over.
Choose an username... said:
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
Click to expand...
Click to collapse
Yes the tab autocomplete works on the "u" of update.zip and "o" of ota.zip, when I tried both. I have to admit, I was quite excited to see your suggestion there, as I thought that would be a really easy way to confirm if something isn't right with adb, but never mind.
I still don't understand why it gives me this error then, though: * cannot read 'update.zip' *.
ramnkc said:
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
Click to expand...
Click to collapse
Thanks for the suggestion, and yes, I did confirm that I renamed the right zip file. That would have been easy thing to fix though, sadly.
edit - I tried the same adb commands with windows powershell too, and got exactly the same error messages.
What ROM was on it before you flashed B09?
Updating to N-B01 worked! I've no idea why this happened the way it did, nor why adb didn't work for sideloading, but I'm really glad that it finally worked.
The order of events:
1) Installed N-B09 via transfer to SD using the android updater, no difference in android version, but appeared in update history.
2) Installed MM-B11, same as above.
3) Tried various methods of installing MM-B11, including:
- SD transfer
- recovery mode SD update (which the phone wouldn't let me do, saying, "Sorry, you can't sdcard upgrade").
- ADB sideload (which never worked even slightly. I always got the message, * cannot read 'update.zip'/'ota.zip'/'update.up.zip' *)
- Tried the above methods with variously named zip files, including "update, ota, and update.up".
- Tried the above methods, but wiping the cache in between processes.​4) Installed N-B01 via transfer to SD using the android updater. This time the process took a lot longer and after rebooting the phone, went through the process of optimizing apps, which it had never done before.
Ok, I think that's everything.
The only theory I can come up with is that: Something (I have no idea what, though) went wrong with the first update attempt and every subsequent attempt to update to an older version didn't work because it didn't want to overwrite newer android version files? That doesn't seem quite right to me, though, as I would assume that whatever is in the update.zip would just overwrite everything as standard, because the assumption would always be that these files are newer than the existing ones.
What would you recommend that I do next? Should I try to push through the latest N update now, then? Has this outcome helped you figure out what the problem was/is?
Whatever the case, I'm happy to finally get an update working. Thanks very much for all your help and suggestions, guys. It was much appreciated!

Categories

Resources