Related
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.
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.
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
[Moto E4](2017)
Including, but not limited to
XT1763
XT1766
XT1767
XT1768
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 Device Thread link
Index for Device Thread Link
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
I'm not planning on adding every Rom or Mod,
but if you have a suggestion for other links
Please post them here.
Mediatek MT6737 Models
XT1763 Dual-Sim (MediaTek), (Brazil)
XT1766 (Europe); Singe-Sim
Qualcomm Snapdragon 427
XT1767
Qualcomm® Snapdragon™ 425
XT1768
Specs
https://www.gsmarena.com/motorola_moto_e4-8721.php
https://www.phonearena.com/phones/Motorola-Moto-E4_id10485/fullspecs
FAQs
Unbricking
https://forum.xda-developers.com/moto-e4/how-to/e4-sprint-xt1766-unbrick-easy-sdcard-t3833408
UnLocking the Bootloader
ReLocking the Bootloader
[Fixing] Baseband <not found> / IMEI=0 / No Network After Flash / Issues
Fixing your Moto stuck in Qualcomm QHSUSB_Bulk or qloader mode
https://forum.xda-developers.com/mo...blankflash-motorola-moto-e4-qualcomm-t3830983
Using Lenovo's MOTO Smart Assistant to Update/Repair/Backup
Custom Roms/Recovery/Root/
Firmware
https://mirrors.lolinet.com/firmware/moto
[Index]Motorola Flashing Utilities, Firmware, and more
I'm not a noob but I need help rooting my phone
mendelgordon said:
I'm not a noob but I need help rooting my phone
Click to expand...
Click to collapse
no root method yet, that I know of
sd_shadow said:
no root method yet, that I know of
Click to expand...
Click to collapse
So how did mer2017 root his? I have the unlocked US version and I already unlocked the bootloader, but SuperSU and all the other root things I tried don't work, I wrote in the root question thread all the things I tried.
Use Moto E³'s TWRP Recovery 3.1.0-0.
Download the twrp XDA forum or bit.ly/motoE3p
If the Amazon ads version bootloader can't be unlocked, will there ever be a way to root it? I know people have had success with the Blu R1 HD and Moto G4 play prime variants.
jnorth159 said:
If the Amazon ads version bootloader can't be unlocked, will there ever be a way to root it? I know people have had success with the Blu R1 HD and Moto G4 play prime variants.
Click to expand...
Click to collapse
Rooting is Unlikely with a locked bootloader
Sent from my sailfish using XDA Labs
Why aren't we able to run a script from the phone to boot twrp since we can't get it flashed? Why do I need a PC every time if we have root?
mendelgordon said:
Why aren't we able to run a script from the phone to boot twrp since we can't get it flashed? Why do I need a PC every time if we have root?
Click to expand...
Click to collapse
Because a version of TWRP built for the E4 hasn't been created yet. The version of TWRP for the G5+ just happens to be compatible enough to boot and root.
xtermmin said:
Because a version of TWRP built for the E4 hasn't been created yet. The version of TWRP for the G5+ just happens to be compatible enough to boot and root.
Click to expand...
Click to collapse
I know that, what I'm asking is, if I can normally use an app (kernel adiutor for example) to boot to twrp and flash something automatically, why can't I use another app to reboot to the bootloader and run fastboot boot twrp.img? When you update your phone it reboots to the bootloader and flashes the update...
Friends, moto e4 locked on Verizon has fcc id IHDT56WC1 and I'm totally noob. Can someone aware on how to find if this phone has GSM support could do so please? So we may close further to unlock it like moto e, e2 or rest Verizon models. Thanks.
What functions of the G5 TWRP fully work on the E4? Does backup and restore work fully? Are there any TWRP stock resources available? By stock resources I mean system backup, etc. I ask cause I'm waiting for stock firmware files to download and I can't yet test this for myself.
So I've been good and rooted for weeks and then I went to flash TWRP and re-root using Magisk. Magisk keeps failing now so I was going to start over from scratch but I don't want to pull the wrong firmware. My E4 is a XT1768 I got from Republic Wireless. Shows its a NA Retail version running NPQ26.69-41. Anyone know which file to pull? I'm guessing the CID 50 version vs. the AMZ CID 18 version, but I've had to flash the AMZ versions before to fix other non-Amazon Motos. Any help appreciated.
vettejock99 said:
So I've been good and rooted for weeks and then I went to flash TWRP and re-root using Magisk. Magisk keeps failing now so I was going to start over from scratch but I don't want to pull the wrong firmware. My E4 is a XT1768 I got from Republic Wireless. Shows its a NA Retail version running NPQ26.69-41. Anyone know which file to pull? I'm guessing the CID 50 version vs. the AMZ CID 18 version, but I've had to flash the AMZ versions before to fix other non-Amazon Motos. Any help appreciated.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=889764386195915160
mendelgordon said:
https://androidfilehost.com/?fid=889764386195915160
Click to expand...
Click to collapse
Thanks! That one worked great! Now to start over...
vettejock99 said:
Thanks! That one worked great! Now to start over...
Click to expand...
Click to collapse
It takes me about two hours (I had to do it many times since I got this phone, since the original E4 I got had ghost touch issues so customer service made me factory reset it multiple times). I'm now on my second E4 but I'm thinking of getting a third, since the fingerprint sensor is quitting on me sometimes (completely ignoring touches, not just saying fingerprint not recognized, and the one touch navbar thing also not working).
mendelgordon said:
It takes me about two hours (I had to do it many times since I got this phone, since the original E4 I got had ghost touch issues so customer service made me factory reset it multiple times). I'm now on my second E4 but I'm thinking of getting a third, since the fingerprint sensor is quitting on me sometimes (completely ignoring touches, not just saying fingerprint not recognized, and the one touch navbar thing also not working).
Click to expand...
Click to collapse
I've actually been hearing about this quite a bit, kind of makes me glad mine doesn't have a finger print scanner.
Sent from my Moto E (4) using XDA Labs
mendelgordon said:
...the fingerprint sensor is quitting on me sometimes (completely ignoring touches, not just saying fingerprint not recognized, and the one touch navbar thing also not working).
Click to expand...
Click to collapse
Restarting fixed this, no clue why.
I don't see any threads that apply to the XT1765 (Metro PCS), searching finds no results, is there a way to root this phone?
HEY FRIENDS, I THINK I WAS IN MARCH SECURITY PATCH LEVEL WHEN I THOUGHT TO UNLOCK BOOTLOADER AND TO ROOT MY XT1643. I SUCCESSFULLY UNLOCKED BOOTLOADER AND WHILE I WAS TRYING TO ROOT BY FLASHING SUPERSU ZIP FILE I LOST MY HANDSETS SOFTWARE. AFTER THAT I FLASHED CUSTOM ROM FOR MY PHONE. I HATED CUSTOM ROM SO I DECIDED TO GET BACK TO STOCK. I FLASHED MY ROM FROM HERE https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
I WANT TO KNOW THAT IS IT DOWNGRADED ROM??
AFTER I FLASHED THIS MY HANDSET IS SHOWING UPDATE , SO I UPDATED. WHILE INSTALLING UPDATE MY PHONE GOT BRICKED.
CAN I USE BLANK FLASH FOR MARCH SECURITY PATCH LEVEL. IF YES CAN ANYONE PROVIDE ME LINK FOR THE BLANK FLASH.
PLZZ IT'S HUMBLE REQUEST.
If you genuinely were on the March 2017 security patch before, try this: https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
echo92 said:
If you genuinely were on the March 2017 security patch before, try this: https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
Click to expand...
Click to collapse
bro , my friend have the same phone. i checked on his phone that it is in march security level.his phone is updated. i think that i m too in march security patch level.
bro i checked the above link the blank flash file they have is of npj95.93.11. but i was in newer version of march security patch level.
ADITYA_KUMAR said:
bro , my friend have the same phone. i checked on his phone that it is in march security level.his phone is updated. i think that i m too in march security patch level.
Click to expand...
Click to collapse
Well, did the blankflash work, then?
By the way, it looks like the June update should have arrived in India: https://forum.xda-developers.com/showpost.php?p=72985910&postcount=61
echo92 said:
Well, did the blankflash work, then?
Click to expand...
Click to collapse
nope bro:crying::crying:
i flashed npj25.93-14. now i need to know which version's update i installed.
sorry for bad english
echo92 said:
Well, did the blankflash work, then?
By the way, it looks like the June update should have arrived in India: https://forum.xda-developers.com/showpost.php?p=72985910&postcount=61
Click to expand...
Click to collapse
i don't think so bro. because today i checked my friends phone. it is showing march security patch level. and his system is up to date.
{
"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"
}
ADITYA_KUMAR said:
nope bro:crying::crying:
i flashed npj25.93-14. now i need to know which version's update i installed.
sorry for bad english
Click to expand...
Click to collapse
Ah, that's a problem - we don't have another blankflash to try (and it looks like you tried all the others).
I understand you don't have much data, does look like downgrading and taking the OTA hard bricked your device unfortunately. Only resolutions are to have your device repaired (probably with a motherboard replacement) or saving up for a new device.
echo92 said:
Ah, that's a problem - we don't have another blankflash to try (and it looks like you tried all the others).
I understand you don't have much data, does look like downgrading and taking the OTA hard bricked your device unfortunately. Only resolutions are to have your device repaired (probably with a motherboard replacement) or saving up for a new device.
Click to expand...
Click to collapse
can u provide me 93.14-4 gpt.bin and bootloader.img plzz
echo92 said:
Ah, that's a problem - we don't have another blankflash to try (and it looks like you tried all the others).
I understand you don't have much data, does look like downgrading and taking the OTA hard bricked your device unfortunately. Only resolutions are to have your device repaired (probably with a motherboard replacement) or saving up for a new device.
Click to expand...
Click to collapse
I also want to know that what is the version of update that has been installed if i am in npj93.14. If the update i got is of npj93.14-4 then genuinly i am in march security patch level. plzz help
ADITYA_KUMAR said:
I also want to know that what is the version of update that has been installed if i am in npj93.14. If the update i got is of npj93.14-4 then genuinly i am in march security patch level. plzz help
Click to expand...
Click to collapse
You flashed the December 2016 update:
NPJ25.93-14: December 2016 security update, B1:03 bootloader
NPJS25.93-14-4: March 2017 security update, B1:05 bootloader
NPJS25.93-14-8: June 2017 security update, B1:06 bootloader.
I don't know how much use it'll be, but I've uploaded the NPJS25.93-14-4 bootloader and GPT to here: https://drive.google.com/drive/folders/0B-GUyOfb8OgzR1VrQ1NHWDVmWE0
Name: NPJS25_93_14_4_gpt_bootloader.zip
Extracted bootloader and gpt:
gpt.bin -
size: 32KB
md5 checksum:be97a48f5ab36009b8c5e5bd55453f1e
Bootloader -
size: 3.56 MB
md5 checksum: 2f7a44bba145811bb6cd4267d6d19805
echo92 said:
You flashed the December 2016 update:
NPJ25.93-14: December 2016 security update, B1:03 bootloader
NPJS25.93-14-4: March 2017 security update, B1:05 bootloader
NPJS25.93-14-8: June 2017 security update, B1:06 bootloader.
I don't know how much use it'll be, but I've uploaded the NPJS25.93-14-4 bootloader and GPT to here: https://drive.google.com/drive/folders/0B-GUyOfb8OgzR1VrQ1NHWDVmWE0
Name: NPJS25_93_14_4_gpt_bootloader.zip
Extracted bootloader and gpt:
gpt.bin -
size: 32KB
md5 checksum:be97a48f5ab36009b8c5e5bd55453f1e
Bootloader -
size: 3.56 MB
md5 checksum: 2f7a44bba145811bb6cd4267d6d19805
Click to expand...
Click to collapse
thnk u bro
is there anyhope of getting updated blankflash?
ADITYA_KUMAR said:
thnk u bro
is there anyhope of getting updated blankflash?
Click to expand...
Click to collapse
Unless somehow Motorola has generated a newer blankflash from one of their engineering teams, and we can get hold of said blankflash (via a leak), it's very unlikely.
As I understand it, you need a singleimage which includes the correct partition structure and key files which include the programmer. The programmer can't be altered as it needs to be signed by Motorola, presumably to ensure whatever is flashed is cryptographically signed by the right certificate, else we could flash anything to the chips. Even if we could make a new singleimage, the programmer could be checking the bootloader on your device to check if you can flash. (e.g. like here: https://forum.xda-developers.com/showpost.php?p=62191317&postcount=2112)
It could happen (though this is just speculation) that when Android O is released, Motorola generates a new blankflash (like was done for Nougat), however, that might depend on if our device is even in production at that time...
Either way, the resolution would have to come from Motorola, either a leak or a new motherboard.
echo92 said:
Unless somehow Motorola has generated a newer blankflash from one of their engineering teams, and we can get hold of said blankflash (via a leak), it's very unlikely.
As I understand it, you need a singleimage which includes the correct partition structure and key files which include the programmer. The programmer can't be altered as it needs to be signed by Motorola, presumably to ensure whatever is flashed is cryptographically signed by the right certificate, else we could flash anything to the chips. Even if we could make a new singleimage, the programmer could be checking the bootloader on your device to check if you can flash. (e.g. like here: https://forum.xda-developers.com/showpost.php?p=62191317&postcount=2112)
It could happen (though this is just speculation) that when Android O is released, Motorola generates a new blankflash (like was done for Nougat), however, that might depend on if our device is even in production at that time...
Either way, the resolution would have to come from Motorola, either a leak or a new motherboard.
Click to expand...
Click to collapse
hey @echo92, i am thinking that qboot can detect our device as qualcomm loader something. but mfastboot can't do it. can we
make qboot to directly flash gpt.bin and bootloader.img? It's just an idea of desperate mind.
ADITYA_KUMAR said:
hey @echo92, i am thinking that qboot can detect our device as qualcomm loader something. but mfastboot can't do it. can we
make qboot to directly flash gpt.bin and bootloader.img? It's just an idea of desperate mind.
Click to expand...
Click to collapse
The fact fastboot can't detect further supports the idea the bootloader is corrupted (as I understand it, fastboot communicates directly with the bootloader). From what I've been reading, looks like you'd need to use the sahara protocol - possibly within qboot? - to communicate (https://github.com/openpst/sahara) and valid, signed programmer files for the hard coded primary bootloader to accept a flash (http://vm1.duckdns.org/Public/Qualcomm-Secure-Boot/Qualcomm-Secure-Boot.htm). Unfortunately, the blankflash we have, even though it appears to fulfil both those criteria, isn't accepted (maybe because the programmer is detecting the bootloader is newer than the expected version)
echo92 said:
The fact fastboot can't detect further supports the idea the bootloader is corrupted (as I understand it, fastboot communicates directly with the bootloader). From what I've been reading, looks like you'd need to use the sahara protocol - possibly within qboot? - to communicate (https://github.com/openpst/sahara) and valid, signed programmer files for the hard coded primary bootloader to accept a flash (http://vm1.duckdns.org/Public/Qualcomm-Secure-Boot/Qualcomm-Secure-Boot.htm). Unfortunately, the blankflash we have, even though it appears to fulfil both those criteria, isn't accepted (maybe because the programmer is detecting the bootloader is newer than the expected version)
Click to expand...
Click to collapse
Bro, i want to know more about programmer.mbn ,where can i find about it? Can we upgade the programmer version(by taking help from new rom) without affecting the signature and certificate. I am new to programming and all this, so sorry for silly talks
ADITYA_KUMAR said:
Bro, i want to know more about programmer.mbn ,where can i find about it? Can we upgade the programmer version(by taking help from new rom) without affecting the signature and certificate. I am new to programming and all this, so sorry for silly talks
Click to expand...
Click to collapse
I'm not sure where to find more info about the programmer.mbn, you could have a look at the other Moto forums where they've had similar hard bricks occur and have tried/trying the same things as us: https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492 https://forum.xda-developers.com/moto-g/general/generating-singleimage-bin-t3008047
But as far as I understand it, you cannot change anything within the programmer without affecting the signature (others have tried in the other unbricking thread that's running: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016/page17 ). We'd likely need an updated programmer.mbn/blankflash straight from Motorola, and as we're not supposed to have these tools, Motorola will likely say no to any request, unfortunately, and just refer you to a service centre for repairs.
echo92 said:
I'm not sure where to find more info about the programmer.mbn, you could have a look at the other Moto forums where they've had similar hard bricks occur and have tried/trying the same things as us: https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492 https://forum.xda-developers.com/moto-g/general/generating-singleimage-bin-t3008047
But as far as I understand it, you cannot change anything within the programmer without affecting the signature (others have tried in the other unbricking thread that's running: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016/page17 ). We'd likely need an updated programmer.mbn/blankflash straight from Motorola, and as we're not supposed to have these tools, Motorola will likely say no to any request, unfortunately, and just refer you to a service centre for repairs.
Click to expand...
Click to collapse
Bro, may i use qpst tool or mtk tool for flashing stock rom directly.
ADITYA_KUMAR said:
Bro, may i use qpst tool or mtk tool for flashing stock rom directly.
Click to expand...
Click to collapse
No idea onto how to use those tools, sorry. I only know a little bit when it comes to unbricking devices and the fact that there's a lot of old/unhelpful information around regarding unbricking doesn't help.
echo92 said:
No idea onto how to use those tools, sorry. I only know a little bit when it comes to unbricking devices and the fact that there's a lot of old/unhelpful information around regarding unbricking doesn't help.
Click to expand...
Click to collapse
Thank you bhai(hindi for brother), i think you are a genius :good: . i have only one phone and have a low budget so i am going to repair it. plzz keep posting me with updates regarding unbricking. Again thanku so much brother.
Hi ! I was using custom roms on my phone then I switched back to stock nd also I relocked my bootloader but after that I cant update it to .67 version I am on .35 version. I am from India and everyone has received OTA for .67 version but mine doesnt shows any update. Any help ?
Sent from my Moto G (5) Plus using Tapatalk
deepu28792 said:
Hi ! I was using custom roms on my phone then I switched back to stock nd also I relocked my bootloader but after that I cant update it to .67 version I am on .35 version. I am from India and everyone has received OTA for .67 version but mine doesnt shows any update. Any help ?
Click to expand...
Click to collapse
Same problem here.
You'd have to be on the NPN25.137-15 firmware to have received the .67 update - if you're on the retin software channel, I think the .35 version is the incorrect one for your channel (.35 is for US devices, if I recall). Therefore, you'll likely not get any updates, and if you were to flash the NPNS25.137-35-5 update, may mean you cannot downgrade in future.
If you're on the retin channel and want the .67 update, then unfortunately you'll likely have to unlock your bootloader (wiping your device) then attempt to flash NPN25.137-15 (do your research first and ensure this does not brick your device), then you should be able to update to NPN25.137-67. As far as I know, there is no fastboot ROM currently for NPN25.137-67 so re-locking the bootloader is not possible at the moment.
echo92 said:
You'd have to be on the NPN25.137-15 firmware to have received the .67 update - if you're on the retin software channel, I think the .35 version is the incorrect one for your channel (.35 is for US devices, if I recall). Therefore, you'll likely not get any updates, and if you were to flash the NPNS25.137-35-5 update, may mean you cannot downgrade in future.
If you're on the retin channel and want the .67 update, then unfortunately you'll likely have to unlock your bootloader (wiping your device) then attempt to flash NPN25.137-15 (do your research first and ensure this does not brick your device), then you should be able to update to NPN25.137-67. As far as I know, there is no fastboot ROM currently for NPN25.137-67 so re-locking the bootloader is not possible at the moment.
Click to expand...
Click to collapse
I downgraded my phone from .35 to .15 version and now I have received OTA and have successfully updated to .67 version.
Sent from my Moto G (5) Plus using Tapatalk
deepu28792 said:
I downgraded my phone from .35 to .15 version and now I have received OTA and have successfully updated to .67 version.
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Please provide instructions for this, I am unable to downgrade.
earlycray said:
Please provide instructions for this, I am unable to downgrade.
Click to expand...
Click to collapse
Its really simple. Just download the firmware .15 from the link below and flash it. If you have already re-locked ur bootloader thn flash the full firmware and if not yet unlocked use the commands provide in the thread. The .15 version shows for Brazil but it works with our Indian version too. Try it I did the same.
https://forum.xda-developers.com/showthread.php?t=3638835
Press thanks if I helped you.
deepu28792 said:
Its really simple. Just download the firmware .15 from the link below and flash it. If you have already re-locked ur bootloader thn flash the full firmware and if not yet unlocked use the commands provide in the thread. The .15 version shows for Brazil but it works with our Indian version too. Try it I did the same.
https://forum.xda-developers.com/showthread.php?t=3638835
Press thanks if I helped you.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am receiving this error. I was previously on NPNS25.137-35-5.
earlycray said:
I am receiving this error. I was previously on NPNS25.137-35-5.
Click to expand...
Click to collapse
then you cant downgrade. I thought you were on .35, I have read it somewhere that if u r on .35-5 then you cannot downgrade
Sent from my Moto G (5) Plus using Tapatalk
deepu28792 said:
then you cant downgrade. I thought you were on .35, I have read it somewhere that if u r on .35-5 then you cannot downgrade
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
I will have to wait for full image of -67 to upgrade, correct ?
earlycray said:
I will have to wait for full image of -67 to upgrade, correct ?
Click to expand...
Click to collapse
I'm not even sure if you can flash the NPN25.137-67 image even, MarckozZ downgraded from NPNS25.137-35-5 to NPN25.137-15 and attempted to take the OTA to NPN25.137-67, which hard bricked their device. https://forum.xda-developers.com/showpost.php?p=73029820&postcount=70
Though they were able to recover their device, it looks like updating is very risky/not possible after the recovery: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
Now, the fastboot of NPN25.137-67 might not let you flash the GPT and bootloader over the NPNS25.137-35-5 and let you flash the rest of the OS, but that's asking for trouble when an OTA arrives - hopefully the OTA scripts would check for a bootloader/GPT mismatch, but they may not and you could run into a hard brick.
echo92 said:
the fastboot of NPN25.137-67 might not let you flash the GPT and bootloader over the NPNS25.137-35-5
Click to expand...
Click to collapse
Wow. I dun goofed. What are my options at this point? Also, could you kindly please explain the above ?
earlycray said:
Wow. I've done goofed. What are my options at this point? Also, could you kindly please explain the above ?
Click to expand...
Click to collapse
As I understand it, fastboot has checks built in that communicate with the bootloader and verify whether the GPT/bootloader of the firmware you're attempting to flash can be flashed. If you have a newer bootloader on your device, then your bootloader may refuse to permit the flash of the older bootloader (especially with the NPNS25.137-35-5 update, which appears to have a critical security bug fixed in the May 2017 patch, so downgrading would allow you to re-open that bug, which Motorola wouldn't want).
Now, you can get around this, in theory, by omitting GPT and bootloader from your fastboot flash, so fastboot may flash the rest of your system. However, now you'll have a NPN25.137-67 system, but a GPT/bootloader from NPNS25.137-35-5. Though this should run, it becomes very risky if you choose to install an OTA and forget you have this mismatch; the OTA will think you have the NPN25.137-67 firmware and patch accordingly, which may seriously corrupt your bootloader. In that case, you'll have to use a blankflash to recover your device (if it works) and be unable to recover your data, unless it was held on a SD card mounted in portable storage. I've seen similar scenarios occur with the Moto G4 (luckily we've just got a new blankflash to recover from the June 2017 security patch) and with the Moto Z Play.
In summary, you could flash the NPN25.137-67 firmware when it comes out, but the mismatch makes updates very risky - I personally wouldn't use the fastboot updates in this situation. You might wish to look into the TWRP flashables of the NPN25.137-67, as they'll update the system side of things (and most if not all the functions of your device should work as though you were still on stock NPN25.137-67), but without the risk of bricking your device. Granted, you'll have to unlock and flash TWRP in this situation though, and you will no longer be able to flash OTA updates, though hopefully the TWRP flashable maintainer will update the TWRP flash file to the newest OTA.
I'm not aware of other options besides keeping an eye out for NPNS25.137-35-5 updates, unfortunately, as your device is off the official update path Later on, Motorola may unify firmware updates into one global file, but for the time being, just be careful (and also be aware that the patch situation is a bit confusing!). On the other hand, at least you've got a May security patch
If I simply stuck to the current firmware, what would happen? The NFC chip appears to be working even tho this is the us? Model.
earlycray said:
If I simply stuck to the current firmware, what would happen? The NFC chip appears to be working even tho this is the us? Model.
Click to expand...
Click to collapse
Hang on, which model of the Moto G5 Plus are you using?
Cause depending on the model, you might actually be on the right firmware and not need the -67 update (which is usually only for retin, Indian retail) devices...
To clarify, as far as I know:
retin (I think retla too?) devices should be on NPN25.137-67 (March 2017 security patch)
retus devices should be on NPNS25.137-33-5 (May), NPNS25.137-35-5 (May) or NPN25.137-43-5 (Verizon specific, March)
reteu devices should be on NPNS25.137-33-5 (May)
From your previous posts you've got a XT1685?
That is correct. However it was purchased in Australia. And judging by some Australian tech forums the latest fw is -67.