DISCLAIMER: I AM NOT RESPONSIBLE FOR WHAT MAY HAPPEN TO YOUR DEVICE, DO THIS AT YOUR OWN RISK.
Before I start: everything I'm going to post here, I learned from this thread: https://forum.xda-developers.com/maven-3/help/zte-maven-3-z835-root-t3705687/page9
VERSION OF MAGISK FLASHEAD v17.1 (Unfortunately no one has flashed version v18.1)
What we need (they will be in the links at the end):
-ZPST for AT&T (with this program we are going to flash the modified boot.img)
-Drivers: QDLoader, ZTE AndroidUSB and ZTE_V889F (in case the previous Zte driver does not work).
-Modified boot.img that are already flashed with Magisk, only the following versions are available:
-Z835V2.0.0B10
-Z835V2.0.0B12
-Z835V1.0.0B13
-Magisk Manager version compatible with v17.1
EVERYTHING YOU NEED IS IN A LINK AT THE END OF THE POST.
Let's get started.
I recommend to do a hard reset before starting, however, in one of my devices I did it having data and applications installed, if you have used kingroot or any other software in your phone, erase all trace of it so you do not have problems.
We download all the contents of the folder, install all drivers included, and the ZPST for AT&T.
Starting to flash:
WE NEED AT LEAST 50-60% of Battery
Turn off the phone and turn on pressing Vol Down + Power Button, the phone will start in FTM mode.
Open ZPST for AT&T and select version Z835
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING, remove the usim and sd card
Once inside the software we proceed to connect the cell phone.
1. You will see if the phone was recognized by the com port.
2. Download, this is where we will enter to download the firmware
3. You will see your information imei and so on.
This is how it will look once connected (Let's go to the download tab)
1. Let's select the firmware (it has to be the same as the cell phone otherwise it can corrupt the imei)
2. We chose where to keep a small log to check if everything went well.
3. HIT THE DOWNLOAD BUTTON!!!!!
WARNING: wait for the device to restart at least 2 or 3 times, one of them will be in FTM mode again, so do not panic, it will take a while in 3% or 5%.
When the phone starts normally, if you did a hard reset configure everything again, otherwise, we will proceed to install the magisk.
DO NOT INSERT THE SD CARD YET!
Magisk asks if I want to update to the latest version, press NO THANKS.
Proceed to uninstall
Now let's install the version of magisk manager we downloaded (com.topjohnwu.magisk_6.1.0-165_minAPI21(nodpi)_apkmirror.com.apk)
When the installation is finished we enter Magisk and this will ask us if we want to upgrade to the latest version, PRESS NO!
Now we will see that magisk is installed correctly.
We see that we can use all its functions.
We will proceed to verify if we have root access.
Download root checker
And Voila!
MEGA link: https://mega.nz/#F!ud8VwKRJ!-cJr7EJyhb1PkziNx5KvLQ
with this can you uninstall original system's apps such as device help, google apps? install recovery and titanium backup? I need to remove a lot of bloatware/default apps that is taking memory from the device
nvizync said:
Root
Click to expand...
Click to collapse
Nice work! This confirms that the bootloader is unlocked, which means we can then use just the firehose to flash these files. I will work on writing something up for that.
deadman96385 said:
Nice work! This confirms that the bootloader is unlocked, which means we can then use just the firehose to flash these files. I will work on writing something up for that.
Click to expand...
Click to collapse
Would love to see that, thanks for the reply! :good:
rickastillo said:
with this can you uninstall original system's apps such as device help, google apps? install recovery and titanium backup? I need to remove a lot of bloatware/default apps that is taking memory from the device
Click to expand...
Click to collapse
You can install titanium backup, twrp is not possible at this point, no one has done it yet, you can delete system apps through adb, using
Code:
adb shell pm uninstall -k --user 0 packagename
But i haven't figured out yet how to get rw permission on system/apps so i can delete system apk's.
@nvizync You should thank me for my boot.img mod of -Z835V2.0.0B10 (Magisk 17.1)
my boot.img mod of:
-Z835V1.0.0B13 (Magisk 18.1) Link: https://mega.nz/#F!88IiFapI!6Peah7woOOaIhusfYCAEcw
-Z835V2.0.0B10 (Magisk 18.1) link: https://mega.nz/#F!V4pAVIYQ!19tWE7_xk_aQtyiu050Y7A
-Z835V2.0.0B12 (Magisk 18.1) Link: https://mega.nz/#F!9lBVkQAZ!WqnRvYa4qcw5MgRxhp1hcA
Thanks for your detailed flash root tutorial
Alijosekt said:
@nvizync You should thank me for my boot.img mod of -Z835V2.0.0B10 (Magisk 17.1)
my boot.img mod of:
-Z835V2.0.0B10 (Magisk 18.1) link: https://mega.nz/#F!V4pAVIYQ!19tWE7_xk_aQtyiu050Y7A
-Z835V2.0.0B12 (Magisk 18.1) Link: https://mega.nz/#F!9lBVkQAZ!WqnRvYa4qcw5MgRxhp1hcA
Thanks for your detailed flash root guide
Click to expand...
Click to collapse
I totally forgot it, yeah, you deserve most of the credit, I linked the original thread, but I'm planning including all the credits.
@nvizync Look what I got! https://github.com/TwrpBuilderTests/android_device_zte_z835/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Alijosekt said:
@nvizync Look what I got! https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Click to expand...
Click to collapse
Ok my way
nvizync said:
Ok my way
Click to expand...
Click to collapse
not boot twrp
Alijosekt said:
not boot twrp
Click to expand...
Click to collapse
Did you tried it
Alijosekt said:
@nvizync Look what I got! https://github.com/TwrpBuilderTests/android_device_zte_z835/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-13
Some brave who flashes it?
Click to expand...
Click to collapse
I tried to flash it, but instead, I just got a bootloop, and I can't access the recovery mode anymore, I should flash the original recovery and see if it works.
nvizync said:
I tried to flash it, but instead, I just got a bootloop, and I can't access the recovery mode anymore, I should flash the original recovery and see if it works.
Click to expand...
Click to collapse
Done, i managed to enter in normal mode and use flashify to flash stock recovery.img.
Hi, I'm stuck at the first step. The ZPST download fails with the message that it can't find the file: sbl1.mbn Any thoughts?
penn462 said:
Hi, I'm stuck at the first step. The ZPST download fails with the message that it can't find the file: sbl1.mbn Any thoughts?
Click to expand...
Click to collapse
Are you using the custom boot.img listed in mega's folder?
nvizync said:
Are you using the custom boot.img listed in mega's folder?
Click to expand...
Click to collapse
Yes. I'm using the folder "Boot Mod Z835V1.0.0B13"
penn462 said:
Yes. I'm using the folder "Boot Mod Z835V1.0.0B13"
Click to expand...
Click to collapse
Thats odd, try this: download another folder B12 or B10, and just paste the B13 boot.img, maybe that could work, one of the devices i rooted was B13.
Well, I tried what you suggested, and now I get "download failed" and "failed to change mode before downloading firmware" It seems to be stuck in FTM. I guess it's bricked?
---------- Post added at 06:52 PM ---------- Previous post was at 06:48 PM ----------
Update: not bricked. Gonna try again.
penn462 said:
Well, I tried what you suggested, and now I get "download failed" and "failed to change mode before downloading firmware" It seems to be stuck in FTM. I guess it's bricked?
Click to expand...
Click to collapse
Fear not, that happened to me also, just keep in ftm and make a stock boot.img flash, provided in the mega folder. Paste the boot stock image inside the b13 folder
Placed stock boot.img into B13 folder in place of custom boot.img. The process failure point is now back to the missing sbl1.mbn problem. I can get the phone to start, however, so it's not bricked. Whew!
Related
ARE YOU SEARCHING TO ROOT YOUR REDMI 2 ?
DISCLAIMER:DO THIS ON YOUR OWN. I'M NOT RESPONSIBLE FOR ANYTHING HAPPENS TO YOU AND YOUR DEVICE.PLEASE DONOT MIRROR THE LINKS
CLICK HERE FOR NATIVE ROOT
IF YOU ARE GETTING STOCK RECOVERY EVEN AFTER FLASHIN CWM, SEE THIS POST
STEP 1- FLASHING CWM ON YOUR PHONE
1.At first, you'll need the "adb" and "fastboot" tools. Get them HERE
2.Extract them into a folder, let's name it "Redmi2" (You can give your own name to the folder. That doesn't matter here.)
3.Now get the CWM .img file from HERE
You can use Philz Touch recovery also. Get HERE
4.Rename cwm.img or philz.img you downloaded above and as "recovery.img" and place it in the Redmi2 folder.
Now the folder will look like this-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.Press and hold "shift" button and right click in the blank area of the folder and click on "open command promt window here". The command prompt will open.
6.Now turn off your Redmi2. Wait until it vibrates. After it's vibrated press and hold "Volume down and Power" keys together until it boots into "fastboot mode". Now connect the Redmi2 to your PC/Laptop through USB cable in fastboot mode itself.
7.Get to the command prompt now.
Now type: " fastboot devices " (without these- " " )
Like this-
8.Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command
9.Now enter the next command: " fastboot flash recovery recovery.img "
Like this-
10. Now this ends...
Type the last command: " fastboot reboot "
Like this-
11.Now your phone will reboot with ClockWorkMod(CWM) installed. CHEERS...
STEP 2- ROOTING YOUR PHONE
1. Firstly get the SuperSU.zip from HERE
2. Now copy the downloaded zip to your sdcard (not in any folder just in sdcard)
3. Boot into CWM recovery by turning off the phone and pressing "Volume UP and Power" button together after the phone vibrates.
4. Once CWM main menu is displayed, select "Install from zip" and browse to the zip that you downloaded earlier and select it.
5. Install the zip. If you get any warning, ignore and proceed.
6. After the installation is complete, reboot your device. (I think you can do that)
7. VOILA..!!! YOU ROOTED YOUR REDMI2
PLEASE HIT THANKS
JOIN OUR FACEBOOK GROUP HERE
CREDITS:
1. I don't claim any credit for "adb and fastboot tools" and the "recovery.img" and "SuperSu.zip"
2. Thanks to @subhrajiNath on Miui english forums who wrote the original guides.
Thread link is here and here
I cannot connect to device using adb on ubuntu.
Any Idea ?
I have opened a thread about this issue here
postadelmaga said:
I cannot connect to device using adb on ubuntu.
Any Idea ?
I have opened a thread about this issue here
Click to expand...
Click to collapse
I'm really sorry man..I've never used ubuntu But I wish to...
Join the FB group and ask there...Maybe it can be helpfull
? not flashing ?
noobpremium said:
I'm really sorry man..I've never used ubuntu But I wish to...
Join the FB group and ask there...Maybe it can be helpfull
Click to expand...
Click to collapse
Ok my fault, It looks I miss the notification MIUI that ask me to allow my pc to dev mode...
Now I have another issue:
After I flash the recovery with flashboot I reboot into recovery but I still have the default one ... not CWM any idea what could be wrong ?
( I have already did this procedure on another phone, same issue but after doing it a couple of time something make the difference )
postadelmaga said:
Ok my fault, It looks I miss the notification MIUI that ask me to allow my pc to dev mode...
Now I have another issue:
After I flash the recovery with flashboot I reboot into recovery but I still have the default one ... not CWM any idea what could be wrong ?
( I have already did this procedure on another phone, same issue but after doing it a couple of time something make the difference )
Click to expand...
Click to collapse
get "Flashify" app from playstore and first take backup of stock recovery and then flash the cwm with it. Thats it..
Actually I didn't knew this method before i made this guide..
Anyway, fastboot gives us a different feel, doesn't it? :v
wait I don't know flashify but it looks it needs root to flash the recovery ... but I think I need cwm to root ... so I think this is not gonna work ...
Ok got it, this may be useful to anybody face the issue with recovery:
I discovered you can workaround the issue in this way:
Temporary boot into CWM:
HTML:
fastboot boot recovery.img
Root the device using CWM
Flash CWM using flashify
[ CWM when you log out ask you for root so maybe it is not necessary to use the zip file ( but I'm not very expert so maybe I'm wrong)]
You can install GAPPS with CWM `gapps-kk-20140606-signed .zip` but be careful, whenever you update MIUI you will look all software installed using CWM. ( superSu and GAPPS for example )
thanks
thanks!
eienkisu said:
thanks!
Click to expand...
Click to collapse
Pleasure
Okay bro :good:
I'll update the OP
I confirm #postadelmaga the CWM recovery does not stay, the only way to do access it is the fastboot boot recovery.img Here's how I succeeded with two phones now.
power on, start wifi, do Miui updates
install ADB or the files above on PC
reboot to fastboot with voldown+pwr
now comes fastboot boot recovery.img
in CWM, sideload SuperSu and Gapps
connect you preferred VPN (if in China)
install and update all Google apps needed
delete most Chinese apps
hey i m unable to flash recovery plzz help
Device version 2014818
Sent from my 2014818
Hi buddy could you plz port touchwiz from galaxy prime?
The simpler solution is to use the xiaomi update tool and flash a developer rom that has builtin root.
http://xiaomi.eu/community/threads/5-4-10.27429/
howto & root from permissions menu:
https://watchpage.wordpress.com/201...redmi-note-4g-developers-roms-version-miui-6/
But to have the cwm running on the phone is always a safe bet for some recovery actions.
not working.
I tried this method. its stuck with flashing the recovery image. always showing flashing the recovery image.... that's all.
godwintgn said:
I tried this method. its stuck with flashing the recovery image. always showing flashing the recovery image.... that's all.
Click to expand...
Click to collapse
Are you on win7? I got this same issue on my win7... try on win8 it works flawlessly
Please hit thanks if done
Ya bro I am using Windows 7. I don't have Windows 8. Thanks for the info.
Shrihari007 said:
Hi buddy could you plz port touchwiz from galaxy prime?
Click to expand...
Click to collapse
TW sucks man.. why do you want it :/ anyways I'll try
leuk_he said:
The simpler solution is to use the xiaomi update tool and flash a developer rom that has builtin root.
http://xiaomi.eu/community/threads/5-4-10.27429/
howto & root from permissions menu:
https://watchpage.wordpress.com/201...redmi-note-4g-developers-roms-version-miui-6/
But to have the cwm running on the phone is always a safe bet for some recovery actions.
Click to expand...
Click to collapse
Thanks to you bro.. I'll update the OP for those who are facing some issues with my guide's precedure..
OP Updated
I've updated the OP with the other guide's link.. please check it out if you're having some issues with this one
godwintgn said:
Ya bro I am using Windows 7. I don't have Windows 8. Thanks for the info.
Click to expand...
Click to collapse
Try on some friend's PC or something
Halo all
Most owners here have rooted (kingroot) their system and attempted to update the rom, forgetting OTA conflicts. Although the consequences are usually resolvable, not in the case of mediatek and our model.
To start, I highly recommend using Ubuntu linux off a flash drive running live, else I suggest using windows 7 (perhaps in a vm too) although it didn't work with me (mediatek driver issues) (users reported that it works fine with windows 10, set wifi connection as metered to prevent automatic driver updates)
Optional: Create a live Ubuntu (download the 64bit version!) stick using this tut: http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
After booting into Ubuntu, remove modemmanager by typing in terminal : sudo apt-get remove modemmanager
Hit y and continue...
Download folder list:
1)spflashtool from http://spflashtool.com/, "Linux 64-bit"
2)CWM(626g+)
3)Scatter file(626g+)
4)Stock cwm backup ~800MB
Link to Download: me1ga.nz/#F!t1A1HJQJ (rename to "mega")
Decryption key:
Code:
!teT23YQ_1PH52USChW3k6g
Google drive mirror folder: https://drive.google.com/folder/d/0BwgllNFqdXuQMXR0a29mZms2VDA/edit
Skip 1,2,3 for Windows users
Flash time:
1)Extract the zip in Home directory, open Terminal again then cd SP_Flash_Tool_exe_Linux_v5.1520.00.100 (tip: type cd SP then hit tab to autocomplete)
2)then: chmod +x *
3) last: sudo ./flash_tool.sh
4)Choose the scatter file and recovery img downloaded like in the pic (checkboxes too):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5)Make sure your phone is off, click Download then plug in the phone using a USB2 port...
6)CWM installed!
7)extract the stock cwm backup zip to sdcard in this following order of directory: clockworkmod/backup/(the extracted contents here)
8)Reboot the phone by hold Vol Down + Power then leave it, due to the issue it will enter cwm automatically
9)navigate to "backup and restore" and choose restore then the folder your copied (in date format)
10)reboot, dun! :highfive:
Big Credits and thanks to: https://www.facebook.com/htc626gplusdev/info/?tab=page_info , for custom recovery...
Hit thanks if this has helped you, would motivate me to update the links lol
Hi, this is to install the cwm recovery... Right? But how do i flash my phone with an HTC stock rom? Because i don't have a back up to restore my phone. And htc already has a default recovery. Can't i use that to flash my phone with the stock rom file? Maybe via adb sideload?
diml0rd said:
Hi, this is to install the cwm recovery... Right? But how do i flash my phone with an HTC stock rom? Because i don't have a back up to restore my phone. And htc already has a default recovery. Can't i use that to flash my phone with the stock rom file? Maybe via adb sideload?
Click to expand...
Click to collapse
I think understanding the title of the thread would answer your question, no this is not "install the cwm recovery" it is required in order to restore stock ROM unofficially, there is no way around it to date, if you are afraid/don't trust the stock ROM backup I provided, then wait for HTC to release RUU and simply use fastboot to update (? mediatek)...
Follow the steps, I've provided everything, you don’t need a backup, download my backup etc...
tpr0 said:
I think understanding the title of the thread would answer your question, no this is not "install the cwm recovery" it is required in order to restore stock ROM unofficially, there is no way around it to date, if you are afraid/don't trust the stock ROM backup I provided, then wait for HTC to release RUU and simply use fastboot to update (? mediatek)...
Follow the steps, I've provided everything, you don’t need a backup, download my backup etc...
Click to expand...
Click to collapse
Sorry i though your link was an update to cwm, not the rom. Just saw the size of the file. Thanks i will try this. This is what I was looking for actually. Too bad i just deleted my arch Linux though ??
tpr0 said:
I think understanding the title of the thread would answer your question, no this is not "install the cwm recovery" it is required in order to restore stock ROM unofficially, there is no way around it to date, if you are afraid/don't trust the stock ROM backup I provided, then wait for HTC to release RUU and simply use fastboot to update (? mediatek)...
Follow the steps, I've provided everything, you don’t need a backup, download my backup etc...
Click to expand...
Click to collapse
can't download :
https://www.dropbox.com/sh/1oev7ymmh...mXInVs_va?dl=0
returns:
This account's public links are generating too much traffic and have been temporarily disabled!
diml0rd said:
can't download :
https://www.dropbox.com/sh/1oev7ymmh...mXInVs_va?dl=0
returns:
This account's public links are generating too much traffic and have been temporarily disabled!
Click to expand...
Click to collapse
Link updated
Hello, sorry, I have the same problem my phone is 626g, I do not know if this guide is, however, the link ww w.dropbox.com/s/drc102llim...atter.txt?dl=0 and the link:w.dropbox.com/s/wt0r1q8xqs...71609.img?dl=0[/url] not working.
Thank you there is nothing about this problem and service HTC wash their hands with this.
tpr0 said:
I think understanding the title of the thread would answer your question, no this is not "install the cwm recovery" it is required in order to restore stock ROM unofficially, there is no way around it to date, if you are afraid/don't trust the stock ROM backup I provided, then wait for HTC to release RUU and simply use fastboot to update (? mediatek)...
Follow the steps, I've provided everything, you don’t need a backup, download my backup etc...
Click to expand...
Click to collapse
sorry but the other two links are broken as well. i have the STOCK CWM.zip now
Hello again, I found the scatter file. But when you download and plug the USB, I get the following message.
PTM changed for ROM; it must be downloaded
Any help please? I read that this was solved by selecting all + download format rather than just download, but I have some fear in doing this.
Cheers
---------- Post added at 10:13 PM ---------- Previous post was at 09:53 PM ----------
Yes, unfortunately we need these files that are not found anywhere. They would be so kind as to re-upload?
Thank you
Cheers
I've been looking for 3 days and there is no way you're tpr0 alone gives a solution, could you please reupload the files? I am eternally grateful. Thank you very much Greetings.
reprono said:
I've been looking for 3 days and there is no way you're tpr0 alone gives a solution, could you please reupload the files? I am eternally grateful. Thank you very much Greetings.
Click to expand...
Click to collapse
Ch
Can you please be more specific about which file? Here's how it looks on my side : http://m.imgur.com/wKhtNtQ
I'll reupload to Google drive soon :good:
tpr0 said:
Hello, sorry for late, I'm also surprised why this solution isnt popular as many users faced the same issue
Can you please be more specific about which file? Here's how it looks on my side : http://m.imgur.com/wKhtNtQ
I'll reupload to Google drive soon :good:
Click to expand...
Click to collapse
please upload these files to your google drive folder:
2)CWM(626g+): https://www.dropbox.com/s/wt0r1q8xqs...71609.img?dl=0 (source and developer in the credits section)
3)Scatter file(626g+):https://www.dropbox.com/s/drc102llim...atter.txt?dl=0
---
just saw that you already did! :good: thanks
Any guidelines for people who are stuck with windows?
Thanks this worked but now my phone is being recognised as "HTC Desire 320" and every time I boot up it says incorrect CID
alvi.mahmud said:
Any guidelines for people who are stuck with windows?
Click to expand...
Click to collapse
You can use VirtualBox to boot linux, use ubuntu 14.04 iso as 'cdrom', install guest additions then follow the procedure. ill post a quick guide soon :good:
tpr0 said:
You can use VirtualBox to boot linux, use ubuntu 14.04 iso as 'cdrom', install guest additions then follow the procedure. ill post a quick guide soon :good:
Click to expand...
Click to collapse
Mine worked on Windows 10
ahmedshauq said:
Mine worked on Windows 10
Click to expand...
Click to collapse
It 'should' work on windows, though at certain settings Windows updates the driver with incorrect version. I recomended Linux to avoid problems with drivers
ahmedshauq said:
Thanks this worked but now my phone is being recognised as "HTC Desire 320" and every time I boot up it says incorrect CID
Click to expand...
Click to collapse
Anyone know a fix?
I just tried it with same result. But I also noticed that I can use only one sim now (SIM management in settings is gray) and language is mixed english with czech (my default).
Awaraine said:
I just tried it with same result. But I also noticed that I can use only one sim now (SIM management in settings is gray) and language is mixed english with czech (my default).
Click to expand...
Click to collapse
I can use both Sims though
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UNLOCK YOUR BOOTLOADER
WARNING: UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.
Prepare Your Moto G5S for Bootloader Unlock
Code:
Your device must be charged up to 70% before going completely through the process mentioned below.
These firmwares are only for the Moto G5S variant.
Make sure that you have installed proper device drivers on your computer.
INSTRUCTIONS:
Make sure to take a backup of your entire device data.
Download the Android SDK OR Download the Minimal ADB and Fastboot
Install the latest Motorola USB Drivers on your desktop. Download here.
Go To Settings -> Dev Settings, And Select "Allow OEM Unlock"
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
Open Command Prompt on androidsdk/platform-tools/ (Hold Shift and right click and press open command window here)
If you have downloaded Minimal ADB and Fastboot Go to C://Program Files/Minimal ADB and Fastboot and open Command Prompt from there.
Connect your Phone to PC
Type this in the CMD prompt window - fastboot oem get_unlock_data
You will get a return string. Copy it. [Right Click-Mark- Mark the text by pressing the shift key-Now press Ctrl+C]
Paste all the lines together in a notepad. Remove the empty spaces.
Now go to the Motorola Site.Sign in using your Google account or Motorola ID. Scroll down the page and paste the copied string in the field at step #6. Then click on ‘Can my device be unlocked?’, after which a "REQUEST UNLOCK KEY" button will appear at the bottom of page.
To get your unlock key, select the ‘I Agree’ option. Note: You will receive an email with your Unlock Key at the email address you used to log in there.
Important – Copy the 20-character key that Motorola sent you via email. Make sure your device is connected.
Then in CMD type: fastboot devices (To check your device is connected)
Then type: fastboot oem unlock UNIQUE_KEY
NOTE: In above command, replace the word ‘UNIQUE_KEY’ with the unlock code that you got via email. Then hit enter and the unlocking process should begin. Wait for a while and soon you’ll see ‘Bootloader Unlocked’ warning on your Moto G5S.
To relock the bootloader:
Go to Fastboot and give the command fastboot oem lock
TWRP by Squid2
See tutorial > [TWRP][montana] Squid TWRP 3.2.0-r1 for Moto G5S <
ROOT/MAGISK
Download the latest Magisk .zip file.
Install the MagiskMananger app on your smartphone.
For MagiskManager to work properly, you must use MagiskSU.
Place the archive (not unwrapping) in the root of the internal memory (or SD card) of the smartphone.
Restart on the twrp by SevenMaxs.
Select the .zip file and flash it.
Then restart your mobile.
Here you are rooted.
Install Busybox ( playstore ).
Other link :
Remove Unlocked Bootloader Message Moto G5S
CF-AUTOROOT Moto G5S
Merci !
How can I remove the bootloader warning? Can I flash a logo from g5 or g5 plus?
you can try this one, which is compatible with the G5S > https://forum.xda-developers.com/mo...ove-unlocked-bootloader-message-moto-t3672419
Thanks a lot. Will try soon I Will have finish to back up my phone with the twrp; For the moment, I just run it. I will flash it since the backup finish.
So, everything work fine. For those who want to Root their phone, no problem.
Now, just wait for custom roms.
patgou.007 said:
So, everything work fine. For those who want to Root their phone, no problem.
Now, just wait for custom roms.
Click to expand...
Click to collapse
thanks for your return.
Ok. Will try to find a solution.
patgou.007 said:
Ok. Will try to find a solution.
Click to expand...
Click to collapse
There is a solution. You need to install the alternative installer.
Members are reminded that discussing Warez, including Lucky P, is strictly forbidden on XDA.
Sorry
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
Anrei Titov said:
There is a solution. You need to install the alternative installer.
Click to expand...
Click to collapse
Which is?
---------- Post added at 07:10 PM ---------- Previous post was at 07:09 PM ----------
Anrei Titov said:
There is a solution. You need to install the alternative installer.
Click to expand...
Click to collapse
Which is?
patgou.007 said:
Which is?
Click to expand...
Click to collapse
On Google Play there is an alternative installer BusyBox.
Whish one? For the moment, I had uninstall magisk and flash stock firmware.
I have a phone unlocked
What I have to do for have a totaly root phone?
patgou.007 said:
I had uninstall magisk and flash stock firmware.
Click to expand...
Click to collapse
Why? I have installed Magisk.
Want to try again with a clean installation. But for thé moment, I can't flash twrp
I dont know why.
Was hard but it's finish. Take G5 method from xda for the root.
For busybox not complete, finish the installation with busybox application from playstore.
Now, everything work fine. I have complete Root.
patgou.007 said:
Was hard but it's finish. Take G5S method from xda for the root.
For busybox not complete, finish the installation with busybox application from playstore.
Now, everything work fine. I have complete Root.
Click to expand...
Click to collapse
Hi, did you use which method for the root?
Sorry, have make a mistake. This one.
https://forum.xda-developers.com/g5/how-to/how-to-root-moto-g5-t3579833
hello, here are some screenshot of squid2's recovery twrp
Thanks guys! squids TWRP works, just flashed it and rooted my G5s!
Now we just have to wait for LineageOS...
Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk.
Recommended to patch your own image read this
Grab the latest Platform Tools HERE
Code:
1. Download a stock Oxygen OS ROM Zip from [URL="https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156267635"]Here[/URL] Or the general section of XDA many users post links to the latest builds.
2. Download [URL="https://androidfilehost.com/?fid=818070582850510260"]payload_dumper-win64.zip[/URL] And extract/copy it to Desktop.
3. Extract your payload.bin from the stock rom zip and copy it into the payload_input folder.
4. Run the payload_dumper exe.
5. When it's finished open the payload_output folder and copy the boot.img to Desktop keep it there as a backup.
6. Copy the same boot.img to your internal storage on your phone.
7. Install the magisk manager APK from here: [URL="https://github.com/topjohnwu/Magisk"]Magisk Manager[/URL]
8. Open Magisk Manager choose install and select "Select and Patch a file" Or if you wish to use beta release go to settings > Update Channel and switch to beta and then back to Install "Select And Patch A File"
9. Navigate to where you copied your boot.img on the phone.
10. Once it's patched you'll have an magisk_patched.img on your phone in the the Downloads folder.
11. Copy that image to your fastboot folder on your PC and flash it with fastboot flash boot magisk_patched.img
Done!
As always I'm not responsible for any issues your device might have or if your cat sets on fire.
Credits:
topjohnwu for Magisk/Manger
geminids14 for payload_dumper-win64
Nice, that is what we need .. Thanks Liam
How can i load twrp? Fastboot boot command, didnt work
DevrimSeven60 said:
How can i load twrp? Fastboot boot command, didnt work
Click to expand...
Click to collapse
Ask in the TWRP thread
Not working for me get a error file is to large to download when try to flash
dajumper said:
Not working for me get a error file is to large to download when try to flash
Click to expand...
Click to collapse
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
liam_davenport said:
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Still the same
Im already rooted with bootimg having lat pie release. Is it possible to flash Android Q on top of last pie release and be rooted? Again I am rooted with magisk, not having twrp.
To update I always flash full updat from local, not reboot, install magisk to other slot and I was ready to go.
Will this work with Q update?
Not working for me. Both sims dissapear and phone keeps FC.
pister said:
Not working for me. Both sims dissapear and phone keeps FC.
Click to expand...
Click to collapse
Issue is on your end, I've flashed this multiple times no issue.
Working perfectly here I've clean flashed and redownloaded from the link and flashed. I've noticed sometime magisk causes sims to not show on boot before reboot the device and they should show again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I see that when I root, both IMEIs disappears. Very strange
Sent from my [device_name] using XDA-Developers Legacy app
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
pister said:
I see that when I root, both IMEIs disappears. Very strange
Click to expand...
Click to collapse
Mine both show. Not sure why yours have disappeared
liam_davenport said:
Mine both show. Not sure why yours have disappeared
Click to expand...
Click to collapse
Don't know. Tried to root by myself and the same happened
Sent from my [device_name] using XDA-Developers Legacy app
NateDev said:
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
Click to expand...
Click to collapse
If you have twrp already you don't need this I posted this for people that want root without using twrp, Just flash magisk 19.4 in twrp
There is a few guides in this forum section with all info you need on how to flash etc
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
mgear356 said:
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
Click to expand...
Click to collapse
You flashed it on Open beta 1?
liam_davenport said:
You flashed it on Open beta 1?
Click to expand...
Click to collapse
Yup open beta 1
Great thanks!
But can we update OTA to B2 with this?
@liam_davenport I'm sorry for the noob question, I just got my OP 7 Pro and never used one before, also, I've been away from everything root related for a long time.
Do I need to unlock the bootloader first in order to do this?
Hello,
I'm trying to patch my boot image without using Magisk App.(via PC) Is there any way to do this?
This is because everytime I do security update every month, I have to:
1. Download factory image
2. Unzip and get boot.img
3. Put boot.img in my phone
4. Patch boot.img with Magisk App
5. Move boot_patched.img to my pc and flash via fastboot
I find this very unefficient, and I want to automate 1~4 by just doing all the process in my PC.
Why wouldn't you install your update and before re-booting the phone go to the Magisk app and let it do the patching for you with "Direct Install" (or "Install to Inactive Slot" if you have device with dual partition)?
Andrologic said:
Why wouldn't you install your update and before re-booting the phone go to the Magisk app and let it do the patching for you with "Direct Install" (or "Install to Inactive Slot" if you have device with dual partition)?
Click to expand...
Click to collapse
@Andrologic This is because I root for VoLTE(Voice over LTE) patch and after that, I assume that I cannot update my phone via OTA. Long ago I tried updating with OTA and for as long as I remember it failed. Ever since that happened, I usually unroot first, do an update with either sideload or OTA or factory image(very often), root again with all the steps above, and so on..
If that's what you really need, just do what Magisk does. It's all on GitHub:
https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh
Didgeridoohan said:
If that's what you really need, just do what Magisk does. It's all on GitHub:
https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh
Click to expand...
Click to collapse
Ah, this was what I was looking for. Thank you.
@Didgeridoohan Do you happen to know where I can get the essential magiskinit and magiskboot binary?
From magisk v22.0 I see that magisk core and magisk manager got merged into one, and now I can't find the latest executable. (x86 too)
They're in the /lib/x86 and folder inside the .apk. If I remember correctly it should just be a matter of renaming them to magiskinit and magiskboot respectively.
Didgeridoohan said:
They're in the /lib/x86 and folder inside the .apk. If I remember correctly it should just be a matter of renaming them to magiskinit and magiskboot respectively.
Click to expand...
Click to collapse
You are talking about these "lib<binaryname>.so" files right?
Yup
Didgeridoohan said:
Yup
Click to expand...
Click to collapse
Thank you for the answer. I really appreciate it.
After update, make a boot.img backup via twrp (copy in twrp folder and rename to boot.img) patch via Magisk and flash new patched boot.img.
Os. I do not like a new method too.
Thank you guys, with these ideas I have been able to write a bash script to automate the whole process of downloading the latest build of lineageos, patch it on the phone using magisk (using adb shell), and flash it in fastboot mode, without needing any user intervention whatsoever.
Sathors said:
Thank you guys, with these ideas I have been able to write a bash script to automate the whole process of downloading the latest build of lineageos, patch it on the phone using magisk (using adb shell), and flash it in fastboot mode, without needing any user intervention whatsoever.
Click to expand...
Click to collapse
Can you share your script?
Hey @eyal1izhaki , sorry for the late reply.
You can find the script I am using here: https://github.com/NicolasWebDev/reinstall-magisk-on-lineageos
If you find any problem or have a suggestion, please tell me!
Oh nice, I tried to run boot_patch.sh on my Ubuntu, didn't go well.. I'll try to run it on my samsung phone as you did.
In not running lineageos but it should be the same process.
Thanks for the script
eyal1izhaki said:
Oh nice, I tried to run boot_patch.sh on my Ubuntu, didn't go well.. I'll try to run it on my samsung phone as you did.
In not running lineageos but it should be the same process.
Thanks for the script
Click to expand...
Click to collapse
https://github.com/Taewan-P/crosshatch-magisk-generator
This is my automation script FYI.
It's mostly close to an automation workflow though...
Also, you should not use the x86 binaries to patch a boot img of an aarch64 device. Flashing the mispatched img will make you boot loop the device.
i have a big dum dum poopy brain i dont know how to do anything will one of you big brain gentlemen please tell me how to patch the boot.img file with the script you guys are talking about and which app do i use and where do i use it and how do i use it. i can't use magisk because it gets stuck on the splash screen with the logo so i'm trying to patch the boot.img file without it. also will it be a problem that the boot.img file has .lz4 at the end (boot.img.lz4). aight thanks im gonna try elongating my neck by tying it to a fan with a rope.
Hi. I am sorry for bumping this thread but I am finding a solution for patching multi-model boot to add Magisk root without a phone.
Will this be possible?
I read the @Sathors script but he pushes the boot file to the android system to patch it. Can this step work on any phone or must on the exact model of the boot.img
Hi @Tungtata . If you look at the boot_patch.sh script in Magisk (https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh), in the header it says the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it seems that to work it needs the corresponding binaries, scripts and files. Maybe you can find all of these files in the Magisk repo, maybe not, in my case it seemed too much hassle to try and find out, knowing that it is working when done on the phone.
But if you really need to do that, then here is a path you can follow.
As for needing the exact phone model to patch the boot image, I don't think so because the script in itself is generic, but it depends on the other files it requires. Anyway, doing a real-life test should be quick.