Ok, so I finally decided to try installing Philz recovery on my GS4. I tried it with the recovery's unified build through CWM Touch, and I didn't use the Loki Doki zip file to patch it. It seemed to boot up just fine, but when I tried restarting the phone and have it automatically boot into Philz using the Cyanogen reboot menu, it brought up the unauthorized software screen with the message on the top left saying "Secure Fail: Kernel". I could not get to the recovery or boot into Android because every time I tried turning it on to just boot into Android, it tries to start Philz. I'd really hate the experience of going back to stock to fix this, so I tried finding a different solution...
And just as I was typing this I found out that I can, in fact, still boot into Android by holding down the down and home buttons, then saying no to the download mode confirmation with down. I think my problem with installing Philz was just that I didn't use Loki Doki because I've seen that CWM Touch doesn't Loki automatically when I first tried flashing the Alucard kernel, and I didn't use the Loki Doki zip file when flashing Philz. I'd appreciate some confirmation and any extra info on what happened here before I try again, as well as whether or not stock recovery images include updates to the bootloader, cause I'd hate to accidentally get stuck with a more restrictive updated one if I ever have to use the one I found.
I'll check this thread tomorrow seeing as it's almost 4am here and my brain has nearly gone full derp after hours of researching this :silly:
AnitaMedic said:
Ok, so I finally decided to try installing Philz recovery on my GS4. I tried it with the recovery's unified build through CWM Touch, and I didn't use the Loki Doki zip file to patch it. It seemed to boot up just fine, but when I tried restarting the phone and have it automatically boot into Philz using the Cyanogen reboot menu, it brought up the unauthorized software screen with the message on the top left saying "Secure Fail: Kernel". I could not get to the recovery or boot into Android because every time I tried turning it on to just boot into Android, it tries to start Philz. I'd really hate the experience of going back to stock to fix this, so I tried finding a different solution...
And just as I was typing this I found out that I can, in fact, still boot into Android by holding down the down and home buttons, then saying no to the download mode confirmation with down. I think my problem with installing Philz was just that I didn't use Loki Doki because I've seen that CWM Touch doesn't Loki automatically when I first tried flashing the Alucard kernel, and I didn't use the Loki Doki zip file when flashing Philz. I'd appreciate some confirmation and any extra info on what happened here before I try again, as well as whether or not stock recovery images include updates to the bootloader, cause I'd hate to accidentally get stuck with a more restrictive updated one if I ever have to use the one I found.
I'll check this thread tomorrow seeing as it's almost 4am here and my brain has nearly gone full derp after hours of researching this :silly:
Click to expand...
Click to collapse
Stock recovery files won't update bootloader, just make sure to use the correct one for your bootloader. It should only be a matter of loki, just make sure you follow specific install instructions.
Sent from my SGH-I337
Related
Hey guys I'm new to android had an iPhone for 6 years. Just got the gs4 two months ago. I rooted the phone took out bloat ware apps using titanium back up. Have a few other rooted apps. Got Interested in ROMs and kernels so did some research looked around on here to how to do it. I downloaded infamouses newest ROM. I have ROM manager and I downloaded cwm recovery through the Rom manager. When I go to back up my current ROM and everything it boots into recovery mode but it isn't cwm recovery. The emblem doesn't come up and I believe its the stock recovery. My question is how can I get the cwm recovery so I can back up my current ROM and then wipe it and install the new one. I'm new so sorry if this is easy or anything I appreciate all the help
Download goo manager and let it install twrp then just flash cwm thru twrp . Or keep twrp and remember to flash loki doki if needed.
Wait!
What firmware is your phone currently on? MDL OR MF3?
If MF3, stop now. Do not flash anything.
Sent from my SGH-I337 using xda premium
Okay I figured out the problems. When I hit reboot and superuser is supposed to grant root permissions an error comes up saying superuser has stopped working then goes into the stock recovery mode. The only thing I found with MDL in it was the baseband version 1337UCUAMDL
Your safe to continue flashing custom recovery on MDL Baseband
Sent from my SGH-I337 using xda app-developers app
Does anyone know how to fix this problem? Its so annoying I have tried goo manager and twsp recovery. And they all do the same thing.
Division4thor said:
Does anyone know how to fix this problem? Its so annoying I have tried goo manager and twsp recovery. And they all do the same thing.
Click to expand...
Click to collapse
Going on the information you have given, if you are doing right and using the correct version for your phone, GooManager and TWRP should be working for you. However, if you go to the development section and look for OUDHS CWM recovery, directions are given in the OP about how to manually install that recovery. Again, directions are in that thread about how to do it. I do hope you are reading all of every post that contains something you are trying to do (in other words, if you use OUDHS, read the entire thread first). Good luck.
scott14719 said:
Going on the information you have given, if you are doing right and using the correct version for your phone, GooManager and TWRP should be working for you. However, if you go to the development section and look for OUDHS CWM recovery, directions are given in the OP about how to manually install that recovery. Again, directions are in that thread about how to do it. I do hope you are reading all of every post that contains something you are trying to do (in other words, if you use OUDHS, read the entire thread first). Good luck.
Click to expand...
Click to collapse
Yeah Idk I'm so over this getting so frustrated. I'm new to this I read that post. Not all 51 pages hope you didn't mean that..
This is the easiest way ever, 1 click, and everything is ready to go....try it...
http://forum.xda-developers.com/showthread.php?t=2297900
Good luck
Thank you
TheAxman said:
This is the easiest way ever, 1 click, and everything is ready to go....try it...
http://forum.xda-developers.com/showthread.php?t=2297900
Good luck
Thank you
Hey thanks for the help. I got twsp recovery through goo manager and worked perfectly. I'm having such a bad experience trying to install this rom. I went into the recovery mode after backing up my current rom and system. I wiped everything out then went into my sd card amd installed the zip that is listed in the infamous page in the developers part. I hit install and then said I'm not rooted and would I like to install superuser. I slide the thing and then went to reboot and now has been stuck saying samsung and custom with an open love under it. Pulled the batter went back into twsp and tried to reboot and still stuck. This is all after I thought I installed the rom already and nothing changed except wiped my phone. Can anyone help
Click to expand...
Click to collapse
Are you installing loki doki after the rom ?
I'm using VS980, on 12B (sorry if I shouldn't have taken the OTA for what I want to do but I didn't know it'd be a problem). I just got this phone a few days ago and I've spent a fair amount of time trying to flash CWM touch to it, using the "loki" method (which I have no idea what loki is or what it's for), and consistently failed.
Each time I try pushing a CWM img with adb using loki_flash it results in an error at the end saying [-] loki aboot version does not match device.
I'm assuming this means the version of loki_flash file I'm using isn't compatible with 12B, but the OP in this thread states that in his walkthrough he's referencing the VZW img file, so I'm confused as to why it isn't working.
Moving on from that, I tried pushing the img without loki just using adb (method #2 in the above thread), and it appeared successful judging by the command prompt, however upon reboot I'm left with a black screen and have to hard restart my phone. I'm left without a working recovery.
With both of these methods failing, I tried installing CWM using an app called freegee, which I found to work, and CWM was fully functional. However, I thereafter tried flashing an AOKP ROM and a CM ROM and both failed. Both failure prompts were different, but the first one mentioned something about loki (again, what does this mean?) I tried rebooting from there and found my phone soft bricked (bootlooping) and I had to restore my nandroid backup.
So in summary, clearly I'm doing something wrong throughout all of the flashing processes that's resulting in recoveries that don't correctly flash ROMs for this phone. Right now I'm left running rooted stock with absolutely no recovery, unless I use freegee to flash TWRP or CWM but I'm left with recoveries that won't flash ROMs.
If anybody could help me sort out this mess I'd appreciate it.
Krogey said:
I'm using VS980, on 12B (sorry if I shouldn't have taken the OTA for what I want to do but I didn't know it'd be a problem). I just got this phone a few days ago and I've spent a fair amount of time trying to flash CWM touch to it, using the "loki" method (which I have no idea what loki is or what it's for), and consistently failed.
Each time I try pushing a CWM img with adb using loki_flash it results in an error at the end saying [-] loki aboot version does not match device.
I'm assuming this means the version of loki_flash file I'm using isn't compatible with 12B, but the OP in this thread states that in his walkthrough he's referencing the VZW img file, so I'm confused as to why it isn't working.
Moving on from that, I tried pushing the img without loki just using adb (method #2 in the above thread), and it appeared successful judging by the command prompt, however upon reboot I'm left with a black screen and have to hard restart my phone. I'm left without a working recovery.
With both of these methods failing, I tried installing CWM using an app called freegee, which I found to work, and CWM was fully functional. However, I thereafter tried flashing an AOKP ROM and a CM ROM and both failed. Both failure prompts were different, but the first one mentioned something about loki (again, what does this mean?) I tried rebooting from there and found my phone soft bricked (bootlooping) and I had to restore my nandroid backup.
So in summary, clearly I'm doing something wrong throughout all of the flashing processes that's resulting in recoveries that don't correctly flash ROMs for this phone. Right now I'm left running rooted stock with absolutely no recovery, unless I use freegee to flash TWRP or CWM but I'm left with recoveries that won't flash ROMs.
If anybody could help me sort out this mess I'd appreciate it.
Click to expand...
Click to collapse
The files from the thread you linked to aren't Loki patched (to my knowledge) look in the Verizon development thread and search for CWM/TWRP for 12B. Those should work. I've been using TWRP and can flash ROMS fine. Also its a matter of those ROMS being patched to flash while on 12B. CM11/gummy/carbon/cyanfox are patched and flash fine.
Here's the link
http://forum.xda-developers.com/showthread.php?p=48879826
Sent from chdhsheh fhhdud
Thank you, that did the trick as far as adb pushing a recovery with loki. It worked and I'm looking at my CWM screen right now. I'll try flashing CM and let you know how it goes although I don't anticipate any problems from here on out.
Thank you again.
I tried to install the CWM Recovery using Odin. Device gets stuck in BootLoop with......
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Cant Boot in download mode
It isnt recognized by the pc, odin or kies
Havet find a clear answer in previous posts. Any help?
luisjo2k said:
I tried to install the CWM Recovery using Odin. Device gets stuck in BootLoop with......
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Cant Boot in download mode
It isnt recognized by the pc, odin or kies
Havet find a clear answer in previous posts. Any help?
Click to expand...
Click to collapse
I am in this situation right now as well after flashing CWM recovery via ODIN. Hopefully someone has an answer. Did you find anything?
Try to overwrite your recovery with Philz Touch. It's working perfect for G900 variants so far:
Philz Touch Recovery Download
babygau said:
Try to overwrite your recovery with Philz Touch. It's working perfect for G900 variants so
Click to expand...
Click to collapse
I was finally able to get the phone into download mode by pulling the battery so I just pushed TWRP to it to fix the CWM issues. I'll check out Philz Touch as well though. Thanks.
knoxrents said:
I was finally able to get the phone into download mode by pulling the battery so I just pushed TWRP to it to fix the CWM issues. I'll check out Philz Touch as well though. Thanks.
Click to expand...
Click to collapse
Great!
IMO, Philz Touch is more beatiful and more functional than TWRP
Hi guys - I had this same issue today. I'd also installed CWM and tried to go into recovery mode via ROM Manager when it happened.
Looked around and after finding this thread I managed to flash with Philz Touch and got it to boot. Managed to get it into recovery mode and run this new Philz Touch version of CWM and do a backup. However just before it got into CWM it still came up with:
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Then loaded into CWM whereas before flashing Philz it was just looping. Is there a way I can stop it from coming up with this?
jeemer said:
Hi guys - I had this same issue today. I'd also installed CWM and tried to go into recovery mode via ROM Manager when it happened.
Looked around and after finding this thread I managed to flash with Philz Touch and got it to boot. Managed to get it into recovery mode and run this new Philz Touch version of CWM and do a backup. However just before it got into CWM it still came up with:
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Then loaded into CWM whereas before flashing Philz it was just looping. Is there a way I can stop it from coming up with this?
Click to expand...
Click to collapse
I'm using TWRP and the same thing comes up. It only comes up for a few seconds so I just don't worry about it. With CWM recovery, it was locked on that screen.
knoxrents said:
I was finally able to get the phone into download mode by pulling the battery so I just pushed TWRP to it to fix the CWM issues. I'll check out Philz Touch as well though. Thanks.
Click to expand...
Click to collapse
I have the same problem but when I pull the battery, then reinstall it I get the same result, I need help in a major way this is a brand new company phone
Noebody said:
I have the same problem but when I pull the battery, then reinstall it I get the same result, I need help in a major way this is a brand new company phone
Click to expand...
Click to collapse
I fixed it!!!
..
S5 set warranty bit recovery (G900i)
I know that philz recovery is best solutino but when I am going to download philz it's giving this error:
Hello,
Unfortunately, as of this time, the main portions of goo.im have been disabled. Due to a finance issue, our CDN account has been suspended, and all files stored on it are effectively non-accessible. Due to some RL issues on my(Alexander)'s part, once goo started actively losing money 6 months ago, I had changed jobs a bit to help support goo. Unfortunately, this wasn't enough combined with some other issues that crept up on me. Due to this, I'm formally shutting down Goo. There is an offer in to take over the files and hosting from a generous sponsor, however, until the financial issues are sorted out, they are unable to adsorb Goo. It's been my pleasure to serve files for you all for the past couple of years, and I wish everyone good luck into the future.
-- Snipa/Alexander Blair
If you have picked up a sponor account within the last two months, please reach out to us if you'd like a refund. It may take some time, but we'll do our best to get these processed and sent out. -- Thanks for everyone who's supported us over the years.
Noebody said:
I fixed it!!!
Click to expand...
Click to collapse
How? Same problem here.
jdrch said:
How? Same problem here.
Click to expand...
Click to collapse
I just saw this, and honestly I don't remember. Remind me what's happening and maybe it'll jog my memory
I can't get a custom recovery install to work. I've been at it for hours and I need to go to bed. For some reason, I can't install a custom recovery on my USA AT&T i337. I'm going to list what I've tried, it will be easier:
Installing TWRP through TWRP manager (TWRP manager crashes while flashing, soft brick)
Installing TWRP through Flashify (says it worked, then soft brick on reboot)
Installing CWM Touch through ROM Manager (says it worked, even shows version of currently installed recovery, soft brick on reboot)
Install/root with CASUAL (says it worked, soft brick on reboot)
I've never had this much trouble getting a custom ROM onto a new phone. Any idea what's going on? Seems like everything I read applies to everyone but me.
http://forum.xda-developers.com/showthread.php?t=2616221
Looks like you are reading the wrong stuff.
If you have newer firmwares, cwm and twrp will not work. The ONLY working recovery is safestrap.
jmjoyas said:
http://forum.xda-developers.com/showthread.php?t=2616221
Looks like you are reading the wrong stuff.
If you have newer firmwares, cwm and twrp will not work. The ONLY working recovery is safestrap.
Click to expand...
Click to collapse
THANK YOU VERY MUCH. Are there only certain ROM's I can flash with safestrap? I flashed SlimKat and didn't have wifi, then tried CM10 and couldn't get past the boot screen. This is the most trouble I think I've ever had with a new phone o_0 thanks for the help though.
EDIT: found the list, ignore dumb obvious question.
v1nsai said:
THANK YOU VERY MUCH. Are there only certain ROM's I can flash with safestrap? I flashed SlimKat and didn't have wifi, then tried CM10 and couldn't get past the boot screen. This is the most trouble I think I've ever had with a new phone o_0 thanks for the help though.
Click to expand...
Click to collapse
Yes, you're limited to the roms you can flash. See this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app
Hey guys, I'm a little devastated. Hoping I didn't ruin my phone.
So, earlier today I unlocked my Moto G4 Plus's bootloader and installed TWRP recovery. I installed ElementalX and a superuser.zip file as well. After reboot, there was no superuser in my app drawer and when I checked my root status with Phh's Root Checker, it said that my phone was not rooted properly. I then found the guide here on how to root, and noticed that it had Phh's SuperUser. I changed the config.txt file like mentioned in the guide, booted into TWRP recovery and installed it and clicked on reboot. I got the usual bootloader unlocked message, but after that my screen went blackish-grey and has been that way since, which is about 15-20 minutes now. I (panicking and being a noob) tried switching it off using the power button which didn't work. I then checked to see if it showed up as connected device in android sdk/fastboot, which it didn't.
WHAT DO I DO? I can't just buy another phone since I can't afford it as I recently bought this one, so it's a really big deal for me. :crying:
PLEASE HELP ME.
Thank you.
UPDATE.
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
UPDATE #2
So I did what abhi212b told me to do and flashed the stock rom. Everything is fine now.
I'll try rooting it again a bit later. Thanks for the help.
UPDATE #3
I tried rooting my phone again, and it went flawlessly this time! Rooted successfully.
What an emotional rollercoaster lol.
Push the power button for at least 2-3 minutes. Worked for me and others in the past.
SSJGod said:
Hey guys, I'm a little devastated. Hoping I didn't ruin my phone.
So, earlier today I unlocked my Moto G4 Plus's bootloader and installed TWRP recovery. I installed ElementalX and a superuser.zip file as well. After reboot, there was no superuser in my app drawer and when I checked my root status with Phh's Root Checker, it said that my phone was not rooted properly. I then found the guide here on how to root, and noticed that it had Phh's SuperUser. I changed the config.txt file like mentioned in the guide, booted into TWRP recovery and installed it and clicked on reboot. I got the usual bootloader unlocked message, but after that my screen went blackish-grey and has been that way since, which is about 15-20 minutes now. I (panicking and being a noob) tried switching it off using the power button which didn't work. I then checked to see if it showed up as connected device in android sdk/fastboot, which it didn't.
WHAT DO I DO? I can't just buy another phone since I can't afford it as I recently bought this one, so it's a really big deal for me. :crying:
PLEASE HELP ME.
Thank you.
Click to expand...
Click to collapse
Like the poster above stated, hold the power button until the screen shuts off. YOUR PHONE WILL AUTO REBOOT!!! The instant the screen turns off, begin holding the volume down button. When you see the fastboot screen pop up, begin flashing your N images again, or use a custom ROM (which are generally much faster, easier to mess with, and easier to recover from).
Ex didn't flash properly.. That is what I can estimate! If u root on stock kernel, it breaks the device.
As said above go to bootloader (works on any screen... Power and volume down) and then to twrp maybe (flash twrp from fastboot). And then restore any previous nandroid u have.. If not u will have to flash stock via fastboot and then flash ex kernel. When u flash, restart and go to about phone and see if the kernel shows elemental x.. If yes, go to twrp and root it via suoersu, phhh's superuser or magisk su.. Whichever u like.. That should be fine!
UPDATE.
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
SSJGod said:
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
Click to expand...
Click to collapse
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
abhi212b said:
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Click to expand...
Click to collapse
Thank you, will try this now.
Only the last SuperSU Beta defaults to systemless install. Any other ones require writing of a .SuperSU file to force systemless before rooting.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
SSJGod said:
Thank you, will try this now.
Click to expand...
Click to collapse
If you have not done this already, you can give it a try by flashing the stock boot.img via twrp and see if that boots the device.
I am not sure that it will work since, i have not tried it.
Exact same thing with the XT1625. I have also found that the systemless method of rooting with SuperSU kills my wifi and cellular network's connection abilities, which might just be a standard G4 thing but the only way I know of to fix it is reflashing the OS (data wipe not necessary).
Just thought this might be helpful to anyone who ran into similar issues to the ones I had.
also i'm still having issues with the stupid thing actually rooting but i'm gonna try again some other day.
just_magikkal said:
Exact same thing with the XT1625. I have also found that the systemless method of rooting with SuperSU kills my wifi and cellular network's connection abilities, which might just be a standard G4 thing but the only way I know of to fix it is reflashing the OS (data wipe not necessary).
Just thought this might be helpful to anyone who ran into similar issues to the ones I had.
also i'm still having issues with the stupid thing actually rooting but i'm gonna try again some other day.
Click to expand...
Click to collapse
I think that is the kernel issue.. you should try EX.. and then use SuperSU or maybe use Magisk SU..
abhi212b said:
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Click to expand...
Click to collapse
Had the same problem as OP and this fixed it, thanks a lot man!
Good to hear now the phone is alive!