Related
HTC One (M9) ReadMe Thread
Q4: Which versions of TWRP and SuperSU are the recommended ones?
A: The answer depends on your current firmware version. If you're using firmware 4.x then you'll find your answer here in the FAQ of the TWRP thread. (Click here, if you can't find SuperSU 2.79 SR3.) For firmware 1.x and 2.x the recommended versions are Captain_Throwback's Beta 1 of TWRP 2.8.7.1 and SuperSU 2.49. For firmware 3.x the recommended versions are TWRP 3.1.1-0 (official) and SuperSU 2.65. Using different versions than the recommended ones will probably lead to a bootloop. The M9 isn't compatible with the ramdisk changes that get executed by many flashable system-less SuperSU versions. However, updating the SuperSU app and its binaries via the Play Store after flashing one of the older versions is safe.
Q5: Are there alternative methods for gaining root?
A: Yes, you can use Magisk if you're using firmware 4.x. (Maybe a user with a lower firmware version can test whether Magisk is usable on firmware 1.x to 3.x, as well?)
Click to expand...
Click to collapse
Requirement
1. S-OFF AND UNLOCKED BOOTLOADER OF HTC ONE M9 (FILE PROVIDED IS FOR INTERNATIONAL VERSION. IF YOU WANT CREATE YOUR CARRIER PHONE COMMENT BELOW )
Method
STRAIGHT TO THE POINT just download the 2 zips provided below and place it in external sd card of phone and reboot to download mode
It will ask to flash press the vol up button and after flash you will have twrp flashed (i had included latest twrp recovery in the zip file but you can place in zip the recovery of your choice but you have to rename it to recovery.img)
NOTE DONT RENAME THE ZIP OR ELSE IT WILL NOT FLASH AND SECONDLY DONT CHANGE THE TXT FILE IN THE ZIP
after flash go to recovery and flash supersu zip
Downloads
Mod Removed
Help Section
Comment or pm me if you are facing any problem and want to get help
If you liked my work hit the appreciation button and if you want to grow my projects donate me as i dont have enough resources
Don't spam. Your previous thread exactly like this has been closed. Can't you take the message from that?
http://forum.xda-developers.com/showthread.php?t=3530127
Hope a mod sees this soon.
Sent from my HTC One M9 using Tapatalk
shaqman89 said:
Don't spam. Your previous thread exactly like this has been closed. Can't you take the message from that?
http://forum.xda-developers.com/showthread.php?t=3530127
Hope a mod sees this soon.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
First of all i am sorry for the previous post.
In my previous post, it was my 1st time i posted anything.I dont know the rules. But now i had got all the rules etc. In previous post i also used some useless terms such as "custom recovery" but in this post everything is ok.
Previous post was closed by moder because i used adf for some earning
But in this the downloads are on direct androidfilehost.com
You can match the md5 in the twrp zip of recovery.img with the md5 of of twrp 3.0.2 at thier website for verification
And try before saying anything
If it will be spam than report about my post
ahmad.abbas54 said:
First of all i am sorry for the previous post.
In my previous post, it was my 1st time i posted anything.I dont know the rules. But now i had got all the rules etc. In previous post i also used some useless terms such as "custom recovery" but in this post everything is ok.
Previous post was closed by moder because i used adf for some earning
But in this the downloads are on direct androidfilehost.com
You can match the md5 in the twrp zip of recovery.img with the md5 of of twrp 3.0.2 at thier website for verification
And try before saying anything
If it will be spam than report about my post
Click to expand...
Click to collapse
You're posting links to outdated versions of both TWRP and SuperSU. The latest versions and guides on how to install them already exist in their official threads.
If you want to be a help, try your hand at questions people are actually asking instead. XDA can always use another helpful expert.
computerslayer said:
You're posting links to outdated versions of both TWRP and SuperSU. The latest versions and guides on how to install them already exist in their official threads.
If you want to be a help, try your hand at questions people are actually asking instead. XDA can always use another helpful expert.
Click to expand...
Click to collapse
Really!! All those methods require a pc. My method is without pc
And Dont miss guide or lie and for your information both twrp and supersu is updated one
Talk before speak
Proofs are attached
ahmad.abbas54 said:
Really!! All those methods require a pc. My method is without pc
And Dont miss guide or lie and for your information both twrp and supersu is updated one
Talk before speak
Proofs are attached
Click to expand...
Click to collapse
I'm sorry if I've offended you - that wasn't my intention. However, you are mistaken about me lying or misguiding others.
Go check out the official TWRP thread. The latest version is posted there - it's version 3.0.3-0.
Check out the official SuperSU thread. The latest version is posted there - it's version 2.79 SR1 (2016-12-22).
Both of these versions, by the way, are important because they address issues that are unique to the M9. Previous versions of TWRP couldn't decrypt HTC's stock encryption. Recent versions of SuperSU couldn't be flashed directly. I'm sure there are other general fixes included as well.
You've got a neat idea, and I commend you for it. But if you're not working with the latest software - and passing it off as the latest - you're adding to people's confusion rather than helping them.
computerslayer said:
I'm sorry if I've offended you - that wasn't my intention. However, you are mistaken about me lying or misguiding others.
Go check out the official TWRP thread. The latest version is posted there - it's version 3.0.3-0.
Check out the official SuperSU thread. The latest version is posted there - it's version 2.79 SR1 (2016-12-22).
Both of these versions, by the way, are important because they address issues that are unique to the M9. Previous versions of TWRP couldn't decrypt HTC's stock encryption. Recent versions of SuperSU couldn't be flashed directly. I'm sure there are other general fixes included as well.
You've got a neat idea, and I commend you for it. But if you're not working with the latest software - and passing it off as the latest - you're adding to people's confusion rather than helping them.
Click to expand...
Click to collapse
I am also sorry if i used some rude words
Still i had checked recently on twrp.me and there's only 3.0.2 for m9 and i am using it right now with supersu 2.79
I am not facing any problem at all in all matters and it is also much stable
You can still update according to your need as you can open up my provided zip and add recovery.img of your choice and also you can flash supersu of your choice
@ahmad.abbas54: What @computerslayer said is correct. There are numerous reports of users facing a bootloop after flashing any other SuperSU version than 2.64 (stable), 2.65 (stable) or the latest beta 2.79 SR1 (link to its thread) on their stock rom. However, flashing one of these three and updating SuperSU via the play store doesn't cause any problems. Therefore I'd ask you for not linking the stable version 2.79.
In regard to TWRP: 3.0.2-0 is working fine. However, it's not the recommended version since 3.0.3-0 (unofficial) is capable of installing HTC's official OTAs.
Flippy498 said:
@ahmad.abbas54: What @computerslayer said is correct. There are numerous reports of users facing a bootloop after flashing any other SuperSU version than 2.64 (stable), 2.65 (stable) or the latest beta 2.79 SR1 (link to its thread) on their stock rom. However, flashing one of these three and updating SuperSU via the play store doesn't cause any problems. Therefore I'd ask you for not linking the stable version 2.79.
In regard to TWRP: 3.0.2-0 is working fine. However, it's not the recommended version since 3.0.3-0 is capable of installing HTC's official OTAs.
Click to expand...
Click to collapse
Kindly elaborate me further about the super su zip which is stable in 2.64 2.79 ??
Btw I had given download link of version supersu 2.79 in my post
ahmad.abbas54 said:
Kindly elaborate me further about the super su zip which is stable in 2.64 2.79 ??
Btw I had given download link of version supersu 2.79 in my post
Click to expand...
Click to collapse
SuperSU changes parts of the ramdisk since the introduction of system-less root. However, the changes that get initiated by any other than the three versions I mentioned above are not compatible with the M9 and cause a bootloop. Updating via the play store only updates the app and its binaries but not the ramdisk changes. This way you could update to a newer version of supersu (before 2.79 sr1 got released) without facing a bootloop.
There are stable and beta releases of SuperSU. Both are different stages of a "software release cycle". (The " " mark the keyword you need to google for further information. At the moment I don't have the time for writing a more detailed post. Sorry.)
You linked the stable version of 2.79. The beta which is safe to use got released a week later than the version in your post and it contains "sr1" in its naming.
Edit: Oh and please don't re-upload files to your afh account that you don't own (e.g. SuperSU) unless you got the permission of the dedicated owner/dev. Your 0PJAIMG.zip should be fine as long as you mention TWRP's devs in the credits of your OP.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
SuperSU changes parts of the ramdisk since the introduction of system-less root. However, the changes that get initiated by any other than the three versions I mentioned above are not compatible with the M9 and cause a bootloop. Updating via the play store only updates the app and its binaries but not the ramdisk changes. This way you could update to a newer version of supersu (before 2.79 sr1 got released) without facing a bootloop.
There are stable and beta releases of SuperSU. Both are different stages of a "software release cycle". (The " " mark the keyword you need to google for further information. At the moment I don't have the time for writing a more detailed post. Sorry.)
You linked the stable version of 2.79. The beta which is safe to use got released a week later than the version in your post and it contains "sr1" in its naming.
Edit: Oh and please don't re-upload files to your afh account that you don't own (e.g. SuperSU) unless you got the permission of the dedicated owner/dev. Your 0PJAIMG.zip should be fine as long as you mention TWRP's devs in the credits of your OP.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ok i will be carefull next time
Had anyone achieved root with my method before??
I mean without pc
ahmad.abbas54 said:
Ok i will be carefull next time
Had anyone achieved root with my method before??
I mean without pc
Click to expand...
Click to collapse
Well, no one ever posted explicit instructions but it should be known to be possible from Sneakyghost's firmware thread. His firmware packs can get flashed via the SD card method, as well, and your archive is somehow similar to his no wipe packs. The difference is that your archive only contains TWRP whereas his packs contain almost the full stock firmware and TWRP instead of the stock recovery.
Nevertheless, step by step instructions like to ones in this thread are always nice to have.
(Although strictly speaking a PC is needed for your method, too, since you can't achieve S-OFF via Sunshine* without root on the M9 and for rooting the M9 the first time you need to unlock the bootloader which requires a PC. However, don't mind my nitpicking. )
* I have not much knowledge about how to use java cards for the same purpose but I think you need a PC for them, as well.
Flippy498 said:
Well, no one ever posted explicit instructions but it should be known to be possible from Sneakyghost's firmware thread. His firmware packs can get flashed via the SD card method, as well, and your archive is somehow similar to his no wipe packs. The difference is that your archive only contains TWRP whereas his packs contain almost the full stock firmware and TWRP instead of the stock recovery.
Nevertheless, step by step instructions like to ones in this thread are always nice to have.
(Although strictly speaking a PC is needed for your method, too, since you can't achieve S-OFF via Sunshine* without root on the M9 and for rooting the M9 the first time you need to unlock the bootloader which requires a PC. However, don't mind my nitpicking. )
* I have not much knowledge about how to use java cards for the same purpose but I think you need a PC for them, as well.
Click to expand...
Click to collapse
Well thats for obvious that we need pc for atleast bootloader unlock
I'm trying this method to flash TWRP on my unlocked, S-Off m9. (Unlocked with SunShine, my Mac with new USB-C port doesn't see device over ADB) I've unzipped your TWRP package, replaced the old TWRP with the latest--renamed "recovery.img"--and re-zipped it. When I boot phone into Download mode, the script recognizes the zip package, and "start ui-update" appears at the top of the screen. Nothing else happens, and if I eventually force power off, the stock Recovery is still installed. Suggestions?
Do S-OFF AND UNLOCKED BOOTLOADER not need a computer ؟؟؟؟؟؟
!!!!!!!!!!!!!!
Please close this trivial matter
Last update: 14.10.2017
Fantastic news
No more waiting for manually signed magisk, supersu or twrp versions from now on. Just install any new version and use the image signature fix action in the troubleshoot menu of the toolkit. :good:
Next level reached
No more waiting for special zenfone 2 patched xposed for magisk. Got my own zip to do some hex patching. You can either use one of the (already patched) xposed versions from the toolkit or download xposed for magisk and use the xposed patcher in the troubleshoot menu.
z00x users please read this post https://forum.xda-developers.com/showpost.php?p=72298931&postcount=214
Introduction
This is a windows batch toolkit for automated actions like bl unlock, flash, root, xposed, sideload tasks, ... for your ze551ml/ze550ml/zx551ml.
I hope you find it useful. Check the tabs above for more screenshots, downloads, review ...
Note:
This tookit works well for a lot of situations, but I need feedback especially for the new supported devices ze550ml and zx551ml. Please go on and try the toolkit, then leave a message on this thread, do a review or just vote.
Before you try any action in the menu, check that the device informations are shown.
Features
Supports ZE551ML, ZE550ML, ZX551ML
Device status and connection information
Automated actions
Bootloader unlock
Flash boot/recovery images (twrp, stock)
Fix wrong or missing image signatures!!
Root / unroot Magisk & SuperSU
Xposed for Magisk (install / uninstall)
Patching xposed for magisk for zenfone 2 (if installed the unpatched xposed for magisk by mistake)
Compatible with most current MM firmware versions from devices ZE551ML, ZE550ML, ZX551ML
Currently integrated Tools
v14.0 (default) and v14.2
SuperSU 2.79SR3 / 2.82 (default) / 2.82SR5
TWRP 3.0.3-M4 / 3.1.1 (default)
Xposed for Magisk v87.3 / v88.0 (default)
Stock boot/recovery support of most current MM firmware versions from devices ZE551ML, ZE550ML, ZX551ML
adb/fastboot 1.0.32 (optional: 1.0.36)
Installation instructions
Do a clean start:
Download the latest base package
Extract to your desired location. It will extract a "ze551ml toolkit" directory with all files.
(Optional / If the automatic download of the device specific files fails) Download the device specific packages and extract it directly to the "ressources" directory
To run the toolkit just execute "ze551ml toolkit.bat" (no admin rights are needed).
Usage instructions
Prerequisite:
Ensure that you have installed device usb drivers (e. g. see: https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/ )
Ensure that you have one of the latest MM firmwares for your device installed.
Ensure that you have enabled USB Debugging in Developer Options
Even if only a few actions could be really harmful to your data: Get a backup!
Then:
Run ze551ml_toolkit.bat
Check device status information & see if toolkit really likes your device
If your bootloader is still locked: Unlock it first with menu B -> choice U
(Optional) Choose your desired versions of the integrated tools in menu O.
(Recommended) Flash twrp with menu F -> choice T. If you want to try a newer twrp version, change it first in menu O
Check all the other nice functions of the toolkit
Downloads
Main: xda devdb archive
Mirror 1: https://mega.nz/#F!u8JhhY7T!9PryiRdjVSFf-O4erijDWg
Mirror 2: https://drive.google.com/drive/folders/0B4r2bJ3AgndSRVl5djNPNV9Qbkk?resourcekey=0-i9dHUezdzckVemi93NlYLA&usp=sharing
File structure:
ze551ml-toolkit-<VERSION>-base.zip - contains the base toolkit package without any device specific files
z00a*.zip - contains all device specific files for Z00A (ZE551ML)
z008*.zip - contains all device specific files for Z008 (ZE550ML)
z00x*.zip - contains all device specific files for Z00X (ZX551ML)
Changelog
Code:
[B]v1.3[/B]
Current changelog: 14.10.2017
[added] xposed for magisk v88.0
[new] Patching xposed for magisk for zenfone 2 (if installed the unpatched version by mistake)
Code:
[B]v1.22[/B]
Current changelog: 08.10.2017
[added] magisk v14.2
[removed] magisk v13.3
[fixed] xposed for magisk v87.3
[new] Fix wrong or missing image signatures!!
[fixed] Better support for encrypted devices
Code:
[B]v1.1b9[/B]
Current changelog: 22.09.2017
[added] magisk v14.0
[removed] magisk <v13.3
[removed] twrp 3.0.2-M1
[updated] magisk uninstaller
Code:
[B]v1.1b8[/B]
Current changelog: 19.07.2017
[added] magisk v13.3
[updated] magisk uninstaller
[new] action to download latest mirror file which is used to get some stock files updates
Code:
[B]v1.1b6[/B]
Current changelog: 13.07.2017
[added] magisk v13.2
[removed] magisk v13.1
[fixed] twrp detection
[modified] magisk manager will now be extracted from zip and installation will be forced after sideload
Code:
[B]v1.1b5[/B]
Current changelog: 11.07.2017
[added] magisk v13.1
[removed] magisk v13 betas
[fixed] minor fixes in supersu actions
Code:
[B]v1.1b3[/B]
Current changelog: 02.07.2017
[added] 2 magisk v13 beta versions
[removed] magisk <v12
[updated] xposed installer
[added] 2 more twrp versions
[fixed] hardened detection of installed twrp version (still needs root or already booted twrp for that)
[fixed] changed the way the toolkit downloads files
Code:
[B]v1.0b10[/B]
Current changelog: 04.04.2017
[added] magisk v12.0
[updated] fixed some help messages
Code:
[B]v1.0b8[/B]
Current changelog: 21.03.2017
[added] support for more devices: z00a, z00d, z00x
[added] automatic download for device files if needed
[added] magisk v11.6
[added] twrp 3.0.3-M4 (for encrypted devices or android n installations
[added] backup efs function
[added] integrity check
[modified] menu structure
[updated] changed some help messages
Code:
[B]v1.0b2[/B]
Current changelog: 14.02.2017
[modified] menu order
[disabled] usage of system installed platform tools, internal are forced now
[fixed] boot2recovery could have been failed in some cases
[fixed] timing problems in wipe routine
[added] validations added to each boot states
[removed] twrp 3.0.3.2
[adjusted] code / function names
Code:
[B]v0.9[/B]
Current changelog: 07.02.2017
[added] new twrp 3.0.3.2
[added] new magisk v11.1
[disabled] second disclaimer
[disabled] bootloader status in device overview at the top as I haven't found a secure way to detect a locked/unlocked bootloader yet.
[removed] magisk v10.2
[removed] twrp 3.0.3-N
Code:
[B]v0.7[/B]
Current changelog: 02.02.2017
[added] boot to safe mode
[added] wipe menu
[added] new twrp 3.0.3-N and platform tools 1.0.3.6 (no default yet. versions can be switched in troubleshoot menu for testing)
Code:
[B]v0.5[/B]
Current changelog: 31.01.2017
[added] each action shows some information about what's going to happen now
[changed] each action must be confirmed to be executed. if you don't need that, enable auto-yes in troubleshoot menu
Code:
[B]v0.3p1[/B]
Changelog: 28.01.2017
[fixed] added missing magisk manager to installation procedure
Thanks to/Credits
Code:
:: > shakalaca
:: > chainfire
:: > topjohnwu
:: > twrp
:: > social-design-concepts
:: > phhusson
:: > say99
:: > Deathschythe33
:: > ggrandou
:: > gerasiov
You'll find more credits inside the source code.
I hope i didn't forget anyone. If so please report.
XDA:DevDB Information
Zenfone 2 ToolKit [Z00A/Z008/Z00X], Tool/Utility for the Asus ZenFone 2
Contributors
rummsbumms
Version Information
Status: Stable
Current Beta Version: 1.3
Beta Release Date: 2017-10-14
Created 2017-01-28
Last Updated 2018-07-31
Reserved
Reserved
What makes this different with @Giovix92's tool?
Yes, same question as above. What makes it different from ZE55xML_Modder by Giovix92
@krasCGQ @fred_gaou
i think that main difference is that this toolkit supports the last 3 MM firmware versions and works automatically for all tasks, so user interaction is reduced to wait & perhaps read
@rummsbumms
Question 1: would you suggest to run ze551ml_toolkit.bat as admin or not?
Question 2: did you personally test all root method provided by toolkit: SuperSU, Magisk+SuperSU, Magisk+phh superuser? Did you succeed to properly unroot all of them? Will you suggest one method rather than another?
Question 3: did you test custom ROM install via TWRP such as last LineageOS after unlock bootloader and install TWRP with your toolkit?
Question 4: What is "Auto Packages" supposed to mean? What does it do? According to script code, it seems to unroot and restore stock bootloader. That's why I don't understand the Auto Packages term.
====
To avoid having to get always the same questions like
How to root for the 1st time or safely upgrade firmware and root again…?
How to get back to a clean stock device?
What does this menu entry really do?
etc.
I would suggest some guide lines to help users in the 1st post as well as in a "how to.txt" file along the toolkit or in the batch itself as a menu entry named "Help" or "FAQ" or else.
====
FEATURES REQUEST
# Add FACTORY RESET DEVICE menu entry. This will imply:
Code:
fastboot erase userdata
fastboot erase cache
# Add Erase /system, /data and /cache menu entry, may be useful before installing a ROM. This will imply:
Code:
fastboot erase system (I guess it will work only if bootloader have been unlocked)
fastboot erase userdata
fastboot erase cache
or a complete wipe that will format the partitions too
Code:
fastboot -w
# Add a way to Back up and restore EFS, see this thread.
# And +1 to the post below about ifwi.
====
I would suggest also in the 1st post as well as in a "how to.txt" that the functions be more detailed. Example:
I see you chose to use adb/fastboot 1.0.32 version. Just to let you know that Minimal ADB and Fastboot v1.42 provide a more up to date adb and fastboot (the last 1.0.36). Why do you use this old 1.0.32 version?
====
I didn't test ZE55xML_Modder by Giovix92 or this toolkit yet, but just by reading the batch file, I can tell your code is way more elegant and skilled and should avoid the magisk root bug that ZE55xML_Modder users encounter.
====
And why checking if ADB is installed as system-wide since your toolkit already provides local adb/fasboot ? What's the point to add this "unnecessary" step ?
====
Great Work ! :good:
I will test your toolkit very soon and give feedback. I hope to get answers from you in the meantime.
Regards
What would be ideal , if possible to add
Is ..
An ifwi version detector
Because , there are a lot of people who flashed their phones who haven't a clue they have M version with LP bootloader.
They think they have M BL and brick their phones
If any help...
IFWI versions on 551 or Z00A
0094.0177 is locked LP bootloader
0094.0173 is unlocked.
0094.0183 is M BL
If your tool kit could detect these , it could flash back original stock recoveries and help many unaware people restore and upgrade stock LP to M
Then they could again use your tool to unlock once upgraded to stock M.
Where they then could make back ups of stock again before flashing custom ROMs
@fred_gaou
You gave some nice questions&suggestions!
About your questions:
You don't need the batch to run as admin as I don't use any function that needs admin rights.
Yes, I've tested all root functions and switched between single supersu, magisk with phh and magisk with supersu, but of course always with running the unroot task first. my personal favorite is magisk with phh b/c of the magisk hide. that's what i need for some banking apps :angel:
Not yet. I don't think i'm going to try that soon as I want to stay at stock rom atm. If you have any idea to implement that to this toolkit, i would be pleased to know.
The idea of the auto packages is to combine some single actions like unroot & root. So there is actually just one package, which I used the most time to get back to my favorite root solution.
The other points:
Giving more guidelines/hints in this thread&toolkit is a good point. I'll try to add this as soon as possible. :good:
Putting factory reset & backup on my todo list :good: Are there any installation procedure for roms that recommend to erase /system first? I've done that by mistake a few months ago and started to sweat. As this is a very dangerous command, I would only implement this if there is a need.
I know about the newer 1.0.36 version. That was the reason for the action "force internal platform toolkit" in the troubleshoot menu. But I had a LOT of problems running the new version on 2 different machines. The daemon didn't start with an error telling that the adb.log couldn't be opened. I'll put it on my todo list too, but with low priority.
timbernot said:
What would be ideal , if possible to add
Is ..
An ifwi version detector
Because , there are a lot of people who flashed their phones who haven't a clue they have M version with LP bootloader.
They think they have M BL and brick their phones
If any help...
IFWI versions on 551 or Z00A
0094.0177 is locked LP bootloader
0094.0173 is unlocked.
0094.0183 is M BL
If your tool kit could detect these , it could flash back original stock recoveries and help many unaware people restore and upgrade stock LP to M
Then they could again use your tool to unlock once upgraded to stock M.
Where they then could make back ups of stock again before flashing custom ROMs
Click to expand...
Click to collapse
Haven't thought about that scenario. Can you give me some more details? Users with bricked phones can only boot fastboot and nothing else?
I currently don't know a method to detect the ifwi version in fastboot state, so i would probably need twrp or a running system (almost certainly with root permission) to get ifwi information.
Hi,
I just want to verify. I have the ASUS Zenfone 2 Deluxe Special Edition that I have upgraded from the stock 5.0.0 Android Lollipop (I forgot the ASUS Firmware version number) to the the Official ASUS 6.0.1 Marshmallow (Version WW-4.21.40.223(andriod M)) I can use this?
I regret upgrading from the Official LP to the Official MM with all the bloatwares. I am looking for a way to get root just like with my Sony Xperia phones but I am learning that getting root on ASUS Zenfones on MM is difficult. Almost all solutions I am reading is advising to downgrade from MM to LP, root, then manually upgrade to MM
rummsbumms said:
Not yet. I don't think i'm going to try that soon as I want to stay at stock rom atm. If you have any idea to implement that to this toolkit, i would be pleased to know.
Click to expand...
Click to collapse
Well, I'm still on stock LP so I would not be a good adviser. I trust the experienced users that switch and update ROM weekly so they will give useful feedback soon. Since some guys on LineageOS used Giovix modder to unlock bootloader and install ROM via TWRP, I guess it's currently the way to go.
rummsbumms said:
The idea of the auto packages is to combine some single actions like unroot & root. So there is actually just one package, which I used the most time to get back to my favorite root solution.
Click to expand...
Click to collapse
I get it now. It could be a useful section in future to run sequential commands at once.
rummsbumms said:
Putting factory reset & backup on my todo list :good: Are there any installation procedure for roms that recommend to erase /system first? I've done that by mistake a few months ago and started to sweat. As this is a very dangerous command, I would only implement this if there is a need.
Click to expand...
Click to collapse
Yes it is wise. I just provided the command because it was implemented in Giovix Modder and often reported as a way to clean up before flash all stock in other device. Don't know for 551.
rummsbumms said:
I know about the newer 1.0.36 version. That was the reason for the action "force internal platform toolkit" in the troubleshoot menu. But I had a LOT of problems running the new version on 2 different machines. The daemon didn't start with an error telling that the adb.log couldn't be opened. I'll put it on my todo list too, but with low priority.
Click to expand...
Click to collapse
Detail is good to know. What OS do you use: 7, 8.1 or 10? If 1.0.32 works fine on every version, there is no point to risk to break anything using 1.0.36.
Thanks for your answers.
rummsbumms said:
Haven't thought about that scenario. Can you give me some more details? Users with bricked phones can only boot fastboot and nothing else?
I currently don't know a method to detect the ifwi version in fastboot state, so i would probably need twrp or a running system (almost certainly with root permission) to get ifwi information.
Click to expand...
Click to collapse
Thinking about it now a bit more , it maybe tail end for this problem .
The actual problem people were having was they thought they had cm13 with M BL , actually they had the LP bootloader cm13 . They would be in a working system then flash 14.1 / 7.1 builds then , brick their devices .
They forget they never upgraded bootloader and with having 6.0.1 M in build information in settings, presumed they had upgraded bootloader at some point but didn't .
Maybe , to prevent the tail enders from performing such tasks again , maybe a simple addition like a warning , like build date which in cm 13 , to check.. if before July 2016 and have IFWI version 0094.0173 unlocked . Then you could direct them to say a return to stock option , flashing back boot and recovery for say on 551 LP 2 20 40 .196 Version , then possibly install the full ROM from say a link or something like ...Then info to upgrade to stock M before returning back to tool to unlock updated to the latest M.
But like mentioned , we maybe at the tail end of this problem.
Probably related to 95% of the bricking threads here for zenfone.
Anyway thanks for taking interest
Deathschythe33 said:
Hi,
I just want to verify. I have the ASUS Zenfone 2 Deluxe Special Edition that I have upgraded from the stock 5.0.0 Android Lollipop (I forgot the ASUS Firmware version number) to the the Official ASUS 6.0.1 Marshmallow (Version WW-4.21.40.223(andriod M)) I can use this?
I regret upgrading from the Official LP to the Official MM with all the bloatwares. I am looking for a way to get root just like with my Sony Xperia phones but I am learning that getting root on ASUS Zenfones on MM is difficult. Almost all solutions I am reading is advising to downgrade from MM to LP, root, then manually upgrade to MM
Click to expand...
Click to collapse
As far as i can see from the asus page, the zf2 deluxe special edition uses the same firmware files and you already have the newest firmware (.223) installed, so i think it should work.
Is your bootloader still locked?
Thank you so much for your awesome ToolKit, works flawlessly !!
<3
v0.5 is out
rummsbumms said:
v0.5 is out
Click to expand...
Click to collapse
thanks, can you simply make 3 downloads complete for the 3 mm versions? now is a bit confusing with this updating/base files.
I don't think that 80mb would be a problem to download, everyone have at least a dsl line, we are not talking of gbs, thanks
v0.7 is out
@fred_gaou: I've tested with win10. 1.0.3.2 works fine and will be default, but I've added 1.0.3.6 too. perhaps someone could test on other machines as i still have problems using it and don't know whats the problem.
@holymoz: I've made a additional "full" package which contains all files. the "base" version still only contains the latest mm firmware files.
@timbernot: Still thinking about it. Maybe some kind of decision tree asking for the problem could lead the user to an action that could cure the problem. I'll keep it on my todo list.
V0.5 works okay on my device with win 10 . i will test later the new build thanks
rummsbumms said:
As far as i can see from the asus page, the zf2 deluxe special edition uses the same firmware files and you already have the newest firmware (.223) installed, so i think it should work.
Is your bootloader still locked?
Click to expand...
Click to collapse
Hello @rummsbumms,
Thank you for taking your time to respond. Yup, my phone's bootloader is still locked. Everything in this phone is "official" including the freaking official bloatwares. I love the HW specs of this phone, but the bloatwares are F***ing crazy!
I ran some troubles whilst was turning my android version 4.4.4 into a 8.1, TWRP helped me with the whole process (if it wasn't by those guys i'd have a bricked phone for sure). While fixing things and figuring out all the misstepped nuances on my end it come to my understandment that TWRP 2.7.1, while funcional, was flawed; since the newer versions could get rid of the necessity of dealing with adb and some weird glitches that not even 5.53785% of the internet community has dealt (or at least expressed) in the past. Errors like "broken pipes" or closed doors on a DMZ connection were spreading the adb sideload route that i had avaliable. For that reason i decided to upgrade TWRP, followed these instructions to the heart paying attention to the warning that 2.8.4 version would be needed if i want a recover-mode route for said upgrade, which made me go for the googleplay manner. My mistake was not backuping the image of the working 2.7.1 version which was in place, i've neglected such feature and gone straight to the 'download and flash' an image, which i opted for getting the 2.8.4 planning on upgrading the remanescent versions directly on recovery-mode. I never came to celebrate such accomplishment since the change of 2.7.1 to 2.8.4 via rooted TWRP app made my recovery-mode to BSoD. Ever since i've tried downgrading to 2.7.1 again to see if would at least return to the old point but i ran outta luck here. Whats the best course of action to take right now? Straight up overwrite it using this. Delete and reinstall?
TLDR::: had TWRP 2.7.1, without making backup of the working stance, installed 2.8.4 image via googleplay official app (rooted), got as result? a bricked, black recover-mode screen. Atempted to reroll to 2.7.1 by downloading it on said app, didn't worked, BSoD stay still when recovery-mode is choosen. What to do to get, if not the newest version of TWRP, at least the 2.7.1 back?
First, flash the latest stock OS (Android 5.1.1), then flash the latest TWRP (twrp-3.2.1-0-mako.img) and proceed with flashing selected rom from there.
Edit: don't use some 3rd party flashing tools, they tend to be broken and/or oudated.
n0b0dy666 said:
First, flash the latest stock OS (Android 5.1.1), then flash the latest TWRP (twrp-3.2.1-0-mako.img) and proceed with flashing selected rom from there.
Edit: don't use some 3rd party flashing tools, they tend to be broken and/or oudated.
Click to expand...
Click to collapse
Thing is: i'm now using nitrogen 8.1 Oreo, which i manage to flash via a working 2.7.1 TWRP plus the flashing tool that i've used was the one provided and advised by TWRP team themselves, the one official on googleplay. I'm up to downgrade android 8.1 to 5.1.1 but how to do it? (considering that i can't access the recovery-mode)
EDIT: perhaps you're saying for me NOT to use something like this?
I always use Skipsoft android toolkit to flash stock/custom roms.
https://forum.xda-developers.com/ne...olkit-skipsoft-android-toolkit-nexus-t1995688
This thread is over :victory:
This problem is now solved. Thank you both for taking time to express some light on my troubles, thanks for answering my plea.
HOWTO: Talking with a correspondent of official TWRP i was advised to download and flash on the official app (googleplay app, just as before) the previous version version 2.7.0 (considering my last working version was 2.7.1) to see the results. It managed to get me back a working recovery-mode screen and from there, i made the needed IMG backup and recovery backup before following the next step: downloading 3.2.1 straight from 2.7.0 (bold, if you'd ask me, but since i got 2.7.0img backup saved this time, i feared no trouble :highfive and IT WORKED!
Hi! I'm on NPJS25.93-14.7-3 (December 2017 security update). My phone is Moto G4 Plus XT1644 and I'm rooted with Magisk.
I want to install the new OTA update (NPJS25.93-14.7-5), but since I'm rooted I need a stock NPJS25.93-14.7-3 so I can restore the recovery. I have been searching for weeks but I can't seem to find this version.
Anyone know where I can find it?
Thanks.
As far as I know, there is currently no NPJ25.93-14.7-3 or NPJ25.93-14.7-5 firmware uploaded to either firmware.center or the Motorola Firmware Team Android FileHost page.
There is a way to revert back to the stock ROM (credit to Danny1976 and pastorbob62 https://forum.xda-developers.com/showpost.php?p=76081679&postcount=110 ), though you will have to flash the NPJ25.93-14.7 stock ROM (Sept 2017 security patch). Though normally downgrading isn't a good idea, in this case you're only downgrading to the directly preceding firmware and then the OTA should bring you back up to NPJ25.93-14.7-3, after which you could flash the OTA update to the Feb 2018 security patch.
So the general procedure is:
1)Back up your device (make a TWRP backup and keep it safe).
2)Download the NPJ25.93-14.7 stock ROM (retail US: https://androidfilehost.com/?fid=817906626617945295 or Amazon software channel: https://androidfilehost.com/?fid=817906626617956922 )
3)Flash as per the above linked XDA post. You may wish to ignore security downgrade errors with GPT/bootloader as the next OTA update should flash the same bootloader as you currently have. These set of flashing commands should not affect your data but nonetheless, at least you have a backup.
4)Reboot and update to NPJ25.93-14.7-3
5)Reboot and update to NPJ25.93-14.7-5
Then you should be up to date. I do not know if this procedure will work for the next OTA update , so perhaps best to boot TWRP, do not swipe to allow modification in TWRP and take a backup of your NPJ25.93-14.7-5 installation. This should be okay to revert back to if there is no firmware still available.
You may wish to read the posts from this page and the subsequent pages for more information: https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page12
echo92 said:
As far as I know, there is currently no NPJ25.93-14.7-3 or NPJ25.93-14.7-5 firmware uploaded to either firmware.center or the Motorola Firmware Team Android FileHost page.
There is a way to revert back to the stock ROM (credit to Danny1976 and pastorbob62 https://forum.xda-developers.com/showpost.php?p=76081679&postcount=110 ), though you will have to flash the NPJ25.93-14.7 stock ROM (Sept 2017 security patch). Though normally downgrading isn't a good idea, in this case you're only downgrading to the directly preceding firmware and then the OTA should bring you back up to NPJ25.93-14.7-3, after which you could flash the OTA update to the Feb 2018 security patch.
So the general procedure is:
1)Back up your device (make a TWRP backup and keep it safe).
2)Download the NPJ25.93-14.7 stock ROM (retail US: https://androidfilehost.com/?fid=817906626617945295 or Amazon software channel: https://androidfilehost.com/?fid=817906626617956922 )
3)Flash as per the above linked XDA post. You may wish to ignore security downgrade errors with GPT/bootloader as the next OTA update should flash the same bootloader as you currently have. These set of flashing commands should not affect your data but nonetheless, at least you have a backup.
4)Reboot and update to NPJ25.93-14.7-3
5)Reboot and update to NPJ25.93-14.7-5
Then you should be up to date. I do not know if this procedure will work for the next OTA update , so perhaps best to boot TWRP, do not swipe to allow modification in TWRP and take a backup of your NPJ25.93-14.7-5 installation. This should be okay to revert back to if there is no firmware still available.
You may wish to read the posts from this page and the subsequent pages for more information: https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page12
Click to expand...
Click to collapse
I will look in to this in more detail. Thank you very much!
This worked like a charm! I followed the steps and now I'm on NPJS25.93-14.7-5.
I read somewhere that this version fixes the screen ghosting effect, but sadly not for me, so I had to root again and correct the RGB values.
Thanks!
juanml said:
This worked like a charm! I followed the steps and now I'm on NPJS25.93-14.7-5.
I read somewhere that this version fixes the screen ghosting effect, but sadly not for me, so I had to root again and correct the RGB values.
Thanks!
Click to expand...
Click to collapse
Yeah, it seems that if you are one of the unfortunate who has the ghost touch issue it isn't fixed by this version. I am on 14.7-5 and I don't have that problem at all, which leads me to believe it is a hardware issue. Doesn't explain why some versions don't have it though.
Hi! Anyone know if this method still works for updating to NPJS25.93-14.7-8?
Since for quiet some time I've tried several methods described here in the forums and elsewhere, I though it is worthwhile to log the one that really worked:
First of all you need to follow the installation instructions.
Second, I'd recommend to refrain from all the Windows-based tools or most of the Android apps (for the exception used here see below). You should also be aware that it is not necessary to flash a new KDZ as several people are suggesting here in the forums, nor is it necessary to update the firmware on your stock device upfront.
Third, it's always a good idea to backup the device (in case something goes wrong) and foremost your data (to be reused on the updated device, since the update will destroy all your data).
You'll need to perform the following steps:
A fix for the radio/modem can be obtained on XDA. I used version 21C which is the latest version that works from Android 5.X upwards.
Install/flash TWRP using Autorec from @bender_007. I recommend to follow this instruction. All other variants/suggestions did not work for me.
Copy the necessary files to your device using adb (radio fix, latest LineageOS, GApps nano in my case)
First install RADIO_D855_21C... then follow the steps starting at "Installing LineageOS from recovery" in the official installation instructions.
Hope this helps -mgw