Related
hi,
My phone is soft bricked and stuck at boot logo. I am trying to flash stock recovery/kdz file using flash tool but getting stuck at"low battery" error.
Could you please help how i can bypass this error? I have spend a lot of time online and tried few methods but always getting stuck at this error. I dont have any alternative phone and this is really disappointing.
I am using E988 India model.
CLICK HERE MATE. LET ME KNOW IF IT HELPS. IF NOT USE THE INSTRUCTIONS BELOW
I'm using same phone and have the same problem. I still can't flash stock with the tool but I can tell you how to get out of soft brick. Download madmacks e980 lokified TWRP recovery and also CM 11 latest version. Get in to recovery mode and go to install file (sideload) and flash the recovery first then reboot in to recovery again and sideload CM 11. When I get a definitive solution to flash stock I will let you know mate. If you have problems or don't know what I'm talking about then reply here. You well need adb installed on computer and open a new command window by holding shift and click right noise button at the same time. Make sure you perform this from the same directory as where there files are that your flashing. Once your phone prompts you to sideload type in to the command window adb sideload (the exact file name of the file you want to flash.zip) but without the brackets
uppon2 said:
CLICK HERE MATE. LET ME KNOW IF IT HELPS. IF NOT USE THE INSTRUCTIONS BELOW
I'm using same phone and have the same problem. I still can't flash stock with the tool but I can tell you how to get out of soft brick. Download madmacks e980 lokified TWRP recovery and also CM 11 latest version. Get in to recovery mode and go to install file (sideload) and flash the recovery first then reboot in to recovery again and sideload CM 11. When I get a definitive solution to flash stock I will let you know mate. If you have problems or don't know what I'm talking about then reply here. You well need adb installed on computer and open a new command window by holding shift and click right noise button at the same time. Make sure you perform this from the same directory as where there files are that your flashing. Once your phone prompts you to sideload type in to the command window adb sideload (the exact file name of the file you want to flash.zip) but without the brackets
Click to expand...
Click to collapse
Thank you very much for this help. I have never tried adb. Probably I shall now learn it and then try to do as you suggested. I am not particular about stock ROM. In fact I will be happy if there is stable cm ROM for this phone.
I juts bought this phone two days back. There are too many model numbers n am little scared now about choosing the right ROM. Do you mind sharing link for correct cm11 ROM please?,
Thanks again for your help!
Sent from my GT-I9500 using xda app-developers app
Currently i want to install lineage os 14.1 on my zenfone 2 deluxe (Z00A)unnoficial cyanogenmod 13
The problem is getting the marshmallow bootloader is impossible
every time i go to the bootloader menu it states:unlock fail reboot in 5 seconds. or something like that i do not know how to fix it as i cannot use asus's app to unlock it because i'm using cm13 and i cannot flash original stock because the official twrp doesn't install and leaves me in a bootloop and i can't flash anything with cyanogen recovery and you know if fact i have more problems but if i can just successfully have the bootloader menu up for enough time to install the new bootloader and so i can install Lineage OS on my zenfone
Please excuse my English, thank you.
Sent from my ASUS_Z00AD using Tapatalk
rommeney said:
Currently i want to install lineage os 14.1 on my zenfone 2 deluxe (Z00A)unnoficial cyanogenmod 13
The problem is getting the marshmallow bootloader is impossible
every time i go to the bootloader menu it states:unlock fail reboot in 5 seconds. or something like that i do not know how to fix it as i cannot use asus's app to unlock it because i'm using cm13 and i cannot flash original stock because the official twrp doesn't install and leaves me in a bootloop and i can't flash anything with cyanogen recovery and you know if fact i have more problems but if i can just successfully have the bootloader menu up for enough time to install the new bootloader and so i can install Lineage OS on my zenfone
Please excuse my English, thank you.
Click to expand...
Click to collapse
what you are stating is unclear. any ways, flash stock raw firmware with commands. and then use unlock app to unlock bl and install twrp.
if you are unable to go to bootloader. try to dd bootloader image in /dev/block/mmcblk0p3 from adb shell
sukhwant717 said:
what you are stating is unclear. any ways, flash stock raw firmware with commands. and then use unlock app to unlock bl and install twrp.
if you are unable to go to bootloader. try to dd bootloader image in /dev/block/mmcblk0p3 from adb shell
Click to expand...
Click to collapse
and how do i do that?
rommeney said:
and how do i do that?
Click to expand...
Click to collapse
first clear few things.
1. are you able to go to fastboot mode with volume plus and power button?
2. are you on twrp recovery? if yes which version?
3. are you on lolipop version?
4. are you root?
5. are you able to go to recovery mode?
sukhwant717 said:
first clear few things.
1. are you able to go to fastboot mode with volume plus and power button?
2. are you on twrp recovery? if yes which version?
3. are you on lolipop version?
4. are you root?
5. are you able to go to recovery mode?
Click to expand...
Click to collapse
i can go to fastboot but it throws this error:"unlock fail reboot in 5 seconds"
no my recovery is the cyanogen recovery
no as i stated i am on cm13 unnoficial
yes i am root as indicated by my developer settings that enables root through adb and application
yes i can go to recovery but only the cyanogen one as installing twrp gives a bootloop
rommeney said:
i can go to fastboot but it throws this error:"unlock fail reboot in 5 seconds"
no my recovery is the cyanogen recovery
no as i stated i am on cm13 unnoficial
yes i am root as indicated by my developer settings that enables root through adb and application
yes i can go to recovery but only the cyanogen one as installing twrp gives a bootloop
Click to expand...
Click to collapse
download the following files
https://drive.google.com/open?id=0B72QQTXqZSRwdE1iNEFwa3pQLXc
https://drive.google.com/open?id=0B72QQTXqZSRwSG0waUhpdHpzVmc
place both files on internal storage ( /sdcard/)
now in terminal run command dd if=/sdcard/droidboot_sign.bin of=/dev/block/mmcblk0p3 (ofc after su i mean root permision)
now reboot device, after reboot try to go to fastboot if still same. again in terminal
dd if=/sdcard/boot_sign.bin of=/dev/block/mmcblk0p1 reboot and after that try to go to boot loader.
one more thing did you tried to unlock the bootloader with some unofficial tool from xda?
sukhwant717 said:
download the following files
https://drive.google.com/open?id=0B72QQTXqZSRwdE1iNEFwa3pQLXc
https://drive.google.com/open?id=0B72QQTXqZSRwSG0waUhpdHpzVmc
place both files on internal storage ( /sdcard/)
now in terminal run command dd if=/sdcard/droidboot_sign.bin of=/dev/block/mmcblk0p3 (ofc after su i mean root permision)
now reboot device, after reboot try to go to fastboot if still same. again in terminal
dd if=/sdcard/boot_sign.bin of=/dev/block/mmcblk0p1 reboot and after that try to go to boot loader.
one more thing did you tried to unlock the bootloader with some unofficial tool from xda?
Click to expand...
Click to collapse
i did that like a year ago i think i used the official unlock app so no
Dude u ****ed up my phone
i tried the second command and my phone is just stuck in a ****ing bootloop
rommeney said:
i tried the second command and my phone is just stuck in a ****ing bootloop
Click to expand...
Click to collapse
Don't be rude. Try to Google for phrases like "zenfone 2 bootloop". Website like Asus Zentalk is generally trustworthy.
rommeney said:
i tried the second command and my phone is just stuck in a ****ing bootloop
Click to expand...
Click to collapse
are you able to stay in bootloader now? with volume plus?
sukhwant717 said:
are you able to stay in bootloader now? with volume plus?
Click to expand...
Click to collapse
yes
and i apologize i flashed my phone with lienage os but when i update now it just boots into twrp
Hi Friends
pleas help , i wanted install Oreo so i went to lock boat-loader by TOOL_ALL_IN_ONE
and i didnt see the alert message and above message appeared "Your device is corrupt. It can't be trusted and will not boot"
so please advise
If you alter the system in any way you can't lock the bootloader as it will not boot due to possible safety issues by modying the system. In order to use the device with a locked bootloader, you need to flash the original OS.
If you want to use a modified system, keep the bootloader unlocked. Unfortunately, there is no other way.
how can i flash rom please help
MsuatafaKhatab said:
how can i flash rom please help
Click to expand...
Click to collapse
It would be helpful to know what you want to flash.
Is it OxygenOS?
Then flash it in e.g. TWRP and then lock the bootloader again.
Is it something else?
Keep the bootloader unlocked.
Macusercom said:
It would be helpful to know what you want to flash.
Is it OxygenOS?
Then flash it in e.g. TWRP and then lock the bootloader again.
Is it something else?
Keep the bootloader unlocked.
Click to expand...
Click to collapse
Is it OxygenOS?
yes it is
Did you modify it in any way? Root, Magisk, Xposed, Recovery, flashable ZIPs or anything else?
yes, the problem i used tool "TOOL_ALL_IN_ONE" to lock boat-loader
Use "fastboot flashing unlock" to unlock it again, install TWRP, use adb push to copy OxygenOS to it, flash OxygenOS, use "fastboot flashing lock" and it should work just fine again.
not allow to me to unlock again
https://imgur.com/a/fIYqZ
I assume this is due to "Allow OEM Unlock" not being enabled. I don't know if anyone has a workaround.
Otherwise, I suggest contacting OnePlus and getting support by an L2 technician.
Macusercom said:
I assume this is due to "Allow OEM Unlock" not being enabled. I don't know if anyone has a workaround.
Otherwise, I suggest contacting OnePlus and getting support by an L2 technician.
Click to expand...
Click to collapse
Thanks pro
I contacted them and they gave file to downlod and will log in to my pc tommorrow to fix
Really appreciate your help
Sent from my LG-H870S using Tapatalk
MsuatafaKhatab said:
Thanks pro
I contacted them and they gave file to downlod and will log in to my pc tommorrow to fix
Really appreciate your help
Sent from my LG-H870S using Tapatalk
Click to expand...
Click to collapse
thanks pro , the session finished with succeed thanks
but why the delete the files after finish installation
MsuatafaKhatab said:
thanks pro , the session finished with succeed thanks
but why the delete the files after finish installation
Click to expand...
Click to collapse
They keep their tools private. So unless you back them up during the session in the background and use a keylogger to get the password, you will never get your hands on the tools. No one does.
But you can contact them again at any time and they will assist you so just don't do this again and you should be fine
this could be avoided if we had fastboot images of OxygenOS..
you can flash any image from fastboot, even if it's locked.
Seven_of_Nine24 said:
this could be avoided if we had fastboot images of OxygenOS..
you can flash any image from fastboot, even if it's locked.
Click to expand...
Click to collapse
How bro
I already fixed by one plus technical support , but to learn
Sent from my ONEPLUS A5010 using Tapatalk
I didn't do anything in my phone n still I got the device is corrupt.
Tejesh.D said:
I didn't do anything in my phone n still I got the device is corrupt.
Click to expand...
Click to collapse
Open ticket in one plus website
They will fix by logging to your PC
Don't worry
They are very friendly
Sent from my ONEPLUS A5010 using Tapatalk
MsuatafaKhatab said:
Open ticket in one plus website
They will fix by logging to your PC
Don't worry
They are very friendly
Click to expand...
Click to collapse
It's working now....but still ll open a ticket
I also faced similar problem yesterday & following steps worked for me
1. I unlocked the bootloader
2. Flashed TWRP & wiped everything (system data cache, internal) I wiped internal because I was seeing random folders in my internal, you can skip it while trying first time but if it doesn't work. Try again with wiping internal.
3.I flashed stock recovery via fastboot.
4. ADB side loaded oxygen OS (any version) using stock recovery.
I side loaded rom because I was unable to select file from stock recovery option "install from internal"
*don't boot now*
5. Reset everything from stock recovery option and then boot it.
I haven't tried to lock bootloader again but it should lock if you try now without rooting it again (⅛)
(⅛) I think the problem was that I mistakenly tried to lock bootloader with magisk installed which made this issue.
(That's what I was able to notice)
Please report back if this was the case for you too.
Sent from my ONEPLUS A5010 using Tapatalk
Try this
https://r.tapatalk.com/shareLink?ur...share_tid=3733012&share_fid=3793&share_type=t
Sumanyu Sinha said:
I also faced similar problem yesterday & following steps worked for me
1. I unlocked the bootloader
2. Flashed TWRP & wiped everything (system data cache, internal) I wiped internal because I was seeing random folders in my internal, you can skip it while trying first time but if it doesn't work. Try again with wiping internal.
3.I flashed stock recovery via fastboot.
4. ADB side loaded oxygen OS (any version) using stock recovery.
I side loaded rom because I was unable to select file from stock recovery option "install from internal"
*don't boot now*
5. Reset everything from stock recovery option and then boot it.
I haven't tried to lock bootloader again but it should lock if you try now without rooting it again (⅛)
(⅛) I think the problem was that I mistakenly tried to lock bootloader with magisk installed which made this issue.
(That's what I was able to notice)
Please report back if this was the case for you too.
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Sent from my ONEPLUS A5010 using Tapatalk
Hi guys, sorry if posting another thread about this problem, but I haven't found anything useful for my case. The problem is I can't boot in recovery. I flash the TWRP img (latest version but I also tried with others) and the process goes without problems, then I DON'T reboot the system or even power off the phone, I directly send the command via command line (adb-fastboot) or via phone to go to the recovery. It seems to work at first look, but before the recovery starts the phone reboot and goes in OS. Now, could the problem be related to the BLOD bug of this devices? I applied the 4core fix for my OS version (January security patch) but I also seen that on the XDA thread they uploaded the 4core version recovery img so maybe the problem is due to this bug which prevent me from enter in the recovery, probably I'm just saying a bunch of stupid things.
Last information: the only way I managed to enter in TWRP recovery was by doing this on fastboot:
fastboot flash recovery recovery.img
fastboot boot recovery.img
But now even this method won't work.
Thanks in advance.
RegularSam said:
Hi guys, sorry if posting another thread about this problem, but I haven't found anything useful for my case. The problem is I can't boot in recovery. I flash the TWRP img (latest version but I also tried with others) and the process goes without problems, then I DON'T reboot the system or even power off the phone, I directly send the command via command line (adb-fastboot) or via phone to go to the recovery. It seems to work at first look, but before the recovery starts the phone reboot and goes in OS. Now, could the problem be related to the BLOD bug of this devices? I applied the 4core fix for my OS version (January security patch) but I also seen that on the XDA thread they uploaded the 4core version recovery img so maybe the problem is due to this bug which prevent me from enter in the recovery, probably I'm just saying a bunch of stupid things.
Last information: the only way I managed to enter in TWRP recovery was by doing this on fastboot:
fastboot flash recovery recovery.img
fastboot boot recovery.img
But now even this method won't work.
Thanks in advance.
Click to expand...
Click to collapse
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hmm, wait, maybe I didn't catch what you were sayin, with "try to look your bootloader" you meant "try to LOCK your bootloader" right?
Because yesterday I've made root with Magisk, if I try to lock the bootloader I risk to brick the phone, isn't it true? Thanks anyway for your reply.
jd1639 said:
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I found the trick. I applied from fastboot the two commands that I mentioned:
fastboot flash recovery recovery.img
fastboot boot recovery.img
Only difference? I didn't run the Command Prompt as administartor, as I did yesterday (I also tried before this operations using PowerShell without success), WOW. Now before reboot the phone I allowed the modification to the partition in TWRP recovery, I saved logs from kernel and recovery and I'm trying to make a backup. I will tell you the results.
Yesterday I've also tried to flash the recovery by using Flashify without success, just sayin.
EDIT:
After rebooting the stock recovery returned. I hate this thing. I've also renamed this two files:
recovery-from-boot-p
install-recovery.sh
It didn't work.
jd1639 said:
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Click to expand...
Click to collapse
Any thoughts? Sorry if I ask but this problem is stopping me from go further with modifications on my device, I would like to install the ElementalX kernel.
RegularSam said:
Any thoughts? Sorry if I ask but this problem is stopping me from go further with modifications on my device, I would like to install the ElementalX kernel.[/QUOTE
From the bootloader boot recovery (twrp), fastboot boot twrp.img. Then flash supersu in twrp. Then boot back into the bootloader and flash twrp, fastboot flash recovery twrp.img. Twrp should stick then. Note: twrp.img is the full name of the twrp image file you're using.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Or, as you are already rooted, you could just try flashing TWRP from the official TWRP app. That should make it stick.
EDIT: Just noticed that you've already tried with Flashify. You could still try with the official app but if that doesn't work, do what jd1639 said.
CazeW said:
Or, as you are already rooted, you could just try flashing TWRP from the official TWRP app. That should make it stick.
EDIT: Just noticed that you've already tried with Flashify. You could still try with the official app but if that doesn't work, do what jd1639 said.
Click to expand...
Click to collapse
I've already tried with the official app and unfortunately I had no success. Anyway, as I said before, by locking again the bootloader couldn't occur a bootloop due to the root?
RegularSam said:
I've already tried with the official app and unfortunately I had no success. Anyway, as I said before, by locking again the bootloader couldn't occur a bootloop due to the root?
Click to expand...
Click to collapse
Locking the bootloader will not cause a boot loop if you're rooted. The reason I asked what happens when you lock the bootloader is that the 5x had had issues with the emmc going bad. A sure sign of that is the bootloader not staying locked after locking it and booting back up.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
RegularSam said:
Any thoughts? Sorry if I ask but this problem is stopping me from go further with modifications on my device, I would like to install the ElementalX kernel.[/QUOTE
From the bootloader boot recovery (twrp), fastboot boot twrp.img. Then flash supersu in twrp. Then boot back into the bootloader and flash twrp, fastboot flash recovery twrp.img. Twrp should stick then. Note: twrp.img is the full name of the twrp image file you're using.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Seriously, this thing is driving me crazy. Tried to go with your suggestions but I can't boot in the recovery, no way. I have also flashed the original recovery and the tried to get in with fastboot boot twrp.img, no success. I can't figure out why I have this problem.
EDIT: great, now even flashing the stock recovery doesn't work, the phone reboot every time I try to get in any recovery. I have no words.
EDIT 2:
GUYS, I think I've found the solution. As I said in the main post, I was thinking that maybe the problem was due to the BLOD bug, in fact the common twrp.img that you can find on the twrp page uses all the 6 cores of the Nexus 5X causing the rebooting which I mentioned. Now, I found this version of twrp 3.1.1 which is modified to use 4Cores, thanks to the user XCnathan32 and his thread about BLOD bug: https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199.
Now it seems like the TWRP Recovery is stick to the phone and I'm really happy to say that. Thanks for all your support, you were very patient!
Click to expand...
Click to collapse
QUICK STEPS TO ROOT MOTOROLA MOTO G STYLUS USING MAGISK
Just Remember*I just want to warn you that, Rooting will void the warranty of your smartphone
Rooting will block the OTA updates
1.First of all, please download and extract the ROM on your computer.
https://r.tapatalk.com/shareLink/to...1&share_fid=3793&share_type=t&link_source=app
2:*Now, connect your moto g stylus with a micro USB cable, and copy only the boot.img file from the extracted folder to your Motorola moto g stylus device storage/memory.
3:*Now you need to Launch Magisk Manager.
4:*After that, you will see a popup window that will ask you to install Magisk.
5:*Finally please select INSTALL and choose to install it again.
6:*Now Please press on “Patch Boot Image File
7:*Navigate to internal storage and select your phone’s boot image that you transferred earlier.
8:*Wait for a couple of seconds. Magisk will start patching the boot image.
9:*Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the same extracted ROM folder on your PC.
10:*Now you can follow the second step to flash the patched boot image file.
Next, you need to enter the following commands step by step:
First of all, you need to Flash the “patched_boot.img” to install Magisk and root your Motorola moto g stylus: fastboot flash boot patched_boot.img
You can also use the devices with A/B partition system, with the following commands:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
After that, you need to replace [patched_boot.img] with the same boot image file that you have already downloaded with the .img.
Now you will see the flashing process have has started. Now, run fastboot and reboot
HOW TO VERIFY IF YOUR MOTOROLA MOTO G STYLUS HAS A SYSTEMLESS ROOT?
Download and install the Magisk Manager app APK, and launch it.
If you want to verify that you have a systemless root, check the top of the screen and if you see all options with Green Tick which means you have successfully rooted and bypassed SafetyNet.
Sent from my moto g stylus using Tapatalk
surprised to see no comments on this topic. I am thinking of getting this phone but only if there is a root method for it.
It definitely works for the metro by TMobile version.
himesh82 said:
surprised to see no comments on this topic. I am thinking of getting this phone but only if there is a root method for it.
Click to expand...
Click to collapse
I got root by using magisk to patch the boot image. I purchased the phone directly from Motorola's website. If you get a version where the bootloader can be unlocked (some carrier versions apparently cannot be unlocked) you can root without much trouble.
dafunk60 said:
I got root by using magisk to patch the boot image. I purchased the phone directly from Motorola's website. If you get a version where the bootloader can be unlocked (some carrier versions apparently cannot be unlocked) you can root without much trouble.
Click to expand...
Click to collapse
I am based in Uk and will order from their website.
How easy it is to use as It has been afew years i tried rooting and will need a super easy guide.
himesh82 said:
I am based in Uk and will order from their website.
How easy it is to use as It has been afew years i tried rooting and will need a super easy guide.
Click to expand...
Click to collapse
I found it to be super easy using magisk, provided you have a PC to flash the patched boot.img to the phone via fastboot. I use the Lenovo Rescue & Smart Assist software on the PC to download the ROM from Motorola. You need to ensure the ROM you're downloading is the same version running on your phone. Using a boot.img from a different version will cause issues.
1. Copy the boot.img to the phone.
2. On the phone, patch the boot.img you just copied over with Magisk Manager.
3. Copy the patched magisk_patched.img back to your PC.
4. Connect to the phone via adb. (There's an adb.exe in the Lenovo Rescue & Smart Assist install directory "C:\Program Files (x86)\Rescue and Smart Assistant".)
5 . Reboot the phone to the bootloader with the following command on the PC:
Code:
adb reboot bootloader
6. Flash the patched boot image with the following command on the PC:
Code:
fastboot flash boot magisk_patched.img
7. Reboot the phone with the following command on the PC:
Code:
fastboot reboot
Once rebooted you can use Magisk Manager to hide root, check the SafetyNet status, etc.
Thank you for your help on this. I rooted my moto x4 long time ago and the process has definately changed.
Still confused regarding your points
1 - where can i find the boot.img
2 - how do you patch using magisk
Also do you not need to unlock boot loader and bypass the verification and why do you need to hide root after?
Thank you
dafunk60 said:
I found it to be super easy using magisk, provided you have a PC to flash the patched boot.img to the phone via fastboot. I use the Lenovo Rescue & Smart Assist software on the PC to download the ROM from Motorola. You need to ensure the ROM you're downloading is the same version running on your phone. Using a boot.img from a different version will cause issues.
1. Copy the boot.img to the phone.
2. On the phone, patch the boot.img you just copied over with Magisk Manager.
3. Copy the patched magisk_patched.img back to your PC.
4. Connect to the phone via adb. (There's an adb.exe in the Lenovo Rescue & Smart Assist install directory "C:\Program Files (x86)\Rescue and Smart Assistant".)
5 . Reboot the phone to the bootloader with the following command on the PC:
Code:
adb reboot bootloader
6. Flash the patched boot image with the following command on the PC:
Code:
fastboot flash boot magisk_patched.img
7. Reboot the phone with the following command on the PC:
Code:
fastboot reboot
Once rebooted you can use Magisk Manager to hide root, check the SafetyNet status, etc.
Click to expand...
Click to collapse
himesh82 said:
Thank you for your help on this. I rooted my moto x4 long time ago and the process has definately changed......
Thank you
Click to expand...
Click to collapse
You're welcome.
himesh82 said:
1 - where can i find the boot.img
Click to expand...
Click to collapse
In the Lenovo software you can choose a download location. The default appears to be "C:\ProgramData\LMSA\Download". In that directory you'll see a "RomFiles" folder which contains folders for the different ROM versions it has downloaded. SOFIAP_RETAIL_QPR30.80_58_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml or SOFIAP_RETAIL_QPRS30.80_58_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml for example. You can find the boot.img file within those folders.
The QPRD30.80_58_3 boot.img file is located in "C:\ProgramData\LMSA\Download\RomFiles\SOFIAP_RETAIL_QPRS30.80_58_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml"
Some people share links to the ROM files but I prefer to get mine from Motorola.
himesh82 said:
2 - how do you patch using magisk
Click to expand...
Click to collapse
Google's your friend on this topic, https://www.xda-developers.com/how-to-use-magisk/
himesh82 said:
Also do you not need to unlock boot loader and bypass the verification and why do you need to hide root after?
Click to expand...
Click to collapse
You do need to unlock the bootloader, unless you have the private key Motorola uses to sign images . Just follow the instructions on the Motorola website. Unlocking the bootloader & rooting are two separate things. You need to unlock the bootloader to allow the hardware to boot unsigned images, such as a patched boot image. Root provides applications root access to the Android OS.
You typically want to hide root as some apps won't function if they detect root, mostly banking & video streaming services I believe. It's not a requirement however.
Thank you again. I will take a good look at the guide and then decide if it is something that I can attempt
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Wait DOES THIS WIPE ALL THE DATA?? I CANT get a clear answer. Supposedly the "official" unlocking through Motorola does but this is the Magisk method and I'm hoping it doesn't wipe the user data or apps.
Also how do you root AFTER you unlock the bootloader?
---------- Post added at 06:43 PM ---------- Previous post was at 06:37 PM ----------
JimmyJurner said:
It definitely works for the metro by TMobile version.
Click to expand...
Click to collapse
Does rooting wipe all the user data and apps?
nokia4life2017 said:
Wait DOES THIS WIPE ALL THE DATA?? I CANT get a clear answer. Supposedly the "official" unlocking through Motorola does but this is the Magisk method and I'm hoping it doesn't wipe the user data or apps.
Also how do you root AFTER you unlock the bootloader?
---------- Post added at 06:43 PM ---------- Previous post was at 06:37 PM ----------
Does rooting wipe all the user data and apps?
Click to expand...
Click to collapse
I honestly don't know. When I did the steps from op I unlocked the bootloader then rooted. I never booted into system. I can't check now because I'm running havoc os gsi and the op method doesn't work on gsis. I tried and it didn't boot but when I flashed the stock boot.img all my setup was still the same. Hope that helps some.
Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
Do you have a carrier model? You might be flashing the wrong boot.img although I'm not sure if theres anything different between then
No I bought the unlocked model from best buy cuz I know carrier models usually aren't rootable. Can some one post a link to the right boot.img
Here is my build number QPRS30.80-58-3 and my device info is in the pic TIA for any help
nokia4life2017 said:
Wait DOES THIS WIPE ALL THE DATA?? I CANT get a clear answer. Supposedly the "official" unlocking through Motorola does but this is the Magisk method and I'm hoping it doesn't wipe the user data or apps.
Also how do you root AFTER you unlock the bootloader?
Does rooting wipe all the user data and apps?
Click to expand...
Click to collapse
There are instructions on rooting in these forums, even in this thread.
Unlocking the bootloader forces user data to be wiped (aka factory reset).
Rooting with Magisk does not wipe user data.
Unlocking the bootloader and rooting are two separate things. Unlocking the bootloader allows unsigned images, such as a modified boot.img, to be run on the device. Rooting provides applications root level access to the Android OS.
---------- Post added at 02:19 AM ---------- Previous post was at 02:10 AM ----------
Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
It sounds like the boot image you're flashing does not match the version of the ROM on the phone. From your subsequent post, it looks like you're running QPRS30.80-58-3. Where did you get the boot.img file that you patched? You can use the Lenovo Rescue software to download the ROM files right from Motorola. These will contain the entire ROM, including the original boot image. Details are in the posts preceding yours. Flash the original boot.img & see if the phone boots. If it does, patch that image with Magisk & flash to obtain root.
Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
Try fastboot flash boot boot.img. When i did the stot a and b method i lost touchscreen etc
I bought a second stylus and the root method is different. So I fastboot flash the image (not to slots) and it worked but when the screen goes off the touch screen isn't responding.
I got it to work by using the assistant mentioned above. And using the fastboot flash magisk_patched.img or fastboot flash boot magisk_patched.img I can't remember which one at the moment but it automatically flashed both A and B slots with no problems. Also is TWRP available for the G Stylus?
Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
i just had the same thing happen to me. But i went to the assistant software and tried to rescue my device and it failed. Did you get it to work and how exactly did you get it working?
Edit: I just got it rescued and Im back up and running. Now I just need to figure out how not to repeat whatever mistake I just made and to get my device rooted. Did you ever figure out what you did wrong?
JimmyJurner said:
It definitely works for the metro by TMobile version.
Click to expand...
Click to collapse
Without unlocking the Bootloader?
*edit*
Cancel that, Just Unlocked my MetroPCS Moto G Stylus's Bootloader
*edit* *edit*
FYI : There is a new build for the RETAIL Channel from 7/21 : mirrors.lolinet.com/firmware/moto/sofiap/official/RETAIL/
Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
I am having the same issue while in fastboot, the device reboots bootloader every 20-30 seconds. I had to wait till the screen went off before hitting enter to get OEM Get_unlock_code.