My OUKITEL U7 Pro NVRam formatted after an update. It lost the IMEI and Barcode and Mac address.
I have found tool to recover them. However one thing that I am not sure of is what I should put in the Barcode. If I open the phone and remove the battery, I see a SN number there is that my barcode?
Also my current version is 2.7 and when I check for wireless update, it said my phone is up to date. However I know the latest version is currently 2.8... will the formatted NVRam prevent my update?
I have tool to edit the NVRam, I just need to know what to put in there. Please help me
One more problem for this phone is I have found that the Caller ID app (com.android.tools.callassistant) that is pre-installed in the official rom is downloading and keep asking me to install random apps like DU battery saver, Apus launcher etc... I have to disable it in app setting to make it stop. Does anyone else has this problem too?
spy007z said:
One more problem for this phone is I have found that the Caller ID app (com.android.tools.callassistant) that is pre-installed in the official rom is downloading and keep asking me to install random apps like DU battery saver, Apus launcher etc... I have to disable it in app setting to make it stop. Does anyone else has this problem too?
Click to expand...
Click to collapse
Same here with Blackview BV2000S I removed this from SYSTEM.IMG and flashed that new IMG to remove this crap.
Just flash the phone taking serious note of the version of DDR that it comes with and as it appears, you have the DDR2 version. So download the latest version of your ROM on needrom.com and flash with SPMDT which you'll find at the same site and instructions on how to flash. Do let me know if you encounter any problems. Cheers!
I have already tried what you suggested before posting. However the problem is that com.android.tools.callassistant is install in the official rom and problem will not be fixed by re-flashing the rom. Temp cure is to install firewall and disable com.android.tools.callassistant. Long term cure is to root the device then remove com.android.tools.callassistant from the rom.
I am using the temp cure currently and is working for me so far. I will never touch another OUKITEL product ever again. Who will put a adware in an official rom?
Based on my experiences setting up this phone (Samsung SM-A500W ie A5) I thought I'd share what worked for me for the Canadians out there as there isn't too much info. Originally started with a stock Rogers ROM on Android 5.0.2 (Lollipop) with baseband A500WVLU1A0J3.
To root, follow instructions here: http://forum.xda-developers.com/samsung-a-series/help/samsung-sm-a500w-t3333196
KingRoot followed by SuperSU Me worked perfectly and afterwards it was not necessary to do anything (like remove or disable KingRoot applications, etc). This allowed me to install AdAway and other root-only apps.
Installing a custom recovery worked multiple ways - see here for twrp: http://forum.xda-developers.com/samsung-a-series/general/to-port-twrp-to-galaxy-a5-a500fu-t3150843
I got TWRP (both 2.x and 3.x versions) to install using both Flashify method and Odin.
I also wanted to install the Xposed Framework on there and long story short ended up soft bricking the phone (oops - was trying to increase free space on System ROM and deleted stuff I shouldn't have). Stock ROMs for this phone can be found here: http://www.sammobile.com/firmwares/database/SM-A500W/ or here: https://samsung-firmware.org/model/SM-A500W/
I did manage to get Xposed Framework installed without deodexed ROM using instructions here: http://forum.xda-developers.com/samsung-a-series/general/tuto-xposed-odex-rom-yes-knox-0x0-t3316688
I used Option 1 (knox tripped since i didn't care about warranty) and it worked perfectly. Had some trouble clearing 500MB on System ROM as noted but with deleting apps I could install later or didn't want managed to get it there. Don't delete Google Play or Play Services!!
Hopefully this helps some of you.
Thanks man! Hopefully someone comes out with a custom ROM or this device!
Looking at the TWRP, there doesn't seem to be a specific mention for the A500W variant. Which version were you able to successfully flash onto your device?
I can't recall exactly which one I installed. I am pretty sure the only difference between the models (F/FU/H/L, etc) is the countries in which they are released. The W variant is the Canadian one, thus has the Canadian radio band support. I was thinking of trying to install one of the ROMS and see if it works, as I am not currently using the phone for cellular service.
Ah safetynet, the thorn in the side of every technical android user who wants to use Android Pay.
It's even worse on a xiaomi device, because once you've been granted a bootloader unlock after waiting for days, you don't want to re-lock it for fear of locking yourself out of the device and having to wait another 30 days before you can get a new unlock permission!
There is a lot of old information around about hiding root, custom kernels, installing things in particular orders and I'm pretty sure I've tried them all - including compiling kernels from scratch with a few different versions of the unlocked bootloader hiding patch.... never getting past the dreaded CTS Mismatch
But all of a sudden I happened on a little known secret found by @kyasu that the build fingerprint is also checked : https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Also, conveniently, Magisk (since v9) patches the ro.boot.verifiedbootstate and related props that SafetyNet checks.
This now gives us two options to enable safetynet regardless of bootloader state.
You will need either a kernel with bootloader state hidden OR magisk, as well as a method of changing the build fingerprint.
This also assumes you've got TWRP installed and are comfortable using it.
Tested on Mi5 Lineage OS 14.1-20170206-NIGHTLY-gemini and various xiamoi.eu 7.2.X and 7.3.X versions:
NOTE: Magisk Hide on MIUI currently does not work (21st July 2017)
This has been widely reported and there are a number of open issues:
https://github.com/topjohnwu/Magisk/issues?utf8=✓&q=is:issue is:open miui
A fix may have been found, not ready to test however:
https://github.com/topjohnwu/Magisk/issues/298#issuecomment-316687923
Magisk:
Remove any previous root, usually this can be done by simply dirty flashing your current rom in twrp.
From TWRP install Magisk v13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Restart and Magisk Manager app should be installed.
Hit the test safetynet button in Magisk Manager, if it passes stop here! Latest lineage roms don't need my magisk fingerprint module anymore, they just work.
Otherwise, download this magisk module on your phone: https://gitlab.com/alelec/magisk-ge...2bbf9dc8/magisk-gemini-safetynet-props-v3.zip
In Magisk Manager, go to modules and install the magisk-gemini-safetynet-props zip just downloaded. It should prompt to restart to enable module, do so.
After restart, fire up Magisk Manager and "tap to start SafetyNet check", fingers crossed it comes up Green!
Note: After each rom update you will need to reinstall Magisk in twrp, but the safetynet enabling module above should stick just fine and not need reinstall.
Custom Kernel:
I don't test this as often, as I prefer the Magisk method, however this is an option for people who don't want any kind of root on their phones.
I also don't maintain any patched kernel for miui based roms as the one's I've tried are just too buggy.
Remove any previous root, usually this can be done by simply dirty flashing your current rom in twrp.
Install gemini-safetynetpass-stable-fingerprint-20170217.zip
this package is based on gemini-safetynetpass-20170213.zip by @kyasu but only changes the build prop fingerprint, the old custom kernel has been removed:
Install a patched kernel, you can either use my autobuild of a patched latest LineageOS kernel for Mi5 (includes fingerprint fix):
https://gitlab.com/alelec/android_kernel_xiaomi_msm8996/tags (LineageOS-gemini-safetynet-kernel_XXXXXX.zip links)
or recent DragonXia kernels appear to be patched
https://forum.xda-developers.com/mi-5/development/kernel-brand-kernel-cm13-alpha-1-0-t3480663 (LineageOS)
https://forum.xda-developers.com/mi-5/development/kernel-dragonxia-kernel-v1-0-t3546619 (MIUI)
Note: Both the kernel and fingerprint zip above will need to be re-installed after each rom update.
On a related note, if you want to use Android Pay on MIUI based roms, make sure the HCE wallet configuration and permissions are set correctly.
See the following for more details: http://en.miui.com/thread-405166-1-1.html
Once you unlock it once, you can unlock it again without waiting. I just unlocked and relocked my Mi5 about 3 times in a couple days.
Sent from my MI 5 using Tapatalk
Oh really? Wow, nothing I've read anywhere in the last few weeks has said that before, certainly simplifies things!
Do non stock kernels boot on a locked bootloader though? They didn't on my previous Sony.
coronafire said:
Oh really? Wow, nothing I've read anywhere in the last few weeks has said that before, certainly simplifies things!
Do non stock kernels boot on a locked bootloader though? They didn't on my previous Sony.
Click to expand...
Click to collapse
It does make it easy. I initially unlocked my bootloader to flash the global stable, then used mi flash to flash the ROM and relock my bootloader. I wasn't happy with the stable ROM, so I went back into the mi unlock tool, unlocked again, and flashed the dev ROM and relocked Then I see 8.2 is coming soon, so I went back to mi unlock and unlocked yet again so I can flash the new 8.2 when it comes out.
I'm not sure on kernels, haven't messed with them on Xiaomi devices.
Sent from my MI 5 using Tapatalk
Did anyone try this patch on MIUI?
Edit: Just tried on MIUI v7.2.9 Global Dev. CTS profile and Basic Integrity check both fails.... What a bummer...
the_poolee said:
Did anyone try this patch on MIUI?
Edit: Just tried on MIUI v7.2.9 Global Dev. CTS profile and Basic Integrity check both fails.... What a bummer...
Click to expand...
Click to collapse
Drats. If basic integrity is failing that's something else triggering the issue. Before I changed the fingerprint I only had cts failing, basic was usually fine. Sometimes a replacement kernel would cause it to fail basic, but I never narrowed down exactly what the cause was.
Works on LOS. Anyway my bank doesn't support android pay yet.
Ulver said:
It does make it easy. I initially unlocked my bootloader to flash the global stable, then used mi flash to flash the ROM and relock my bootloader. I wasn't happy with the stable ROM, so I went back into the mi unlock tool, unlocked again, and flashed the dev ROM and relocked Then I see 8.2 is coming soon, so I went back to mi unlock and unlocked yet again so I can flash the new 8.2 when it comes out.
Click to expand...
Click to collapse
Looked into it some more to confirm - I'm quite sure you can't re-lock the bootloader if using anything that's not an official xiaomi rom, ie if using lineage, or even the xiaomi.eu rom, you can't lock bootloader without having a bootloop.
And yeah, I've confimed this method doesn't work on xiaomi.eu rom 7.1.20 or 7.2.16 on mi5. It gets both failed basic integritry and failed cts profile match.
I've also tried on Global Stable 8.1.4.0 with unlocked bootloader and had no luck at all, same error.
This was a clean install, factory wipe, install magisk v11.1. Initially the check couldn't work at all, I had to get google play services updated for anything to work. Then the check operates, but fails on both counts.
I passed safety net on 8.1.2.0 global stable, but failed to add a card in Android Pay. I'm hoping 8.2 works.
Sent from my MI 5 using Tapatalk
Ulver said:
I passed safety net on 8.1.2.0 global stable, but failed to add a card in Android Pay. I'm hoping 8.2 works.
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
As described by @Ulver if you're on official builds, you should be able to re-lock the bootloader and avoid this issue (although without root I guess).
Aside from that, you definitely shouldn't need the zip I made for the build prop change, as you'll already have a stable build fingerprint
It turns out there's lots of versions of official rom that don't pass safetynet even when cleanly flashed with locked bootloader - xiaomi themselves keep breaking it!
A little search finds lots of references, such as this entire thread, and this post in particular: http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=273319&pid=7515203
This certainly complicates things....
Turns out you can't always re-unlock....
To test more thoroughly I decided to flashtool wipe and lock my mi5 to stable release that's reported to pass safetynet; global_images_V8.0.2.0.MAAMIDG
My plan is to verify that it passed when locked (it did), then unlock and just install magisk to see if that worked to hide.
Well, MiUnlock has told me I can't unlock, I logged back into unlock web site and it now says my unlock request is rejected (on same account as I originally unlocked on). So now I have a locked device on global stable and have to wait for re-application to unlock.
FWIW I then allowed MIUI to OTA update itself to 8.1.2.0(MAAMIDI) and then safetynet helper originally told me no, fail on both basic and cts.
Ran it a couple more times though and now it's passing. go figure... safetynet is somewhat unreliable.
tl;dr don't re-lock your phone assuming you'll be able to immediately re-unlock it, it clearly works some of the time, not always though.
Good news, I've got SafetyNet pass on xiaomi.eu (MIUI) rom with unlocked bootloader
In the end it's basically the same as the original LOS method except that as we've all seen earlier Magisk v11.1 isn't working for MIUI.
This win was achieved with Magisk v9 and phh-superuser-magisk-r266-2 with the current Magisk Manager (4.2.6)
As per the screenshot I'm running xiaomi.eu MUIU 8.3 7.2.24 in Mi5
My procedure was:
* dirty flash rom to clean up prior attempts (Install) xiaomi.eu_multi_MI5_7.2.24_v8-7.0.zip
* Install gemini-safetynetpass-stable-fingerprint-20170217.zip
* Install Magisk-v9.zip
* Install phh-superuser-magisk-r266-2.zip
* Reboot.
Simple as that, Magisk Manager shows SafetyNet passing (after asking for root privs on first launch)
I've added a new card in Android Pay, haven't tested at a terminal yet though.
If anyone's interested I previously got SafetyNet passing on MIUI with a custom kernel instead of Magisk, this gave SafetyNet green without any kind of root.
The problem with custom kernel's at this stage is the capacitive buttons (back and app switch) have reduced sensitivity / only work well when the phone is charging. AFAIK this is only really a problem on phones with LGD lcd's (what I have), the other ones might work fine.
If anyone wants to try my kernel instead let me know and I'll share it, I found it to be a bit flaky though.
@up:
For me not working.. SafetyNet test always have CTS false.. I tried clean install and for now it's not works.
rafix96 said:
@up:
For me not working.. SafetyNet test always have CTS false.. I tried clean install and for now it's not works.
Click to expand...
Click to collapse
Which version of which rom did you try?
coronafire said:
Which version of which rom did you try?
Click to expand...
Click to collapse
I would definitely would like to confirm this on the latest miui official global dev
First i try this on 7.2.24 xiaomi.eu later i updated MIUI to 7.2.3 and unfortunately it does not working too...
rafix96 said:
First i try this on 7.2.24 xiaomi.eu later i updated MIUI to 7.2.3 and unfortunately it does not working too...
Click to expand...
Click to collapse
That's annoying, 7.2.24 is what works for me. It's been my daily driver since, and I've used android pay at a terminal no worries.
Do you definitely have Magisk v9 and phh-superuser-magisk-r266-2.zip ?
Magisk v11 cannot be installed else a dirty flash will be needed.
Oh, I just remembered I've also installed the 'phh's SuperUser' app from Play Store. This is probably needed
After that I opened Magisk Manager, which asked for root permissions the first time (which has to be granted).
@coronafire
Yes i tried everything but i have another one idea, when i come back to home i did MiFlash and then install eu 7.2.24 maybe will work.
Wysłane z mojego MI 5 przy użyciu Tapatalka
basically, if you don't need root, just flash
the latest zip in the following link (by kyasu)
https://www.androidfilehost.com/?w=files&flid=149919
will pass safetynet without locked bootloader. As they latest kernel is 2 weeks old, please consider there may be some drawback in flashing an old kernel to latest LOS build. By the way, would kyasu please update the file or let us know is there is any easy way to patch on our own?
hklam0 said:
basically, if you don't need root, just flash
the latest zip in the following link (by kyasu)
https://www.androidfilehost.com/?w=files&flid=149919
will pass safetynet without locked bootloader. As they latest kernel is 2 weeks old, please consider there may be some drawback in flashing an old kernel to latest LOS build. By the way, would kyasu please update the file or let us know is there is any easy way to patch on our own?
Click to expand...
Click to collapse
Just to note, this is only for LineageOS, not MIUI.
Personally I find it easier to not need to replace the kernel and just install magisk, if root isn't wanted it can be disabled in the magisk app.
But yes it's true you can replace the kernel with a patched one, avoiding installing any kind of root.
I've experimented with this quite a bit myself, however to update it requires at a minimum applying a patch/commit to a fork of the kernel source you're starting with and compiling it.
I've got a fork of the MIUI kernel from @Shaky156 with the appropriate patch:
https://github.com/andrewleech/Mi5-...mmit/66cbe734eb15d2508a5c80157a8af38d59373535
and example build script:
https://github.com/andrewleech/Mi5-MIUI8-Nougat-Kernel/blob/master/build.sh
Or there's the original patch by @Sultanxda which usually works as well, I did test this on a LineageOS kernel but this is pretty out of date too by now, and I started from a different forked kernel anyway.
https://github.com/andrewleech/andr...mmit/f8314c10146971979ad26c881be9bd17603c1e7d
Downloading through the website doesn't work, because I recently updated my firmware through OTA and I bought my OP 7T Pro in Shanghai. I am trying to root my device by using this tutorial:
watch?v=VGjYuvoBpPA <-- YouTube URL
However, I am not sure if this is the only way or if there are better ways of rooter OP 7T Pro devices without needing the payload data as described in the YouTube video. Any help is appreciated!
S1nPur1ty said:
Downloading through the website doesn't work, because I recently updated my firmware through OTA and I bought my OP 7T Pro in Shanghai. I am trying to root my device by using this tutorial:
watch?v=VGjYuvoBpPA <-- YouTube URL
However, I am not sure if this is the only way or if there are better ways of rooter OP 7T Pro devices without needing the payload data as described in the YouTube video. Any help is appreciated!
Click to expand...
Click to collapse
You basically have 3 choices to acquire the boot.img:
1. Payload Dumper
2. TWRP and adb
3. Download the stock boot.img for your version of Hydrogen OS (if it exists)
There are "auto root" tools out there, but not sure how they are. I personally used #2, but payload Dumper works quite well too.
Pretty sure the auto root tool on here works on any version of ROMs. But keep in mind that when you wanna perform a OTA update after root using the restore image method, the auto tool backed up the extracted stock boot image on our pc rather than letting Magisk does its normal job and store in our phone the way Magisk wants. What I mean is that we essentially lose root first and need to re-run the auto tool after each OTA update. I'm just lazy to get perform the normal methods, so I just double click on that auto tool each time and let it does its job each time I lose root after each OTA update. I remember it actually worked flawlessly and let Magisk back up the stock boot image at first, but then after some OTAs later when I messed up and reset factory settings in recovery and had to re-root my phone using the tool, magisk acts weird and stopped storing a back up boot image in the phone.
S1nPur1ty said:
Downloading through the website doesn't work, because I recently updated my firmware through OTA and I bought my OP 7T Pro in Shanghai. I am trying to root my device by using this tutorial:
watch?v=VGjYuvoBpPA <-- YouTube URL
However, I am not sure if this is the only way or if there are better ways of rooter OP 7T Pro devices without needing the payload data as described in the YouTube video. Any help is appreciated!
Click to expand...
Click to collapse
I did eventually unbrick my device, because for some reason I ended up not being able to call anymore. When unbricking, I installed the EU version and everything seems to be working fine now. However, I regret for not backing up the root data; because the Chinese version has Oneplus Roaming option where you can use internet in any country without having the need for any sim card. Also, you can record any conversations without any third party apps needed, so it's unfortunate. I wish I could install the Chinese version again, because they really were a big help in the past.
S1nPur1ty said:
I did eventually unbrick my device, because for some reason I ended up not being able to call anymore. When unbricking, I installed the EU version and everything seems to be working fine now. However, I regret for not backing up the root data; because the Chinese version has Oneplus Roaming option where you can use internet in any country without having the need for any sim card. Also, you can record any conversations without any third party apps needed, so it's unfortunate. I wish I could install the Chinese version again, because they really were a big help in the past.
Click to expand...
Click to collapse
I'm Chinese, and I can help you to download last version H2OS.
According to the people on reddit it is because I have debloated my phone. I also tried to install the Pixel Experience Plus custom rom at one point but it didn't work, I did reinstall the stock recovery an relocked the bootloader after that.
I did factory reset it and even flashed it with an ozip file still no update.
also found an ofp file for the Android 11 update but relme flash tool wouldn't work with it.
Is there any other way to manually update it or force it to update?
Thanks in advance.
Do you really want it?
I think it's a bloatware dud.
The "security" is not needed and comes at a stiff price as you will see if you load it.
Scoped storage sucks.
Rule #1, if your OS is running fast, stable and fulfilling its mission... let it be.
You do make a good point.
But if it is possible and I don't like it I can always reverse to Android 10.
At this point I just want to try it out and try the Pixel Experience rom.
If it isn't, well both my phone and I will survive.
thephone.geek said:
You do make a good point.
But if it is possible and I don't like it I can always reverse to Android 10.
At this point I just want to try it out and try the Pixel Experience rom.
If it isn't, well both my phone and I will survive.
Click to expand...
Click to collapse
You can go back... as long as it doesn't update the boot loader version too.
As a Samsung user I'm all too aware of that trick.
I would investigate what advantages R has over Q that would benefit you. Scoped storage isn't fully implemented on Q apparently and seems to run as well maybe better than Pie. In Q it's scoped storage in all it's blazing cpu cycle sucking glory.
Is there anyway to do it using adb?
I got Realme 7 Pro from Amazon Warehouse with somehow broken security - figerprint scanner didn't work and the phone didn't want update itself thru OTA, even with relocked bootloader and when connected via VPN to Germany, Italy etc. It actually updated to Android 11 C23 using OTA when I changed phone's region to Singapore using the service code. Then I was still able to go back to Android 10 using OZIP file (like described in this guide), or it was also possible to flash individual img files from fastboot using adb as described here. But OTA updates and fingerprint scanner were still broken until I sent the phone to Realme service and they reflashed it completely within warranty - after that fingerprint sensor works properly and I got OTA update to Android 11 C26 right after connecting to Germany over VPN.