Database Develop

[REF][GUIDE] How to: update firmware with CWM app and clockworkmod recovery

This guide will hopefully help people with minimal to zero knowledge or people which are very afraid to just try things on their own to upgrade their Samsung Galaxy Note GT-N7000 to a newer firmware, which might be a pre-release firmware, a leak from somewhere or which won't be or isn't yet available on KIES. The procedure outlined graphically and textually explicitly only takes care of firmware releases which don't come packed as a single .tar.md5 file of about 850mb, but to releases which are split up in several packages of varying size with the file extension .tar.md5. The same procedure applies to single-file releases as well, coming as a single packaged .tar.md5 file. When flashing a single file release, naturally some steps can or must be skipped, like extracting the image files or several selection dialogs in CWM, as there is one one choice to make when dealing with a single file.
The procedure outlined may not be the shortest possible or the least complex one. But I do judge it to be the probably most universal one and following the steps closely should avoid all kind of problems and lead to a seamless and trouble free update. All possible firmware combinations should be updateable this way, as long as the prerequisites are met and the instructions are followed closely. This procedure does not influence or trigger the custom binary flash counter or the yellow warning triangle.
Information: Please read instructions carefully, as it took me quite some time to structure and present them as they are. You may ask questions if problems arise, if important details differ from the steps presented here or you would like to add anything, but post's which clearly show that the author didn't read this message or the very clear instructions in their entirety and rather just puts up a post out of pure lazyness, will get deleted and I will ask moderators or admins to impose some sort of punishment on the poster. I will not let party poopers insult me with their lazyness.
The information presented is structured and numbered. All steps which follow a number are according to my judgement closely connected and form one step. This explains why not every single click or action gets it's own number. Numbers in brackets inside a paragraph, for example [3] means there is a picture existing for the information given in this step. In this example case, it would be picture with index number 3, as pictures as well will be numbered and labelled accordingly.
If you find this information helpful, you may hit the thanks button.
End of introduction. The procedure starts here.
Minimum prerequisites:
Pre-rooted firmware on the device *)
CWM app
SD card, ~1GB free space
*) If you come here without a pre-rooted device, go back and check the threads on how to obtain root. Do not ask here, this thread is for updating an already rooted device only.
1. Prepare the device:
You'll need to prepare your device in a specific way to be able to use this method. You will need an external SD card with at least about 1GB free storage. Access the SD card on the device or by mounting it on your desktop pc [1]. Create a folder in the root of the card named "firmware". Thus, when accessed through the device, the complete path to that folder should be "/sdcard/external_sd/firmware" [1]. This is the folder CWM checks for firmware parts to be flashed.
{
"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"
}
Image 1: Path on external SD card
2. Find the appropriate firmware you want to upgrade to:
Decide on a firmware you want to upgrade to. Download it from your source of choice. You may end up with a .zip or .rar. or generally speaking an archive file [2] you have to extract. Do so.
Image 2: archived firmware release
After the extraction you will most likely find a subfolder being created with several files inside. The content of the firmware you downloaded may differ from the content shown in the image below [3], this does not matter, as long as some central files which I will get to later are at hand. Once you got this far, you may minimise the window, as we will continue elsewhere.
Image 3: extracted firmware release
3. Find and flash the matching cf-root kernel:
Information: If you just rooted your device and did not change kernels since, there is a certain possibility that you already run a cf-root kernel. In this case, this step can also be left out. If you do not know or are unsure, continue to follow the guide.
In order to maximise compatibility with the CWM app, a cf-root kernel will be used for all flashing activities. Find the kernel matching the the firmware you chose to upgrade to in chainfires cf-root release thread. You find the thread here: http://forum.xda-developers.com/showthread.php?t=1331784
If there is no exact match, general rule of thumb use the one you read the best reviews about or just the newest one available. It does not matter if the kernel is two or three releases older than the firmware you want to flash.
Substeps 3.1 Download and extract the kernel image:
- 3.1 a) Download the corresponding kernel as instructed above.
- 3.1 b) The kernel comes pre-packed as a .zip file. Extract it [4].
- 3.1 c) Inside the .zip there will be a .tar file. Extract it.
- 3.1 d) You'll find a file named zImage, push it to the device into the folder created in step 1.
- 3.1 e) Unmount the SD card from the pc, in case you have it mounted.
Image 4: archived cf-root kernel (release shown: KL7)
Substeps 3.2 Flash the kernel on the device using CWM:
- 3.2 a) Launch the CWM app, select "Flash kernel" [5].
- 3.2 b) Navigate to folder from step 1 and select zImage.
- 3.2 c) Confirm the dialog [6], the device will reboot. *)
*) In case you encounter a bootloop, turn off the device, enter recovery with VolUp-Home-Power and chose to "wipe cache" and under advanced, "wipe dalvik cache". Reboot afterwards.
Image 5: CWM app, select [1] (left); Image 6: kernel flash confirmation (right)
4. Flash the firmware:
Navigate to the folder you minimised in step 2, containing the extracted firmware. Of interest are only 3 (three) files, which must be copied to the folder created in step 1. Depending on the firmware release, the names of the files of course differ. Below I will give the generic name of the three files in question and then list a couple variations, so everyone can figure out, which files are to be taken. After copying the files, make sure to unmount the SD card from the pc, it must be accessible on the device.
Files of release XXLA3:
CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5
MODEM_N7000XXLA3_REV_05_CL1095424.tar.md5
GT-N7000-MULTI-CSC-OXALA3.tar.md5
Files of release XXLA1:
CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
GT-N7000-MULTI-CSC-OXALA1.tar.md5
Abstraction: The files containing CODE, MODEM and MULTI-CSC are to be taken and put in the folder created in step 1.
Substeps 4.1 Flash the firmware on the device using CWM:
- 4.1 a) Launch the CWM app, select "Flash stock firmware" [5].
- 4.1 b) Confirm the dialog, also confirm the second dialog.
- 4.1 c) Select zImage as "Source file for: kernel" [7].
- 4.1 d) Select MULTI-CSC as "Source file for: cache" [8].
- 4.1 e) Confirm the dialog.
- 4.1 f) Chose "Keep CF-Root kernel" [9].
Image 5: CWM app, select [2] (left); Image 7: kernel source confirmation (right)
Image 8: cache/CSC source confirmation (left); Image 9: root options (right)
The device will now reboot twice, enter recovery each time and flash the firmware chosen. After the flash, you will be running an updated and pre-rooted Android build on a cf-root kernel. You may freely flash the kernel of your choice in case you do not want cf-root. It is highly recommended that you do switch over to cf-root when flashing to have maximum compatibility between kernel, recovery and CWM app.
You may hit the thanks button now

Message 2
Update overview
Update 19 January 2012, Revision 2
Added the information that the guide also applies to single-file releases coming as a single .tar.md5

Message 3
Outline for future updates
-Update procedure in guide where it differs from multi-file firmware to single-file firmware flashing.
-Information on how to create a nandroid/CWM backup and - provided the firmwares are compatible - restore data after a successful upgrade.

This guide works perfect and very easy to understand!!! Just flashed mine to latest firmware using this guide and it was a breeze!
Thanks
Sent from my GT-N7000 using xda premium

You're welcome. Damn I totally underestimated how long it takes to throw all this sh** together...

Schaggo You are Great
schaggo you are really great.
I was running all over the forum to check how should i upgrade my note from KL3 to LA1 or LA3 through CWm and Mobile Odin Pro.
I screwed my mobile twice with "Logo.*****" error when trying it through mobile odin. Literally i got panicked when my phone came with that "Logo *****error". So I went back to stock KL3 after my two attempts which didnt work.
Later i saw this thread and you know what.. it was crystal clear.... Newbee like me prefer your kind of tutorial to MOD our phones without screwing it.. Even a 10yr kid who knows english can upgrade his/her GN with your guide lines. i.e it is explained in such a way.
Thanks alot for your guidelines..

schaggo said:
1. Prepare the device:
You'll need to prepare your device in a specific way to be able to use this method. You will need an external SD card with at least about 1GB free storage. Access the SD card on the device or by mounting it on your desktop pc [1]. Create a folder in the root of the card named "firmware". Thus, when accessed through the device, the complete path to that folder should be "/sdcard/external_sd/firmware" [1]. This is the folder CWM checks for firmware parts to be flashed.
Click to expand...
Click to collapse
Hi, Thanks for the incredible tutorial.
I was just wondering why we should create the firmware folder under the /sdcard/external_sd/
Shouldn't it be working on the /sdcard/ only?. Sometimes I have problems with CWM and the external card, it gets unmounted e.g. while doing backups
Thanks

The reason is quite simple: it's hardcoded this way. The file(s) to be flashed must reside at /sdcard/external_sd/firmware.
I backup onto the internal memory and use the external card mainly for storing some MP3 and stuff I brought over from my previous Android...

Very clear and understandable, thanks for the great guide! I think one of the major issues with a lot of the other guides on here is the language barrier, for me at least. I say that in the most non-offensive way possible.
Sent from my GT-N7000 using XDA App

Hello Schaggo,
Sorry for cross posting this, but I just discovered your suggestion in the other thread that noob should really follow your guide here and avoid ruining their devices
So I rooted my note and am ready to upgrade it back to Debitel's LA4 firmware, using CWM instead of MobileOdin, and I'm stuck as shown in the attachment, I not only tried LA4, but also Debitel's KK9. It also turned out to be the same result, "can't mount firmwareflash.zip".
Do you have any suggestion to solve this issue?
Thanks a lot!
EDIT: SORRY, forgot to attach the quote of my own from that other thread "[STOCK ROMs]" by THE DOCTOR ;p
cswithxda said:
Please help me
I finished "downgrading to KJ4" and "Rooting", and now I'm on my way upgrading to XXLA4 (Debitel) (which I originally had).
I'm using CWM (tried to avoid Odin, even tho i know it's safe to flash factory ROM, but still, it will try to keep current Kernel). And I got this after I choose "Keep CF-Root Kernel" and the device restarts.
BTW, the firmware is on an external SD card itself. I saw a previous member addressed this issue by starting to use a physical external SD card, but I am already using one
EDIT: just edited the attachment, now it shows how it "aborted" the process ;(
Click to expand...
Click to collapse

Sometimes the ROM - zips is inside the original zip..
run it in Winrar and see what it shows..

cswithxda said:
Hello Schaggo,
Sorry for cross posting this, but I just discovered your suggestion in the other thread that noob should really follow your guide here and avoid ruining their devices
So I rooted my note and am ready to upgrade it back to Debitel's LA4 firmware, using CWM instead of MobileOdin, and I'm stuck as shown in the attachment, I not only tried LA4, but also Debitel's KK9. It also turned out to be the same result, "can't mount firmwareflash.zip".
Do you have any suggestion to solve this issue?
Thanks a lot!
EDIT: SORRY, forgot to attach the quote of my own from that other thread "[STOCK ROMs]" by THE DOCTOR ;p
Click to expand...
Click to collapse
OK. I just figured this out (in the process of flashing tho)
So here's what I did differently this last time from previous attempts (likely 50+ times in the past couple hours): when copying the firmware .tar.md5 file over to the phone from my computer, I dragged that SS_DL.dll file (provided that you have any) together this time. And the CWM recognized the firmware fine.
I'm just writing this down in case anyone else in the future have this issue. So keep this on record.
NOW, HOORAY! Debitel LA4 with Rooted KK9 Kernel!
Love this forum!

This is interesting, as I deliberatly leave out the .dll file. I did so when I flashed KK9. Also when I flashed LA4. In fact, every time. And I flashed them all since November (except LA6, which brings nothing new to the table).
Could it be the file(s) got damaged in the process of transferring it onto the device when you tried the first time round? As the .dll is of absolutely no value to Android.
Edit: but yeah, xda is a godsend...
#Tapatalk #Galaxy Note

Stareing at your screenshot again, it rather seems to me the recovery is/was unable to mount the sdcard and stalled. I also have to say, I never got the countdown your screenshot exposes. I mean its quite a while since I flashed LA4 but I'm quite sure my flashing activities went differently. Could it be that your sdcard is borked? Did you unmount it correctly (eject on pc, then unmount)? Quite hard to pinpoint, now that it worked...
#Tapatalk #Galaxy Note

Thanks for your reply!
Yes, I can't think of what I did differently besides copying that additional dll file.
I did try to copy files to SD card many times thinking that it could be the file was corrupted during the transfer. I also see people with this issue suggesting that the issue was due to the corrupted firmware file from download, so I downloaded it again and the issue persisted.
Also, there is no option on my computer to eject either the phone or SD card, so I always have to just unplug the phone, after which I unmount the SD card in the phone, and re-mount it.
Hopefully when next upgrade thru CWM is coming up and I can try it again, but for now, I definitely do not want to mess with it anymore, as I've spent nearly 10 hrs last night to solve this problem

May I flash Team Rocket Rom 1.1 (ICS 4.0.3) with CWM ?

cswithxda said:
Also, there is no option on my computer to eject either the phone or SD card, so I always have to just unplug the phone, after which I unmount the SD card in the phone, and re-mount it.
Click to expand...
Click to collapse
This way the card can get dirty. In case you're using Windows: sure it's there, at least since Windows 2000 if not longer. Right click the mounted drive, select "Eject". Wait for the confirmation. Otherwise in the systemtray, select the USB icon and unmount the (two) drives.
Hopefully when next upgrade thru CWM is coming up
Click to expand...
Click to collapse
I'm downloading LP1 right now. I'll flash it right when it's done and see what's what.
minhsu said:
May I flash Team Rocket Rom 1.1 (ICS 4.0.3) with CWM ?
Click to expand...
Click to collapse
I'm not aware of the format the Team Rocket ROM comes in. But if it's a .zip containing a couple files and a META-INF folder, then no, you can't flash it using this method. In this case it's an "update.zip" and you have to flash it using the "Flash update.zip" methon in CWM App.

I really don't have that
I don't have USB tray icon when the phone is connected either (i do see it when a flash drive or external hard drive is connected)
Please see the attachment ...

LOL... you access the device through KIES and MTP (Media Transfer Protocol), you don't mount it as a USB mass storage device. No wonder!
Oh my godness, KIES is such ****!

Oops! Noobility here...
How do I change to USB connection? I clicked on "USB connected" tab, but nothing happens, so I could only access MTP mode

Gear Live 5.1.1 OTA Url

Grabbed this from a logcat of my freshly reset watch
https://android.googleapis.com/pack...1f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf
.zip

elitistphoenix said:
Grabbed this from a logcat of my freshly reset watch
https://android.googleapis.com/pack...1f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf
.zip
Click to expand...
Click to collapse
Thanks. Installing it right now. Do you by any chance have a backup of recovery partition? The one that is newer than or KNX01Q
Wohoo they included wifi support in this(unlike some other android wear watches that were promised wifi, but didn't get one with update).
{
"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"
}

Sorry not at the moment

how do you install it?
EDIT:
I figured it out:
1. reboot into boot menu(samsung logo + diagonal swipe)
2. select recovey
3. use adb to update
4. adb sideload file.zip

https://android.googleapis.com/pack....signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip

any other option other than sideload? I'm having hard time with TWRP and win drivers for sideload use

What about power saving for wifi? In advanced setting is set to 120 minutes, but I don't know what does this mean: disconnects from wifi after 120 minutes?

And I don't have my charge cradle at the office.
Guess I will do this tonight!

insaned said:
any other option other than sideload? I'm having hard time with TWRP and win drivers for sideload use
Click to expand...
Click to collapse
Yea, sideload on TWRP doesn't work for me too. What I did was I modified updater-script in ota zip, pushed zip file using adb into watch storage and just installed it as update.
1. Follow this video https://www.youtube.com/watch?v=WSi0yuRkfPk
2. In TWRP click on install
3. Go into /sdcard/ folder in the TWRP filemanager
4. click on 1e8de7cfe6d5fece253b47a727bb7f1580f31f21...
5. swipe and install

aligatro2010 said:
Yea, sideload on TWRP doesn't work for me too. What I did was I modified updater-script in ota zip, pushed zip file using adb into watch storage and just installed it as update.
1. Download https://dl.dropboxusercontent.com/u/36544414/updater-script
2. Open your 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip using winrar
3. Place file from 1 into \META-INF\com\google\android
4. load into TWRP and on pc do adb push 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip /sdcard/
5. In TWRP click on install
6. Go into /sdcard/ folder in the TWRP filemanager
7. click on 1e8de7cfe6d5fece253b47a727bb7f1580f31f21...
8. swipe and install
Click to expand...
Click to collapse
Thanks for the detailed steps.
However I still get a error flashing the zip..
"Error executing updater binary in zip..."

insaned said:
Thanks for the detailed steps.
However I still get a error flashing the zip..
"Error executing updater binary in zip..."
Click to expand...
Click to collapse
Hmm I should probably zip that updater-script as the windows might be screwing up the endlines when you save it. What is the full error?
https://dl.dropboxusercontent.com/u/36544414/updater-script.zip Here you go.

aligatro2010 said:
Hmm I should probably zip that updater-script as the windows might be screwing up the endlines when you save it. What is the full error?
https://dl.dropboxusercontent.com/u/36544414/updater-script.zip Here you go.
Click to expand...
Click to collapse
Thanks.
I even deleted the file in the 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip.zip and inserted your file there.
Still the same error.
will you mind upload the full zip you used and share it? Thanks for all the trouble.. I guess my watch is fighting back this update by all means!!
E:Error executing updater binary in 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip.zip "
Error flashing zip '/sdcard/1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip.zip'
Click to expand...
Click to collapse

insaned said:
Thanks.
I even deleted the file in the 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip.zip and inserted your file there.
Still the same error.
will you mind upload the full zip you used and share it? Thanks for all the trouble.. I guess my watch is fighting back this update by all means!!
Click to expand...
Click to collapse
Try this one.
https://dl.dropboxusercontent.com/u/36544414/updater-script 2.zip I've redone it from scratch. And tested it flashing.
If that doesn't work, just follow this short video I made. Note that I am using notepad++
https://www.youtube.com/watch?v=WSi0yuRkfPk

aligatro2010 said:
Try this one.
https://dl.dropboxusercontent.com/u/36544414/updater-script 2.zip I've redone it from scratch. And tested it flashing.
If that doesn't work, just follow this short video I made. Note that I am using notepad++
https://www.youtube.com/watch?v=WSi0yuRkfPk
Click to expand...
Click to collapse
Tried both methods but something still returning this error.... it is like if I was trying to inject in in other watch

insaned said:
Tried both methods but something still returning this error.... it is like if I was trying to inject in in other watch
Click to expand...
Click to collapse
What happens if you try to flash the unmodified firmware file. Does it still return the exact same error or is it complaining about wrong fingerprint?
I am gonna upload my modified zip. its gonna take some time. my upload speed sucks.
Looking at your pictures, it seems that the file app_process2, on your watch, has a different checksum than what is supposed to be. So, either your have older firmware than LWX49K(5.0.2) or that file became corrupted or something else happened to it.

aligatro2010 said:
What happens if you try to flash the unmodified firmware file. Does it still return the exact same error or is it complaining about wrong fingerprint?
I am gonna upload my modified zip. its gonna take some time. my upload speed sucks.
Looking at your pictures, it seems that the file app_process2, on your watch, has a different checksum than what is supposed to be. So, either your have older firmware than LWX49K(5.0.2) or that file became corrupted or something else happened to it.
Click to expand...
Click to collapse
I have LWX49K (5.0.2) so I really dunno what might happened.. or it was doing root or I don't understand..!

insaned said:
I have LWX49K (5.0.2) so I really dunno what might happened.. or it was doing root or I don't understand..!
Click to expand...
Click to collapse
Well if thats the only file corrupted, I can give you a backup of mine.
Hmm now that I think about it, I can't because I already upgraded, but I can give you the one from newer firmware and remove check for that one file in the updater-script.
Ok so find this line in your updater-script and just remove it
apply_patch_check("/system/bin/app_process32", "a92a761aef714b5e97bc2f27991d6c6d3432e0eb", "ee28188953742e905c1b20a5349a2184581e2972") || abort(""/system/bin/app_process32" has unexpected contents.");
in TWRP fist go into "mount" and make sure that "system" has checkmark in front of it.
Then get a backup of your file by adb pull /system/bin/app_process32 . Save it to a safe place
Download https://dl.dropboxusercontent.com/u/36544414/modified OTA 81/app_process32
And do adb push app_process32 /system/bin/

aligatro2010 said:
Well if thats the only file corrupted, I can give you a backup of mine.
Hmm now that I think about it, I can't because I already upgraded, but I can give you the one from newer firmware and remove check for that one file in the updater-script.
Click to expand...
Click to collapse
If reseting device would fiznthe file I can do it straight, but I'm not sure of that!
Sent from my SM-G920F using Tapatalk

insaned said:
If reseting device would fiznthe file I can do it straight, but I'm not sure of that!
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I don't think it will since its located in the system partition. When you do reset it formats userdata partition.

aligatro2010 said:
Well if thats the only file corrupted, I can give you a backup of mine.
Hmm now that I think about it, I can't because I already upgraded, but I can give you the one from newer firmware and remove check for that one file in the updater-script.
Ok so find this line in your updater-script and just remove it
apply_patch_check("/system/bin/app_process32", "a92a761aef714b5e97bc2f27991d6c6d3432e0eb", "ee28188953742e905c1b20a5349a2184581e2972") || abort(""/system/bin/app_process32" has unexpected contents.");
in TWRP fist go into "mount" and make sure that "system" has checkmark in front of it.
Then get a backup of your file by adb pull /system/bin/app_process32 . Save it to a safe place
Download https://dl.dropboxusercontent.com/u/36544414/modified OTA 81/app_process32
And do adb push app_process32 /system/bin/
Click to expand...
Click to collapse
Thanks , I will trybit noe as soon as I arrive home sinxe I came to e work
Sent from my SM-G920F using Tapatalk

Tutorial How to root ZTE z835 (Maven 3) with Magisk.

DISCLAIMER: I AM NOT RESPONSIBLE FOR WHAT MAY HAPPEN TO YOUR DEVICE, DO THIS AT YOUR OWN RISK.
Before I start: everything I'm going to post here, I learned from this thread: https://forum.xda-developers.com/maven-3/help/zte-maven-3-z835-root-t3705687/page9
VERSION OF MAGISK FLASHEAD v17.1 (Unfortunately no one has flashed version v18.1)
What we need (they will be in the links at the end):
-ZPST for AT&T (with this program we are going to flash the modified boot.img)
-Drivers: QDLoader, ZTE AndroidUSB and ZTE_V889F (in case the previous Zte driver does not work).
-Modified boot.img that are already flashed with Magisk, only the following versions are available:
-Z835V2.0.0B10
-Z835V2.0.0B12
-Z835V1.0.0B13
-Magisk Manager version compatible with v17.1
EVERYTHING YOU NEED IS IN A LINK AT THE END OF THE POST.
Let's get started.
I recommend to do a hard reset before starting, however, in one of my devices I did it having data and applications installed, if you have used kingroot or any other software in your phone, erase all trace of it so you do not have problems.
We download all the contents of the folder, install all drivers included, and the ZPST for AT&T.
Starting to flash:
WE NEED AT LEAST 50-60% of Battery
Turn off the phone and turn on pressing Vol Down + Power Button, the phone will start in FTM mode.
Open ZPST for AT&T and select version Z835
{
"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"
}
WARNING, remove the usim and sd card
Once inside the software we proceed to connect the cell phone.
1. You will see if the phone was recognized by the com port.
2. Download, this is where we will enter to download the firmware
3. You will see your information imei and so on.
This is how it will look once connected (Let's go to the download tab)
1. Let's select the firmware (it has to be the same as the cell phone otherwise it can corrupt the imei)
2. We chose where to keep a small log to check if everything went well.
3. HIT THE DOWNLOAD BUTTON!!!!!
WARNING: wait for the device to restart at least 2 or 3 times, one of them will be in FTM mode again, so do not panic, it will take a while in 3% or 5%.
When the phone starts normally, if you did a hard reset configure everything again, otherwise, we will proceed to install the magisk.
DO NOT INSERT THE SD CARD YET!
Magisk asks if I want to update to the latest version, press NO THANKS.
Proceed to uninstall
Now let's install the version of magisk manager we downloaded (com.topjohnwu.magisk_6.1.0-165_minAPI21(nodpi)_apkmirror.com.apk)
When the installation is finished we enter Magisk and this will ask us if we want to upgrade to the latest version, PRESS NO!
Now we will see that magisk is installed correctly.
We see that we can use all its functions.
We will proceed to verify if we have root access.
Download root checker
And Voila!
MEGA link: https://mega.nz/#F!ud8VwKRJ!-cJr7EJyhb1PkziNx5KvLQ

with this can you uninstall original system's apps such as device help, google apps? install recovery and titanium backup? I need to remove a lot of bloatware/default apps that is taking memory from the device

nvizync said:
Root
Click to expand...
Click to collapse
Nice work! This confirms that the bootloader is unlocked, which means we can then use just the firehose to flash these files. I will work on writing something up for that.

deadman96385 said:
Nice work! This confirms that the bootloader is unlocked, which means we can then use just the firehose to flash these files. I will work on writing something up for that.
Click to expand...
Click to collapse
Would love to see that, thanks for the reply! :good:

rickastillo said:
with this can you uninstall original system's apps such as device help, google apps? install recovery and titanium backup? I need to remove a lot of bloatware/default apps that is taking memory from the device
Click to expand...
Click to collapse
You can install titanium backup, twrp is not possible at this point, no one has done it yet, you can delete system apps through adb, using
Code:
adb shell pm uninstall -k --user 0 packagename
But i haven't figured out yet how to get rw permission on system/apps so i can delete system apk's.

@nvizync You should thank me for my boot.img mod of -Z835V2.0.0B10 (Magisk 17.1)
my boot.img mod of:
-Z835V1.0.0B13 (Magisk 18.1) Link: https://mega.nz/#F!88IiFapI!6Peah7woOOaIhusfYCAEcw
-Z835V2.0.0B10 (Magisk 18.1) link: https://mega.nz/#F!V4pAVIYQ!19tWE7_xk_aQtyiu050Y7A
-Z835V2.0.0B12 (Magisk 18.1) Link: https://mega.nz/#F!9lBVkQAZ!WqnRvYa4qcw5MgRxhp1hcA
Thanks for your detailed flash root tutorial

Alijosekt said:
@nvizync You should thank me for my boot.img mod of -Z835V2.0.0B10 (Magisk 17.1)
my boot.img mod of:
-Z835V2.0.0B10 (Magisk 18.1) link: https://mega.nz/#F!V4pAVIYQ!19tWE7_xk_aQtyiu050Y7A
-Z835V2.0.0B12 (Magisk 18.1) Link: https://mega.nz/#F!9lBVkQAZ!WqnRvYa4qcw5MgRxhp1hcA
Thanks for your detailed flash root guide
Click to expand...
Click to collapse
I totally forgot it, yeah, you deserve most of the credit, I linked the original thread, but I'm planning including all the credits.

@nvizync Look what I got! https://github.com/TwrpBuilderTests/android_device_zte_z835/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?

Alijosekt said:
@nvizync Look what I got! https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Click to expand...
Click to collapse
Ok my way

nvizync said:
Ok my way
Click to expand...
Click to collapse
not boot twrp

Alijosekt said:
not boot twrp
Click to expand...
Click to collapse
Did you tried it

Alijosekt said:
@nvizync Look what I got! https://github.com/TwrpBuilderTests/android_device_zte_z835/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Click to expand...
Click to collapse
I tried to flash it, but instead, I just got a bootloop, and I can't access the recovery mode anymore, I should flash the original recovery and see if it works.

nvizync said:
I tried to flash it, but instead, I just got a bootloop, and I can't access the recovery mode anymore, I should flash the original recovery and see if it works.
Click to expand...
Click to collapse
Done, i managed to enter in normal mode and use flashify to flash stock recovery.img.

Hi, I'm stuck at the first step. The ZPST download fails with the message that it can't find the file: sbl1.mbn Any thoughts?

penn462 said:
Hi, I'm stuck at the first step. The ZPST download fails with the message that it can't find the file: sbl1.mbn Any thoughts?
Click to expand...
Click to collapse
Are you using the custom boot.img listed in mega's folder?

nvizync said:
Are you using the custom boot.img listed in mega's folder?
Click to expand...
Click to collapse
Yes. I'm using the folder "Boot Mod Z835V1.0.0B13"

penn462 said:
Yes. I'm using the folder "Boot Mod Z835V1.0.0B13"
Click to expand...
Click to collapse
Thats odd, try this: download another folder B12 or B10, and just paste the B13 boot.img, maybe that could work, one of the devices i rooted was B13.

Well, I tried what you suggested, and now I get "download failed" and "failed to change mode before downloading firmware" It seems to be stuck in FTM. I guess it's bricked?
---------- Post added at 06:52 PM ---------- Previous post was at 06:48 PM ----------
Update: not bricked. Gonna try again.

penn462 said:
Well, I tried what you suggested, and now I get "download failed" and "failed to change mode before downloading firmware" It seems to be stuck in FTM. I guess it's bricked?
Click to expand...
Click to collapse
Fear not, that happened to me also, just keep in ftm and make a stock boot.img flash, provided in the mega folder. Paste the boot stock image inside the b13 folder

Placed stock boot.img into B13 folder in place of custom boot.img. The process failure point is now back to the missing sbl1.mbn problem. I can get the phone to start, however, so it's not bricked. Whew!

[MAGISK][Android 10]Patched Boot Image For OnePlus 7 Pro

Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk.
Recommended to patch your own image read this
Grab the latest Platform Tools HERE
Code:
1. Download a stock Oxygen OS ROM Zip from [URL="https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156267635"]Here[/URL] Or the general section of XDA many users post links to the latest builds.
2. Download [URL="https://androidfilehost.com/?fid=818070582850510260"]payload_dumper-win64.zip[/URL] And extract/copy it to Desktop.
3. Extract your payload.bin from the stock rom zip and copy it into the payload_input folder.
4. Run the payload_dumper exe.
5. When it's finished open the payload_output folder and copy the boot.img to Desktop keep it there as a backup.
6. Copy the same boot.img to your internal storage on your phone.
7. Install the magisk manager APK from here: [URL="https://github.com/topjohnwu/Magisk"]Magisk Manager[/URL]
8. Open Magisk Manager choose install and select "Select and Patch a file" Or if you wish to use beta release go to settings > Update Channel and switch to beta and then back to Install "Select And Patch A File"
9. Navigate to where you copied your boot.img on the phone.
10. Once it's patched you'll have an magisk_patched.img on your phone in the the Downloads folder.
11. Copy that image to your fastboot folder on your PC and flash it with fastboot flash boot magisk_patched.img
Done!
As always I'm not responsible for any issues your device might have or if your cat sets on fire.
Credits:
topjohnwu for Magisk/Manger
geminids14 for payload_dumper-win64

Nice, that is what we need .. Thanks Liam

How can i load twrp? Fastboot boot command, didnt work

DevrimSeven60 said:
How can i load twrp? Fastboot boot command, didnt work
Click to expand...
Click to collapse
Ask in the TWRP thread

Not working for me get a error file is to large to download when try to flash

dajumper said:
Not working for me get a error file is to large to download when try to flash
Click to expand...
Click to collapse
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools

liam_davenport said:
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Still the same

Im already rooted with bootimg having lat pie release. Is it possible to flash Android Q on top of last pie release and be rooted? Again I am rooted with magisk, not having twrp.
To update I always flash full updat from local, not reboot, install magisk to other slot and I was ready to go.
Will this work with Q update?

Not working for me. Both sims dissapear and phone keeps FC.

pister said:
Not working for me. Both sims dissapear and phone keeps FC.
Click to expand...
Click to collapse
Issue is on your end, I've flashed this multiple times no issue.
Working perfectly here I've clean flashed and redownloaded from the link and flashed. I've noticed sometime magisk causes sims to not show on boot before reboot the device and they should show again.
{
"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"
}

I see that when I root, both IMEIs disappears. Very strange
Sent from my [device_name] using XDA-Developers Legacy app

error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash

pister said:
I see that when I root, both IMEIs disappears. Very strange
Click to expand...
Click to collapse
Mine both show. Not sure why yours have disappeared

liam_davenport said:
Mine both show. Not sure why yours have disappeared
Click to expand...
Click to collapse
Don't know. Tried to root by myself and the same happened
Sent from my [device_name] using XDA-Developers Legacy app

NateDev said:
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
Click to expand...
Click to collapse
If you have twrp already you don't need this I posted this for people that want root without using twrp, Just flash magisk 19.4 in twrp
There is a few guides in this forum section with all info you need on how to flash etc

Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it

mgear356 said:
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
Click to expand...
Click to collapse
You flashed it on Open beta 1?

liam_davenport said:
You flashed it on Open beta 1?
Click to expand...
Click to collapse
Yup open beta 1

Great thanks!
But can we update OTA to B2 with this?

@liam_davenport I'm sorry for the noob question, I just got my OP 7 Pro and never used one before, also, I've been away from everything root related for a long time.
Do I need to unlock the bootloader first in order to do this?

Question Just got mine, few questions:

Hi everyone,
I bought my Zenfone 8 from a pretty secretive seller, it came without anything except charger and the phone itself.
The seller says it is Hong Kong specified but in fact the charge is a Type M plug with a .in TLD Indian site on it.
The phone model is ASUS_I006D;
Firmware version is 30.11.51.83 which seems to be up-to-date but Security update indicates it is on May 5, 2021 with a red exclamation mark, it says "your system is up to date" when I tap on it to check update.
Is that normal?
Thanks,
Abe.

Could you screenshot that please?

Kenora_I said:
Could you screenshot that please?
Click to expand...
Click to collapse
Sure, here you go:
{
"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"
}

Your phone is outdated actually there was an update in july follow below steps to manually install the latest update.
Steps for update:
1. Go to the "ASUS Download Center"page of the ASUS Official Website https://www.asus.com/support/Download-Center/ to download the ZIP file of the needed firmware.
1.1 Key-in the product model name you're searching for.
1.2 Choose "Driver & Utility".
1.3 Select OS "Android".
1.4 Tap“BIOS & FIRMWARE”, please carefully confirm the version number and read the upgrade instruction in the description field, then follow the instruction to download and install the update firmware.
2. Put the ZIP file in the root directory of the phone's internal storage.
2-1. Download by Phone/Pad：Please select the download path to the root directory of the phone's internal storage (or copy/move from default download path).
2-2. Download by PC：Connect your phone to PC via USB cable, and copy the ZIP file to the root directory of the phone's internal storage. Remove the USB cable from the phone while finishing the file save.
3. Reboot your phone and check for the firmware update notification pop-up on the status bar.
4. Tap "System update file detected" and follow the steps shown to update the firmware.
Note: The steps or photos shown above may vary depending on the device models.

@Kenora_I The Update was canceled for some reason. Probably a bug was found so you have to wait a bit longer for the next update to arrive

Kenora_I said:
Your phone is outdated actually there was an update in july follow below steps to manually install the latest update.
Steps for update:
1. Go to the "ASUS Download Center"page of the ASUS Official Website https://www.asus.com/support/Download-Center/ to download the ZIP file of the needed firmware.
1.1 Key-in the product model name you're searching for.
1.2 Choose "Driver & Utility".
1.3 Select OS "Android".
1.4 Tap“BIOS & FIRMWARE”, please carefully confirm the version number and read the upgrade instruction in the description field, then follow the instruction to download and install the update firmware.
2. Put the ZIP file in the root directory of the phone's internal storage.
2-1. Download by Phone/Pad：Please select the download path to the root directory of the phone's internal storage (or copy/move from default download path).
2-2. Download by PC：Connect your phone to PC via USB cable, and copy the ZIP file to the root directory of the phone's internal storage. Remove the USB cable from the phone while finishing the file save.
3. Reboot your phone and check for the firmware update notification pop-up on the status bar.
4. Tap "System update file detected" and follow the steps shown to update the firmware.
Note: The steps or photos shown above may vary depending on the device models.
Click to expand...
Click to collapse
Thank you, but unfortunately I just can't make it work.
I've downloaded the firmware Version WW-30.11.51.67, which is the latest according to the website,
- I've tested the ZIP file downloaded to make sure it is corrupt free;
- checked multiple times for the file name, to be sure it keeps as the same as the file name on the website without anything may causes problem like (1);
- rebooted several times and waited minutes after for the notification, but nothing showed up.
I found that my current firmware version is WW_30.11.51.83, it seems even newer than the one listed on the website, I don't know if it is the cause.

Mine shows 5 May 2021 too and I am on WW_30.11.51.83
I stopped bothering to be honest. Waiting for LOS anyway.
EDIT: that last firmware update came out in July btw, if I remember correctly.

mickey36736 said:
@Kenora_I The Update was canceled for some reason. Probably a bug was found so you have to wait a bit longer for the next update to arrive
Click to expand...
Click to collapse
Oh maybe this is what exactly happening to me, thank you. Seems have to wait for the next release and finger crossed to fix the security patch left behind problem.

A new update has arrived
Version 30.11.51.103

mickey36736 said:
A new update has arrived
Version 30.11.51.103
Click to expand...
Click to collapse
Yes, receiving the update just now in GER, too.

mickey36736 said:
A new update has arrived
Version 30.11.51.103
Click to expand...
Click to collapse
It is still out of luck in BG so far, but it's so great to know new release is out.

The update zip is saved on your sd, save it before reboot

etann said:
Oh maybe this is what exactly happening to me, thank you. Seems have to wait for the next release and finger crossed to fix the security patch left behind problem.
Click to expand...
Click to collapse
Okay, what you see is perfectly normal. Just a warning that a security update hasn’t been installed in 90 days.
It is a warning to tell ya to update ypur device to protect you from the latest vulnerabilities.
It will disappear once you install the update.
Thanks @mickey36736 for telling me about the canceled update.