AOSP 13
This is a moto-common project release under the codename amogus. This build supports the following devices: rav, rav_t, sofia, sofiap, sofiap_ao, sofiap_sprout, sofiar.
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's AOSP?
AOSP is Android as Google publish without any modifications.
Whats not working?
Speakerphone on sofia variants
Instructions to install the ROM:
Reboot to bootloader:
Code:
adb reboot bootloader
The following will wipe your internal data:
Code:
fastboot -w
Code:
fastboot update package.zip
It will reboot your device to fastbootd, you might get the following warning:
Code:
FAILED (remote: 'Old partitions are not compatible with the new super layout; wipe needed')
, but you can continue with the following commands
Fastbootd:
Code:
fastboot flash product product.img
Code:
fastboot flash system system.img
Code:
fastboot flash vendor vendor.img
Code:
fastboot reboot
Downloads: Here
Source Code: Here
Sept 2: Fixed USB Mode Switching, Switched to new rebased kernel, Switched to EROFS
Sept 12: EGIS Fingerprint gestures fixed, Switch BtAudio to AIDL and September Patch level
Sept 28:
System Responsiveness has been tuned and improved
Introduce Multigenerational LRU Framework
Tune Dalvik Heap Sizes
Switched to QTI Thermal HAL
DT2W has been fixed for RAV (HIMAX) variants of amogus
Signature Spoofing support has been added to the ROM
Jan 26:
January Security Patch
Feb 27:
Feb security patch
Nice finally something other than Android 11
Good work, it works for now.
Is there any Gapps available for this Android version ?
I look forward to giving this a try when Gapps is available.
I decided to give it a try and it's working well with the exception of what has already been declared to not be working:
USB Mode Switching
Speakerphone on sofia variants
I can confirm that these are broken on Sophia, and I can also confirm that the Speakerphone also doesn't work in video calls made using Signal.
I know it's ASOP but including a browser that can download would help greatly with getting F-DROID (especially with USB Mode Switching being broken). The Webview browser can't seem to download anything. You can browse with it but not download.
Thank you very much for the hard work.
Matthew
matthewadie said:
I decided to give it a try and it's working well with the exception of what has already been declared to not be working:
USB Mode Switching
Speakerphone on sofia variants
I can confirm that these are broken on Sophia, and I can also confirm that the Speakerphone also doesn't work in video calls made using Signal.
I know it's ASOP but including a browser that can download would help greatly with getting F-DROID (especially with USB Mode Switching being broken). The Webview browser can't seem to download anything. You can browse with it but not download.
Thank you very much for the hard work.
Matthew
Click to expand...
Click to collapse
USB Mode switching does not impact the function of ADB, you can use that to install any third party apps. Thank you for the review
GApps would be nice. Also, would flashing this and later trying to flash an Android 11 ROM trigger anti-rollback protection?
kotchama said:
GApps would be nice. Also, would flashing this and later trying to flash an Android 11 ROM trigger anti-rollback protection?
Click to expand...
Click to collapse
No it will not trigger anti rollback protection, I'll consider adding gapps but eh
Going to check it out and see if I can acquire root access to check what is messing with the speakerphone and USB. Nice to see something new to test on these phones!
Tried this on my SofiaR and I guess the radio files just didnt flash or it didnt keep the original ones but yea I have no cell service, is this normal? Tired installing it again and had the same issue.
killahrey said:
Tried this on my SofiaR and I guess the radio files just didnt flash or it didnt keep the original ones but yea I have no cell service, is this normal? Tired installing it again and had the same issue.
Click to expand...
Click to collapse
I suggest you flash stock and verify that cell service works there and then reflash this rom on top. It is verified that cell service works on this build
Electimon said:
I suggest you flash stock and verify that cell service works there and then reflash this rom on top. It is verified that cell service works on this build
Click to expand...
Click to collapse
I flashed a stock rom and the phone rebooted, everything seemed fine. I turned off the phone to reflash this rom but before I had the chance to the phone would not boot to anymore. Seems completely bricked, but its probably my own doing.
killahrey said:
I flashed a stock rom and the phone rebooted, everything seemed fine. I turned off the phone to reflash this rom but before I had the chance to the phone would not boot to anymore. Seems completely bricked, but its probably my own doing.
Click to expand...
Click to collapse
Ok since it bricked before you had a chance to flash the rom, the issue is most likely with how you flashed stock. Can you show me the process you took todo that? Also if you plug in the device to a Windows machine, in device manager does it show QUSB_BULK?
The only thing different from stock was the twrp recovery img. I'm guessing I may have accidentally flashed the wrong boot.img some how, honestly I'm not sure. There is no response from the device on windows or Kali. Does not indicate it's charging in anyway and all restart processes do nothing. Wanted to use this as a backup before I got my new phone in a few days but it is what it is. I highly doubt it was any of your img's.
killahrey said:
The only thing different from stock was the twrp recovery img. I'm guessing I may have accidentally flashed the wrong boot.img some how, honestly I'm not sure. There is no response from the device on windows or Kali. Does not indicate it's charging in anyway and all restart processes do nothing. Wanted to use this as a backup before I got my new phone in a few days but it is what it is. I highly doubt it was any of your img's.
Click to expand...
Click to collapse
There is one way to revive it but it involves disassembly, would you like me to tell you about it? I know not much have the tools for it.
Electimon said:
There is one way to revive it but it involves disassembly, would you like me to tell you about it? I know not much have the tools for it.
Click to expand...
Click to collapse
I was considering disassembly to see if a battery unplug would help but if there is something else you think I should do I'm all ears.
killahrey said:
I was considering disassembly to see if a battery unplug would help but if there is something else you think I should do I'm all ears.
Click to expand...
Click to collapse
Yes the device has testpoints on the motherboard, if you bridge them it will enter EDL mode. From there you can use a blankflash to restore the bootloader and hopefully unbrick. Unplug the battery and bridge those pads, while bridged plug in the USB cable and with any luck you will be in EDL. From there you can plug the battery back in so it can flash successfully. You can find the blankflash on https://mirrors.lolinet.com/
{
"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"
}
Electimon said:
Yes the device has testpoints on the motherboard, if you bridge them it will enter EDL mode. From there you can use a blankflash to restore the bootloader and hopefully unbrick. Unplug the battery and bridge those pads, while bridged plug in the USB cable and with any luck you will be in EDL. From there you can plug the battery back in so it can flash successfully. You can find the blankflash on https://mirrors.lolinet.com/
View attachment 5699785
Click to expand...
Click to collapse
Awesome, thanks for this info. I'll mess with this tonight and see if I can bring it back to life.
Sept 2: Fixed USB Mode Switching, Switched to new rebased kernel, Switched to EROFS
Question why is it that the built in file manager is unable to install apps? I understand we can use ADB to install apps, still this seems like abnormal behavior .
As always, thanks for the ROM.
Related
{
"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"
}
NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
/*
* [B]Your warranty is now void.[/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Sources: https://github.com/TeamWin
Device tree: https://github.com/TeamWin/android_device_huawei_charlotte
Download
Flashing:
Code:
fastboot flash recovery_ramdisk twrp-3.2.1-0-charlotte.img
Special thanks to @Dees_Troy for the Huawei Blanc device tree, which this is based on.
Thank you so much Is there any chance of you uploading a twrp flashable image of the newest p20 pro update?
Will try this when I get home. It doesn't replace eRecovery, right? So I can still recover if anything goes wrong? Also, best way to boot into TWRP once flashed?
danifilth4king said:
Will try this when I get home. It doesn't replace eRecovery, right? So I can still recover if anything goes wrong? Also, best way to boot into TWRP once flashed?
Click to expand...
Click to collapse
As long as you flash the image to recovery_ramdisk it does not replace eRecovery, no. I actually used eRecovery to restore while testing my build.
Once flashed you can boot into TWRP via "adb reboot recovery" out of a running system with enabled ADB or via pressing VolUp+Power on a powered off device.
Many thanks a1Pha, just installed on a CLT-L29 8.1.0.106(C432), works flawless. Great job !
Once flashed you can boot into TWRP via "adb reboot recovery" out of a running system with enabled ADB or via pressing VolUp+Power on a powered off device.[/QUOTE]
You can also reboot to recovery if your phone is up and running opening Magisk Manager -> Modules, three points on the upper right corner will give you the choice recovery, bootloader or download...
Cheers.
buenso80 said:
Thank you so much Is there any chance of you uploading a twrp flashable image of the newest p20 pro update?
Click to expand...
Click to collapse
To be honest: This is my first Huawei and I am still figuring out how they manage their region-specific customization. Also it seems not so easy to get the UPDATE.APP for current builds. So no promises here - but I'll try to figure out and create a new thread if I'm able to build something.
Thanks given! I'll try this when I get a chance! This is a good start for this new device
a1Pha said:
To be honest: This is my first Huawei and I am still figuring out how they manage their region-specific customization. Also it seems not so easy to get the UPDATE.APP for current builds. So no promises here - but I'll try to figure out and create a new thread if I'm able to build something.
Click to expand...
Click to collapse
Maybe this could be usefull?
https://forum.xda-developers.com/hu...rmware-release-clt-l29-8-1-0-107c432-t3779167
buenso80 said:
Maybe this could be usefull?
https://forum.xda-developers.com/hu...rmware-release-clt-l29-8-1-0-107c432-t3779167
Click to expand...
Click to collapse
Thanks. As soon as I've got a fully working system.img which doesn't break different country models you'll hear from me.
Does it work for the CLT-L09 as well?
llvllorpheus said:
Does it work for the CLT-L09 as well?
Click to expand...
Click to collapse
Yes, I'm actually on CLT-L09!
llvllorpheus said:
Does it work for the CLT-L09 as well?
Click to expand...
Click to collapse
Works perfect
a1Pha said:
As long as you flash the image to recovery_ramdisk it does not replace eRecovery, no. I actually used eRecovery to restore while testing my build.
Once flashed you can boot into TWRP via "adb reboot recovery" out of a running system with enabled ADB or via pressing VolUp+Power on a powered off device.
Click to expand...
Click to collapse
How do you get back into eRecovery once you have flashed twrp?
Volume up gets you to twrp - is there a special key combo/sequence to get to eRecovery? I as as I have access to funkyhuawei. Also - how would one go back to stock with this installed? Sorry first time doing this for years
Cheers
Andy
---------- Post added at 06:52 PM ---------- Previous post was at 06:30 PM ----------
Ok so I managed to get into eRecovery by powering off and holding vol up and pwr until the phone vibrated, then release power and continued holding vol up until eRecovery appeared. If I wanted to completely remove TWRP and root etc once in eRecovery would it simply be a case of clicking download latest version and recovery? Then once recovered I could relock the bootloader? Or are there some other steps to do?
If anyone could help so I know for future reference that would be amazing. Thank you in advance
andrewglass3 said:
How do you get back into eRecovery once you have flashed twrp?
Another way to enter eRecovery: Shut down phone, press VOL+ and connect to USB... and wait
Click to expand...
Click to collapse
andrewglass3 said:
If I wanted to completely remove TWRP and root etc once in eRecovery would it simply be a case of clicking download latest version and recovery? Then once recovered I could relock the bootloader? Or are there some other steps to do?
If anyone could help so I know for future reference that would be amazing. Thank you in advance
Click to expand...
Click to collapse
Glad you made it
I used eRecovery after I bricked my recovery partition and ended up with a working stock recovery, so yes, that should be the way. I did not try to relock the bootloader though.
Official builds from twrp.me are now available, OP updated.
a1Pha said:
Official builds from twrp.me are now available, OP updated.
Click to expand...
Click to collapse
i see pretorians TWRP has MTP working fine
but the official TWRP has not
if we decide to flash pretorians twrp and then yours, is that fine? or do we have to flash stock in-between?
virtyx said:
i see pretorians TWRP has MTP working fine
but the official TWRP has not
if we decide to flash pretorians twrp and then yours, is that fine? or do we have to flash stock in-between?
Click to expand...
Click to collapse
You should be fine switching between the builds as long as you don't touch other partitions.
a1Pha said:
You should be fine switching between the builds as long as you don't touch other partitions.
Click to expand...
Click to collapse
ty!
hopefully official can get MTP working fine fingers crossed.
Good day.
Can this use for rebrand from OCT652 to C636?
Thanks.
Hi im trying to find if there has been proper recovery made for the x704a devices and if there is actually custom roms that support the x704a . I've searched and searched and cant find much solid info. I see tons of the 704f, l, etc. but cant find anything specific or will work with the x704a for sure. I have the tablet with the stock android 71.1. rom and its a buggy mess always lagging and have to restart multiple times a day just to be able to try to use it. And its done this from day one and even after reflashing the stock rom from scratch. Trying to find options to make this thing better vs throwing it in the trash and wasting the money i paid for it. All help would be appreciated . Thanks in advance
Hi I am using a recovery that works with the x704a its hard to find I will have a look for a link or I can send you the file.
Regards Ashley
Download the onekey unlock and the twrp.
The default language is Chinese.
https://drive.google.com/open?id=1H5k46hztwj_1FeBxzfFIXqo5hy0OpJvr
So what custom roms have you guys found for these?
Sent from my HD1925 using Tapatalk
This tablet blows...x704a
I watched tons of reviews on the Lenovo tab 10. All positive reviews. So, when I found a version with 1 less gig of ram but cellular support I jumped on it as a $200 gift for my wife. Lenovo, the Amazon seller used the same exact name for the x704f and x704a.. they are not the same , this tablet blows. I ended up getting her another tablet and we are stuck with this pos. I would like to get a rooted cfw like lineage and no luck so far.
I have the same problem! My tablet is a lenovo tab x704A and only information about x704F appears, I don't know if it is the same, then try with that info, unlock the bootloader, download the twrp recovery for x704F when flashing it tells me that the procedure was a success, but the device It does not restart in twrp recovery, I did everything using the commands, I did it manually from the tab and nothing is only the original recovery (oem) as if I had not installed it, it must be because that recovery is not compatible. If you can help me!
Tegra4Me said:
This tablet blows...x704a
I watched tons of reviews on the Lenovo tab 10. All positive reviews. So, when I found a version with 1 less gig of ram but cellular support I jumped on it as a $200 gift for my wife. Lenovo, the Amazon seller used the same exact name for the x704f and x704a.. they are not the same , this tablet blows. I ended up getting her another tablet and we are stuck with this pos. I would like to get a rooted cfw like lineage and no luck so far.
Click to expand...
Click to collapse
Are you talking about Lenovo Tab4 10 x704A ? Is that the one with the ATT logo on the back, cuz I have that (one with 2gb of ram) and its rooted with magisk and has lineage OS and works great. You do need a special twrp file though.
{
"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"
}
manny71 said:
I have the same problem! My tablet is a lenovo tab x704A and only information about x704F appears, I don't know if it is the same, then try with that info, unlock the bootloader, download the twrp recovery for x704F when flashing it tells me that the procedure was a success, but the device It does not restart in twrp recovery, I did everything using the commands, I did it manually from the tab and nothing is only the original recovery (oem) as if I had not installed it, it must be because that recovery is not compatible. If you can help me!
Click to expand...
Click to collapse
I have Lenovo tab x704A its one with the ATT logo on the back right? It uses a special twrp file that only works with x704A recovery-TWRP-3.3.0-0521-LENOVO_TBX704A-CN-wzsx150.img . No other x704 variants twrps work on x704A and I have tried. Download that try to flash that to your recovery. I used this ROM https://forum.xda-developers.com/t/...neageos-16-0-for-lenovo-tab4-10-plus.3923394/
I haven't gotten to try the newer OS10 Lineage 17.
Folty57fg said:
I have Lenovo tab x704A its one with the ATT logo on the back right? It uses a special twrp file that only works with x704A recovery-TWRP-3.3.0-0521-LENOVO_TBX704A-CN-wzsx150.img . No other x704 variants twrps work on x704A and I have tried. Download that try to flash that to your recovery. I used this ROM https://forum.xda-developers.com/t/...neageos-16-0-for-lenovo-tab4-10-plus.3923394/
I haven't gotten to try the newer OS10 Lineage 17.
Click to expand...
Click to collapse
So this rom works with the x704a?
Folty57fg said:
Are you talking about Lenovo Tab4 10 x704A ? Is that the one with the ATT logo on the back, cuz I have that (one with 2gb of ram) and its rooted with magisk and has lineage OS and works great. You do need a special twrp file though.
View attachment 5187855
Click to expand...
Click to collapse
Could you help me with step by steps to install the twrp which you provided. I have the same XB704A tablet and I’m not successful in installing this twrp. I’m stuck. Kindly reply here or mail me at [email protected]
Bhaskarrv said:
Could you help me with step by steps to install the twrp which you provided. I have the same XB704A tablet and I’m not successful in installing this twrp. I’m stuck. Kindly reply here or mail me at [email protected]
Click to expand...
Click to collapse
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Don't setup, cause you will need to format your tablet later again. Shutdown tablet. Hold volume up and power button to start to bootloader
Then run
Code:
fastboot flash recovery twrp-3.2.3-0-<your-filename>.img
to flash TWRP
Select with volume buttons "Recovery Mode" and press power button
Select to write to system, otherwise you can't flash ROM
Backup at least system and boot partitions to your sdcard cause you will wipe data in next step. Choose "System Image" for the system partition backup.
Flash the recovery that I mentioned. Recovery-TWRP-3.3.0-0521-LENOVO_TBX704A-CN
The instructions I used were from this thread.
[ROM][UNOFFICIAL][9.0][TB-X704F/L] LineageOS 16.0 for Lenovo Tab4 10 Plus
/* * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...). * Please do some research if you have any concerns about features included in the...
forum.xda-developers.com
Use the twrp that I link, its only compatible with our tablet model. I rename it to like twrp.img then use "fastboot flash recovery twrp.img" instead of typing the whole name of the img file.
marcmann982 said:
So this rom works with the x704a?
Click to expand...
Click to collapse
sorry for late response, yes it works with x704a that what I screenshot it, you need a specific TWRP to install ROM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pixel Experience for Lenovo Tab 4 8 Plus
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 10.0
What's working?
Wifi
Mobile data
GPS
Camera
Bluetooth
FM Radio
Sound / vibration
Facelock
Fingerprint
Known issues
You tell me.
December 2020 security patch
Android 10
DON'T FLASH GAPPS, ALREADY INCLUDED
Download ROM
Android OS version: 10
Security patch level: December 2020
Build author/Device Maintainer: ChasTechProjects
Kernel Source: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953
Device Source code: https://github.com/ChasTechProjects/android_device_lenovo_TB8704
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
To install you should be running stock firmware, you can restore using the Lenovo Rescue and Smart Assistant (LMSA) tool on a PC, then follow the instructions in the app to rescue the device. Make sure to unlock the bootloader as well.
Now grab a copy of TWRP recovery from here. Install fastboot and adb on your PC by following this tutorial on XDA.
Boot your device into fastboot mode (power + volume down). You should know when you are in fastboot mode as it will show on the screen.
Open up the terminal or command prompt and run:
Code:
fastboot flash recovery <path to twrp.img>
Now turn off your device by pressing power until the screen is black, then boot into recovery (power + volume up).
TWRP should boot up. DO NOT ERASE SYSTEM, OTHERWISE YOUR DEVICE WILL HANG ON THE GOOGLE LOGO. Go to Advanced, tap ADB sideload, then run the following on your PC.
Code:
adb sideload <path to rom.zip>
Once it's finished sideloading, reboot back into recovery, then swipe factory reset. Now reboot into system.
It will take a couple of minutes to load and then you should see setup. You can now setup your device. Enjoy Pixel Experience and Android 10 on your Lenovo Tab 4 8 Plus!
Great work man, thank you
Thanks, I am looking forward to try this ROM out.
Now I am running Lineage 16, and trying to back to stock with LMSA but it just fails during the flashing process. Is there any preparations that needs to be done before using LMSA to go back to stock?
dape16 said:
Thanks, I am looking forward to try this ROM out.
Now I am running Lineage 16, and trying to back to stock with LMSA but it just fails during the flashing process. Is there any preparations that needs to be done before using LMSA to go back to stock?
Click to expand...
Click to collapse
Have you tried this?
1. Turn off the device.
2. Plug the USB cable into the computer, but NOT the tablet.
3. Press the volume up button (just that button, no others) and connect the tablet at the same time.
4. Keep pressing the volume button for a few seconds and then release.
5. Check if the device is recognised in Windows device manager, it should say something like "QCom QDL mode".
Thanx a lot, it's great!!
Everything is working beautifully and smoothly.
Just FM radio does not start.
Any help about the radio please..
Followed your instructions and everything worked well. Very happy with this one, I came from the other PixelExperience (Android 9) and this is a great upgrade. Keep up the good work!
Thanks.. This rom make my tablet like brand new.
thank you for the firmware, but there is one bug in the "about the Tablet" menu that does not show imei and serial number and does not show the firmware of the communication module.
I installed this on my TB-8704F and am getting no Wifi, and Bluetooth force closes. I installed it twice using the provided procedure. Can someone help please?
mr.inter said:
I installed this on my TB-8704F and am getting no Wifi, and Bluetooth force closes. I installed it twice using the provided procedure. Can someone help please?
Click to expand...
Click to collapse
Have you tried other custom ROMs?
I originally had Lineage OS 17.1, flashed stock Nougat with Miflash, and attempted installing this, where my issue was encountered. Wifi works if I flash stock once again.
mr.inter said:
I originally had Lineage OS 17.1, flashed stock Nougat with Miflash, and attempted installing this, where my issue was encountered. Wifi works if I flash stock once again.
Click to expand...
Click to collapse
Try flashing Oreo using the LMSA instead.
Unfortunately I'm having issues with LMSA.
Driver in Windows 10 seems to be ok. I even tried with an older version.
Given that LMSA did not work, I restored an official untouched Oreo image through TWRP and then installed Pixel Experience, however issue persisted.
mr.inter said:
Given that LMSA did not work, I restored an official untouched Oreo image through TWRP and then installed Pixel Experience, however issue persisted.
Click to expand...
Click to collapse
There's your problem. The TWRP image is likely missing proprietary drivers, etc. Follow the tutorial here https://android.stackexchange.com/q...image-lenovo-tab-m10-tb-x605l-lte-android-8-o using QDL on Linux and the official stock firmware.
I used official stock firmware (Android 7 QFIL - since this does not seem to exist for Oreo), and have just performed OTA update from Nougat to stock Oreo, however I still have no Wifi or Bluetooth on this ROM. I still came from an untouched Oreo image even though I did not follow the above procedure as of yet.
mr.inter said:
I used official stock firmware (Android 7 QFIL - since this does not seem to exist for Oreo), and have just performed OTA update from Nougat to stock Oreo, however I still have no Wifi or Bluetooth on this ROM. I still came from an untouched Oreo image even though I did not follow the above procedure as of yet.
Click to expand...
Click to collapse
Do other ROMs continue to work? Like, can you install LOS 17 on this and get back to me on that?
Yes everything else was working prior attempting to flash Pixel Experience. Will continue troubleshooting tomorrow.
Today I did the same thing as I was intending to install LOS 17 over this ROM without wiping anything, and Wifi and Bluetooth worked. Very strange but at the same time I am happy that now I have a chance to try this ROM.
Nice ROM . For those coming from another custom ROM: For moving over to Pixel Experience it was sufficient to boot into the recovery, wiping cache, dalvik and data and then installing PE (via adb sideload in my case). After a reboot PE loaded and could get set up.
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA!Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT!
What does not work?Fingerprint
face unlock
native camera app(Use gcam)
no notification slider
no modular refresh rate
no auto brightness(Not yet will be implemented)
no 5g(no worry no one uses it yet so)
maybe more let me know if you found a solution so i can add it under this post
I'm working on a overlay to fix some things for this device
What do I need?A Unlocked bootloader Follow below.
Stock zip download this with oxygen updater(enable advanced mode and download your version)
Oneplus drivers Here
Latest Fastboot Enhance Here
And a GSI of choice you can get Here or Here dot os works good with this phone
Choose AB GSI and you don't need slim(Low system volume device's) or vndklite(For older device's)
Unzip and put all the things in a folder.
Start with installing the Usb drivers
and connection device to your computer. (no need to disconnect till your set)
If your in windows use
Code:
cmd
Unlocking Bootloader (This will wipe device)
Go to Settings/About device/Version and tap the build number/version until you see your already a developer.
Spoiler: screen
{
"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"
}
Go to Settings/Additional settings/Developer options and enable OEM unlocking
Spoiler: screen
On your Computer open fastboot tool folder and open a terminal there and type
adb devices
Accept on your phone
adb reboot bootloader
wait till boot
fastboot flashing unlock
device will ask you to confirm if you want to unlock Confirm this
Spoiler: screen
Gathering your assetsOn your computer open platform-tools-enchanted folder and launch FastbootEnhance.exe
Now go to payload dumper and open your version zip
Go to partitions and CTRL click vbmeta, boot, system.
check the allow incremental box on the side
click extract images and extract them to your folder
Spoiler: screen
Preping device for GSIOn your computer open fastboot tool folder and open a terminal there and type
adb reboot bootloader
Wait till boot
fastboot reboot fastboot
you will see a screen with Chinese and languages as options don't do anything here.
On your computer open platform-tools-enchanted folder and launch FastbootEnhance.exe
than click on your device and go to partitions
Spoiler: screen
To make space for our new OS we need to make space so we are going to remove the old firmware left after update's
In the petitions tab type -cow and delete these volume's, Yes all volumes this will not affect your device
Spoiler: screen
Skip all above if you already on a GSIThe flashing of the GSI Make sure your GSI is a .img Unzip if its a xz/zip file
Now open fastboot tools folder and start a terminal there
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system Gsi.img
Spoiler: screen
wait till finished than on the phone click English and Format data and wait till it boots.
Spoiler: Pixel experience
Spoiler: CherishOS
The rootingget you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader
fastboot boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
reserve
Back to stock
Very simple aslong you dont mess around with other partitions
Open the fastboot tools folder and start a terminal.
adb reboot bootloader
fastboot reboot fastboot
fastboot erase system
fastboot flash system THE_SYSTEM_IMG_BACKUP_YOU_EXTRACTED
fastboot flash vbmeta vbmeta.img(Will remove gsi flash ability)
fastboot flash boot boot.img(Will remove root)
wait till finished than on the phone click English and Format data and wait till it boots. and your back to ****ty ColorOs
Absolutely what we need
Have anyone tried GSI on OP 10 T. Wanted to get a sense of this before I jump on.
Good man
I'll flash in the morning.
Cheers.
dladz said:
Good man
I'll flash in the morning.
Cheers.
Click to expand...
Click to collapse
Which one you took? Working fine so far?
I'm gonna make a overlay for our device this may box some issues and bugs
MrScarl3t said:
I'm gonna make a overlay for our device this may box some issues and bugs
Click to expand...
Click to collapse
Overlay?
lovesetcpu said:
Which one you took? Working fine so far?
Click to expand...
Click to collapse
I actually updated to beta 2, I couldn't help myself..tbh it's really good I'd recommend it.
Proximity sensor doesn't work for me or auto brightness but everything else is superb.. you can update directly from 12 to 13 using the update APK..
If you check the beta update thread on xda in this 10 pro section and you'll see it.. look for post #55
Thanks for the great guide on GSI. I managed to flash PE and Cherish OS, however, had to revert to stock as I couldn't get VOLTE to work. Tried all the ims in settings option, the GSI VOLTE FIX module but nothing helped. I can het LTE working, but not VOLTE. The problem is IMS is not registering. You have any suggestion to get the VOLTE working. BTW, my device is OP 10 T
alanzaki073 said:
Thanks for the great guide on GSI. I managed to flash PE and Cherish OS, however, had to revert to stock as I couldn't get VOLTE to work. Tried all the ims in settings option, the GSI VOLTE FIX module but nothing helped. I can het LTE working, but not VOLTE. The problem is IMS is not registering. You have any suggestion to get the VOLTE working. BTW, my device is OP 10 T
Click to expand...
Click to collapse
What didn't work or what did? Besides volte, I don't care for it here in the UK anyway.
But I'm interested in what is functional and what's not..
Appreciate you giving it a whirl.
dladz said:
What didn't work or what did? Besides volte, I don't care for it here in the UK anyway.
But I'm interested in what is functional and what's not..
Appreciate you giving it a whirl.
Click to expand...
Click to collapse
Honestly it was pretty good overall. As mentioned in OP, finger print, DTW, face unlock, auto brightness, VOLTE (my requirement as my network works on that for voice), doesn't work.
Besides these fairly good, passes safety net without root, (may pass even with it), fast charging ( didn't exactly time it or measure, but was fairly close to the stock ultra fast charging experience), and the beautiful fluid AOSP experience, 120 hz rr and the performance was somewhat better than stock, at least for gaming. Got 2800+ on 3d mark extreme and got 95% stability on the stress test. FYI - OP 10 T
alanzaki073 said:
Thanks for the great guide on GSI. I managed to flash PE and Cherish OS, however, had to revert to stock as I couldn't get VOLTE to work. Tried all the ims in settings option, the GSI VOLTE FIX module but nothing helped. I can het LTE working, but not VOLTE. The problem is IMS is not registering. You have any suggestion to get the VOLTE working. BTW, my device is OP 10 T
Click to expand...
Click to collapse
I will try tomorrow with OnePlus IMS apks maybe it will work. The phh IMS is not supported that's why
MrScarl3t said:
I will try tomorrow with OnePlus IMS apks maybe it will work. The phh IMS is not supported that's why
Click to expand...
Click to collapse
So, is it gonna be stored in System/priv app? I'm currently back on stock (will check for the ims apk) but itching to flash either PE or Corvus
alanzaki073 said:
So, is it gonna be stored in System/priv app? I'm currently back on stock (will check for the ims apk) but itching to flash either PE or Corvus
Click to expand...
Click to collapse
The name is org.codeaurora.ims don't know where it's located
I wish that it became more stable!
I can't stand with ColorOS 13 [OxygenOS 13] !!
Any luck on VOLTE?
Just wanted to say thanks again, it's great that you took the time to explain what to do in detail. Was able to flash dotOS without problems and to go back to Oxygen OS as well
yo-less said:
Just wanted to say thanks again, it's great that you took the time to explain what to do in detail. Was able to flash dotOS without problems and to go back to Oxygen OS as well
Click to expand...
Click to collapse
How was the experience?
Why you back to OxygenOS?
Few things to keep in mind before starting the process:
If you are on ColorOS12 make sure you are flashing OxygenOS12 and NOT OxygenOS 13; similarly if you are ColorOS13 you will have to use OxygenOS13 zip.
You must ALWAYS use OxygenOS newer than the ColorOS you have currently installed.
[English] Written Instructions:
(Note this is for 10pro, steps are the same but DON'T use any firmwares mentioned there)
How to Install Indian ROM on Chinese OnePlus 10 Pro
In this comprehensive tutorial, we will show you the detailed steps to install the Indian ROM on the Chinese OnePlus 10 Pro.
www.droidwin.com
[Chinese] Written Instructions:
关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安
Video Tutorial:
Downloads Links:
80W_C.15_OOS_Android13
150W_C.15_OOS_Android13
You can also follow the same instructions if you wish to convert to ColorOS. Just make sure you use ColorOS zip in that case.
Download link for ColorOS:
150W_ColorOS_C.17_Android13
I flashed OxygenOS into my new china OnePlus ACE (model PGKM10) recently. I'd like to share my experience here.
Note:
Be careful about each step, any small mistake might make your device hard bricked. If so, you have to contact the official service center to send your phone, or search for a random people who have the official internal tools to help you.
Don't simply reboot your phone if some error happened in fastboot mode, otherwise it might hard bricked.
Don't mess android version. For example use OxygenOS Android 13 and ColorOS Android 12, It will hard bricked.
Read it all before you touch your phone and PC!
Steps:
Prepare Fastboot Enhance (windows only), an OxygenOS rom.
Boot into your OnePlus ACE, enter developer mode, and enable oem unlocking and USB debugging.
Try to connect your phone with your PC. If you are using Windows 10 or newer, it would install OnePlus driver. It's necessary, otherwise you PC might not recognize your phone after enter fastboot mode. If you are using other OS, it's not required.
Turn off your device, enter fastboot mode. Note the fastboot interface looks like normal boot interface, but with some tiny text in the middle that says it's in fastboot mode.
Run fastboot flashing unlock to unlock partitions for flashing.
Prepare Fastboot Enhance, note it's windows only. If you are using other OS, you need to use fastboot command line tool, do it manually, and it has high risk. I failed once at the fastboot commands, and hard bricked.
Open fastboot enhance, click Partitions button, press Flash payload.bin, select the payload.bin file in the oxygenOS rom, and start. Some tutorials says to remove *-cow partitions, but I didn't find these partitions. That's fine.
If everything success, you can reboot your phone and enjoy!
Troubleshooting:
Myphone is not recognized by PC.
That's because your Windows PC needs OnePlus driver, try step 3.
If you completed step 3, but still got this problem. Just search it, you will get a lot of solutions. They are basically install winusb driver manually with the existing driver on PC.
My phone is hardbricked.
Don't worry.
Don't waste your time to try to solve by yourself. For example, mtk-client don't work. As the author mentioned at issue 577, Mediatek has locked it (dimencity 8100) down completely. The only way as I know is to use the official OPPO internal tools (Qualcomm 9008 mode), it requires internet and an internal employee account. Though its name, it works also for Mediatek dimencity 8100.
One way is to contact the official service center, and send your device to them. I didn't try it, but I think they can solve your issue.
Another way is to find a person who has the official internal tools, and pay for the service. The pros of this way is the whole process is online, and fast. I found NC Phone on youtube, and solved my issue. Note in this way, a Windows 64-bit, teamviewer and internet is required.
I
6cdh said:
I flashed OxygenOS into my new china OnePlus ACE (model PGKM10) recently. I'd like to share my experience here.
Note:
Be careful about each step, any small mistake might make your device hard bricked. If so, you have to contact the official service center to send your phone, or search for a random people who have the official internal tools to help you.
Don't simply reboot your phone if some error happened in fastboot mode, otherwise it might hard bricked.
Don't mess android version. For example use OxygenOS Android 13 and ColorOS Android 12, It will hard bricked.
Read it all before you touch your phone and PC!
Steps:
Prepare Fastboot Enhance (windows only), an OxygenOS rom.
Boot into your OnePlus ACE, enter developer mode, and enable oem unlocking and USB debugging.
Try to connect your phone with your PC. If you are using Windows 10 or newer, it would install OnePlus driver. It's necessary, otherwise you PC might not recognize your phone after enter fastboot mode. If you are using other OS, it's not required.
Turn off your device, enter fastboot mode. Note the fastboot interface looks like normal boot interface, but with some tiny text in the middle that says it's in fastboot mode.
Run fastboot flashing unlock to unlock partitions for flashing.
Prepare Fastboot Enhance, note it's windows only. If you are using other OS, you need to use fastboot command line tool, do it manually, and it has high risk. I failed once at the fastboot commands, and hard bricked.
Open fastboot enhance, click Partitions button, press Flash payload.bin, select the payload.bin file in the oxygenOS rom, and start. Some tutorials says to remove *-com partitions, but I didn't find these partitions. That's fine.
If everything success, you can reboot your phone and enjoy!
Troubleshooting:
Myphone is not recognized by PC.
That's because your Windows PC needs OnePlus driver, try step 2.
If you completed step 2, but still got this problem. Just search it, you will get a lot of solutions. They are basically install winusb driver manually with the existing driver on PC.
My phone is hardbricked.
Don't worry.
Don't waste your time to try to solve by yourself. For example, mtk-client don't work. As the author mentioned at issue 577, Mediatek has locked it (dimencity 8100) down completely. The only way as I know is to use the official OPPO internal tools (Qualcomm 9008 mode), it requires internet and an internal employee account. Though its name, it works also for Mediatek dimencity 8100.
One way is to contact the official service center, and send your device to them. I didn't try it, but I think they can solve your issue.
Another way is to find a person who has the official internal tools, and pay for the service. The pros of this way is the whole process is online, and fast. I found NC Phone on youtube, and solved my issue. Note in this way, a Windows 64-bit, teamviewer and internet is required.
Click to expand...
Click to collapse
In the Step #7, it should be *-cow partitions, No?
yashaswee1708 said:
I
In the Step #7, it should be *-cow partitions, No?
Click to expand...
Click to collapse
Ah, yes, it's a typo. edited.
I using color os c18 version. Can I flash oxygenOs c15 version? Both using android 13.
{
"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"
}
sSjBlueVN197 said:
I using color os c18 version. Can I flash oxygenOs c15 version? Both using android 13.View attachment 5876919
Click to expand...
Click to collapse
Better use OxygenOS13 C.18
https://gauss-componentotacostmanual-in.allawnofs.com/remove-e7d2bf870d4f18a40c740c8e51f95561/component-ota/23/02/17/2e75056f9c944c9e83dbeee99dca4734.zip
yashaswee1708 said:
Better use OxygenOS13 C.18
https://gauss-componentotacostmanual-in.allawnofs.com/remove-e7d2bf870d4f18a40c740c8e51f95561/component-ota/23/02/17/2e75056f9c944c9e83dbeee99dca4734.zip
Click to expand...
Click to collapse
are you sent to me 150w version? I flashed that version then my phone are not working, boot into OS then reboot.....
sSjBlueVN197 said:
are you sent to me 150w version? I flashed that version then my phone are not working, boot into OS then reboot.....
Click to expand...
Click to collapse
Yes it's for 150W. What you said shouldn't happen! It has worked for others.
Are you able to boot into fastboot?
(Try all key combinations)
yashaswee1708 said:
Yes it's for 150W. What you said shouldn't happen! It has worked for others.
Are you able to boot into fastboot?
(Try all key combinations)
Click to expand...
Click to collapse
I can boot into fastboot. T have done according above steps. But in step #7, i can't find *cow file so after flashed, i reboot the system but it not working normaly
Launcher not working, It just display black screen and battert percent always display 0%. After 2~3 minute, my phone auto reboot system, and I can't factory reset in settings
sSjBlueVN197 said:
Launcher not working, It just display black screen and battert percent always display 0%. After 2~3 minute, my phone auto reboot system, and I can't factory reset in settings
Click to expand...
Click to collapse
Try factory reset from recovery?
sSjBlueVN197 said:
I can boot into fastboot. T have done according above steps. But in step #7, i can't find *cow file so after flashed, i reboot the system but it not working normaly
Click to expand...
Click to collapse
If you can boot in fastboot do the process again. I'll share the zip once again
oh, I'm trying factory from recovery, it can be done. Thanks you very much ^^!
after flashed OOS, can I re-lock bootloader?
sSjBlueVN197 said:
oh, I'm trying factory from recovery, it can be done. Thanks you very much ^^!
Click to expand...
Click to collapse
Let me know if the issues are fixed
sSjBlueVN197 said:
after flashed OOS, can I re-lock bootloader?
Click to expand...
Click to collapse
You can but the process is a bit complicated, on recent updates some time the phone is bricking when we run the query fastboot flashing lock.
So I won't recommend it. Until we can find a easier way.
yashaswee1708 said:
Let me know if the issues are fixed
Click to expand...
Click to collapse
oh yeah, Issue occur when flash without format data, only format data from recovery to resolve this issue ^^
sSjBlueVN197 said:
oh yeah, Issue occur when flash without format data, only format data from recovery to resolve this issue ^^
Click to expand...
Click to collapse
So currently everything is okay?
yashaswee1708 said:
So currently everything is okay?
Click to expand...
Click to collapse
yup, everything is OK
80W_C.15_OOS_Android13 it's for Ace racing bro?