Database Users

[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 Thread][Moto E4] Ask Any Question, Noob Friendly (2017)

[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?

SM-G9550 Tomato Rom +Factory Bootloader/Tomato Bootloader+Root [Odin]

Hello,
here i upload my Tomato Rom 5.0 inkl Factory Bootloader . That one has no root because i dont know how to root that one. SD load is disabled in recovery but adb stock on boot enabled. If anyone knows how to do this please write me
Tomato Rom inkl Factory BL and Recovery
https://mega.nz/#!JjpzTbDJ!NoFKsh2V-TvAVY2KXpq6306z4SK0SkmlF4Y3QIhO-M0
Tomato Rom 5.0 , That version is untouched the Version from GFan , downloaded from very slow baidu Server in over 4 Hours ---- You can get it here from Mega
https://mega.nz/#!o2JlnD7a!Ftd9O38_xNoNaRjDDmyut24BT61ysw-l-b8iiB452Bo
Factory abl.elf and xbl.elf here from SM-G9550 You can flash this Tar in AP from Odin
https://mega.nz/#!NmZiHJAT!S4Hyiv6qnUWPmlPPJLCmM9jWH5I5aYjNmErA_6uD2ys
you can replace that two with any stock xbl abl from 9550 china/tgy
The next days i will upload all roms for 9550 that exist

Any info about this ROM? Features, ChangeLog, Bugs?

http://bbs.gfan.com/forum.php?mod=v...age=1&filter=typeid&typeid=12871&typeid=12871
from that tomato rom i took the system and replaced it from factory rom
{
"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"
}

@partcyborg @elliwigy what is going on here?
Sent from my SM-G955U using Tapatalk

progro420 said:
@[email protected] what is going on here?
Click to expand...
Click to collapse
I have no idea he was calling it samfail before I asked him to stop. Idk about you guys but that screenshot looks fuzzy and ancient to me. Like the first sampwnd did with eng system and aqcf combo boot.
The eng kernel does NOT boot on our devices. It gives an error of something like "please install user Firmware" if you flash it. I know this first hand. I also know it's NOT public firmware and hasn't been given out anywhere online.
My guess is it's an old combo boot/kernel as those are labeled as "ENG BOOT AND ROOT" all over the internet before the combo factory firmwares were common. If you search XDA you will find threads where elliwigy is *****ing about the exact same issue of people telling him they have eng boot when it's always combo.
In short, I don't believe a word of it . Confident enough in that statement that I'll happily eat crow if he has some magic eng boot that works
Hey maybe it charges to 100% and has unlocked bootloader too! I ???

That Version is for 9550 Versions.
That AP comes from that image:Tomato-G9550-QJ8-v5.0-freeODIN(线刷版)
in the complete Tomato are these Files:
CSC_WIPE_Tomato-G9550-QJ8-v5.0-odin.tar.md5
CSC_Tomato-G9550-QJ8-v5.0-odin.tar.md5
CP_G9550ZCU1AQJ8_CP7863601_CL12302925_QB15438164_REV00_user_low_ship_MULTI_CERT.tar.md5
BL_G9550ZCU1AQJ8_CL12302925_QB15438164_REV00_user_low_ship_MULTI_CERT.tar.md5
AP_Tomato-G9550-QJ8-v5.0-free-odin.tar.md5
Its easy to create Roms for that phone. you can inject Custom System.img in stock AP. You only need to replace them with own System.img.ext4 and only need is to retar it with 7zip. then reflash that with Odin. That method works with 9550 and i bet with 955/950 versions too. I already creating my rom list for 9550 to publish here. These Roms are all from China and the Soul Rom 835 comes with Playstore and prerooted .

012345678 said:
That Version is for 9550 Versions.
That AP comes from that image:Tomato-G9550-QJ8-v5.0-freeODIN(线刷版)
in the complete Tomato are these Files:
CSC_WIPE_Tomato-G9550-QJ8-v5.0-odin.tar.md5
CSC_Tomato-G9550-QJ8-v5.0-odin.tar.md5
CP_G9550ZCU1AQJ8_CP7863601_CL12302925_QB15438164_REV00_user_low_ship_MULTI_CERT.tar.md5
BL_G9550ZCU1AQJ8_CL12302925_QB15438164_REV00_user_low_ship_MULTI_CERT.tar.md5
AP_Tomato-G9550-QJ8-v5.0-free-odin.tar.md5
Its easy to create Roms for that phone. you can inject Custom System.img in stock AP. You only need to replace them with own System.img.ext4 and only need is to retar it with 7zip. then reflash that with Odin. That method works with 9550 and i bet with 955/950 versions too. I already creating my rom list for 9550 to publish here. These Roms are all from China and the Soul Rom 835 comes with Playstore and prerooted .
Click to expand...
Click to collapse
So only works on Chinese variants with unlocked bootloader
Sent from my SM-G955U using Tapatalk

progro420 said:
@[email protected] what is going on here?
Click to expand...
Click to collapse
its clearly listed for G9550 not a USA variant..
partcyborg said:
I have no idea he was calling it samfail before I asked him to stop. Idk about you guys but that screenshot looks fuzzy and ancient to me. Like the first sampwnd did with eng system and aqcf combo boot.
The eng kernel does NOT boot on our devices. It gives an error of something like "please install user Firmware" if you flash it. I know this first hand. I also know it's NOT public firmware and hasn't been given out anywhere online.
My guess is it's an old combo boot/kernel as those are labeled as "ENG BOOT AND ROOT" all over the internet before the combo factory firmwares were common. If you search XDA you will find threads where elliwigy is *****ing about the exact same issue of people telling him they have eng boot when it's always combo.
In short, I don't believe a word of it . Confident enough in that statement that I'll happily eat crow if he has some magic eng boot that works
Hey maybe it charges to 100% and has unlocked bootloader too! I ???
Click to expand...
Click to collapse
you wouldnt get the "fuzzy screen" as with original SamPWND in a screenshot lmao.. most likely his upload or something.. screenshots should always look normal..
either way, not for usa variants as op stated
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
progro420 said:
So only works on Chinese variants with unlocked bootloader
Click to expand...
Click to collapse
yes.. you can see the model in the thread title.....

It works with the us att variant too but I don't trust it knox is 2.8 and says shared device it has systemlink files and they dump your SIM and track u with a virtual SIM

elliwigy said:
its clearly listed for G9550 not a USA variant..
you wouldnt get the "fuzzy screen" as with original SamPWND in a screenshot lmao.. most likely his upload or something.. screenshots should always look normal..
either way, not for usa variants as op stated
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
yes.. you can see the model in the thread title.....
Click to expand...
Click to collapse
Seems it works on at&t also Lol
Look at the post above mine
Sent from my SM-G955U using Tapatalk

This is part of the build prop

Im guessing they attack thu the pre installed google drive intall a update to google sevices , to sideload ****

Hello
So, I have the G-9550 Hong Kong variant.. I bricked it and need to Odin flash firmware back to the phone.. Is this rom safe or no.? If not is there a better alternative. I haven't found anything. I'm in the U.S. on T-mobile. Thanks for your help..!

jdizzle98 said:
So, I have the G-9550 Hong Kong variant.. I bricked it and need to Odin flash firmware back to the phone.. Is this rom safe or no.? If not is there a better alternative. I haven't found anything. I'm in the U.S. on T-mobile. Thanks for your help..!
Click to expand...
Click to collapse
you can reflash, to be sure not get trapped in FRP you need to flash CHINA ABL.elf and XBL.elf
its already the version 6 out.

Mark805 said:
It works with the us att variant too but I don't trust it knox is 2.8 and says shared device it has systemlink files and they dump your SIM and track u with a virtual SIM
Click to expand...
Click to collapse
Virtual Sim is for Samsung Data Store. A Service for Asians. You can connect all over the World with charged virtual Sim

012345678 said:
Virtual Sim is for Samsung Data Store. A Service for Asians. You can connect all over the World with charged virtual Sim
Click to expand...
Click to collapse
FullScreen Photo For V5
https://drive.google.com/file/d/1raRQ0WTuyez3uMrhcurKVyoOsmhqNsFH/view?usp=sharing

kin201303 said:
FullScreen Photo For V5
https://drive.google.com/file/d/1raRQ0WTuyez3uMrhcurKVyoOsmhqNsFH/view?usp=sharing
Click to expand...
Click to collapse
thanks.

SM-G9550 oreo update
Have you recieved the oreo update yet for your SM-G9550. If so could you do a system img and boot img pull so I can port it.
012345678 said:
Hello,
here i upload my Tomato Rom 5.0 inkl Factory Bootloader . That one has no root because i dont know how to root that one. SD load is disabled in recovery but adb stock on boot enabled. If anyone knows how to do this please write me
Tomato Rom inkl Factory BL and Recovery
https://mega.nz/#!JjpzTbDJ!NoFKsh2V-TvAVY2KXpq6306z4SK0SkmlF4Y3QIhO-M0
Tomato Rom 5.0 , That version is untouched the Version from GFan , downloaded from very slow baidu Server in over 4 Hours ---- You can get it here from Mega
https://mega.nz/#!o2JlnD7a!Ftd9O38_xNoNaRjDDmyut24BT61ysw-l-b8iiB452Bo
Factory abl.elf and xbl.elf here from SM-G9550 You can flash this Tar in AP from Odin
https://mega.nz/#!NmZiHJAT!S4Hyiv6qnUWPmlPPJLCmM9jWH5I5aYjNmErA_6uD2ys
you can replace that two with any stock xbl abl from 9550 china/tgy
The next days i will upload all roms for 9550 that exist
Click to expand...
Click to collapse

012345678 said:
you can reflash, to be sure not get trapped in FRP you need to flash CHINA ABL.elf and XBL.elf
its already the version 6 out.
Click to expand...
Click to collapse
please where to get that and how to flash? i cant flash anything to s8+ with HK firmware. it is giving me binary blocked by frp. No oem unlock, bl unlocked with crom already, google account removed, but still cant flash twrp or patched boot or whatever custom.

Meizu 16 global root?

Hello.
Is it possible to do root on the global version of flyme 7 for meizu 16?

Do you have news ? Thanks you

INTseed said:
Hello.
Is it possible to do root on the global version of flyme 7 for meizu 16?
Click to expand...
Click to collapse
Not via the built-in settings since Meizu has disabled the root feature (although you might still see it)
I am not going to try, but if you wanna risk it, you can try Kingoroot (beware, contains maleware)
Besides root, I would love a twrp version for the 16th.

So, appears that I've bought meizu right in time, when rooting is all pain again! lol hell, I was hoping that this time I won't need to scratch my brain untill it bleeds haha
No news meantime? Need to wait for someone to solve that rooting 16th stuff?

I'm waiting for root also.
I have asked meizu seller on AliExpress but so far they didn't respond to it

fatjoez said:
I'm waiting for root also.
I have asked meizu seller on AliExpress but so far they didn't respond to it
Click to expand...
Click to collapse
I'm sorry but they are the most unlikely people to help you out with this.
You will have to wait for either a twrp or a release of the root option restriction in an upcoming flymeOS update.
Since both options are rather unlikely to happen soon, you might be stuck with unrooted stock for a while. Sorry.

I've heard that there are succesfull tests of unlocking and flashing twrp done already! They aren't letting it go public yet tho.

Hi. Got my white global few days ago. This is good news.
Where to follow these news? Patiently waiting for root and xposed-magisk.

meizu16th-user said:
Hi. Got my white global few days ago. This is good news.
Where to follow these news? Patiently waiting for root and xposed-magisk.
Click to expand...
Click to collapse
Yeah, I'm waiting for using tweaks too. I've read about it at 4pda.ru but nothing certain besides someone varified there is a tested way but it will take time till it goes public.
I believe you can just check on here, it will pop up eventually since xda is the biggest android dev solutions pool as far as I know.
If I'll read anything new at 4pda, I'll post it here.

Also watching 4pda.ru for news.
Flashed Chinese firmware, applied for root through painfull online application and waiting for root authorization code.
Phone runs great, chinese firmware is ok, everything is in english and completely usable.

meizu16th-user said:
Also watching 4pda.ru for news.
Flashed Chinese firmware, applied for root through painfull online application and waiting for root authorization code.
Phone runs great, chinese firmware is ok, everything is in english and completely usable.
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?showtopic=905401&st=3860#entry78128995
Hm, may be I should switch to cn version also But I don't have that many bugs, only common. Thanks for the idea anyway! Somewhy didn';t think of that.

Successfully rooted. Chinese firmware. Titanium backup working.
Will post a complete tutorial and share links.
Few more posts - newbie account.

Found a little tweak for mback.
Installed gravitybox for oreo in xposed.
In navigation keys actions enabled double tap action to home for all keys ( menu, home, back, recents). Will explore more which one is responsible...
Now when i double tap mback it goes to home.
Reason, sometimes its hard to press mback to go home when you are holding phone with one hand. And when surfing in browser it goes back and you lose current page..
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
Anyone with russian language knowledge.
There are flymetools for flyme 7 on 4pda ru. Cant register and download because of russian captcha.
Flymetools is and xposed module for tweaking flymeos.

meizu16th-user said:
Anyone with russian language knowledge.
There are flymetools for flyme 7 on 4pda ru. Cant register and download because of russian captcha.
Flymetools is and xposed module for tweaking flymeos.
Click to expand...
Click to collapse
PM me the link, I'll get it for you.
PS I'm using gesture system, it's pretty ok to me so far.
PPS chinese version runs ok? No special bugs and all? Wonder if there will be a way to add more languages, never used flyme before... Not sure I want to keep using english all the time.

Thanks everyone. can you please PM me guide for chinese firmware.
The russians use Global firmware right? If they have root maybe we can get it soon on global firmware rooted

deleater said:
PM me the link, I'll get it for you.
PS I'm using gesture system, it's pretty ok to me so far.
PPS chinese version runs ok? No special bugs and all? Wonder if there will be a way to add more languages, never used flyme before... Not sure I want to keep using english all the time.
Click to expand...
Click to collapse
Hi.
Exploring combination of mback and xposed egde gestures. So far so god.
Chinese version runs ok. I have frozen few chinese apps i really do not need and the rest is ok. In chinese firmware there are only english and chinese system language - so you know.
---------- Post added at 10:20 PM ---------- Previous post was at 10:10 PM ----------
fatjoez said:
Thanks everyone. can you please PM me guide for chinese firmware.
The russians use Global firmware right? If they have root maybe we can get it soon on global firmware rooted
Click to expand...
Click to collapse
Not sure about RU firmware root. I would say no because members of 4pda ru are aslo switching to chinese firmware to get root...
Quick chinese firmware flash tutorial:
Go to flyme cn. Find firmware for meizu 16th . Download latest A version.
Site is slow but downloading update was ok.
Copy update.zip and copy to your phone.
Shut down.
Power on + Volume up.
You will boot into stock recovery.
Update and clear data.
Wait 5 minutes.
Done.
Root is another story. PM google translate link.

please could we have the step by step procedure?
meizu16th-user said:
Also watching 4pda.ru for news.
Flashed Chinese firmware, applied for root through painfull online application and waiting for root authorization code.
Phone runs great, chinese firmware is ok, everything is in english and completely usable.
Click to expand...
Click to collapse
Please could we have the step by step procedure?
Why do we need to install the Chinese firmware - why does it not work with the global version?
Could we please also list the bugs people are observing (ideally needs a separate thread)

jam_27 said:
Please could we have the step by step procedure?
Why do we need to install the Chinese firmware - why does it not work with the global version?
Could we please also list the bugs people are observing (ideally needs a separate thread)
Click to expand...
Click to collapse
I think this is my 10th post. Now i can? post links. Will write a complete tutorial in english with links.
Meizu made it only possible for chinese firmware to have root so far. Period.
My only bug so far is that camera sometimes shows a message that by turning on wifi scaning something something... i always click cancel, didnt have time to explore yet.
Yes a separate thread and section would be nice. You can vote, comment, make a request somewhere on the forum...
Test, can i share links and images... Google play with chinese A firmware.
{
"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"
}
Yes i can...

meizu16th-user said:
I think this is my 10th post. Now i can? post links. Will write a complete tutorial in english with links.
Meizu made it only possible for chinese firmware to have root so far. Period.
Click to expand...
Click to collapse
OK, is there a way to backup my Global Rom before I install the chinese firmware ?
link to chinese firmware - v7.1.1.2A
link to manual firmware upgrade. Could someome please detail this in English?
My 16th is on its way, but those could who already have the global version confirm if they have the current ROM (Flyme 7.1.1.0G) as listed here?

jam_27 said:
OK, is there a way to backup my Global Rom before I install the chinese firmware ?
Click to expand...
Click to collapse
Dont know.
There is google backup. I have not tried.