Database Users

[how to] downgrade moto x after ota camera patch update, lost root ability

{
"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"
}
Hello,
I dont have enough posts to post in dev section so I posted here and put is on my blog as well.
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANYTHING THAT MIGHT OCCURE WITH YOUR DEVICE. PLEASE READ ALL ARTICLES IN FULL BEFORE ATTEMPTING.
(Only tested for Rogers, cannot guarantee this works with other firmwares but I do not see why it wouldn't)
Not sure is this was covered before but I couldnt find anything with respect to my situation. I recently discovered a way to DOWNGRADE my MOTO X after I installed the OTA camera patch that allowed rooting via JCASE's PwnMyMoto to not work. I tried using RSDLite to flash back to the original stock firmware to no avail. I was lazy and did NOT google around and didnt read JCASE's updated disclaimer on his [Root/Write Protection Bypass] MotoX (no unlock needed) post at XDA that read
"The latest OTAs patch this exploit
The "Camera patch" patches the vulnerability we use to gain system user, and pwnmymoto will no longer work on devices with this update"
All credit where credit is due, I simply discovered a flaw to undo the update OTA camera patch giving me back the ability to use JCASE root method, which involved swapping the gpt.bin file from the new stock firmware found here: http://sbf.droid-developers.org/ghost_rcica/list.php
ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1FF.xml.zip (camera patch)
to the original
Rogers_XT1058_4.2.2-13.9.0Q2.X-116-LCX-26-34_CFC_1FF.xml.zip (no camera patch)
I then fired up RSDLite removed the necessary line from the XML to allow the flashing of the original firmware and voila!!!!!! bobs your uncle! the OTA appeared on screen asking to be installed. Ignore for now root your phone using JCASE PwnMyMoto found in the link below:
[Root/Write Protection Bypass] MotoX (no unlock needed)
If you want to apply the OTA patch I highly recommend you read both JCASE article in full and the one below as well before attempting to do this. The article below describes how to preserve root and apply the OTA camera patch.
Tutorial: How To Protect and Restore Root for an OTA Update
All credit for rooting and saving/preserveing root to JCASE and Dark9781 on XDA developers.
Thank you.

g01di3l0ck5 said:
Hello,
I dont have enough posts to post in dev section so I posted here and put is on my blog as well.
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANYTHING THAT MIGHT OCCURE WITH YOUR DEVICE. PLEASE READ ALL ARTICLES IN FULL BEFORE ATTEMPTING.
(Only tested for Rogers, cannot guarantee this works with other firmwares but I do not see why it wouldn't)
Not sure is this was covered before but I couldnt find anything with respect to my situation. I recently discovered a way to DOWNGRADE my MOTO X after I installed the OTA camera patch that allowed rooting via JCASE's PwnMyMoto to not work. I tried using RSDLite to flash back to the original stock firmware to no avail. I was lazy and did NOT google around and didnt read JCASE's updated disclaimer on his [Root/Write Protection Bypass] MotoX (no unlock needed) post at XDA that read
"The latest OTAs patch this exploit
The "Camera patch" patches the vulnerability we use to gain system user, and pwnmymoto will no longer work on devices with this update"
All credit where credit is due, I simply discovered a flaw to undo the update OTA camera patch giving me back the ability to use JCASE root method, which involved swapping the gpt.bin file from the new stock firmware found here: http://sbf.droid-developers.org/ghost_rcica/list.php
ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1FF.xml.zip (camera patch)
to the original
Rogers_XT1058_4.2.2-13.9.0Q2.X-116-LCX-26-34_CFC_1FF.xml.zip (no camera patch)
I then fired up RSDLite removed the necessary line from the XML to allow the flashing of the original firmware and voila!!!!!! bobs your uncle! the OTA appeared on screen asking to be installed. Ignore for now root your phone using JCASE PwnMyMoto found in the link below:
[Root/Write Protection Bypass] MotoX (no unlock needed)
If you want to apply the OTA patch I highly recommend you read both JCASE article in full and the one below as well before attempting to do this. The article below describes how to preserve root and apply the OTA camera patch.
Tutorial: How To Protect and Restore Root for an OTA Update
All credit for rooting and saving/preserveing root to JCASE and Dark9781 on XDA developers.
Thank you.
Click to expand...
Click to collapse
removing the necessary line from the xml I don't feel like would solve the problem. I think once you take the OTA it puts code in the bootloader that doesn't allow you to downgrade. Since bootloaders are locked for people that are actually stuck on the update (because they would just unlock the BL if they were and wanted to downgrade) I didn't think there was a way to downgrade since we can't touch the BL. Maybe rogers is different or you didn't take the full OTA but Id like to know if anyone else has success with this.

Can already verify this doesn't work with ATT. I've tried changing the same file to old/new/other carrier, didn't matter. Once you get past the GPT flash that works, the rest will still fail.

rmead01 said:
Can already verify this doesn't work with ATT. I've tried changing the same file to old/new/other carrier, didn't matter. Once you get past the GPT flash that works, the rest will still fail.
Click to expand...
Click to collapse
Try unlocking the bootloader first. Google "moto x unlock bootloader", i can't post links yet. Open motorola's link.
After that, follow what the OP said.

dliberalesso said:
Try unlocking the bootloader first. Google "moto x unlock bootloader", i can't post links yet. Open motorola's link.
After that, follow what the OP said.
Click to expand...
Click to collapse
Unlocked bootloader is necessary.

dliberalesso said:
Try unlocking the bootloader first. Google "moto x unlock bootloader", i can't post links yet. Open motorola's link.
After that, follow what the OP said.
Click to expand...
Click to collapse
ATT and VZW bootloaders are locked. This is why it won't work.

dliberalesso said:
Try unlocking the bootloader first. Google "moto x unlock bootloader", i can't post links yet. Open motorola's link.
After that, follow what the OP said.
Click to expand...
Click to collapse
The reason most people want to downgrade after an OTA is because they lost root. If they could unlock the bootloader, they could just get root again and not have to downgrade.

Most pointless thread ever. Root normally with unlocked bootloader and still have fixes. You don't need an exploit to root if your bootloader is unlocked.
Sent from my XT1055 using Tapatalk

Does anyone from rogers know if the first file name mentioned is a working Rogers with ota?
Sent from my XT1058 using Tapatalk

Instructions for root
g01di3l0ck5 said:
Hello,
I dont have enough posts to post in dev section so I posted here and put is on my blog as well.
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANYTHING THAT MIGHT OCCURE WITH YOUR DEVICE. PLEASE READ ALL ARTICLES IN FULL BEFORE ATTEMPTING.
(Only tested for Rogers, cannot guarantee this works with other firmwares but I do not see why it wouldn't)
Not sure is this was covered before but I couldnt find anything with respect to my situation. I recently discovered a way to DOWNGRADE my MOTO X after I installed the OTA camera patch that allowed rooting via JCASE's PwnMyMoto to not work. I tried using RSDLite to flash back to the original stock firmware to no avail. I was lazy and did NOT google around and didnt read JCASE's updated disclaimer on his [Root/Write Protection Bypass] MotoX (no unlock needed) post at XDA that read
"The latest OTAs patch this exploit
The "Camera patch" patches the vulnerability we use to gain system user, and pwnmymoto will no longer work on devices with this update"
All credit where credit is due, I simply discovered a flaw to undo the update OTA camera patch giving me back the ability to use JCASE root method, which involved swapping the gpt.bin file from the new stock firmware found here: http://sbf.droid-developers.org/ghost_rcica/list.php
ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1FF.xml.zip (camera patch)
to the original
Rogers_XT1058_4.2.2-13.9.0Q2.X-116-LCX-26-34_CFC_1FF.xml.zip (no camera patch)
I then fired up RSDLite removed the necessary line from the XML to allow the flashing of the original firmware and voila!!!!!! bobs your uncle! the OTA appeared on screen asking to be installed. Ignore for now root your phone using JCASE PwnMyMoto found in the link below:
[Root/Write Protection Bypass] MotoX (no unlock needed)
If you want to apply the OTA patch I highly recommend you read both JCASE article in full and the one below as well before attempting to do this. The article below describes how to preserve root and apply the OTA camera patch.
Tutorial: How To Protect and Restore Root for an OTA Update
All credit for rooting and saving/preserveing root to JCASE and Dark9781 on XDA developers.
Thank you.
Click to expand...
Click to collapse
I am new here to the forums, and I have a tmobile moto x (unlocked bootloader) running 4.4 with camera update. I just want to know your exact method on how to downgrade.
I know I download the older firmware, then is there a Mac version or equivalent to the rsdlite as I only have access to a Mac? I also do not know what to revert back to.
Any help would be appreciated.

[Root] Root for S6 coming soon

If anyone knows where to download G920AUCU1AOCE please send me the link through PM. Many thanks.
[5/8] Beta 1 released! http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
[5/8] Beta 1 will be released in 24hrs. Following ROM FP will be supported for testing:
G9200ZCU1AOD5
G9200ZHU1AOD3
G9200ZHU1AOD9
G920R4TYU1AOD3
G920IDVU1AOD1
G920FXXU1AOCV
G920PVPU1AOCF
G920TUVU1AOCG
G920VVRU1AOC3
G920FXXU1AOBN
We are throwing another party, soon... :laugh::laugh::laugh:
Root on SM-G9200 has been achieved without tripping Knox, utilising a new vulnerability just reported (https://twitter.com/grsecurity/status/594483601661505536)
{
"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"
}
ROM specific data will be required, so please let me know your current ROM fingerprint so we can extract data from them. A download link will be appreciated.
Just S6 fingerprint please. Generic root for 32-bit devices will be released in new version of Kingroot (see Q&A)
Credits:
Vulnerability: memeda, wushi
Original idea of exploit: memeda
Exploit: idl3r, Qoobee
Special thanks to:
Kingroot team for help testing and great root manager
Q&A:
[5/5] Sorry for the delay, busy paint balling and fly crossing pacific
Q: When will you release it?
A: We are currently working to make it more reliable and covering more ROMs. Please stay tuned
Q: Is this fake?
A: No. We discovered this vulnerability and we don't bother faking a root. See this answer for an explanation of the screenshot: http://forum.xda-developers.com/showpost.php?p=60531263&postcount=34
Q: How to get a fingerprint?
A: Please follow these steps:
1. Run "adb shell"
2. Type "getprop | grep fingerprint"
3. Please copy and paste the result
Q: Why fingerprint is needed?
A: We will try to extract the kernel for certain binary gadgets to help the root.
Q: Is this a generic root?
A: Not for this particular tool. But generic root is possible for most 4.3+ devices with this vulnerability. I just bought an S6 so I decided to root it first. Stay tuned for other devices
We've been working on generic root with Kingroot team to test it out on wide range of devices. Test results just came out and it looks very positive. It will be released in Kingroot in 2-3 days, and shall cover 80%+ of post-futex kernels (may take sometime to optimize the model/FP data).
Among them are devices (32-bit for now) like Sony Xperia Z3, LG G3, Huawei Honor 6, 6Plus, Mate 7 and many other devices,with support of their latest Android L or Kitkat ROM. Stay tuned S5 and Note3 with Android L are also supported for specific FP, with new FP added in the future.
Q: S6 Edge?
A: We'll look into the kernel first. So far there are QC charging (hardware) issues for S6 Edge and potentially we will wait till this potential HW issue is fixed.
Q: Will this work for AT&T/Verizon/etc version?
A: In theory, yes. Locked bootloader doesn't affect this one. However, if bootloader locks the UFS controller for write protection (like Note4), chances are su install won't be permanent.
Q: Why you report this vulnerability? Vendor will fix it soon!
A: First of all we are researchers. Releasing 0day exp to public without notifying the vendor is non-ethical. Secondary there is no sense of hiding it since when this tool is released, vulnerability will be learnt by vendor. With all debugging tools/HW and expertise they have no software level obfuscation/encryption would help hiding the vulnerability.
Update:
[5/5] Add Q&A
[5/6] Update status of GENERIC root
[5/8] Beta 1 status update

Thats great
Would be it like towelroot?

I knew that spaceship I saw last night was bringing something of use!!!

I have no idea what any of the jargon means unfortunately, but a root without tripping knox?! Definitely looking forward to this. I was planning to root my phone only after the warranty expires haha.

idler1984 said:
We are throwing another party, soon... :laugh::laugh::laugh:
Root on SM-G9200 has been achieved without tripping Knox, utilising a new vulnerability just reported (https://twitter.com/grsecurity/status/594483601661505536)
ROM specific data will be required, so please let me know your current ROM fingerprint so we can extract data from them. A download link will be appreciated.
Credits:
Vulnerability: memeda, wushi
Original idea of exploit: memeda
Exploit: idl3r, Qoobee
Special thank to:
Kingroot team for help testing and great root manager
Click to expand...
Click to collapse
The China G9200 and HK G9200 has slightly different, please ensure that root is also working on HK G9200.
http://www.romhome.com/28270.html
HKG9200 stock firmware download link is here via Baidu cloud

could you tell me if this method is universal like towelroot? for any phone? when it will be available for everyone?
i was on the edge of loosing my warranty today, i wanted to flash cwm to install root but now when there is hope for knox 0x0 root i will wait

Kriomag said:
could you tell me if this method is universal like towelroot? for any phone? when it will be available for everyone?
i was on the edge of loosing my warranty today, i wanted to flash cwm to install root but now when there is hope for knox 0x0 root i will wait
Click to expand...
Click to collapse
Pump the brakes, homie. Let's let something materialize before we start the 20 questions. Wait for a drop and an OP.

This exploit will work with all S6 variants, right?

Seems likely. Shame that it was released now, though, since the forthcoming 5.1 release might patch the exploit.

idler1984 said:
We are throwing another party, soon... :laugh::laugh::laugh:
Root on SM-G9200 has been achieved without tripping Knox, utilising a new vulnerability just reported (https://twitter.com/grsecurity/status/594483601661505536)
ROM specific data will be required, so please let me know your current ROM fingerprint so we can extract data from them. A download link will be appreciated.
Credits:
Vulnerability: memeda, wushi
Original idea of exploit: memeda
Exploit: idl3r, Qoobee
Special thank to:
Kingroot team for help testing and great root manager
Click to expand...
Click to collapse
I can help, I am on a 920I from a carrier in Brazil.
But, I really don't know how to get rom fingerprint... sorry bout the noob question.

Wiseor said:
This exploit will work with all S6 variants, right?
Click to expand...
Click to collapse
Will this work on at&t and Verizon models?

I'm in the same boat. SM-G920A
Any way I can help I will but I don't have a clue what I'm doing

Wiseor said:
I'm in the same boat. SM-G920A
Any way I can help I will but I don't have a clue what I'm doing
Click to expand...
Click to collapse
Hopefully this exploit will work on at&t and Verizon models since they have locked bootloaders.

Hope it works for Verizon.

pm me if you need someone to test on an s6 edge (verizon)
Sent from my SM-G925V using XDA Free mobile app

When are they releasing the root?

I hope not until after 5.1 is released so they cannot patch it.

anewday said:
I hope not until after 5.1 is released so they cannot patch it.
Click to expand...
Click to collapse
if you read you can see its already been patched.. therefore newer L builds probably already have a patch for it..
people on 5.1 will have to downgrade id assume to 5.0 or lower to take advantage of it
Sent from my SM-G925V using XDA Free mobile app
---------- Post added at 10:40 PM ---------- Previous post was at 10:38 PM ----------
Hi,
Recently we found a use-after-free bug which can lead to kernel arbitrary
execution in Linux kernel.
The bug was reported to the linux security group and it has been fixed.(commit
a134f083e79f ("ipv4: Missing sk_nulls_node_init() in ping_unhash()"). You
can find the fix commit here:
https://github.com/torvalds/linux/commit/6c3c1eb3c35e8856d6dcb01b412316a676f58bbe
The bug exists in all versions of linux kernel. And the credit is to Wen Xu
and wushi of KeenTeam.
I am looking forward to your reply.
Thanks,
Wen Xu @ Keen Team
Sent from my SM-G925V using XDA Free mobile app
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
clearly said its fixed
Sent from my SM-G925V using XDA Free mobile app

Fruktsallad said:
Seems likely. Shame that it was released now, though, since the forthcoming 5.1 release might patch the exploit.
Click to expand...
Click to collapse
no problem here, if older kernels can be rooted you just have to flashfire 5.1 on top of it just like on old S5 where on 4.4 kernel you could towelroot the device and then using flashfire jump to 5.0 with root

Yo, if anyone can answer how to get a "fingerprint" for your ROM, I'd be happy to upload anything from my AT&T S6 edge.

[GUIDE]ROOT Your LG Marshmallow ROM With Systemless ROOT. No More ExFAT Issues!

This is not a fix for already persisting issues. If you're currently dealing with ExFAT (or BT) issues, Systemless ROOT will not help you. Bring your device in a state where you don't have these issues by flashing a stock ROM matching exactly your variant and location. Then use Systemless ROOT using a custom recovery.
Unlocked Bootloaders Only
Confirmed working by me on a H815-EUR bought in Germany.
UPDATE: Confirmed to be working on following MM ROMs:
H815 EUR 20A/C/D Germany
H815 EUR 20B Poland
H815 EUR 20A Croatia
Please report if this works for you according to this scheme: H815-EUR-20A-GERMANY
Legend
Blue: Device Model
Black: Device region
Red: Firmware Version
Green: Location
Simple:
After flashing or updating to a stock LG MM ROM, boot into TWRP and flash Chainfire's Systemless ROOT 2.67. It'll automatically backup, patch and flash the Kernel. It'd be great if you could confirm by giving details about your device, e.g. "H815-EUR Germany" or "H815-EUR Poland" etc.
As stated by @Chainfire in his thread:
If you are coming from a SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this.
If you are coming from a SuperSU system-less install, you must re-flash the stock kernel prior to installing this.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!
Future updates will be significantly less painful
Click to expand...
Click to collapse
With the introduction of TWRP 3.X.X., this is no longer an issue. TWRP will no longer ask to install SuperSU if it detects a Marshmallow ROM.
For G4 (H815) users:
You have to reflash the latest stock KDZ or .zip (modem, system, boot - restart recovery - bootloader) if you're currently dealing with exFAT issues. Then you can fire up TWRP and flash Systemless ROOT 2.67.
The reason why you might want to use this method to root instead of simply flashing a pre-patched Kernel is differences in ROM versions. As it happened to me, on my H815-EUR from Germany, I received the MM update. It was called "20A" for some reason, but it has the same fixes and updates as 20B. So it's not to be confused with the early 20A build from Poland! Quick as I am, I flashed the repacked boot.img for 20A by @cile381 and lost exFAT support, and somehow corrupted ADB, since cile381's repacked kernel was built from and for the Poland 20A build.
I hope this'll help you =)

Great, but if it's not necessary to flash a modified boot image anymore, do we could have root permission with Android MM, by flashing a modified system image (with supersu injected) by using the DD method with Android 5.1 running? This can be helpful for people who can't unlock the bootloader

Andrea__93 said:
Great, but if it's not necessary to flash a modified boot image anymore, do we could have root permission with Android MM, by flashing a modified system image (with supersu injected) by using the DD method with Android 5.1 running? This can be helpful for people who can't unlock the bootloader
Click to expand...
Click to collapse
No, that's not true. You still need a modified boot.img. With this method, you basically create your very own patched kernel, from the boot.img extracted from your very device.
MM still requires a patched/repacked kernel.
EDIT: Ok, now I see where the confusion came from. Misleading title.

thank you ! very useful ...
i have a question :
why ,with a phone (bootloader unlocked) with MM 6 ,it's possible to easily have a root .......but the locked device no ? ===> but instead of use TWRP , by injecting only the SuperSU with adb fastboot (or kdz pack?) for locked device???

Basically, Marshmallow has very strict security restrictions. The stock kernel won't allow any modifications. That's why we need a modified (vulnearable) one. You can simply flash a modified kernel onto a bootloader unlocked device. But since you can't flash custom boot.img's on locked devices, people with non-unlockable devices currently have no way to root their MM devices.
More details can be found in this XDA article.

very very interesting what you have said ,thank you for sharing and help
i didn't know MM...
that's mean ther NEVER have a chance for a root of MM with locked bootloader !!! if i have correctly understood ...
the only way is to unlock this damned bootloader ......or downgrade to LP by LG-UP (kdz) and then root with fastboot method ??? i'm true ???
i just discover this LG G4
in the past i have had a LG optimus series ...with old methods and full possibilities !
i begin to believe that it's the begining of the dead of android development if all manufacturers and google "lock" and add too many securities on these news devices with "hard" methods ...

Haha, sure! You're welcome =)
I wouldn say "never". There's always a chance that a genius will find a way. You also need to factor in the relatively young age of the G4.
To the last part: Yeah, it's getting harder and harder. But nothing unexpected. Remember, power users like us do only make up a very small, almost insignificant amount of all the Android users out there. I'm sure most people don't even know what Android is. Google just went full on Spock and said "Thee needs of the many outweigh the needs of the few or the one" :laugh:

ho my god ...sh** ........
imagine the future LG G5 (and others manufacturers ) with bootloader locked !!!! and if they never want to unlock with these new security politic........and this damned MM for original firmware more and more securised ==> we all profoundly have it on ours ass !!!
otherwise there are big chance to hard brick devices with bests devs attempts ...
Sorry for my bad words ,but this xda article that you previously have given to me ,make me really afraid !!!!!!! ...
Another big question :
when we have done MM update on G4 ,i have read that it's possible to easily downgrade to LP with LG-UP ....but full upgrade ??? it change this new MM bootloader with LP one ? for to have the possibility to root with locked bootloader ...

"While horror for us XDA people, it's better for the general public." This is how I think Google and OEMs justify their decision (which I find questionable tbh). But enough of that. Let's keep it on topic. I'd love to see reports from you whether it worked or not. Please include your ROM version, device and the country it was bough in. E.G. H815-EUR v20A Germany.
Btw. This just happened
{
"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"
}

Just used this on LG G4 H81520A, ( bootloader officially LG Unlocked ) went sweet as a nut.

I think if you flashed the repacked 20B boot.img it's possible you wouldn't have had ExFat issues. German 20A is Polish 20B. When you mismatch boot.img's you have ExFAT issues.
Systemless root is certainly nice though. I wasn't aware there was an automated tool now. Will make getting root after a new release even easier now

I'm not worried about the G5 to be honest. The LG v10 makes it as easy as on Nexus to unlock the bootloader: Look here. Sorry for offtopic, but it really fitted for me .

MickyFoley said:
I'm not worried about the G5 to be honest. The LG v10 makes it as easy as on Nexus to unlock the bootloader: Look here. Sorry for offtopic, but it really fitted for me .
Click to expand...
Click to collapse
If it is only for the T-Mobile variant they are probably at the same (if not worse) point that the G4 is. At least we can officially unlock some devices...

nitrous² said:
"While horror for us XDA people, it's better for the general public." This is how I think Google and OEMs justify their decision (which I find questionable tbh). But enough of that. Let's keep it on topic. I'd love to see reports from you whether it worked or not. Please include your ROM version, device and the country it was bough in. E.G. H815-EUR v20A Germany.
Click to expand...
Click to collapse
ok ,sorry for out of topic ...
i keep you thread preciously whe i will decide to unlock my bootloader thank again and again !
MickyFoley said:
I'm not worried about the G5 to be honest. The LG v10 makes it as easy as on Nexus to unlock the bootloader: Look here. Sorry for offtopic, but it really fitted for me .
Click to expand...
Click to collapse
i like your optimism ! i want to believe ...

I never had exfat problem with cile381 repacked kernel as autoprime stated it only happens if boot. Img mismatches. Other than that maybe this method could solve exfat problem on cm13?

@i-m: exFAT-issues of CM13 should be solved at 7th of December :
Code:
g4: vold: enable native exfat support (android_device_lge_g4-common)
g4: build exfat driver (android_kernel_lge_msm8992)

autoprime said:
I think if you flashed the repacked 20B boot.img it's possible you wouldn't have had ExFat issues. German 20A is Polish 20B. When you mismatch boot.img's you have ExFAT issues.
Systemless root is certainly nice though. I wasn't aware there was an automated tool now. Will make getting root after a new release even easier now
Click to expand...
Click to collapse
I did that too. I mean, flashing repacked 20B on German 20A. I then no longer had issues with exFAT formatted cards, but ADB was still "corrupted", meaning it wouldn't let me authorize my PC and the option to de-authorize was no longer available in the developer settings menu. Of course, might as well be an isolated case.
i-m said:
I never had exfat problem with cile381 repacked kernel as autoprime stated it only happens if boot. Img mismatches. Other than that maybe this method could solve exfat problem on cm13?
Click to expand...
Click to collapse
Sure you hadn't. But if you read OP closely, you'll see why some people, me included, had issues. No, it will not solve exFAT issues for CM13.
MickyFoley said:
@i-m: exFAT-issues of CM13 should be solved at 7th of December :
Code:
g4: vold: enable native exfat support (android_device_lge_g4-common)
g4: build exfat driver (android_kernel_lge_msm8992)
Click to expand...
Click to collapse
It was still broken when I tried the nighlty from December 7th.

Followed OP, root is working.
Still can't use my SD Card as on rooted 5.1:
- in FX Explorer I need to set a bookmark to a mounted location somewhere deep in the root filesystem,
- Lightroom says SD Card not available.
But this is a Marshmallow specific problem, isn't it?

Jens1969 said:
Followed OP, root is working.
Still can't use my SD Card as on rooted 5.1:
- in FX Explorer I need to set a bookmark to a mounted location somewhere deep in the root filesystem,
- Lightroom says SD Card not available.
But this is a Marshmallow specific problem, isn't it?
Click to expand...
Click to collapse
Apps have to be updated for proper support for SD cards. I switched to Solid Explorer because FX hasn't been updated for months.

Jens1969 said:
Followed OP, root is working.
Still can't use my SD Card as on rooted 5.1:
- in FX Explorer I need to set a bookmark to a mounted location somewhere deep in the root filesystem,
- Lightroom says SD Card not available.
But this is a Marshmallow specific problem, isn't it?
Click to expand...
Click to collapse
This is not a fix for devices that ran into SdCard issues. This is supposed to help you prevent exFAT issues from happening. The pre-requisite is an alread working device without exFAT issues.
This is specifically for Marshmallow devices. I'm surprised your device booted up after this Systemless ROOT patches your Marshmallow FW's kernel.

[Help Me] Moto G5 Plus Hard Bricked & Solved

Hello All,
Recently my device Moto G5 Plus Hard Bricked and was not opening. When I plug data cable to laptop or Charger LED light was blinking. I have searched many threads on this Forum but finally, somehow I managed to recover my Device. (This thread Helped me to recover my device https://forum.xda-developers.com/showpost.php?p=73268905) And the thing is BlankFlash (@vache) for POTTER was not working on my device and I have searched thread and got to know that I have downgraded update and due to this my device has eaten up my bootloader. So now one of the members of this forum (@Rakesh1b) helped me to recover my device as he said "Now I need to blank flash (ALBUS) with Moto Z2 Bootloader (it has worked with many members and me too) on Moto G5 Plus and it worked fine and I cannot Install Stock ROM on POTTER rather I have to install Stock ROM which STOCK TOM DEODEXED DEBLOATED" then I can Install any Custom ROM on it! You can see the picture I have attached to this thread.
Now my actual problem is "I want to go back to my STOCK ROM (I need OTA Updates though) with Relock Bootloader" Can anyone help me to figure out these problems which I am facing now.
{
"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"
}

Bro sorry to say this that until we get an updated blankflash which has an updated bootloader and gpt version of potter which has either the same or higher version that we had in our mobile when they're bricked i.e mostly after May or June or same as April version of bootloader we cannot get back to stock room because you know that the bootloader and gpt are of motoz so obviously the ROM won't bootup due to mismatch so let's hope and wait for the developers or any member until they release a leaked Motorola blankflash with updated blankflash there is nothing we can do until then but just wait in xda for motog4 also same happened when many had updated through OTA to take nougat and they had downgraded before that and they had waited for 4 to 6 months till and updated blankflash is leaked but in our case we are very lucky that Albus blankflash worked and we are able to use our phones ,potter blankflash will work for them who had not updated bootloader when flashing different ROMs the npns35-5,npns33-3,.67 OTA had updated bootloader and gpt if we have not tried any of these then vaches blankflash will work.
I am confident that an updated blankflash with the bootloader and gpt of the updated version will be released but we have to wait till then we can only hope that vache sees our problem then there is chance because the current blankflash is even provided by him thanks a ton vache without your help many potters would have been in coma.
Guys first don't hardbrick your mobile read everything carefully then flash if they're safe. That they won't mess with your bootloader.
Caution:
* Don't take OTA after downgrading ROM.
* Flash any stock ROMs through fastboot only.
And there is not much problem with custom ROMs which are twrp flashable.

Bhai, suppose if vache releases updated Blank Flash for Moto G5 plus with updated bootloader then can we Install NPN137.15 then get OTA directly to NPN137. 67??? Is this possible if he releases the updated one???
Also please inform me if vache releases updated version of Blank Flash. Because badly I'm in need of this. Hope you understand my pain !!!

If vache releases an updated blankflash with updated bootloader and gpt then you can flash npn15 through fastboot ROM but if you again try to take OTA then what happens is if the bootloader version in OTA is old compared to bldr version in blankflash then you will again successfully hardbrick your mobile now same blankflash can be used again to revive it back but the solution is when an updated blankflash comes then whatever stock ROMs we flash we have to just flash them using fastboot method in this method if we are on a latest available ROM and we try to downgrade to old version of ROM then fastboot will safely don't allow us to flash the old rom saying downgrade error or even it flashes it will leave the bootloader and gpt with the updated version and only flashes system images and you could boot up your downgraded ROM the thing is fastboot verifies and keeps us in safe zone but in the case of OTA it doesn't check all that but only checks if it is on the correct default ROM for which the OTA is released and patches the ROM with all the contents in it so we are risking taking the OTA so safe method is to flash only fastboot stock ROMs that will be released and stay with them if we are clear about the versions of bootloader gpt then we can take OTA there is no problem but many don't know that and they try and bricked their devices.
Hope you understood.

Dear posters... 3 things:
1. Please do NOT keep quoting the previous post - there's no point and it just slows page loads down.
2. Do NOT keep "mentioning" other members in your posts. This REALLY annoys those you have mentioned as their inbox gets full of repeated childish demands for attention. And guess what? They ignore them... and you.
3. Questions must be asked in the Q and A Forum. So moved.

If anyone finds the Blank Flash updated version for Moto g5+ with updated bootloader please let me know through this thread. I'll be thankful.

Can anyone help me to get a better camera quality on custom ROM

anthonyqwe said:
Can anyone help me to get a better camera quality on custom ROM
Click to expand...
Click to collapse
No Chance Bro, only on stock you can achieve...

@Rakesh1b Bro, as you know I'm using Albus bootloader in my potter. So can I use albus stock ROM in my potter??

?? bro I could understand your desperation there is no other way other than using twrp based stock ROMs or any custom ROMs for us u had been using debloated stock ROM since I bricked it is much more faster and stable than Moto stock images don't try any other ROMs which are not meant for motog5plus plus because there kernel source varies and configuration varies so don't try any other ROM and mess your potter u will make it totally unusable if even the current blankflash fails to work after installing any other ROM.
Hope you understood.
Be cool just enjoy your potter till new blankflash is released.
Bye..

@vache please help!!!

the best option we have since i also hardbricked and returned thanks to albus, is to wait for the release of Oreo, rather than using new blank flash, with oreo stock rom image (around 1.5 gb) and flashing it through fastboot we'll be able to return to stock since will have new updated recovery gpt and whatever is needed. by the monent as Rakesh1b said debloated is better than stock faster cleaner etc and the otas.......not necesary really i have installes lineage 14.1 (nougat based) and works awesome, maybe ill move to 15 once more stable and may be even before the offic( oreo based) ial release of oreo.

LLegion said:
the best option we have since i also hardbricked and returned thanks to albus, is to wait for the release of Oreo, rather than using new blank flash, with oreo stock rom image (around 1.5 gb) and flashing it through fastboot we'll be able to return to stock since will have new updated recovery gpt and whatever is needed. by the monent as Rakesh1b said debloated is better than stock faster cleaner etc and the otas.......not necesary really i have installes lineage 14.1 (nougat based) and works awesome, maybe ill move to 15 once more stable and may be even before the offic( oreo based) ial release of oreo.
Click to expand...
Click to collapse
Gpt and bootloader from Oreo won't be enough. Since they're using albus bootloader and partitions, overwriting gpt and bootloader from Oreo, will simply throw errors. Definitely will be needed a blankflash specifically for potter; then any Oreo firmware will work for flashing.

Moto G5s Hard bricked blankflash files and loader.img required.

Rakesh1b said:
bro I could understand your desperation there is no other way other than using twrp based stock ROMs or any custom ROMs for us u had been using debloated stock ROM since I bricked it is much more faster and stable than Moto stock images don't try any other ROMs which are not meant for motog5plus plus because there kernel source varies and configuration varies so don't try any other ROM and mess your potter u will make it totally unusable if even the current blankflash fails to work after installing any other ROM.
Hope you understood.
Be cool just enjoy your potter till new blankflash is released.
Bye..
Click to expand...
Click to collapse
Did Vache realesed Potter BlankFlash? I have find something in potter folder http://cloud.vache-android.com/Moto/potter/blankflash/ is this the original blank flash of potter?

mohammadsharfuddin said:
Did Vache realesed Potter BlankFlash? I have find something in potter folder http://cloud.vache-android.com/Moto/potter/blankflash/ is this the original blank flash of potter?
Click to expand...
Click to collapse
Nope, it's the one that he developed. There's no official one yet.

thedr34m13 said:
Nope, it's the one that he developed. There's no official one yet.
Click to expand...
Click to collapse
I thought that blankflash, with the April 2017 timestamp on it, was the original potter one, as it looked to be leaked with the original factory image? Regardless, we can't make blankflashes sadly (needing to be signed by Motorola, as I understand it) and that potter blankflash is far too old to be used in most cases.
If we're really lucky, perhaps a factory Oreo stock ROM might be leaked which may have an original Oreo potter blankflash. If not (i.e. it's just a standard fastboot ROM) then we'd have to wait for a leak or spend money on a new motherboard.

echo92 said:
I thought that blankflash, with the April 2017 timestamp on it, was the original potter one, as it looked to be leaked with the original factory image? Regardless, we can't make blankflashes sadly (needing to be signed by Motorola, as I understand it) and that potter blankflash is far too old to be used in most cases.
If we're really lucky, perhaps a factory Oreo stock ROM might be leaked which may have an original Oreo potter blankflash. If not (i.e. it's just a standard fastboot ROM) then we'd have to wait for a leak or spend money on a new motherboard.
Click to expand...
Click to collapse
It it's an original one then I heard wrong, but like you said it's outdated. I'm really hoping that stock Oreo fixes all the imei issues and such.
How does the pixel series do in terms of going back to stock? Google does have full firmware images online, but do they completely restore the phone?

thedr34m13 said:
It it's an original one then I heard wrong, but like you said it's outdated. I'm really hoping that stock Oreo fixes all the imei issues and such.
How does the pixel series do in terms of going back to stock? Google does have full firmware images online, but do they completely restore the phone?
Click to expand...
Click to collapse
Yeah, depends on what we'll get when the Oreo fastboot ROMs come out. I still am not entirely sure what causes the loss of IMEI (would be nice to know to prevent a future repeat), though like you I hope that the updated modems fix those unfortunate IMEI issues.
I think the fastboot images for Pixel devices do let you restore back to stock without wiping data (unless you're coming from a custom ROM, then general advice seems to be a full wipe). Like with our Moto devices, you can do the equivalent of omitting 'fastboot erase userdata' with removing -w in the flashing script: https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
I guess the provision of updated firmware makes it less likely that a user flashes old firmware and then gets hard bricked by an old OTA flashing over a newer bootloader, and also Google appears to prevent you from flashing older firmware anyway: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
That being said, there appear to be some Pixels that have been hard bricked (though looks like hardware failure than flashing something the Pixel didn't like: https://forum.xda-developers.com/pixel/help/pixel-bricked-replaced-phone-returned-t3776752

Stuck in bootloop
I blankflashed the albus bootloader on my potter. But when i flash the stock potter rom, it doesn't boot up and goes into boot loop . Only shows the unlocked bootloader warning again and again. Also i am unable to flash the twrp of either potter or albus. It says unsigned bootloader.
Can u provide the link of the stock rom that u flashed?

[Help Thread][ Moto G7 ](2019) Ask Any Question, Noob Friendly

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Moto G7
2019
​
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"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"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters...
...
...
...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for Moto G7
[Index] Motorola Flashing Utilities and Firmware
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
​

Specs
https://www.phonemore.com/models/motorola/moto-g7/
XT1962-1 Single-sim ..... Canada, USA.
XT1962-4 Dual-sim ....... Latin America, Brazil
XT1962-5 NFC Dual-sim Europe, Various (International)
If you flash an older Firmware than the current version on the phone.
The bootloader needs to be unlocked.
Do not install OTA Updates, they will likely brick the device.
Do not install OTA Updates if
The device is rooted;
A Custom recovery is installed
Firmware was downgrated
FAQs
UnLocking the Bootloader
[GUIDE] unlock your G7 bootloader by mingkee
ReLocking the Bootloader
Back to Stock & ReLock Boot Loader (Google Fi) by vbrtrmn
[Fixing] Baseband <not found> / IMEI=0 / No Network After Flash / Issues
Fixing your Moto stuck in Qualcomm QHSUSB_Bulk or qloader mode
Need a Loader File to unbrick Moto G7. by Phillen13
Loader.img https://mega.nz/#!DXYVTS5C!DKclE5fxKw2TZU5n2-J3f1S1taCTf2BxgdGXDZ7NmmM
Using Lenovo's MOTO Smart Assistant to Update/Repair/Backup
How to fix MOTO G7 / xt1962-1 stuck in Bootloader (stuck in fastboot) unable to boot by sd86
Flashing Firmware and Updates
https://mirrors.lolinet.com/firmware/moto/river/official/
manually update G7 using fastboot by mingkee
xt1962-1/river_amz stock resources (16_7) & tools by sd86
Back to Stock & ReLock Boot Loader (Google Fi) by vbrtrmn
Custom Roms/Recovery/Root/
Root your G7 with Magisk
[ROM][UNOFFICIAL]Lineage OS 16.0
TWRP for Moto G7 (river)
News
https://www.xda-developers.com/moto-g7-moto-g7-play-moto-g7-plus-moto-g7-power-forums/
.

I will be getting G7 for sure (Plus does not have US version) and I am sure it will support T-Mobile VoLTE and Wi-Fi calling like the predecessors.
Hopefully some developer will develop TWRP so well can root it

Does the Moto G7 support hdmi video out on the USB-C port? Thanks!

kaiomatico said:
Does the Moto G7 support hdmi video out on the USB-C port? Thanks!
Click to expand...
Click to collapse
I don't see any specs that say for sure, but I expect it will not as the G6 line did not.

I will be picking up my Moto g7 within the next hour or so and I will begin trying to see how far I can get before I get back to streaming later

Does anybody know how to download full ROM from Moto/Lenovo?
I may try to make patched boot.img for root
I am not gonna make TWRP because I don't know how to do

i just got mine yesterday at best buy. its a great phone compared to the g6. good design, lightweight and smooth Ui.
---------- Post added at 08:11 AM ---------- Previous post was at 08:10 AM ----------
mingkee said:
Does anybody know how to download full ROM from Moto/Lenovo?
I may try to make patched boot.img for root
I am not gonna make TWRP because I don't know how to do
Click to expand...
Click to collapse
each phone has its own partition table soo im not sure? the full rom probably isnt available yet.

Good news: now mine is bootloader unlocked and it's ready to install root
Hopefully somebody can get both original and patched boot.img and/or TWRP for it.

Root is available for open market model.
Let the fun begin

will there be a magisk release for the G7? if so, when will it be released? how long does the development process usually take ?

mingkee said:
Root is available for open market model.
Let the fun begin
Click to expand...
Click to collapse
How do I know if my G7 bought at Best Buy yesterday is "open market"? What other types are there?

maybeme2 said:
How do I know if my G7 bought at Best Buy yesterday is "open market"? What other types are there?
Click to expand...
Click to collapse
I have two
One bought from Best Buy
One bought from B&H
Both are rooted and bootloader unlocked
---------- Post added at 01:01 AM ---------- Previous post was at 01:00 AM ----------
aquinteros said:
will there be a magisk release for the G7? if so, when will it be released? how long does the development process usually take ?
Click to expand...
Click to collapse
Just use the current version to patch boot.img and install Manager

mingkee said:
I have two
One bought from Best Buy
One bought from B&H
Both are rooted and bootloader unlocked
Click to expand...
Click to collapse
So, is the one from Best Buy 'open market'?
More importantly for me, how exactly would I unlock the bootloader and root the G7. Can it be unrooted if necessary? I thought that was all still in development including no twrp recovery available.

maybeme2 said:
So, is the one from Best Buy 'open market'?
More importantly for me, how exactly would I unlock the bootloader and root the G7. Can it be unrooted if necessary? I thought that was all still in development including no twrp recovery available.
Click to expand...
Click to collapse
I have both rooted by patching boot.img with Magisk
Since I downloaded full ROM, I can revert it to clean stock if I want to

So I've been trying to perform a stock update but can't get my device to use magisks OTA ability. So I'm trying to flash the recent OTA with RSD but can't get the program to detect my device. I'm at a loss, would someone be able to help me out?

Which Moto G7 preinstalled apps can be safely disabled? Anyone know?

Omegapsy said:
So I've been trying to perform a stock update but can't get my device to use magisks OTA ability. So I'm trying to flash the recent OTA with RSD but can't get the program to detect my device. I'm at a loss, would someone be able to help me out?
Click to expand...
Click to collapse
RSD only recognize phones with Windows 7. Windows 10 will run RSD but won't recognize any phones (even in compatibility mode)
---------- Post added at 04:36 PM ---------- Previous post was at 04:35 PM ----------
mingkee said:
I have both rooted by patching boot.img with Magisk
Since I downloaded full ROM, I can revert it to clean stock if I want to
Click to expand...
Click to collapse
What is your exact model from BestBuy and BH Photo? Are they the same? Will they both work for Verizon? I assume RETUS or RETAIL? XT1962-1?

HueyT said:
RSD only recognize phones with Windows 7. Windows 10 will run RSD but won't recognize any phones (even in compatibility mode)
Click to expand...
Click to collapse
That's ass. No worries though since I've since managed to learn how to manually apply the packages via fastboot. Thanks for the info.

hueyt said:
rsd only recognize phones with windows 7. Windows 10 will run rsd but won't recognize any phones (even in compatibility mode)
---------- post added at 04:36 pm ---------- previous post was at 04:35 pm ----------
what is your exact model from bestbuy and bh photo? Are they the same? Will they both work for verizon? I assume retus or retail? Xt1962-1?
Click to expand...
Click to collapse
xt1962-1
retus