Tried my luck repartitioning the tablet, increasing the system partition and reducing the userdata partition. afterwards i flashed a/b gsi's using makemesar zip in order to get them working. that did not work, had to go back to stock.
Lately, i have discovered that our tablet shares some specs with its cousin, the Mediapad T5. and T4 has an active community, more developers, more custom recovery and even a way to rebrand their tablet to their chinese counterparts. how is this rebranding important ?
well, the chinese counterparts have access to updates. huawei didnt drop support for them as it did for us. so, they got update to android 9 and then Harmony OS (which is Android 10).
So i will see if i can rebrand my tablet into a chinese counterpart and get update to android 10. afterwards i will make a guide here.
If it works it would be fantastic. Is it possible flashing the Chinese iso image
directly to the European device?
yes, thats the intended output. the chinese device has even updates to harmony os 2.0 (android 10). so far these been a few success stories and a lot of hard-breaks. so dont jump into other threads and flash stuff.
Fytdyh said:
yes, thats the intended output. the chinese device has even updates to harmony os 2.0 (android 10). so far these been a few success stories and a lot of hard-breaks. so dont jump into other threads and flash stuff.
Click to expand...
Click to collapse
Yes, I've read the t5 thread. I hope you can find a way to rebrand this model too. If you need some help you can send me a p.m.
Thanks God! I hope you have success in your way, good luck! It would be fabulous update to android 10 this tablet.. oh my god.. still at 8. So sad
Is there a way to rebrand this model to chinese?
Related
Hi,
I have the an european Honor6x BLN-21 still on EMUI 5.0.3. I want to upgrade to OpenKirin/Omnirom 5.2 but that requires EMUI 8.
Do I understand it correctly that I can use "Resurrection Remix OS Beta 3" to get my Honor6x to EMUI 8? or can i directly use Omnirim 5.2?
Cheers
Hello there,
absolutely not! You've misunderstood the correct path to follow. You can't flash RROS beta 3 over EMUI 5.0.3 because it requires your device to be already on EMUI 8 in way to correctly flash those ROMs. You should do this before:
1) unlock the bootloader of your device;
2) debrand your device to India variant thanks to this guide https://forum.xda-developers.com/honor-6x/how-to/guide-debranding-to-india-variant-bln-t3679402;
3) update to EMUI 8 in way to finally obtain Treble compatibility, steps listed here https://forum.xda-developers.com/honor-6x/how-to/update-bln-l22c675-emui-5-x-x-to-emui-8-t3819317
If you manage to update to EMUI 8, you'll open wide your path to many other stuff (GSIs, ROMs for EMUI 8), and so you'll have the better base/preparation to start playing. Good luck
alright ill to become indian
if were on that, is whats the cheapest way to get the bootloader unlocked these days?
DC-Unlocker is the anwser. The credits necessary to unlock the device are 4$, as said by many other users, but since that in this way you can give a new life to your phone, it's an acceptable compromise.
RedSkull23 said:
DC-Unlocker is the anwser. The credits necessary to unlock the device are 4$, as said by many other users, but since that in this way you can give a new life to your phone, it's an acceptable compromise.
Click to expand...
Click to collapse
Great, that actually worked. Thanks
sungod3k said:
Great, that actually worked. Thanks
Click to expand...
Click to collapse
Ok. No problem, next time thank me with the appropriate button
I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.
Jewel724 said:
I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.
Click to expand...
Click to collapse
Vivo doesn't allow bootloader to be unlocked
That's nonsense, I can enable OEM unlocking in the developer settings, ain't that what's required?
Austinredstoner said:
Vivo doesn't allow bootloader to be unlocked
Click to expand...
Click to collapse
It's not Vivo company! That's a BLU company.
Jewel724 said:
I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.
Click to expand...
Click to collapse
You need a special steps for work. Not a exclusive file to your phone because GSI (actual custom rom for any device with Android 8.1 and next android version) need some files to fix booting that in your device. But the happy notice is about actual GSI files not need very files for fix or maybe nothing.
Try install AOSP from phhusson Android 9 and Android 10 repository to know. Other great GSI is crDroid by eremitein or other GSI files by him. Need testing.
DragonPitbull said:
It's not Vivo company! That's a BLU company.
You need a special steps for work. Not a exclusive file to your phone because GSI (actual custom rom for any device with Android 8.1 and next android version) need some files to fix booting that in your device. But the happy notice is about actual GSI files not need very files for fix or maybe nothing.
Try install AOSP from phhusson Android 9 and Android 10 repository to know. Other great GSI is crDroid by eremitein or other GSI files by him. Need testing.
Click to expand...
Click to collapse
I'm on.. what's it called, Oreo? Android 8. Not sure if that's going to cause any trouble for roms.
Jewel724 said:
I'm on.. what's it called, Oreo? Android 8. Not sure if that's going to cause any trouble for roms.
Click to expand...
Click to collapse
Yes! Android 8 from very OEMs/companies not have Treble/GSI compatibility.
Only Android 8.1 has that.
Update: Install this app https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en-US in the phone and know what architecture your phone/firmware has. That will show you which type of GSI file you can test.
Listing what that app says..
Required Image: Needs an image file named system-arm64-aonly.img.xz
Treble and VNDK: Supports legacy version of Treble, using VNDK version 27.0
System as Root: Does not support, use an a-only OS.
ARM-64 archetecture.
Seamless Upgrades not supported.
Does not use Dynamic Partitions.
Unless I missed anything, is this what was needed? Also I am on 8.1.0 for android version, I didn't know if that was just Oreo or if 8.1 had it's own name.
Jewel724 said:
Listing what that app says..
Required Image: Needs an image file named system-arm64-aonly.img.xz
Treble and VNDK: Supports legacy version of Treble, using VNDK version 27.0
System as Root: Does not support, use an a-only OS.
ARM-64 archetecture.
Seamless Upgrades not supported.
Does not use Dynamic Partitions.
Unless I missed anything, is this what was needed? Also I am on 8.1.0 for android version, I didn't know if that was just Oreo or if 8.1 had it's own name.
Click to expand...
Click to collapse
In the first update Android 7.1 [Nougat] to 8.0 and after upgrade to 8.1 [Oreo]. Normal.
All informations good to know what GSI you should test.
Now you can install with fastboot or Custom Recovery [TWRP]. So if has is better and fast.
If not so can using fastboot commands.
Obviusly need bootloader unlocked!
You can read and find more threads but this is good: https://forum.xda-developers.com/t/guide-blu-vivo-xl4-vivo-xi-vivo-xi.3877294/
The only part I should warn you about is the loss of IMEI. So soon as you can do backup from your phone the files NVRAM; NDATA; NVCFG with SPFT or other way like fastboot you won't have wasted time and hassles.
DragonPitbull said:
In the first update Android 7.1 [Nougat] to 8.0 and after upgrade to 8.1 [Oreo]. Normal.
All informations good to know what GSI you should test.
Now you can install with fastboot or Custom Recovery [TWRP]. So if has is better and fast.
If not so can using fastboot commands.
Obviusly need bootloader unlocked!
You can read and find more threads but this is good: https://forum.xda-developers.com/t/guide-blu-vivo-xl4-vivo-xi-vivo-xi.3877294/
The only part I should warn you about is the loss of IMEI. So soon as you can do backup from your phone the files NVRAM; NDATA; NVCFG with SPFT or other way like fastboot you won't have wasted time and hassles.
Click to expand...
Click to collapse
I'll give it a shot. In terms of performing a backup, I would assume that' typical "copy all files on phone to desktop folder just in case"
I should've mentioned, I don't have an SD card in my device, just a SIM card. I don't think I can use TWRP, which is going to complicate matters.
Hello I have a Blu Vivo XL4 android 8.1.0 Oreo, I'm trying to install a custom rom, I looked everywhere not a single rom is made for Blu phones.
bootloader unlocked
according to treble info:
System-arm64-aonly.img.xz
Your device supports the legacy version of project treble using VNDK version 27.0
Use an A-ONLY operating system
ARM64
Seamless upgrades are not supported
NO dynamic partitions
HELP
thanks
Hi I have a samsung SM-970u ( s10e snapdragon TMO) is there a way to make a downgrade form android 11 to android 10 ?
I...wondered the exact same thing....
but even with an unlocked bootloader it doesn't seem possible if your bootloader version is too high...it was possible when Android 11 first came out but versions may have changed now. I tried flashing with odin myself but I'm getting sw rev check fail... even with an unlocked bootoader.
I'd love to be wrong cause I want stock android 10 but i can't find info otherwise.
Deathlan said:
Hi I have a samsung SM-970u ( s10e snapdragon TMO) is there a way to make a downgrade form android 11 to android 10 ?
Click to expand...
Click to collapse
What's your current Build/Baseband?
I was wondering if I can downgrade from 12 to 9.
But as I'm reading a lot of posts, I'm guessing it will be next to impossible?
Build: SPA1.210812.016.G970FXXUEGVA4
Baseband: G970FXXUEGVA2
Cilvaring said:
I was wondering if I can downgrade from 12 to 9.
But as I'm reading a lot of posts, I'm guessing it will be next to impossible?
Build: SPA1.210812.016.G970FXXUEGVA4
Baseband: G970FXXUEGVA2
Click to expand...
Click to collapse
You can never officially downgrade more than one version.
The only possibility would be to unlock the phone's bootloader and flash a custom ROM based on Android 9. But I do not even know if it is theoretically possible to run an Android 9 ROM on an Android 12 bootloader
iBowToAndroid said:
You can never officially downgrade more than one version.
The only possibility would be to unlock the phone's bootloader and flash a custom ROM based on Android 9. But I do not even know if it is theoretically possible to run an Android 9 ROM on an Android 12 bootloader
Click to expand...
Click to collapse
From what I've learned the phone has a version of the bootloader.
In my case that's version 14 (resp. E because it's hexadecimal)
I found that f.e. Android 11 was released in versions that had different bootloader versions (9, A, B, C, D & E).
So I was only able to install the Android 11 that came with bootloader version E.
And as it stands now, it seems like it's impossible to downgrade the bootloader which in the end makes it a huge pile of s**t on Samsung's or even Google's end.
It's kinda the Apple way of doing things and not letting you do what you wish...
Cilvaring said:
It's kinda the Apple way of doing things and not letting you do what you wish...
Click to expand...
Click to collapse
Kind of. Except:
1. Apple doesn't let you downgrade firmware at all
2. Apple doesn't offer unlockable bootloaders and therefore there's no possibility of a custom ROM
Cilvaring said:
From what I've learned the phone has a version of the bootloader.
In my case that's version 14 (resp. E because it's hexadecimal)
I found that f.e. Android 11 was released in versions that had different bootloader versions (9, A, B, C, D & E).
So I was only able to install the Android 11 that came with bootloader version E.
And as it stands now, it seems like it's impossible to downgrade the bootloader which in the end makes it a huge pile of s**t on Samsung's or even Google's end.
It's kinda the Apple way of doing things and not letting you do what you wish...
Click to expand...
Click to collapse
It's a cruel lesson. Android becomes more Apple than Android with each upgrade.
Literally the first thing I do on a new Samsung is package block OTA updates.
I have two N10+'s, one running on 9, the other 10.
They will stay on that firmware.
iBowToAndroid said:
Kind of. Except:
1. Apple doesn't let you downgrade firmware at all
2. Apple doesn't offer unlockable bootloaders and therefore there's no possibility of a custom ROM
Click to expand...
Click to collapse
Well yes, but the fact that google's core apps are not open source and more and more APIs or libraries are only available on phones that have certain pre-installed google apps takes a big piece of liberty out of android.
My bet also is, it won't get better since google just won't stop generating money in new ways day after day.
But: Android still is a whole lot better than the half-eaten piece of fruit. No doubt.
blackhawk said:
It's a cruel lesson. Android becomes more Apple than Android with each upgrade.
Literally the first thing I do on a new Samsung is package block OTA updates.
I have two N10+'s, one running on 9, the other 10.
They will stay on that firmware.
Click to expand...
Click to collapse
I hear you.
Was running a S7 with Oreo before I switched to the S10e now and it will stay on Oreo until it dies as a backup phone.
Sadly the seller of the S10e already had updated it to 12, so I'm stuck with at least 11 due to the bootloader.
Cilvaring said:
I hear you.
Was running a S7 with Oreo before I switched to the S10e now and it will stay on Oreo until it dies as a backup phone.
Sadly the seller of the S10e already had updated it to 12, so I'm stuck with at least 11 due to the bootloader.
Click to expand...
Click to collapse
Android 11 was one reason I bought a new N10+ about 5 months ago versus a N20U. I thought new N10+ be running on 9 but it ended up loaded with 10 due to the manufacturing date. It turned out ok.
I learned the hard way with Samsung and upgrades 6 years ago... and was about as happy as you.
Unfortunately many of the resellers will load whatever is the latest OS version when they test out a phone.
It's more than just a little aggravating. Forget the Google bs hype... I still remember the horror of MS Vista
Hopefully you'll find workarounds to iron out the rough edges or if it really gets on your last nerve return or resell it. Life's too short to live with a phone you hate.
Finally got my tablet back after two months of back and fourth from China (long story).
I just wanted to put a bit of an update. The tablet came back with the default firmware and recvied 5 OTA's of differing sizes. The software is now in a place where if English is your native language I'd comfortable recommend this tablet. Every thing seems to work nicely now. Netflix supports Dolby Vision, the security center is working and if you add a third party launcher and deactivate the Chinese apps you'd barely know it wasn't made for your region. It took 3 months from Launch but Lenovo got there in the end.
Having used the tablet for about 4/5 hours straight I can comfortably confirm the Screen is far far better than the P11 Pro. You'll notice on the P11 Pro that pixle arrangement gives a grainy look on some colours most notably red. This does not occur on the P12 Pro. It was worth the wait.
Update. However the below info is still relevant regarding flashing Global ROM's to the CN Tablet.
I have a seperate thread here covering other annoyances. https://forum.xda-developers.com/t/no-opencl-or-dts-on-p12-but-present-on-p11-2021.4366861/
Due to these issues I decided to flash to the ROW (international) P12 Pro ROM using the instructions at on this video (using the correct ROM for my device obviously)
THIS PROCESS DOES NOT WORK. DO NOT ATTEMPT THE ABOVE YOU WILL BE STUCK IN THE BOOT LOADER.
I will update this thread if the situation improves!
If anyone can help me locate the chinese stock ROM for this tablet I would greatly appreciate it and will buy you a couple of beers via Paypal.
Moving some of the comments from my thread to this one.
According to the Chinese forums, the protections (against region switch and rollback) were implemented since ZUI 12.6. This was before the release of this device and applies to P11 series as well.
I suppose the bootloader you flashed can detect whether your device is of the right region or not, and will not proceed any further. If that's the case... I think you'll have to wait until someone actually dumped an entire PRC FW (including the bootloader parts), so you can (probably) at least revert the device back to a working state.
Anyone who hasn't OTA upgraded the P12 (XiaoXin Pad Pro 12.6) may try using logcat (or use tools like Fiddler) to obtain some hints about possible whereabouts of full OTA packages for this device. It may be possible to convert a full OTA package to a way usable by QFIL to restore the device. I once tried this to look for hints, but no avail... maybe the OTA servers have changed since then.
LSS4181 said:
Moving some of the comments from my thread to this one.
According to the Chinese forums, the protections (against region switch and rollback) were implemented since ZUI 12.6. This was before the release of this device and applies to P11 series as well.
I suppose the bootloader you flashed can detect whether your device is of the right region or not, and will not proceed any further. If that's the case... I think you'll have to wait until someone actually dumped an entire PRC FW (including the bootloader parts), so you can (probably) at least revert the device back to a working state.
Anyone who hasn't OTA upgraded the P12 (XiaoXin Pad Pro 12.6) may try using logcat (or use tools like Fiddler) to obtain some hints about possible whereabouts of full OTA packages for this device. It may be possible to convert a full OTA package to a way usable by QFIL to restore the device. I once tried this to look for hints, but no avail... maybe the OTA servers have changed since then.
Click to expand...
Click to collapse
Thanks for the update. Yes it's pretty grim. At this point I think I have to send it back to China for Repair or claim on gadget insurance!
Updated first post to reflect the most recent software updates. TLDR go for the Chinese ROM if English is your native language and you want trouble free OTA's.
The data for the Chinese version of the firmware has been uploaded to a Japanese blog.
However, this data does not contain contents.xml and is incomplete.
Can't install it with QFIL as it is.
TB-Q706F_CN_WIFI_USER_Q00243.2_R_ZUI_13.0.348_ST_210929
TB-Q706F_CN_WIFI_USER_Q00243.2_R_ZUI_13.0.348_ST_210929 - Google Drive
drive.google.com
Lenovo XiaoXin Pad Pro 12.6レビュー。最高画質の原神を中央値60FPSでプレイできる最強タブレット - AndroPlus
BanggoodでLenovo XiaoXin Pad Pro 12.6を割引価格で購入しました。 12.6インチ、120Hz対応有機EL Lenovo XiaoXin Pad Pro 12.6は12.6インチ2560x1600解像度の有機ELディスプレイを搭載したAndroidタブレットです。
androplus.org
Yes, it is a backup of some partitions (not all) only. It not possible use with Qfil for flashing.
It can be usable for flashing via fastboot.
Hey guys all good?
I got my hands on an A53 already on Android 13 (U.I 5.1), then I unlocked the bootloader, rooted, magisk working but then I decided to downgrade from 13 to 12 because of a few things
I tried via Odin (13.14.4 and 13.12.7) and both didn't work the first odin it fails the flashing and the second pass but it didn't flash the whole thing just reset the phone
any idea? or I'm now stuck with Android 13?
Cheers
From what I can find, Odin supposedly won't allow a downgrade if the boot loader version is lower.
That's just what people seem to say about Samsung devices and downgrading. I've never tried it and never will. Would immediately use multiple OS versions however if Android actually supported dual booting. Its fantastically messed up that it doesn't.
Not sure if TWRP will. Didn't look that one up. You didn't bring that one up but it might be a way to do it.
sandsofmyst said:
From what I can find, Odin supposedly won't allow a downgrade if the boot loader version is lower.
That's just what people seem to say about Samsung devices and downgrading. I've never tried it and never will. Would immediately use multiple OS versions however if Android actually supported dual booting. Its fantastically messed up that it doesn't.
Not sure if TWRP will. Didn't look that one up. You didn't bring that one up but it might be a way to do it.
Click to expand...
Click to collapse
Thanks for the reply. I was thinking something about that too. Not that the bootloader is lower but that it was modified (root) i guess
Unfortunately TWRP is not compatible yet with Android 13 UI 5.1 at least accordingly to this topic
So i guess I'm stuck for now
biustech said:
Thanks for the reply. I was thinking something about that too. Not that the bootloader is lower but that it was modified (root) i guess
Unfortunately TWRP is not compatible yet with Android 13 UI 5.1 at least accordingly to this topic
So i guess I'm stuck for now
Click to expand...
Click to collapse
You could flash a GSI image, but I guess that wouldn't be OneUI anymore
Hello you all hope you're having a good day, so no way to downgrade a53 5g from Android 13 to android 12 ??? I found some firmwares for Android 12 but the binary number is 4 and Android 13 is actually on binary number 5 , no way to do the downgrade with Odin?
I read somewhere that is not possible to flash a firmware with different binary number is it true ?? I would like to comeback to android 12 it's better