I've been on android 8 for a few weeks via the 'trail' oreo on my Chinese A2017 version. Don't bother it's full of bugs. System UI crashes repeatedly particularly when using Spotify. Wi fi is now unable to transfer from main router to a booster. battery life is worse. it appears to have corrupted my SD card too!!!
front firing speakers said:
I've been on android 8 for a few weeks via the 'trail' oreo on my Chinese A2017 version. Don't bother it's full of bugs. System UI crashes repeatedly particularly when using Spotify. Wi fi is now unable to transfer from main router to a booster. battery life is worse. it appears to have corrupted my SD card too!!!
Click to expand...
Click to collapse
Haven't they been all beta builds? That's kinda what I expect.
front firing speakers said:
I've been on android 8 for a few weeks via the 'trail' oreo on my Chinese A2017 version. Don't bother it's full of bugs. System UI crashes repeatedly particularly when using Spotify. Wi fi is now unable to transfer from main router to a booster. battery life is worse. it appears to have corrupted my SD card too!!!
Click to expand...
Click to collapse
-The systemUI thing hasn't happened to anyone over the telegram chat, and they used B01 and B09. including slim
-Dunno about the wifi thing
-Battery life is the same for the people who tested
-Your SD isn't corrupt, you have to format it from the ROM. Get everything off of it via TWRP and format it from the ROM itself
what version of oreo your talking about?
8.0 for that was released formally for the A2017. Not as stable as android 7
Choose an username... said:
-The systemUI thing hasn't happened to anyone over the telegram chat, and they used B01 and B09. including slim
-Dunno about the wifi thing
-Battery life is the same for the people who tested
-Your SD isn't corrupt, you have to format it from the ROM. Get everything off of it via TWRP and format it from the ROM itself
Click to expand...
Click to collapse
That's gobbledygook to non mod routing folk. what does get off via TWRP mean?
front firing speakers said:
That's gobbledygook to non mod routing folk. what does get off via TWRP mean?
Click to expand...
Click to collapse
Boot in TWRP,connect device to laptop/pc and copy all your stuff from microSD to your laptop/pc.
When you have done this,unplug the cable and reboot the system.
Then go to storage,select your microSD and format (NOTE: everything will be deleted from your microSD)
after the format,your microSD should work as it should be
do I download TWRP from the Google play store? and presumably follow instructions given one imagines?
why after Oreo update are there many more completely unnecessary messages. Android system regarding your SD card, Gmail and other apps running in the background. Rather annoying
Choose an username... said:
-The systemUI thing hasn't happened to anyone over the telegram chat, and they used B01 and B09. including slim
-Dunno about the wifi thing
-Battery life is the same for the people who tested
-Your SD isn't corrupt, you have to format it from the ROM. Get everything off of it via TWRP and format it from the ROM itself
Click to expand...
Click to collapse
Got everything off my SD card via TWRP, 19 hours for a 256GB. Reformatted it in B35. Still corrupt. Craziest thing, TWRP, Oreo rom, and windows can still read my SD. B35 used to be able to. Stumped.
---------- Post added at 07:45 AM ---------- Previous post was at 07:25 AM ----------
Formatted sd card as FAT in TWRP and now B35 can see it.
front firing speakers said:
do I download TWRP from the Google play store? and presumably follow instructions given one imagines?
Click to expand...
Click to collapse
Oh, you are still locked just put the sd card somewhere so that you can read it and put everything on your pc, maybe an sd card reader like the laptop ones or another phone
JKSurf said:
Got everything off my SD card via TWRP, 19 hours for a 256GB. Reformatted it in B35. Still corrupt. Craziest thing, TWRP, Oreo rom, and windows can still read my SD. B35 used to be able to. Stumped.
---------- Post added at 07:45 AM ---------- Previous post was at 07:25 AM ----------
Formatted sd card as FAT in TWRP and now B35 can see it.
Click to expand...
Click to collapse
If you use magisk 15.x and your sd card is exFAT, you will get message "sd card is corrupted".
You should use magisk 14 if you want to get exFAT sd card working.
It worked for me on b35 with different sd cards.
Srgqw said:
If you use magisk 15.x and your sd card is exFAT, you will get message "sd card is corrupted".
You should use magisk 14 if you want to get exFAT sd card working.
It worked for me on b35 with different sd cards.
Click to expand...
Click to collapse
I'll give it a shot but 15 was working before for me with exFAT.
---------- Post added at 12:56 PM ---------- Previous post was at 12:35 PM ----------
@Srgqw You're right. Magisk was our issue. 14 works with exFAT
I agree the oreo stock rom on 2017a is horrible even after the latest update ... system ui crashes all the time especially relating to google apps. Chromecast/maps all not working properly. I'm rolling back to an earlier release but I can't find a recent stock rom for the A2017 - has anyone got one? The zte site seems to have taken them down.....
[email protected] I downloaded 7.1.1 b15 and when I tried loading update.zip it failed...so looks like moving backwards is not easy!
Jules_wake said:
I agree the oreo stock rom on 2017a is horrible even after the latest update ... system ui crashes all the time especially relating to google apps. Chromecast/maps all not working properly. I'm rolling back to an earlier release but I can't find a recent stock rom for the A2017 - has anyone got one? The zte site seems to have taken them down.....
[email protected] I downloaded 7.1.1 b15 and when I tried loading update.zip it failed...so looks like moving backwards is not easy!
Click to expand...
Click to collapse
Do you like resurrecting dead threads?
Do you like giving insightful replies to dead threads?!
Jules_wake said:
Do you like giving insightful replies to dead threads?!
Click to expand...
Click to collapse
Not usually.
Running a 2/24 build of AEX with HellsGate 1.2.1 and the only problem I have is GPS takes a minute to lock. Otherwise not sure what everyone has issues with.
Oh yeah I use hangouts for phone calls, so that may be why I never experience call issues.
A2017G / Rom stock V3.00 B11 flashed with TWRP 3.2.1.6 + G modem :
- installed Google play store to update android play services, then DEACTIVATE AND REACTIVATE play services, no bugs, dual sims ok, no call bug, no battery drain.
- Button mapper on the store is great to bypass "myvoice"
- We can't modify build.prop to set all the right settings for international stuffs unless applying nfound boot patch that breaks dolby. Still trying to find out why exactly. (if someone has an idea of why ...)
So, it's a nice working rom for what is it : a beta.
Sn8K said:
A2017G / Rom stock V3.00 B11 flashed with TWRP 3.2.1.6 + G modem :
- installed Google play store to update android play services, then DEACTIVATE AND REACTIVATE play services, no bugs, dual sims ok, no call bug, no battery drain.
- Button mapper on the store is great to bypass "myvoice"
- We can't modify build.prop to set all the right settings for international stuffs unless applying nfound boot patch that breaks dolby. Still trying to find out why exactly. (if someone has an idea of why ...)
So, it's a nice working rom for what is it : a beta.
Click to expand...
Click to collapse
I'm not sure if I am reading this correctly. are you talking about THE beta? you have the rom? I did not see any post that it was leaked
edit: you also quote twrp 3.2.1.6 but the latest is 3.2.1.0, are you from the future?
rzarectha said:
I'm not sure if I am reading this correctly. are you talking about THE beta? you have the rom? I did not see any post that it was leaked
edit: you also quote twrp 3.2.1.6 but the latest is 3.2.1.0, are you from the future?
Click to expand...
Click to collapse
Nope it's not THAT beta but the chinese one you can find here : https://forum.xda-developers.com/axon-7/development/edl-package-edl-package-t3754862
And afaik he's not from the future because twrp 3.2.1.6 is available for quite some time now thnx to @NFound....there's even a 7 one
Related
I am shocked to see that our device is on the list of first batch official lineageOS support,
download here and enjoy:
https://download.lineageos.org/v521
I am curious why no one is claiming the bounty for custom roms for V521.
O nice! Let's do this!
googlephone said:
I am shocked to see that our device is on the list of first batch official lineageOS support,
download here and enjoy:
https://download.lineageos.org/v521
I am curious why no one is claiming the bounty for custom roms for V521.
Click to expand...
Click to collapse
Wow! This is unexpected. Anyone tried it yet?
Any way to this thread tagged with so it shows up here :
https://forum.xda-developers.com/t/lg-g-padx
---------- Post added at 09:58 AM ---------- Previous post was at 09:23 AM ----------
Anyone have a good workflow for flashing? I'm rooted, stock 7.0 , unlocked with TWRP installed. Are we just needing to wipe data , and flash the ROM along with Gapps?
For anyone that has installed, does LineageOS retain the expanded desktop feature (immersive mode) that CM had?
The biggest reason for me staying on MM is for Xposed Framework, and a module that forces apps to hide the status bar. With expanded desktop I would have no problem ditching Xposed and upgrading to 14.1 on this tablet.
EDIT: Found this for upgrading, not sure if it is relevant to us -->https://www.reddit.com/r/LineageOS/comments/5qhers/correct_procedure_for_updating_from_cm130_to/
Munns86 said:
Wow! This is unexpected. Anyone tried it yet?
Any way to this thread tagged with so it shows up here :
https://forum.xda-developers.com/t/lg-g-padx
---------- Post added at 09:58 AM ---------- Previous post was at 09:23 AM ----------
Anyone have a good workflow for flashing? I'm rooted, stock 7.0 , unlocked with TWRP installed. Are we just needing to wipe data , and flash the ROM along with Gapps?
Click to expand...
Click to collapse
I'm using it and it's really smooth. Not sure if anything is broken in the first build though. Haven't gotten a chance to test out bluetooth or LTE.
Ravoz88 said:
For anyone that has installed, does LineageOS retain the expanded desktop feature (immersive mode) that CM had?
The biggest reason for me staying on MM is for Xposed Framework, and a module that forces apps to hide the status bar. With expanded desktop I would have no problem ditching Xposed and upgrading to 14.1 on this tablet.
EDIT: Found this for upgrading, not sure if it is relevant to us -->https://www.reddit.com/r/LineageOS/comments/5qhers/correct_procedure_for_updating_from_cm130_to/
Click to expand...
Click to collapse
Yeah, immersive mode is still available on LineageOS on the v521.
emilyrugburn said:
I'm using it and it's really smooth. Not sure if anything is broken in the first build though. Haven't gotten a chance to test out bluetooth or LTE.
Yeah, immersive mode is still available on LineageOS on the v521.
Click to expand...
Click to collapse
Which gapps did you use? I've tried both the Arm64 7.1 nano and pico from opengapps.org and they are both giving me an error 64 when flashing. I was able to flash the ROM just fine.
EDIT: figured it out. I though the 617 was 64bit. I was able to flash just the Arm (non-64bit) pico's just fine.
Also did you flash the root zip?
Only issue I've seen so far is it seems like the screen randomly shuts off. Like it seems to coincide with me tilting the tablet maybe.
EDIT: Sadly I found the answer. It seems to be the magent in my case. Never had the issue with stock. It's one of those smart covers ones
Munns86 said:
Which gapps did you use? I've tried both the Arm64 7.1 nano and pico from opengapps.org and they are both giving me an error 64 when flashing. I was able to flash the ROM just fine.
EDIT: figured it out. I though the 617 was 64bit. I was able to flash just the Arm (non-64bit) pico's just fine.
Also did you flash the root zip?
Only issue I've seen so far is it seems like the screen randomly shuts off. Like it seems to coincide with me tilting the tablet maybe.
Click to expand...
Click to collapse
Yes you just want to use regular ARM 7.1 gapps. I have used root zip and it seems to work just fine. I have not noticed any kind of screen randomly shutting off, you sure its not double tap misfiring?
Sadly I found the answer. It seems to be the magent in my case. Never had the issue with stock. It's one of those smart covers ones.
Munns86 said:
Which gapps did you use? I've tried both the Arm64 7.1 nano and pico from opengapps.org and they are both giving me an error 64 when flashing. I was able to flash the ROM just fine.
EDIT: figured it out. I though the 617 was 64bit. I was able to flash just the Arm (non-64bit) pico's just fine.
Also did you flash the root zip?
Only issue I've seen so far is it seems like the screen randomly shuts off. Like it seems to coincide with me tilting the tablet maybe.
EDIT: Sadly I found the answer. It seems to be the magent in my case. Never had the issue with stock. It's one of those smart covers ones
Click to expand...
Click to collapse
The cpu inside is 64 bit but LG is too lazy to put 64 bit android on it. So our device has 32 bit os with a 64 bit cpu.
It's not simple to convert 32 bit os to 64 bit os because we also need to modify bootloader and other proprietary parts to 64 bit, which is nearly impossible.
Our device doesn't have a dedicated smart cover sensor, but have one regular magnet field sensor.
A dedicated smart cover sensor is some kind of a magnet sensor at a designed location and sensitivity.
The problem may be the developers are trying to use the regular magnet field sensor as the smart cover sensor, but it's not perfect due to non-ideal sensor location and sensitivity.
googlephone said:
Our device doesn't have a dedicated smart cover sensor, but have one regular magnet field sensor.
A dedicated smart cover sensor is some kind of a magnet sensor at a designed location and sensitivity.
The problem may be the developers are trying to use the regular magnet field sensor as the smart cover sensor, but it's not perfect due to non-ideal sensor location and sensitivity.
Click to expand...
Click to collapse
Know of any way to disable it?
I've been running this since last night. So far it's been great. One issue I've had is not being able to use the built in file explorer to copy/paste internal and sdcard storage. Even trying to run it as root give errors. That's the only real issue I've had.
The magnetic sensor is VERY sensitive and the screen shuts off easily with a magnetic case (even with the case open).
Back when this device was first rooted I unlocked the boot loader and installed TWRP for some reason I cannot get my device to boot into recovery. When I try from ADB the device reboots and shows the normal "this device cannot be checked for corruption" screen and hangs. I tried to flash the newer version of TWRP with the same result. Any suggestions of what else to try?
painter_ said:
Back when this device was first rooted I unlocked the boot loader and installed TWRP for some reason I cannot get my device to boot into recovery. When I try from ADB the device reboots and shows the normal "this device cannot be checked for corruption" screen and hangs. I tried to flash the newer version of TWRP with the same result. Any suggestions of what else to try?
Click to expand...
Click to collapse
Strange. Have you tried booting into recovery via the hardware buttons?
Turn the power off.
Press and hold the Power + Volume Down key on the right side of the device until the LG logo is displayed.
Briefly release only the Power key when the LG logo is displayed.
Quickly press and hold the Power key again.
Release all keys when the Factory reset screen is displayed.
Press the Volume keys to highlight Yes, and then the Power key to select factory reset.
Press the Volume keys to highlight Yes, then the Power key to start the reset.
Hey could anyone help me out? Back when I rooted this tablet at the end of November, I installed the TWRP version from the TWRP thread. I don't know what it is about this version, but I have never been able to mount or format external SD cards or OTG USB's.
I'm trying to flash the new LineageOS, but I can't because I can't get the table to friggen mount my external storage!
Anyone have any ideas? Months ago someone said I needed to point TWRP to the mount point, but I have no idea how to do this...I've searched through all of the settings and options.
Thanks!
Ravoz88 said:
Hey could anyone help me out? Back when I rooted this tablet at the end of November, I installed the TWRP version from the TWRP thread. I don't know what it is about this version, but I have never been able to mount or format external SD cards or OTG USB's.
I'm trying to flash the new LineageOS, but I can't because I can't get the table to friggen mount my external storage!
Anyone have any ideas? Months ago someone said I needed to point TWRP to the mount point, but I have no idea how to do this...I've searched through all of the settings and options.
Thanks!
Click to expand...
Click to collapse
What error do you get when you try and mount?
Munns86 said:
What error do you get when you try and mount?
Click to expand...
Click to collapse
I can't even get that far. I am unable to even click on the external drives. TWRP sees them, but I can't select them.
If I try and wipe, format or partition them it returns error 2. I'm sure because they are not mounted, so they are unavailable, and it fails.
I've tried formating in my computer with ext4 and fat32. Still won't mount.
I may try and flash TWRP again. Since I sounds like not everyone has this issue. I have seen at least 2 others that have though.
EDIT: apparently selecting "install" option allows me to then select the OTG, and it mounts...Not in mount, not in wipe, not in partition, and not in file manager. But as soon as I choose the install option it mounts. Boy I could have saved a lot of time if I new about this quirk haha.
---------- Post added at 08:50 PM ---------- Previous post was at 08:18 PM ----------
Flashing LineageOS tonight, my v521 crashes instantly at reboot. The screen flashes and then shuts off immediately.
Fortunately I made a nandroid backup way back when I first rooted it back in November.
Not sure what went wrong. I flashed it again to make sure, and it crashes.
Munns86 said:
Strange. Have you tried booting into recovery via the hardware buttons?
Turn the power off.
Press and hold the Power + Volume Down key on the right side of the device until the LG logo is displayed.
Briefly release only the Power key when the LG logo is displayed.
Quickly press and hold the Power key again.
Release all keys when the Factory reset screen is displayed.
Press the Volume keys to highlight Yes, and then the Power key to select factory reset.
Press the Volume keys to highlight Yes, then the Power key to start the reset.
Click to expand...
Click to collapse
Nope, No Go. I am able to get to the factory wipe screen and go through the motions but the screen freezes and the device is not wiped. I think that I need to use the LG tool and return to stock and start over.
Ravoz88 said:
I can't even get that far. I am unable to even click on the external drives. TWRP sees them, but I can't select them.
If I try and wipe, format or partition them it returns error 2. I'm sure because they are not mounted, so they are unavailable, and it fails.
I've tried formating in my computer with ext4 and fat32. Still won't mount.
I may try and flash TWRP again. Since I sounds like not everyone has this issue. I have seen at least 2 others that have though.
EDIT: apparently selecting "install" option allows me to then select the OTG, and it mounts...Not in mount, not in wipe, not in partition, and not in file manager. But as soon as I choose the install option it mounts. Boy I could have saved a lot of time if I new about this quirk haha.
---------- Post added at 08:50 PM ---------- Previous post was at 08:18 PM ----------
Flashing LineageOS tonight, my v521 crashes instantly at reboot. The screen flashes and then shuts off immediately.
Fortunately I made a nandroid backup way back when I first rooted it back in November.
Not sure what went wrong. I flashed it again to make sure, and it crashes.
Click to expand...
Click to collapse
Do you do a wipe all data when flashing?
Did you come from 6.0 or 7.0?
EDIT: I see from your post in a different thread you were on 6.0
I was on stock 7.0. Used dirtycow to root and install TWRP. TWRP did not mount data and other partitions, so I wasn't able to flash lineageos. Used flashify to flash lineageos and opengapps. Flashed ok, then when starting to boot, saw enter pin to decrypt (except I didn't create a pin, so didn't have it). I was finally able to factory reset and wipe data after playing around in TWRP. Now, I still can't boot into lineageos.. it boots straight into TWRP everytime. Tried reflashing and wiping, still same. Any suggestions?
I tried the nightly. I will retry with experimental.
You can use adb sideload to install your lineage zip.
Place the zip in your adb folder on your C drive.
While in Twrp connect to your computer, then follow the directions detailed in the original post, instead of supersu, change your command to reflect the name of your lineage zip file in your adb folder .
Worked for me. On first boot, put superuser on your main SD card (you will have to enable developer options and allow the new adb key) and then change the USB connection to file transfer instead of USB charge only) ,
boot back into twrp and flash the supersu zip that is on your Main SD card for root.
The current Twrp 3.0.2.0 does not work with 7.1.1 to see the other drives(external, other etc.).
We will need an update to 3.0.2.2 at some point for those on 7.0 like the V500 has available.
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
vsriram92 said:
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
Click to expand...
Click to collapse
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
So nice of their support site to be down...
tomlogan1 said:
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
Click to expand...
Click to collapse
Instructions > https://forum.xda-developers.com/honor-5x/how-to/guide-force-installing-stock-ota-t3502874
What are the bug fixes???
Are there any new features???
I am currently on custom ROM and would like to know the answers to these questions to see if it's worth it to go back to stock rom
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
m0ndul said:
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
Click to expand...
Click to collapse
So much miss information .. no one bothers to find the truth
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
animeme said:
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
Click to expand...
Click to collapse
Link below or install the Huawei Firmware Finder form the Google Play Store and set it up to get OTA files in settings.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=kiw-l24
deleted
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
What he said.
I'm hoping it's nothing more than a VoLTE update that LOS maintainers warn against anyway, if there's actually no one to further explain what it is
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
my kiwi-L24 got re-flashed today, it is weird that this B351 update is no longer available from B331's update check
searched on internet, there is news about "honor 5c" getting a B351 nougat update
This came up on one of the 5X's that I have. Updated and forgot to put back stock recovery. Don't be like me and forget to do that. Now it won't work properly and I can't get to start any apps to try and fix it. I can put back TWRP and wipe it, but I don't want to lose my data. I also have that problem now where it keeps telling that the SD card is corrupted. I backed up the data and scrubbed the card in the phone but it keeps coming back with the same thing.
If someone did an actual successful update properly (with stock recovery) then please update and say if everything is working. If not, I'm going to have to find some way to backup the data and then scrub it.
*EDIT*
I believe something like this happened to me before. I was on B151 and went to B331 with TWRP installed by accident. What happened was that the OS was still running EMUI 3.1 but the build was saying B331. After fighting with it (and community support) I managed to get it to B331 fully and EMUI 4.0 - since then and a few custom ROMs I'm back on B151 EMUI 3.1 due to stability. Games and some apps just didn't work on the new one. The second phone was on B331 fully though - then I made the same mistake and it went to B351. This time though, the phone seems screwed. No apps will load. I can get into settings and the file manager, but no Titanium Backup and no Flashify. Going to put back TWRP and try to flash GAPPS and see if it will help me get into Play Store. From there I'll try to reinstall Flashify and flash the ZIP of the update. Will post back once done.
*EDIT*
Well that didn't work. Even after going back and trying to root the device again - then checking the option for it to not detect the dirty flash - still didn't work. Kept complaining that stock apps are already present.
I'm going to try and get some files off the device, but keep having issues. Not sure why. May just have to scrub. Will update again.
*EDIT*
With TWRP on I used "ADB PULL" to get certain files from the root system which I couldn't access otherwise for some reason. Then copied the other things (photos and such) and will now be using the UPDATE.APP to get it working. For this I formatted the SD from within TWRP and created the DLOAD folder (with no caps - so that's dload - but I'm not sure if it matters) and will be copying the UPDATE.APP. Not sure which version yet, because there was some problem with one I had downloaded before. So I need to double-check and re-download.
*EDIT*
So I've successfully flashed the UPDATE.APP from the SD card (same one the phone was claiming is corrupted). Just for reference, here is the file information and hashes.
File Name: Honor 5X_Firmware_KIW-L24_Android 6.0.1_EMUI 4.0_C567D003_United States.zip
Size: 1762266487 bytes
ADLER32: 27cb0c31
CRC32: 1d9379b9
MD2: 6517c34dc9bac0cd8680e3c4fd09d8d9
MD4: 4a803765c0ed54cb5d6853a9f365cd3b
MD5: 04f60b067d546ad71f556e44a7934dc7
SHA1: 8d2718568ac6509a40c95e42857d400395eb88d2
SHA256: 82975923172b3800d3f09f76691f2a694ab98110e3f909084a02bd566448386f
SHA384: da53b58b8e20395595590fd0cec30e56fa6a62e638ec53e46a74ebf58d051fdd7576602019bd3130ca5c00cc432715a0
SHA512: 806e0e8969c293ca8b497a786699ee306352ad6ef434552f2d23decff8a5279c7fd605e046c13f11c2f87947f5a2bdf23d78fdec6263661e68f023fd72bf4381
RIPEMD128: 9d963e5d51c9df9554fa3422da84dd27
RIPEMD160: a1e5b8f08b65dd2bb08e04d62db270ad8f4cf51a
TIGER128: 66fb4e4e4ce11cb30626aea807355f83
TIGER160: 66fb4e4e4ce11cb30626aea807355f8345f1dd79
TIGER192: 66fb4e4e4ce11cb30626aea807355f8345f1dd79dbb39488
GOST: 93774537f6ca49d4406f9d3a0316d014e1e099b34fc1cd9b968dacc870700827
The file name may be different, but as long as you got the right one you should be OK. If you have issues when copied to an SD card - verify that the file on the SD card has the correct hashes. To make it faster use CRC32. For more surety, use MD5. You can get a tool like WinMD5 to check. It's free.
So now that it's done, I'm going to set it up as a new phone and wait to see if the update comes back on. If it does, I'll get it down and upload the B351 recovery. After that I'll need to remember that I have to put back the stock recovery before running any updates. Flashify FTW.
BTW - during the initial setup after connecting to wireless it came back with the update. Pics to follow.
Files will be uploaded here: https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
*EDIT*
So the files are uploading to the folder. The screenshot is attached. Had one issue where after the update I couldn't get back into the phone. Had to wipe/factory reset. I've used FASTBOOT BOOT TWRP.IMG to take the backups of the BOOT and RECOVERY. Hopefully one of the gurus can use that and give the IMG files. I'm going to try root and get FLASHIFY to backup the stock recovery and add to the folder.
khat17 said:
This came up on one of the 5X's that I have...............
Click to expand...
Click to collapse
I don't really like to do double replies, but I guess for ease of finding the info it's better this way. Unless a mod thinks differently and wants to merge all the info.
Google Drive Link With Files
https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
This contains TWRP backups of the recovery and boot images. There's also a file called KIW-L24-B351 which was created with Flashify. I assume you can add the IMG extension to it and flash as needed.
Basically I had this update run on another phone (my wife's) and it messed with the phone due to the recovery being TWRP and not stock. My fault - forgot to do that before handing the phone back to her. I believe it happened to me before but it never messed up the phone this way. Nothing would work except core apps like settings and the stock file manager. The Play Store wouldn't even open.
Anyways - back to factory with UPDATE.APP then run the automatic update from an OTA update on wireless, then FASTBOOT BOOT TWRP.IMG and capture the backups. Then flash SuperSU to get root. Then Flashify. Files are uploaded for your convenience.
Warning that during the initial OTA it took a while. And after it was done I couldn't get into the phone with the password. Had to factory wipe/reset again and setup again. Disable passwords just in case I guess. Hope this helps others - have fun.
No major differences. I haven't really used the stock OS6 but some things look a little different. Nothing major. Will see when she's using it if it lags or has improved memory and such. Not sure if I'll be able to test with apps that wouldn't run previously for me, but will see. Tested with TransDrone and it failed. Once SeedBox information is loaded it still crashes. Only happens on OS6 so I'm sticking with OS5 on mine. Does not happen with custom roms however (from what I recall - would have to check back).
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
raulpcamara said:
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
Click to expand...
Click to collapse
Follow this video if don't know how to flash back stock recovery through adb. Then take a look at those threads how to downgrade, here, here, here. Hope it helps.
bluesky299 said:
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
Click to expand...
Click to collapse
Same here.
It had been too many months of the Honor 5X in the closet so i almost lost track what to do but what i did was revert all the way back to Stock ROM (had to flash an extracted/saved Recovery.IMG) and then do the UPDATE.APP from Dload complete and repeat on up to the current B351.
Of course lost Root but when ready can add that back too.
Yes the Honor 5X runs much smoother now than before plus that Battery Drain issue (Remember That?) where we had to dig deep to change 4 to 0 i think, well Battery Life is also greatly improved on mine.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
I tried to update as the previous user did using TWRP and got the corrupted SD card message. I then tried to go back to stock ROM. Went into bootloop.
Been having a hell of a time getting anything to work properly since.
Software Update: Axon 7 (A2017U) owners... Within the next 48 hours, an update will bring a security patch to your device. Bluebourne and KRACK vulnerabilities will be remedied with this patch.
https://community.zteusa.com/discussion/52369/software-update-axon-7-a2017u-now-on-b35
DrakenFX said:
Software Update: Axon 7 (A2017U) owners... Within the next 48 hours, an update will bring a security patch to your device. Bluebourne and KRACK vulnerabilities will be remedied with this patch.
https://community.zteusa.com/discussion/52369/software-update-axon-7-a2017u-now-on-b35
Click to expand...
Click to collapse
Which is the patch date? G B09 has the December 1 patch, just wanted to know which one fixes this stuff
Can someone provide a B35 update zip? It's no issue for me to connect to Wi-Fi to install it, but I like to keep offline cached copies of files for recovery purposes, so that I can update even without Internet.
Thanks!
Edit: I have A2017U.
When will the B35 firmware will be available as flashable TWRP zip across a2017 devices?Does it have a improved battery life?
Predatorhaze said:
When will the B35 firmware will be available as flashable TWRP zip across a2017 devices?Does it have a improved battery life?
Click to expand...
Click to collapse
As soon as you make one?
Pretty sure it's available now. Let us know how the battery life is.
I know I asked before, but if someone can post a direct URL link to the B35 update file (whether it be a zip or something else) then it would be much appreciated. I know @DrakenFX released a system and bootstack zip, but I would rather use official files. I can't save an offline copy of the file since I'm not currently rooted, I suspect it is stored in the /cache partition. The file size is close to 700MB. I just want a copy for offline use. Maybe someone with root can capture a copy of the file after it has downloaded, but before the phone reboots to apply it. Or maybe the URL can be sniffed with WireShark or whatever. A B35 full OTA zip is better, but ZTE hasn't posted an SD card update download on the zteusa.com website yet.
Thanks!
I was able to grab the B35 update zip without rooting. I let the updater download the file, then quickly powered off the phone before it had a chance to reboot and install. Then I booted into EDL mode, and used @tennear's Axon7Tool to write TWRP. From TWRP I went to /data/data/com.zte.zdm/files, and grabbed a file called fota_update.zip. Then I reflashed the stock recovery with Axon7Tool, and installed the zip. All went fine. I suspect you can grab any OTA zip this way. Maybe I'll upload a copy of the file later.
If there's any interest in a B35 SL!M➀ aroma-version let me know
raystef66 said:
If there's any interest in a B35 SL!M➀ aroma-version let me know
Click to expand...
Click to collapse
Yes, sir! Very interested in flashing the update through TWRP while maintaining the advantages of stock for the hardware on board.
raystef66 said:
If there's any interest in a B35 SL!M➀ aroma-version let me know
Click to expand...
Click to collapse
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
amphi66 said:
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
Click to expand...
Click to collapse
I think you're referring to this one ?
In general, did you see quite some difference before and after ?
You can PM for the tons of frozen stuff you like to get rid off. Think i might work on it these days to have some fun :cyclops:
raystef66 said:
I think you're referring to this one ?
In general, did you see quite some difference before and after ?
You can PM for the tons of frozen stuff you like to get rid off. Think i might work on it these days to have some fun :cyclops:
Click to expand...
Click to collapse
Yes. I downloaded those 'init' files way back last Spring & found them more effective (at least impression-wise) than the AKT stuff. His "Conservative" mod helps w/ battery w/o a noticeable performance hit.
Early on I found the A7 was not happy when some apps were removed & replaced, but functioned OK if they were kept frozen & then replaced. Fortunately there is enough storage & memory that inefficiency does not (so far) cause issues. Sort of like the legacy SubStratum which could (sort of) work as long as system apps were excluded.
I look forward to your "hobby". Thanks
hi.
if i upgarde my A2017u directly from setting>update on my phone, i loose root and twrp or not?
redhou said:
hi.
if i upgarde my A2017u directly from setting>update on my phone, i loose root and twrp or not?
Click to expand...
Click to collapse
If you are using TWRP and/or are rooted, that setting>update will fail due to modified system files. READ & follow directions in post #2 HERE. Data will be saved & TWRP will be upgraded (if req'd).
davisml said:
Yes, sir! Very interested in flashing the update through TWRP while maintaining the advantages of stock for the hardware on board.
Click to expand...
Click to collapse
amphi66 said:
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
Click to expand...
Click to collapse
Working on it Was harder then our G version stocksystem to make it boot with aroma. Really weird stocksystem...
But i succeeded. Having bootloader changed, twrp build-in and seperate modems, bootanimation changed, build-in battery tweaks, magisk, supersu, fasterUI....all ok now. Just adding some other stuff in next days. Hope to release it in the weekend :cyclops:
amphi66 said:
If you are using TWRP and/or are rooted, that setting>update will fail due to modified system files. READ & follow directions in post #2 HERE. Data will be saved & TWRP will be upgraded (if req'd).
Click to expand...
Click to collapse
the download file start with no probleme using setting>update. i had stoped it.
can i continu ? i had a lot of difficult before root my phone in past and i don't like to loose it
redhou said:
the download file start with no probleme using setting>update. i had stoped it.
can i continu ? i had a lot of difficult before root my phone in past and i don't like to loose it
Click to expand...
Click to collapse
It will download, but the install will simply fail as it checks the system files, but certainly you are free to do as you wish. Good Luck!
raystef66 said:
Working on it Was harder then our G version stocksystem to make it boot with aroma. Really weird stocksystem...
But i succeeded. Having bootloader changed, twrp build-in and seperate modems, bootanimation changed, build-in battery tweaks, magisk, supersu, fasterUI....all ok now. Just adding some other stuff in next days. Hope to release it in the weekend :cyclops:
Click to expand...
Click to collapse
Uploading A2017(U)(N-B35)_AROMA_SL!M¹_DF!NR now Preparing a seperate thread on ROM section. Keeping you updated when ready :good:
EDIT : DONE ! LINK
hi, i am installing the new OTA update but it when my restarts TWRP asks for password to mount and doesn't allow me to install this new OTA update. I entered my phone password which said it decrypted the pkg but then it only opens the TWRP GUI. I tried to install the zip manually but it said it failed.
How can I let the phone install it without TWRP interfering?
Thanks a lot.
lachdanan said:
How can I let the phone install it without TWRP interfering?
Click to expand...
Click to collapse
You can't. Use stock recovery if you insist on OTA, or use DrakenFx's zips to flash from TWRP. The latter is much more convenient.
Ok my friends, it's true that family moto g6 (specifically g6 play) will receive android 10? if it's possitive... When will we have news about this?
Also ... does anyone know if there is any rom in development with android 10 for this model (lineage, RR, etc.)?
If anyone knows about this, I think several would appreciate this valuable information.
Answer 1, just wait for Moto to announce it, usually they announce when there gonna do a soak test of a new Android version so whenever Moto does that will be some sort of answer however soak test usually go on for a few months basically it's prolly gonna be almost another year before we hear anything I mean we just got official pie about 2 months ago now after they did soak test for months.
Answer 2, there is not even a custom rom like rr or anything for this device for Oreo or pie so doubtable. Best you can do is try out gsi A only builds, custom rom means it's made specifically for this device where as gsi is compatible with any phone that shipped with Android 8. There is a gsi thread you can out
Answer 3: Motorola has already confirmed that the Moto G6 Play will only get one major OS upgrade, and being that we got Pie now that's all it will get unless a DEV figures out how to make a custom rom for Android 10.
PimpMy5Ton said:
Answer 3: Motorola has already confirmed that the Moto G6 Play will only get one major OS upgrade, and being that we got Pie now that's all it will get unless a DEV figures out how to make a custom rom for Android 10.
Click to expand...
Click to collapse
I have no WiFi right now or I'd already be trying to build for us. They finally fixed the sources for our phone. Phh has Android 10 GSIs out. They'll boot if you flash the Oreo vendor, oem, and boot images first but it's very alpha at the moment. You also need to flash phh's modified magisk from his first Android 10 release. LTE is broken (3G works), and it has some graphics glitches. Most everything else is working fine though. It's not a daily driver yet but it's getting there fast. It will break LTE on stock. To fix that just flash your firmware and let it setup until it reactivates, then you can restore a backup like normal.
Spaceminer said:
I have no WiFi right now or I'd already be trying to build for us. They finally fixed the sources for our phone. Phh has Android 10 GSIs out. They'll boot if you flash the Oreo vendor, oem, and boot images first but it's very alpha at the moment. You also need to flash phh's modified magisk from his first Android 10 release. LTE is broken (3G works), and it has some graphics glitches. Most everything else is working fine though. It's not a daily driver yet but it's getting there fast. It will break LTE on stock. To fix that just flash your firmware and let it setup until it reactivates, then you can restore a backup like normal.
Click to expand...
Click to collapse
That's cool, I was just adding to the answer as to the number of os upgrades that Moto phones get, as far as Phh's android 10 you should be fine as long as you include vendor partition with your stock backup.
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
@Spaceminer Could you link to the sources for the Moto G6 Play?? I have the XT1922-7 Boost Mobile variant.
PimpMy5Ton said:
That's cool, I was just adding to the answer as to the number of os upgrades that Moto phones get, as far as Phh's android 10 you should be fine as long as you include vendor partition with your stock backup.
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
@Spaceminer Could you link to the sources for the Moto G6 Play?? I have the XT1922-7 Boost Mobile variant.
Click to expand...
Click to collapse
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PCP29.118-41
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
ry755 said:
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
Click to expand...
Click to collapse
Glad to have it running with Pie and more stable, those are great news
ry755 said:
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
Click to expand...
Click to collapse
Can you guide us? I install the test img but cant boot on pie vendor
Grom9A said:
Can you guide us? I install the test img but cant boot on pie vendor
Click to expand...
Click to collapse
First flash the latest stock boot.img to remove any leftover traces of Magisk, which is now incompatible with phh's AOSP 10 builds.
After that you'll need to disable encryption and dm-verity, if you haven't already done that:
- Download the dm-verity + forced encryption disabler zip here
- Boot into TWRP, go to Wipe, and press Format Data. This will wipe everything from the internal storage! Make sure you have backups stored somewhere else.
- Reboot > Reboot Recovery
- Copy the disabler zip to your phone and flash it
Now the test image should be able to boot on Pie vendor.
(There might be other/better ways of doing this, but those are the steps that worked for me)
ry755 said:
First flash the latest stock boot.img to remove any leftover traces of Magisk, which is now incompatible with phh's AOSP 10 builds.
After that you'll need to disable encryption and dm-verity, if you haven't already done that:
- Download the dm-verity + forced encryption disabler zip here
- Boot into TWRP, go to Wipe, and press Format Data. This will wipe everything from the internal storage! Make sure you have backups stored somewhere else.
- Reboot > Reboot Recovery
- Copy the disabler zip to your phone and flash it
Now the test image should be able to boot on Pie vendor.
(There might be other/better ways of doing this, but those are the steps that worked for me)
Click to expand...
Click to collapse
Thanks, it works. We need to find a way to restore the sound. I try a few zips they send on the telegram group but nothing.
Grom9A said:
Thanks, it works. We need to find a way to restore the sound. I try a few zips they send on the telegram group but nothing.
Click to expand...
Click to collapse
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Spaceminer said:
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Click to expand...
Click to collapse
Did you flash the stock boot.img? That's all I had to do to make it work, I didn't have to format data since I already have it decrypted.
Spaceminer said:
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Click to expand...
Click to collapse
I want to try but can't root this rom
Grom9A said:
I want to try but can't root this rom
Click to expand...
Click to collapse
Under phh's v200 build there's a special magisk he made for his Android 10 GSI.
---------- Post added at 08:11 PM ---------- Previous post was at 08:07 PM ----------
ry755 said:
Did you flash the stock boot.img? That's all I had to do to make it work, I didn't have to format data since I already have it decrypted.
Click to expand...
Click to collapse
Maybe I flashed the wrong boot.img... I might've mixed up Oreo and Pie boot images. I have both firmwares sitting right next to each other.
Spaceminer said:
Under phh's v200 build there's a special magisk he made for his Android 10 GSI.
Click to expand...
Click to collapse
I've tried that along with a few other people in the Moto G6 Telegram group, flashing it just causes bootloops.
ry755 said:
I've tried that along with a few other people in the Moto G6 Telegram group, flashing it just causes bootloops.
Click to expand...
Click to collapse
That explains my problem. I definitely flashed his magisk. Have you guys tried magisk v20 yet?
Spaceminer said:
That explains my problem. I definitely flashed his magisk. Have you guys tried magisk v20 yet?
Click to expand...
Click to collapse
Yep, any kind of Magisk makes it bootloop. Someone reported it to phh and his response was "well don't use magisk then" lol
ry755 said:
Yep, any kind of Magisk makes it bootloop. Someone reported it to phh and his response was "well don't use magisk then" lol
Click to expand...
Click to collapse
I'll check it out and see what I can do. That's not surprising though. It's extremely alpha, so he's probably just prioritizing stock functionality over everything else right now.
I can't get it rooted, but v202 just went up, so I'm going to try my luck with it.
I have tried twice on my OnePlus 6T T-Mobile variant to upgrade to the newest Open Beta. It runs the current open beta released in September just fine. But then when I do a local upgrade to the Android 10 open beta, right after it finishes installing and I press reboot, I get a message that says Build Version and HW version do not match and it ets stuck in a bootloop. To fix it, I have to use MSMDownloadTool to fix it. I have tried doing a local upgrade using a locked and unlocked bootloader and both lead to the same problem. Has anyone succesfully updated their TMo variant because i hate having to keep restoring my device?
I usually wait for a while until official Android 10 ROM for international OnePlus 6T version (and flash it via TWRP both times so I don't get any conflicts, with same copies of the OS across both slots), then I do whatever I want (I usually upgrade the bootloader and vendor this way so newer flavor of LineageOS 16 or later ROMs work best). I didn't run into hardware mismatch warning, yet I managed to successfully flash the successive OxygenOS updates meant for the international OnePlus 6T on my T-Mobile OnePlus 6T so far without seeing any UEFI bootloader warning at all. I had to be careful, I partly bricked my Google Pixel phone the last time (rendered Slot A completely unbootable by accident, so I had to figure out how to restore it the hard way, without the computer).
Sent from my OnePlus 6T using Tapatalk
bigmikey307 said:
I have tried twice on my OnePlus 6T T-Mobile variant to upgrade to the newest Open Beta. It runs the current open beta released in September just fine. But then when I do a local upgrade to the Android 10 open beta, right after it finishes installing and I press reboot, I get a message that says Build Version and HW version do not match and it ets stuck in a bootloop. To fix it, I have to use MSMDownloadTool to fix it. I have tried doing a local upgrade using a locked and unlocked bootloader and both lead to the same problem. Has anyone succesfully updated their TMo variant because i hate having to keep restoring my device?
Click to expand...
Click to collapse
Here is the solution for the moment.
I already installed it and everything works fine.
https://forum.xda-developers.com/showpost.php?p=80600661&postcount=52
ajnexus5 said:
Here is the solution for the moment.
I already installed it and everything works fine.
https://forum.xda-developers.com/showpost.php?p=80600661&postcount=52
Click to expand...
Click to collapse
I'm not interested in rooting my phone :silly: so is there any work around for unrooted users at the moment? Ty
Not yet. The fastboot ROM is pre-rooted, so there's no additional tinkering needed. Just flash the fastboot ROM and upon reboot, it's rooted. You can always jump back to the stable build when it's released next month if you'd like.
That file was deleted. Is there any other way to flash it?
jaceypoo said:
That file was deleted. Is there any other way to flash it?
Click to expand...
Click to collapse
Yes. Payload.bin decrypt and manual fastboot flash.
1-click T-mobile Android 10 for 6T:
https://drive.google.com/open?id=1jhGVmfC42UyVGDYUQhBFInjYUmZf4lxa
bradhoschar said:
Not yet. The fastboot ROM is pre-rooted, so there's no additional tinkering needed. Just flash the fastboot ROM and upon reboot, it's rooted. You can always jump back to the stable build when it's released next month if you'd like.
Click to expand...
Click to collapse
How is the Zip? I am new to the OnePlus forums do not see the least of two of 0 years ago I do so much trust that this would not happen as with P there were never problems with the V T which Vojo is some without root version?
Installed just fine, I love the new interface. BT isn't working for my Garmin watch. I guess I will have to wait for a full release for this to be fixed up.
Just a heads up to those who haven't made an actual phone call yet, Everyone I've spoken to has told me they can't hear me at all and that the quality comes out pretty garbled. Just something to look out for! If anyone has a fix for it please let us know!
chillaxnphilx said:
Just a heads up to those who haven't made an actual phone call yet, Everyone I've spoken to has told me they can't hear me at all and that the quality comes out pretty garbled. Just something to look out for! If anyone has a fix for it please let us know!
Click to expand...
Click to collapse
No issues on the T-mo fastboot ROM
Well, actually right now I cannot get into recovery. Says Qualcomm Dump. Questions? Should I try flashing TWRP?
---------- Post added at 01:06 PM ---------- Previous post was at 01:05 PM ----------
EspElement said:
Well, actually right now I cannot get into recovery. Says Qualcomm Dump. Questions? Should I try flashing TWRP?
Click to expand...
Click to collapse
I even tried to fastboot boot recovery.img
It didn't work, just sits at fastboot screen.
bradhoschar said:
No issues on the T-mo fastboot ROM
Click to expand...
Click to collapse
You haven't used the gyro, proximity sensor, specialized fonts, or emojis yet.
The OB1 creates a new partition called "reserve". This partition is not present on the Tmobile variants and its not created during install. There are issues with the Tmobile build, and its going to stay that way until an updated MSMtool comes out, Tmobile updates to A10, or some maniac actually goes through and fixes every single symlink that's broken.
OP ran out of space on system partition, so they're solution was to create a new partition and symlink everything from there to system.
hartleyshc said:
You haven't used the gyro, proximity sensor, specialized fonts, or emojis yet.
The OB1 creates a new partition called "reserve". This partition is not present on the Tmobile variants and its not created during install. There are issues with the Tmobile build, and its going to stay that way until an updated MSMtool comes out, Tmobile updates to A10, or some maniac actually goes through and fixes every single symlink that's broken.
OP ran out of space on system partition, so they're solution was to create a new partition and symlink everything from there to system.
Click to expand...
Click to collapse
Gyro and prox works for me.
Emojis work after magisk module flash.
chillaxnphilx said:
Just a heads up to those who haven't made an actual phone call yet, Everyone I've spoken to has told me they can't hear me at all and that the quality comes out pretty garbled. Just something to look out for! If anyone has a fix for it please let us know!
Click to expand...
Click to collapse
I have heard of this from multiuple people in the forums and it is also occuring with the Hydrogen Beta for Android 10. Thats where I first saw it. I dont know if my phone is affected.
hartleyshc said:
You haven't used the gyro, proximity sensor, specialized fonts, or emojis yet.
The OB1 creates a new partition called "reserve". This partition is not present on the Tmobile variants and its not created during install. There are issues with the Tmobile build, and its going to stay that way until an updated MSMtool comes out, Tmobile updates to A10, or some maniac actually goes through and fixes every single symlink that's broken.
OP ran out of space on system partition, so they're solution was to create a new partition and symlink everything from there to system.
Click to expand...
Click to collapse
Gyro and Prox are working fine for me. Dont know about fonts and emoji's as I dont use them. Everything "else" seems fine at this point.
Scott said:
I have heard of this from multiuple people in the forums and it is also occuring with the Hydrogen Beta for Android 10. Thats where I first saw it. I dont know if my phone is affected.
Patching the boot.img with magisk canary is somehow breaking the symlinks to reserve.img (possibly others). reserve.img is where the extra fonts, oneplus specific apks (like weather, launcher icons, etc) are stored. If you wanna check, flip your font to oneplus slate, if its in italics, its hosed. If your font is looking at special characters and your getting boxes with X's in them, your hosed.
only way to fix is a clean flash, and use magisk stable manager to patch your boot.img if your rooting.
Click to expand...
Click to collapse
aer0zer0 said:
Patching the boot.img with magisk canary is somehow breaking the symlinks to reserve.img (possibly others). reserve.img is where the extra fonts, oneplus specific apks (like weather, launcher icons, etc) are stored. If you wanna check, flip your font to oneplus slate, if its in italics, its hosed. If your font is looking at special characters and your getting boxes with X's in them, your hosed.
only way to fix is a clean flash, and use magisk stable manager to patch your boot.img if your rooting.
Click to expand...
Click to collapse
Ok, yeah, I do have the italic font. I thought that was just "new".
So basically, dont root it and it will be fine?
Scott said:
Ok, yeah, I do have the italic font. I thought that was just "new".
So basically, dont root it and it will be fine?
Click to expand...
Click to collapse
root your boot.img using magisk 20.0 stable.
but your going to need to reflash? are you tmob or stable?
bradhoschar said:
1-click T-mobile Android 10 for 6T:
https://drive.google.com/open?id=1jhGVmfC42UyVGDYUQhBFInjYUmZf4lxa
Click to expand...
Click to collapse
is this the pre rooted version
Sent from my ONEPLUS A6013 using Tapatalk