Nokia 6 Rooting? - Nokia 6 Questions & Answers

Hi!
I need some help rooting my Nokia 6 Mobile phone
The model number is TA- 1033
I have tried all kinds of different sources as a guide, but all failed for me.
I tried several one-click root tools as well. (Kingroot, Kingo Root)
I have tried to unlock the bootloader with Fastboot and ADB for the TWRP recovery flash
I have got developer options and also enabled USB Debugging and OEM unlocking ut the procedure still fail all the time.
I've tied to flash the TWRP without unlocking the bootloader but that ailed as well.
My device is not bricked yet.
Thank you for your help

My attempts to root were successful only on Nougat (Not Oreo, because of bootloader)
Make a backup of all your important files in your phone.
Download OST and with it install this stock rom (https://mega.nz/#!5ccRnb4b!VsgiKQ4CjxFyjbjcxR0esjeKmHZsUTnEz0FA_FMZQbM)
(To install it, you need the phone in bootloader mode.)
If it displays an error the first time, try again until the installation is fully successful.
Once the phone is turned on, the first thing you need to do is turn off automatic software updates. Know that if you want root, you should forget about OTA updates.
Once all written above is done remains to unlock the bootloader and installing TWRP.
For that..
Enter in bootloader mode.
Use Fastboot from your PC and enter this command to allow the partitions to be changed on your phone.
(To get MD5 of your serial number, use this website: http://www.miraclesalad.com/webtools/md5.php)
fastboot oem dm-verity [MD5_of_your_device_serial_number]
(Example: fastboot oem dm-verity 5f47b9a8dc1da1873c12945cf806691e)
After that download this bootloader(http://pc.cd/xUFrtalK) and flash it:
fastboot flash aboot D1C-emmc_appsboot.mbn
(Make sure that downloaded bootloader is located in adb/fastboot folder)[Or you can type full file path of bootloader(Example: "C:\Users\Martin\Downloads\D1C-emmc_appsboot.mbn")]
(This to flash an unlocked bootloader.)
fastboot reboot-bootloader
(This is to reboot for using new unlocked bootloader.)
fastboot oem dm-verity [MD5_of_your_device_serial_number]
(Again to allow installing partitions.)
Download recovery from here: https://mega.nz/#F!K1k0gC5C!xpw3-AQvSQJ5p6VWX19gpA)
Flash it with this command:
fastboot flash recovery nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img
(Make sure that downloaded recovery is located in adb/fastboot folder)[Or you can type full file path of twrp recovery(Example: "C:\Users\Martin\Downloads\nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img")]
After that reboot to twrp recovery and flash Magisk ROOT.
All is done.
Magisk is built in recovery. You don't need to download it from internet. Flash magisk which is in recovery.
Warning: After opening magisk manager you can update app but you can't update magisk version (core). Because latest version cause bootloop on ours devices. Use 16.1 version which is in recovery build it.
I hope everything will be fine. Good luck!

Hi! I have some issues.
marto2013 said:
My attempts to root were successful only on Nougat (Not Oreo, because of bootloader)
Make a backup of all your important files in your phone.
Download OST and with it install this stock rom
Click to expand...
Click to collapse
Okay
So when I tried to flash the rom you gave me it failed with a download error. I tried to use OST LA 6.0.4 and 6.1.2 but both failed.
Clicking on the "Edit phone information" didn't work either. Can you help me in this situation? I have tried to reinstall OST LA several times, but it didn't resolve the problem.

VargaTibor1 said:
Okay
So when I tried to flash the rom you gave me it failed with a download error. I tried to use OST LA 6.0.4 and 6.1.2 but both failed.
Clicking on the "Edit phone information" didn't work either. Can you help me in this situation? I have tried to reinstall OST LA several times, but it didn't resolve the problem.
Click to expand...
Click to collapse
On which patch level are you?

ZeroPointMax said:
On which patch level are you?
Click to expand...
Click to collapse
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08

VargaTibor1 said:
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
Click to expand...
Click to collapse
That means you cannot use OST LA or oem-veracity. Nokia changed the algorithm with August patch. You can basically not root your phone anymore using this method.

ZeroPointMax said:
That means you cannot use OST LA or oem-veracity. Nokia changed the algorithm with August patch. You can basically not root your phone anymore using this method.
Click to expand...
Click to collapse
He can downgrade his bootloader using older OTA update.
=====
VargaTibor1 said:
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
Click to expand...
Click to collapse
Make backup on anything! You will not have access to anything until you install the rom I gave you in the first post.
Go to recovery and flash this ota update.
https://my.pcloud.com/publink/show?code=XZYg1T7ZzpJwx2DdRo4wbpTUEXABAfnS9PgX
After all go to recovery again.
If it says that the Android version is 7.1, then everything is ready.
If it does not get the first time, flash ota again.
When I did it, I think I flash two times ota update.
If it's okay, try the Instructions from the first post again.

marto2013 said:
He can downgrade his bootloader using older OTA update.
=====
Make backup on anything! You will not have access to anything until you install the rom I gave you in the first post.
Go to recovery and flash this ota update.
https://my.pcloud.com/publink/show?code=XZYg1T7ZzpJwx2DdRo4wbpTUEXABAfnS9PgX
After all go to recovery again.
If it says that the Android version is 7.1, then everything is ready.
If it does not get the first time, flash ota again.
When I did it, I think I flash two times ota update.
If it's okay, try the Instructions from the first post again.
Click to expand...
Click to collapse
I thought this wouldn't work too

Related

[ROOT][MARSHMALLOW][HONOR 4C] Root, Recovery & Bootloader Unlock by HassanMirza01

DESCRIPTION:
Today i found the New Root & Installing Custom Recovery(TWRP) in MARSHMALLOW ROM surely...
I will Provide correct info and help......All This you are gonna do is At your Own Risk... Damage to your device of any type is at your Own Responsibility,,, Don't point finger at me or I will Just Laugh at you...
PREREQUISTES:
First of all, You should Unlock Bootloader so that on every reboot, Your Root shouldn't damage. You can unlock bootloader by simple procedure...and also enable the USB Debugging from Developers options in settings...
PROCEDURE:
FOR UNLOCKING BOOTLOADER, FOLLOW THIS
Download the Attached PC Software Named "Huawei Product ID Generator" then Extract this zip file...
Now open it, fill all Info in it and it will Generate a Product ID for your Phone....
Now go to this site Unlocking Code website
Login to this site using your Huawei id which you made in themes store or in huawei cloud!!
Use the Serial Number Written on BACK OF YOUR PHONE..!!
Fill like, smartphone>Product Model should be "HUAWEI Y300-0000"
then fill all fields and captcha also.. Click Submit and get the UNLOCKING CODE....
you can unlock bootloader wid that code then and root permanently....
After receiving the unlock code, write down the code;
Now go in your 4C's Settings>About Phone.
Then tap on Build number 10 times,,, you will get the Developers options in Last of Settings app. Open Developers option and Turn On the USB DEBUGGING.
Now connect your device to PC in MTP/FILES mode and then install the ADB drivers for it....
To install adb drivers correctly, use the Software Adb Driver Installer from here
LINK FOR ADB DRIVER INSTALLER
Full ADB folder is also attached Below.... put this folder in drive C.
Now Direct the cursor on the folder ADB, hold Shift and the right mouse button and choose "Open Command Window";
connect your phone to the PC in the "media device";
at the command prompt prescribe ADB Devices ;
then we write ADB reboot bootloader (the device will reboot mode fastboot);
then typed fastboot oem unlock **************** (where the asterisks replace unlock code);
BOOTLOADER UNLOCKED NOW!!
Now You are Ready to install TWRP recovery in Marshmallow first.... Download the Root and TWRP recovery File from here...
This File Also contain Stock Recovery of Marshmallow Rom
4C Root+TWRP by [email protected]
After this, unzip it and better come again in Fastboot Mode like above as explained, this time, move the recovery file to the adb folder which you want to install.
After that, type fastboot devices to see if your device is correctly attached to PC or Laptop. if yes then type this command in cmd to install the Custom Recovery(TWRP) in your phone.
fastboot flash recovery twrp.img
Then
fastboot reboot
This will reboot your phone and TWRP installed.
Gonna Done Root now... READ CAREFULLY... ROOTING MARSHMALLOW IS NOT EASY...
Download This Zip File and then Go in TWRP recovery and swipe for allow modifications...... and then flash that zip file named 1.zip...
After its done,, restart your phone and if it promp to install su, ignore it....
Open supersu app installed in your phone and let it update its binaries...when done, reboot to recovery again and this time flash This File.
Then reboot your phone and then supersu will be stable,,,
Now you have Successfully Rooted Marshmallow
Hit Thanks and Support me if you Like and get help from this thread...Thank you...
This is Based on Stock Huawei Kernel, Not compiled by Me...
Contributors:
@HassanMirza01
Mohamed A. Abd Ellatif
Version Information:
Status: Stable
Stable Release Date: 2015-09-28
Created on: 2016-02-19
Last Updated on: 2016-04-09
Reserved
Is this is TWRP for Marshmallow? Because the recovery files.you have uploaded are dated 25th September 2015?
@mfbcool yes...this is for Marshmallow... But dont swipe allow modifications!!
Member gettin error after swiping...just do read only...
I root my device by this method yesterday
but today root not work in titanum backup
I check it by root checker and everything is ok
Even though this method works, I would not recommend moving SuperSU to system partition. I didn't moved it and still SU permissions are working fine. I say so because Chainfire in his new SuperSU adopted a 'Systemless Root' method that roots without modifying the system partition so that apps like Android Pay work properly. He achieved this by patching the Boot image and so root is installed in boot image and is enabled at every boot (that's why you may experience some boot loops after rooting). This makes taking OTA updates and unrooting the device easier as you can unroot by flashing the Stock Boot.img instead of flashing the whole system partition.
I believe moving SuperSU to system partition destroys the main purpose and idea Chainfire had while making SuperSU compatible with Marshmallow. We all know EMUI won't update on Rooted devices. So it would be a pain to reflash whole Stock System Partition before taking OTA.
Hi thanks, I'm root my mobile I'm in android 6.0 now how to get back to kikkat a stock rom from twrp
@G E N E R A L open supersu app and tick the mount name separation and restart phone... Titanium, kingroot all will recognize root
Hit thanks if it helps....
@TMDMOOSA if you wanna go back to KK, Flash stock recovery first!!
Then flash the back pkg B320, then B070
If you gets error, flash middle pkg of chc rom and then flash directly KK Rom usin stock recovery!!
hi
i have a problem
by flashing file 1.zip phone reboot twice and screen go black and nothing happens after
by flashing the ROM problem fix but i cant root my phone
i try this three times!!
what can i do?
thnx
@inshaalmirza
hello, I by mistake flash the root.zip of lollipop to my phone running marshmallow. Now my phone is stuck on bootscreen. what should I do now. adb is not working
onlyankush_s said:
@inshaalmirza
hello, I by mistake flash the root.zip of lollipop to my phone running marshmallow. Now my phone is stuck on bootscreen. what should I do now. adb is not working
Click to expand...
Click to collapse
this happened for me by flashing right zip file!!!
no solution??
i wipe all the data (even system data) by custom recovery and turn off the phone and hold power volume down and up together
by doing this if you have ROM file in your sd , new ROM will be instal on your device
just please tell me how i can root my phone??
@inshaalmirza @ mfbcool please reply what to do
onlyankush_s said:
@inshaalmirza
hello, I by mistake flash the root.zip of lollipop to my phone running marshmallow. Now my phone is stuck on bootscreen. what should I do now. adb is not working
Click to expand...
Click to collapse
onlyankush_s said:
@ mfbcool please reply what to do
Click to expand...
Click to collapse
Flash the complete Marshmallow ROM through Stock Recovery.
matinone said:
hi
i have a problem
by flashing file 1.zip phone reboot twice and screen go black and nothing happens after
by flashing the ROM problem fix but i cant root my phone
i try this three times!!
what can i do?
thnx
Click to expand...
Click to collapse
no one??
please
@onlyankush_s go in fastboot and then flash the system.img again.... Or flash stock M wid stock recovery...
@matinone there is written that flash supersu again after flashing 1.zip
Flash supersu zip too and tell... Or flash srock rom again by same method i told in most previous posr.... I am sick right now thats why replying late!!
inshaalmirza said:
@matinone there is written that flash supersu again after flashing 1.zip
Flash supersu zip too and tell... Or flash srock rom again by same method i told in most previous posr.... I am sick right now thats why replying late!!
Click to expand...
Click to collapse
thanks a lot!!!
it worked
by the same steps.it look like i got lucky this time
hope you get better soon
hi
plz help
i flash stock recovery and my phone go to rescue mode
help
I have successfully built TWRP 3.0.0-0 for our device which fixes the weird swipe to allow modifications bug and is fully compatible with Android 6.0 Marshmallow.
See here: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-0-0-huawei-honor-4c-t3349495
Also, to re-flash Stock ROM, you don't need to flash Stock Recovery. Huawei phones have 2 inbuilt recoveries. The second recovery (which is the Stock) can be accessed by 3 buttons method (Power + Volume Up + Volume Down).
@mfbcool i saw that thread early... Great work man... I know huawei have 2 inbuilt recoveries but 2nd one is erecovery and thats of no use at all... I tried it too many times!! If twrp 3.0 can flash update.app files,,, it gonna rocks , wish u best of luck man!! You did it

[ZE552KL/Z012DC] Canadian Thread - Unlock, Root, Update to Nougat

This thread will be for the Canadian version of ZE552KL, and will be updated with specific info relevant to Z012DC model found in Canada (Canada Computers, Staples, other retailers). It has WW SKU number.
It took me a while and some searching to figure all steps out. I also modified Asus N and M firmware to remove version checks. Without this step - i was stuck with error 7 in TWRP. The only difference between Z012D and Z012DC seems to be in Fastboot and ADB drivers, TWRP recovery, system images seem to work well so far.
Steps:
1. Download Fastboot and ADB Drivers. For me usb driver on ZE552KL Asus download page didn't work. Select "Only install driver", you do not need to update your drivers via DRP.
Fastboot driver (for Vendor VID_18D1&PID_D00D): http://drivers.drp.su/Telephone/Hua...03.00/Huawei-FORCED-Allx64-2.00.03.00-drp.exe
ADB Driver (for VID_18D1&PID_D002): http://drivers.drp.su/Telephone/Leshcat/WinAll/Leshcat-WinAll-drp.exe
2. Save the following files on your External SD Card:
Modified M image UL-ASUS_Z012D-WW-13.20.10.152-user.zip
Modified N image UL-ASUS_Z012D-WW-14.2015.1701.8-user.zip
SuperSU - latest version from here
no-verity-opt-encrypt-5-1.zip. Give thanks to @kaffeine1 , without him - we would all be stuck with black screens
3. Save ADB and Fastboot files on your computer, and extract; give thanks to @snowwolf725
4. Download newer recovery (TWRP 3.1.0) from here
5. Unlock bootloader via unofficial unlock method; give thanks to @snowwolf725
6. Get into fastboot by turning off the phone, and pressing volume up + power. Install recovery that you downloaded in step #4:
Code:
fastboot flash recovery twrp-3.1.0-0-Z012D.img
7. Follow the steps this guide by @kaffeine1 . Skip the steps of downloading Nougat and Marshmallow firmware from Asus site, as you have already downloaded and saved both firmwares in Step #2 . Also skip the last step - do not reboot into Nougat, but go back to fastboot mode.
8. Root Nougat - follow steps under #2 here:
https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926
How to update to the latest version of OS:
1. Go to Asus Site, download latest WW image UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
2. Extract UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip\META-INF\com\google\android\updater_script , edit, remove first two lines, and put back into the zip file (e.g. using 7zip)
3. Extract from above zip file boot.img , and flash it via: fastboot flash boot boot.img
4. Flash recovery: fastboot flash recovery twrp-3.1.0-0-Z012D.img
5. Reboot into recovery, and flash:
- Firmware that you modified in #2
- no-verity-opt-encrypt-5.1.zip
- Latest SuperSU
- Rooted.zip (from step #8 above)
6. Reboot mobile, and enjoy new version!
Phone info as purchased:
Model Number: ASUS_Z012DC
Android version: 6.0.1
Baseband version: M3.10.42-Libra_080001
Build number: MMB29P.WW_Phone-13.20.10.152-20161222
Manufacture date (on the box): January 2017
Latest version - UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
Model Number: ASUS_Z012DC
Android version: 7.0
Baseband version: M3.10.47-Libra_080001
Build number: NRD90M.WW_Phone-14.2020.1703.28-20170410
Special thanks to:
- @jcadduono for TWRP recovery
- @snowwolf725 for guide unlock bootloader
- @kaffeine1 for guide how to upgrade to N from M
Reserved for future use
can i follow this step for ZE520KL ?
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
lastremnant said:
can i follow this step for ZE520KL ?
Click to expand...
Click to collapse
no, I do not think so. these are different phones.
DilipRB said:
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
Click to expand...
Click to collapse
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
anterus said:
no, I do not think so. these are different phones.
Click to expand...
Click to collapse
nevermind sir, it worked for me
Strange things do happen!!!
anterus said:
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
Click to expand...
Click to collapse
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
lastremnant said:
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
Click to expand...
Click to collapse
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
DilipRB said:
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
Click to expand...
Click to collapse
i found it ...
apktool from :
https://forum.xda-developers.com/showthread.php?t=1989533
Sorry this was for apks... but i guess same principle aplies... when i can i shall try and post the outcome
DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
I noticed that in some cases TWRP doesn't "stick", and gets overridden by default bootloader. Specific check is essentially useless - just to prevent flash of improper image. Just remove the check in the new FW, or use modified FW that has the check removed. I think in your case you can just re-flash TWRP since your bootloader is unlocked?
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
DilipRB said:
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
Click to expand...
Click to collapse
flash modified images through twrp - with links in OP
Well my wife liked the phone so much, that she "kindly requested" me to gift it to her... now she is the proud owner of a canadian vertion of ZE552KL and i got myself a ZS570KL
thanks a lot for all your help.
P.D. : i think she was not happy with the time i was spending with the device.
I know this is going to sound super dumb, but the unofficial bootloader unlock still triggers the bootup message and voids the warranty, right?
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
DilipRB said:
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
Click to expand...
Click to collapse
That's what some manufacturers do, like Motorola and HTC. But from back when I unlocked the BL on my Zenfone 2 Laser, I remember that all it did (as far as I could tell) was unlock the bootloader and set a flag in the bootloader that made it say it was unlocked that couldn't be reversed. No need for fancy registration systems when you can just boot up the phone and take a look.
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Jarrick said:
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Click to expand...
Click to collapse
Updated OP with instructions regarding how to upgrade to the latest version of N - just tested steps myself. Should be applicable to all future versions of N posted on Asus site. Enjoy!

AP Fastboot Flash Mode (Secure)

Hi there,
I tried to update my Moto G4 Plus and I think I made some big mistakes..
I can only start into Bootloader with the following text shown below:
AP Fastboot Flash Mode (Secure)
BL: B0.0E (sha-4986429, 2016-104-13 14:23:47)
Baseband: [bla] ATHENE_EMEA_DSDS_CUST
Product/Variant: athene_16mp XT1642 16GB P2A
Serial Number: [bla]
CPU: MSM8952
eMMC: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=5f
Console [NULL]: null
Battery OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
Click to expand...
Click to collapse
- No TWRP or other Recovery
- No OS
- No Fastboot connection to my Win10 64bit anymore (
I think the problem is the "AP Fastboot Flash Mode (Secure)" Mode.
Any ideas how to solve it?!
thanks alot anyway
The AP Fastboot Flash mode(secure) seems okay to me. However it is highly possible that your drivers aren't installed on the phone. So in this case try to first connect the phone to the computer and see if it get's detected or not, and then you should manually install the fastboot USB driver. Download the driver zip from Google's repository and extract it, later choose the .inf file and then the Android Bootloader Interface.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
PS: This driver and the fastboot adb binaries are completely different thing. fastboot won't work unless you have this USB driver.
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
stefanhanz said:
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
Click to expand...
Click to collapse
The latest stock ROM is the NPJS25.93-14-10 (Sept 2017 security patch) build https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You'll have to flash the stock ROM in fastboot, which would wipe TWRP off your device again. You cannot properly flash stock firmware in TWRP (only can flash the system in TWRP).
Once you've flashed the stock ROM and TWRP, you can use ElementalX, I'm using the 1.0.4 stock version on the NPJS25.93-14-10 build with magisk 13.3 (to root) and it's running stably on my XT1642.
Thank you! Now its working as it should with the newest updates!
Thread can be closed. Thanks
stefanhanz said:
Thank you! Now its working as it should with the newest updates!
Thread can be closed. Thanks
Click to expand...
Click to collapse
Hello Friend
I would like to know if you can explain how to fix it is that the same happens to me the ap fastboot flash mode * secure * because before I had already used the blanckflash to revive it because first soo turned on the white led
sersrendon said:
Hello Friend
I would like to know if you can explain how to fix it is that the same happens to me the ap fastboot flash mode * secure * because before I had already used the blanckflash to revive it because first soo turned on the white led
Click to expand...
Click to collapse
Does anyone know what happened?
I updated the rom appeared this message.
Cell Phone: Moto g 4
Please help me :crying: :crying:
Imagens:
h t t p s:/ /goo.gl/nupYsT
h t t p s:/ /goo.gl/G8KNNV
Rog Ballester said:
Does anyone know what happened?
I updated the rom appeared this message.
Cell Phone: Moto g 4
Please help me :crying: :crying:
Imagens:
h t t p s:/ /goo.gl/nupYsT
h t t p s:/ /goo.gl/G8KNNV
Click to expand...
Click to collapse
Looks like you've used the blankflash and your device is in the temporary bootloader, waiting for a stock firmware flash to repair.
You could flash the latest December 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You do not have to use the OEM lock commands whilst flashing. Also, be aware this flashing procedure will erase your device. As always, if this works please do not flash older stock firmwares if you can, else you may hard brick again.
echo92 said:
Looks like you've used the blankflash and your device is in the temporary bootloader, waiting for a stock firmware flash to repair.
You could flash the latest December 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You do not have to use the OEM lock commands whilst flashing. Also, be aware this flashing procedure will erase your device. As always, if this works please do not flash older stock firmwares if you can, else you may hard brick again.
Click to expand...
Click to collapse
Não estou conseguindo, de uma olhada nessas imagens por favor
https: / /goo.gl/nupYsT
https: / /goo.gl/G8KNNV
Rog Ballester said:
Não estou conseguindo, de uma olhada nessas imagens por favor
https: / /goo.gl/nupYsT
https: / /goo.gl/G8KNNV
Click to expand...
Click to collapse
1) please post in English in these forums.
2) the images load up okay, you may require a Facebook account to access after removing the spaces in the link.
3) again, from what I see in the pictures, it appears your device has been flashed with a temporary bootloader and requires a full firmware flash. The above stock ROM should work with XT1626 devices, you may wish to check the stock ROM thread to confirm.
Edit: here are a couple of reports suggesting the ROM works on XT1626 devices. https://forum.xda-developers.com/showpost.php?p=75139620&postcount=538 https://forum.xda-developers.com/showpost.php?p=75263192&postcount=573
echo92 said:
1) please post in English in these forums.
2) the images load up okay, you may require a Facebook account to access after removing the spaces in the link.
3) again, from what I see in the pictures, it appears your device has been flashed with a temporary bootloader and requires a full firmware flash. The above stock ROM should work with XT1626 devices, you may wish to check the stock ROM thread to confirm.
Edit: here are a couple of reports suggesting the ROM works on XT1626 devices. https://forum.xda-developers.com/showpost.php?p=75139620&postcount=538 https://forum.xda-developers.com/showpost.php?p=75263192&postcount=573
Click to expand...
Click to collapse
When I pass the firmware flash, it comes back on the same screen
Gets stuck
:crying::crying:
Rog Ballester said:
When I pass the firmware flash, it comes back on the same screen
Gets stuck
:crying::crying:
Click to expand...
Click to collapse
Can I ask how you're flashing the firmware?
Have you got your device connected to your computer via USB?
Does your device show on your computer, and do you have the stock ROM downloaded and extracted to your ADB folder?
When you flash, do you see [okay] after each command?
I'd like to see a copy of the flashing output if possible please
echo92 said:
Can I ask how you're flashing the firmware?
Have you got your device connected to your computer via USB?
Does your device show on your computer, and do you have the stock ROM downloaded and extracted to your ADB folder?
When you flash, do you see [okay] after each command?
I'd like to see a copy of the flashing output if possible please
Click to expand...
Click to collapse
Yes, I have the room files.
Yes, my computer recognizes
I had the bootloader unlocked, I went to update and it caught
please look at the pictures:
https://goo.gl/q7AHhL
https://goo.gl/QstpTS
https://goo.gl/JSz8r2
Rog Ballester said:
Yes, I have the room files.
Yes, my computer recognizes
I had the bootloader unlocked, I went to update and it caught
please look at the pictures:
https://goo.gl/q7AHhL
https://goo.gl/QstpTS
https://goo.gl/JSz8r2
Click to expand...
Click to collapse
Okay, what about the rest of the flashing output, from starting with the fastboot flash partition gpt... command? I only see the end of the commands with fastboot OEM lock and fastboot reboot, where's the important section?
Also, you may wish to replace the NPJS25.93-14-8 stock ROM you have with the NPJS25.93-14-13 stock ROM if you see pre flash validation or security downgrade errors.
echo92 said:
Okay, what about the rest of the flashing output, from starting with the fastboot flash partition gpt... command? I only see the end of the commands with fastboot OEM lock and fastboot reboot, where's the important section?
Also, you may wish to replace the NPJS25.93-14-8 stock ROM you have with the NPJS25.93-14-13 stock ROM if you see pre flash validation or security downgrade errors.
Click to expand...
Click to collapse
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
Do you believe you can recover your cell phone?
Rog Ballester said:
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
Do you believe you can recover your cell phone?
Click to expand...
Click to collapse
I saw security downgrade errors, suggesting the stock ROM you are trying to flash is too old. Pre flash validation errors indicate the same thing, your downloaded stock ROM is not new enough to repair your device.
Please download the newest NPJS25.93-14-13 stock ROM as linked previously, delete the old stock ROM you have and replace with the newer stock ROM. Then try again. With a locked bootloader, especially, this is crucial. The bootloaders will block any attempts to flash old firmware if locked, hence why your device is still not working.
I've not bricked my phone, this process has been shown to work for others though. In some cases, flashing newer firmware than what you had could work. You have the June 2017 build, the NPJS25.93-14-13 build is December 2017.
echo92 said:
I saw security downgrade errors, suggesting the stock ROM you are trying to flash is too old. Pre flash validation errors indicate the same thing, your downloaded stock ROM is not new enough to repair your device.
Please download the newest NPJS25.93-14-13 stock ROM as linked previously, delete the old stock ROM you have and replace with the newer stock ROM. Then try again. With a locked bootloader, especially, this is crucial. The bootloaders will block any attempts to flash old firmware if locked, hence why your device is still not working.
I've not bricked my phone, this process has been shown to work for others though. In some cases, flashing newer firmware than what you had could work. You have the June 2017 build, the NPJS25.93-14-13 build is December 2017.
Click to expand...
Click to collapse
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
I wanted to thank you from the bottom of my heart. I got it sorted. Thank you so much for helping me. :good::fingers-crossed:
Rog Ballester said:
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
I wanted to thank you from the bottom of my heart. I got it sorted. Thank you so much for helping me. :good::fingers-crossed:
Click to expand...
Click to collapse
You're welcome
Please, in future, avoid downgrading your stock firmware if you can. If you do downgrade stock firmware, avoid OTA updates. Custom ROMs do not appear to matter in this regard.
I do not know if blankflashes will keep working as Motorola keeps updating the stock firmware. We may eventually need a new blankflash. Blankflashes are also rare as Motorola does not formally release them (luckily, we have a working one). So, do not rely on a blankflash to always bail you out of trouble.
stefanhanz said:
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
Click to expand...
Click to collapse
How did you installed twrp can you help me out please i am stuck on ap fastboot flash mode (secure)
with no rom and no recovery can you please help me? how will i get out of this situation? Please!
ILLUSORYINK said:
How did you installed twrp can you help me out please i am stuck on ap fastboot flash mode (secure)
with no rom and no recovery can you please help me? how will i get out of this situation? Please!
Click to expand...
Click to collapse
How did you get into this state in the first place?
I see from your other post you installed AICP, so you must have TWRP on your device already?
If you need to re-flash TWRP, then boot your device to the bootloader.
Connect your device to your computer, preferably with the original USB cable.
Open the ADB terminal on your computer, and ensure you have the TWRP flashable image on your computer, in your ADB folder.
In the ADB terminal, type 'fastboot devices' without quotes, ensure you get a serial number response from your device.
If you get a response, then type 'fastboot flash recovery <name of TWRP image>' without quotes, where the <name of TWRP image> is the TWRP image file name as on your computer. Ensure the file name is the same, taking into account file name extensions.
You should have flashed TWRP to your recovery partition on your device - use the volume keys on your device to select 'Recovery' then press the power button to boot to recovery. You should be booting to TWRP recovery.
In there, you should be able to copy a custom ROM and flash that within TWRP. Alternatively, you could download a fastboot stock ROM and flash that within fastboot (not TWRP) to restore your device, but ensure it's the correct and latest stock ROM for your device.

[X01BD] Can't install TWRP after unlocking with Official UnlockTool

Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
Guys, no one to help or assist?
Mr147 said:
Guys, no one to help or assist?
Click to expand...
Click to collapse
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
X10MINISTER said:
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
Click to expand...
Click to collapse
Yes, everything done.
Still no success.
Mr147 said:
Yes, everything done.
Still no success.
Click to expand...
Click to collapse
Did ur unlocking bootloader succeed?
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
X10MINISTER said:
Did ur unlocking bootloader succeed?
Click to expand...
Click to collapse
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Tyakrish said:
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
Click to expand...
Click to collapse
Tried everything except 2, none worked. I'll drop them a query over twitter like you say, let's see what their reply is.
I am on stock recovery, non working bootloader but unlocked, and stock rom unrooted.
I think Pie update may give some insight on fixing this.
Mr147 said:
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Click to expand...
Click to collapse
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
X10MINISTER said:
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
Click to expand...
Click to collapse
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Click to expand...
Click to collapse
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
#ArtFuL said:
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
Click to expand...
Click to collapse
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
So is it done?
Mr147 said:
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
Click to expand...
Click to collapse
See I recommend please use Linux (Manjaro or Ubuntu) , Windows will have driver issues forever and ever
had same issue after fota update UL-ASUS_X01BD-WW-15.2016
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Thanks , this method work me. had same issue after fota update UL-ASUS_X01BD-WW-15.2016.1902.192-user
Click to expand...
Click to collapse
I've the same problem too. Let me know if you've configure it out. Thanks.
Okay @Mr147, I've fix this. I checked Windows Update and there was a pending ASUS driver update. I downloaded it and now I can use the fastboot commands.
Anyone that can fix this problem? I also experience this.
Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
I suggest to Unlock with unofficial step, or read the post https://www.blocknesia.com/2019/04/unlock-bootloader-dan-install-twrp-asus-zenfone-max-pro-m2.html

Unlocking bootloader

With the huawei support down, could anyone please help me to unlock huawei nova 2i RNE-L22 bootloader and to root it?
DC. UNLOCKER?
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
bootloader unlock codes forbidden
Chisetdel31260 said:
DC. UNLOCKER?
It says
> If your phone runs Android 8 or later with latest security patch - then this service won't work!
I have the latest security patch(March 1, 2019), I've been searching for the past 3 days for a working method to root my mate 10 lite, found nothing.
Huawei stopped providing oem unlock codes, All the services that provided unlock codes for money are now obsolete too.
I'm trying to find a way to root this phone on my own, but I'm not sure where to go from here.
I've read this book today "XDA Developers' Android Hacker's Toolkit", but it teaches how to use rooting methods that are already out there and not how to create your own way to root a device.
Can you provide guidance on where to go from here to learn how to find vulnerabilities in android?
Click to expand...
Click to collapse
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite .
it works
bozka1 said:
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite ane than using Service ROM flash FW with security patch max. april 2018. After you can get bootloader unlock code here
(4€/4$).
Service ROMs you can find here :
Type RNE- or Rhone or Mate 10 lite. Gl!
Click to expand...
Click to collapse
Thanks, it worked!
I got my bootloader unlocker, now I'm installing a custom rom, but there's no much custom roms for mate 10 lite.
m10_lite said:
Thanks, it worked!
I got my bootloader unlocker, now I'm installing a custom rom, but there's no much custom roms for mate 10 lite.
Click to expand...
Click to collapse
Best Custom ROM is Stock ROM & root .
bozka1 said:
Best Custom ROM is Stock ROM & root .
Click to expand...
Click to collapse
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
davideakc said:
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
Click to expand...
Click to collapse
He did already
bozka1 said:
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite ane than using Service ROM flash FW with security patch max. april 2018. After you can get bootloader unlock code here
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
(4€/4$).
Service ROMs you can find here :
https://androidhost.ru/search.html
Type RNE- or Rhone or Mate 10 lite. Gl!
Click to expand...
Click to collapse
ante0 said:
He did already
Click to expand...
Click to collapse
Sorry, I've not explained clearly what i want to do...
I'm already with bootloader unlocked, I need a guide for root the phone
davideakc said:
Sorry, I've not explained clearly what i want to do...
I'm already with bootloader unlocked, I need a guide for root the phone
Click to expand...
Click to collapse
Sorry, I misread. xD
Well, you can either flash TWRP for Oreo. Not sure which is "best" though, take one with decryption support if available for RNE on Oreo. Then you flash Magisk zip in twrp.
Or you can take your stock ramdisk and patch it in Magisk Manager, then flash the patched ramdisk from fastboot.
I would provably go with TWRP and Magisk zip though, as you would need a stock ramdisk from an update.app of your build. So saves some downloading
Basically flash TWRP using fastboot: fastboot flash recovery_ramdisk twrp.img
Reboot to recovery which will end up in TWRP. Flash latest Magisk using the Install button in twrp.
ante0 said:
Sorry, I misread. xD
Well, you can either flash TWRP for Oreo. Not sure which is "best" though, take one with decryption support if available for RNE on Oreo. Then you flash Magisk zip in twrp.
Or you can take your stock ramdisk and patch it in Magisk Manager, then flash the patched ramdisk from fastboot.
I would provably go with TWRP and Magisk zip though, as you would need a stock ramdisk from an update.app of your build. So saves some downloading
Basically flash TWRP using fastboot: fastboot flash recovery_ramdisk twrp.img
Reboot to recovery which will end up in TWRP. Flash latest Magisk using the Install button in twrp.
Click to expand...
Click to collapse
Don't worry, thanks for the fast reply!
davideakc said:
Don't worry, thanks for the fast reply!
Click to expand...
Click to collapse
I can't find any TWRP with decryption. This one might work, it's from the MorfuZ thread: https://mega.nz/#!uD4FlCqL!ERBzP4ZWa2sR8f_wnn15F_cOFCdYVKgfYETjiehQkkQ
So it may or may not have working decryption. But if you have an external SD it doesn't really matter as you'd only transfer magisk to that.
Magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download latest stable.
Flash twrp using fastboot.
Reboot to recovery.
Transfer magisk zip to external SD.
Flash Magisk zip using the Install button
You will probably have to browse to /external_sd manually as it will default to /sdcard in the install browser.
If it fails to install using TWRP:
Open terminal in TWRP from the Advanced button then enter this command:
dd if=/dev/block/bootdevice/by-name/ramdisk of=/external_sd/ramdisk.img
This will dump your stock ramdisk to external sd, which you then can patch in Magisk Manager and flash the output file to 'ramdisk' using fastboot. You will have to install Magisk Manager apk first though, it can be found in the Magisk thread.
davideakc said:
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
Click to expand...
Click to collapse
Only EMUI 8.x !!!
Your device must have an*unlocked bootloader.
Huawei HiSuite installed on your computer because it will install all the USB drivers
Download and install*Minimal ADB and fastboot Tool*on your computer. The folder location should be C:\Program Files(x86)\Minimal ADB and fastboot.
https://www.the***********.com/minimal-adb-and-fastboot-tool-for-windows/
Download*TWRP-oreo-smart.img*file
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Copy the downloaded* TWRP file to the*Minimal ADB and fastboot folder.
Enable OEM unlocking on your phone (developer options) and USB debugging mode.
Now launch MAF32.exe (or cmd-here) file from the Minimal ADB and fastboot folder, a command window will open up.
Turn off your phone and connect to your PC. Reboot to fastboot mode using button combination Power and Volume down.
In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery_ramdisk TWRP-oreo-smart.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button combination Power and Volume Up or command*
adb reboot recovery
Download and copy to SD card latest Magisk.zip.
Boot your phone into TWRP,* in TWRP main menu tap 'Install', then navigate to the*Magisk.zip , tap it, then ‘Swipe to confirm Flash’.*
When the process is complete, tap Reboot System.
Enjoy !*
bozka1 said:
Only EMUI 8.x !!!
Your device must have an*unlocked bootloader.
Huawei HiSuite installed on your computer because it will install all the USB drivers
Download and install*Minimal ADB and fastboot Tool*on your computer. The folder location should be C:\Program Files(x86)\Minimal ADB and fastboot.
https://www.the***********.com/minimal-adb-and-fastboot-tool-for-windows/
Download*TWRP-oreo-smart.img*file
https://mega.nz/#!ot8TGIIa!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Copy the downloaded* TWRP file to the*Minimal ADB and fastboot folder.
Enable OEM unlocking on your phone (developer options) and USB debugging mode.
Now launch MAF32.exe (or cmd-here) file from the Minimal ADB and fastboot folder, a command window will open up.
Turn off your phone and connect to your PC. Reboot to fastboot mode using button combination Power and Volume down.
In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery_ramdisk TWRP-oreo-smart.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button combination Power and Volume Up or command*
adb reboot recovery
Download and copy to SD card latest Magisk.zip.
Boot your phone into TWRP,* in TWRP main menu tap 'Install', then navigate to the*Magisk.zip , tap it, then ‘Swipe to confirm Flash’.*
When the process is complete, tap Reboot System.
Enjoy !*
Click to expand...
Click to collapse
If I do this, I lost all apps and data or not?
davideakc said:
If I do this, I lost all apps and data or not?
Click to expand...
Click to collapse
No you won't, but you should always backup your data.
AztekSoul said:
No you won't, but you should always backup your data.
Click to expand...
Click to collapse
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
davideakc said:
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
Click to expand...
Click to collapse
Yes you can, although you have to download updates through firmware finder and update with HuRUpdater in twrp.
davideakc said:
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
Click to expand...
Click to collapse
Then there is another solution - install TWRP over eRecovery (my own experience) :
- copy to SD card TWRP-oreo-smart.img
- in main TWRP menu tap Install image, then navigate
to the TWRP-oreo-smart, select
eRecovery_ramdisk and confirm Flash . System
reboot.
- Download and copy to the Minimal ADB and fastboot folder RECOVERY_RAMDISK330.img
https://mega.nz/#!I511VK4b!9cGodiCORHOvXndOCHyqcezpHmUk2zeTslqpbZe8pk4
Connect your phone to PC in fastboot mode and install recovery_ramdisk using command
- fastboot flash recovery_ramdisk RECOVERY_RAMDISK330.img
- fastboot reboot
How to boot into TWRP: reboot your phone and press Volume Up key up to 3 seconds to enter TWRP.
bozka1 said:
Then there is another solution - install TWRP over eRecovery (my own experience) :
- copy to SD card TWRP-oreo-smart.img
- in main TWRP menu tap Install image, then navigate
to the TWRP-oreo-smart, select
eRecovery_ramdisk and confirm Flash . System
reboot.
- Download and copy to the Minimal ADB and fastboot folder RECOVERY_RAMDISK330.img
https://mega.nz/#!I511VK4b!9cGodiCORHOvXndOCHyqcezpHmUk2zeTslqpbZe8pk4
Connect your phone to PC in fastboot mode and install recovery_ramdisk using command
- fastboot flash recovery_ramdisk RECOVERY_RAMDISK330.img
- fastboot reboot
How to boot into TWRP: reboot your phone and press Volume Up key up to 3 seconds to enter TWRP.
Click to expand...
Click to collapse
After that, how can I restore factory eRecovery?
davideakc said:
After that, how can I restore factory eRecovery?
Click to expand...
Click to collapse
Okay, one can install Magisk without TWRP. There are plenty of guides on how to do these things in the Mate 10 forums. Of course, TWRP makes things easier ....

Categories

Resources