Database Info

[Q] How do I root the AT&T Avail (ZTE Z990)?

What I have tried:
SuperOneClick (all versions) <-- Siege Tanks Were Doomed
Gingerbreak <-- Just sits there
Z4Root <-- doesn't do anything
Rageagainstthecage <-- doesn't work
tried flashing Clockwork mod via tcard like works for the ZTE Blade, phone pretends like it is working then reboots and no change, trying to start using the power button and vol - yields nothing.
tried cooking my own rom with the kitchen make the update.zip file
Do adb reboot recovery
the phone comes back to the android system recovery <3e>
I select the option to do update.zip from sdcard
I get:
verifying update package...
installation aborted...
I need root access to remove the AT&T preloaded apps that won't uninstall won't stay killed and are hogging all my space on the phone (limited storage). I would also like to be able to upgrade to 2.3.7 from my current 2.3.4 and possibly make my own roms.
I have emailed ZTE Chinese support to see if I can get an non pork filled rom the Indian who answered their tech support line didn't have an answer and told me not to flash the ZTE roamer rom (if I could even find it) because it will brick my phone. They have been no help!
What am I doing wrong in the android recovery (I have tried both installer scripts)? Is there a way to rebuild the system.img from the system folder that was created in the kitchen because I might be able to rebuild it into the .bin file that the phone will accept from a sdcard with the built in update feature?

Ok so I figured out how to repack the system.img I then dropped it back into the folder and used zte-pack.exe to build my .bin file. I go to the tcard update and it fails verification...is there a signature that needs to be made? I didn't see an option in zte-pack

i got the same phone with at&t....was unable to root it either, but i only tried super one click...
good luck and share, if you find a way.

Not sure if there is away as of yet. Just did a fast search and it seems no root has been done for it yet

try another time z4root

I am unable to root my XT928 either...Good Luck!

Apo11on said:
i got the same phone with at&t....was unable to root it either, but i only tried super one click...
good luck and share, if you find a way.
Click to expand...
Click to collapse
I am soooo close just need that extra little bit of help, I will get it and when I do I will definitely share. I've only had a droid for 2 weeks and I have come this far, I am not going to stop. I have a BS in Computer Science and used to be a MCSE, I don't know this tech well enough yet but I will. Just hoping someone on here has the skillset I need to help complete this,

primanka said:
try another time z4root
Click to expand...
Click to collapse
tried it multiple times as I have with all of the one click exploits and custom rom trials

We got root, just need a forum to post, and maybe anotehr tester if someone is interested.
Shoot me a pm

jcase said:
We got root, just need a forum to post, and maybe anotehr tester if someone is interested.
Shoot me a pm
Click to expand...
Click to collapse
Thank you kind Sir! jcase to the rescue again - spent a couple of hours with me and busted this thing open. I can confirm my AT&T Aveil ZTE Z990 is fully rooted now. Mad props to jcase

{
"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"
}
Will post instructions after I Get another tester and write it up, however I am submitting a CVE And reporting it to google/zte. It is particularly dangerous (as far as malware abusing it).

jcase said:
Will post instructions after I Get another tester and write it up, however I am submitting a CVE And reporting it to google/zte. It is particularly dangerous (as far as malware abusing it).
Click to expand...
Click to collapse
Just woke up and saw this...can't wait to test thanks. PM Sent

I can confirm it works..I am now rooted!
jcase said he will post later... was able to remove the annoying at&t apps and gain back 30mb using titanium back...now to learn how to flash a custom rom...

http://www.androidpolice.com/2012/0...e-avail-att-offer-quick-and-easy-root-access/
enjoy

There are detailed instructions for rooting, unlocking, other ROMs and more on a Russian site but I don't understand much of it. If anyone can help out it would be great!
I'm prevented from posting links here but search for zte Roamer unlock.

schoolage said:
There are detailed instructions for rooting, unlocking, other ROMs and more on a Russian site but I don't understand much of it. If anyone can help out it would be great!
I'm prevented from posting links here but search for zte Roamer unlock.
Click to expand...
Click to collapse
we know about this - i'm fluent in russian. none of their file links work - it's an old thread on 4pda forums. you can use translate.google.com or several other engines, to translate web pages in real time.

according to ZTE although they share the same model numbers they have different radios (IE GSM / CDMA) and flashing the roamer to the avail will brick it. Apparently ZTE has not gotten the concept of using distinct model numbers yet...

I was able to get root by simply entering *983*7668#. watch the screen and you will see a message that says wait a few minutes for root. I then installed superuser and Titanium Backup proceeded to remove the apps I didn't want/need, I was also able to backup everything else that I wanted to!

theloon said:
I was able to get root by simply entering *983*7668#. watch the screen and you will see a message that says wait a few minutes for root. I then installed superuser and Titanium Backup proceeded to remove the apps I didn't want/need, I was also able to backup everything else that I wanted to!
Click to expand...
Click to collapse
How did you run Titanium Backup without installing a su binary?

shimapan said:
How did you run Titanium Backup without installing a su binary?
Click to expand...
Click to collapse
It just worked, even after a fresh flashing of the T card image.bin from ZTE.
Oh and heres a little batch file with needed files to automate jcase's procedure.

[Toolkit] Wug's Nexus Root Toolkit v2.1.4 [Updated 01/16/16]: Nexus 7 (2013) Thread

Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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 read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}

I can't find 1.6.6 it still says "Version 1.6.6 coming soon, ETA = 07.28.2013"
Thanks.

ashik992 said:
I can't find 1.6.6 it still says "Version 1.6.6 coming soon, ETA = 07.28.2013"
Thanks.
Click to expand...
Click to collapse
Maybe try clearing browser cache. Here are some external mirrors:
Mediafire: [redacted]
Dev-host: [redacted]
Enjoy! ^_^
{{ WugFresh }}

Thx Wug! I was wondering if you were going to update the toolkit to work with flo, and BAM! Here it is! Love your work, hope you keep at it. :good:

I did not chose twrp
I use 1.66 to root my nexus 7 (2012) and I did not check the (also flash custom recovery) first pass was pushing temporary twrp, and second it flash the twrp.
Why? I get a real problem with twrp with the 4.3 update, so I did not want it in my device.
Is this a bug in the toolkit? or there is a reason why the twrp is push without asking to flash?
Still the best toolkit I ever use.

You may want to change the main body font. It's almost impossible to read on the xda app with the dark theme selected
prshosting.org

Thanks for your work. I first ran and used the "raw driver" install. Went to step 3 and ran the "check". "Success"! When installing Root & Recovery, it gets to the point where it says pushing root files to device, but when it's supposed to boot into TWRP, it boots into system "android man with red exclamation mark on his belly" mode. Tried it twice with the same result. Any ideas? I did notice that in Device Mgr "portable devices" isn't showing at all. However in Prompt mode, an "adb devices" shows device serial #. It's as if TWRP wasn't flashed correctly.

melfunn said:
Thanks for your work. I first ran and used the "raw driver" install. Went to step 3 and ran the "check". "Success"! When installing Root & Recovery, it gets to the point where it says pushing root files to device, but when it's supposed to boot into TWRP, it boots into system "android man with red exclamation mark on his belly" mode. Tried it twice with the same result. Any ideas? I did notice that in Device Mgr "portable devices" isn't showing at all. However in Prompt mode, an "adb devices" shows device serial #. It's as if TWRP wasn't flashed correctly.
Click to expand...
Click to collapse
Same issue I'm having.

Thanks for the app! Unlocking went fine, I'm hesitant to root if it's going to leave me with TWRP even if I leave that field unchecked, anyone else have the same problem as Lachaine? Or has anyone successfully gained root and maintained stock recovery with this?

funkbucket007 said:
Same issue I'm having.
Click to expand...
Click to collapse
Please try enabling this option:
Cheers.
{{ WugFresh }}

Thanks for all your hard work on this, and for sharing it with the community!! It's great having multiple options!!! I didn't use this, but just wanted to say thanks for building this and freely sharing it!!!! It's devs like you that make XDA such a great community to be a part of!!!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium

WugFresh said:
Please try enabling this option:
Cheers.
{{ WugFresh }}
Click to expand...
Click to collapse
Check that option and start over with the root process?

I'm having the same problem. Made the changes in setting and no difference.

jsnietka said:
I'm having the same problem. Made the changes in setting and no difference.
Click to expand...
Click to collapse
Same here.
Sent from my SAMSUNG-SGH-I317 using xda premium
---------- Post added at 02:50 PM ---------- Previous post was at 01:53 PM ----------
k5mitch said:
Same here.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
jsnietka said:
I'm having the same problem. Made the changes in setting and no difference.
Click to expand...
Click to collapse
Third time is a charm.:good:

k5mitch said:
Same here.
Sent from my SAMSUNG-SGH-I317 using xda premium
---------- Post added at 02:50 PM ---------- Previous post was at 01:53 PM ----------
Third time is a charm.:good:
Click to expand...
Click to collapse
Are you saying it finally worked?
I've done it twice same lil dead android with the red triangle.
Guess I'll try again

Unlocked, rooted and installed TWRP. No problems.
Thanks!

feron said:
Are you saying it finally worked?
I've done it twice same lil dead android with the red triangle.
Guess I'll try again
Click to expand...
Click to collapse
ODD.. third time it worked... lol

feron said:
ODD.. third time it worked... lol
Click to expand...
Click to collapse
Well after I checked the option wug suggested I closed the program and re-started it. Walah it worked.
Sent from my SAMSUNG-SGH-I317 using xda premium

k5mitch said:
Well after I checked the option wug suggested I closed the program and re-started it. Walah it worked.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Yes don't forget to restart the toolkit before trying again. Worked for me when I did. Thanks wug!

Having an issue. Stock build# is JWR66N but is not listed, so i choose the closest one, JWR66V. So far it installed the adb drivers but fails on the Full Driver Test and Checking ADB Status. The device shows up perfectly now in DM, as a Nexus7, so the drivers have a clean install. Rebooted 2-3 times already. I can go to the adb command line and its installed but not sure why the app or PC doesn't see it setup right? I cant continue to the next steps if adb is not right...lol

How to install January 5th patch while using custom recovery and root on Google Pixel

Okay, I am sure a lot of you already know how to do this to your Pixel. Some of us do not, and I was one of them. I am the standard noob that just followed Youtube videos to unlock previous carrier locked phones. I am now enjoying this Google Pixel that is unlocked!
So if you are reading this thread, hopefully there isn't another one just like this (yes I looked).
To start off, if you are in here reading this, you have unlocked your bootloader and installed a custom recovery such as TWRP and rooted. Now you are seeing that you need to update your phone with the latest security patch. You try and you try and you can't do it. Even when you unroot it will still fail to update, or at least it did for me. Here I will explain what I went through and did to obtain the latest update. (Warning, you will loose root and custom recovery). THIS IS INTENDED FOR THE GOOGLE STORE PURCHASED PHONES
Lets get this started finally.....
Go into your developer options and enable usb debugging.
Download the newly released package file from google that has fastboot and ADB without needing android SDK.
DOWNLOAD or read about it HERE
Now you will need to download the Factory Image for you device
Find your correct device HERE
Make sure you choose the correct device and correct update, for me I downloaded the "7.1.1 (NMF26U, Jan 2017)" for my Pixel. Also a USA phone.
So now you have the adb fastboot binary package and your factory image. You will need to extract the platform-tools-latest-windows.zip and open the folder and you will see another folder, open it and now you will see a bunch of files. Now open another window and extract your factory image. Once it is done, open the folder until you see the files. Now copy these into the Platform tools folder in the directory with the fastboot.
Once this is done your folder should look like this:
{
"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"
}
Now you will want to right click "flash-all" and click edit. It will open notepad and show the contents of the batch file. You can hit Ctrl+F and type in -w in the search and hit okay, or you can look for it without search (it is near the bottom). Once you find it, just delete the "-w" and save the file. Make sure to keep it as the batch file or this won't work.
Once this is done, in the folder that is shown above, click a blank area in the folder so no file is highlighted. Now hold shift and right click, it will come up with a dialog saying open command window here, click that.
Now we are going to reboot the phone into bootloader mode. In the command window, type everything that is underlined below
adb reboot bootloader
Now your phone should have booted into the bootloader screen or it should be asking for USB rights to use adb. If it asks for permission, hit okay and re run the code above and your phone should reboot.
Once you are in the bootloader screen you will need to do is run the flash-all.bat. It will load and go though some text on the CMD window it brings up. It will say some files are missing, which is fine. But if it fails it will tell you that it did. You can also tell by rebooting the phone or click "start" in the bootloader mode and then checking for OTA updates. It should say January 5th patch installed.
Now you can go through and install your custom recovery again and re root. Which takes no time at all and I am sure someone on here has posted before. If not, let me know and I can make a tutorial over it.
Note: I am very sorry for the bad layout and extended write up. First time ever doing this and I am hoping to help people. If there are any errors, let me know!

All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.

zelendel said:
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
Click to expand...
Click to collapse
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself

exbtlegends said:
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
Click to expand...
Click to collapse
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.

jrat69 said:
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
Click to expand...
Click to collapse
Not a problem ?

I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.

32BitWhore said:
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
Click to expand...
Click to collapse
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.

This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.

Good work. This is a very minute stuff of removing -w from the batch file. Very handy work.
Sent from my Pixel using Tapatalk

Do you need to reflash stock kernel before removing root/TWRP before flashing?

32BitWhore said:
Do you need to reflash stock kernel before removing root/TWRP before flashing?
Click to expand...
Click to collapse
Flashing the image overwrites anything you customized besides the regular user data and internal storage (with the -w removed). You don't have to remove or reflash anything else before following these instructions.

TCPDump said:
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Click to expand...
Click to collapse
I couldn't side load the update.. TWRP would not load the side load feature.

I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?

km8j said:
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
Click to expand...
Click to collapse
Even when I un rooted mine. I was still failing to get the update.

If you made any changes the the system partition then it will fail and simply unrooting doesn't make the all the changes needed. So if OTA mean anything to you then I would suggest not messing with your device as there is Jo promise that after an OTA you will be able to root again tonight away

jesssiii said:
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
Click to expand...
Click to collapse
I know the past 2 were the same for google pixel and Verizon pixel but I wouldn't assume they are always going to be. I'm sure some of them will be specific at times whenever Verizon decides they wanna mess with them

FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.

SpoiledHeeb said:
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
Click to expand...
Click to collapse
You need SuperSU 2.79 RC3

[OOS][Oreo] Enable Google Daydream VR Support

For Oxygen OS - 5.1.3 Oreo on Oneplus 5T.
Flash in TWRP after making a backup.
Please read all info below.
{
"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"
}
!!! CAUTION !!!
Use at your own risk. Backup before flashing.
I am not responsible for bricked devices,
thermonuclear war or your monkey dancing samba!
IMPORTANT INFO:
Flashing
The installer changes one file. It overwrites \system\etc\permissions\handheld_core_hardware.xml
with an updated version to enable the Google Daydream support.
Removing
There is also the remover ZIP. It restores the stock OOS 5.1.3 permission file.
After flashing - get ready
You wiped your cache and dalvik and boot the device.
Go to your application list and show system apps.
Delete cache and data of the Play Store app so Daydream is
downloadable via Play Store. Open Play Store,
do not forget to set your previous Play Store configuration and install:
• Daydream
• Daydream Keyboard
• Google VR Services
Some reported that setting to skip all intros in Daydream developers options
fixed problems that occured.
Start, set the other config which is needed and try. For me it works fine.
The only thing that is a bit sad is that the 5T with full HD gives a not very sharp display view - it is grainy.
๏[-ิ_•ิ]๏

Does it work on 5.0.3?
Also, does it trigger the 'safetynet'?

lockywolf said:
Does it work on 5.0.3?
Click to expand...
Click to collapse
Actually the file did not change for 5.0.3, but I changed the ZIP filename to clearify.
lockywolf said:
Also, does it trigger the 'safetynet'?
Click to expand...
Click to collapse
I don't think so.
By the way; it is a tiny mod that does no heavy system tweaking.
I made it just for convenience so users do not need to use a root explorer and text editor for the changes.

Thank you.
Just FYI, it's not working in Oreo Resurrection Remix.
I can open Daydream without issue.
But as soon as I put my OP5T into the headset, the OP5T hard reboots.
I attached a logcat in case anyone is interested.

CZ Eddie said:
Thank you.
Just FYI, it's not working in Oreo Resurrection Remix.
I can open Daydream without issue.
But as soon as I put my OP5T into the headset, the OP5T hard reboots.
I attached a logcat in case anyone is interested.
Click to expand...
Click to collapse
This is happening to me as well on AICP. Wanting this to work lol. Please keep me updated if you find anything out!

CZ Eddie said:
Just FYI, it's not working in Oreo Resurrection Remix.
Click to expand...
Click to collapse
bschmidy10 said:
Please keep me updated if you find anything out!
Click to expand...
Click to collapse
See, I am not a real dev... just some guy with basic knowledge. I updated the ZIP and made two new for the ROMs you use.
Try them, but read the OP/CAUTION section please.
The attached ZIPs contain the modified file from your ROMs which are different in one line compared to OOS.
Plus I added a mod for the build.prop to maybe make it work.
If all fails I guess this try was just an interesting waste of time,
and someone more advanced would have to figure out a possible solution.
•••

Thank you!
I'm sorry but my Resurrection Remix Oreo still forced rebooted when I put the phone into the headset. I attached another logcat if you're interested.

CZ Eddie said:
Thank you!
I'm sorry but my Resurrection Remix Oreo still forced rebooted when I put the phone into the headset. I attached another logcat if you're interested.
Click to expand...
Click to collapse
As I wrote I can not help any further.
I installed Google VR keyboard, Daydream, VR services etc. and tested some apps under OOS 5.0.3, but all without VR hardware - I do not own the headset/controller. I enabled developer options on Daydream and skipped all intros, read that elsewhere.

I've got the same problem, RR 8.0.1. Logcat implies that the ACore process lacks permissions to access the VR hardware, and crashes upon attempting it, taking the entire systemui and all of its children with it.
I'm in the process of experimenting and seeing if it's possible to grant those permissions somehow..

Anybody got it working? I saw the set today at a store and thought about buying it...

This has always worked for me: https://www.xda-developers.com/force-daydream-vr-compatibility/
never needed to change the device name, just added the 2 lines and rebooted. Daydream apps download and update via playstore as well.

OTA Updates
Does unlocking bootloader, flashing twrp and installing this, cause problems with OTA Updates or something?

aschi2403 said:
Does unlocking bootloader, flashing twrp and installing this, cause problems with OTA Updates or something?
Click to expand...
Click to collapse
Did you face problems with OTA? I will update this if I find the time.
Gesendet von meinem ONEPLUS A5010 mit Tapatalk

t-ryder said:
Did you face problems with OTA? I will update this if I find the time.
Gesendet von meinem ONEPLUS A5010 mit Tapatalk
Click to expand...
Click to collapse
No I din't face any, I just wanted to know if there are known problems before I install this.
But now I have a new Question. I thought to not mess around with OTA as I read on some XDA-Thread that TWRP might keep official OTA from working, I would just unlock the bootloader and then boot into TWRP with "fastboot boot recovery.img", flash this zip and reboot into stock OOS with this guide https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592 on.
But then on the twrp Website I read that "swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel" so my question is, can I flash this zip without messing around with OOS, I don't really want to install a custom kernel, because for now I just want the stable stock rom.

aschi2403 said:
No I din't face any, I just wanted to know if there are known problems before I install this.
But now I have a new Question. I thought to not mess around with OTA as I read on some XDA-Thread that TWRP might keep official OTA from working, I would just unlock the bootloader and then boot into TWRP with "fastboot boot recovery.img", flash this zip and reboot into stock OOS with this guide https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592 on.
But then on the twrp Website I read that "swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel" so my question is, can I flash this zip without messing around with OOS, I don't really want to install a custom kernel, because for now I just want the stable stock rom.
Click to expand...
Click to collapse
I tried it and I didn't face any of my concerns, but I'm on OxygenOs 5.1.2 and after flashing this, wiping cache, then reboot. Daydream App after a long black screen shows me, that my device isn't compatible with Daydream. Did I do something wrong or is it because of the OxygenOS Version?

EDIT: see post #19

I just bought a Daydream Set (v1) for like 20$ second hand online. Will report regarding further testing when the set has arrived.

Updated for Oxygen OS 5.1.3

Got my headset and all works fine. The image is a bit grainy because 5T has only full HD.
No need for an installer with build.prop changes. I tested the system changes and updated the installer and remover.
If you have tried the old installer/enabler you may restore your build.prop using a root file explorer. It is located in /system (.bak file).
Have fun.

M.Sami said:
never needed to change the device name, just added the 2 lines and rebooted.
Click to expand...
Click to collapse
Yes, you are right.

Lg g7 thinq (lg710pm) to (g710ulm10g)

Few weeks ago i got a LG G7 “UNLOCKED” on ebay, the phone had a sticker where it said model “LGG710PM”, the bad news i was stuck with a FIRMWARE LM-G710ULM (V10b-LAO-COM) MAY 2018. I tried updating the phone via OTA or LGBridge and i had no luck. So i looked online for the correct KDZ file for the LGG710PM and also no luck, So what i did is look for a G710ULM KDZ, but the only one the i could find was the G710ULM10G_00 (https://www.mylgphones.com/lg-g7-thinq-project-fi-stock-firmware-g710ulm10g.html) . So after searching online and watching some videos on youtube if this could work, i found a youtuber video (MAXLEE) he change a FIRMWARE of sprint to a Canadian FIRMWARE and it work he did it on a LG G6. So what i did is try it on MY G7 model LGG710PM“ the only thing is that on the G7 there's a few more steps to do:
1) Download G710ULM10G_00 KDZ file
https://www.mylgphones.com/lg-g7-thinq-project-fi-stock-firmware-g710ulm10g.html
2) Download LGUP and install (make sure to use this link for download and follow instructions, like this you don't get an error when
you insert the KDZ file and hit START).
https://mega.nz/#!kCpHBaia!xZmico6MYL1T07ffuc8z6cCbs5oU4pKEz5VG-AwfvV0
A) Make sure you don't have LGBrige installed, if so UNINSTALL and delete any folder of LGBridge after you have uninstalled
(C:\Program Files (x86)\LG Electronics)
B) Download the LGUP zip file and unzip, if you don't have the drivers install lgdrives(The file is inside the folder LGUP-LG G7 ThinQ).
After that install “LGUP_Install_Ver_1_14_3 (1).msi “ file.
{
"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"
}
C) After installing LGUP you must go to C:\Program Files (x86)\LG Electronics\LGUP and copy the first three files(CODEFIRE, LOG,
model) from the UNZIPED FILE from step B.
D) Go to file “model” (C:\Program Files (x86)\LG Electronics\LGUP\model) then go to file “common”....go to step “E” don't close the
window….
E) Go to the UNZIP FOLDER, go to file WindowsLGFirmwareExtract-1.2.6.1-Release. Run “WindowsLGFirmwareExtract.exe” and select
the KDZ file you downloaded, then make sure you
check on “LGUPc.dll. EXTRACT KDZ.
F) A file “LGUPc.dll” will be created, Copy that file into the folder “common”...... you should had left that window open from step “D”. Rename the actual “LGUP_Common.dll” to
“LGUP_CommonDDD.dll” and “LGUPc.dll” to “LGUP_Common.dll” and then deltate the “LGUP_CommonDDD.dll”.
Open LGUP...put your phone in download mode... select the KDZ file you downloaded from step “1” and in PROCESS select REFURBISH…. Then click START.

Thanks for posting the guide but I don't see any links to download the files on step 2

hytl said:
Thanks for posting the guide but I don't see any links to download the files on step 2
Click to expand...
Click to collapse
True, already put the link, thanks.

Radha09 said:
True, already put the link, thanks.
Click to expand...
Click to collapse
Thank you. I wonder after we upgrade to this firmware, will we be able to get OTA update?

hytl said:
Thank you. I wonder after we upgrade to this firmware, will we be able to get OTA update?
Click to expand...
Click to collapse
i hope so....

I got SPC Code does not match error.

hytl said:
I got SPC Code does not match error.
Click to expand...
Click to collapse
Where did you get that error?

After I click start in LGUP

hytl said:
After I click start in LGUP
Click to expand...
Click to collapse
Did you see the video from Victor Hernandez i know its in Spanish but just to make sure you made the steps.... and one more thing i forgot to mention is that before putting start you need to have you phone in download mode here's a link ....... https://www.youtube.com/watch?v=EkKfPPBzJ1c

Radha09 said:
Where did you get that error?
Click to expand...
Click to collapse
Radha09 said:
Did you see the video from Victor Hernandez i know its in Spanish but just to make sure you made the steps.... and one more thing i forgot to mention is that before putting start you need to have you phone in download mode here's a link ....... https://www.youtube.com/watch?v=EkKfPPBzJ1c
Click to expand...
Click to collapse
Thanks. It's flashing now. I didn't put the phone into download mode.

hytl said:
Thanks. It's flashing now. I didn't put the phone into download mode.
Click to expand...
Click to collapse
:good:

hytl said:
Thanks. It's flashing now. I didn't put the phone into download mode.
Click to expand...
Click to collapse
Cool, sorry that i forgot to mention that step.....hope it works for you too.

Could you please post screenshot of your phone software info? Is your SN under Hardware info blank?

hytl said:
Could you please post screenshot of your phone software info? Is your SN under Hardware info blank?
Click to expand...
Click to collapse
SN under Hardware is BLANK that has always been that way.... cant fix that.

I just checked with LGBridge. It still says "Cannot check software version. Please try again". I don't think we will be able to do OTA update in the future.

hytl said:
I just checked with LGBridge. It still says "Cannot check software version. Please try again". I don't think we will be able to do OTA update in the future.
Click to expand...
Click to collapse
Yeah, i think its because the firmware is from another hardware and not the sprint.... at least we are not stuck on MAY......

Radha09 said:
Where did you get that error?
Click to expand...
Click to collapse
Radha09 said:
Yeah, i think its because the firmware is from another hardware and not the sprint.... at least we are not stuck on MAY......
Click to expand...
Click to collapse
Yeah. I'm glad that we aren't stuck on May patch anymore. I don't remember but I don't think I had wifi calling before I flash this. Now I got wifi calling, so great. Thanks for the great guide.

Great! So is safe to flash then . Besides S/N still blank, any other side effect after flash? I assume storage 64gb still same, imie # still same, phone still unlocked, lte signal better? Good to see wifi calling is enabled.
Sent from my LM-G710 using Tapatalk

jonahy said:
Great! So is safe to flash then . Besides S/N still blank, any other side effect after flash? I assume storage 64gb still same, imie # still same, phone still unlocked, lte signal better? Good to see wifi calling is enabled.
Click to expand...
Click to collapse
Yes I guess it's safe it worked for me and also for member hytl. Everything is working fine, the phone is still unlocked, and everything else is the same nothing changes. You get battery improvement and camera. LTE signal it's the same for me.

Thanks Im gonna try later.. Do I need to do factory rest before flash and after?