Database Develop

HELP NEEDED - Failed to Upgrade to Gingerbread Tab almost dead

Dear All,
I tried to upgrade from this thread
http://forum.xda-developers.com/showthread.php?t=1073854
My baseband version was P1000XXJK5
I stricktly followed all instructions and I always been stuck on Samsung logo.
Then I retried and I find out that I have error messages on the system recovery:
E:failed to mount /preload (No such file or directory)
E:install_application_for_customer:Can't mount /preload
your storage not prepared yet, please use UI menu for format and reboot actions.
I tried to reinstall old and new firmwares as well but all attempts remain unsuccessful.
What should I do now???[/QUOTE]
{
"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"
}
Damn I am really lost, what can I do now...

Maybe nothing but what is that __ in your file location

I have the same problem...

As you're now in the Recovery menu choose option 'wipe cache', then 'wipe data/factory reset' and after that reboot and you should be fine.

I did this with [stock rom][2.3.3] p1000xxjq1 p1000xxjq1 p1000xxjpz:
http://forum.xda-developers.com/showthread.php?t=1073854
Procedure (ODIN !):
- Press the thanks button and/or donate
- Download and extract the firmware zip
- Download and extract the attached gt-p1000_mr_PIT.zip
- Download and extract the attached dbdata.zip
- Flash the firmware tar as PDA, repartition enabled, use the attached PIT
- After flash immediately boot into download mode again
- Flash dbdata.tar as PDA (NO repartition)
- After flash immediately boot into recovery mode
- Wipe cache
- Wipe data / factory reset
Now I have gingerbread working

joedoe said:
As you're now in the Recovery menu choose option 'wipe cache', then 'wipe data/factory reset' and after that reboot and you should be fine.
Click to expand...
Click to collapse
Already tried this unsuccessfully
When trying to wipe data, I got the following error msg
E:format_volume: rfs format failed on /dev/block/mmcblk0p2

cirion said:
I did this with [stock rom][2.3.3] p1000xxjq1 p1000xxjq1 p1000xxjpz:
http://forum.xda-developers.com/showthread.php?t=1073854
Procedure (ODIN !):
- Press the thanks button and/or donate
- Download and extract the firmware zip
- Download and extract the attached gt-p1000_mr_PIT.zip
- Download and extract the attached dbdata.zip
- Flash the firmware tar as PDA, repartition enabled, use the attached PIT
- After flash immediately boot into download mode again
- Flash dbdata.tar as PDA (NO repartition)
- After flash immediately boot into recovery mode
- Wipe cache
- Wipe data / factory reset
Now I have gingerbread working
Click to expand...
Click to collapse
As you can see above (screenshot) all update won't finalize and I got a big FAILED just after the HIDDEN process.
see below
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> Sbl.bin
<ID:0/004> param.lfs
<ID:0/004> zImage
<ID:0/004> factoryfs.rfs
<ID:0/004> cache.rfs
<ID:0/004> hidden.rfs
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

DinoZ1 said:
Already tried this unsuccessfully
When trying to wipe data, I got the following error msg
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Click to expand...
Click to collapse
If so just try to reboot and if succeeded go back to download mode and reflash.

joedoe said:
If so just try to reboot and if succeeded go back to download mode and reflash.
Click to expand...
Click to collapse
As I said I am no longer able to finish upgrade process now...
I have been trying over and over but... nothing seems to work.
Something is wrong with the mounting of dir

DinoZ1 said:
As I said I am no longer able to finish upgrade process now...
I have been trying over and over but... nothing seems to work.
Something is wrong with the mounting of dir
Click to expand...
Click to collapse
Do you have a External Sd-Card inserted ?? If so, try to remove it and
try again.

This may have already been addressed but instead of using PIT files with ODIN why don't you use Heimdall?

Hi
I had exactly the same issue so used heimdall first and then Odin. following this link:
http://forum.xda-developers.com/showthread.php?t=1078622#
All flashed and working properly.
Hope that helps

May be nothing short of a suggestion, but do you have lagfix enabled (if you have cwm already installed)? If so, try disabling it.
Good luck.

DinoZ1 said:
As I said I am no longer able to finish upgrade process now...
I have been trying over and over but... nothing seems to work.
Something is wrong with the mounting of dir
Click to expand...
Click to collapse
this is where my tutorial come's into picture for GSM Tabs. have you tried it yet?
http://forum.xda-developers.com/showthread.php?t=1078622

As soon as you flash the rom you're supposed to go back into download mode and flash a dbdata file from odin.

DinoZ1 said:
Dear All,
I tried to upgrade from this thread
http://forum.xda-developers.com/showthread.php?t=1073854
Click to expand...
Click to collapse
Download and read the guide from the OP in the Overcome 2.x thread. Follow the instructions up to the end of the section for installing the "safe" version of Gingerbread and you'll be fine.
Assuming you're using a standard GSM P1000 galaxy tab that is.
Also, not a development topic, should be in Q&A or General.

The key is to do a factory wide after the flash, otherwise ur tab will not boot
Sent from my GT-P1000 using XDA Premium App

rangercaptain said:
As soon as you flash the rom you're supposed to go back into download mode and flash a dbdata file from odin.
Click to expand...
Click to collapse
I was? ...
Sent from my "better than an iPad" tab... Running Overcome GINGERBREAD!!!

oddball69 said:
Do you have a External Sd-Card inserted ?? If so, try to remove it and
try again.
Click to expand...
Click to collapse
I already have tried this but same sad result

[tutorial] root samsung galaxy a6 plus a605g

DISCLAIMER This is the method which worked personally for me after trying out a number of attempts. Try at your own risk. I am not responsible for any bricked devices.
First of all I would like to appreciate @topjohnwu for his amazing Magisk Project and being wonderful people around in XDA. It is because of the Magisk project that the A6 plus got root although having no stable twrp.
Directions
First of all you need to download the following files :
Latest version of ODIN
7Z Zstandard
Samsung USB Drivers
Stock Firmware of your model ( Use Sammobile or Updato)
Magisk Manager v6.0.0 apk ( https://******************/ or xda thread )
After downloading all of these tools, install 7zip Zstandard , Odin and Samsung USB driver in your Pc or Laptop. After that you need to extract your stock firmware if it's in compressed zip with 7zip. Now , there will be 5 files AP, BL, CSC, HOME CSC and CP. You need to extract AP file to get boot.img of your device . Select the AP file , right click > 7zip Zstandard > Extract Here.
Once decompressed you will find your boot.img.lz4 in there. again extract it using 7zip Zstandard and you will get your boot.img .Now transfer this boot.img to your android device.
Install Magisk Manager latest version (v6.0.0 as of now) in your phone and got to settinngs and select patched boot output format to img.tat . Return to the homepage of app and tap on install now. From the two options, select Patch boot image and browse to your boot.img. From here, a black terminal will appear and Magisk will download the root zip and patch your boot image to be ready for Magisk su. Once it is done with the process, it will show you the location if the patched image file. Now, Copy this patched image to your desktop and make sure you have both, the stock boot.img and the patched boot.img in case something goes wrong. In your device go to Settings > About Phone > Software Information and tap on the Build number for around 7 times until it shows “Developer settings has been turned on” . Now come again to the settings of your device and move to bottom. Below About Phone you will find Developer Settings. Go and tick on OEM Unlock there . It will ask for a reboot , allow it to perform that. Now follow the final steps given below:
1) Download Odin to your laptop/PC.
2) Turn off your phone.
3) Go to download mode (by pressing Volume down+Volume up buttons together and then connect the USB cable)
4)Press the Volume up button to continue.
5)Open Odin on your laptop/pc.
6) Connect your phone to your laptop/PC through USB cable.
7) When ODIN detects your phone, It will show added in the Log.
8) In ODIN click on AP and then select the patched boot.img file you created.
9) Click on start. The flashing process will start.
10) If the flashing succeeds, ODIN will show 'PASS'. That means the boot image flashed successfully.
11) After it finishes, go back and reboot your phone.
Enjoy your rooted Samsung Galaxy A6 PLUS !!!
{
"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"
}

Thanks bro for the root method and detailed tutorial.. will i have to follow the same steps to root my sm-a605f device !!

kifayat83 said:
Thanks bro for the root method and detailed tutorial.. will i have to follow the same steps to root my sm-a605f device !!
Click to expand...
Click to collapse
Ys

kifayat83 said:
Thanks bro for the root method and detailed tutorial.. will i have to follow the same steps to root my sm-a605f device !!
Click to expand...
Click to collapse
Hello
Did you try this method?
Plz inform me if it worked for you

My OEM unlock option gone. try to reflash patched boot img but got an error iyhat only official binary can be flash

badagila said:
My OEM unlock option gone. try to reflash patched boot img but got an error iyhat only official binary can be flash
Click to expand...
Click to collapse
Hi
Does this method work for you?
pinoy here
thankz
---------- Post added at 13:36 ---------- Previous post was at 13:02 ----------
Dev-sahil (Devil) said:
DISCLAIMER This is the method which worked personally for me after trying out a number of attempts. Try at your own risk. I am not responsible for any bricked devices.
First of all I would like to appreciate @topjohnwu for his amazing Magisk Project and being wonderful people around in XDA. It is because of the Magisk project that the A6 plus got root although having no stable twrp.
Directions
First of all you need to download the following files :
Latest version of ODIN
7Z Zstandard
Samsung USB Drivers
Stock Firmware of your model ( Use Sammobile or Updato)
Magisk Manager v6.0.0 apk ( https://******************/ or xda thread )
After downloading all of these tools, install 7zip Zstandard , Odin and Samsung USB driver in your Pc or Laptop. After that you need to extract your stock firmware if it's in compressed zip with 7zip. Now , there will be 5 files AP, BL, CSC, HOME CSC and CP. You need to extract AP file to get boot.img of your device . Select the AP file , right click > 7zip Zstandard > Extract Here.
Once decompressed you will find your boot.img.lz4 in there. again extract it using 7zip Zstandard and you will get your boot.img .Now transfer this boot.img to your android device.
Install Magisk Manager latest version (v6.0.0 as of now) in your phone and got to settinngs and select patched boot output format to img.tat . Return to the homepage of app and tap on install now. From the two options, select Patch boot image and browse to your boot.img. From here, a black terminal will appear and Magisk will download the root zip and patch your boot image to be ready for Magisk su. Once it is done with the process, it will show you the location if the patched image file. Now, Copy this patched image to your desktop and make sure you have both, the stock boot.img and the patched boot.img in case something goes wrong. In your device go to Settings > About Phone > Software Information and tap on the Build number for around 7 times until it shows “Developer settings has been turned on” . Now come again to the settings of your device and move to bottom. Below About Phone you will find Developer Settings. Go and tick on OEM Unlock there . It will ask for a reboot , allow it to perform that. Now follow the final steps given below:
1) Download Odin to your laptop/PC.
2) Turn off your phone.
3) Go to download mode (by pressing Volume down+Volume up buttons together and then connect the USB cable)
4)Press the Volume up button to continue.
5)Open Odin on your laptop/pc.
6) Connect your phone to your laptop/PC through USB cable.
7) When ODIN detects your phone, It will show added in the Log.
8) In ODIN click on AP and then select the patched boot.img file you created.
9) Click on start. The flashing process will start.
10) If the flashing succeeds, ODIN will show 'PASS'. That means the boot image flashed successfully.
11) After it finishes, go back and reboot your phone.
Enjoy your rooted Samsung Galaxy A6 PLUS !!!
Click to expand...
Click to collapse
Hi sir..
i want to try this method but the problem is when i try to unlock OEM...
its says that it will reset my phone to its factory settings
did this method still works if i do that?
before, unlocking oem will just restart your device but now it will reset to factory defaults..
Im using android security patch level (July 1,2018)

Not sure it worked
Hello,
Thank you for the tutorial.
I tried this method, and seems like it didn't work. I'm not really sure, beause I used one root checker app, and it says it's not rooted, and used another one that said it is :silly:
Anyway I installed titanium backup that said root is not granted, although on the bootup image of the phone the're's something written in yellow.
And more, I cannot log in to my samsung account anymore, seems I'm in to flash again.
Edit : My phone is an a605F, but I think it doesn't matter.

Dev-sahil (Devil) said:
DISCLAIMER This is the method which worked personally for me after trying out a number of attempts. Try at your own risk. I am not responsible for any bricked devices.
First of all I would like to appreciate @topjohnwu for his amazing Magisk Project and being wonderful people around in XDA. It is because of the Magisk project that the A6 plus got root although having no stable twrp.
Directions
First of all you need to download the following files :
Latest version of ODIN
7Z Zstandard
Samsung USB Drivers
Stock Firmware of your model ( Use Sammobile or Updato)
Magisk Manager v6.0.0 apk ( https://******************/ or xda thread )
After downloading all of these tools, install 7zip Zstandard , Odin and Samsung USB driver in your Pc or Laptop. After that you need to extract your stock firmware if it's in compressed zip with 7zip. Now , there will be 5 files AP, BL, CSC, HOME CSC and CP. You need to extract AP file to get boot.img of your device . Select the AP file , right click > 7zip Zstandard > Extract Here.
Once decompressed you will find your boot.img.lz4 in there. again extract it using 7zip Zstandard and you will get your boot.img .Now transfer this boot.img to your android device.
Install Magisk Manager latest version (v6.0.0 as of now) in your phone and got to settinngs and select patched boot output format to img.tat . Return to the homepage of app and tap on install now. From the two options, select Patch boot image and browse to your boot.img. From here, a black terminal will appear and Magisk will download the root zip and patch your boot image to be ready for Magisk su. Once it is done with the process, it will show you the location if the patched image file. Now, Copy this patched image to your desktop and make sure you have both, the stock boot.img and the patched boot.img in case something goes wrong. In your device go to Settings > About Phone > Software Information and tap on the Build number for around 7 times until it shows “Developer settings has been turned on” . Now come again to the settings of your device and move to bottom. Below About Phone you will find Developer Settings. Go and tick on OEM Unlock there . It will ask for a reboot , allow it to perform that. Now follow the final steps given below:
1) Download Odin to your laptop/PC.
2) Turn off your phone.
3) Go to download mode (by pressing Volume down+Volume up buttons together and then connect the USB cable)
4)Press the Volume up button to continue.
5)Open Odin on your laptop/pc.
6) Connect your phone to your laptop/PC through USB cable.
7) When ODIN detects your phone, It will show added in the Log.
8) In ODIN click on AP and then select the patched boot.img file you created.
9) Click on start. The flashing process will start.
10) If the flashing succeeds, ODIN will show 'PASS'. That means the boot image flashed successfully.
11) After it finishes, go back and reboot your phone.
Enjoy your rooted Samsung Galaxy A6 PLUS !!!
Click to expand...
Click to collapse
done SM-A605GN, thank you and here is binary 8 patched file to help others

''''''Samsung a6 plus sm 605gn root''''''
The Directoins give are 100% correct
Should work with right firmware
Majisk works and updates itself corectly
Majisk patches firmware app file corectly
Odin works corectly
Every 100% ok
'''''THE STUPID QUESTION''''
The Samsung a6 plus sm 605gn was brought ''NEW boxed 2 days ago'12th ..Aug..2022 '''(2019 new and never used)
Phone was flat needed 12 hours charge
As as phone booted it came up as Android 9 with 2019 patch
As soon as it found interest it started to update itself
After a hour it finished update and after final reboot
the a6 plus is now Android 10/10q with 2021 patch
The Stupid question is what firmware do I root with Android 9 or Android 10

How to make Combination File for Samsung

Nowadays I have noticed that to unlock FRP lock in Samsung mobile there is need of combination file. It is very hard to find a combination file for the latest Android version. Mostly I use ******* to download the file. but now we can make our combination file with a stock firmware.
MOD EDIT: LINK REMOVED
First, download the FRP Hijacker by Haggard V1.0
Now install the FRP Hijacker after successfully install the FRP Hijacker
Open FRP Hijacker you will see the SAM TOOLS tab click on it
You will see the Create ADB Enabled File
Choose the Stock file in the file tab
Click on create a file it will take around 5 minutes to create combination file
After finish the process you will the see a zip file in the same folder.
Use latest Odin to flash this file
In case this file bricked the Samsung device flash the stock file.
{
"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"
}

Nice tutorial and very useful, but I have 5 files in the stock firware downloaded from samobile.What file should I select? AP, BL, CSC or CP?
Thanks

I have tried using AP file ... but it generated a 19 MB combination file .. while i see everywhere that the combination files are 1+ GB. @how2solutions Can you please let us know how to create combination file from multiple firmaware files (like we have now AB,BL, CP, CSC?) thanks!

killer0007 said:
Nice tutorial and very useful, but I have 5 files in the stock firware downloaded from samobile.What file should I select? AP, BL, CSC or CP?
Thanks
Click to expand...
Click to collapse
Select only AP file

Hello.
I have tried with AP only, but it creates a combination file of about 20 MB, while all other combination files have 1.2 GB.
I have looked into the files, and the small one has only boot image, while the other has all the images.

It doesn`t work for Samsung Galaxy S9, S9+, Note9

Ah. Ok. Does someone knows how the combination files are created for this devices?

rhadoo_ds said:
Hello.
I have tried with AP only, but it creates a combination file of about 20 MB, while all other combination files have 1.2 GB.
I have looked into the files, and the small one has only boot image, while the other has all the images.
Click to expand...
Click to collapse
Same for me,i have Samsung S8+

I guess this is for adb enable with flash to bypass frp lock not a real combination file.

rhadoo_ds said:
Hello.
I have tried with AP only, but it creates a combination file of about 20 MB, while all other combination files have 1.2 GB.
I have looked into the files, and the small one has only boot image, while the other has all the images.
Click to expand...
Click to collapse
It is the ADB enabler, when i flashed my stock firmware it came out only 20 mb when the stock rom is like 1.8 GB .....

I have seen a lot of combination files for n960u and u1. But it seems you only need this to solve FRPs and google locks. do these combo files have anything to do with root? Seems not. But what about EFS folder access? Can anyone enlighten me?
If I flash a combo firmware in my phone that is not locked in anyway will I brick it?

This tool is not to create combination rom
It is the tool to open adb
I can't get the stock rom
because boot.img.ext4 in the rom will not be able to unlock ADB
ie you have to choose COMBINATION rom
This tool will extract boot.img.ext4 from combination rom
form a TAR file, you can flash this file to unlock ADB
MEANING FOR THE COMBINATION OF THE WHOLE FLASH, THIS TOOL IS EXTRACTED BOOT.IMG
you will be able to open ADB, maybe FRP)
But I think this way will not work on new phones, because when you flash BOOT.IMG, the phone will be hung on the logo.
This topic has not been verified, the poster has tried to copy from a certain source

Select only AP file
killer0007 said:
Nice tutorial and very useful, but I have 5 files in the stock firware downloaded from samobile.What file should I select? AP, BL, CSC or CP?
Thanks
Click to expand...
Click to collapse
when you download stock ROM you have to select only AP file to make ADB enabled file.
:good:

Is the Samsung series A successful with the combination file?

Ahmab78 said:
Is the Samsung series A successful with the combination file?
Click to expand...
Click to collapse
Every time I attempt to flash an official Samsung Combination file to my SM-A516U, I am greeted with a message telling me I need permission to use an official binary (PIT). So, I use a the correct PIT file for my mobile and I'm told I need permission for official binary (BOOTLOADER). I'm guessing the bootloader is locked? Any body else attempting to make progress with the A series?

how2solutions said:
Nowadays I have noticed that to unlock FRP lock in Samsung mobile there is need of combination file. It is very hard to find a combination file for the latest Android version. Mostly I use ******* to download the file. but now we can make our combination file with a stock firmware.
MOD EDIT: LINK REMOVED
First, download the FRP Hijacker by Haggard V1.0
Now install the FRP Hijacker after successfully install the FRP Hijacker
Open FRP Hijacker you will see the SAM TOOLS tab click on it
You will see the Create ADB Enabled File
Choose the Stock file in the file tab
Click on create a file it will take around 5 minutes to create combination file
After finish the process you will the see a zip file in the same folder.
Use latest Odin to flash this file
In case this file bricked the Samsung device flash the stock file.
Click to expand...
Click to collapse
6. Click on create a file it will take around 5 minutes to create ADB enable file

hi i want to make a combination file , that i can flash it into a phone and then unlock FRP lock . please help me . i have no other choices.

Thread closed.

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?