Related
New User who doesn't know how to root and bootunlock your yureka here is the guide,
http://www.thetechnotriad.com/326/how-to-root-yu-yureka/
GUIDE TO FLASH CM 14.1 VIA TWRP
I will tell you about the twrp method which i used to flash my rom.
After flashing twrp just download the rom given in the links below this thread and save it in sd card root folder,
Boot into recovery by pressing volume up and volume down and power key,
First of all backup your current SYSTEM DATA BOOT,
then go into wipe > advance wipe then select SYSTEM, DATA, DALVIK CACHE, CACHE,
and swipe to wipe.
Then go back to twrp home and select install and select the external sd and select the rom .zip file and swipe to flash it,
Same you have to do with gapps.zip file
Then just clear DALVIK CACHE
and reboot,
It will take up some time in cm logo then it will normally start
THIS METHOD WILL ERASE ALL APPS AND DATA BUT WILL NOT MESS UP WITH YOUR INTERNAL STORAGE OR EXTERNAL.
Download Links.
Link for Rom
https://docs.google.com/uc?confirm=u9h2&export=download&id=0B8Vodzmhc0GlY0R6UHh6UldzU00
https://forum.xda-developers.com/yureka/orig-development/rom-cyanogenmod-14-0-t3457546
Link for Gapp
http://opengapps.org/
GUIDE TO FLASH VOLTE ON YU YUREKA
Download the required files given below in the links
1.Extract both the zip folder and copy the NON-HLOS.bin file to ADB folder,
2.Reboot the phone to fastboot mode.
3.Open the ADB folder Press alt + shift + right click and click on open command window here.
5.Now type or copy paste this... Code:
( fastboot -i 0x1ebf flash modem NON-HLOS.bin )
Hit Enter.
This will flash the modem files.
When it says OK disconnect the phone and reboot.
Links for Volte Modem Files,
https://uplod.ws/hmr2cvk4xwao
https://uplod.ws/hmr2cvk4xwao
NOTE :- ALL THIS METHOD ARE NOT INVENTED BY ME I JUST TRIED IT AND WAS SUCCESSFUL BY LUCK
IF YOUR MOBILE IS BRICKED YOU ARE RESPONSIBLE FOR THAT JUST TRY NOT TO DO ANYTHING WRONG.
CREDITS :-
thetechnotriad for root guide
Men_in_black007 for the links
CM team
Geekysondh for the VOLTE files and guide.
I just gave a complete method to upgrade your OS to CM 14.1 and also flashing volte
I am also a new user here but know little bit about rooting n all
if u find it helpful that's enough for me
I am not at all good in providing guidance so if any errors mistake sorry for that
If any errors u face just leave a msg sure i will help u out as even i have face 100 of errors while trying this method coz of silly mistakes i did.
sk.shehbaz said:
New User who doesn't know how to root and bootunlock your yureka here is the guide,
http://www.thetechnotriad.com/326/how-to-root-yu-yureka/
GUIDE TO FLASH CM 14.1 VIA TWRP
I will tell you about the twrp method which i used to flash my rom.
After flashing twrp just download the rom given in the links below this thread and save it in sd card root folder,
Boot into recovery by pressing volume up and volume down and power key,
First of all backup your current SYSTEM DATA BOOT,
then go into wipe > advance wipe then select SYSTEM, DATA, DALVIK CACHE, CACHE,
and swipe to wipe.
Then go back to twrp home and select install and select the external sd and select the rom .zip file and swipe to flash it,
Same you have to do with gapps.zip file
Then just clear DALVIK CACHE
and reboot,
It will take up some time in cm logo then it will normally start
THIS METHOD WILL ERASE ALL APPS AND DATA BUT WILL NOT MESS UP WITH YOUR INTERNAL STORAGE OR EXTERNAL.
Download Links.
Link for Rom
https://docs.google.com/uc?confirm=u9h2&export=download&id=0B8Vodzmhc0GlY0R6UHh6UldzU00
https://forum.xda-developers.com/yureka/orig-development/rom-cyanogenmod-14-0-t3457546
Link for Gapp
http://opengapps.org/
GUIDE TO FLASH VOLTE ON YU YUREKA
Download the required files given below in the links
1.Extract both the zip folder and copy the NON-HLOS.bin file to ADB folder,
2.Reboot the phone to fastboot mode.
3.Open the ADB folder Press alt + shift + right click and click on open command window here.
5.Now type or copy paste this... Code:
( fastboot -i 0x1ebf flash modem NON-HLOS.bin )
Hit Enter.
This will flash the modem files.
When it says OK disconnect the phone and reboot.
Links for Volte Modem Files,
https://uplod.ws/hmr2cvk4xwao
https://uplod.ws/hmr2cvk4xwao
NOTE :- ALL THIS METHOD ARE NOT INVENTED BY ME I JUST TRIED IT AND WAS SUCCESSFUL BY LUCK
IF YOUR MOBILE IS BRICKED YOU ARE RESPONSIBLE FOR THAT JUST TRY NOT TO DO ANYTHING WRONG.
CREDITS :-
thetechnotriad for root guide
Men_in_black007 for the links
CM team
Geekysondh for the VOLTE files and guide.
I just gave a complete method to upgrade your OS to CM 14.1 and also flashing volte
I am also a new user here but know little bit about rooting n all
if u find it helpful that's enough for me
I am not at all good in providing guidance so if any errors mistake sorry for that
If any errors u face just leave a msg sure i will help u out as even i have face 100 of errors while trying this method coz of silly mistakes i did.
Click to expand...
Click to collapse
Thanks alot bro successfully updated to cm 14.1 and volte method working now i can call directly from phone app no need of jio4g voice app thanks alot
can someone guide me how to unlock bootloader on mac via terminal
i cant seem to unlock bootloader & thus everything else fails.
& now its stuck on bootlogo..
./fastboot-mac -i 0x1ebf devices (give me no response)
./fastboot-mac -i 0x1ebf oem unlock (says OKAY - but i dont think its unlocked)
Then i did :
Advanced reboot – turn it ON
Update Cyanogen recovery – turn it OFF
Android debugging – turn it ON
Now, turn off your phone.
then i did this :
./fastboot-mac -i 0x1ebf flash recovery yu-twrp-recoveryx64.img
after this i cannot boot into recovery. the bootlogo is stuck & if i press vol+ & vol- & power, it jusst keep rebooting.
now just stuck on YU bootlogo..
i can get into fastboot mode only & from fastboot, i can do this :
./fastboot-mac -i 0x1ebf boot recovery-yu.img
this brings me to cynogen recovery 6 & from there i did a wipe everything but no custom rom can be installed... all show errors, obviously, cause theres not root.
HELP !!
NOW, i'm stuck on boot logo..
cant do anything.
How should i revert back to everything stock & start all over again/
i have access to fast boot & 1 time boot recovery at a time
hypermaster said:
NOW, i'm stuck on boot logo..
cant do anything.
How should i revert back to everything stock & start all over again/
i have access to fast boot & 1 time boot recovery at a time
Click to expand...
Click to collapse
Kindly Share me your model no. And details of your mobile
sk.shehbaz said:
Kindly Share me your model no. And details of your mobile
Click to expand...
Click to collapse
YU YUREKA AO5510
Stuck on YU Boot Logo...
cant do anything, even if i 1 time boot to CM 6 & try to install the factory OS, it fails of shows aborted.
I Just want to go back to Stock & then try again clean.
& If i try to install official ROM after data wipe & system wipe, i get the below error :
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
& with cm-11.0-XNPH05Q-tomato-signed-fastboot.zip
EOCD not found, not Zip
error: failed to access zipdata in 'Qu/?^?`??????z?????Y\f?f"??=????????6??o??????m`????Ќ
??????E??z???Q??ō?m??Óo??[?????iG????7C'H?纛E??zU?JϞ?'
i now have access to a windows 10 laptop also apart from a mac
I tried you steps but when I place call phone restarts and goes into bootloop
from fastboot on my mac i did this :
./fastboot-mac -i 0x1ebf boot recovery-yu.img
(Booted into CM 6 for this 1 time only)
Wiped everything
tried to install : QuarkOS™-v3.0-Stable_YUREKA.zip
Surprisingly, this installed & i did a REBOOT, but now again, its been stuck on YU Boot logo.
jatintomar said:
I tried you steps but when I place call phone restarts and goes into bootloop
Click to expand...
Click to collapse
Wipe the mobile completely then first install your OS then flash the VOLTE files and see there on fastboot if any error pops up and let me know when you are entering the commands to flash VOLTE what exactly is there on fastboot showing.
hypermaster said:
YU YUREKA AO5510
Stuck on YU Boot Logo...
cant do anything, even if i 1 time boot to CM 6 & try to install the factory OS, it fails of shows aborted.
I Just want to go back to Stock & then try again clean.
& If i try to install official ROM after data wipe & system wipe, i get the below error :
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
& with cm-11.0-XNPH05Q-tomato-signed-fastboot.zip
EOCD not found, not Zip
error: failed to access zipdata in 'Qu/?^?`??????z?????Y\f?f"??=????????6??o??????m`????Ќ
??????E??z???Q??ō?m??Óo??[?????iG????7C'H?纛E??zU?JϞ?'
i now have access to a windows 10 laptop also apart from a mac
Click to expand...
Click to collapse
Windows 10 okk install Pda drivers first of all then adb and fastboot and ill post u link to flash it via fastboot coz windows 10 doesn't support normal drivers and doesn't flash the device i have faced this issue on my laptop then i flash it from my p.c which is win 7 there it was successful and yeah install stock version of yureka ill share links for you okk
hypermaster said:
from fastboot on my mac i did this :
./fastboot-mac -i 0x1ebf boot recovery-yu.img
(Booted into CM 6 for this 1 time only)
Wiped everything
tried to install : QuarkOS™-v3.0-Stable_YUREKA.zip
Surprisingly, this installed & i did a REBOOT, but now again, its been stuck on YU Boot logo.
Click to expand...
Click to collapse
https://m.youtube.com/watch?v=t5G42isjf68
Follow the tutorial and first uninstall each and every drivers from windows and then start the procedure again.
And quote me so I'll get a notification of your reply.
hypermaster said:
from fastboot on my mac i did this :
./fastboot-mac -i 0x1ebf boot recovery-yu.img
(Booted into CM 6 for this 1 time only)
Wiped everything
tried to install : QuarkOS™-v3.0-Stable_YUREKA.zip
Surprisingly, this installed & i did a REBOOT, but now again, its been stuck on YU Boot logo.
Click to expand...
Click to collapse
https://m.youtube.com/watch?v=t5G42isjf68
Follow this steps bro and yeah first uninstall each n every drivers from your windows then start the whole procedure again.
Update me soon will be waiting for your reply
sk.shehbaz said:
Windows 10 okk install Pda drivers first of all then adb and fastboot and ill post u link to flash it via fastboot coz windows 10 doesn't support normal drivers and doesn't flash the device i have faced this issue on my laptop then i flash it from my p.c which is win 7 there it was successful and yeah install stock version of yureka ill share links for you okk
Click to expand...
Click to collapse
Thanks a lot..
i downloaded & entered fastboot mode & did this :
factory-image-flash-tools-windows-flashtools
Flash-all.bat
This installed all boot.img, system, userdata,modem,bootloader, slb1, tz, aboot - All went well, then it said disconnect device & reboot.
Now, its not booting, no fastboot mode also, no recovery mode also.
now, its completely dead... nothings coming on now....
Just putting it for charging for awhile now, lets see if something comes up.
Just noticed. Device manager (windows 10) does not detect anything, when i connect USB to laptop.. only the red light shows now.
hypermaster said:
Thanks a lot..
i downloaded & entered fastboot mode & did this :
factory-image-flash-tools-windows-flashtools
Flash-all.bat
This installed all boot.img, system, userdata,modem,bootloader, slb1, tz, aboot - All went well, then it said disconnect device & reboot.
Now, its not booting, no fastboot mode also, no recovery mode also.
now, its completely dead... nothings coming on now....
Just putting it for charging for awhile now, lets see if something comes up.
Just noticed. Device manager (windows 10) does not detect anything, when i connect USB to laptop.. only the red light shows now.
Click to expand...
Click to collapse
Did you install the drivers first Coz Pda drivers are the only one which detects my yureka in fastboot mode on windows 10
hypermaster said:
Thanks a lot..
i downloaded & entered fastboot mode & did this :
factory-image-flash-tools-windows-flashtools
Flash-all.bat
This installed all boot.img, system, userdata,modem,bootloader, slb1, tz, aboot - All went well, then it said disconnect device & reboot.
Now, its not booting, no fastboot mode also, no recovery mode also.
now, its completely dead... nothings coming on now....
Just putting it for charging for awhile now, lets see if something comes up.
Just noticed. Device manager (windows 10) does not detect anything, when i connect USB to laptop.. only the red light shows now.
Click to expand...
Click to collapse
And yeah i have given you a link so you can follow the tutorial as per the video it will be better if you follow that.
sk.shehbaz said:
And yeah i have given you a link so you can follow the tutorial as per the video it will be better if you follow that.
Click to expand...
Click to collapse
Thanks so much.
Yes i have pdanet installed.
in cmd prompt, it used to detect the devices also.
But now after flashing all orginal rom files, its now dead, i dont even have fastboot more now ?
Now, i cant even get into fastboot mode...
---------- Post added at 10:55 AM ---------- Previous post was at 10:32 AM ----------
hypermaster said:
Thanks so much.
Yes i have pdanet installed.
in cmd prompt, it used to detect the devices also.
But now after flashing all orginal rom files, its now dead, i dont even have fastboot more now ?
Now, i cant even get into fastboot mode...
Click to expand...
Click to collapse
I THINK I HAVE HARD BRICKED MY YUREKA - Theres no Fastboot also.
Now, i need someone who can Unbrick a hardbricked yureka with emmc memory card system
Anyone in Mumbai who can do this for me ?
hypermaster said:
Thanks so much.
Yes i have pdanet installed.
in cmd prompt, it used to detect the devices also.
But now after flashing all orginal rom files, its now dead, i dont even have fastboot more now ?
Now, i cant even get into fastboot mode...
---------- Post added at 10:55 AM ---------- Previous post was at 10:32 AM ----------
I THINK I HAVE HARD BRICKED MY YUREKA - Theres no Fastboot also.
Now, i need someone who can Unbrick a hardbricked yureka with emmc memory card system
Anyone in Mumbai who can do this for me ?
Click to expand...
Click to collapse
Message me in PM bro we will sort it out bdw m also Mumbaikar
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
teji007 said:
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
Click to expand...
Click to collapse
sudo fastboot -i 0x19d2 boot recovery.img
sudo command not recognized in windows
anish.mvj said:
sudo fastboot -i 0x19d2 boot recovery.img
Click to expand...
Click to collapse
Sir.
i tried this command also but windows didnt recognized sudo command.
Plz any other way?
teji007 said:
Sir.
i tried this command also but windows didnt recognized sudo command.
Plz any other way?
Click to expand...
Click to collapse
That is ubuntu command.
For windows run CMD as administrator and then run
fastboot -i 0x19d2 boot recovery.img
Thanks and a little more help
anish.mvj said:
That is ubuntu command.
For windows run CMD as administrator and then run
fastboot -i 0x19d2 boot recovery.img
Click to expand...
Click to collapse
Thank you very much
Sir i upgraded my nx529j to 6.0.1, is there anyway to root it or downgrade to 5.1.1?
teji007 said:
Thank you very much
Sir i upgraded my nx529j to 6.0.1, is there anyway to root it or downgrade to 5.1.1?
Click to expand...
Click to collapse
Yes its possible.
Rooting is absolutely not required.
Follow the steps below
1. Download the latest 1.40 firmware from nubia india website support page. [Direct Link]
2. Then open the zip file and extract the recovery.img to local folder. Transfer the zip as it is to SD card
3. Goto fastboot/bootloader and run following
Code:
fastboot -i 0x19d2 flash recovery recovery.img
4. Then select reboot to recovery from bootloader menu.
5. Select wipe all application
6. Then install the downloaded zip [i hope you have already know how to do that]
It will automatically reboot.
That's it you are done downgrading
Failed
anish.mvj said:
Yes its possible.
Rooting is absolutely not required.
Follow the steps below
1. Download the latest 1.40 firmware from nubia india website support page. [Direct Link]
2. Then open the zip file and extract the recovery.img to local folder. Transfer the zip as it is to SD card
3. Goto fastboot/bootloader and run following
Code:
fastboot -i 0x19d2 flash recovery recovery.img
4. Then select reboot to recovery from bootloader menu.
5. Select wipe all application
6. Then install the downloaded zip [i hope you have already know how to do that]
It will automatically reboot.
That's it you are done downgrading
Click to expand...
Click to collapse
It says wiping failed(please wipe again or do it after reboot) everytime.
and nothing is working even app wipe or data wipe, only cache wiped works and choose from phone storage is also n ot working and sd card is also being not dtetected.
even in TWRP
anish.mvj said:
Yes its possible.
Rooting is absolutely not required.
Follow the steps below
1. Download the latest 1.40 firmware from nubia india website support page. [Direct Link]
2. Then open the zip file and extract the recovery.img to local folder. Transfer the zip as it is to SD card
3. Goto fastboot/bootloader and run following
Code:
fastboot -i 0x19d2 flash recovery recovery.img
4. Then select reboot to recovery from bootloader menu.
5. Select wipe all application
6. Then install the downloaded zip [i hope you have already know how to do that]
It will automatically reboot.
That's it you are done downgrading
Click to expand...
Click to collapse
I insatlled TWRP recovery, even in that wiping is not working. is there any way to install custom roms without rooting.
i actully installed official 6.0.1 update from their official nubia site and installed it.
teji007 said:
I insatlled TWRP recovery, even in that wiping is not working. is there any way to install custom roms without rooting.
i actully installed official 6.0.1 update from their official nubia site and installed it.
Click to expand...
Click to collapse
Dude please be clear what you want to do? Stock rom or custom?
Custom
anish.mvj said:
Dude please be clear what you want to do? Stock rom or custom?
Click to expand...
Click to collapse
.
Sir i want custom Rom. and sir now i am bricked
teji007 said:
.
Sir i want custom Rom. and sir now i am bricked
Click to expand...
Click to collapse
what do you mean by your are bricked?
If you want custom rom
Goto TWRP wipe everything
if above fails then try out following
Option 1:
Goto Bootloader mode and from that menu goto emergency recovery. Try wiping from there if successful, flash a stock rom [Kitkat] and boot to system. After first boot goto settings and reset factory settings. Then goto TWRP and wipe, it will wipe for sure. then you can install any custom rom
Option 2:
Download the oldest firmware from the nubia site [1.37] and flash recovery from there [extract the recovery from zip and flash it in bootloader]. Then use
Code:
fastboot -i 0x19d2 boot TWRP.img
to boot to twrp, don't flash it. Then goto advanced and select adb sideload. swipe to start sideload. after that open the zip you downloaded and got to
Code:
/META-INF/com/google/android/
and open updater-script with any of the text file. Delete the first line and save. update the zip.
open cmd from that folder where zip is located. then type
Code:
adb sideload NX529J_Z69_EN_NSXPK1JD00K137.zip
and press enter. let it complete and then reboot. it should boot to factory firmware. Follow the same procedure to factory reset from settings menu then flash TWRP and flash custom rom
Use the above steps. If all fails then revert back.
Thanks going to try
anish.mvj said:
what do you mean by your are bricked?
If you want custom rom
Goto TWRP wipe everything
if above fails then try out following
Option 1:
Goto Bootloader mode and from that menu goto emergency recovery. Try wiping from there if successful, flash a stock rom [Kitkat] and boot to system. After first boot goto settings and reset factory settings. Then goto TWRP and wipe, it will wipe for sure. then you can install any custom rom
Option 2:
Download the oldest firmware from the nubia site [1.37] and flash recovery from there [extract the recovery from zip and flash it in bootloader]. Then use
Code:
fastboot -i 0x19d2 boot TWRP.img
to boot to twrp, don't flash it. Then goto advanced and select adb sideload. swipe to start sideload. after that open the zip you downloaded and got to
Code:
/META-INF/com/google/android/
and open updater-script with any of the text file. Delete the first line and save. update the zip.
open cmd from that folder where zip is located. then type
Code:
adb sideload NX529J_Z69_EN_NSXPK1JD00K137.zip
and press enter. let it complete and then reboot. it should boot to factory firmware. Follow the same procedure to factory reset from settings menu then flash TWRP and flash custom rom
Use the above steps. If all fails then revert back.
Click to expand...
Click to collapse
Thank you very much sir.
Can i contact you by any other means? whatsapp or any other
teji007 said:
Thank you very much sir.
Can i contact you by any other means? whatsapp or any other
Click to expand...
Click to collapse
Check your private message
adb sideload not working
anish.mvj said:
what do you mean by your are bricked?
If you want custom rom
Goto TWRP wipe everything
if above fails then try out following
Option 1:
Goto Bootloader mode and from that menu goto emergency recovery. Try wiping from there if successful, flash a stock rom [Kitkat] and boot to system. After first boot goto settings and reset factory settings. Then goto TWRP and wipe, it will wipe for sure. then you can install any custom rom
Option 2:
Download the oldest firmware from the nubia site [1.37] and flash recovery from there [extract the recovery from zip and flash it in bootloader]. Then use
Code:
fastboot -i 0x19d2 boot TWRP.img
to boot to twrp, don't flash it. Then goto advanced and select adb sideload. swipe to start sideload. after that open the zip you downloaded and got to
Code:
/META-INF/com/google/android/
and open updater-script with any of the text file. Delete the first line and save. update the zip.
open cmd from that folder where zip is located. then type
Code:
adb sideload NX529J_Z69_EN_NSXPK1JD00K137.zip
and press enter. let it complete and then reboot. it should boot to factory firmware. Follow the same procedure to factory reset from settings menu then flash TWRP and flash custom rom
Use the above steps. If all fails then revert back.
Click to expand...
Click to collapse
Sir, its been 5 mins its "starting ADB sideload feature" but nothing
adb sideload failed
anish.mvj said:
Check your private message
Click to expand...
Click to collapse
Sir ,
ADB sideload failed
teji007 said:
Sir ,
ADB sideload failed
Click to expand...
Click to collapse
Hi how did your device visible in fastboot devices?
I installed adb drivers and all but my device is not listed in fastboot devices..
It is being listed in adb devices but not on fastboot devices. Can you help me with this?
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
teji007 said:
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
Click to expand...
Click to collapse
Hi how did your device visible in fastboot devices?
I installed adb drivers and all but my device is not listed in fastboot devices..
It is being listed in adb devices but not on fastboot devices. Can you help me with this?
Maze has finally published the Alpha Stock-Rom.
Download Link: https://goo.gl/9kCJiv :fingers-crossed:
The system.img file is incorrectly downloaded as a system 002.img file. It must be renamed. And then copy it to the folder "3. Maze_Alpha_V05_20170816 Official ROM".
Thanks!
Hope anyone can root this phone.
Hi!
I am in need of a new phone, and this one looks quite good at the price.. But what do you think can i expect from custom ROM scene here for it? I am a Xiaomi Fan, and my Mi4 was and is one of the best supported phones still. Do you think there will be a subforum for this device, custom ROMs (preferreable Lineage OS, or other close to AOSP ROMs? OFC nobody can know now, i understand, but what tells your experience of other new phones from new companys? It has created quite a buzz, so i think there will be a demand for sure..
Just am 2 afraid to get a phone without good custom ROM. Never had an Android in last 5 years with stock ROM. Total nightmare for me now to have to go back.
Root + TWRP 3.2.1
3 Methods to root MAZE Alpha
Note: Method II is the most universal and must works with almost any official ROM
I- Method 1 : flashing modified Magisk boot.img
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v14
7. Voila
I have used this Magisk guide to create it
I used old manual guide :
Code:
adb shell "rm -rf /data/local/tmp/*"
adb push META-INF/com/google/android/update-binary common magisk_inject boot.img /data/local/tmp
adb shell "cd /data/local/tmp/magisk_inject; mv ../common/* .; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox"
adb pull /data/local/tmp/magisk_inject/new-boot.img
adb shell "rm -rf /data/local/tmp/*"
II- Method 2 : using TWRP and Magisk.zip (External SDCARD or USB OTG cable needed)
1. reboot int bootloader mode : adb reboot bootloader
2. unzip and flash the the attached TWRP recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3. In TWRP choose first "change language" then press the "cancel" button while asking you for decryption password for data
4. In your PC download the Magisk-v15.3.zip and put it in a USB key, or an SDCARD
5. Use an usb otg cable to connect the USB key to your phone running TWRP and install the Magisk-v14.zip from Usb-otg (or SDCARD)
6. bonus: do a complete backup of your phone : all partitions except cache and data to your Usb-otg (or SDCARD)
7. reboot and install the MagiskManager apk v14
III- Method 3 : using the phhusson modified boot image
1- flash the attached boot image, using fasboot (fastboot flash boot boot-super-bootimg-output-su-eng-r318.img) or SPFlashTools using the attached scatter, if you do not want to unlock your bootloader
2- reboot to Android then install from google play the phhsusson superuser
3- Voila
Important Notes:
1- In all case you can use SPFlashTools to flash boot image without unlocking bootloader.
2- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Some useful tips
1- manual install of busybox :
a- root you phone with method II if not already done
b- stay in TWRP (or boot TWRP as in method II) then in advance->sideload slide the slider to confirm and after cancel that (we will not sideloading any thing, just to activate adb)
c- unzip and copy the attached busybox : adb push busybox /external_sd/
d- mount the system partition with the TWRP mount button
e- copy the busybox binary to /system/xbin : adb shell --> cp /external_sd/busybox /system/xbin/
f- make executable busybox and create links (the point at the end is a part of the command) : cd /system/xbin/; chmod 755 busybox; ./busybox --install -s .
g- umount the system partition in TWRP and reboot
2- manually install the OTA update.zip :
a- Google and download those 3 tools BlockImageUpdate, simg2img and img2simg.
b- In a terminal of your Linux PC do :
Code:
simg2img system.img system.raw.img # convert the sparse image to a normal raw (ext4) image
BlockImageUpdate system.raw.img system.transfer.list system.new.dat system.patch.dat # patch the newly created raw image
img2simg system.raw.img system.img # convert the patched raw image to a flashable sparse image
- system.img: you old system image (from 20170816 official rom)
- system.transfer.list, system.new.dat and system.patch.dat : inside the OTA update.zip
c- After that the original system.img will be patched and you will have an updated system.img.
d- Flash this patched system.img and also all .bin and .img files inside the update.zip (just replace old ones in the original 20170816 rom by those) and you will have the new official rom
3- Using supersu as root manager :
The last update at this time of supersu zip (2.82 SR5) works well, even it cannot update the su binary.
Credits to Magisk Devs, Phhusson and Jemmini
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
If I root my phone with this method, will I get further OTA Updates from Maze?
Following to see where this goes.
Cheers
CrashCrash123 said:
If I root my phone with this method, will I get further OTA Updates from Maze?
Click to expand...
Click to collapse
Yes.
You will only lost the root.
If the new update have the same kernel, the same methode with the same boot image can be used to root it again, othewise, we can follow the Magisk guide to create a new one.
I have tried this method. But it only works until the reboot. Then the root access is gone again.
SomeOneX said:
I have tried this method. But it only works until the reboot. Then the root access is gone again.
Click to expand...
Click to collapse
The root is permanent.
If you lost it, perhaps the first time we unlock the bootloader, the phone do a reset, and we lost the root (I suppose).
Just re-flash the new boot again, and it will be permanent : fastboot flash boot new-boot.img
Hi . I have locked the OEM lock but I can not install it through fastboot (remote: not allowed in lock state)
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
alfymon22 said:
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
Click to expand...
Click to collapse
It seems (take with a pinch of salt) that VoLTE is supported, but then most sites that announce that also make mistakes on other specs, so...)
As for custom ROMs, so far the square root of bugger all, but the consumer phones are just filtering in, so give it time.
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
it worked, but i have cts fail on safetynet check. how you fixed this?
PrimateaEu said:
it worked, but i have cts fail on safetynet check. how you fixed this?
Click to expand...
Click to collapse
install the universal safety net fix
Hey guys, does this root method wipe the data partition?
KilljoyTDA said:
Hey guys, does this root method wipe the data partition?
Click to expand...
Click to collapse
The flash of the boot image does not wipe the data, but unlocking the bootloader reset the phone and wipe the data.
If you phone is already unlocked, you will not loss the data, otherwise do a backup before.
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
KilljoyTDA said:
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
Click to expand...
Click to collapse
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Thank you @dreambo for this method, but for me "fastboot flashing unlock" not work, "fastboot oem unlock" working for me, all ok
ps:excusez moi pour mon anglais
dreambo said:
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Click to expand...
Click to collapse
Well I failed to back up for some reason anyways, so since I had almost nothing vital on the internal memory, I rooted (sucessfully) and now I'm reinstalling/reconfiguring my apps. Thanks anyways
*Download all necessary files*
Magisk v15.0 or newest available
Download ElementalX kernel @ elementalx.org
Download latest Magisk Manager from official xda thread
Download TWRP for Moto G4 (Athene)
from twrp.me
Unlock bootloader (Go to Motorola's official site)
Check Unknown Sources in Android settings under security tab.
Download and install ADB & Fastboot on your PC
Boot into fastboot by holding down vol down and power.
Once you see Android robot with text at the bottom, on your computer in cmd type "fastboot boot TWRP image path" ex: fastboot boot D:/TWRPimages/twrp.athene.img
Once phone boots to TWRP, TWRP will ask to make modifications to system. Keep read only. (Note: if is asks to install, always say no.) Next go to backup, and make backup. (Just backup what is selected by default: system, data, and most importantly, boot.img) Note: make sure to tell it to backup to SD, and make sure the SD card is formatted as portable, not adoptable. Note: you might need mount the card under Mount tab first before being able to select it.
Next, go to mount, and uncheck "keep system read only", and swipe to allow modifications. Go to install, and flash ElementalX, and set it up in the following screen. As we already have the turbopower charger, you don't need to enable USB fast charging.
Wipe dalvik cache, and flash Magisk. Then, wipe dalvik again, and power off.
Boot into Android to make sure everything works. Install Magisk app if it didn't appear in your apps drawer from the .apk you downloaded earlier.
Hope this helps! Good luck!
Note: If you would like to flash TWRP instead, use "fastboot flash recovery TWRP.img" instead of fastboot boot.
Thank you for this tutorial! Is it required to install the ElementalX kernel?
Romano2K said:
Thank you for this tutorial! Is it required to install the ElementalX kernel?
Click to expand...
Click to collapse
It appears to be. I tried it without ElementalX first and got to the point of installing Magisk then rebooting before my G4 went to brick with the flashing light. Same behavior occurred when installed SuperSU. After installing ElementalX everything worked fine.
To supplement this guide, here are a few more links and notes of what I did.
Links
The December 2017 Nougat ROM from here
G4 compatible Shreps TWRP from here
Current Magisk here
ElementalX for G4 is here
If needed, install Platform Tools and Android File Transfer
Steps
Install the ROM using these commands (on Mac):
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
./fastboot flash logo logo.bin
./fastboot flash boot boot.img
./fastboot flash recovery ./twrp-3.1.1-athene_shreps.img
./fastboot flash dsp adspso.bin
./fastboot flash oem oem.img
./fastboot flash system system.img_sparsechunk.0
./fastboot flash system system.img_sparsechunk.1
./fastboot flash system system.img_sparsechunk.2
./fastboot flash system system.img_sparsechunk.3
./fastboot flash system system.img_sparsechunk.4
./fastboot flash system system.img_sparsechunk.5
./fastboot flash system system.img_sparsechunk.6
./fastboot flash system system.img_sparsechunk.7
./fastboot flash modem NON-HLOS.bin
./fastboot erase modemst1
./fastboot erase modemst2
./fastboot flash fsg fsg.mbn
./fastboot erase cache
./fastboot erase userdata
./fastboot erase customize
./fastboot erase clogo
Click to expand...
Click to collapse
After running commands, restart bootloader w/o rebooting
Go into recovery w/o rebooting
Reboot
After booting into the OS, turn on Developer Mode (tap About / Build Number 8 times)
Go to Developer Options and turn on OEM unlocking and USB debugging
Copy Magisk and ElementX kernel to / using Android File Transfer (if AFT doesn't connect select USB config, change to charging then back to MTP to enable file transfer)
Reboot into Recovery, then Install Magisk and ElementX from TWRP
Performed on an G4 XT-1625, resulted was a rooted Nougat.
@Sanras, I followed your instructions and they went great on a republic wireless xt1625, thank you! But your post just says to boot into twrp, which means if I ever want to use twrp I have to connect my computer. Is there a special way to flash twrp instead of just booting to it? Because I tried flashing twrp but the phone wouldn't boot afterward. So I had to flash the stock rom and redo everything. Let me know and thanks!
supermaxkato said:
@Sanras, I followed your instructions and they went great on a republic wireless xt1625, thank you! But your post just says to boot into twrp, which means if I ever want to use twrp I have to connect my computer. Is there a special way to flash twrp instead of just booting to it? Because I tried flashing twrp but the phone wouldn't boot afterward. So I had to flash the stock rom and redo everything. Let me know and thanks!
Click to expand...
Click to collapse
You should be able to flash TWRP. That's actually the most used method. I simply recommended booting and not flashing because it is easier to revert to stock for an update. However, you should be able to flash TWRP if you want with "fastboot flash recovery D:/TWRPimages/twrp.athene.img"
(Replace last part with image path on your computer)
Thanks Sanras,
Great guide, worked for me with no problems.
Anyone know how to approach security updates after rooting via this method?
Currently on Dec17 looking to update to Apr18 security patch just don't want to brick device.
Thanks in advance. :good:
Thanks. Sanras.
I got my phone bricked after restore my stock rom and try to install magisk to it. This solved my case also.
I just have to pay attention that just installing the kernel after try the magisk is not enough. Like you said:
* Install ElementalX kernel; wipe caches
* then install Magisk (again), and wipe caches again
Is this safe for Qualcomm variants like the Boost Mobile version?
chuman72486 said:
Is this safe for Qualcomm variants like the Boost Mobile version?
Click to expand...
Click to collapse
Yes, my own G4 is a Snapdragon 617 (unlocked US Variant) XT-1625
SD Card Configured Adoptable
Sanras said:
*Download all necessary files*
Magisk v15.0 or newest available
Download ElementalX kernel @ elementalx.org
Download latest Magisk Manager from official xda thread
Download TWRP for Moto G4 (Athene)
from twrp.me
Unlock bootloader (Go to Motorola's official site)
Check Unknown Sources in Android settings under security tab.
Download and install ADB & Fastboot on your PC
Boot into fastboot by holding down vol down and power.
Once you see Android robot with text at the bottom, on your computer in cmd type "fastboot boot TWRP image path" ex: fastboot boot D:/TWRPimages/twrp.athene.img
Once phone boots to TWRP, TWRP will ask to make modifications to system. Keep read only. (Note: if is asks to install, always say no.) Next go to backup, and make backup. (Just backup what is selected by default: system, data, and most importantly, boot.img) Note: make sure to tell it to backup to SD, and make sure the SD card is formatted as portable, not adoptable. Note: you might need mount the card under Mount tab first before being able to select it.
Next, go to mount, and uncheck "keep system read only", and swipe to allow modifications. Go to install, and flash ElementalX, and set it up in the following screen. As we already have the turbopower charger, you don't need to enable USB fast charging.
Wipe dalvik cache, and flash Magisk. Then, wipe dalvik again, and power off.
Boot into Android to make sure everything works. Install Magisk app if it didn't appear in your apps drawer from the .apk you downloaded earlier.
Hope this helps! Good luck!
Note: If you would like to flash TWRP instead, use "fastboot flash recovery TWRP.img" instead of fastboot boot.
Click to expand...
Click to collapse
My Moto G4 has an SD card formatted adoptable. Is there a work around in step 6 to accommodate an adoptable SD card?
Thanks
rwruck said:
My Moto G4 has an SD card formatted adoptable. Is there a work around in step 6 to accommodate an adoptable SD card?
Thanks
Click to expand...
Click to collapse
Sure. Instead of making a backup to the card, backup to internal storage. Then, before doing anything else, on your pc copy the files from the newly created TWRP folder on your internal storage. These are your backups. You can then proceed with the rest of the steps. Honestly, the backup isn't even necessary, it's just good to have in case something goes wrong.
Hi
I know it's a bit old now, but I'm unable to root my Nougat XT1641
I already have the whole stuff :
- BL unlocked ;
- TWRP installed ;
- all backups done.
But everytime I try to flash ElementalX/Magisk, it fails and ends in a bootloop.
Can someone have an advice to help me ?
Well, I used this : https://topjohnwu.github.io/Magisk/install.html#patching-images
Patching my boot.img did the trick !
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622
Download: https://dl.twrp.me/blueline/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
GitHub: https://github.com/topjohnwu/Magisk/releases
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
Was my misunderstanding. I thought you were implying people should go back to stock recovery to flash ota. You are talking about flashing ota in twrp. You might clear that up a little bit in that section.
Great post.
Unfortunately, if you are writing a process, then writing everything out is a requirement. Especially with item numbers or using an outline format. Not everyone understands shortcuts taken or abbreviated words, unless they are spelled out in the beginning. IMO, wrote and read too many processes. Including software requirement documentation.
Hi,
thanks for the thread :good:
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
Yes, I think so too.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
The boot.img is into "image.zip"
Then I suggest to flash into a and b (or both)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
or
fastboot flash boot --slot all boot.img
Edit
be careful here: Factory reset via ADB sideload (can also do this without wiping data)
bootloader is bootloader, boot is boot, bootloader.img isn't boot.img
so, maybe better to write:
fastboot flash bootloader nameofbootloader.img or if simply renamed fastboot flash bootloader bootloader.img
deleted, bug.
trouble flashing files
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
wangdaning said:
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
Click to expand...
Click to collapse
Thanks, but still no luck.
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
fyrmd said:
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
Click to expand...
Click to collapse
I always buy Anker cables and chargers. All have been good so far.
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
Are you able to get into recovery? If so, download the full ota to your pc and side load it with adb.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
i same issue
rczrider said:
[*]Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Click to expand...
Click to collapse
why not copy all files?
---------- Post added at 11:58 AM ---------- Previous post was at 11:55 AM ----------
fyrmd said:
Thanks, but still no luck.
Click to expand...
Click to collapse
boot to the twrp.img and flash the twrp.zip, unless you are on android 10 you should have no problem unless you are doing it wrong. not exactly hard to do.
How to enable oem unlock in this case?
pedro5148 said:
How to enable oem unlock in this case?
Click to expand...
Click to collapse
There are a few suggestions at https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
However, if the network carrier has locked the bootloader, you cannot unlock it. In the U.S., Verizon and AT&T phones generally cannot be unlocked due to locked bootloaders.