Hi guys, so I bought my first Realme phone a couple of months ago and I noticed that the Google Pay app wasn't working. I checked the ali store where i bought it and surely it said "Global rom: This is the version with global firmware installed, with many languages, including portuguese language, spanish language, google store is normal, but please note that google pay payment does not work properly". For any reason, this ROM wont let me have Google Pay, so I wanted to know if any of you knows how to enable the Google Pay app? or should I install another ROM? Has any of you had a similar problem? Thanks
Perhaps shift from global to Europe firmware?
Im from South America, so I dont know if the European firmware would work. I'm having a little bit of trouble finding out how RUI 3.0 - Firmware - ROM work. Also, do you know how to do the shift from Global to European? Or at least a tutorial? Ive seen the site https://realmefirmware.com/realme-gt-neo2-5g-firmware/ which has the global firmware released today but I dont know if it's just installing the firmware and problem solved.
Bootloader unlocked = no google pay, it will only work with the original firmware channel, don't try locking your bootloader if you are not 100% sure of it, this will cause your phone to bootloop and you will end up with a bricked device that only realme support would be able to solve, the best solution would be to spoof your device fingerprint to pass the SafetyNet and everything will work just fine, you can contact me for help if you want.
Yes Im going to need a little bit of help with that, thanks
hen1_98 said:
Bootloader unlocked = no google pay, it will only work with the original firmware channel, don't try locking your bootloader if you are not 100% sure of it, this will cause your phone to bootloop and you will end up with a bricked device that only realme support would be able to solve, the best solution would be to spoof your device fingerprint to pass the SafetyNet and everything will work just fine, you can contact me for help if you want.
Click to expand...
Click to collapse
Hello hen1_98, so may I know how to spoof the fingerprint to pass SafetyNet?
drwpls said:
Hello hen1_98, so may I know how to spoof the fingerprint to pass SafetyNet?
Click to expand...
Click to collapse
With Magisk installed you can use the Universal SafetyNetFix by kdrag0n, easy fix
hello, I also flashed the phone, changed the region, rooted it (now it does not work). And closed the bootloader. works on the old bank, but the new (other) does not want to.
hen1_98 said:
With Magisk installed you can use the Universal SafetyNetFix by kdrag0n, easy fix
Click to expand...
Click to collapse
i did install it, but CTS profile still not pass.
I figure out that I need a valid fingerprint which associate to the device (The one which registered to google) to make CTS check pass.
So, I need the fingerprint when the device is in stock rom and haven't rooted.
Related
I'm unable to use Android Pay - I'm not rooted, the boot loader is RELOCKED but when I try and add my card I get the dreaded "Google is unable to verify that your device or software running on it is Android compatible" error.
So, I was wondering, is it the fact that I did previous unlock my boot loader or something else stopping me.
BTW, Vendor: hw Country: eu, running C432B170.
Cheers.
No joy either
Same problem here. Imported mine and have done nothing but update to latest version of official roms (tried a couple of different ones today as well) and I get the same error. No rooting, purposely held off doing so so I could try Android Pay. SafetyNet Helper says the "CTS profile match" is false. My wild stab in the dark is that it is something to do it with it being identified as an international handset or handset from a non-Android pay supported country.
Had a web chat with an Android Pay helpdesk monkey and they had me reboot and reinstall a few times. They've also had me send some screenshots but I'm not holding out much hope for a useful reply.
captainkibble said:
CTS
Click to expand...
Click to collapse
CTS or CSC?
themissionimpossible said:
CTS or CSC?
Click to expand...
Click to collapse
CTS. Just double checked.
Maybe it's the same thing as CSC for Samsung phones.
In case, this might represent the target market for that phone, and that market might not yet be allowed to use Android Pay.
I'm using the single SIM version, NXT-L09, I managed to add my card but when I tried to pay for something in store I got the unable to verify.... message pop up on screen.
It also fails the CTS profile match in Safetynet helper
Android Pay worked for me today
I gave safetynet helper another try and this time it said my device passed. Re added my card to it and then used it on a London bus.
Using a Mate 8 NXT-L09C636B170
I too am able to use Android Pay. It started working for me last Thursday. While I had an open support ticket with the Android Pay help desk I periodically checked to see if it had started working. Eventually it did. I was able to add cards, SafetyNet Helper passed it's check and I was able to make payments. Result.
The same day, Android Pay help desk got back to me regarding my support ticket (there had been some backwards and forwards with logs, screenshots and the like). They concluded that Android Pay would not work because my phone was rooted. It isn't and has never has been. They had me send screenshots of multiple root checkers that displayed that the phone was not rooted *before* they came to this conclusion. I guess they just wanted the ticket closed and that was the most convenient excuse.
I've put it down to enough people reporting handsets not working that the Google added more phones to the "approved list" and help desks don't know what they are talking about.
My build number is NXT-L29C636B180
Hm.. Well this was interesting to read. Thanks for the updates saying that Android Pay does in fact (hopefully) work! I'm going to to get the L29 International dual SIM version soon so I was curious... I'll update when I get it and test it out
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
gnasher666 said:
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
Click to expand...
Click to collapse
Same here...
bh4714 said:
Same here...
Click to expand...
Click to collapse
I've downgraded to B170 and now have Android Pay working.
The high level process was:
All done via the help of SRK Tool http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
1) Unlock Boot Loader
2) Install Custom Recovery
3) Root Phone
4) Change to oeminfo and custom.bin eu (c432) - Even though I already was
5) Copy Full Update.app for C432B153 to dload folder
6) Flash stock recovery
7) Boot recovery and allow update to install
8) Factory Reset
9) Copy Update.app for C432B170 to dload folder
10) Boot recovery and allow update to install
I'm not sure how but following this process (although I've listed the steps from memory and not in front of my Laptop I did this on) I ended up with a Bootload LOCKED C432B170 and Android Pay works. I've not - nor will I update to and EMUI 4.1 version until they are released as OTA updates that my phone asks me to install
Android Pay was working fine on B103, I've upgraded to B321 via dload and now got pop up info that my device is incompatible with android pay. Any ideas?
Sent from Huawei Mate 8
Just one question
Hi,
Which recovery should I flash? the one for EMUI 4.1 or 4.0?
thanks
I believe Android Pay will not work with EMUI 4.1. I wish we were warned about this before we were allowed to flash to 320 or 321. No warning with the update links. Sucks!
Sent from my HUAWEI NXT-L29 using XDA-Developers mobile app
Hello Forum People,
I have my bootloader unlocked, build MHA-L29C432B198, TWRP recovery and I use Magisk v14.5 however I cannot seem to pass SafetyNet with Magisk failing on ctsProfile and basicIntegrity and "SafetyNet Test" (from the Play Store) passing Safety Net Request but failing Response Signature Validation ("Response Payload Validation Failed").
I have a suspicion that this is due to the unlocked bootloader as I have removed Magisk and anything else I think might have tripped SafetyNet but always the same issue.
Can anyone confirm if this is the cause or otherwise and if having my bootloader unlocked is 'causing SafetyNet to fail then is it safe to relock after re-installing Magisk and returning recovery back to stock or is there some kind of work around?
Muchos appreciated in advance!!
It works fine with unlocked bootloader. Check in Playstore - hamburger menu - scroll down - Settings - scroll down - Device certification: can be certified or uncertified.
It's usually uncertified if your firmware is not approved yet by Huawei. And that would make safetynet fail.
What modules are you using? Xposed will also make safetynet fail.
You could try installing the propfix for magisk, found here: https://mega.nz/#!IOAgibSQ!uix7Gku_MY0ETP-zTae03awF_uH_Jgatr1SDEEvw77A
And did you happen to have SuperSU installed prior to Magisk?
ante0 said:
It works fine with unlocked bootloader. Check in Playstore - hamburger menu - scroll down - Settings - scroll down - Device certification: can be certified or uncertified.
It's usually uncertified if your firmware is not approved yet by Huawei. And that would make safetynet fail.
What modules are you using? Xposed will also make safetynet fail.
You could try installing the propfix for magisk, found here: https://mega.nz/#!IOAgibSQ!uix7Gku_MY0ETP-zTae03awF_uH_Jgatr1SDEEvw77A
And did you happen to have SuperSU installed prior to Magisk?
Click to expand...
Click to collapse
I have tried the propfix and that was unsuccessful in my case. Looks like it's because the firmware is uncertified which is confusing since I updated OTA by official means; update manager gave me a notification, I updated.
Is this a likely scenario that it could be uncertified even though they issued the update?
beejkitsune said:
I have tried the propfix and that was unsuccessful in my case. Looks like it's because the firmware is uncertified which is confusing since I updated OTA by official means; update manager gave me a notification, I updated.
Is this a likely scenario that it could be uncertified even though they issued the update?
Click to expand...
Click to collapse
So according to HiSuite I have an official ROM, I have performed a full factory reset and I am still getting uncertified status through Play Store. I cannot understand this as previously everything was working fine, I could use my banking app etc. and then one day everything stopped working and the only thing I can trace it to is this uncertified status.
Can anyone help me at all because short of going to extremes of using FH to rebrand etc I am all out of ideas and not being able to pass SafetyNet is really annoying; I can no longer use my banking app or Android Pay.
beejkitsune said:
So according to HiSuite I have an official ROM, I have performed a full factory reset and I am still getting uncertified status through Play Store. I cannot understand this as previously everything was working fine, I could use my banking app etc. and then one day everything stopped working and the only thing I can trace it to is this uncertified status.
Can anyone help me at all because short of going to extremes of using FH to rebrand etc I am all out of ideas and not being able to pass SafetyNet is really annoying; I can no longer use my banking app or Android Pay.
Click to expand...
Click to collapse
This is infuriating. I cannot seem to fathom why my device would suddenly be unverified.
I have considered locking my bootloader again but with attempts to do that I am given re-locked status. Suggestions, anyone, please?
Sent from my Mate 9 using XDA Labs
beejkitsune said:
This is infuriating. I cannot seem to fathom why my device would suddenly be unverified.
I have considered locking my bootloader again but with attempts to do that I am given re-locked status. Suggestions, anyone, please?
Sent from my Mate 9 using XDA Labs
Click to expand...
Click to collapse
I know my comment comes a little late, but just so you know,
I'm not certified (according to Google play store), and yet I pass SafetyNet. So your problem doesn't seem to be related.
I'm on B197 and Safety Net 14.3, and B197 was also officially pushed to my phone by Huawei.
Surfinette said:
I know my comment comes a little late, but just so you know,
I'm not certified (according to Google play store), and yet I pass SafetyNet. So your problem doesn't seem to be related.
I'm on B197 and Safety Net 14.3, and B197 was also officially pushed to my phone by Huawei.
Click to expand...
Click to collapse
Thanks for the reply. My solution ended up being to. Rebrand and then update to the Oreo release MHA-L29C432 8.0.0.361. Play Store now certified and passing SafetyNet with no issues. I'm still not 100% sure what tripped SafetyNet originally, nothing seems to be consistent with other people's experiences but I have now a resolution albeit not the desired approach, nor solution.
Does anyone know how to root? Till yet ?
Today IT was my Christmas.present
Thanks
Daniel
No source from motorola, nor updates yet.
Hello you can root your moto with magisk.
Mounib BOULAABI said:
Hello you can root your moto with magisk.
Click to expand...
Click to collapse
If you have a copy of the boot.img
Sent from my mata using XDA Labs
Thanks by the way. I found i way to root my Device.
Please do tell, how?
Danieldergrosse said:
Thanks by the way. I found i way to root my Device.
Click to expand...
Click to collapse
Would you mind sharing your way to root your device? Every piece of knowledge can help other users here on XDA.
Sent from my Moto G5 Plus using XDA Labs
http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method
Danieldergrosse said:
http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method
Click to expand...
Click to collapse
*
your link seems dead or not correct. - edit: link correct, was not working due to my vpn...
I assume he patched a G8+ boot.img with magisk manager.
boot image can be extracted from official Doha firmware found here: https://mirrors.lolinet.com/firmware/moto/doha/official/
manual on how to do this can be found on official magisk manager website.
be aware that when unlocking bootloader your phone will reset to factory settings.
This is what I did. Yes..
Worked great for my G8+. I guess people should just check which stock ROM file they get from lolinet to make sure it's the right one. I say that because, in my case, lolinet list had two files for the Brazilian stock ROM. I went to Settings / About / Version number and downloaded the matching file. Don't know whether the other file would work the same or not. Just didn't want to risk having any issue since G8+ is somewhat new and there's not much info on solving root problems on the Internet.
Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl
carl.13 said:
Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl
Click to expand...
Click to collapse
Hello, Carl. I guess it's not possible unless there's a flaw in the security. There are some articles on the Internet about that. Google "is-there-a-way-to-root-an-android-phone-without-unlocking-the-bootloader". I can't post URLs yet.
As for Motorola devices, I was able to unlock the bootloader without problems on my G8+, last week. The only caveat, I'm my case, is that I had to wait some days for the unlock bootloader option be available under developer options. It was disabled by default in my G8+. And, yes, they're releasing bootloader unlocking codes.
THANKS!
Have anybody with a rooted device tried to get wide angle camera working in gcam ports?
Thanks.
successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google
esrd43 said:
successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google
Click to expand...
Click to collapse
magisk module debloater and also sdmaid helped with most of the bloatware, the only thing I could not remove was google files but I just deactivated it.
a really weird thing happened with the April 1st update, basically the update started automatically and it failed at 3/6 so I tought I should restart my phone and test it again, but it got stuck in bootloop and I had to reflash a rom with fastboot cmd.
I think that's because I unlocked the bootloader and rooted my phone, cause u lose the right for updates after you do that, but for some reason lenovo/moto update system goes automatically the next second u connect to the internet and fails halfway thru so u have a higher chance to ruin your phone or something, instead of denying the update from the start
so the solution I found was to try and delete "moto update service" app that I can't force stop or disable but I couldnt find it in system/app or system/priv-app, that's because the app name is "3c_ota", so deleting that with SD Maid app worked and the "update system" option in settings is reverted to a sort of default android one that lets you check manually.
Had a similiar issue. I soft bricked my phone (bootloop) and installed a stock rom from an unofficial source. The funny thing is, this version did make like 3 or 4 system upgrades to PPSI.29.65-51 without any issue. But the 1st April updated failed to install. I then flashed the official 1st april stock image with the moto rescue and smart assistant. After that, the official ROM tells me my phone is not allowed to do updates because the security of this phone is compromised and I should contact lenovo support
Those upates are kinda annoying if they don't work, I guess I'll just completey flash the phone every 6-12 months with the moto assistant.
yeah you should always have a backup rom that you can download with moto assistant or from lolinet g8 roms (https://mirrors.lolinet.com/firmware/moto/doha/official/)
I also got the same message saying that my phone is compromised ( unlocked bootloader + rooted) and it won't receive any further updates, but I just deleted the "3c_ota" app (the moto update service) which is bad cause if forces automatic updates the second u connect to internet.
I'm not going to touch any further updates or security patches until android 10, which I will attempt to flash via moto assistant
Basically the title. I received my Chinese Edge S today, so far I like it but I've barely used it. I thought I got a model with Gapps preloaded, but I was wrong (big surprise). I sideloaded Play Store, but haven't gotten much farther. Unlocking the bootloader was a little difficult, I had to factory reset, with the SIM card installed, to get "OEM Unlocking" to not be grayed out. But from there it was simple, I used the Motorola website to get the unlock code, ran it, no problem. I just followed the normal Magisk instructions: I installed the Magisk app, found the boot.img file inside the ROM download from the Lenovo Rescue and Smart Assistant, patched it with Magisk, flashed it via fastboot and I'm rooted. Once I hid Magisk, Google Pay seems to work fine (although it says NFC is not set up...I'll have to test it tomorrow for tap to pay to see if it works; when I go into NFC settings it says Google Pay is default). I'll let you all know how it goes. I also downloaded Google Assistant, but as I suspected it isn't working. I tried to sideload Gapps from Android 10, but it didn't work. I'll have to try TWRP later, or maybe wait until an Android 10 Gapps is available.
EDIT: Since I have root, is there a way install the Gapps? I found BiTGApps which has Android 11 support, but it only lists TWRP install method and there's currently no TWRP for this phone.
HopelesRomantc91 said:
Basically the title. I received my Chinese Edge S today, so far I like it but I've barely used it. I thought I got a model with Gapps preloaded, but I was wrong (big surprise). I sideloaded Play Store, but haven't gotten much farther. Unlocking the bootloader was a little difficult, I had to factory reset, with the SIM card installed, to get "OEM Unlocking" to not be grayed out. But from there it was simple, I used the Motorola website to get the unlock code, ran it, no problem. I just followed the normal Magisk instructions: I installed the Magisk app, found the boot.img file inside the ROM download from the Lenovo Rescue and Smart Assistant, patched it with Magisk, flashed it via fastboot and I'm rooted. Once I hid Magisk, Google Pay seems to work fine (although it says NFC is not set up...I'll have to test it tomorrow for tap to pay to see if it works; when I go into NFC settings it says Google Pay is default). I'll let you all know how it goes. I also downloaded Google Assistant, but as I suspected it isn't working. I tried to sideload Gapps from Android 10, but it didn't work. I'll have to try TWRP later, or maybe wait until an Android 10 Gapps is available.
EDIT: Since I have root, is there a way install the Gapps? I found BiTGApps which has Android 11 support, but it only lists TWRP install method and there's currently no TWRP for this phone.
Click to expand...
Click to collapse
Wow, thanks for all this info. That is great that you were already able to root and get Magisk on there with minimal issues. This is pretty much what I do with my phones right out of the box. Regarding that link for Gapps, I read through the start of that thread and the package is definitely what we'll probably need for this phone. But, without a working recovery at this point, I don't think there is another way to install it.
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
syncrosys said:
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
Click to expand...
Click to collapse
If you don't mind me asking, where did you purchase the phone? And where do you live?
Edit: Just saw your answer in the other thread.
CCivale said:
If you don't mind me asking, where did you purchase the phone? And where do you live?
Edit: Just saw your answer in the other thread.
Click to expand...
Click to collapse
It's worth noting that I cancelled my Giztop purchase and bought from Aliexpress instead. Can't remember if I actually said that or not.
there is twrp, it is experimental
Electimon said:
there is twrp, it is experimental
Click to expand...
Click to collapse
I couldn't find it, can you link it?
Electimon said:
there is twrp, it is experimental
Click to expand...
Click to collapse
Can you link it?
syncrosys said:
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
Click to expand...
Click to collapse
Any idea when the G100 ROM will be available?
Can you please describe the steps on how to flash the new ROM?
ktitimbo said:
Any idea when the G100 ROM will be available?
Can you please describe the steps on how to flash the new ROM?
Click to expand...
Click to collapse
I imagine it'll be available as soon as the phone itself is, just a matter of someone downloading the G100 ROM with RSA, then uploading it for the rest of us. I also imagine the process will simply be to download it, and rename it so RSA will flash it instead of the Chinese ROM for us, but that's really only speculation at this point. It may have a checksum that would make flashing a little more difficult, in which case it would be a matter of installing TWRP (once available) and then flashing that way.
@HopelesRomantc91
Can you share the URL for unlock code request?
I couldn't unlock with global website...
I think I just used the global one here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/
Hello, I have patched boot img to my moto edge S 5g Chinese version and I have magisk root ok but if I restart the motorola it is lost and I have to reinstall boot parched, do you know why?
HopelesRomantc91 said:
I imagine it'll be available as soon as the phone itself is, just a matter of someone downloading the G100 ROM with RSA, then uploading it for the rest of us. I also imagine the process will simply be to download it, and rename it so RSA will flash it instead of the Chinese ROM for us, but that's really only speculation at this point. It may have a checksum that would make flashing a little more difficult, in which case it would be a matter of installing TWRP (once available) and then flashing that way.
Click to expand...
Click to collapse
Thanks for info . İs flashing g100 rom need root device or unlocking bootloader ?
Good morning
So I've a xiaoxin pad 11 pro:
Model: tb-j706f
android version: 10
software version: tb-_706f_rf01_201229
ROM: TB-J706F_S240073_201229_ROW
kernel: 4.14.117 from 2020
Widevine: L1
And I whant to update to TB-J706F_S620150_211226_ROW. So my questions are many
-Can i use lenovo sofware to update?
-Do i need to lock or unlock oem bootloader from settings?
-Can only be done using QFIL or other softwares?
-Do i need to find out if it's region lock?
-How to backup this img, if everything goes wrong?
-Do i have to install the original chinese version, or can i just update the international one?
I see alot of threats talking about going from international to chinese, but I like to have play store and keepping widevine lv.1. Without having to do a lot of "work".
I've tried to use the OTA function, but downloads the update (just after my current version) it restart's and gets to the lenovo logo on the screen and reboots. Like a boot loop. I've to manually shutdown the tablet and it's back to normal.
After readding this forum, i still dont see a uniform way to update this device, and more importantly a easy way to do it. Can all of you help me?
- yes
- no
- yes
- even CN versions can be flashed with global rom
- you could still flash an img you download online if something wrongs happen
- it's on your own, if you have L1 with global unless you want latest updates no need to go CN, stay global.
if OTA update doesn't work maybe reset the device or even flash the newest rom available from lolinet then update with OTA.
@melones22 Thanks for the aswers.
Do you know if i download the newest global rom from lolinet, and force install, if i keep my lv1?
if you relock bootloader, likely. personally with natsafety patch + hde etc still l3
be absolute sure that you didn’t modified anything else than flashing before relocking
front3 said:
Good morning
So I've a xiaoxin pad 11 pro:
Model: tb-j706f
android version: 10
software version: tb-_706f_rf01_201229
ROM: TB-J706F_S240073_201229_ROW
kernel: 4.14.117 from 2020
Widevine: L1
And I whant to update to TB-J706F_S620150_211226_ROW. So my questions are many
-Can i use lenovo sofware to update?
Click to expand...
Click to collapse
Yes, but I nver used it
front3 said:
-Do i need to lock or unlock oem bootloader from settings?
Click to expand...
Click to collapse
If you flash stock ROMs CN or Global you do NOT need to unlock bootloader
front3 said:
-Can only be done using QFIL or other softwares?
Click to expand...
Click to collapse
To flash a ROM you can use QFIL, I never used Lenovo softwaare so I am not sure if you can flash form there only last version or if you have a choice.
Normally you should not be required to use QFIL and you should be able to update with OTA updates.
front3 said:
-Do i need to find out if it's region lock?
Click to expand...
Click to collapse
If you are having problems updating I guess it doesn't hurt finding that out.
front3 said:
-How to backup this img, if everything goes wrong?
Click to expand...
Click to collapse
You should backup QCN with QFIL and all partitions (you can probably exclude vendor and userdata) with QFIL or edl, there is a guide for both methods (I use edl) https://forum.xda-developers.com/t/two-ways-to-backup-tb-j706f-without-unlocking-bootloader.4402799/
front3 said:
-Do i have to install the original chinese version, or can i just update the international one?
Click to expand...
Click to collapse
You should be able to update your global ROM but since you are having problems I don't exclude you might need to go back to CN ROM before flashing again the Global ROM.
front3 said:
I see alot of threats talking about going from international to chinese, but I like to have play store and keepping widevine lv.1. Without having to do a lot of "work".
I've tried to use the OTA function, but downloads the update (just after my current version) it restart's and gets to the lenovo logo on the screen and reboots. Like a boot loop. I've to manually shutdown the tablet and it's back to normal.
After readding this forum, i still dont see a uniform way to update this device, and more importantly a easy way to do it. Can all of you help me?
Click to expand...
Click to collapse
I am not sure what's the problem with your OTA update.
I would suggest to:
Backup your QCN and all partitions first
Open your QCN with QCNView and check the region in NV Item 6858
If your region is 02 is Global and OTA update should work, so maybe try a factory reset and see if after OTA update works.
If it's 00 (region unlocked) or 01 (China) that might be the reason OTA updates are not working.
Edit
I read again the version you have now and it's quite old, that probably does not have any region lock.
In the one tablet I had from the shop with Chinese ROM I flashed TB-J706F_S250260_210804_ROW, that set it as global region and then from that I run OTA updates.
So I think you should backup as I said before and then flash TB-J706F_S250260_210804_ROW, make sure to select the right settings in QFIL and NEVER check "Reset state machine".
MrCrayon said:
Yes, but I nver used it
If you flash stock ROMs CN or Global you do NOT need to unlock bootloader
To flash a ROM you can use QFIL, I never used Lenovo softwaare so I am not sure if you can flash form there only last version or if you have a choice.
Normally you should not be required to use QFIL and you should be able to update with OTA updates.
If you are having problems updating I guess it doesn't hurt finding that out.
You should backup QCN with QFIL and all partitions (you can probably exclude vendor and userdata) with QFIL or edl, there is a guide for both methods (I use edl) https://forum.xda-developers.com/t/two-ways-to-backup-tb-j706f-without-unlocking-bootloader.4402799/
You should be able to update your global ROM but since you are having problems I don't exclude you might need to go back to CN ROM before flashing again the Global ROM.
I am not sure what's the problem with your OTA update.
I would suggest to:
Backup your QCN and all partitions first
Open your QCN with QCNView and check the region in NV Item 6858
If your region is 02 is Global and OTA update should work, so maybe try a factory reset and see if after OTA update works.
If it's 00 (region unlocked) or 01 (China) that might be the reason OTA updates are not working.
Edit
I read again the version you have now and it's quite old, that probably does not have any region lock.
In the one tablet I had from the shop with Chinese ROM I flashed TB-J706F_S250260_210804_ROW, that set it as global region and then from that I run OTA updates.
So I think you should backup as I said before and then flash TB-J706F_S250260_210804_ROW, make sure to select the right settings in QFIL and NEVER check "Reset state machine".
Click to expand...
Click to collapse
Hi Mr. Crayon,
Is there any guide in how to do as what you mentioned above ? I'm quite new to this 'manual update' and still learning. Would really appreciate your help on this. My Xiaoxin Pad Pro 2020 (TB-J706F_S268018_210731_ROW) is still running on android 10 and my device is not certified by play protect. T.T
Hello.
Thanks @MrCrayon, but i never has able to use qfil to backup my device. To complicated for me. But thanks for the help.
So what i did to update my tablet. After feeling the same way @shaoki92 , i just tried to use lenovo tools. And... puff... update done.
No problems what so ever,
Did not lose L1
And did not have to mess with bootloader or region lock.
But i understand that i took a big risk. The tablet could've become just a paper weight. But until now working fine. With new android and everything.
front3 said:
Hello.
Thanks @MrCrayon, but i never has able to use qfil to backup my device. To complicated for me. But thanks for the help.
So what i did to update my tablet. After feeling the same way @shaoki92 , i just tried to use lenovo tools. And... puff... update done.
No problems what so ever,
Did not lose L1
And did not have to mess with bootloader or region lock.
But i understand that i took a big risk. The tablet could've become just a paper weight. But until now working fine. With new android and everything.
Click to expand...
Click to collapse
Hi front3,
May i ask how do you update using lenovo tools ? Thanks
Im no expert that so ever. But i can tell you that i did.
Install lenovo assistance, on windows.
Used the charging cable of the tablet to connect to pc.
Launch the app
Connect to the device via app
(And i dont remember now, but i think its recue my device, and update, inside the app)
The app gives you a warning about using the tool on CH devices, and i took the risk.
Check the firmware version that the app gives you, and what it the lastest that has been deploid. Just to be sure. And do it if you dont mind taking the risk, do it.
In my case, the version that the app recomended has not on lolinet at that time. It only show up there, weeks later. But because the app connects to lenovo servers directly, i think it was safe.
Be careful because you can brick the device. And like @MrCrayon explained, i had one very old firmware, so xiaoxin didnt have the same "security" feactures has the newer devices. So maybe that is why it worked.