Here's TWRP 2.8.5.0 for the LG G Pad 8.3 GPE.
Download here: http://d-h.st/pNx
Older version:
2.8.1.0: http://d-h.st/FNQ
Flash using fastboot.
Alternatively, flash using Flashify from Play Store.
Enjoy!
aidfarh said:
Here's TWRP 2.8.1.0 for the LG G Pad 8.3 GPE.
Download here: http://d-h.st/FNQ
Flash using fastboot.
Alternatively, flash using Flashify from Play Store.
Enjoy!
Click to expand...
Click to collapse
Thank you for your contribution. Could you upload a file without the .exe extension? It causes problems installing from Linux, unless you know a workaround?
sleekmason said:
Thank you for your contribution. Could you upload a file without the .exe extension? It causes problems installing from Linux, unless you know a workaround?
Click to expand...
Click to collapse
What .exe extension? The file has an .img extension.
aidfarh said:
What .exe extension? The file has an .img extension.
Click to expand...
Click to collapse
When I downloaded the file, it was .IMG.exe. Figured you used windows. Maybe the download site added it?
sleekmason said:
When I downloaded the file, it was .IMG.exe. Figured you used windows. Maybe the download site added it?
Click to expand...
Click to collapse
No, the file on the download site doesn't have the .exe extension. It's probably your browser that's adding the .exe extension. Try using another browser.
If you're still having problem downloading, here's a link to the zipped file: http://d-h.st/8uF
aidfarh said:
If you're still having problem downloading, here's a link to the zipped file: http://d-h.st/8uF
Click to expand...
Click to collapse
I'll check... And, thank you.
Do NOT install this. It installs a downloader with adblock, coupons, all kinds of goodies.
Colchiro said:
Do NOT install this. It installs a downloader with adblock, coupons, all kinds of goodies.
Click to expand...
Click to collapse
I'm not sure what you installed, but I got nothing of the sort, just an updated recovery.
Sent from my LG-V510 using Tapatalk
A downloader is not needed to DL a 10 mb file and when it says it's going to get me an adblocker and coupons, I'm cancelling it immediately. I blame the "malware" on the hosting company, not the OP.
I clicked the OP's link again and I have 3 "Download" buttons. The middle one gives me the recovery image.
The first and last (larger) buttons give me the exe download.
Stick to the smaller, middle button to avoid the crap I complained about.
aidfarh said:
Here's TWRP 2.8.1.0 for the LG G Pad 8.3 GPE.
Download here: http://d-h.st/FNQ
Flash using fastboot.
Alternatively, flash using Flashify from Play Store.
Enjoy!
Click to expand...
Click to collapse
Flashed this and it works awesome. Thanks for your work and effort.
nvm
Maybe @aidfarh can do...
Hopefully the V510 will get TWRP 2.8.4.0 now that its available. Has some awesome features including being able to flash images.
galaxys said:
Maybe @aidfarh can do...
Hopefully the V510 will get TWRP 2.8.4.0 now that its available. Has some awesome features including being able to flash images.
Click to expand...
Click to collapse
+1
Twrp 2.8.5.0 is now out! Latest TWRP now support CM12 OTA Updates among other fixes! Hopefully @aidfarh can get it for us.
Changelog:
Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
Improve thread handling and move input handling into the main rendering thread to improve stability
Make MTP work even if unplugged and plugged back in
Unify scrollable list code and make kinetic scrolling feel more natural
Fix handling of mapped zip files for OTA updates (CM12 updater)
USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
Other small fixes and improvements. Ref: http://www.teamw.in/project/twrp2
I've uploaded version 2.8.5.0. Link's in OP.
aidfarh said:
I've uploaded version 2.8.5.0. Link's in OP.
Click to expand...
Click to collapse
Working well for me. Used fastboot to install. Thank you!
Thanks for keeping our v510 alive & kicking! this is awesome!
Worked fine with Flashify. From now on we can flash images directly from TWRP! Very cool
Just to avoid accidents, the OP might want to add 'v510' to the file name, so that v500 users don't accidentally flash this file.
For some reason, no matter how many different versions of TWRP I try, I still can't see my TWRP backup folder.
Related
Does anyone know why the Moto X is not listed on TWRP's supported devices page?
http://teamw.in/twrp_view_all_devices
I would really like to have twrp 2.7 for USB OTG mounting. Anyone know why it's not available?
Moto x is not supported by twrp. So someone needs to make a Moto x version. Just like the other versions we have.
Sent from my N5 cell phone telephone....
TWRP 2.6.3.1 works just fine with the Moto X. USBotg works natively with v4.4.2 but leaves a notification that cannot be cleared. Using Stickmount, unmounting leaves a notification error, but that can be swiped away.
TWRP encrypted /data support for Moto X ?
I have the latest (2.6.3.2 twrp motox from dhacker) and have recently encrypted /data.
As a result, when I go to do a backup twrp is unable to mount /data and therefore fails.
I've googled various things (twrp, encryption, motox, various combinations) and this
was the most promising thread.
As mentioned (above) twrp doesn't support the motox devices...
Does anyone have any suggestions how to
a. take a backup of the encrypted /data partition
b. find a twrp for motox that will do so
or worst case
c. where to find instructions on how to build twrp for the xt1053/58/60...
Thanks in advance.
Ehud
Tucson AZ US
Groid said:
TWRP 2.6.3.1 works just fine with the Moto X. USBotg works natively with v4.4.2 but leaves a notification that cannot be cleared. Using Stickmount, unmounting leaves a notification error, but that can be swiped away.
Click to expand...
Click to collapse
Are you talking about OTG in recovery or in the actual android OS? I'm talking about twrp recovery... didn't know there was a way to use stick mount in recovery... anyway otg works within cwm recovery but not twrp for me.... why isn't the Moto x officially supported by TWRP? There are a lot more less popular devices that are... Thanks
dkoon1987 said:
Are you talking about OTG in recovery or in the actual android OS? I'm talking about twrp recovery... didn't know there was a way to use stick mount in recovery... anyway otg works within cwm recovery but not twrp for me.... why isn't the Moto x officially supported by TWRP? There are a lot more less popular devices that are... Thanks
Click to expand...
Click to collapse
Yeah, sorry, I didn't get that you were only specifically looking for otg in recovery. I've never tried it in recovery. Also, I don't have an encrypted phone.
http://androidhosting.org/Devs/Dhacker29/MotoX/TWRP-2.7.0.0-moto_msm8960dt.img
Moto X Finally Gets Official Build Of TWRP Custom Recovery :
http://www.androidpolice.com/2014/06/10/moto-x-finally-gets-official-build-of-twrp-custom-recovery/
http://teamw.in/project/twrp2/234
hotsync100 said:
Moto X Finally Gets Official Build Of TWRP Custom Recovery :
http://www.androidpolice.com/2014/06/10/moto-x-finally-gets-official-build-of-twrp-custom-recovery/
http://teamw.in/project/twrp2/234
Click to expand...
Click to collapse
Link is currently broken for moto x (ghost)... :/
samwathegreat said:
Link is currently broken for moto x (ghost)... :/
Click to expand...
Click to collapse
When the link gets fixed should a new post be added to the Android Development subforum?
Link is working fine. Here's a direct link to the img: http://techerrata.com/browse/twrp2/ghost.
thehockeydude44 said:
When the link gets fixed should a new post be added to the Android Development subforum?
Click to expand...
Click to collapse
A new post, yes. A new thread isn't necessary. Just forewarning those who might jump to download only to find the link broken...
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
klobkelosh said:
Link is working fine. Here's a direct link to the img: http://techerrata.com/browse/twrp2/ghost.
Click to expand...
Click to collapse
The link from within twrp manager is what is broken (still):
Warning: md5_file(ghost/openrecovery-twrp-2.7.1.1-ghost.img): failed to open stream: No such file or directory in /home/mazwoz/public_html/recovery/file/twrp2/download.php on line 70 MD5:
samwathegreat said:
A new post, yes. A new thread isn't necessary. Just forewarning those who might jump to download only to find the link broken...
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
The link from within twrp manager is what is broken (still):
Warning: md5_file(ghost/openrecovery-twrp-2.7.1.1-ghost.img): failed to open stream: No such file or directory in /home/mazwoz/public_html/recovery/file/twrp2/download.php on line 70 MD5:
Click to expand...
Click to collapse
One could flash the img via fastboot. Or, download the img and flash on device with the flashify app.
klobkelosh said:
One could flash the img via fastboot. Or, download the img and flash on device with the flashify app.
Click to expand...
Click to collapse
Absolutely, one could definitely flash the img via fastboot.
The point is, now that Moto X has official support of TWRP, the OFFICIAL TWRP page recommends using the Official "TWRP Manager" app.
This is a great idea, because you can easily flash any new updates from directly within the app.
So: Anyone interested in updating to the new version, go ahead and flash via fastboot as @klobkelosh has suggested.
But it would still be nice for the "TWRP Manager" link to be fixed so that we can use the app, as the developers intended.
Information on the app here: http://teamw.in/project/twrp2/234
As for "Flashify", that app was reported in another Moto X forum to NOT work on the Moto X. If you have personally used it and it does indeed work for flashing recovery to Moto X, please post back here and let us know. I have not recommended the app to anyone because it was reported to fail while attempting to flash recovery on the X.
samwathegreat said:
As for "Flashify", that app was reported in another Moto X forum to NOT work on the Moto X. If you have personally used it and it does indeed work for flashing recovery to Moto X, please post back here and let us know. I have not recommended the app to anyone because it was reported to fail while attempting to flash recovery on the X.
Click to expand...
Click to collapse
My bad. I have not tested flashify on Moto x. I used it on a gnex and made the unfounded assumption that it works on Moto x. Apologies.
On the other hand... http://forum.xda-developers.com/showthread.php?p=53311645
Hopefully the twrp manager developers can fix the problem.
Flashed 2.7.1.1 with flashify just recently and all is good. Nice not having to plug in using the fastboot method.
ConstantHero said:
Flashed 2.7.1.1 with flashify just recently and all is good. Nice not having to plug in using the fastboot method.
Click to expand...
Click to collapse
Thanks for the info. Now we know this is a working alternative.
Also, sent a message notifying the TWRP team of the broken in-app link. I imagine it will be fixed soon.
Flashed mine with rom toolbox pro.
Sent from my Nexus 7 using Tapatalk
samwathegreat said:
A new post, yes. A new thread isn't necessary.
Click to expand...
Click to collapse
Why not a new thread? I'm not trying to start an argument, just curious... The current thread about TWRP is titled with version 2.6.3.1 with 489 replies, making a new one would clean it up.
thehockeydude44 said:
Why not a new thread? I'm not trying to start an argument, just curious... The current thread about TWRP is titled with version 2.6.3.1 with 489 replies, making a new one would clean it up.
Click to expand...
Click to collapse
Sure...do it. I agree that it should clean things up.
You might even include info about the new version of SuperSU. This could be useful since those on 4.4.3 are recommended to use the latest versions of both TWRP and SuperSU.
This is the CM-12.1 recovery for fugu.
Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery-20150418.img
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Dude, quit being so amazing. It's getting ridiculous.
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Yes!!! Glad to see you!
@WugFresh
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Dear Developers,
It has come to our attention that due to excessive ads that simulate download buttons, fly-by malware APK attacks from Mobogenie, and reused (and potentially dangerous) reused short URLs, Dev-Host no longer meets our minimum acceptable requirements as a hosting affiliate. As such, we are ending our affiliation with this provider. We urge you to find a safer download host for your development projects such as our other affiliates: Goo.im and AndroidFileHost.
Click to expand...
Click to collapse
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
GabbyWC said:
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Click to expand...
Click to collapse
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
---------- Post added at 03:27 AM ---------- Previous post was at 03:17 AM ----------
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I have to agree with Wugfresh on this bro AndroidFileHost is great. All you need to do is @ the guy on Twitter and he'll hook you up with a developer account complete with ftp access.
Wugfresh the issue with a revision on this is it's cm's android bootable recovery so technically anytime a commit is made to that repo it would be a revision change.
I'll host the updated image somewhere else tonight and I will be adding the date to the end of the image so you can tell if it is updated.
bkjolly said:
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
Click to expand...
Click to collapse
The Q&A for Xposed on Android 5.0 at http://www.xda-developers.com/xposed-framework-for-android-lollipop-is-here/ contains this quote:
I want to install it. Now! What do I have to do?
Make sure that you’ve read my words above and you’re familiar with your phone’s internals. Obviously, you need to be on a Lollipop ROM and have a good backup of your data. For now, I will only publish the ARMv7 version. 64-bit is more complex, so let’s try the “easy” variant first.
For now, the installation has to be performed manually in a custom recovery. Flashing the zip file will install:
* app_process32_xposed and some symlinks
* libexposed_art.so
* libart.so and some related binaries + libraries (based on 5.0.2, enhanced with support for hooking etc.)
* XposedBridge.jar (now stored in /system/framework)
Backups of existing files will be created automatically and could be restored later.
Can confirm a working flash. Everything looks great! Thanks for all the hard work
no option to make a recovery image...whats the point of this then?
I tried to wipe my cache to free some space and it sent my nexus player into a bootloop...whats going on with this?
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Edit
Noob
I'm a bit of a noob - I have managed to ADB a new boot and system image to my nexus player - it's now running lollipop1.6. What does this recovery mean and how is it different than loading a boot and system image? Thanks - Does this require ClockworkMod?
dhacker29 said:
I just got my Nexus Player last night and made a working version of CM recovery for it. Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery.img - 8.41 MB
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Click to expand...
Click to collapse
OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
if you restored your backup you would be downgrading it from the update you just took. you dont need a custom recovery to back up apps and their data, there are apps for that. a custom recovery makes it so its easier to flash new/custom roms(os), make backups of the current rom(os) so if anything goes wrong you can restore it, flash zips like the supersu zip or xposed framework. if you try take an ota with a custom recovery the ota will fail to install as its looking for the stock recovery(may be diff on a nexus device but its always been like that on the devices i have owned)
OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
This recovery does not provide a "nandroid" type backup where all of your info is zipped up and stored on the devices internal storage, where any application can get access to it, but rather supports adb backup. which backs up your information to a file on your computer. See http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351 for more information on usage.
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I swtiched to andriodfilehost and uploaded the latest version.
dhacker29 said:
I swtiched to andriodfilehost and uploaded the latest version.
Click to expand...
Click to collapse
Thanks for an update. I tried to full backup by following commands.
adb backup -apk -shared -all -f C:\backup20151904.ab
But getting this "Now unlock your device and confirm the backup operation" lines and asking for unlock your deivice to confirm. Any sugestion to pass this. Thanks
Yes it seems Google decided to remove the backup confirmation dialog from TcSettings
So it means adb backup of a full ROM is not possible? Going to try your rom later.
Sent from my Nexus 6 using Tapatalk 2
DISCLAIMER
We are not responsible for any damage, bootloop, bricked or broken tablets and Relationships.
Team @csolanol & @diegocr is back!!!
Notice
This recovery can't be flashed to the tablet meanwhile the bootloader is locked. We don't have any way to unlock it for now so you must launch it this way:
Code:
fastboot boot TWRP_Fire_2.8.7.0_adb.img
Edit: Project became stable. Got rid of the backlight error thanks to @diegocr.
Download
https://www.androidfilehost.com/?fid=24269982087018181
Update 2015-12-14
MTP working, if doesn't mount disable and re-enable
Don't use USB storage, not working
Update 2015-12-13
Added adb & USB storage mount USB storage not working
XDA:DevDB Information
[CUSTOM RECOVERY] TWRP Recovery, Tool/Utility for the Amazon Fire
Contributors
csolanol, diegocr
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2015-11-09
Created 2015-11-06
Last Updated 2015-12-14
Video: 2015 Fire: Booting TWRP, Rooting, Installing Gapps
Basic Directions
Download/Install Drivers
Verify Divers were installed Correctly
Download/Install ADB/Fastboot files
Test Fastboot commands
Download Twrp.img from link in post #1
Boot Custom Recovery with
Code:
fastboot boot TWRP_Fire_recovery.img
check root status with https://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
This is a temporary recovery, it must be booted with fastboot commands, every time want to use it.
What you can do with a Custom Recovery
Root Stock rom with SuperSu.zip
Install Google Apps Select Arm | 5.1 | pico version
Install Xposed Framwork
Backup Rom
Install Custom ROM
Install Stock Firmware (UnBrick)
...
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Awesomeslayerg said:
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Click to expand...
Click to collapse
I don't think there is anyway to do that which is why signed software is generally trust-able.
bullet25 said:
I don't think there is anyway to do that which is why signed software is generally trust-able.
Click to expand...
Click to collapse
Well i've seen people using lg sign tool or something to sign there images to flash thier images and make them bootable.
keep up the great work now we just gotta get custom rom installed
Can Flashify be used to boot into the recovery?
niphoet said:
Can Flashify be used to boot into the recovery?
Click to expand...
Click to collapse
no, can not
Sent from my KFFOWI using Tapatalk
Hopefully we'll get custom roms soon... AOSP on a $50, quality, device would be awesome!
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
petermg said:
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
Just ignore that line.
Any Tom development started yet?
Awesomeslayerg said:
Any Tom development started yet?
Click to expand...
Click to collapse
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
added video to post #2
Harry44 said:
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
Click to expand...
Click to collapse
That sounds really great. I tried to make a deblooated rom, but I broke the settings application by accident. I guess I'll just wait until someone else releases theirs... :/
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
hey since this is running lollipop amazon os. cany you guys make a costom rom like the hdx developers do that can be booted without unlocking the bootloader. they use safestrap which is like twrp but for locked bootloaders and install custom roms. they arnt fully custom they have amazon aspects that let it boot with the locked bootloader but it is almost fully custom the hdx has a nexus rom and a cm11 rom they made for it.
sandman512 said:
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
Click to expand...
Click to collapse
Did you install Google apps zip?
It's not unusual for google services to slow down a device
sd_shadow said:
Did you install Google apps zip?
It's not unusual for google services to slow down a device
Click to expand...
Click to collapse
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
sandman512 said:
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
Click to expand...
Click to collapse
Not as easily as it they were installed.
Use a root file manager, to delete or rename or move.
Use titanium backup pro or similar app, to freeze google apps
you freeze all google apps, and see if performance improved, them unfreeze google apps one at a time to see which ones are causing issues.
[ROM/Kernel] Stock 7.1.1 B02 based for A2017G. The "We can do it better than zte" ed.
No fancy super nice pictures and no other great blabla here.
Thx @wineds for providing a TWRP backup from the system. It's the base of this.
Thx @SuperR. for his great kitchen.
Little mods:
init.d enabled
dm-verity disabled
SuperSU included
Spyware stuff:
tencentNLP removed
Email_ZTE removed
no further actions done on this.
For me it's working with the Universal Bootstack. You will find it in the LOS thread.
Flash it with TWRP.
Download:
The ROM --> https://www.androidfilehost.com/?fid=673368273298948672
The Stock Kernel if you played to much with the others -->https://www.androidfilehost.com/?fid=817550096634763383
p.s.: I've read about problem with big sdcards in conjunction with the original B02 rom. I've never been on this crap version, so I can't tell if there's a difference in the behaviour. But up to now I have no problem with my 128GB sandisk card. And yes, it's formated with extfs.
This rom can flash from twrp? What version of twrp?
Thank you, I was expecting something like this.
I use google translate
Enviado desde mi ZTE A2017U mediante Tapatalk
davidroid1 said:
This rom can flash from twrp? What version of twrp?
Thank you, I was expecting something like this.
I use google translate
Enviado desde mi ZTE A2017U mediante Tapatalk
Click to expand...
Click to collapse
For me TWRP 3.1 did its job.
tron1 said:
No fancy super nice pictures and no other great blabla here.
Thx @wineds for providing a TWRP backup from the system. It's the base of this.
Thx @SuperR. for his great kitchen.
Little mods:
init.d enabled
dm-verity disabled
SuperSU included
Spyware stuff:
tencentNLP removed
Email_ZTE removed
no further actions done on this.
For me it's working with the Universal Bootloader. You will find it in the LOS thread.
Flash it with TWRP.
Download:
The ROM --> https://www.androidfilehost.com/?fid=673368273298948672
The Stock Kernel if you played to much with the others -->https://www.androidfilehost.com/?fid=817550096634763383
p.s.: I've read about problem with big sdcards in conjunction with the original B02 rom. I've never been on this crap version, so I can't tell if there's a difference in the behaviour. But up to now I have no problem with my 128GB sandisk card. And yes, it's formated with extfs.
Click to expand...
Click to collapse
How did you disable dm-verity? Patch the boot image with the no-verity zip from nethunter?
With the removal of TNL does the Google Location Provider now provide the location information?
sToRm1nG said:
How did you disable dm-verity? Patch the boot image with the no-verity zip from nethunter?
With the removal of TNL does the Google Location Provider now provide the location information?
Click to expand...
Click to collapse
Google maps showed me my correct location while beeing inside my house. So i guess it is working right. If not we still have the option to flash/install opengapps to make it run as designed.
tron1 said:
Google maps showed me my correct location while beeing inside my house. So i guess it is working right. If not we still have the option to flash/install opengapps to make it run as designed.
Click to expand...
Click to collapse
Thanks, I will probably try it myself since I am not completely satisfied with LOS.
What about dm-verity? Did you patch the boot image with the zip file I was talking about? I'm asking because I'd probably do it myself.
sToRm1nG said:
Thanks, I will probably try it myself since I am not completely satisfied with LOS.
What about dm-verity? Did you patch the boot image with the zip file I was talking about? I'm asking because I'd probably do it myself.
Click to expand...
Click to collapse
It's just a "click" in the SuperRs kitchen boot image config menu.
Anyone who has U model tried?
WesTD said:
Anyone who has U model tried?
Click to expand...
Click to collapse
I'm not sure if the U model contains the Tencent Network Location app (AFAIK it is not).
Pin Input necessary after installation ....
I´m have a A2017G with Stockrom B08 on MM and TWRP 3.1.0.0
Installed the first the Kernel and then the Nougat_7_1_1_B02_we_can_do_it_better_than_zte.zip.
Wipe Cache and Reboot to recovery , than into to the system.
Result:
Need a Pin for the first start, but no ok. I could input all numbers and delete it. But nothing go on.
Any Idea for my failure ?
Snoopy2006 said:
I´m have a A2017G with Stockrom B08 on MM and TWRP 3.1.0.0
Installed the first the Kernel and then the Nougat_7_1_1_B02_we_can_do_it_better_than_zte.zip.
Wipe Cache and Reboot to recovery , than into to the system.
Result:
Need a Pin for the first start, but no ok. I could input all numbers and delete it. But nothing go on.
Any Idea for my failure ?
Click to expand...
Click to collapse
Yes, I have an idea. You didn't read and/or under-stand what you have to flash and what not. You don't have to flash the kernel (it's just in case you played with other kernels, so you don't need to flash the whole system). The thing you have to flash before is the universal Bootstack from the LOS thread. For removing the pin do the following in TWRP:
head to Advanced > File Manager, and go to the /data/system folder. Scroll down and find the two files with the .key extension. Delete both of them (by tapping on the file and then tapping the “Delete” button). Then, delete all the files containing the word locksettings.
From MM B08 to Nougat 7.1.1 B02
tron1 said:
Yes, I have an idea. You didn't read and/or under-stand what you have to flash and what not. You don't have to flash the kernel (it's just in case you played with other kernels, so you don't need to flash the whole system). The thing you have to flash before is the universal Bootstack from the LOS thread. For removing the pin do the following in TWRP:
head to Advanced > File Manager, and go to the /data/system folder. Scroll down and find the two files with
Click to expand...
Click to collapse
At the Moment I`m back to MM B08 on the Axon 7 2017 G !
What should I flash ?
tron1 said:
Yes, I have an idea. You didn't read and/or under-stand what you have to flash and what not. You don't have to flash the kernel (it's just in case you played with other kernels, so you don't need to flash the whole system). The thing you have to flash before is the universal Bootstack from the LOS thread. For removing the pin do the following in TWRP:
head to Advanced > File Manager, and go to the /data/system folder. Scroll down and find the two files with the .key extension. Delete both of them (by tapping on the file and then tapping the “Delete” button). Then, delete all the files containing the word locksettings.
Click to expand...
Click to collapse
In my Systemfolder I find gatekeeper.password.key and gatekeeper.pattern.key. Should I remove these 2 Files ?
hi
thx for the build, but seems I missed something, because the gps is not working without wifi(gps cant lock on).
I tried google and here. coming from NucleaRom flashed only the rom and the universal bootstack.
can we select the apps which we want and which we do not want while installing ?
sendem said:
hi
thx for the build, but seems I missed something, because the gps is not working without wifi(gps cant lock on).
I tried google and here. coming from NucleaRom flashed only the rom and the universal bootstack.
Click to expand...
Click to collapse
Tried it with Sigic and GPS test tool, no problem here
I flashed the kernel now the gps its ok(so no problems for me) .dont use the latest twrp 3.1 it has some bugs.
best regards.
I understand you kept this close to stock, but I have 3 questions.
Does it support Live Wallpaper? (stock B02 doesn't)
Can you turn off the lock screen 'None'?
Does it run Daydream smoothly?
You need to put it in the viewer to really tell. I tried on other ROMS, but it was super choppy and jittery to the point of nausea.
Very good battery life, but no MTP connection possible. It's the same fault as with all LOS based roms (based on 7.1.2).
HuKu52 said:
Very good battery life, but no MTP connection possible. It's the same fault as with all LOS based roms (based on 7.1.2).
Click to expand...
Click to collapse
No problem here. Check bootstack/modem
*FILES REMOVED UNTIL FURTHER NOTICE, AS USERS ARE HAVING CONNECTION ISSUES AFTER FLASHING*
Here are the latest stock retail builds packaged into TWRP flashable format.
You can use these files to upgrade and downgrade stock builds safely, as they do not include gpt (partition table) or bootloader.
Usage is simple:
Copy file to device storage
Reboot into TWRP
Flash zip
Profit!
Please remember to hit the "THANKS" button if these files help you!
NOTES:
Dm-verity and force encryption have been disabled in the boot images, and unlocked device/dm-verity warnings have been disabled in the logo images.
Do NOT attempt to apply standard OTAs over these builds; they will fail.
If you get an OTA for a build that's not yet available, please share it!
How To Pull An OTA update:
Download the update
Power off and boot into TWRP
Go to Advanced > File Manager
Navigate to /cache
There will be a Blur_Version_blah.zip file
Copy to internal storage or sdcard
Copy from internal storage or sdcard to PC (optional, recommended)
Upload to Drive, Mega, or whichever file sharing service you choose
Share the link!
If you're rooted/modded and want to prevent potential auto updating, you can wipe /cache to remove the file.
DOWNLOADS:
CREDITS:
Android
Lenovorola
@tal.aloni for SparseConverter posted here:
https://forum.xda-developers.com/showthread.php?t=2749797
@erfanoabdi for imgpatchtools posted here:
https://forum.xda-developers.com/an...ev-img-patch-tools-sdat2img-ota-zips-t3640308
@A.S._id for img repack tools posted here:
https://forum.xda-developers.com/showthread.php?t=2600364
@xpirt for sdat tools posted here:
https://forum.xda-developers.com/an.../how-to-conver-lollipop-dat-files-to-t2978952
Please tell me these actually work. I am desperate for any ROM for the XT1710-01 variant. I will go as far as paying.
Thank you so much,it works on xt1710-08 well,just backup EFS in trwp just in case of no signal,after flash this rom in twrp,restore EFS and enjoy it.Also,you can root it with flashing magisk
So the 118-19-6 is good for the XT1710-01 Retail directly from Motorola?
I'm on the stock 118-9 version, Security Update of July 1st, and Android 7.1.1. No OTA update available when I check.
Are these 7.1.2 yet?
THANKS
KeepingItCuttingEdge said:
Are these 7.1.2 yet?
Click to expand...
Click to collapse
It's still 7.1.1. See the attached screenshot.
KeepingItCuttingEdge said:
So the 118-19-6 is good for the XT1710-01 Retail directly from Motorola?
I'm on the stock 118-9 version, Security Update of July 1st, and Android 7.1.1. No OTA update available when I check.
Click to expand...
Click to collapse
Any response to these questions, OP?
I am in the same boat.
New builds are up
KeepingItCuttingEdge said:
So the 118-19-6 is good for the XT1710-01 Retail directly from Motorola?
I'm on the stock 118-9 version, Security Update of July 1st, and Android 7.1.1. No OTA update available when I check.
Are these 7.1.2 yet?
THANKS
Click to expand...
Click to collapse
There is no 118-9 version.
pizza_pablo said:
Any response to these questions, OP?
I am in the same boat.
Click to expand...
Click to collapse
There is no 118-9 version.
If I knew, I would answer.
These files are are made from official fastboot files shared by @Junior Passos.
Check out his afh page for albus here: https://androidfilehost.com/?a=show&w=files&flid=195559
Q9Nap said:
New builds are up
There is no 118-9 version.
There is no 118-9 version.
If I knew, I would answer.
These files are are made from official fastboot files shared by @Junior Passos.
Check out his afh page for albus here: https://androidfilehost.com/?a=show&w=files&flid=195559
Click to expand...
Click to collapse
This is from a US unlocked Z2 Play.
The model number is XT1710-01.
Are the listed firmware versions proper for my model?
pizza_pablo said:
This is from a US unlocked Z2 Play.
The model number is XT1710-01.
Are the listed firmware versions proper for my model?
Click to expand...
Click to collapse
Dude, what did I just say? I DON'T KNOW.
I'm sure it will work, but it may take you off your official upgrade path.
And with no fastboot file available for your current software version, I would take a full TWRP backup and copy to pc for safekeeping before trying anything.
Welcome to Flashing 101
Q9Nap said:
*removed*
Due to lack of interest.
Click to expand...
Click to collapse
Noooo, please restore! I've been using the steps and files provided to get rid of the annoying "an update is available" notifications on my rooted XT1710-09!
And yesterday a new one has appeared...
Indeed please restore it can't hurt having it up here
We don't even have custom roms, this is the closest we can get for now. Please post more builds!
Q9Nap said:
*removed*
Due to lack of interest.
Click to expand...
Click to collapse
I'm going to buy my z2 play bike at the end of the year and it's a shame not to have an updated lite rom. Probably you should be doing a good job.
It would be nice to have a rom lite for ALL MODEL with deodex, delete more apps OTA / CCC / CCE, OTA process is deleted, remove a lot of the background services collect and send data on the type of phone (DropBox, MotoCare , MotoConntect, Drive and etc).
ilgrosso said:
Noooo, please restore! I've been using the steps and files provided to get rid of the annoying "an update is available" notifications on my rooted XT1710-09!
And yesterday a new one has appeared...
Click to expand...
Click to collapse
Lars1703 said:
Indeed please restore it can't hurt having it up here
Click to expand...
Click to collapse
f.baio said:
We don't even have custom roms, this is the closest we can get for now. Please post more builds!
Click to expand...
Click to collapse
Guth13 said:
I'm going to buy my z2 play bike at the end of the year and it's a shame not to have an updated lite rom. Probably you should be doing a good job.
It would be nice to have a rom lite for ALL MODEL with deodex, delete more apps OTA / CCC / CCE, OTA process is deleted, remove a lot of the background services collect and send data on the type of phone (DropBox, MotoCare , MotoConntect, Drive and etc).
Click to expand...
Click to collapse
Updated the OP with the latest retail build NPSS26.118-19-11.
Unlike most carrier unlocked moto devices, which tend to have multiple upgrade paths for different regions, the albus seems to have only one upgrade path for the retail variant so far.
Someone correct me if I'm wrong, and please post the OTA files for alternate upgrade paths if you have them; directions are in the OP.
I have linked the tools I use to create these at the bottom of the OP.
You can use these tools and info in their threads to reverse engineer the stock build and modify it to your liking.
Thank you so much now i can have the latest update for my rooted moto thanks a lot
I have an unlocked Moto Z2 Play XT1710-01 and this is the latest update I am seeing:
NPSS26.118-24-6
https://drive.google.com/file/d/1IUG-o0HWCgFGyNwX3aWzd4oqhHAzK25T/view?usp=sharing
EDIT:
I think i now understand the file name structure and that it includes the date. My updated was from 6/26 and your updated was from 11/19. I just updated to the newest. Thank you for doing this!
sirkuttin said:
I have an unlocked Moto Z2 Play XT1710-01 and this is the latest update I am seeing:
NPSS26.118-24-6
https://drive.google.com/file/d/1IUG-o0HWCgFGyNwX3aWzd4oqhHAzK25T/view?usp=sharing
EDIT:
I think i now understand the file name structure and that it includes the date. My updated was from 6/26 and your updated was from 11/19. I just updated to the newest. Thank you for doing this!
Click to expand...
Click to collapse
The file name structure doesn't have anything to do with the date it was made afaik.
That update is for "albus_c" and not "albus". I'm not sure what the difference is.
Apparently, there are multiple upgrade paths after all.
Flashing this will likely take you off your current upgrade path, but it is safe, so you can always go back to your previous stock build if you want.
Q9Nap said:
Updated the OP with the latest retail build NPSS26.118-19-11.
Unlike most carrier unlocked moto devices, which tend to have multiple upgrade paths for different regions, the albus seems to have only one upgrade path for the retail variant so far.
Someone correct me if I'm wrong, and please post the OTA files for alternate upgrade paths if you have them; directions are in the OP.
I have linked the tools I use to create these at the bottom of the OP.
You can use these tools and info in their threads to reverse engineer the stock build and modify it to your liking.
Click to expand...
Click to collapse
Thanks @Q9Nap!
I've attempted to follow your instructions about applying OTA via TWRP, but that fails because of mismatching thumbprint - which sounds odd since I've downloaded and attempted to flash on exactly the same device...
Anyway, I'll try soon to flash the full stock ROM, after download from the link you've re-posted.
New update NOT PATCHED YET NPSS26.118-19-14
https://drive.google.com/file/d/1df6c3cWDU0mxt__mFhL-GiqzQzLWdKrD/view?usp=drivesdk
Contains November security updates
This has not yet been patched please wait for OP to do So
@Q9Nap can you put a tutorial on here telling us how to make a update flashable