Are you sick of searching through a 200 page thread over one topic just to find the download link to the newest thread?
Well over at allshadow.com I have compiled all of the information of the Firmwares and update everyone on the newest builds
Sure there's a sticky of a chart but how could a chart help you find the newest updates?
http://allshadow.com/forum/viewtopic.php?f=9&t=5692
links down man.
That fast? Re updating
Mast3rmatt said:
Are you sick of searching through a 200 page thread over one topic just to find the download link to the newest thread?
Well over at allshadow.com I have compiled all of the information of the Firmwares and update everyone on the newest builds
Sure there's a sticky of a chart but how could a chart help you find the newest updates?
http://http://allshadow.com/forum/viewtopic.php?f=9&t=5692&p=40416#p40416
Click to expand...
Click to collapse
Edit: since you got it fixed
*sigh*
Try this: http://allshadow.com/forum/viewtopic.php?f=9&t=5692&p=40416
You got one too many "http"s in there, turbo.
nice work. I like how everything is there for newbies to go by without posting multiple topics.
This would be a nice sticky or a reference site to point all questions about firmware to.
I fixed, i sorta found that out.
Do you want me to port this thread over? It wont take that long?
You don't mention the holiday firmware for both us and eu
n0ahg said:
You don't mention the holiday firmware for both us and eu
Click to expand...
Click to collapse
What do you mean? This is the most recent firmware's
I will add those in a sec
I'm currently running the following
signed-dream_gfh_eu-ota-147201.ea8cd686.zip
updated with
signed-gfh_eu-CRB43-from-CRB21.62e94a26.zip
(update is signed-gfh-CRB43-from-CRB21.c88b03d2.zip for us)
I don't know the name of the eu CRB43 file without upgrading though if there is one :-(
Basically this is the nearest I can get to a non t-mobile adp like firmware for europe, unless you know of another ;-)
Please don't let this thread go to waste.
I agree completely. A thread called 'Everything about Firmwares' with incomplete information would be a waste ;-)
n0ahg said:
I agree completely. A thread called 'Everything about Firmwares' with incomplete information would be a waste ;-)
Click to expand...
Click to collapse
Well I was only giving information on the newest builds, sorta waste of your time if you flash RC30, who in the world would do that? I will update to make everyone happier.
Who would want to flash RC30 when a) I'm in europe and b) RCB43 gfh is out?
[None]
This thread has Great Info for new Android Users, let's try to keep it alive don't just trash it with off topic posts. Great Job Matt
I'm not trashing the thread, just trying to make sure the information is complete as it would be great to have it all in one place
Anything else you want me to add> I just added all the older builds and added some new sections on User Created Firmware Changes. Thanks for the Props
Hello
I have this eZee'Tab785D11-M by Storex (I cant find it anymore in storex website ).
Ive tried to find in the forum, but could find anything for this specific model.
Im looking for a way to proper root it and unroot if I need later. And update the android version if possible.
I haven't tried any method cuz Im new to this and I dont wanna brick it.
The specifications are the followoing
Processor: 1,2GHz Dual Core
Ram: 1Gb
Android Version: 4.2.2
Size: 7,85 inches
Resolution: 1024x768 (4:3 LCD)
Hi,
I can't find anything on XDA about your device, but one of the first 2 for methods in this directory may possibly work for you.... Use at your own risk of course,
XDA Root Directory
As far as a newer android version goes.... Unless someone stays development for your device, you will probably have to wait for the manufacturer to update you.... Assuming they do.
Good luck!
---------- Post added at 08:54 AM ---------- Previous post was at 08:43 AM ----------
If those methods don't work out for you, you will need to ask for help here....
> General discussion > Questions and Answers
KJ said:
Hi,
I can't find anything on XDA about your device, but one of the first 2 for methods in this directory may possibly work for you.... Use at your own risk of course,
XDA Root Directory
As far as a newer android version goes.... Unless someone stays development for your device, you will probably have to wait for the manufacturer to update you.... Assuming they do.
Good luck!
---------- Post added at 08:54 AM ---------- Previous post was at 08:43 AM ----------
If those methods don't work out for you, you will need to ask for help here....
> General discussion > Questions and Answers
Click to expand...
Click to collapse
Hi, thanks for the answer.
That seems some what dangerous method to root :crying: , but I will see if it will work :fingers-crossed:
Unfortunately I think they wont update it to a later android version. I was thinking if I could update through an unofficial way?
The main reason is to use the apps mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2329080 , to remove the buggy touch buttoms, that sometimes when pressing back it also takes screenshots or and reduces the volume, also happens when Im just scrolling the setting menu or in some games, that is really annoying . And to reduce the resolution to see if I can get some better fps in games, though the gpu is a mali 400. But that requires 4.3 https://play.google.com/store/apps/details?id=com.nomone.resolution_changer
Rooting has nothing to do with updating... In a way.
Yes, developers can often create aosp roms for devices with Android versions higher than the devices official last version. But I can't find any for your device. And yes, you need root and a custom recovery for flashing roms. So those root methods probably won't help with that.
So it's up to the manufacturer to update you.... And they may have stopped updating your device, or just haven't yet. Updates can come very slow, if ever for less popular devices I'm afraid.
As far as Rooting being risky, yes it can be. Everything we do when altering our devices can be risky. It comes with the territory.
---------- Post added at 09:26 AM ---------- Previous post was at 09:25 AM ----------
If you want to avoid risk for now, I suggest asking for help in the 2nd link I gave you. ?
KJ said:
Rooting has nothing to do with updating... In a way.
Yes, developers can often create aosp roms for devices with Android versions higher than the devices official last version. But I can't find any for your device. And yes, you need root and a custom recovery for flashing roms. So those root methods probably won't help with that.
So it's up to the manufacturer to update you.... And they may have stopped updating your device, or just haven't yet. Updates can come very slow, if ever for less popular devices I'm afraid.
As far as Rooting being risky, yes it can be. Everything we do when altering our devices can be risky. It comes with the territory.
---------- Post added at 09:26 AM ---------- Previous post was at 09:25 AM ----------
If you want to avoid risk for now, I suggest asking for help in the 2nd link I gave you. ?
Click to expand...
Click to collapse
Ok, I will follow that link for further help , thanks.
Motorola Moto E (4th Gen) xt1766 SPerry
Sprint, Boost Mobile, Virgin Mobile, TextNow
Stock Android 7.1.1 Nougat
Build No. NCQS26.69-64-11
TWRP Flashable Installer
WARNING • • • • • • •
Altering, modifying or otherwise tampering with your device's stock filesystem configuration will render your warranty null & void, and carries with it an inherent risk of causing damage to your device. By proceeding further, you acknowledge and understand any such risks, and take sole accountability for the integrity of your device. You are encouraged to fully read this guide prior to performing any steps. I assume no liability in the event you damage your device or render it unable to function normally. However, with that having been said, should you encounter any adverse issues installing any of the files herein, stay calm and describe your issue in comments, using clear and concise dictum. I will assist to the best of my ability to help you troubleshoot your problem. Follow the below instructions carefully, paying close attention to detail, and things should go smoothly.
• • • • • • • • • • •
IMPORTANT NOTE: I am new to XDA and I'm here to learn and grow as an Android enthusiast. When posting, please be respectful to me and other members. Under no circumstances should members ask for ETAs, updates, etc. Also, I respectfully ask that this thread stay on topic with stock ROM related subject matter only.
--SPECS:
• Model: Qualcomm xt1766 SPerry Only
• Providers: Sprint, Boost Mobile, Virgin Mobile
• Android Version: 7.1.1 Nougat
• Build No. NCQS26.69-64-11
• Kernel: Linux 3.18.31-perf
• Radio: M8920_15000.280.06.58.06R
• Security Patch Level: November 1, 2018
• Build Date: November 18, 2018
--CHANGELOG:
This is an incremental update from the NCQS26.69-64-10 build number, bringing the build up to NCQS26.69-64-11. With this update comes typical bug fixes, stability improvements, and Google security patches up to November 1, 2018. More noteworthy is the update to the radio firmware (baseband), from version M8920_15000.280.06.58.05R up to version M8920_15000.280.06.58.06R. This update patches some integrity issues with LTE data connectivity in some North American regions, improves seamless cellular data handover in domestic roaming scenarios, and fixes instabilities with 4G/LTE Band 41 (TDD-LTE), improving upon carrier aggregation. It should be noted that my stock ROM installer does not update your radio firmware, but only the Android OS, the /OEM partition, and the stock boot image. If you have not updated your device to NCQS26.69-64-11 by OTA or firmware package, you are strongly encouraged to update your radio firmware now, by downloading my baseband updater from the link below, and installing it via TWRP.
•Kernel Source Code: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NCQ26.69-48
--FEATURES:
• Systemless Root: Magisk v18.0-stable
• Init.d & su.d support
• BusyBox: v1.29.3 static binaries
• SafetyNet Pass: ctsProfile & basicIntegrity
• AVB/dm-verity disabled
• Force encryption disabled (opt encrypt)
• Zipaligned /system/app & /framework
• Debloated (see links below for debloated build)
--REQUIREMENTS:
An unlocked bootloader and TWRP custom recovery are required for installation of this ROM. I strongly recommend @squid2's TWRP v3.2.1-r1, to ensure the best results on installation. After installation of this ROM, you may then update your TWRP version/build. Also, for best results, you'll need an external microSD with at least 1.5 GB free storage space.
--INSTALLATION GUIDE:
1. Recommended -- download the baseband updater from the link below and install it via TWRP;
2. Download the ROM zip and save it to your device's external storage;
3. Boot into TWRP recovery mode. Perform a wipe on /system, /cache, & Dalik. Now select Wipe again and format /userdata (this is crucial to disabling force encryption);
4. Select Install, navigate to the saved location of the ROM zip on external storage, and commence with installation;
5. Done. Reboot System
** Following initial installation, prior to completing setup, it is completely normal to experience a couple of bootloops. Just be patient.
--F2FS LOOPBACK KERNEL BUG:
Like a great many Motorola smartphones, the Moto E4 (xt1766) ships with an inherent kernel issue known as the f2fs loopback bug. In a nutshell, the xt1766's /userdata partition is formatted using the f2fs filesystem standard. The bug prevents loopback devices (.img files) from being mounted read/write (R/W). Because Magisk implements a magisk.img loopback configuration for systemless root and systemless modifications, the inability to mount read/write is extremely problematic. Luckily, a workaround exists as a Magisk module, known as the F2FS Loopback Bug Workaround. The module works by moving magisk.img to the /cache partition, which uses the ext4 filesystem type, then symlinking it to its actual location in the /userdata partition (/data/adb/magisk.img). Moreover, shortly following each and every reboot, magisk_merge.img is automatically regenerated and is handled in the same manner as magisk.img. With this workaround, a patched or modified kernel is not needed.
After the initial setup following first boot, open the Magisk Manager app and follow all prompts and grant any necessary permissions. Then go to the Downloads section within the Magisk Manager app and find the F2FS Loopback Bug Workaround module. Download it, boot into TWRP recovery mode and install the module. On reboot, the Modules section in the Magisk Manager app should indicate that the F2FS module is installed. To avoid any future issues, it is strongly advised to install any and all Magisk modules from TWRP recovery mode, versus installing them via Magisk Manager.
DEBLOATED BUILD:
I have added a debloated build to the links below. This ROM has all attributes of the standard build except that I have removed all annoying Amazon and carrier-specific bloatware from /oem/app and /oem/priv-app. In addition, I have removed many non-essential Google apps from /system/app and /system/priv-app, leaving a moderately slimmed down and bloat-free stock ROM. This ROM should be installed using the above instructions as well.
THANKS/MENTIONS:
Thanks to @VR25 for his Magisk module for the f2fs loopback bug.
Thanks to @squid2 for his TWRP builds for this and many other Moto devices. Thanks to @topjohnwu for his Magisk Universal Systemless Interface and, last but not least, thanks to @madbat99 for his warm welcome to me, and his encouragement, and to @Davey126.
--BUGS:
No known bugs
Download Links:
_______________________________________________
Baseband (radio firmware) Updater
Version: M8920_15000.280.06.58.06R: https://drive.google.com/file/d/1YckU38KUWL9YiHP4eafVteK0zArcXonu/view?usp=drivesdk
Stock ROM (Rooted, BusyBox)
Build No. NCQS26.69-64-11: https://drive.google.com/file/d/19bEz9nHZn9NP42RAl4VQGfR8WSO_Bc9y/view?usp=drivesdk
Stock ROM (Debloated, Rooted, BusyBox)
Build No. NCQS26.69-64-11: https://drive.google.com/file/d/1EMkriY3thTejiyRndiSjM-hoQdGuh-3X/view?usp=drivesdk
Stock Recovery: https://drive.google.com/file/d/1GLj-2lMkuwJFlLMYs-S754oDv0YfgdUQ/view?usp=drivesdk
Unmodified Stock Boot Image
(secure boot, avb/dm-verity, force encrypt): https://drive.google.com/file/d/1Rau38EC2FTiuu-4MFhbzatagDlWe7hvI/view?usp=drivesdk
Debloated & deodexed version in the works.
Nice opening move to XDA. Contributing instead of leeching.
Wish I still had this device.
If I had a bic lighter in my hand bro... It would be lit in the air
madbat99 said:
Nice opening move to XDA. Contributing instead leeching.
Wish I still had this device.
If I had a bic lighter in my hand bro... It would be lit in the air
Click to expand...
Click to collapse
Thank you for the warm welcome @madbat99
Yeah, I noticed a lot of what you mentioned before I ever joined up. Seems like a lot of demanding, disrespectful behavior goes on. I see the Android Community as a place where we should all give and take equally. I can tell that you have that ideology, and I wish there were more like you.
Welcome! Thanks for the ROM, I will be trying it out soon.
Just curious as to how important it is to update the baseband? Will this rom still work if you don't? Thanks for any info about this or what updating it does.
[email protected]@bl3s said:
Just curious as to how important it is to update the baseband? Will this rom still work if you don't? Thanks for any info about this or what updating it does.
Click to expand...
Click to collapse
Did you by chance read the op? Specifically the part that says "changelog?
Try again, you'll see your answer.
C'mon dude, the thread isn't even 1 full page yet and people are already skipping the original post.
madbat99 said:
Did you by chance read the op? Specifically the part that says "changelog?
Try again, you'll see your answer.
C'mon dude, the thread isn't even 1 full page yet and people are already skipping the original post.
Click to expand...
Click to collapse
Aww - come on! No spoon feeding? ?
In all likelihood, this ROM should work fine with the previous baseband (M8920_15000.280.05.58.05R) version. However, I cannot confirm this one way or the other. For members fearing that updating the baseband will cause issues on custom ROMs (as has been the case on past OTAs), it certainly won't hurt to try installing this ROM without first updating the baseband. After all, once the baseband is updated, there is no going back. Like an old carpenter used to tell me, "it's always better to cut a board too long than it is to cut it too short."
But to emphasize, there were some significant changes made to the radio firmware via the latest update. For the best results, it is strongly recommended that you update your baseband in accord with the latest incremental update. With that being said, if updating the baseband does cause adverse issues on any custom ROMs, please don't use this thread as a forum to address any such grievances. Should I get any type of confirmation on this, I will certainly include such info in the OP.
To reiterate the OP and to stress what @madbat99 suggested, guys (& girls) please read the instructions and my informal changelog carefully, before installing anything. If there is something that isn't clear, please ask. If I don't know the answer then I'll do my best to find out.
Davey126 said:
Aww - come on! No spoon feeding? ?
Click to expand...
Click to collapse
Yeah, no spoon feeding but plenty of talking down to. You people are a$$holes and you know it. ?
---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ----------
LenovoTech said:
In all likelihood, this ROM should work fine with the previous baseband (M8920_15000.280.05.58.05R) version. However, I cannot confirm this one way or the other. For members fearing that updating the baseband will cause issues on custom ROMs (as has been the case on past OTAs), it certainly won't hurt to try installing this ROM without first updating the baseband. After all, once the baseband is updated, there is no going back. Like an old carpenter used to tell me, "it's always better to cut a board too long than it is to cut it too short."
But to emphasize, there were some significant changes made to the radio firmware via the latest update. For the best results, it is strongly recommended that you update your baseband in accord with the latest incremental update. With that being said, if updating the baseband does cause adverse issues on any custom ROMs, please don't use this thread as a forum to address any such grievances. Should I get any type of confirmation on this, I will certainly include such info in the OP.
To reiterate the OP and to stress what @madbat99 suggested, guys (& girls) please read the instructions and my informal changelog carefully, before installing anything. If there is something that isn't clear, please ask. If I don't know the answer then I'll do my best to find out.
Click to expand...
Click to collapse
Thanks for actually answering the question rather than just talk down to me.
---------- Post added at 10:25 AM ---------- Previous post was at 10:22 AM ----------
madbat99 said:
Did you by chance read the op? Specifically the part that says "changelog?
Try again, you'll see your answer.
C'mon dude, the thread isn't even 1 full page yet and people are already skipping the original post.
Click to expand...
Click to collapse
Extremely helpful answer. You honestly would have been more helpful had you said nothing. Thanks for nothing. i see lenovotech posted the info I was looking for below.
[email protected]@bl3s said:
Yeah, no spoon feeding but plenty of talking down to. You people are a$$holes and you know it. ?
---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ----------
Thanks for actually answering the question rather than just talk down to me.
---------- Post added at 10:25 AM ---------- Previous post was at 10:22 AM ----------
Extremely helpful answer. You honestly would have been more helpful had you said nothing. Thanks for nothing. i see lenovotech posted the info I was looking for below.
Click to expand...
Click to collapse
Not to start the thread off on a negative note or get into quarrels, and not to take sides, but I honestly don't believe anybody was necessarily talking down to you. There have been a number of threads on this device where members don't read the OP or don't read warnings, then they blame devs & contributors when things go wrong. @madbat99 and @Davey126 are both extremely knowledgeable individuals in the Android community. I think I can speak for then both by saying that they simply want to see members take greater care and pay more attention to detail. Such would keep these threads running more smoothly. I'm glad my elaboration gave you some insight, but please refrain from flaming or name-calling on the thread. I ask you that with respect. Thank you.
[email protected]@bl3s said:
Yeah, no spoon feeding but plenty of talking down to. You people are a$$holes and you know it. ?
---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ----------
Thanks for actually answering the question rather than just talk down to me.
---------- Post added at 10:25 AM ---------- Previous post was at 10:22 AM ----------
Extremely helpful answer. You honestly would have been more helpful had you said nothing. Thanks for nothing. i see lenovotech posted the info I was looking for below.
Click to expand...
Click to collapse
I wasn't really talking down, just some light hearted sarcasm.
But I did answer you. Op says what the baseband does. I didn't have time to retype it, so I just mentioned where it was.
To be fair, the rules we all agree to when we sign up say, to fully read the OP and at least the last 10 pages of a thread before asking a question that may be answered already.
A successful, easily flashable stock ROM is just what this device needed.
LenovoTech said:
Not to start the thread off on a negative note or get into quarrels, and not to take sides, but I honestly don't believe anybody was necessarily talking down to you. There have been a number of threads on this device where members don't read the OP or don't read warnings, then they blame devs & contributors when things go wrong. @madbat99 and @Davey126 are both extremely knowledgeable individuals in the Android community. I think I can speak for then both by saying that they simply want to see members take greater care and pay more attention to detail. Such would keep these threads running more smoothly. I'm glad my elaboration gave you some insight, but please refrain from flaming or name-calling on the thread. I ask you that with respect. Thank you.
Click to expand...
Click to collapse
Ok, my apologies for getting upset. And I ageee with you, both madbat and davey are both pretty dang helpful on these forums. I've seen them on many different device forums for the same devices I have and they have both even replied to me and helped before (not to this account btw, another account that I lost access to) However sometimes it really seems that they do kind of make fun of,/poke fun at someone asking a simple question or they talk to them in a sort of condescending manner that isn't very helpful and sometimes makes the person asking the question feel attacked. I've seen it on more than one occasion. The times that they are very nice and helpful is way more than the times they aren't though. My apologies to both of these guys in this post. And once again thanks lenovotech for the amswer that you provided. I do appreciate it.
One last joke...? Don't hate me.
And for my own redemption... It is there in the op. @[email protected]@bl3s
Keep in mind, I gave you a thanks bro.
-CHANGELOG:
This build is an incremental update from the NCQS26.69-64-10 build number, bringing the build up to NCQS26.69-64-11. With this update comes typical bug fixes, stability improvements, and Google security patches up to November 1, 2018. More noteworthy is the update to the radio firmware (baseband), from version M8920_15000.280.06.58.05R up to version M8920_15000.280.06.58.06R. This update patches some integrity issues with LTE data connectivity in some North American regions, improves seamless cellular data handover in domestic roaming scenarios, and fixes instabilities with 4G/LTE Band 41 (TDD-LTE), improving upon carrier aggregation. It should be noted that my stock ROM installer does not update your radio firmware, but only the Android OS, the /OEM partition, and the stock boot image. If you have not updated your device to NCQS26.69-64-11 by OTA or firmware package, you are strongly encouraged to update your radio firmware now, by downloading my baseband updater from the link below, and installing it via TWRP.
madbat99 said:
One last joke...? Don't hate me.
And for my own redemption... It is there in the op. @[email protected]@bl3s
Keep in mind, I gave you a thanks bro.
-CHANGELOG:
This build is an incremental update from the NCQS26.69-64-10 build number, bringing the build up to NCQS26.69-64-11. With this update comes typical bug fixes, stability improvements, and Google security patches up to November 1, 2018. More noteworthy is the update to the radio firmware (baseband), from version M8920_15000.280.06.58.05R up to version M8920_15000.280.06.58.06R. This update patches some integrity issues with LTE data connectivity in some North American regions, improves seamless cellular data handover in domestic roaming scenarios, and fixes instabilities with 4G/LTE Band 41 (TDD-LTE), improving upon carrier aggregation. It should be noted that my stock ROM installer does not update your radio firmware, but only the Android OS, the /OEM partition, and the stock boot image. If you have not updated your device to NCQS26.69-64-11 by OTA or firmware package, you are strongly encouraged to update your radio firmware now, by downloading my baseband updater from the link below, and installing it via TWRP.
Click to expand...
Click to collapse
You just like to stir the pot don't you?
After lenovotech was professional with his response (which actually answered my question, unlike your replies) I made my apology for getting upset and yet you still feel the need to come in this thread and try to be funny (btw, your "joke" really isn't funny. Don't quit your day job bro) I guess this is just how xda is anymore. You should take notes on keeping things professional rather than trying to be funny. Like I said before your replies in this thread have been less than helpful. You have been more than helpful in numerous other threads I've seen you in so not sure why your posts in this particular thread are so useless/unhelpful.
Anyways, No hard feelings. Lenovotech did answer my question so I'm good and may flash this rom within the next few days.
P.s. I will not be replying back to anything/anyone relating to this off topic nonsense. I'm here for info on android and nothing else. Thank you lenovotech for the rom btw. ?
[email protected]@bl3s said:
P.s. I will not be replying back to anything/anyone relating to this off topic nonsense. I'm here for info on android and nothing else. Thank you lenovotech for the rom btw. ?
Click to expand...
Click to collapse
Excellent. Looking forward to more relevant posts which assumes due diligence prior to asking questions.
My post, and subsequent copy of op, literally answered the question to the letter. And even prompted a smile with the "member's" misinterpretation of my post (and the rules for that matter), and I'm still the bad guy....
Nice
Ba da bomp bomp baaa, I'm lovin it.
Guess I'm too old for the new generation.
We old timers realize when we jump to the wrong conclusion and are usually quick to laugh at ourselves.
No hard feeling intended, felt, or taken.
This thread will soon be populated by people thanking op for this. My guess, op has a great future here.
madbat99 said:
My post, and subsequent copy of op, literally answered the question to the letter. And even prompted a smile with the "member's" misinterpretation of my post (and the rules for that matter), and I'm still the bad guy....
Nice
Ba da bomp bomp baaa, I'm lovin it.
Guess I'm too old for the new generation.
We old timers realize when we jump to the wrong conclusion and are usually quick to laugh at ourselves.
No hard feeling intended, felt, or taken.
This thread will soon be populated by people thanking op for this. My guess, op has a great future here.
Click to expand...
Click to collapse
@madbat99 I have long been reading your threads, posts and guides, way before I took the leap and joined up. In short, you have been giving me Android knowledge long before I got the opportunity to meet you here. I consider both you and @Davey126 two of the most knowledgeable members on Motorola devices (and Android in general) here on XDA. So, your encouragement and kind words mean a lot. There is no doubt I will need your insight and advice during my journey on XDA. So I do want to sincerely thank you (and @Davey126) for everything.
Davey126 said:
Aww - come on! No spoon feeding? ?
Click to expand...
Click to collapse
reason my g6 play and E5 + twrp and decrypt guidez are short and simple
I have attempted to download the rooted stock, limited to my phone I have been unsuccessful. I'm not rooted, running the stock ROM. On either WiFi or network, it fails to download. I have been able to add it to my drive, but can't get it to work from there. I'm probably treading in off topic but I have tried everything I know with zero results. I'm hoping someone could suggest something that could help.