Hellow My Friends...
I Create Boot.img File for Root All Xperia M4 Aqua Variants in Unlock Bootloader And 26.3.A.1.33 Firmware, Hope Work for you
I And My Friend Test All of Boot.img in All Variants
Code:
* 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 make nandroid backup before flashing this as a preaution!
Do Steps Like Under:
1- Download Your Boot.img variant And TWRP
E2303:
http://www.mediafire.com/file/y6pagtazu5mqnc4/boot+E2303.rar
E2306:
https://drive.google.com/file/d/0By8Royf_hNU8Z29oUUNVeDgzTGc/view?usp=drivesdk
E2312:
https://www.mediafire.com/?3who10e6a0lxwct
E2333:
https://www.mediafire.com/?ltpscpy3dpy6m7n
E2353:
https://drive.google.com/file/d/0B9PdiUEYtxNkdTZEaF9GT082REU/view
TWRP:
https://drive.google.com/file/d/0Bwfkh9Wew36kem9wdDQ1enJkUmc
** E2363 Users can use E2333 variant Boot.img **
2- Copy Boot.img And TWRP 3.0.2-0 in C:/adb Drive
3- Plug your device to PC in fastboot Mode
4- type cmd in C:/adb Folder AdressBar
5- Type in adb For Flash Boot.img:
fastboot flash boot boot.img
And For TWRP:
fastboot flash recovery recovery.img
6- Unplug your phone and restart it
Credits : @dani020110 For TWRP recovery
** Prees Thanks if i helped you **
Root works fine
Super all works fine with root and SuperSU App!
But you have an idea why the mobile network not work? Is it possible the reason is the boot.img, or a fault with the Provider?
Floh1990 said:
Super all works fine with root and SuperSU App!
But you have an idea why the mobile network not work? Is it possible the reason is the boot.img, or a fault with the Provider?
Click to expand...
Click to collapse
Whats your variant and your rom? if you install true Boot.img its impossible.
After a provider sms to config the Internet and mms it works! But not by itself, I had to request it manually.
The phone variant is E2303 with Android 6.
Floh1990 said:
After a provider sms to config the Internet and mms it works! But not by itself, I had to request it manually.
The phone variant is E2303 with Android 6.
Click to expand...
Click to collapse
Okay bro but its not for Boot.img, its work great My friends test all of them
Locked Bootloader
EHSAN™ said:
Okay bro but its not for Boot.img, its work great My friends test all of them
Click to expand...
Click to collapse
Does this work with locked bootloader devices?
kgalv419 said:
Does this work with locked bootloader devices?
Click to expand...
Click to collapse
No, adb Need Unlock Bootloader.
EHSAN™ said:
No, adb Need Unlock Bootloader.
Click to expand...
Click to collapse
Oh I see, ok thanks so much, guess everyone with locked bootloaders will have to wait probably months before we get root on marshmallow.
I cannot unlock bootloader on e2363 Build No.- 26.3.B.1.33. Please help. I used latest flashtool. I am quite a noob at rooting I checked from service menu. I have permission to unlock bootloader. But flashtool says "root access denied" and "you do not have permission to unlock bootloader officially". Please help! :crying:
prathamesh95 said:
I cannot unlock bootloader on e2363 Build No.- 26.3.B.1.33. Please help. I used latest flashtool. I am quite a noob at rooting I checked from service menu. I have permission to unlock bootloader. But flashtool says "root access denied" and "you do not have permission to unlock bootloader officially". Please help! :crying:
Click to expand...
Click to collapse
Same problem with e2303
Hello,
About unlocking bootloader issues:
1) Unplug USB cable if plugged.
2) Start your phone in "normal" mode (no adb, no fastboot).
3) Check "Enable OEM unlock" AND "Enable USB debugging" under the "Developer Options" menu (press 5 times the "About phone" settings menu to make the hidden "Developer Options" menu appear if needed).
See attachements (it's in french sorry)
4) Plug the USB cable and accept the security key on the phone (check the checkbox "Always accept" - or similar).
5) Power off your phone and restart in fastboot.
6) Ensure your device is detected by your computer (command should be something like "fastboot devices" - check the fastboot help for exact syntax).
7) Proceed to the unlocking by launching the command with your unlock key.
Note: if this procedure fails, unplug your phone, ensure there is no adb running processes and kill them if there are.
Then restart at step 5.
Regards
it says ''cannot load recover.img
russelpena06 said:
it says ''cannot load recover.img
Click to expand...
Click to collapse
Insert Name of Recovery Carefully.
how to update to SuperSu 2.79 ?
fadyzico said:
how to update to SuperSu 2.79 ?
Click to expand...
Click to collapse
Do not Update, Because Lose SU Binary And Root. Use This Version 2.79 Not Diffrent With 2.78
EHSAN™ said:
Do not Update, Because Lose SU Binary And Root. Use This Version 2.79 Not Diffrent With 2.78
Click to expand...
Click to collapse
hi. i have this problem. i updated supersu from playstore, and now it wants to update binary but it wont succeed. 2303 still is rooted (rootcheck su v.2.77). have tried to fastboot boot and recovery and it says done but nothing changed. what should i do now
msa78 said:
hi. i have this problem. i updated supersu from playstore, and now it wants to update binary but it wont succeed. 2303 still is rooted (rootcheck su v.2.77). have tried to fastboot boot and recovery and it says done but nothing changed. what should i do now
Click to expand...
Click to collapse
You Must Be Flash System And Kernel With Flashtools And Do Root Steps Again.
This phone was worst buy, has only like 1gb free storage for apps, cannot be rooted correctly, cannot use sdcard as adoptive storage, cannot install custom rom . worst buy .
will this work for 26.3.B.1.33 ?!
ahmedelwakil07 said:
will this work for 26.3.B.1.33 ?!
Click to expand...
Click to collapse
This is only for 33 build
Related
Hi someone can give MI guide to root my xperia z5c android 5.1.1 E5823 firmware 32.0.a.6.200 please? Tank to the helpers
N22121991 said:
Hi someone can give MI guide to root my xperia z5c android 5.1.1 E5823 firmware 32.0.a.6.200 please? Tank to the helpers
Click to expand...
Click to collapse
Enable developer options first in your phone, followed to enable OEM unlock and enable USB debugging.
Search on google there is a Sony official site to let you input your IMEI and get the unlock key. You'll need to use fastboot(search on google if you don't know what is it) to unlock via command prompt in Windows, a factory reset will perform after unlocked.
Kernel: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
Recovery: http://forum.xda-developers.com/z5-compact/orig-development/twrp-z5-compact-t3235161 (you only need the recovery.img from it)
And then, you just need to "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" in command prompt to flash custom kernel and custom recovery.
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
At last, "fastboot boot recovery.img" to flash the flashablesu.zip in recovery and install any of busybox utility via Playstore. Upgrade to camera 2.0 via "What's new" if you will install xposed bcoz stock cam 1.0 will FC.
Pretty much that's all of it.
hello
Thanks
Does it work with encrypted device ?
Bear in mind that if you unlock bootloader, your camera will worsen, you will lose image enhancements like x reality and your warranty will be void. Etc. Etc. So you might want to hold off on root. Just letting you know, that is
Sadman Khan said:
Bear in mind that if you unlock bootloader, your camera will worsen, you will lose image enhancements like x reality and your warranty will be void. Etc. Etc. So you might want to hold off on root. Just letting you know, that is
Click to expand...
Click to collapse
i don't totally agree because what i did,well,unlock device's bootloader & everything blah blah blah..but camera seems to be just fine.but of course,you'd definitely can see the difference..now since drm restore for our devices is already available however,it indeed restored the functions and the bravia engine & all(except the drm key itself),i noticed that my rooting status has changed from "unlock bootloader allowed: yes" to unlock bootloader allowed: no"!also,even if says so,my phone still has twrp installed,rooted & a custom kernel..all seems to be working as i so far observed..just that rooting status thing changed..kinda wierd,though!
Arturiuz! said:
i don't totally agree because what i did,well,unlock device's bootloader & everything blah blah blah..but camera seems to be just fine.but of course,you'd definitely can see the difference..now since drm restore for our devices is already available however,it indeed restored the functions and the bravia engine & all(except the drm key itself),i noticed that my rooting status has changed from "unlock bootloader allowed: yes" to unlock bootloader allowed: no"!also,even if says so,my phone still has twrp installed,rooted & a custom kernel..all seems to be working as i so far observed..just that rooting status thing changed..kinda wierd,though!
Click to expand...
Click to collapse
Mine says the same "unlock bootloader allowed: no" but root and everything works fine, and the camera definitely improved although its still crap in my opinion. Have a couple of before and after shots if someone is interested.
Radeon1337 said:
Mine says the same "unlock bootloader allowed: no" but root and everything works fine, and the camera definitely improved although its still crap in my opinion. Have a couple of before and after shots if someone is interested.
Click to expand...
Click to collapse
wait!let me correct myself a little(this is really weird!)..my drm keys are restored,to wc as far as i am knowledgable of,that shouldnt be the case after unlocking the BL..
*apologies here!im still trying to figure out how to insert a screenshot as a proof!i'm just using my phone atm..peace!
Arturiuz! said:
wait!let me correct myself a little(this is really weird!)..my drm keys are restored,to wc as far as i am knowledgable of,that shouldnt be the case after unlocking the BL..
*apologies here!im still trying to figure out how to insert a screenshot as a proof!i'm just using my phone atm..peace!
Click to expand...
Click to collapse
got it!here's for the screenshot before i unlocked my device..then drm keys lost..then when flashed the drmrestore.zip,consecutively..
MystereT said:
hello
Thanks
Does it work with encrypted device ?
Click to expand...
Click to collapse
Did you ever take the plunge with encryption? TWRP supposedly supports encryption, but want to make sure I have a way to a working phone if encryption doesn't work.
Don't remember if I can undo encryption via twrp, or at that point is it just prudent to flashtool it back to a clean image if not? My understanding is really just need to get a kernel on there that will boot, and provide the rest of the system with or without encryption.
Ready to pull the trigger on this to root and try with my encryption, but think I'll pull down a clean version of .200 firmware for the z5c first...
Yesterday there is a way to get Z5/Z5C/Z5P Rec & Root
and revive DRM & BE2 & Camera noise reduction by one-click (need unlocked BL),
I'm afraid to try...
Works like a charm
I can confirm drm-restore patch works like a charm and everything (camera noise reduction etc.)
iMaeGoo said:
Yesterday there is a way to get Z5/Z5C/Z5P Rec & Root
and revive DRM & BE2 & Camera noise reduction by one-click (need unlocked BL),
I'm afraid to try...
Click to expand...
Click to collapse
TheEndHK said:
Enable developer options first in your phone, followed to enable OEM unlock and enable USB debugging.
Search on google there is a Sony official site to let you input your IMEI and get the unlock key. You'll need to use fastboot(search on google if you don't know what is it) to unlock via command prompt in Windows, a factory reset will perform after unlocked.
Kernel: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
Recovery: http://forum.xda-developers.com/z5-compact/orig-development/twrp-z5-compact-t3235161 (you only need the recovery.img from it)
And then, you just need to "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" in command prompt to flash custom kernel and custom recovery.
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
At last, "fastboot boot recovery.img" to flash the flashablesu.zip in recovery and install any of busybox utility via Playstore. Upgrade to camera 2.0 via "What's new" if you will install xposed bcoz stock cam 1.0 will FC.
Pretty much that's all of it.
Click to expand...
Click to collapse
hi Bro! is there any trouble if i flash (obviously via fastboot) only the recovery over the stock kernel firmware .200?? or is mandatory flash kernel and recovery?
thanks!
acabreram said:
hi Bro! is there any trouble if i flash (obviously via fastboot) only the recovery over the stock kernel firmware .200?? or is mandatory flash kernel and recovery?
thanks!
Click to expand...
Click to collapse
Stock kernel will get a bootloop if you rooted. The current build of Z5c kernel got dm-verity, when it detect your /system has changed like flashed flashablesu.zip to attempt to root probably it will not boot. You need a custom insecure kernel to root.
TheEndHK said:
Stock kernel will get a bootloop if you rooted. The current build of Z5c kernel got dm-verity, when it detect your /system has changed like flashed flashablesu.zip to attempt to root probably it will not boot. You need a custom insecure kernel to root.
Click to expand...
Click to collapse
ok Bro thanks!! there is not custom kernel of firmware .200 yet right?
acabreram said:
ok Bro thanks!! there is not custom kernel of firmware .200 yet right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=64849573&postcount=2
plz read it clearly
can someone share stock E5823 fw .200 kernel, I need it to test this method
Help
TheEndHK said:
Enable developer options first in your phone, followed to enable OEM unlock and enable USB debugging.
Search on google there is a Sony official site to let you input your IMEI and get the unlock key. You'll need to use fastboot(search on google if you don't know what is it) to unlock via command prompt in Windows, a factory reset will perform after unlocked.
Kernel: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
Recovery: http://forum.xda-developers.com/z5-compact/orig-development/twrp-z5-compact-t3235161 (you only need the recovery.img from it)
And then, you just need to "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" in command prompt to flash custom kernel and custom recovery.
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
At last, "fastboot boot recovery.img" to flash the flashablesu.zip in recovery and install any of busybox utility via Playstore. Upgrade to camera 2.0 via "What's new" if you will install xposed bcoz stock cam 1.0 will FC.
Pretty much that's all of it.
Click to expand...
Click to collapse
Hello, tks by the step by step u did... Sorry by my poor english, i am braziliam and need little help here.
1 - My z5c already is unlocked;
2 - I download the zombie kernel like u said (ok, get the boot.img file);
3 - I try to download the recovery, but when open the 7zip on windows cannot unzip the recovery.img file;
4 - Try to download this one (TWRP for Z5C) and ok, i get the recovery.img file from this (this is the same recovery file ???).
So the questoin is:
I can flash this files above (boot and recovery) on my z5c - E5823 - 32.0.A.6.200 ????
And why not flash the boot.img from the recovery zip file ??? Whats the diference ???
Regards and tks again !!!
puiatmp said:
Hello, tks by the step by step u did... Sorry by my poor english, i am braziliam and need little help here.
1 - My z5c already is unlocked;
2 - I download the zombie kernel like u said (ok, get the boot.img file);
3 - I try to download the recovery, but when open the 7zip on windows cannot unzip the recovery.img file;
4 - Try to download this one (TWRP for Z5C) and ok, i get the recovery.img file from this (this is the same recovery file ???).
So the questoin is:
I can flash this files above (boot and recovery) on my z5c - E5823 - 32.0.A.6.200 ????
And why not flash the boot.img from the recovery zip file ??? Whats the diference ???
Regards and tks again !!!
Click to expand...
Click to collapse
because it's only meant to be flashed in/by fastboot mode through command prompt or cmd.flashing it using recovery won't install those img's..not unless those were re/packed that could also be flashed through recovery..i've tried it but gave me error. & it's better that way installing it through command prompt/fastboot mode.
Arturiuz! said:
because it's only meant to be flashed in/by fastboot mode through command prompt or cmd.flashing it using recovery won't install those img's..not unless those were re/packed that could also be flashed through recovery..i've tried it but gave me error. & it's better that way installing it through command prompt/fastboot mode.
Click to expand...
Click to collapse
hey friend, tks for response.
I know we need to use fastboot to flash this files and i know how to do this.
I only wanna know if the files are compatible with my model and version device.
puiatmp said:
hey friend, tks for response.
I know we need to use fastboot to flash this files and i know how to do this.
I only wanna know if the files are compatible with my model and version device.
Click to expand...
Click to collapse
yes! it's(actually)for E5823 devices to be specific & as per OP(even as i have checked the links)..it even worked on mine wc is E5803! might want try it out first & see for yourself!
So the OFFICIAL 6.0.1 is already out and this is not the BETA version. It's for consumer release.
So how do you get to this eh?
NOTES: Flashtool can be used for both LB/UB. You won't lose DRM keys or unlock bootloader if you flash via flashtool.
1. Install Flashtool (get it here: http://www.flashtool.net/downloads.php).
2. There is a XperiFirm option there which would allow you to download official FTF files.
3. Navigate your way to Z3 Compact and grab the D5803 version US Variant (since this is configured for GLOBAL-LTE but i might still need to test bands). Or just grab anything you want there as long as it's version: 23.5.A.0.570
3. Flash using flashmode (hit the lightning icon there).
Now there's this "WIPE" Box, you have 2 options!
- Check User data and App logs and hit flash -- this will factory reset phone so you better have a backup!
- Leave them UNCHECKED if you want to retain your apps from your previous STOCK ROM. (might automatically uninstall incompatible apps in the process).
Once it asks for your device to be connected. Do as it says (power down, then hold the vol. down button as you plug the phone in).
-- this should start flashing.
4. After the process you may now boot the phone and there you have it!
-- Things below require unlocked BL --
If you want root, you can use fastboot and TWRP 3.X (I've tested the TWRP version 3.0.2 on the 6.0.1 beta before)
send this command on fastboot:
Code:
fastboot flash recovery <your twrp img here>
and hit enter. It must return 'OKAY'.
Unplug phone then boot into recovery and flash your SuperSU.zip
https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
MINE!
Give a link to proper TWRP image please
tRippinthehead said:
Give a link to proper TWRP image please
Click to expand...
Click to collapse
If you have a locked BL, then root and install DualRecovery. There is an excellent thread here on XDA and you'll be on TWRP in no time. It also makes sure you'll have the drivers and flash tool and everything that you'll need for this already configured and ready to go.
If you have an unlocked BL, just go find TWRP and flash through fastboot.
Thanks OP!
P.S. I'm guessing for those with locked BLs, we can use PRFCreator and that FTF from Xperifirm to create a flashable, pre-rooted MM ROM...anyone tried? My Z3c is currently bricked (hopefully fixable) so I can't test at the moment.
Another DEV published a root method, both for the LB and UB:
http://forum.xda-developers.com/z3/general/wip-sony-android-6-0-mm-t3337357/page1
Keep in mind that that method was used for the BETA version of the rom, but yeah it's more likely that it would work with the consumer release. I'll update the OP once I relock my BL and successfully gain root with it.
The UB method there has the same effect as mine
I could not get root with the method, i would get boot img failure on flashing superSU in twrp with unlocked BL but to solve the issue i just flashed the advanced kernel for 6.0.1 and superSU flashed fine..not sure if anyone else is having this problem but this method did not work for me.
Do I keep root with locked bootloader with this method ?
Title of this topic is confusing, it seems that you need BL unlocked to get root.
hayatesan said:
Do I keep root with locked bootloader with this method ?
Title of this topic is confusing, it seems that you need BL unlocked to get root.
Click to expand...
Click to collapse
No you will lose root if you flash ftf on locked BL, you will need to root again using whichever method you used previously. If you flash an ftf file on ANY bootloader locked or unlocked it resets your phone to the contents of the ftf file.
Fictional Reality said:
No you will lose root if you flash ftf on locked BL, you will need to root again using whichever method you used previously. If you flash an ftf file on ANY bootloader locked or unlocked it resets your phone to the contents of the ftf file.
Click to expand...
Click to collapse
And which is the method to root this version with BL??
hv6478 said:
P.S. I'm guessing for those with locked BLs, we can use PRFCreator and that FTF from Xperifirm to create a flashable, pre-rooted MM ROM...anyone tried? My Z3c is currently bricked (hopefully fixable) so I can't test at the moment.
Click to expand...
Click to collapse
I'm giving it a try so I'll let you know.
EDIT: Admittedly I haven't got a clue how to use prfcreator but I tried and whilst it flashed there was no root or recovery.
2nd EDIT: XDR doesn't work on MM yet. I'll give TWRP a try.
TWRP 3.0.2 for Z3C https://dl.twrp.me/z3c/twrp-3.0.2-0-z3c.img.html
Buleste said:
I'm giving it a try so I'll let you know.
EDIT: Admittedly I haven't got a clue how to use prfcreator but I tried and whilst it flashed there was no root or recovery.
2nd EDIT: XDR doesn't work on MM yet. I'll give TWRP a try.
TWRP 3.0.2 for Z3C https://dl.twrp.me/z3c/twrp-3.0.2-0-z3c.img.html
Click to expand...
Click to collapse
Nice that sounds promising, at least it worked with the .zip that you created!
Which version of SuperSU are you using?
Thanks,
hv
hv6478 said:
Nice that sounds promising, at least it worked with the .zip that you created!
Which version of SuperSU are you using?
Thanks,
hv
Click to expand...
Click to collapse
I'm using BETA-SuperSU-v2.71-20160331103524.zip
However I was looking at the PRFCreator thread and it looks like if you add Recroot v2 as the SuperSU it should work. Not sure if it will give a recovery though.
EDIT: Okay. Didn't install the SuperSU binary properly but Kingroot could install the root though. Tried to remove it and replace with SuperSU and got a bootloop. However I have a cunning plan.
Xperia Z3 Compact - UB
I could not get TWRP recovery with the fastboot method.
I tried to install several "recoverys" but none are installed.
Help me please.
Buleste said:
I'm using BETA-SuperSU-v2.71-20160331103524.zip
However I was looking at the PRFCreator thread and it looks like if you add Recroot v2 as the SuperSU it should work. Not sure if it will give a recovery though.
EDIT: Okay. Didn't install the SuperSU binary properly but Kingroot could install the root though. Tried to remove it and replace with SuperSU and got a bootloop. However I have a cunning plan.
Click to expand...
Click to collapse
I love the sound of progress!
rvnlvrz said:
So the OFFICIAL 6.0.1 is already out and this is not the BETA version. It's for consumer release.
So how do you get to this eh?
NOTES: Flashtool can be used for both LB/UB. You won't lose DRM keys or unlock bootloader if you flash via flashtool.
1. Install Flashtool (get it here: http://www.flashtool.net/downloads.php).
2. There is a XperiFirm option there which would allow you to download official FTF files.
3. Navigate your way to Z3 Compact and grab the D5803 version US Variant (since this is configured for GLOBAL-LTE but i might still need to test bands). Or just grab anything you want there as long as it's version: 23.5.A.0.570
3. Flash using flashmode (hit the lightning icon there).
Now there's this "WIPE" Box, you have 2 options!
- Check User data and App logs and hit flash -- this will factory reset phone so you better have a backup!
- Leave them UNCHECKED if you want to retain your apps from your previous STOCK ROM. (might automatically uninstall incompatible apps in the process).
Once it asks for your device to be connected. Do as it says (power down, then hold the vol. down button as you plug the phone in).
-- this should start flashing.
4. After the process you may now boot the phone and there you have it!
-- Things below require unlocked BL --
If you want root, you can use fastboot and TWRP 3.X (I've tested the TWRP version 3.0.2 on the 6.0.1 beta before)
send this command on fastboot:
Code:
fastboot flash recovery <your twrp img here>
and hit enter. It must return 'OKAY'.
Unplug phone then boot into recovery and flash your SuperSU.zip
https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
Click to expand...
Click to collapse
It doesn't work, I have trying out for a while, but fastboot doesn't flash anything
hv6478 said:
I love the sound of progress!
Click to expand...
Click to collapse
We have progress of sorts.
With prf creator add superSU and create the prerooted ROM.
In TWRP Wipe everything but SDcard and OTG
Install pre rooted ROM
Then Install RICDefieat.zip, byeselinux_flashable.zip, and BusyBox-v1.24.1-Stericson.zip
Power off the phone.
Open Flashtool
Load ftf of .570 and check the Exclude System box and flash the phone
Install TWRP using Z3C_MM_TWRP_Recovery_V2_By_Serajr
And that should be it.
Managed to get everything working bar the TWRP but I think that was my fault.
A download file of everything you need bar the ROM.
Buleste said:
We have progress of sorts.
With prf creator add superSU and create the prerooted ROM.
In TWRP Wipe everything but SDcard and OTG
Install pre rooted ROM
Then Install RICDefieat.zip, byeselinux_flashable.zip, and BusyBox-v1.24.1-Stericson.zip
Power off the phone.
Open Flashtool
Load ftf of .570 and check the Exclude System box and flash the phone
Install TWRP using Z3C_MM_TWRP_Recovery_V2_By_Serajr
And that should be it.
Managed to get everything working bar the TWRP but I think that was my fault.
A download file of everything you need bar the ROM.
Click to expand...
Click to collapse
Worked?
marlontravagli said:
Worked?
Click to expand...
Click to collapse
It seems to be working for me at the moment. Even TWRP.
Edit: TWRP is unstable and sometimes becomes unavailable . If that happens just find SGP621-RICDefeat.zip to enable R/W again and reinstall.
Buleste said:
We have progress of sorts.
With prf creator add superSU and create the prerooted ROM.
In TWRP Wipe everything but SDcard and OTG
Install pre rooted ROM
Then Install RICDefieat.zip, byeselinux_flashable.zip, and BusyBox-v1.24.1-Stericson.zip
Power off the phone.
Open Flashtool
Load ftf of .570 and check the Exclude System box and flash the phone
Install TWRP using Z3C_MM_TWRP_Recovery_V2_By_Serajr
And that should be it.
Managed to get everything working bar the TWRP but I think that was my fault.
A download file of everything you need bar the ROM.
Click to expand...
Click to collapse
ok...this sims to be right, thanks
superpipo said:
ok...this sims to be right, thanks
Click to expand...
Click to collapse
It seems that updating busybox to 1.24.1 stericson stops R/W permissions and the ability to access TWRP however it is easily fixed.
Doing this quick update because today, when trying to root my phone, bricked it several times and lost all app info
If you are using android 7.11, this guide works fine: https://forum.xda-developers.com/zenfone-3-zoom/how-to/how-to-root-zenfone-3-zoom-ze553kl-t3622256
If on android 8, SuperSU will brick your phone. Use Magisk instead:
- enable usb debug mode on your phone
- unlock bootloader
- plug phone into your computer
on your pc
- Download fastboot and adb:
* Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
* macos: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
* linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
- download the latest Magisk unlock script from https://github.com/topjohnwu/Magisk/releases and copy it to a MicroSD or USB that you can attach to your phone. Look for Magisk, not Magisk Manager
- download twrp v 3.1.0-0-Z01H-20170408: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w?E81jQTCD (this is from https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w, as described in the old root guide using twrp + supersu. It is supposed to be safe)
- `adb reboot bootloader`
- `fastboot flash recovery <path to twrp image downloaded>`
- `fastboot reboot`
Right now, you should probably backup your phone.
back on your phone:
- before booting, press volume up on the bootloader, there, select Recovery. Using fastboot to reboot into recovery might cause the stock recovery image to reflash
- if prompted to enable system modifications, allow it.
- If prompted to decrypt your data in TWRP, use the PIN you setup. If it doesn't work, I can't guarantee you won't brick our phone. Feeling brave enough? In case of brick keep reading, it is easy to restore your phone to stock Android 8 using official firmware.
- press install, choose the device attached to your phone that has Magisk-xxx.zip and select it
- flash the image and it should be OK
In case of brick or unsuccessful flash from SuperSU and without backup:
- Don't panic, like I did today
- download the latest firmware from Asus: https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_BIOS/
- follow this guide: https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
- when the phone reboots, boot into recovery
- enable ADB sideload
- on your pc: `adb sideload <path to newest firmare>`
- now follow the root guide above before starting your phone
- ???
- profit
Note: commands using adb and fastboot assume you have put the contents from the downloaded platform tools in your PATH, else execute them from the directory in which they were extracted, for instance, on linux:
- `cd /home/$USER/Downloads`
- `unzip platform-tools-latest-linux.zip`
- `cd platform-tools`
- `./adb devices`
Bricked my phone.
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
gchamon said:
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
Click to expand...
Click to collapse
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
This is strange. Magisk is supposed to patch the boot image and install its app (by the way, if you update magisk using the app, phone enters bootloop)
Anyway, I have encountered myself many problems when installing, but nothing like this. Bootloops and corruption message on bootloader yes, but I can't seem to recall anything about partitions not being mounted. If installing stock recovery image, boot image and system doesn't do the trick, in my experience it is either bad partitioning, although unlikely, because those procedures doesn't repartition anything, or bad internal storage.
But just to be sure, you should reflash stock 7.1 image (recovery, boot and system) with fastboot, enter stock recovery and wipe cache/factory reset. If your phone is physically healthy, this should work
anonymousbsb said:
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
Click to expand...
Click to collapse
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Enrico06 said:
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Click to expand...
Click to collapse
Cool, if this fixes the issue I will update the guide with this info
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
kingairtel08 said:
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
Click to expand...
Click to collapse
Downgrade to 7.1.1 and try it again.
Already tried on 7.1.1 lot of times same error shows.
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
normal. please wait 15min max
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
I can't really help you there. This guide is supposed to work for those who are able to unlock bootloader using official asus tools. Never heard of unofficial unlock methods. It is possible that you have a hardware problem if you use those tools and they just don't work.
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
Have you used the latest official unlocking tool? I see there's a July 2019 version available.
If you are on an older version of Android (not Oreo) are you presently still getting OTA update prompts?
I tried this tool but no result.
is it possible to root ZE553KL without loosing user application's data? I have unrooted device, wanted to migrate telegram secret chats to new phone. it is doable but with rooted smartphone only. if rooting process is destructive I cannot migrate. if rooting is doable with preserving installed applications along with their data then there is a hope for successful migration.
does this method look promising or it is just fake method?
Asus Zenfone 3 Zoom ZE553KL root using Magisk [No need TWRP Recovery
How to root Asus Zenfone 3 Zoom ZE553KL with Magisk [no need TWRP recovery, easy method to rood your Android device.
www.mobilewithdrivers.com
so i rooted device. here are images.
guide later
my version is 61.0.A.10.1.release-keys
Chinese Stock
the original image
boot_X-FLASH-ALL-4BA8.tar.gz
magisk patched image
magisk_patched-23000_clKca.tar.gz
guide:
!!!DATA WIPE AUTOMATE!!!
1. unlock the device
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code
2.download the firmware.
use xperiFirm. find it in xda.
downloading takes me 20hr.
3.unsin the boot image
use unsin. also find in xda.
4.install magisk. and push boot image to device storage.
magisk in xda. or https://github.com/topjohnwu/Magisk/releases
5.follow magisk guide
https://topjohnwu.github.io/Magisk/install.html#patching-images
Copy the boot image to your device
Press the Install button in the Magisk card
Choose “Select and Patch a File” in method, and select the stock boot image
The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.
Copy the patched image to your PC with ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].img
Click to expand...
Click to collapse
fastboot mode is volume up and plug cable when power off
====if your downloaded my magisk patched image, you start here.====
Flash the patched boot/recovery image to your device.
For most devices, reboot into fastboot mode and flash with command:
fastboot flash boot /path/to/magisk_patched.img or
Reboot and voila!
Click to expand...
Click to collapse
6.open magisk follow it to root your device.
7.done
Sorry, after that i have to use the phone further with unlocked bootloader to keep root ?
Is the phone loose something functionality after unlocking ?
DennisDD78 said:
Sorry, after that i have to use the phone further with unlocked bootloader to keep root ?
Is the phone loose something functionality after unlocking ?
Click to expand...
Click to collapse
Good question. I m sure DRM would gone.
But since Chinese is really just AOSP. I m havent lost any functionality.
To be Tested:
Pair dualshock 4 game pad
HDMI input as Display
Camera seems OK. And encrypt phone And encrypt tf card works fine.
So what feature Other?
Hello,is there any way I can unlock the /system partition?
Hellp there, I also use XQ-BC72 but when I try to unlock my phone, typing “fastboot oem unlock 0x<insert your unlock code>” into CMD it will back a weird message:"FAILED (remote: 'Command not supported in default implementation')". Did U had solution? Thx a lot.
I can not get into the step of download that get stuck by the unlock step......wtf is it
Unlock code is replace by mine correctly...... Confusing......
zzqstcc007 said:
Unlock code is replace by mine correctly...... Confusing......
Click to expand...
Click to collapse
fastboot mode is volume up and plug cable when power off
Click to expand...
Click to collapse
you may need to install the fastboot driver manually
Hi everyone, this is my first post here on Xda,
I seem to have committed a costly mistake since this is not available in India, in a hurry i bought the Japanese version of this phone, the S0-51B,which incidentally is a single sim variant. Is there anyway of I can flash this Chinese Rom and achieve Dual Sim?
I saw online that there is not much hardware difference between this and the Chinese version. Can anyone kindly confirm this?.
lxjsilver said:
Hello,is there any way I can unlock the /system partition?
Click to expand...
Click to collapse
Hi,
someone found a way?
i wan't to make a root for ios emoji
hanania said:
i wan't to make a root for ios emoji
Click to expand...
Click to collapse
Just for emojis come on...
Hi
I recently bought a p20 lite from Facebook and i think the previous owner must have flashed the wrong firmware. In developer options there is no oem unlock button, and i tried eRecovery and it didn't work. The phone is dual sim, some apps see as if the phone is rooted and when i check with root checker, there's no root. I'm from South Africa and i hope i provided the necessary information. I would like to downgrade the phone to the firmware I'll be able to get the bootloader code from.
Looneychoons said:
Hi
I recently bought a p20 lite from Facebook and i think the previous owner must have flashed the wrong firmware. In developer options there is no oem unlock button, and i tried eRecovery and it didn't work. The phone is dual sim, some apps see as if the phone is rooted and when i check with root checker, there's no root. I'm from South Africa and i hope i provided the necessary information. I would like to downgrade the phone to the firmware I'll be able to get the bootloader code from.
Click to expand...
Click to collapse
Hi, just to be sure -
A) enter Project Menu (*#*#2846579#*#*) > 'Network info ... ' > 'Vendor country info'
B) In fastboot mode run command
fastboot oem oemimforead-CUSTOM_VERSION
and post the results.
Edit.: what was the reason for the failure with erecovery?
-Alf- said:
Hi, just to be sure -
A) enter Project Menu (*#*#2846579#*#*) > 'Network info ... ' > 'Vendor country info'
B) In fastboot mode run command
fastboot oem oemimforead-CUSTOM_VERSION
and post the results.
Edit.: what was the reason for the failure with erecovery?
Click to expand...
Click to collapse
Thanks for the reply man.
Vendor country is hw/meafnaf. Secondly, I get oeminforead-CUSTOM_VERSION failed. When i did erecovery i got 'Getting package info failed' i did factory reset and tried again but same error.
Looneychoons said:
Thanks for the reply man.
Vendor country is hw/meafnaf. Secondly, I get oeminforead-CUSTOM_VERSION failed. When i did erecovery i got 'Getting package info failed' i did factory reset and tried again but same error.
Click to expand...
Click to collapse
Okay, try this way out:
1. Download Oreo Service ROM
2. Unpack it and copy dload folder (can be found in 'Software') to the SD Card (without unpacking it!)
3. Turn of your phone and use three button combo (dload method) .
The process will erase all your data!
-Alf- said:
Okay, try this way out:
1. Download Oreo Service ROM
2. Unpack it and copy dload folder (can be found in 'Software') to the SD Card (without unpacking it!)
3. Turn of your phone and use three button combo (dload method) .
The process will erase all your data!
Click to expand...
Click to collapse
Thank you bro I'll let you know how it goes. After dload do i setup the device or wipe and factory reset, also do i check for updates or just buy credits for dc unlocker to get my bootloader code?
Looneychoons said:
buy credits for dc unlocker to get my bootloader code?
Click to expand...
Click to collapse
First check if ANE-LX2 is supported, I'm not sure...
Looneychoons said:
wipe and factory reset,
Click to expand...
Click to collapse
not necessary now
-Alf- said:
First check if ANE-LX2 is supported, I'm not sure...
not necessary now
Click to expand...
Click to collapse
Thanks man I'll kepl you posted.
-Alf- said:
First check if ANE-LX2 is supported, I'm not sure...
not necessary now
Click to expand...
Click to collapse
Hey bro I can't thank you enough. All went well after dload, I got my oem unlock button working, all that's left is to get my bootloader code. After I get it I want to root my phone, so can you please help me with a tutorial, from installing the correct twrp for my device and flashing magisk?
Looneychoons said:
Hey bro I can't thank you enough. All went well after dload, I got my oem unlock button working, all that's left is to get my bootloader code. After I get it I want to root my phone, so can you please help me with a tutorial, from installing the correct twrp for my device and flashing magisk?
View attachment 5372567View attachment 5372569
Click to expand...
Click to collapse
For Oreo only!
Download TWRP
Magisk.zip
Magisk manager apk
- download Magisk.zip and copy it to SD
- install Magisk manager apk
- install TWRP in fastboot mode, use command:
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot
- flash magisk.zip in TWRP
- reboot
- open M.manager apk
Update Manager & Magisk , if you want.
-Alf- said:
For Oreo only!
Download TWRP
Magisk.zip
Magisk manager apk
- download Magisk.zip and copy it to SD
- install Magisk manager apk
- install TWRP in fastboot mode, use command:
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot
- flash magisk.zip in TWRP
- reboot
- open M.manager apk
Update Manager & Magisk , if you want.
Click to expand...
Click to collapse
Really bro thank you. You're the best.