{
"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"
}
Official TWRP support for Xperia ZR.
WARNING! New versions of TWRP not compatible with Android Lollipop (5.0/5.1.1) due to SELinux rejection
Download links:
Latest TWRP image file : https://drive.google.com/open?id=0B7CPZEsTdmVda19qckNlcEFhUlU
Latest flashable TWRP image : https://drive.google.com/open?id=0B7CPZEsTdmVdbU1hS09xZ2JncWs
FOTA Cleaner: https://drive.google.com/open?id=0B7CPZEsTdmVdMWY0VUhadFFMekE
TWRP folder (on GoogleDrive): https://drive.google.com/open?id=0B7CPZEsTdmVdQ3ZPUmFXbnVhdU0
Device page: https://twrp.me/sony/sonyxperiazr.html
TWRP Changelog: https://twrp.me
Latest compatible TWRP version with Android 5.0/5.1.1:
TWRP image file : https://basketbuild.com/filedl/devs...pa_a/dogo/TWRP-Recovery/twrp-3.0.3-0-dogo.img
Flashable TWRP image : https://basketbuild.com/filedl/devs...a_a/dogo/TWRP-Recovery/TWRP-v3.0.3-0-dogo.zip
Stock kernel (.222/.228) with TWRP 3.0.3: https://basketbuild.com/filedl/devs?dev=Chippa_a&dl=Chippa_a/dogo/TWRP-Recovery/stock/boot.img
Flashable stock kernel (.222/.228) with TWRP 3.0.3: https://basketbuild.com/filedl/devs...P-Recovery/stock/TWRP-v3.0.3-0-stock-dogo.zip
Installation Instructions
Manual install to FOTA:
Code:
adb root
adb wait-for-device
adb push patchtoimage.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Update the installed version:
Download flashable zip
Enter the Recovery as usual
Flash
Deleted
I flashed the zip using my current TWRP (which is in the FOTAKernel partition) and now I cannot boot to recovery, it'll restart itself and try to get to recovery creating a bootloop. Any idea how to solve this?
sieem said:
I flashed the zip using my current TWRP (which is in the FOTAKernel partition) and now I cannot boot to recovery, it'll restart itself and try to get to recovery creating a bootloop. Any idea how to solve this?
Click to expand...
Click to collapse
Download the attached zip, extract recovery.img and put it in your sdcard.
Download and open Terminal then type
"su" enter
"dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" enter, without the quotes ofc.
reboot to recovery.
Also, could you test something? I edited the default.prop of the recovery for dogo(5502), see if you get the assert error while flashing ROMs, that is if you want to.
sufoalmighty said:
Download the attached zip, extract recovery.img and put it in your sdcard.
Download and open Terminal then type
"su" enter
"dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" enter, without the quotes ofc.
reboot to recovery.
Also, could you test something? I edited the default.prop of the recovery for dogo(5502), see if you get the assert error while flashing ROMs, that is if you want to.
Click to expand...
Click to collapse
Thanks, the terminal command worked flawlessly (I only needed to change sdcard to storage/sdcard1).
I installed your zip and downloaded the latest official cm12.1 nightly, no assert problems. I got the LTE version of dogo, but I guess "dogo" in the build.prop is enough to pass the test in the updater script.
i downloded https://dl.twrp.me/dogo/twrp-3.0.0-1-dogo.img.html and then use the dd comand to flash to FOTA parittion, now my phone boot loops if I try to enter recovery
nostupidthing said:
i downloded https://dl.twrp.me/dogo/twrp-3.0.0-1-dogo.img.html and then use the dd comand to flash to FOTA parittion, now my phone boot loops if I try to enter recovery
Click to expand...
Click to collapse
You read "Warning"?
Oh crap me.... Sorry
Added STOCK kernel (.228) with TWRP 3.0.0.
Hey! Links are updated. Now it's a new version 3.0.1 and supported Lollipop!
Also updated in stock kernel.
Enjoy
Can you make a flashable. 228 kernel??
neildalal said:
Can you make a flashable. 228 kernel??
Click to expand...
Click to collapse
I'm using this
http://forum.xda-developers.com/xpe...t/zip-flashable-zip-kernel-xperia-zr-t3026295
Just put boot.img to zip,,and flash,,
jabr1G said:
I'm using this
http://forum.xda-developers.com/xperia-zr/orig-development/zip-flashable-zip-kernel-xperia-zr-t3026295
Just put boot.img to zip,,and flash,,
Click to expand...
Click to collapse
How do I put the image file in the zip??
neildalal said:
How do I put the image file in the zip??
Click to expand...
Click to collapse
Extrack the zip with root explorer,go to extraced if you finish,,and copy the boot img in folder,,then zip again,,
Or if using pc open zip with 7zip then drage and place boot img,,finish flash with recovery,
Chippa_a said:
Hey! Links are updated. Now it's a new version 3.0.1 and supported Lollipop!
Also updated in stock kernel.
Enjoy
Click to expand...
Click to collapse
Can I install Twrp 3.0.1 on LB?
Sent from my C5503 using Tapatalk
ostadmaster said:
Can I install Twrp 3.0.1 on LB?
Sent from my C5503 using Tapatalk
Click to expand...
Click to collapse
Thanks for update!
nostupidthing said:
Thanks for update!
Click to expand...
Click to collapse
Are You Ok?
I'm not deceloper.
I asked my question
:/
Sent from my C5503 using Tapatalk
ostadmaster said:
Are You Ok?
I'm not deceloper.
I asked my question
:/
Sent from my C5503 using Tapatalk
Click to expand...
Click to collapse
no, you are okay no
---------- Post added at 07:07 PM ---------- Previous post was at 06:48 PM ----------
nevermind all is working now, it's just taking a very long time to boot
---------- Post added at 07:07 PM ---------- Previous post was at 07:07 PM ----------
but why is it the new version takes so long to boot??
nostupidthing said:
after flashing flashable zip 3.0.1-0, can no longer boot into TWRP, stuck in splash logo, what can I do
Click to expand...
Click to collapse
Please don't quote the whole post, read the forum rules.
Regarding boot speed: I have no such problem watching. All loaded quickly and works perfectly. Maybe you did something wrong?
Just need improve flashable archive for CM recovery. Will be later...
______________
All archives updated for CM recovery and added flashable stock kernel with TWRP!
Sorry.
Yes there's probably some problems with my device, could be hardware, it cannot reboot normally now, must wipe davik cache, or it will stay in the cm flashing logo forever......
Related
Originally posted by Koushik Dutta on Google+:
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes: update from 09.05.11
Fix the fact that some users were loosing root access with 5.0.1.0
Fix menu bug Even if you select no during wipe dalvik cache, it still says it wipes it (it is not actually wiping it, it is just a display bug)
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
Click to expand...
Click to collapse
To flash recovery for Nexus S, download recovery and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
ill try
Sent from my Google Nexus S using XDA Premium App
I'm on it!
Or you can directly flash it from Rom Manager
You can also just put it on SD and flash from terminal then reboot.
Edit- before someone asks
su(press enter)
flash_image recovery /sdcard/5014cw.img(press enter)
reboot recovery(press enter)
Obviously the sdcard/* is whatever you rename the file
sent from my nexus s on a kang from simms
zadnica said:
Originally posted by Koushik Dutta on Google+:
To flash recovery for Nexus S, download recovery and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
I wish I would have seen this BEFORE I updated. It kept taking me to bootloader screen!!!!! But I unistalled and installed and finally got it to work!
Sent from my Nexus S using Tapatalk
Hey guys,
Everytime I restore from a backup through Rom Manager with the new recovery, I lose root. Right now, I'm stuck at work and cannot flash a rom, theme, battery mod, etc. I'll go back to 4.0.1.4 as soon as I go home
Am I the only one?
Edit: Found a solution==> Reboot into Recovery, flash su.zip again, and it's all good now!
f.
suhas_sm said:
Or you can directly flash it from Rom Manager
Click to expand...
Click to collapse
doesn't work for me..
I always recommend not using rom manager for anything flashing related, most problems occur for people when they're using rom manager and get fixed when done through recovery or in this case terminal/adb
RevengeITA said:
doesn't work for me..
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
sinik420 said:
I always recommend not using rom manager for anything flashing related, most problems occur for people when they're using rom manager and get fixed when done through recovery or in this case terminal/adb
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
I prefer my previous post using terminal
zadnica said:
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
It took me two or three tries through terminal
Robin_216 said:
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
Robin_216 said:
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
Click to expand...
Click to collapse
What the errors?
Worked like a charm thanks
Backups are significantly faster, thanks. (Flashed using fastboot)
zadnica said:
What the errors?
Click to expand...
Click to collapse
{
"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 are the errors that appear. I however managed to flash it with rom manager after some tries so it works now.
Sent from my Nexus S using XDA App
Robin_216 said:
These are the errors that appear. I however managed to flash it with rom manager after some tries so it works now.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I had the same issue. What helped for me was (in Terminal) :
su
mount -o rw,remount /dev/block/mtdblock3 /system
chmod 755 /system/bin/flash_image (wait for a minute)
(Reboot if the next step didn't work)
flash_image recovery /sdcard/RECOVERY.img
Click to expand...
Click to collapse
If I use the latest one, can I boot into recovery by using Rom manager? Will Rom manager detect my latest clockworkmod?
Accidentally sent from my Nexus S using XDA Premium App
Strangely, *immediately* after flashing the new recovery, I have begun to experience the Nexus S Google Voice Search bug. In the two months I've had the phone, this never happened - not even once.
This was with a two week old CM nightly, and a Matrix kernel.
Regardless - I'm hoping we'll start to see 2.3.6 kernels/roms come out soon which will fix it permanently. I'm just shocked that this issue popped up immediately after flashing the updated Clockwork.
{
"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"
}
THIS IS A PROXY THREAD Creator and Maintainer is pershoot
This is CWM for the ASUS Transformer Pad (TF701T – Macallan).
-You must be unlocked (use ASUS’s unlock tool to perform this)
-You must be on 10.26.1.18 bootloader (updating to ASUS’s latest 4.3 release will install this)
For complete Info and Download: VISIT HERE
***Once there, check out the Recent Entries on the right side of the page for latest updates***
-Unlock your device using the ASUS Unlock tool.
-Boot in once and execute: adb reboot bootloader
Fastboot:
To boot the recovery:
fastboot boot recovery.img
To permanently flash the recovery:
fastboot flash recovery recovery.img
Source:
https://github.com/pershoot/android_device_asus_tf701t
https://github.com/pershoot/android_kernel_asus_tf701t
https://github.com/CyanogenMod/android_bootable_recovery
Creator and Maintainer:
@pershoot
Video Tutorial
Video Tutorial Thanks @wwjoshdew
Ah just saw screenies. Nice job pershoot.
Why is the version still 6.0.4.6?
CWM 6.0.4.7
OP Updated
Feb/2 OP updated
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
I was on 6.0.4.6 and i used flashify to update. Worked fine.
hetzbh said:
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
Click to expand...
Click to collapse
Both cromix and cm11 will require the latest bootloader to eliminate compatibility issues it is recommended to flash to the latest asus firmware
Sent from my SGH-T889 using XDA Premium 4 mobile app
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
wwjoshdew said:
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
Click to expand...
Click to collapse
included in the post alongside the screenshots. Thanks a lot!!!
OP updated 2/16, installation video tutorial included. Thanks to @wwjoshdew
recovery updated with baseline build and sorted dock sd card functionality and usbdisk functionality.
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
sbdags said:
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
Click to expand...
Click to collapse
i'll look in to it...
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
lortay78 said:
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
Click to expand...
Click to collapse
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
sbdags said:
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
Click to expand...
Click to collapse
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
lortay78 said:
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
Click to expand...
Click to collapse
Very common mistake that happens to the best of us
updated.
Hi,
I spent hours trying to get this to work before discovering there are two missing steps in the OP's instructions.
There's a shell script that calls an application that restores the stock boot loader on every boot.
You have to delete it.
Steps:
1. Root.
2. Install Root Explorer.
3. Go into /etc
4. Delete install_recovery.sh
5. Go into /system
6. Delete recovery-from-boot.p
You have to delete the files. You can't just rename them or change the extension because the system actually searches the filesystem for a file whose contents matches an MD5 hash and will find it if you rename it.
After you do this, THEN follow OP's instructions.
{
"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"
}
ClockworkMod recovery is a recovery designed by Koushik Dutta
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements:
Any Android One device with Unlocked Bootloader
Unlocking the bootloader:
Reboot to fastboot mode
Execute following commands
Code:
fastboot oem unlock
fastboot format userdata
Note: You will lose all data of your's after this
Install recovery through fastboot:
Download the recovery.img from here
Reboot the phone into bootloader/fastboot mode
Code:
adb reboot bootloader
Flash the recovery image and reboot
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot
Note: In the install menu, do not select /sdcard because we don't have internal storage which is meant for anything other than installing apps. We only have external sd which is /external_sd which you have to select. This applies for backup and restore and every other operation involving the sdcard.
XDA:DevDB Information
CWM Recovery, a Recovery for Android One devices
Contributors
varun.chitre15
Version Information
Status: Testing
Created 2014-09-24
Last Updated 2014-09-24
good work!!
have cwm now.
are you going to release recovery sources???
Ok!! Awesome!! but...
Will we get the OTA Updates and will the ota update install successfully with this recovery.... i am scared.... if it dosent... can anyone post the stock recovery (or the rom) image... Thanks forur hard work.. :laugh:
alaap_surendran said:
Will we get the OTA Updates and will the ota update install successfully with this recovery.... i am scared.... if it dosent... can anyone post the stock recovery (or the rom) image... Thanks forur hard work.. :laugh:
Click to expand...
Click to collapse
posting stock recovey is not possible yet because there is no root method without cwm.
when OP get the DEVICE(mostly this saturday) he will put more methods for root without cwm.
that time he will post stock recovery too. so have little patience.
k2wl said:
posting stock recovey is not possible yet because there is no root method without cwm.
when OP get the DEVICE(mostly this saturday) he will put more methods for root without cwm.
that time he will post stock recovery too. so have little patience.
Click to expand...
Click to collapse
whenever i reboot i go to cwm. help? is this one of those recoveries where u have to reflash the stock one before rebooting?
Recognized Noob said:
whenever i reboot i go to cwm. help?
Click to expand...
Click to collapse
have you formated userdata partition???
it may be bad flash
go back to fastboot mode
format cache,data and system and then flash cwm.
reboot
k2wl said:
have you formated userdata partition???
it may be bad flash
go back to fastboot mode
format cache,data and system and then flash cwm.
reboot
Click to expand...
Click to collapse
i go to cmd and do fastboot format system then cache followed by userdata and then flash but still nothing. help
Edit: now i am stuck at Karbonn logo. please help
k2wl said:
posting stock recovey is not possible yet because there is no root method without cwm.
when OP get the DEVICE(mostly this saturday) he will put more methods for root without cwm.
that time he will post stock recovery too. so have little patience.
Click to expand...
Click to collapse
Recognized Noob said:
whenever i reboot i go to cwm. help? is this one of those recoveries where u have to reflash the stock one before rebooting?
Click to expand...
Click to collapse
I am not going to flash this until the OP gets his Android One Device... Thanks @k2wl ......
Sent from my Nexus 7 using XDA Free mobile app
k2wl said:
have you formated userdata partition???
it may be bad flash
go back to fastboot mode
format cache,data and system and then flash cwm.
reboot
Click to expand...
Click to collapse
Why would you suggest him to format system?
Recognized Noob said:
i go to cmd and do fastboot format system then cache followed by userdata and then flash but still nothing. help
Edit: now i am stuck at Karbonn logo. please help
Click to expand...
Click to collapse
You now have to wait for someone to dump system image to be able to boot into system because you just formatted it. I will do it once I have my phone.
If you had followed the instructions cut to cut you might not have faced this.
k2wl said:
have you formated userdata partition???
it may be bad flash
go back to fastboot mode
format cache,data and system and then flash cwm.
reboot
Click to expand...
Click to collapse
cam u atleast gimme system.img?
Recognized Noob said:
cam u atleast gimme system.img?
Click to expand...
Click to collapse
I don't have it yet. As I said you have to wait for someone to dump the system partition which will happen once this recovery is fixed to read sdcards
varun.chitre15 said:
I don't have it yet. As I said you have to wait for someone to dump the system partition which will happen once this recovery is fixed to read sdcards
Click to expand...
Click to collapse
i had extracted the folder system previously. can it be used somehow?
Recognized Noob said:
i had extracted the folder system previously. can it be used somehow?
Click to expand...
Click to collapse
No
@ Recognized Noob
https://s.basketbuild.com/filedl/devs?dev=k2wl&dl=k2wl/stocksystem.img.zip
this is system img form my device
i have formatted my system and i didn’t get any boot loop.
anyway sorry for inconvenience.http://forum.xda-developers.com/member.php?u=5393124
Just a warning: Do not attempt to do a backup in the recovery because there is no where to store it
for me everything work in smooth like butter...I have rooted installed cwm
varunrocks17 said:
for me everything work in smooth like butter...I have rooted installed cwm
Click to expand...
Click to collapse
Can you dump the boot.img if you have adb?Run:
Code:
su dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img
And upload the boot.IMG from your internal memory.
##W4TCH0UT## said:
Can you dump the boot.img if you have adb?Run:
Code:
su dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img
And upload the boot.IMG from your internal memory.
Click to expand...
Click to collapse
Please keep the threads free from OT. Stock boot image is attached
Please someone provide guide for adb
I've rooted my galaxy y previously but it didn't require adb commands if someone could provide me guide for setting up adb it would be really helpful and how to go to recovery mode in this device?
k2wl said:
@ Recognized Noob
https://s.basketbuild.com/filedl/devs?dev=k2wl&dl=k2wl/stocksystem.img.zip
this is system img form my device
i have formatted my system and i didn’t get any boot loop.
anyway sorry for inconvenience.http://forum.xda-developers.com/member.php?u=5393124
Click to expand...
Click to collapse
BTW which variant of phone u have?
Sent from my Micromax AQ4501 using Tapatalk
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!
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?