Database Users

Guide for updating to 4.4 KitKat

Hello,
i have been reading guides all the day and no-one had a solutions to my problems so i would like to write my own to help out others who are encountering my same issues.
----------------------------------------------------------------------------------------
This guide is for Windows and explains everything you need to update your Nexus 7 (2013) Wifi (flo) from 4.3 JSS15R to 4.4 KRT16O
----------------------------------------------------------------------------------------
1) disconnect table from USB cables if it is connected to the pc
2) go http://developer.android.com/sdk/index.html and download the SDK
3) unzip the SDK in C\
4) go in C:\adt-bundle-windows and start the SDK Manager
let is load and scan for all possible updates.. when it has finished click on Deselect All then choose only these to packages:
Tools --> Android SDK Platform Tools
Extra --> Google USB Driver
if the Android SDK Platform tools are updated then you will only have 1 package to download else you will see Install 2 Packages, click it, then select Accept Licence and click Install.. wait it to finish and then close
5) let's now download the factory image
Nexus 7 2013 only WIFI (flo) "razor" is here: https://developers.google.com/android/nexus/images#razorkrt16o and download the first link of the page (4.4 (KRT16O) Link)
Nexus 7 2013 MOBILE/LTE (deb) "razorg" is here: https://developers.google.com/android/nexus/images#razorgkrt16o and download the first link of the page (4.4 (KRT16O) Link)
for some reason the MD5 checksum and SHA1 for the flo version dont match but i read people have been able to install this image anyway (i installed the OTA so i did'nt try this install)
unzip the downloaded file and you should get a .tar file.. unzip it again and you should get a bunch of files.. i got the following ones:
1)bootloader-flo-flo-03.14.img
2)flash-all.bat
3)flash-all.sh
4)flash-base.sh
5)image-razor-krt16o.zip
place all these files in C:\adt-bundle-windows\sdk\platform-tools\
6) now let's install the drivers correctly and flash the update
First thing, keep the Nexus 7 not connected to the USB cable. Then switch it on and go into Settings --> Storage click on the Options and choose USB computer connection and make sure to have the CAMERA (PTP) selected.
Now go into developer options and select Stay Awake and USB Debugging
Go back to the home screen and connect the tablet to the PC.. let the PC try to install it by himself.
Now press WINDOWS+R and run devmgmt.msc
If you see a device called Nexus 7 with a yellow sign then right click on it and choose Update software driver.
Then select the second option (find a driver on the computer), then select the second option (choose manually a driver from a list), now click first option (show all the devices), then click Driver disk button, then browse to C:\adt-bundle-windows\sdk\extras\google\usb_driver\ and choose android_winusb.inf and do ok.
The box should fill with a device called Android Composite ADB Interface, choose that and do next
To check if you have done right do:
WINDOWS+R and run cmd
in cmd do cd.. until you get into C:\
then do cd adt-(tab) to autocompile and enter
then do cd sdk enter
cd platform-tools enter
adb.exe devices enter
the daemon should start and you should get a list of devices attached showing you a code made of numbers and letters.. this is your nexus 7.
if cmd says the device is unauthorized then look at your tablet and allow the computer to operate
let's now install the driver also in fastboot so to do this always in cmd type
adb.exe reboot-bootloader
the tablet will reboot into the bootloader and you will see an android with the open tummy
now inside the command prompt window run the following commands:
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-krt16o.zip
if everything has gone right you should have updated using the factory image and the tablet should reboot by now...
else continue reading:
if you had any issues we can then try to update through OTA which means you will need to download another package
the nexus 7 ONLY WIFI OTA: http://android.clients.google.com/p....signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
not sure if the nexus 7 LTE OTA url has been released or not because i can't find it.. if anyone has the link and can point it out to me i would be glad to add it here
download it and place it always in
C:\adt-bundle-windows\sdk\platform-tools\
rename it to something easier and redo
adb.exe sideload ota_zipfilename (enter)
everything should go fine now, so it will reboot.. configure the tablet again if it is the case
7) changing recovery
download latest recovery from here http://techerrata.com/browse/twrp2/flo
place the download img into C:\adt-bundle-windows\sdk\platform-tools\
then reboot to bootloader using adb or simply switch the table on keep vol down down
in cmd type
fastboot.exe flash recovery recoveryimagefile
8) rooting the tablet
btw sideloading the zip for rooting requires a custom recovery such as TWRP so step 7 must be achieved in order to root this way
download the latest superSU from here http://download.chainfire.eu/supersu
go into recovery mode passing by the bootloader
do another adb sideload passing this time the zip for supersu
everything done hopefully
hope this helps others which had issues with drivers and had issues with the original factory image 4.4 (KRT16O) giving the E: signature verification failed

Great guide!
The package for the link https://developers.google.com/android/nexus/images#razorkrt16o fails verification for me as well and does not install once its side loaded. So it's probably beneficial to just point to the other link.:good:

haet said:
Great guide!
The package for the link https://developers.google.com/android/nexus/images#razorkrt16o fails verification for me as well and does not install once its side loaded. So it's probably beneficial to just point to the other link.:good:
Click to expand...
Click to collapse
The factory image isn't meant to be side loaded. It needs to be installed using fastboot/bootloader.

If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.

cincibluer6 said:
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.
Click to expand...
Click to collapse
Gotcha.
There is quite a size difference between the the zip and the tgz format. Is this only because of compression format? Or is it more beneficial to flash one over the other?

cincibluer6 said:
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.
Click to expand...
Click to collapse
There are zips and then there are ZIPS
It isn't the type of archive that is critical but the contents of the zip. Zip is just a generic archive format and can store anything.
The OTA zips include specific content. In particular they are
signed by google
include an install script to handle patching, replacing files, and setting up permissions
include an install utility to run the script
include individual patch files
include whole files if the patches would be too large
have a specific directory structure where everything is supposed to be located
The factory images are also delivered in an archive. They are first archived in a tar format, which just collects a bunch of files and doesn't compress. Then they are gzip'd which is a Gnu archiver which performs a similar job to zip, but uses a different format and algorithm. Within the original tar archive there is also a zip archive. That zip contains images of the kernel, recovery, rom, user and data partitions, but it doesn't include the aforementioned items that make a zip into an OTA-style zip.
The factory images are NOT meant to be flashed in recovery. Recovery will be expecting the stuff above that OTA-style zips have. If you try to flash the factory image, the first point of failure is the signature verification fails, because it isn't signed (and even if it were signed, it wouldn't be signed in the way recovery is expecting)
So what is the difference between flashing via Recovery and the OTA-style zip vs running flash-all and the factory image?
The OTA-style flash will go and examine each file it needs to patch to make sure it is stock JSS15R. It must do this because it doesn't have the complete KRT16O file, only a patch (difference between the JSS15R and KRT16O versions of the file) that only makes sense if applied to the original JSS15R file. Even if there is a one space difference in the file, the patch would fail.
Since the OTA-style patches files (in general) it will leave files you have added in place. In particular the files installed to keep root are left in place and so are apps, sounds, images, etc. you added to the ROM (/system) partition. So you ask why do you lose root? You don't lose the root files that were installed, they are neutered because at the end of the OTA-style install, it resets the permissions in all the directories to what they are supposed to be. This drops the special permissions you gave the root files to do their job. Also the OTA-style patch does not directly overwrite your recovery. Upon first boot, there is a script that runs which builds the new recovery using the installed kernel. This is why if you immediately (prior to reboot) run the SuperSU install script after the installation of the OTA-style update.zip, you can restore root and keep your recovery. The SuperSU install script replaces the script that builds the new recovery, with its own file. It also reinstalls and sets the permissions on the root files. So in effect, you have root and have prevented stock recovery from being installed over your custom recovery.
The Recovery that you use to run the OTA-style update.zip is just special program that boots up on the linux kernel and accepts certain actions. The source code for Recovery along with the kernel is published. People can easily replace Recovery with their own custom program and that is why you have custom recoveries.
The factory images on the other hand install through the bootloader. This is a low-level program similar to BIOS on PCs. It has more limited functions and the code is proprietary. It is harder to do custom bootloaders because the source code isn't published.
The bootloader has a more limited set of functionality and you communicate with bootloader using a different program called fastboot.
The bootloader expects the files you give it to be .img files or you can give it a zip archive full of .img files. These are not patches of files like the OTA. These are complete images to replace the existing partitions. It is like a Norton Ghost image (factory image style) of your entire hard drive vs an incremental backup (OTA-style) of just the files that changed.
Given they are full images, they will overwrite the partitions completely so anything you had on them before is wiped out and overwritten.
Also full images are always larger than OTA patch-style updates because they contain everything rather than just the changed file patches.
By default they use the -w option in the fastboot install instructions, which will wipe your user data as well, but you can remove the -w option and keep your user data, though there are always a small percentage of upgrades where it won't work to keep your user data (same with the OTA).
Anyway that is just a brief summary. There are many more details and nuances I didn't list.

^^ I won't go ahead and quote you but thanks for the full on summary. I knew what .tgz was and all that (using Linux for a few years now) but I'm new to most of the Android like stuff.
Thanks for clarifying and explaining it so well.

Just gave the sideload of SuperSU a shot and was given two errors:
failed to verify whole-file signature
signature verification failed

haet said:
Just gave the sideload of SuperSU a shot and was given two errors:
failed to verify whole-file signature
signature verification failed
Click to expand...
Click to collapse
You cannot sideload the SuperSU update.zip using stock recovery because it isn't signed by Asus/Google.
It is signed, but using a generic cert.
You need to use custom recovery like TWRP or CWM to install it. You can use their menu system to choose the file or if they have sideload, you can sideload using custom recovery.

sfhub said:
You cannot sideload the SuperSU update.zip using stock recovery because it isn't signed by Asus/Google.
It is signed, but using a generic cert.
You need to use custom recovery like TWRP or CWM to install it. You can use their menu system to choose the file or if they have sideload, you can sideload using custom recovery.
Click to expand...
Click to collapse
Makes sense. Thanks for the help!

Windows 2008 server usb drivers?
This guide was great, and everything worked fine until I reboot into recovery and choose to adb sideload an image. Then, the device doesn't get recognized, and the google drivers don't work. So, I can't see the device with the ADB interface driver.
Does any have experience with this? Am I out of luck? I couldn't find anyone talking about drivers for windows server 2008 anywhere -- but usually win7 drivers work fine -- just not here.
I don't have another windows installation anywhere, so if there isn't an answer, I will just have to wait for OTA
** UPDATE **
I found some universal drivers from Koushik Dutta: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked! Then I used the OTA download (your second option), sideloaded it, and got the update. Now running KitKat, so thanks a bunch! hopefully someone else will find this driver option useful.

I'll give those universal drivers a go. Hell, I've tried everything else on the Internet with complete failure. One last try before I give up.
Sent from my SM-P600 using XDA Premium HD app

jbwray said:
This guide was great, and everything worked fine until I reboot into recovery and choose to adb sideload an image. Then, the device doesn't get recognized, and the google drivers don't work. So, I can't see the device with the ADB interface driver.
Does any have experience with this? Am I out of luck? I couldn't find anyone talking about drivers for windows server 2008 anywhere -- but usually win7 drivers work fine -- just not here.
I don't have another windows installation anywhere, so if there isn't an answer, I will just have to wait for OTA
** UPDATE **
I found some universal drivers from Koushik Dutta: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked! Then I used the OTA download (your second option), sideloaded it, and got the update. Now running KitKat, so thanks a bunch! hopefully someone else will find this driver option useful.
Click to expand...
Click to collapse
You sir are a genius (and the driver author). I had the exact problem and looked everywhere. I am low tech, too. So following these two guides;
http://phandroid.com/2013/11/13/how-to-install-kitkat-nexus-7/
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I am now on 4.4. And everything is intact. Thank you!

I also ran into Google USB driver problems after the Nexus dropped into recovery mode. So I gave up trying to use Windows 8 and switched over to using Ubuntu workstation. Getting ADB to run on Ubuntu is very easy and so flashing the Kit Kat OTA file was a breeze.
On Ubuntu there's no need to install the full SDK just to get ADB and Fastboot; the process is outlined here: http://forum.xda-developers.com/showthread.php?t=1860108. From there it's just simple command line entries from a terminal i.e. "adb devices."
I was disappointed to see Google has kept the black top and bottom bars for tablets. I usually run Teslacoil's launcher and installed their beta launcher with transparent bars a welcome relief.

doorunrun said:
I also ran into Google USB driver problems after the Nexus dropped into recovery mode. So I gave up trying to use Windows 8 and switched over to using Ubuntu workstation. Getting ADB to run on Ubuntu is very easy and so flashing the Kit Kat OTA file was a breeze.
On Ubuntu there's no need to install the full SDK just to get ADB and Fastboot; the process is outlined here: http://forum.xda-developers.com/showthread.php?t=1860108. From there it's just simple command line entries from a terminal i.e. "adb devices."
I was disappointed to see Google has kept the black top and bottom bars for tablets. I usually run Teslacoil's launcher and installed their beta launcher with transparent bars a welcome relief.
Click to expand...
Click to collapse
If you install the latest Google search apk and GEL from the nexus 5, you will have transparent nav bar.
{
"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"
}
Sent from my Nexus 7 using Tapatalk 4

Hi. This will wipe the device right? We should have a backup before proceeding?

ganstar said:
You sir are a genius (and the driver author). I had the exact problem and looked everywhere. I am low tech, too. So following these two guides;
http://phandroid.com/2013/11/13/how-to-install-kitkat-nexus-7/
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I am now on 4.4. And everything is intact. Thank you!
Click to expand...
Click to collapse
You should also know that Google has drivers as well located at http://developer.android.com/sdk/win-usb.html, which is what you would have downloaded right after you installed the SDK package.

For those who can't get their devices recognised even after doing everything correctly. Just boot the tablet and change from MTP to PTP. Worked for me.
Sent from my Nexus 7 (2013)

I was on PTP. still didn't work
BreakShadow said:
For those who can't get their devices recognised even after doing everything correctly. Just boot the tablet and change from MTP to PTP. Worked for me.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I was on PTP. Still didn't work until I found those drivers. The drivers from Google were what I was using, but they didn't support the device in fastboot mode for the version of windows I was using. (2008 server R2)

haet said:
You should also know that Google has drivers as well located at http://developer.android.com/sdk/win-usb.html, which is what you would have downloaded right after you installed the SDK package.
Click to expand...
Click to collapse
I had those, they didn't work for me, as others have noted as well.

[WORKAROUND] Bootloops due leaking handles with Xposed in Lollipop

Fix found and released:
http://forum.xda-developers.com/showthread.php?p=60454547
Downloads & instructions: http://forum.xda-developers.com/showthread.php?t=3034811
Discussion & Q&A:http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
I asked moderator to close this thread as issue was fixed by releasing new version of Xposed framework. Please send your further questions and post to respective thread.
This thread is about workaround found for bootloops of Xposed in XPERIA family Lollipop. Because of development progress, I have decided to remove historical development, you can see it here:
LATEST VERSION will be always posted at the END of this post
PLEASE READ INSTRUCTIONS .... The attachment IS NOT flashable!!! For flashables see EDIT 5 and bellow...
I hope I can present some good news for users with locked bootloaders who are getting bootloops with Xposed and Lollipop.
This is still continuous WIP. Know what you do, this is a development thread.
For time being, most complete solution by my opinion was made by @mionica, see EDIT 6 and hist post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123? and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
As you may already know, we have find out, that some undetected error is causing system to bootloop, if too many applications are installed.
Exact numbers are varying between different ROMs and devices, generally the maximum number of apps is about 320-330.
Debloating (uninstalling unnecessary apps) helps, but remains limiting and for many frustrating. After a research, we have found out,
that there is probably a bug, that is causing many files being left open when booting Lollipop with Xposed.
Users on unlocked bootloader may modify certain kernel parameters to raise number of open files. This can not be done on Locked Bootloader.
After some research and hours of experiments, I found a way, how to change the filelimit for Zygote and subsequent processes. Therefore every child of zygote (hence every app etc.) will inherit raised open files limit from 1024 to 4096.
This change should work on all 5.0 compatible system, not only XPERIAs, however I only tested it on Z3 D6603 fw 690. But the modification
is done on Linux system level, therefore it should teoretically work just everywhere... It should work also on Locked bootloaders as well.
The principle is easy, however implementation was a tricky, because of lack of native linux utils support on Android and fact that we can not
easily modify booting behaviour. But gladly enough we have XZDualRecovery (gret thanks @[NUT])....
XZDualRecovery enables to call init scripts on startup. I have created a startup script that waits for zygote process to come up, and calls
external program that changes open file limits for that process. This external program is compiled by me from source provided by http://lzone.de/cheat-sheet/ulimit
Prerequisities: Functional XZDualRecovery or other form of init.d support.
Installation:
Extract downloaded ZIP file, it contains:
flimit-binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
remount /system rw (mount -o remount,rw /system)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
test run installation:
Code:
su
/data/flimit/flimit $(pgrep zygote)
output should be:
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=1024; hard=4096
New limits: soft=4096; hard=4096
If not, check permissions etc.
Check script by running:
Code:
su
sh /system/etc/init.d/01_flimit
it should now give output (if you succesfully ran /data/flimit/flimit....):
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=4096; hard=4096
New limits: soft=4096; hard=4096
reboot
Thats all. Now you can install and update lot more applications. Now I have about 455 packages reported by pm list packages and no bootloop.
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
EDIT:Please let me know, if you had to modify the script or instructions to work on your device, so I can perhaps make better or more universal version. Thank you guys.
EDIT 2:While this workaround makes it possible to run Xposed on untouched vanilla Stock ROM, you may still consider debloating it, as debloating will make run your device more smoothly and saves battery. Guys who made debloating scripts made significant efforts in identifying which apps can be safely removed without harming any significant functionality.
EDIT 3:The ZIP is NOT flashable, follow instructions ^^^^ --- buddy @McBane87 is developing flashable version.
EDIT 4:Buddy @nurps found a bug causing Opera browser to quit upon starting. @mionica proposed lowering softlimits for open files to 2048 from 4096 in first version of script. Version 1.1 is released.
EDIT 5:Buddy @McBane87 created customized flashable version of this workaround, so you can flash it from recovery if you struggle with bootloops, dont like to wait fro 300apps to optimize after Dalvik wipe and mess with adb/terminal..
http://forum.xda-developers.com/showthread.php?p=60276913
EDIT 6:Buddy @mionica published another flashable zip. It is complete installer for the workaround, so far most sofisticated workaround from system point of view. The uninstaller completely removes Xposed if you are too tired of it and forgot to make backup Files are bellow, for instructions etc. check it out on http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123 and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
Changelog:
v1: Initial release
v1.1: Changed limits to 2048 from 4096 as high limits caused Opera Webbrowsers to crash
v2.0 Reference script - for production please flash @mionica version of flashable, my script is published for educational purposes. added mionicas mod to detect only changed limits and subsequently remove only those that are child of zygote
***************************************
I would like to thank mainly to @[NUT] and to guys who made significant effort with debloating, made other discoveries or were an inspiration
for me, including but not limited to @serajr @moly82 @AndroPlus (for his work on file limits in kernel) @redincali and of course to @rovo89
for his Xposed framework. My apologies if I forgot someone, PM me, its 2 o'clock in morning
or in this post http://forum.xda-developers.com/showpost.php?p=60349914&postcount=354
While I have developed initial version (see history), other guys (mainly @mionica and @McBane87) greatly enhanced and redeveloped whole thing.
Current development version and downloadable files you can always find in @mionica post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123
@mionica managed to analyze boot process on both ROMs with and without Xposed and came to conclusion that leaks are caused by Xposed process leaking open file handles, see here http://forum.xda-developers.com/showpost.php?p=60373854&postcount=417
There is a current version of the workaround fix (see above), that seems to be the last possible, before Xposed will be released with patch addressing that issue. Good news is that thanks to @mionica precise analysis, @rovo89 - developer of Xposed is already aware of the problem nad it´s cause.
Recommended installation steps:
by @mionica
Anybody who is still having any kind of issues, for whatever reason, please do the following:
get into TWRP;
install, in this order, without rebooting:
xposed-uninstall-v1.1.zip
If you don't have an sd card, you'll need to reboot once after the uninstall .zip, boot the system normally, then get back in the recovery and install the other 3. This only applies to people who don't use an SD card
xzdr-busybox-enable-v1.0.zip
xposed-sdk21-arm-date.zip
xposed-leakplug-v1.2.zip
copy the logs to the PC, over USB:
uninstall_xposed.log
install_busybox.log
install_leakplug.log
each of the 3 zip's will tell you where it saved the log (it's usually the external sdcard)
reboot to system
Thanks in advance for not asking any questions about whether you have to do any of these steps; yes, you have to.
Click to expand...
Click to collapse
If you follow other instructions than provided by @mionica please get then support from someone else than him.
The basic idea behind is that Xposed bootloops because of it exhausted resources available due to probably internal bug. The workaround basically provides higher limits for open files during boot and restores previous limits after device has booted. The latest flashable installer is very advanced and automates the installation, including necessary checks for proper XZDR configuration, busybox etc.
When you experience bootloops after installing Xposed, or you had Xposed working and it started to bootloop after you have installed new app or upgraded a system app, simply reboot to recovery and flash the zip. No need to wipe anything.
When installing new, I recommend flashing this zip first, then install Xposed usual way (flash, wipe, reboot, install Xposed apk, install modules).
Be aware that while the workaround works for about 80% of cases, there are people who have lots of applications or heavily modified system, experiencing random reboots. Cause is under investiogation, but most probably is in Xposed itself.

Excellent work friend @ondrejvaroscak. Congrats! Awesome

Was waiting a long time for this! Thanks man! working perfectly.

Working perfectly on D6603, thanks

I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button

Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?

Thanks Bro , Very Nice !!
Perfect Work !!

Z1, C6903
Thank you for this great solution, works on Z1.

NetSkill said:
I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button
Click to expand...
Click to collapse
Unless I will be blessed with some debugging skills, I have no clue... I think limit is just much higher. Once you reach limit you can simply edit script and change two numbers...
Yes, now regular reboot works.
Sent from my D6603 using XDA Free mobile app

norti said:
Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?
Click to expand...
Click to collapse
I think it will take time, because first @rovo89 would probably want to investigate, how much is it a bug, a constellation of coincidences and so on. I am not sure, if the same bootloops appear only on XPERIAs or it is a phenomenon on other brands as well... And given the fact, that big number of Samsungs can not run Xposed at all, maybe he will try to solve that Samsung puzzle as priority. But that is only guess..

Working on fully setup 5.02 on Z2 thanks.

ondrejvaroscak said:
Installation:
Extract downloaded ZIP file, it contains:
flimit - binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
Click to expand...
Click to collapse
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa

hispanico957 said:
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa
Click to expand...
Click to collapse
Any recovery that supports init.d and byeselinux. So if you find this two settings in your XZDR.prop, you just enable them by setting "true".
I tested with 2.8.12,
XZDR.prop is located in /sdcard1 so its External SD card. If no SD card, then its located in /cache.
/data/limit you create absolutely, it means in / is folder data (that already exists) and you create flimit in /data, so:
Code:
adb shell
su
mkdir /data/flimit
byeselinux you enable by setting "dr.keep.byeselinux=true" in XZDR.prop (it may be set to false by default depending on version fo XZDR you have).

Ok fine... for verify all you said:
{
"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"
}
dont find ? where i wrong ??? the folder and file are present
Thank
Hispa
P.S.
Whe you said :
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
Click to expand...
Click to collapse
i mean to pu dr.initd.active=false ??
and last after all i can install xposed over .726 odexed ?

hispanico957 said:
Ok fine... for verify all you said:
su
/data/flimit/flimit $(pgrep zygote)
this command from ADB ?
Thank
Hispa
Click to expand...
Click to collapse
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app

Great thanks

ondrejvaroscak said:
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Thank solved but see please my post #14
Hispa

In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !

Pandemic said:
In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
Click to expand...
Click to collapse
+1 i too cannot find thet line

hispanico957 said:
Ok fine... for verify all you said:
dont find ? where i wrong ??? the folder and file are present
Click to expand...
Click to collapse
can you run "ls -l /data/flimit/*" and paste output to reply?
Whe you said :
i mean to pu dr.initd.active=false ??
Click to expand...
Click to collapse
Exactly, when you put dr.initd.active=false and have full stock, it should again bootloop. Then you replace the XZDR.prop file with version with init.d enabled and it should boot normally again.
and last after all i can install xposed over .726 odexed ?
Click to expand...
Click to collapse
I think without any problem. Deodexing has nothing to do with working Xposed, but it is may be necessary for some modules (Gravitybox?)?

[GUIDE] Lenovo Yoga Tab 3 8 / YT3-850F - How to unlock and root

Hello there!
After searching the internet up and down for a guide how to root this device and having found nothing, i decided to do it by myself - with success.
Here i want to share my way of unlocking this device for others:
Warning: Backup all your data first, as the unlocking of the device will reset it to factory defaults!
This is a guide for people who are aware of the risks of flashing, it lies completely in your own responsibility!
Before doing anything at all, read this post carefuly!
Requirements:
Lenovo Yoga Tab 3 8 / YT3-850F (obviously)
Having ADB and fastboot installed.
Getting a proper twrp version & Chainfires SuperSU
Links:
15 seconds ADB Installer v1.4.3: https://forum.xda-developers.com/showthread.php?t=2588979
Fitting twrp: http://www.htcmania.com/showthread.php?t=1291696
The thread's in spanish, i used google translate.
Chainfires SuperSU: https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
This one worked for me, first i flashed an older version and got stuck within a bootloop. Reflashing this newer version and wiping all caches within twrp helped.
Step by step:
1. First you want to unlock the "developer options" in your settings.
To do this go into settings -> about this device and tap on "BuildNumber" 7 times.
After two taps, a small pop up notification should appear saying "you are now X steps away from being a developer" with a number that counts down with every additional tap.
unlocked developer options.
2. Now you can go into the developer options and activate both "USB debugging" and "OEM Unlock".
Both are needed for beeing able to flash anything onto your device in the first place.
3. Install Lenovos USB drivers & the 15 seconds ADB Installer v1.4.3
4. Boot your device into Recovery Mode. To do this, turn it on while holding both the On-Button as well as Volume-Up.
Inside the Recovery console select "boot into bootloader" with the volume keys and confirm with the on button.
See: https://forum.xda-developers.com/wiki/Lenovo_Yoga_Tab_3_-_8"-_YT3-850F
5. Connect your Tablet to your PC via USB.
Now open a console prompt on your PC and Type "fastboot oem unlock" (without the quotes of course).
This should unlock the bootloader for flashing.
6. Flash the twrp image supplied in the links section.
For Android 6 extract the "TWRP 3.0.2.7 (a)" folder from the downloaded archive, for Android 5 the "TWRP 2.8.7.7" folder.
Inside this folder, there should be a folder called "img", enter it.
Inside the img folder open a new console by “Shift + Right click” on any empty white space inside the folder and then select “Open command window here” from the context menu.
Now type "fastboot twrp.img", this should install twrp onto your device.
Now type "fastboot reboot" to reboot your device.
See: http://rootmygalaxy.net/install-twrp-recovery-via-fastboot/
Note: I have done this step on Android 6, so noe guarantee for Android 5.
7. You can enter twrp the same way now like the original recovery menu.
It will boot up in russian language, but you can change it to english or some other choices:
{
"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"
}
8. It is advisable that you do a backup of your system files now with twrp, in case something goes wrong with SuperSU.
9. Copy the zip of Chainfires SuperSU onto your Device.
Within twrp you can now install SuperSU, which will root your device.
10. Done! Enjoy your newly rootet device!
Final words: To the moderators: Feel free to edit this thread for better understandability.

Hi, would you know if this method also works for model Lenovo Yoga Tab 3 10.1 / YT3-X50F? Thanks in advance.

ale_aas said:
Hi, would you know if this method also works for model Lenovo Yoga Tab 3 10.1 / YT3-X50F? Thanks in advance.
Click to expand...
Click to collapse
I have the same model, did it work for you?

fede01_8 said:
I have the same model, did it work for you?
Click to expand...
Click to collapse
Hi, please, feel free to follow the steps in this post: https://forum.xda-developers.com/th...e-yoga-tab-3-10-1-yt3-x50f-twrp-root-t3695297
I just uploaded it, and work fine for me.

Thanks so much!
Thanks So much, yYour guide worked successfully, but I was not very clear how to install the TWRP recovery, so I had to install it manually using the guide on this page:
http://www.techmoviles.com/instalar-twrp-recovery-en-depositivos-android-mediante-fastboot/
In this guide is more detailed, it can serve any other also
regards! very thankful.
PD: My YogaTab3 is of model YT3-850F, in case someone has doubts
drwakey said:
Hello there!
After searching the internet up and down for a guide how to root this device and having found nothing, i decided to do it by myself - with success.
Here i want to share my way of unlocking this device for others:
Warning: Backup all your data first, as the unlocking of the device will reset it to factory defaults!
This is a guide for people who are aware of the risks of flashing, it lies completely in your own responsibility!
Before doing anything at all, read this post carefuly!
Requirements:
Lenovo Yoga Tab 3 8 / YT3-850F (obviously)
Having ADB and fastboot installed.
Getting a proper twrp version & Chainfires SuperSU
Links:
15 seconds ADB Installer v1.4.3: https://forum.xda-developers.com/showthread.php?t=2588979
Fitting twrp: http://www.htcmania.com/showthread.php?t=1291696
The thread's in spanish, i used google translate.
Chainfires SuperSU: https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
This one worked for me, first i flashed an older version and got stuck within a bootloop. Reflashing this newer version and wiping all caches within twrp helped.
Step by step:
1. First you want to unlock the "developer options" in your settings.
To do this go into settings -> about this device and tap on "BuildNumber" 7 times.
After two taps, a small pop up notification should appear saying "you are now X steps away from being a developer" with a number that counts down with every additional tap.
unlocked developer options.
2. Now you can go into the developer options and activate both "USB debugging" and "OEM Unlock".
Both are needed for beeing able to flash anything onto your device in the first place.
3. Install Lenovos USB drivers & the 15 seconds ADB Installer v1.4.3
4. Boot your device into Recovery Mode. To do this, turn it on while holding both the On-Button as well as Volume-Up.
Inside the Recovery console select "boot into bootloader" with the volume keys and confirm with the on button.
See: https://forum.xda-developers.com/wiki/Lenovo_Yoga_Tab_3_-_8"-_YT3-850F
5. Connect your Tablet to your PC via USB.
Now open a console prompt on your PC and Type "fastboot oem unlock" (without the quotes of course).
This should unlock the bootloader for flashing.
6. Flash the twrp image supplied in the links section.
For Android 6 extract the "TWRP 3.0.2.7 (a)" folder from the downloaded archive, for Android 5 the "TWRP 2.8.7.7" folder.
Inside this folder, there should be a folder called "img", enter it.
Inside the img folder open a new console by “Shift + Right click” on any empty white space inside the folder and then select “Open command window here” from the context menu.
Now type "fastboot twrp.img", this should install twrp onto your device.
Now type "fastboot reboot" to reboot your device.
See: http://rootmygalaxy.net/install-twrp-recovery-via-fastboot/
Note: I have done this step on Android 6, so noe guarantee for Android 5.
7. You can enter twrp the same way now like the original recovery menu.
It will boot up in russian language, but you can change it to english or some other choices:
8. It is advisable that you do a backup of your system files now with twrp, in case something goes wrong with SuperSU.
9. Copy the zip of Chainfires SuperSU onto your Device.
Within twrp you can now install SuperSU, which will root your device.
10. Done! Enjoy your newly rootet device!
Final words: To the moderators: Feel free to edit this thread for better understandability.
Click to expand...
Click to collapse

what about yt3-850m, anyone tried this on it?

thank you for this guide, but before we delve in, is there any custom rom we could flash?
my device is at 6.0.1 from telco, so unless there are nougat/oreo/pie roms out there, having a rooted device has little benefit?

ewong3 said:
thank you for this guide, but before we delve in, is there any custom rom we could flash?
my device is at 6.0.1 from telco, so unless there are nougat/oreo/pie roms out there, having a rooted device has little benefit?
Click to expand...
Click to collapse
It would facilitate the installation of Magisk though which in many ways is better than custom rom installation :good:

I did this same thing, but replaced supersu with magisk. Similar process, but rather than flashing supersu from twrp, just download magisk.apk from github, rename to magisk.zip, and flash with twrp.
Upon reboot I still had to install the magisk apk manually, as the magisk app didn't show up. Once installed, I had to go through one more step in the magisk app to reflash it properly, using the direct install method.
Instructions to install twrp (google translated from the thread linked above):
Original post (Translated)​
A month ago I bought this tablet and these are the things I did to it and that can help you
Before that, thanks to:
lenovo-forums.ru - Where I got everything from
SevenMaxs - User of that forum, who made the TWRP
baikal0912 and Steaven - From that forum too, for posting the Roms for the tablet (5.1 and 6.0 respectively)
Note 1 from OP: If you already updated to the latest version without touching anything, you only need to do the first 2 points (if you want to)
Note 2: In case you have touched and cannot update, continue from the point that you have not done (bootloader, twrp or update)
1. Unlock Bootloader​
Activate developer options
For this you have to go to "Settings -> About the tablet". Once here, you have to touch several times on "Compilation number", until it says "You are already a programmer"
Enable debugging and unlock permissions
Go to "Developer Options" and check the boxes for "OEM Unlocking" and "USB debugging"
Connect tablet to your computer
Download file and unzip it
01. Bootloader
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Run Unlock_Bootloader.bat
Note from Gramdalf: I was on linux, but was still able to do this - just look at the `.bat` file and enter the fastboot/adb commands as they are.
Review the tablet, as a code will appear and ask for permission to activate debugging, select 'Remember this computer's RSA key'
2. Install TWRP​
Connect tablet to PC
download file
02. TWRP
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Install
-If it comes with Android 5 from the factory, apply TWRP 2.8.7.7.
-If it comes with Android 6, install TWRP 3.0.2.7 (a)
You only have to open the .bat that is in each folder.
Note from Gramdalf: Same thing, just enter the commands as they are in the .bat script, making sure that you are in the correct directory. The only difference with this is that with the `tools\fastboot -i 0x17ef flash recovery img\twrp.img` command, `-i` wasn't an available option - I was able to run it just fine without it. The recovery flashed correctly, but just keep in mind that I'm not sure if there are any lasting side effects that I am unaware of.
-If you have Android 5 and then update to Android 6, you have to install TWRP 2.8.7.7 and then you can flash 3.0.2.7 which is in the "TWRP 3.0.2.7 (b)" folder from the same TWRP (it's a zip )
Note from OP: TWRP says 850M, but it is compatible with it. There is a version from someone on XDA who tweaked a few things for the 850F, but I haven't tested it.
Note from Gramdalf: I didn't do the following part in my case, but it's there just in case you want it
3. Firmware​
Android 5.1
YT3-850F_USR_S000025_1510160911_Q1241_ROW_factory_update
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Android 6
YT3-850F_000109_161226_ROW_otafull
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Just go into TWRP and flash.
Note from OP: When upgrading from 5 to 6, the bootloader is locked again and TWRP is removed, you need to do step 1 and 2 again.
Root and Xposed
Enter TWRP
Flash SuperSU
Restart
Check that it is rooted
Enter TWRP
Flash Xposed
Restart
Install the Xposed APK
Verify that it has been installed correctly
04. Programas
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

[Guide] Tired of EMUI ? Here's a full guide on how to install a Treble Rom

So I was tired of EMUI, the UI design isn't really that bad but it really clashed with Android's Material Design, so since our Mate 9 is Treble compatible, I decided to try a few Treble ROMs. After many fails and factory resets, I finally settled on Havoc-OS. Here I made a guide on how to switch to a Treble Rom.
So a few things to note :
There's no (fully) compatible TWRP recovery for Kirin devices. Either they work but cannot flash OpenGApps or they simply don't work with Treble ROMs.
Huawei's eRecovery seems to work. For me at least, it didn't work before. So as usual, BACKUP ALL OF YOUR DATA(Titanium Backup or HiSuite for apps if needed). You can also use TWRP with stock EMUI if you want to backup your partitions in case something goes really bad.
Make sure you're using stock kernel, ramdisk and recovery_ramdisk before starting anything.
A Micro SD card is optional but useful for restoring things or if you don't want to transfer all of your backup data to your PC
USB Debugging isn't really needed.
-------------------Requirements-------------------
- Your phone, obviously. Has to be a Mate 9 (Pro) updated to Android 8.0 Oreo.
- An unlocked bootloader (Since Huawei stopped giving unlock codes, I can't help you on that one. Sorry boys)
- A PC and a USB Type-C cable.
-------------------A. First things first-------------------
Enable OEM Unlocking
An easy thing to do, otherwise you won't be able to flash anything on your phone (FRP will be "Lock" on bootloader screen). You may think that this is kind of a mandatory thing to do since you've unlocked your bootloader, but you can get it back to disabled and greyed out anytime, so here's a reminder.
1. Enable developer options by going to Settings > System > About Phone and taping multiple times on Build Number
{
"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"
}
2. Once that's done, go to Developer Options and enable OEM Unlocking.
-------------------B. Downloads-------------------
1. Download and install Minimal ADB
Click here to download Minimal ADB
2. Download your ROM, right now there are two fully compatible ROMs :
- OpenKirin Builds : https://openkirin.net/download/
- Havoc-OS : https://forum.xda-developers.com/mate-9/development/rom-havoc-os-t3826470
You'll get an img file that you must put inside where you installed Minimal ADB.
3a. For later : Download Huawei Firmware Finder and Huawei Update Extractor
- Huawei Firmware Finder
- Huawei Update Extractor > If you're not running Windows (Mac, Linux) (Thanks to irony_delerium)
- Also download Magisk Manager (This is an APK)
--- OR ---
3b. Download this patched Ramdisk with Magisk included so that you don't have to download all of the above. CREATED WITH BUILD NUMBER MHA-L29 8.0.0.370(C432). USE AT YOUR OWN RISK IF IT DOESN'T EXACTLY MATCH YOUR PHONE BUILD.
Here (name is patched_boot.img)
-------------------C. Installation-------------------
Now that you've got your Rom img and Minimal ADB, we can start installing it.
1. Turn off your phone.
2. Plug your phone into your PC AND hold down the volume down button until you get a (terrible) white screen saying you're in fastboot&rescue mode.
3a. Open a command prompt (with admin rights if possible) on your PC and get to your Minimal ADB directory. By default, it should look like this :
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
3b. If you installed Minimal ADB on a different drive, then type this :
Code:
cd /d {DRIVELETTER}:/{MINIMAL ADB DIRECTORY/}
4. Make sure your phone is detected by typing :
Code:
fastboot devices
This should show up.
5. Now you can start flashing your ROM by typing :
Code:
fastboot flash system {IMGFILE}.img
Your ROM should start flashing with the message 'target reported max download size of 494927872 bytes'
It should take a minute.
Once you see 'finished. total time: times', that means your ROM has been flashed.
Don't reboot just yet. Things won't work
6. Reboot to recovery by turning off your phone (hold down power button for ~5 seconds) and holding volume up.
7. Now that you are in EMUI recovery, do the following :
- Wipe cache
- Wipe data/factory reset
You MUSTdo this otherwise you will have multiple issues.
8. You're done for the installation. Now reboot to system and start your phone first config (again).
-------------------D. Root-------------------
Your Treble Rom isn't rooted by default. But the Treble Rom itself triggers the SafetyNet flag, which means even if your phone is super clean, it is not certified. So it is obviously completely optional, by it is extremely recommended to install Magisk.
If you downloaded the patched_boot.img file in the attachment
The install process will be extremely easy. It will install Magisk 16.7 (only Beta works with Treble right now). So all you have to do is :
Get to fastboot mode by turning off your phone, plugging it to your PC while holding volume down button. Then, type the following command in the same command prompt window :
Code:
fastboot flash recovery_ramdisk patched_boot.img
It should take around 5 seconds. Now you can reboot and download Magisk Manager. But Safetynet will still trigger (if it doesn't, tell me). You'll have to follow E. SAFETYNET.
If you're not using the attachment
1. Check your phone Android version and build number. It is in Settings > About phone. Write it down, you'll need it.
2. (Install and) Open Huawei Firmware Finder. Get in the 'Common Base' tab and type in your phone build number.
3. Find the matching build number in the list. Make sure its type is 'FullOTA-MF' and its size is 2Go+. Then click on the blue link in the 'Filelist' column. Copy paste the first (ending with 'update.zip') in your browser to download the zip file. It should take some time.
4. Once it's downloaded, open it with 7Zip/WinRar and extract the file named 'UPDATE.APP'.
5. Open Huawei Update Extractor, go to the Settings tab and untick everything.
6. Now, go to the Extract tab and click on the dots on the right and select your extracted 'UPDATE.APP'. A ton of files should appear.
7. Right click on 'RAMDISK', and 'Extract selected'. Put it somewhere on your PC, you'll need it.
8. Plug your phone on your computer and put your RAMDISK.IMG in a folder on your phone.
9. On your phone, download and install Magisk Manager. If it prompts you to do so, do not install it. Then go to Settings tab and change 'Update Channel' to 'Beta'.
10. Now go back and tap 'Install', then choose 'Patch Boot Image File' and select your RAMDISK.IMG that you transferred to your phone. Then let Magisk do its thing.
11. Once it's done, on your PC, go to Your Phone/Internal Store/MagiskManager, and transfer the file 'patched_boot.img' to your Minimal ADB folder.
12. Turn off your phone and get to fastboot mode. You know how to do it now, don't you ?
13. In the same command prompt on your PC, type :
Code:
fastboot flash recovery_ramdisk patched_boot.img
It should take around 5 seconds. Now you can reboot and BAM, you're rooted. But Safetynet will still trigger (if it doesn't, tell me). You'll have to follow E. SAFETYNET.
-------------------E. SafetyNet-------------------
Magisk may be installed, but with a Treble Rom, SafetyNet should trigger anyway. So you'll have to do a few things.
1. In Magisk Manager, go to the Downloads tab and search for 'MagiskHide Props Config'. Install it, then reboot your phone.
2a. Once your phone is rebooted, download Terminal Emulator on the Play Store
--- OR ---
2b. Go to developer options and enable 'Local Terminal'.
3. Open your terminal, then type :
Code:
su
(Accept root request)
Code:
props
Things should appear. Woah.
4. Type 1 (Edit device fingerprint), then f, then choose a vendor and a model by typing the right number, then press y. Don't reboot yet (press n)
5. Type 6 (Script settings), then 1, then y. Now you can reboot (press y). Once it's done, make sure that 'boot stage' is 'currently post-fs-data'. Otherwise SafetyNet will still trigger.
THERE YOU GO ! Your phone should pass SafetyNet. You can check this by trying to search for the Netflix app on the Play Store or going into the Play Store settings and making sure your device is Certified'.
If you have any question/bug, do ask/report all of dem to me.

I haven't rooted or done anything with this device since I've bought it coming from all Samsung devices previously. This guide is awesome! Nice work!

About Firmware Finder:
You don't need to install this as a desktop app:
http://pro-teammt.ru/firmware-database/
The page itself is in Russian, but Chrome usually offers to automatically translate, and it's not terribly complex anyway.
There is also the Firmware Finder app in Google Play. Either work.
(This also makes it accessible to those of us who don't run windows as a primary desktop.)
--
If you're not on Windows (Linux, Mac, BSD):
The following GitHub repo contains a Perl script for extracting the contents of UPDATE.APP:
https://github.com/marcominetti/split_updata.pl
Run:
splitupdate UPDATE.APP
The full image will be extracted into a subdirectory "output".

i install Havoc via fastboot ok
but i return stock huawei , install system.img of update.app ok
but now after install stock huawei system my phone lost language portuguese Brazil ...no more all languages

irony_delerium said:
About Firmware Finder:
You don't need to install this as a desktop app:
http://pro-teammt.ru/firmware-database/
The page itself is in Russian, but Chrome usually offers to automatically translate, and it's not terribly complex anyway.
There is also the Firmware Finder app in Google Play. Either work.
(This also makes it accessible to those of us who don't run windows as a primary desktop.)
--
If you're not on Windows (Linux, Mac, BSD):
The following GitHub repo contains a Perl script for extracting the contents of UPDATE.APP:
https://github.com/marcominetti/split_updata.pl
Run:
splitupdate UPDATE.APP
The full image will be extracted into a subdirectory "output".
Click to expand...
Click to collapse
Yup, I'm aware of the Play Store app, but IMO, having everything directly on your PC is more convenient. Also what you said is useful for people not running Windows, so kudos to you for that.

aureliomilitao said:
i install Havoc via fastboot ok
but i return stock huawei , install system.img of update.app ok
but now after install stock huawei system my phone lost language portuguese Brazil ...no more all languages
Click to expand...
Click to collapse
Huh, that's a strange issue. I'd suggest you do this :
- If you don't care about all you data being lost (you got a backup), get to Huawei eRecovery by rebooting your phone and holding volume up button for 3 seconds on the screen saying your bootloader has been unlocked. Then follow the indications on screen, by choosing 'Download latest version'
- The fact that you can't choose any language is odd, as all languages are included in system.img. So you probably got a... kind of faulty system.img from your update.app, which is also strange.

Deytron said:
Huh, that's a strange issue. I'd suggest you do this :
- If you don't care about all you data being lost (you got a backup), get to Huawei eRecovery by rebooting your phone and holding volume up button for 3 seconds on the screen saying your bootloader has been unlocked. Then follow the indications on screen, by choosing 'Download latest version'
- The fact that you can't choose any language is odd, as all languages are included in system.img. So you probably got a... kind of faulty system.img from your update.app, which is also strange.
Click to expand...
Click to collapse
i extract system.img in update.app ...and lost Brazil language

aureliomilitao said:
i extract system.img in update.app ...and lost Brazil language
Click to expand...
Click to collapse
Well... I'm sorry, but I can't help you on that one. It just doesn't make sense. You can't "lose" a language. As I said, try to use Huawei eRecovery to completely restore your phone.

Solved

How To Guide [GUIDE][HowTo]Pushing an OTA.zip Update with ADB Sideload - via Recovery - via Local Update

ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK.
THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!)
GOOD CONTINUATION TO ALL
Installing an OTA.zip Update with ADB Sideload​
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine - ​
Click to expand...
Click to collapse
In this thread you will find different ways to install an OTA update :
Via ADB SIDELOAD (this post) - Via Recovery Mode - Via Local Upgrade
​I am writing this tutorial on ADB Sideload, one more on this topic, in order to be able to push an OTA Zip update, which for some reason could not be done properly.
Sometimes manufacturers allow users to make links or zip files of OTA updates available to other users. Once you have downloaded the OTA zip file, you will need this tutorial to proceed with the installation.
I borrowed the first two screenshots from the web so that I could explain clearly with pictures.
In the end it is very simple and requires little command line knowledge. But you will need to check some things:
- Firmware stock
- Unmodified system partition
- Third party apps like Magisk, Xposed Framework, and as a precaution TWRP Recovery should not be installed on your smartphone
Before starting, here is the list of prerequisites to perform the sideloading of the OTA package.
1. Have a backup of your data, even if theoretically performing a sideload will not erase your data,
2. Download the USB Drivers from the manufacturer, or the latest one from Google ( Link )
3. If you haven't already done so, you must download and install Android SDK Platform-tools (platform-tools_r33.0.2-windows.zip)
4. Don't forget to push on this folder "platform-tools" the file named "Global full Nothing OS 1.1.0.zip" - for example- that you need
4. And finally you will have to activate the USB debugging of your Phone(1) : to do so, you have to go to : Settings => System => Advanced => Type 7 times on the build number => once done, a pop-up will appear and will tell you that you have become a "Developer" => On some devices you will have to type in the Pin code.
5. Once you have become a developer => go back to System => Developer Options => Enable the USB Debug toggle
6. That's it if you are ready to do a Sideload, but also other operations!
{
"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"
}
​
These prerequisites are essential for this and a number of other operations.
You are ready, the tension is rising! You will succeed!
To do this, you must reboot your Phone(1) into the standard recovery system and you have 2 ways to reboot into Recovery.
1. You can use the hardware key combination specific to your smartphone.
2. Or use the ADB command
Booting into Recovery Stock mode with the ADB command
You go to the start screen of your PC and in the search bar you type:
Code:
cmd
and then press Enter. The command prompt starts.
Depending on where you have placed your "Platform-tools" folder you type:
Code:
C:\WINDOWS\system32>cd c:\platform-tools
and you should see on your command line screen
Code:
c:\platform-tools>
Once you are in your Platform-tools folder, connect your smartphone to your PC, making sure that USb debugging is effective.
Type the following command: adb devices and you should see the identification of your smartphone
When you run an ADB command, you should see an RSA key prompt on your smartphone screen asking you to allow USB debugging. Press OK to allow it.​
Type the following command: adb reboot recovery​
Then the command: adb sideload "file name".zip - For the example, I typed the full name of the file, but you can rename the file shorter like "nothing_ota".zip
That's it, normally the installation is started and you just have to wait for the update to be installed on your device. Once the installation is successful, you can restart your device.
I hope this tutorial has helped you to push an OTA.zip update.
Go ahead now

Installation via recovery mode​
The recovery mode of the Phone(1) is similar to that of the Google Pixel. This allows you to easily sideload the update packages via the recovery interface.
To perform this process, here are the steps and requirements:
Have downloaded the .zip file of the update to your computer
Your Phone(1) must be recognised by the ADB command on your computer
The Process:
Go to your Shell terminal, then run the recognition command:
Code:
adb devices
then the command :
Code:
adb reboot recovery
On your Phone(1) screen, you should see this "No command"
While pressing the Power button, press the Volume Up button then release both buttons quickly. The Android recovery menu should be visible.
Nothing Phone 1 recovery mode
On your Phone(1) screen, select the option: Apply update from ADB.
On your computer, run the command:
Code:
adb devices
This should return the serial number of the device with the 'sideload' next to its name, indicating that your device is connected to the computer in sideload mode.
On your computer, run the command:
Code:
adb sideload "filename".zip
The "filename" part should be replaced with the full path, followed by the name of the file downloaded in step 1.
The update will be installed on your phone.
Once the installation is complete, select "Reboot system now" on your phone to reboot into the new version.
Well done, you have installed the new update of Nothing OS to your Phone(1) with success
To date I still haven't received my phone(1). Once I have it in my hands, I will make screenshots about this tutorial.

Install OTA using Local Upgrade method​
Create a folder named “ota” (without the quotes) at the root of the internal storage. Meaning outside every folder.
Copy the OTA update ZIP file from above to that folder.
Open the phone app and Dial ##682##
This should launch an offline update tool.
The tool will scan for an OTA file from internal storage and install it.
If that fails, you can manually browse for the OTA package.
After selecting the OTA file, the wizard will apply the update.
Reboot the device and you are on the latest firmware.

Reserved 3

I think also after update, reboot, redo the step and sideload also Magisk for keep root

Pho3nX said:
I think also after update, reboot, redo the step and sideload also Magisk for keep root
Click to expand...
Click to collapse
Yes I agree, but those tutos are for everyone, and everyone doesn't rooted his smartphone like us
So I won't confuse them

hello, thanks for the guide, when I do all the steps without any problems and reboot, it opens with the old version, where could I be doing wrong?

This will work to downgrade the phone also?

pankspoo said:
This will work to downgrade the phone also?
Click to expand...
Click to collapse
no, np1 has a very strict anti rollback check. I don't suggest to downgrade this phone

sh4tteredd said:
no, np1 has a very strict anti rollback check. I don't suggest to downgrade this phone
Click to expand...
Click to collapse
So we can use your Windows tool to downgrade ?

pankspoo said:
So we can use your Windows tool to downgrade ?
Click to expand...
Click to collapse
I won't downgrade this phone at all. Btw maybe I'm wrong and it can work but I'm not sure and I don't suggest to do it

Hi, I am currently trying to update from Nothing OS 1.1.3 to 1.1.4 but i keep receiving this error even though i have uninstalled magisk, didn't modify my system partition and have a stock firmware. The phone is still able to boot correctly after this failed installation but i cannot flash the new update.

demiii said:
Hi, I am currently trying to update from Nothing OS 1.1.3 to 1.1.4 but i keep receiving this error even though i have uninstalled magisk, didn't modify my system partition and have a stock firmware. The phone is still able to boot correctly after this failed installation but i cannot flash the new update.
View attachment 5716899
Click to expand...
Click to collapse
Which version of ADB Sideload do you use ?
Post 1 or Post 2

Sib64 said:
Which version of ADB Sideload do you use ?
Post 1 or Post 2
Click to expand...
Click to collapse
What I did was reboot to recovery, navigate to Apply Update via Sideload through the recovery interface and from there entered the command adb sideload filename.zip so i guess it is the method in post 2
UPDATE:
I have tried the method in Post 1 and this error shows up:
UPDATE 2:
I have tried revoking USB DEBUGGING authorization, adb kill-server, adb start-server and authorizing again
I have tried deleting adbkey and adbkey.pub files in C:Users/$Name/.android
I have tried following suggestions about solving this error both from this and this StackOverflow thread
Nothing worked for me.

You don't need to use ADB to sideload an OTA, the nothing phone contains an OTA updater In the phones os already, the only thing you need the computer for is to move the OTA to the phone

Here is what someone on the nothing discord said to do and it worked
dont sideload
Create a folder named “ota” (without the quotes) at the root of the internal storage of your phone. Then copy the update ZIP file to that folder.
Dial `*#*#682#*#* `to open up the offline update tool.
You can also use an activity launcher app to locate and execute the “OfflineOTAUpgrade” tool. The package name of the tool is com.nothing.OfflineOTAUpgradeApp.

Hi, I have just tried your method but an error window pops up:

Hello, can I normally use in built in recovery updater to upgrade to 1.1.4 if I'm rooted and have Nacisk installed?

Ky0sHiR0 said:
Hello, can I normally use in built in recovery updater to upgrade to 1.1.4 if I'm rooted and have Nacisk installed?
Click to expand...
Click to collapse
You can only upgrade not downgrade

demiii said:
Hi, I have just tried your method but an error window pops up:
View attachment 5717197
Click to expand...
Click to collapse
If you go on nothing discord and put that error maybe they can help