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!
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
patched boot.img :
https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
Click to expand...
Click to collapse
Hi, might be a stupid question but where is the patched boot.img/how do I do it myself?
Craventoby said:
Hi, might be a stupid question but where is the patched boot.img/how do I do it myself?
Click to expand...
Click to collapse
I will upload it, i downloaded the new firmware with june security patch and extracted the boot.img from it, you can do the same or wait when i go home to upload it for you
https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w
Craventoby said:
Hi, might be a stupid question but where is the patched boot.img/how do I do it myself?
Click to expand...
Click to collapse
https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w
enjoy
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
patched boot.img :
Click to expand...
Click to collapse
Hey, I did root my phone with that but the wifi doesn't seem to work anymore.. do you have the same issue or/and do you have the stock boot.img file that I can try to flash ?
Thanks !
Hironichu said:
Hey, I did root my phone with that but the wifi doesn't seem to work anymore.. do you have the same issue or/and do you have the stock boot.img file that I can try to flash ?
Thanks !
Click to expand...
Click to collapse
https://mega.nz/#!6nJhQKba!XylZfJqVyRCXdIzZnVbhwhQFs5arpPf6Cg36mR0L9_Q
Hironichu said:
Hey, I did root my phone with that but the wifi doesn't seem to work anymore.. do you have the same issue or/and do you have the stock boot.img file that I can try to flash ?
Thanks !
Click to expand...
Click to collapse
Small update on this, there was an Android update recently, and it fixes everything ??* so if someone else here has the same issues somehow, updating to July update fixes it
I've some questions:
-does Nokia release his kernel source and which version use? on their website there is only for 3.1 I don't know if are same thing.
-Does support treble?
hello, now there is a august update for nokia 3.2 Do u have the boot file for that.. or how can I find it??
I add this phone to the list of my amazon.it account to make some stuff like twrp and roms but didn't buy yet, I'm afraid that Nokia will not release kernel source soon so in case of taking one I can make a twrp with stock kernel extracted from boot.img see ya.
Edit: buying this phone has been cancelled after reading unlocking bootloader seems to be "impossible" shame on you dear Nokia
disy
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
patched boot.img 8LSD2fhKkw6nCvdOKcU1j0w"]https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w[/URL]
Click to expand...
Click to collapse
Good afternoon, I HAVE BY THIS METHOD THE PHONE IN THE LOADER HANGED, HELP TO RETURN TO THE OPERATIONAL CONDITION.
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb
Click to expand...
Click to collapse
Can you tell what your current build number is?
I suspect there is more than one firmware flavor around.
Thanks!
.
JFDee said:
Can you tell what your current build number is?
I suspect there is more than one firmware flavor around.
Thanks!
.
Click to expand...
Click to collapse
i dont know coz i sold the phone months ago but i managed to root it without problems you have just to patch it by your self with your current build and then flash it using fastboot mode
bouyhy01 said:
i dont know coz i sold the phone months ago but i managed to root it without problems you have just to patch it by your self with your current build and then flash it using fastboot mode
Click to expand...
Click to collapse
Thanks for replying!
Unfortunately, I don't have my current build as a separate firmware file, and QFIL is not able to get the boot image from my phone because the communication stops right away.
My build number starts with 00EEA, whereas your boot image (and the full stock ROM on Mega that you linked) contains 00WW. I'm not sure this firmware is compatible with my Nokia 3.2 ...
.
JFDee said:
Thanks for replying!
Unfortunately, I don't have my current build as a separate firmware file, and QFIL is not able to get the boot image from my phone because the communication stops right away.
My build number starts with 00EEA, whereas your boot image (and the full stock ROM on Mega that you linked) contains 00WW. I'm not sure this firmware is compatible with my Nokia 3.2 ...
.
Click to expand...
Click to collapse
if you have a link for the whole firmware i can download it and extract the boot.img for you and then upload it i do have a gigabit internet speed
bouyhy01 said:
if you have a link for the whole firmware i can download it and extract the boot.img for you and then upload it i do have a gigabit internet speed
Click to expand...
Click to collapse
Thanks!
I've looked around and so far could not find the stock firmware for my phone.
If I had it, I'm sure I could manage to extract the boot.img and let Magisk patch it (I've done that before with other devices).
JFDee said:
Thanks!
I've looked around and so far could not find the stock firmware for my phone.
If I had it, I'm sure I could manage to extract the boot.img and let Magisk patch it (I've done that before with other devices).
Click to expand...
Click to collapse
i found it but its a .bin
bouyhy01 said:
i found it but its a .bin
Click to expand...
Click to collapse
Thanks for your efforts - I was able to solve the problem today.
It seems there are different versions of the same "programmer" around that is used in QFIL to extract your own boot image from the phone.
Originally, I used the one provided by @hikari_calyx in his unlock thread. Today I noticed that the programmer file in the stock firmware you provide here has a slightly different size. I tried this one and it worked.
So I could extract my "boot.img" from the phone. Rooting was easy after that.
I think it's always safer to use one's own boot image than trying to flash one that was lying around elsewhere.
Here is my post in the other thread for reference. Thanks again for your research and for providing the stock firmware!
.
Hello JFDee,
is it possible that you upload your original or modified boot image also?
Because i flashed the boot image that was given here and now i have the same problem, like said before.
WLAN is not working anymore and the Boot time is very long. Updating also don't work.
I also saw the differences in the build numbers.
My is like yours 00EEA....
This would be really nice, because i don'T find the stock image for this number.
Best regards!!!!
JFDee said:
Thanks for your efforts - I was able to solve the problem today.
It seems there are different versions of the same "programmer" around that is used in QFIL to extract your own boot image from the phone.
Originally, I used the one provided by @hikari_calyx in his unlock thread. Today I noticed that the programmer file in the stock firmware you provide here has a slightly different size. I tried this one and it worked.
So I could extract my "boot.img" from the phone. Rooting was easy after that.
I think it's always safer to use one's own boot image than trying to flash one that was lying around elsewhere.
Here is my post in the other thread for reference. Thanks again for your research and for providing the stock firmware!
.
Click to expand...
Click to collapse
Has anyone here rooted this tablet with Magisk?
Any very detailed step by step guide somewhere with links to the specific files to download for this tablet? (It'd be great if it didnt't require a PC but even if it does, I'd really appreciate a detailed step by step guide to put Magisk on this tablet)
Thanks
Try this
Planet Indigo said:
Has anyone here rooted this tablet with Magisk?
Any very detailed step by step guide somewhere with links to the specific files to download for this tablet? (It'd be great if it didnt't require a PC but even if it does, I'd really appreciate a detailed step by step guide to put Magisk on this tablet)
Thanks
Click to expand...
Click to collapse
Hi there,
I wouldnt't use Magisk on your device as it might softbrick your drive
So use KINGOROOT.
THE STEPS ARE VERY EASY TO FOLLOW.
https://www.kingoapp.com/
Regards,
KIBS2173
KIBS2173 said:
Hi there,
I wouldnt't use Magisk on your device as it might softbrick your drive
So use KINGOROOT.
THE STEPS ARE VERY EASY TO FOLLOW.
https://www.kingoapp.com/
Regards,
KIBS2173
Click to expand...
Click to collapse
Why would Magisk be more risky than Kingoroot on this device? I liked the idea of Magisk because it is systemless root and it is easier to hide from some apps.
Can Kingoroot one click root apk even root a Teclast M16 running android 8?
For M16, there is no root at all yet. I look forward to it myself, but so far there is nothing ....
Planet Indigo said:
Why would Magisk be more risky than Kingoroot on this device? I liked the idea of Magisk because it is systemless root and it is easier to hide from some apps.
Can Kingoroot one click root apk even root a Teclast M16 running android 8?
Click to expand...
Click to collapse
Hi there,
I tried Magisk on a chinese phone, and after flashing the software, the phone just went into black screen and soft-bricking the whole phone, the phone works in the background but the screen is black. And KINGOROOT will not flash anything into your device.
Regards
KIBS2173
Karamarov1 said:
For M16, there is no root at all yet. I look forward to it myself, but so far there is nothing ....
Click to expand...
Click to collapse
So you have the tablet yourself and no luck with anything?
I can't seem to find anything on the net about rooting this tablet, it's weird too since it "only" has android 8, not the latest android versions. I sure hope Magisk or another root method is going to be developed soon because I'm really interested in that tablet model.
KIBS2173 said:
Hi there,
I tried Magisk on a chinese phone, and after flashing the software, the phone just went into black screen and soft-bricking the whole phone, the phone works in the background but the screen is black. And KINGOROOT will not flash anything into your device.
Regards
KIBS2173
Click to expand...
Click to collapse
I heard from another forum user who has the Teclast M16 and he said that Kingoroot didn't work on it.
Try this
Planet Indigo said:
So you have the tablet yourself and no luck with anything?
I can't seem to find anything on the net about rooting this tablet, it's weird too since it "only" has android 8, not the latest android versions. I sure hope Magisk or another root method is going to be developed soon because I'm really interested in that tablet model.
I heard from another forum user who has the Teclast M16 and he said that Kingoroot didn't work on it.
Click to expand...
Click to collapse
Hi there,
So i was researching more about this tablet, turns out you can root by installing a custom recovery (TWRP) and from there you can install SUPERSU to achieve root for your tablet. I am not sure if this method works, but if your able to get the stock firmware and the stock recovery and the software to flash the firmware i think you might as well go ahead using that method.
THIS IS THE ARTICLE I FOUND ONLINE :
https://www.getdroidtips.com/how-to-install-twrp-recovery-on-teclast-t30-and-root-it-easily/
*MAKE SURE YOU FIND OUT IF THIS TABLET HAS A TWRP RECOVERY BEFORE DOING ANYTHING ELSE*
Thank you for looking into it, unfortunately that guide is for the Teclast T30 and the guy advises to only use it for that model. I don't own that tablet yet so I can't try any of the steps myself but I'm very interested in this particular model (16/9 ratio, hdmi out, dc charger in, etc...) so I was really hoping to find a tested working method to root it before I go ahead and purchase it.
i found this: https://www.getdroidtips.com/root-teclast-m16/
I rooted my Teclast M16 using Magisk. Simply unlocked the bootloader through adb/fastboot commands, then have magisk manager patch the boot image from firmware download and then flash it using adb/fastboot command line fastboot flash boot magisk_patched_boot.img reboot system and its rooted.
I haven't found a twrp recovery yet, but I'm thinking about trying my hand at building my own, despite being a noob.
I can confirm
install adb fast boot
Enable USB debugging and OEM Unlock on your Android device.
adb reboot bootloader
fastboot flashing unlock
Volume up
fastboot reboot
Wait a few minutes to reinstall
enable usb debugging again
download firmware
you will finde a google spreadsheet on the facebook page of telcast
Copy boot.img on the device
install magisk manager via apk
install magisk via patch boot.img in download folder
download patched boot.img
patch device
adb reboot-bootloader
fastboot flash boot magisk_patched_boot.img
fastboot reboot
M16(M6P2)_Android 8.0_V1.07_SZ
boot.img httpx://mirr.re/d/2wHd
full httpx://mirrorace.com/m/1Ek3z httpx://mirr.re/d/2wHj
Hi. Have you got you on working twrp recoberto?
fdsafggg said:
I can confirm
install adb fast boot
Enable USB debugging and OEM Unlock on your Android device.
adb reboot bootloader
fastboot flashing unlock
Volume up
fastboot reboot
Wait a few minutes to reinstall
enable usb debugging again
download firmware
you will finde a google spreadsheet on the facebook page of telcast
Copy boot.img on the device
install magisk manager via apk
install magisk via patch boot.img in download folder
download patched boot.img
patch device
adb reboot-bootloader
fastboot flash boot magisk_patched_boot.img
fastboot reboot
M16(M6P2)_Android 8.0_V1.07_SZ
boot.img httpx://mirr.re/d/2wHd
full httpx://mirrorace.com/m/1Ek3z httpx://mirr.re/d/2wHj
Click to expand...
Click to collapse
Hi.
I tried to unlock the bootloader .
adb devices command shows the m16.
I send the command "adb reboot bootloader" - the device enter in bootloader.
next I send the command "fastboot devices" and I get this:
PS E:\modified_fastboot> fastboot devices
???????????? fastboot
any help to make fast boot see the device?
Thank you
dcoelho said:
Cześć.
Próbowałem odblokować bootloader.
Polecenie urządzeń adb pokazuje m16.
Wysyłam polecenie "adb reboot bootloader" - urządzenie wchodzi w bootloader.
następnie wysyłam polecenie „urządzenia fastboot” i otrzymuję to:
PS E:\modified_fastboot> urządzenia fastboot
???????????? szybki start
jakakolwiek pomoc, aby szybki rozruch zobaczył urządzenie?
Dziękuję Ci
Click to expand...
Click to collapse
Hi, You bad comand when bootloader. When bootloader after comand: " fastboot oem unlock" , luck on skreen, push volume up, wait moment, after next comand:"fastboot reboot". After this command, the tablet will reset to factory settings with unlocked bootloader.
Hello everyone. I have TWRP for M16, everything is almost fine, after uploading it normally work on M16, except for touch not working, I did not check if it works with the mouse. Maybe someone will find it to correct it so that the touch works? I upload the file, it may be useful to someone. Regards RW
reupload boot.img
Unlocking Bootloader1. Make sure you have a sim and active mobile data. Then go to about phone tap build number 7-8 times. After that go to advanced settings > developer options > turn on OEM unlocking and then check if this device is secure and click add account and device.
2. Download Mi unlock tool from here. Extract it and paste it in C:/unlock. or else your device won't be recognized for unlocking.
3. Open Mi unlock tool and then enter the Mi account which was on your device. Put your device in fastboot mode by pressing vol- and power and then connect to PC. Press unlock and if it tells you to wait you have no other option but to wait. If your mi flash tool shows connect your device even after you have connected it. Follow this guide here.
4. After you have unlocked your bootloader reboot your phone.
Flashing TWRP and Rooting via magisk
1. Download this TWRP image here. Thanks to the original developer mauronofrio.
2. Download adb and fastboot tools here and install it.
3. Now put your phone in fastboot mode and connect it with your pc. Now where you have downloaded the TWRP file rename it to TWRP.img and open a CMD window there if you don't know how just google.
4. Type the following commands
1. fastboot devices
2. fastboot flash recovery TWRP.img
3. fastboot reboot recovery.
Click to expand...
Click to collapse
5. Your phone will boot into TWRP now. But TWRP will be overwritten by stock miui recovery to stop that you need to flash Magisk. Download this zip move it to internal storage then flash by tapping on install and swipe to flash. Reboot your device. Reboot to recovery again to check if TWRP is present.
Now your device is rooted
OR
Flash latest OrangeFox Recovery if you don't want magisk.
Flashing A rom
1. Download.
2. Flash.
3 Format Data.
Done
Feel free to ask any questions. And don't point a finger at me for messing your device.
My mi unlock tool says can't get info. I using Indian version miui 12
Thanks for the useful guide. I have a quick question, does this works with MIUI 12?
igeekyayush said:
My mi unlock tool says can't get info. I using Indian version miui 12
Click to expand...
Click to collapse
Sorry for late reply. Have you installed the drivers correctly? Try using another port in your pc or use this mi unlock tool version zip
Doombuggie85 said:
Thanks for the useful guide. I have a quick question, does this works with MIUI 12?
Click to expand...
Click to collapse
Yes, it does.
hello,
thanks for the reply sir. yes i've tired changing port, pc everything. today i've factory reset my phone and added mi account and now i'm getting 7 days wait time. let's see now
LoadOP2 said:
Sorry for late reply. Have you installed the drivers correctly? Try using another port in your pc or use this mi unlock tool version zip
Click to expand...
Click to collapse
igeekyayush said:
hello,
thanks for the reply sir. yes i've tired changing port, pc everything. today i've factory reset my phone and added mi account and now i'm getting 7 days wait time. let's see now
Click to expand...
Click to collapse
Okay keep the sim inserted and use the device for 7 days. And if it doesn't work try using older version of unlock tool.
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
_benedict_ said:
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
Click to expand...
Click to collapse
Flashing a custom rom is optional. You don't NEED to flash a rom to get TWRP...
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
I've unlocked the bootloader using the unlock tool and waited for 7 days,
But i rooted the device using a different method where i patched a boot.img and flashed that to the device.
Will this method still work for me as I'm already rooted but just want TWRP so i can flash other ROMs.. The post says you have to flash magisk from the (temporary) TWRP for the TWRP to stay as the recovery..
Will the magisk on my phone and the magisk installed here collide?
I just want TWRP so i can switch to a custom rom, so any input is appreciated!!
_benedict_ said:
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
Click to expand...
Click to collapse
Skip the flashing a rom part and you will be good to go.
But i rooted the device using a different method where i patched a boot.img and flashed that to the device.
Will this method still work for me as I'm already rooted but just want TWRP so i can flash other ROMs.. The post says you have to flash magisk from the (temporary) TWRP for the TWRP to stay as the recovery..
Will the magisk on my phone and the magisk installed here collide?
I just want TWRP so i can switch to a custom rom, so any input is appreciated!!
Click to expand...
Click to collapse
You can flash twrp and then check if it persists. If not flash magisk again their is no thing as magisk colliding lol. Just make sure you flash a newer version. And if nothing works flash stock rom and then twrp.
If you have the stock boot IMG flash it and then intsall twrp and magisk.
smsry said:
Flashing a custom rom is optional. You don't NEED to flash a rom to get TWRP...
Click to expand...
Click to collapse
LoadOP2 said:
Skip the flashing a rom part and you will be good to go.
Click to expand...
Click to collapse
Haha, makes sense! Thank you for your answers
Nevermind.. i got it to work pretty easily..
I have twrp on this device and Pixel Experience ROM and it's working all fine..
But there's this one thing where when booting to recovery, it asks me to input a password for User(0) when i try to input anything it says password failed..
From reading the log, it says it's for decrypting data(8f I'm not mistaken)
Is this important? Do i need to decrypt it?
Currently the ROM works fine with no errors, so I'm not gonna bother, but would still like to know what this "decrypting" thing is..
smsry said:
Nevermind.. i got it to work pretty easily..
I have twrp on this device and Pixel Experience ROM and it's working all fine..
But there's this one thing where when booting to recovery, it asks me to input a password for User(0) when i try to input anything it says password failed..
From reading the log, it says it's for decrypting data(8f I'm not mistaken)
Is this important? Do i need to decrypt it?
Currently the ROM works fine with no errors, so I'm not gonna bother, but would still like to know what this "decrypting" thing is..
Click to expand...
Click to collapse
Yes, If you use a lock screen enter that password it will be decrypted. You will have to format data if you decide to flash any other rom anyway.
flashed twrp but not able to boot into recovery.
igeekyayush said:
flashed twrp but not able to boot into recovery.
Click to expand...
Click to collapse
There can be many reasons for that. Please tell me the error or what's actually happening. Then only I can be of help.
Sir ive used xiaomi flashtool v2 after that and it worked. Thanks sir. After that i updated to latest twrp from that chinese one.
LoadOP2 said:
There can be many reasons for that. Please tell me the error or what's actually happening. Then only I can be of help.
Click to expand...
Click to collapse
Joyeuse
Hello, Does it work for Joyeuse (European version)?
The name of TWRP says Curtana -Unified
rfguy said:
Hello, Does it work for Joyeuse (European version)?
The name of TWRP says Curtana -Unified
Click to expand...
Click to collapse
Yes Unified means all Snapdragon 720g Devices which include Joyeuse, Curtana, Gram, Excalibur.
Hey buddy, thank you for this quick step-by-step guide. I flash ROMs since 2012 and you know what? It helped me the same. Having all stuff needed for go from stock to custom concentrated in one place (plus some useful tip like the Magisk flash at the end) it's always useful and time-saving. Thank you
2 Micro-notes about fastboot btw:
- write 'fastboot (with lowered 'f'): it may confuse some newbie
- it's 'reboot' instead of 'boot'
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.