I have always gone with Motorola phones in the past because they have always been root friendly. Not too long ago I picked up a Moto e6 after looking online to make sure it was rootable. Seems I may have the only version of the phone on earth that cannot be rooted. I've been trying to use the Magisk method. First, I tried having Magisk modify the boot.img file and while it says "success" at the end, with no errors, it is totally borked. The boot.img (original) is 32Mb in size but the Magisk-modified (rooted) boot.img is only 9.7Mb. I've gone down this road before and if I go ahead and try and flash that boot.img to my phone, it will brick. Then I tried to run Magisk on the recovery.img instead. That original file is 48Mb in size but the Magisk-modified version is only 15.9Mb. Again, from past experience I'm not even going to try and flash that image to the phone because the recovery will be borked.
My phone is a Moto e6 Surfna, retail unlocked, Android 9, build number PPBS29.73-81-5-14-5-4-2-6-3. I tried once before using a basic stock ROM of 28.73-81 but that REALLY borked the phone with it, pre-root attempt, being unable to even see its own cell phone modem (it became a tiny tablet device with only wifi). I assume that there was something wrong/missing in the stock rom vs my phone. Why is Magisk borking the boot and recovery images so badly? Is there ANYONE on Earth with a successfully rooted Moto e6 retail with the build I have?
Related
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
judask24 said:
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
Click to expand...
Click to collapse
No luck here...there is post over on Android Forums that Verizon users are getting the 4.4.4 OTA update but nobody has posted the captured zip file yet.
Captured Verizon CDMA Moto G 4.4.4 Update Zip
Here's a link to download the new Verizon Moto G 4.4.4 CDMA version of Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
http://goo.gl/Vuw0P9
or
http://www.mediafire.com/download/3q7paotltq951id/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
netkeys said:
Here's a link to download the new Verizon Moto G 4.4.4 CDMA version of Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
http://goo.gl/Vuw0P9
or
http://www.mediafire.com/download/3q7paotltq951id/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
Click to expand...
Click to collapse
That 173.44.20.falcon_cdma.Verizon.en.US is the 4.4.2 Kit Kat currently installed on the G's. I am looking for the newer one. 210.12.41.falcon_cdma.Verizon.en.US which is the 4.4.4 update.
judask24 said:
That 173.44.20.falcon_cdma.Verizon.en.US is the 4.4.2 Kit Kat currently installed on the G's. I am looking for the newer one. 210.12.41.falcon_cdma.Verizon.en.US which is the 4.4.4 update.
Click to expand...
Click to collapse
This is the file downloaded on 7-21-2014. Attached is a screen shot of the updater.
netkeys said:
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
Click to expand...
Click to collapse
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
randomchaos26 said:
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
Click to expand...
Click to collapse
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when I check for system update in settings, still says "software is up to date". Any suggestions?
chinocritter said:
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when when I check for system update in settings, still says "software is up to date". Any suggestions?
Click to expand...
Click to collapse
It was pulled from the /cache folder. If you put in /storage/sdcard0 you may also need to rename to update.zip
randomchaos26 said:
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
Click to expand...
Click to collapse
Yes please do. My wife's phone is wanting to update since Sunday night.
Seems to work just fine on Page Plus after the update, root works, and nothing has caught on fire yet. Edit: Tested data and calling, both seem to work fine.
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
If you want to get rid of the ugly "WARNING BOOTLOADER UNLOCKED IT WILL KILL YOUR FAMILY" boot logo, flash the logo.bin (fastboot flash logo logo.bin) in the attached zip file. It is just a simple hex edit of the logo address in the file header. I've included the original as logo.bin.bak so you can verify it against the original, and compare the two files if you want to see how it's done.
chinocritter said:
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when I check for system update in settings, still says "software is up to date". Any suggestions?
Click to expand...
Click to collapse
I think you can select "apply update from sdcard" in the recovery mode. No?
EDIT: You flashed to PagePlus. I missed that part. Sorry about that.
I was on a AOSP based rom.
So I flashed back to stock via CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.
Booted up once to make sure the the flash went well.
Flashed CWM via bootloader. Tried TWRP first, did not work with the update.zip.
Renamed the zip above to update.zip and flashed via cwm. Worked fine. (yes the zip is 4.4.4)
Before rebooting, went ahead and flashed supersu.zip.
Then rebooted back to bootloader and flashed my preferred recovery, TWRP.
All seems well. This is on PagePlus.
Bout time we get 4.4.4. I'm also using Boost Moto G to Verizon/Page Plus. I will update when I have free time. Thanks for the info, guys.
XDA Dark said:
Bout time we get 4.4.4. I'm also using Boost Moto G to Verizon/Page Plus. I will update when I have free time. Thanks for the info, guys.
Click to expand...
Click to collapse
It sounds like the 4.4.4 update is working fine...the only issue is that there doesn't seem to be a full stock 4.4.4 flash available (like we have for 4.4.2), and from what I can tell from posts (haven't tried this myself), you cannot reflash the full stock 4.4.2 after the 4.4.4 update since the bootloader and/or partitions have changed. There may be some workarounds, but those seem to be for other models or geographies as best I can tell. Once we have the full 4.4.4 flash, then at least you can always revert to that, but it doesn't appear to be released yet.
I've been keeping an eye out for the update OTA. I guess I'd rather just go down that path officially since my phones not rooted and had stock locked bootloader. Just wish it would hurry up and be pushed to my device.
Install zip via stock recovery
judask24 said:
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
Click to expand...
Click to collapse
Ota file works it is 4.4.4 update for Verizon Mota G. Download zip to phone power off. Hold down power and volume down for a few seconds release. Once at menu go to recovery. Once in recovery android with exclamation with no options will appear. Press and hold Volume up for 10 seconds continue to hold while now also pressing power button for 3 seconds release. Your in recovery mode select update from zip and proceed. Happy camping with new dialer update camera shots in low lightness and other fixes and features!
randomchaos26 said:
Seems to work just fine on Page Plus after the update, root works, and nothing has caught on fire yet. Edit: Tested data and calling, both seem to work fine.
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
If you want to get rid of the ugly "WARNING BOOTLOADER UNLOCKED IT WILL KILL YOUR FAMILY" boot logo, flash the logo.bin (fastboot flash logo logo.bin) in the attached zip file. It is just a simple hex edit of the logo address in the file header. I've included the original as logo.bin.bak so you can verify it against the original, and compare the two files if you want to see how it's done.
Click to expand...
Click to collapse
Followed these directions and worked without any problem.
The fixed the external USB mounting problem that was in 4.4.2
I updated today on Boost Mobile Moto G flashed to Page Plus with no issues... Success
Sent from my XT1028 using XDA Free mobile app
randomchaos26 said:
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
Click to expand...
Click to collapse
Thanks for the instruction. Questions:
(1) My flashed page plus moto-g is on rooted stock rom (with unlocked bootloader of course). Do I still need to restore the system partition back to stock?
(2) What is "CFC-fastboot"? Do you mean
fastboot falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip
(i.e. no underscore between fastboot and falcon) ?
Thanks!
it's available on OTA now yay
So I've tinkered a lot with this device, as well as the RAZR M. You may not recall my username, but I am the one that found out that the LG G3s Clockworkmod Recovery works on our locked devices. That being said, I've made several other side attempts at unlocking the bootloader on these devices, all of course to no avail. There are a few odd things I've found in an attempt to downgrade to 183.46.10. First of all, you CAN downgrade to 183.46.10 easily from 183.46.15 obviously if you are unlocked OR if you replace the gpt.bin, tz.mbn, and boot.img from 183.46.15 and run the flashing script. I've also noticed that devices that are on 182.46.15 also are running with an updated "sbl3.mbn" . So if you have RSD Flashed to 183.46.15 (or are just running that firmware), the only three updated files you're dealing with are the kernel (boot.img), trust zone (tz.mbn), and partition graph (gpt.bin). I've tried to flash a downgraded boot.img (the May 2nd) kernel via this "FlashBackToKK" script from droidrzr.com, and the kernel flashed successfully from the CWM recovery, but of course when I booted the device, I got a fastboot error boot failed: Downgraded security version. So the kernel successfully flashed, but some other part of the boot chain, presumably the trust zone, knows that the kernel image has been downgraded, so WHAT IF all three updated partitions are flashed via that CWM Recovery script? I need everyone who has experience in this kind of thing to please respond..
Honestly however way you try to work around I really don't believe will work. I really think some reverse engineering and code are needed for this to work. There way of bootloader locking on the razrs helped pathed the way of success in them keeping the Galaxy S5 and Other Phones BL Locked! Once one of them are unlocked I believe the s5 phones will be just as easy or similar. Maybe some hex editing and some file checksums need to be patch. Just my thought. I'll leave it to the experts.
I recently rooted, and later un-rooted my LG Stylo 2 Plus using TWRP, installing SuperSU. I found out about this other root called Magisk, that can apparently mask your status of being rooted. I tried my very hardest to install it, but it would not work. It mentioned that one of the requirements was to have a stock image, but I'm pretty sure I downgraded my image to Android 6.0 after flashing another stock rom from online. All of this has got my head wrapped around and I'm not sure if a factory reset will just brick my phone or something. I wanted to know if there's any way I can fix this mess.
Has anyone ran into the chance of seeing any custom recovery for this phone yet?
Unfortunately, I have no such experience
However, I successfully rooted the phone with Magisk
mingkee said:
Unfortunately, I have no such experience
However, I successfully rooted the phone with Magisk
Click to expand...
Click to collapse
How did you do that since the current way is to rename the apk and flash in a custom recovery?
1 Unlock bootloader
2 get stock firmware from program, forgot the name is the recovery stuff for moto
3 extract boot l.img
4 install magisk app and click install in the app, choosing patch boot.img
5 open adb adb reboot fastboot fastboot flashing boot boot.img
Viola rooted. I don't see any twrp, roms or anything. Could try a different variant I know moto g stylus twrp is really moto g 8 pro, or something like that. I'd back up with the recovery program tho, it has saved me when messing with flashing roms. GL
I also got root albeit tricky since trying root on the MetroPCS version will make the screen lose all touch functionality.
What good is root on this phone with you can't do anything with Android 10 being Read Only. I've been reading up on that and even in custom recovery it still is Read Only. That's the problem. So yay we got root but can't modify anything in it.
Articul8Madness said:
I also got root albeit tricky since trying root on the MetroPCS version will make the screen lose all touch functionality.
What good is root on this phone with you can't do anything with Android 10 being Read Only. I've been reading up on that and even in custom recovery it still is Read Only. That's the problem. So yay we got root but can't modify anything in it.
Click to expand...
Click to collapse
Main reason for me to root would be to bypass Hotspot limit via MagiskHide Props Config, and Screen2Auto AA mod/hack to send all apps to Car Stereo.
Does this touchscreen bug affect the T-Mobile version of the Ace 5G? I haven't ordered one yet.
Hello,
I have a moto G100 I just purchased. I unlocked the bootloader and I tried to install LineageOS but it was being difficult. I could get it to boot into TWRP. Now I tried to restore everything to stock as it wasn't even booting. After flashing the rom back in via fastboot the unit shows up as a serial device but that's it, no picture on the screen or anything.
I need some help to get this working again. Besides the directions on the LineageOS page sucks, steps are missing and things do not work properly.
Any help would be appreciated.
This is Qualcomm HS-USB QDLoader 9008 mode and won't boot.
Can anyone please help so this won't take weeks or months?
Thanks
Hello,
I fixed the brick with the blankflash file blankflash_nio_RRTS31.Q1-84-24-3-6
I was able to then use the official tool to recover the firmware. I was able to get LineageOS working but I wasn't able to do TWRP at all properly.
So I managed to install twrp but couldn't install lineage or anything out of it...
I managed to get TWRP installed but it was essentially useless as I couldn't access the internal flash unless it was setup by the OS already if you format the internal flash storage with TWRP it's useless especially via MTP.
I was able to install LineageOS and I was able to boot it, but I don't understand why it says I do not have enough space to install gapps. Without gapps LineageOS is essentially useless as an OS unless you do not use anything from google at all whatsoever not eve maps or anything.
How do I fix it so I can install gapps? I can't resize the system partition via TWRP as it doesn't even show it.
Thanks
if you have the bootloader unlocked you can try the "tinyflashscript" way and use that to overwrite all partitions with a stock image found here
RET stands for Retail and than the region code follows, just download the latest one for your region
after that your partitions are reset to the start and you could keep it that way or attempt to install lineage again but clean this time
I ran into the exact same situation as you with the storage issues and this fixed it for me
Hello my G100 was fully hard bricked trying to installed LineageOS (not the modded). I followed the following steps:
1. Installed and booted into LineageOS recovery from electimon.
2. Factory reset
3. Install ROM as adb sideload.
However, installation stuck at 47% and aborted. Phone was hard bricked once turned off. It couldn't even boot into booloader.
Luckily, I was able to enter EDL mode by pressing and holding volume and power down together for some time while it was plugged into PC using usb. Then I used blankflash to restore. This saved me from taking it to repair centre.
Hello,
I had the same brick issue and blankflash fixed it for me. I will try writing stock again then install LOSRecovery again and then try sideloading both LineageOS and gapps but I don't think that will work correctly as I think I did try that but we shall see, last time I did an install though after fixing the brick issue I used fastboot to do the stock recovery which should have fixed the partition sizes...
Thanks
It's strange that device becomes hard bricked because I installed LineageOS before and it booted fine. Only thing now changed is that I'm using February stock ROM instead of December one. Did Motorola change anything in Feb update that would cause hard brick when trying to install custom ROM?
Also, I've never did the "Ensuring all firmware partitions are consistent" thing. It worked before but not sure if we need to do it now.
Hello,
Strange indeed I can get LineageOS installed BUT because this is an A/B phone which is so silly, I can't install Gapps into LineageOS so essentially useless as the installer says the partition is too small and I do not have a way to fix that at the moment.
Thanks, and blankflash was able to get me up and running on stock but I cannot use the phone yet just like the DooGee S95 Pro I bought in hopes to use LineageOS... long story. Stuck with my ZTE Axon 7 from 2016 and a crap phone to make calls since my provider killed service to my ZTE Axon 7 so I carry basically 3 phones now. Until there is a fully working TWRP I am essentially screwed and feel like I wasted $400 on another phone.
marcusah123 said:
Hello,
Strange indeed I can get LineageOS installed BUT because this is an A/B phone which is so silly, I can't install Gapps into LineageOS so essentially useless as the installer says the partition is too small and I do not have a way to fix that at the moment.
Thanks, and blankflash was able to get me up and running on stock but I cannot use the phone yet just like the DooGee S95 Pro I bought in hopes to use LineageOS... long story. Stuck with my ZTE Axon 7 from 2016 and a crap phone to make calls since my provider killed service to my ZTE Axon 7 so I carry basically 3 phones now. Until there is a fully working TWRP I am essentially screwed and feel like I wasted $400 on another phone.
Click to expand...
Click to collapse
Using the method I described above I was able to install Lineageos 19.1 and then gapps (mindthegapps) using lineage recovery. it should be entirely possible
Hello,
With the storage not being large enough I was trying to install openGapps ( stock size ) for Android 11 since I was trying to use Lineage 18.1 and not 19/19.1 since 19/19.1 appear to have bugs and 18.1 does not. Anyhow I tried to sideload openGapps and it said there wasn't enough space on the system partition. I suppose I should try mindthegapps instead.
Thanks
So anyone successfully installed it without causing hardbrick? What exact steps did u follow? r u using g100 or edge s and what is the build number of stock rom prior to install? thanks
Windoors said:
So anyone successfully installed it without causing hardbrick? What exact steps did u follow? r u using g100 or edge s and what is the build number of stock rom prior to install? thanks
Click to expand...
Click to collapse
I used the latest stock after doing a recovery with blankflash and the rescue utility from Motorola. I then installed LOSrecovery because TWRP isn't ready. I then booted into LOSrecovery and sideloaded 19.1 latest from this forum. I can't figure out how to resize /system correctly so I cannot install anything other than MindTheGapps which sucks a lot.
Anyhow if we get a working TWRP soon that will allow resize as TWRP can't show the system partition and A/B switching is being worked out then we will be good to go.
If this isn't helpful or you need exact commands then I can do that too for you.