Hi well, when removing the pixel experience A12 rom and putting miui through miflash, I searched for wifis and called "nvram warning err 0x10" and managed to fix it by flashing the rom "Redmi Note 8 Pro ENG Firmware (Engineering Rom)" by typing the mac address manually (I took it out of the registry of my router) but I had a doubt, the imei is intact, the baseband also, the mobile model, everything seems to be correct, I just lost the mac address of the wifi that gave me a random and showed that error.
With everything I am telling you, have I been able to lose any function of the device? for example nfc, quality of the cameras or something important that I forgot, or I simply lost the mac address of the wifi and when fixing it it is as if nothing had happened?
I am concerned that something is corrupted in the background on the system and I don't know and in the future I have a brick when updating or anything else.
ps: factory reset phone from settings by reconfiguring google account and at this time it does not show nvram error.
Enteoria is all good, or have I been able to erase something else without my knowing it?
Greetings and thank you very much
The worst thing that would happen is losing your sensor calibration data (Which requires /persist and /nvdata to be corrupted too) which you can check by manually testing them using CPU-Z or MIUI's own testing app.
You said that your IMEI,Baseband etc. is intact so you should be good.
Also remember to back up your nvcfg,nvdata,nvram,persist,protect1 and protect2 partition.(use adb or dd to backup don't use TWRP)
Related
Hi,
I've been trying to access my phone, or at least the storage. All I need is to collect the data (pictures, documents, appdata etc.), then I can just wipe everything. I'd really appreciate some help!
My problem is that I cracked my screen, and it took a couple of months to get the right replacement part from China. When I fixed the phone I restarted it, but had forgotten the password pattern (it's long and complicated). There is no "forgot password" function on ColorOS for some reason, so there's no way I can reset it.
Info:
- Oppo Find 7 International
- Stock ColorOS 1.2.x (Android 4.3)
- NOT rooted
- Suspect USB-debugging is disabled (since I cannot connect through ADB)
- ColorOS Recovery ver 1.0
I've tried connecting it through ADB from Ubuntu, but it doesn't find the phone.
I've tried finding bugs or glitches to bypass password pattern. No luck.
I've tried installing bypass tools via ColorOS Recovery from SD card, but I get "Installation Failed".
My last hope is to download forensic software to breach into the phone. I've also seen people using development boards and send commands via JTAG. I have Raspberry Pi and Redboard (Arduino from Sparkfun) - in case I can use those. I am not afraid to do some experimental stuff on the device, I just don't want to lose the data on it. Device wipe is out of the question.
Perhaps you know a way to at least get access to the storage? It is not encrypted. I can install from storage, so I can see all folders etc. in recovery. So I guess it have to be possible to extract the data somehow.
Ok so essentially im trying to spoof my mac address on my newly purchased verizon HTC 10 its a great phone but of course i got caught up in how pretty the phone was and purchased it without realizing that Verizon prevents you from unlocking the bootloader ( cant say i'm surprised it is verizon after all ) no big deal so i purchased sunshine to get s-off which worked very well, flashed twrp recovery and easily installed viper rom, after installing all my apps, i thought that surely spoofing my mac would be no problem, after all i spoofed the mac on my jailbroken iphone with a simple terminal command that modifed the mac in NVRAM. Then the great train wreak began, first i started with the play store apps which would spoof the mac however they failed to authenticate with any network that had any kind of security so that was a no-go, then i used busy-box commands to try and attempt to spoof the mac same issue failed to authenticate, so then i just figured id go into the filesystem and modify some files, however every tutorial i could find pointed to a /efs directory which was not present at all or a /persist directory which was also not present there were a few other directories none of which i could find. Eventually i just got so pissed i took the wifi firmware files ( and if anyone was wondering the model of the chip is a bcm 4359 which is apparently a really good chip ) and went into a hex editor and found macaddr=%2 and changed %2 to equal the mac im trying to spoof. Of course when i applied the modified firmware files the wifi failed to turn on at all, so i thought maybe its the viper rom, perhaps it lacks directorys that a stock 6.0.1 rom does, but after restoring my backup its the exact same root directory as viper, what i don't understand is why its so easy too spoof a mac address on an IOS DEVICE, but on an open source operating system such as android its giving me this much trouble, maybe i'm just stupid and missing something really obvious but surly it cant be this difficult to spoof a mac on android, any help would be greatly appreciated.
Hi, I did the imei operation with octoplus. But I get the error in the download mode is shown in the pictures. Why stems. The firmware does not update.
[IMG="https://eksiup.com/p/hj237254vfnk"]
[IMG="https://eksiup.com/p/zr237258pjnd"]
Nexus 5x imei repair
Most here won't discuss imei repair/replacement due to issues with the legality of the subject.
I borked my imei attempting to back it up with miracle box, so I feel your pain.
Our phone doesn't like to have it's internals probed by "smart programs".
Every time a N5x gets bricked, it's because someone tried to take the easy way out & use a frontend to a program that actually works on it's own.
You're gonna have to start by erasing modemst1 and modemst2 from fastboot.
See if that fixes the problem.
Activate diagnostic mode by opening your terminal emulator/using adb and do
setprop sys.usb.config diag,adb
Now you can use qfil/qpst to make a backup .qcn to hex edit your imei (converted to hex) into.
Remove anything that shouldn't be there, like a bunch of random data that looks like it could be other imei numbers... Whatever caused your phone to get so confused that it couldn't decide what the imei was.
Use qfil/qpst to restore your edited .qcn (you'll probably have to flash multiple times to make it stick), and bam!
You're golden, Ponyboy
This ONLY fixes the lack of imei.
Anything else that's missing will have to be added manually.
I don't know how, but persist partition apparently got damaged in my device after installing of custom ROM. So would anybody dump that partition and send to me?
Here is the way you can get it: boot into TWRP -> Advanced -> Terminal (or in rooted adb shell) run "dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img". The .img file will emerge in your root directory.
Upd: flashing other device's persist.img can't solve my problem, so I really don't know what to do
By the way my problem is missing of all sensors data (accelerometer, light sensor, proximity sensor...) after installing Pixel Dust ROM. I have flashed stock Q and P firmwares by several times, but it made no changes. However my persist partition looks fine to compare the one from device with working sensors
You can't just take someones persist. How do you know it's not hardware damage since sensors can fail after all? if you use someones persist, your using all their unique data. Have you tried downgrading to Android 9?
djared704 said:
You can't just take someones persist. How do you know it's not hardware damage since sensors can fail after all? if you use someones persist, your using all their unique data. Have you tried downgrading to Android 9?
Click to expand...
Click to collapse
Yes, I tried to downgrade to Pie, even to stock 7.1.2 image, but it still not got any use. And the strange fact is, that sometimes I can get data from proximity, light and pressure sensors, but it can suddenly disappear during one up time (I mean between reboots), and it means what at least two modules responsible for that sensors (TMD4903 and BMP2805) still can work fine... I guess
I assume, that weird behaviour can be related to some data which keeps untouchable during wipes or any firmware upgrade. Some data like PIN or something, and it were corrupted
Hello,
while attempting to root my Blackview BV6000s (containing Mediatek MT6737T chip) I lost both IMEI's. Although I succeeded in rooting the phone, I was not able to restore the IMEI.
1) If I use Mediatek Engineering apk, when I send the string "AT+ EGMR=1,7,"IMEI_1″ I receive the error "This Command is not allowed in user build". I have read a lot of forum posts where they say to put a blank after "AT+", but it doesn't work placing the blank in any place: before or after the "+", or without blank at all. Always the same result: "This Command is not allowed in user build". I have tried all the versions of MTK engineering apk that I found inside and outside google play store
2) It is not possible to get any connection with "MTK Droid tool". Same result with MauiMETA
3) With SN write tool, when I plug the USB cable the phone powers on and the Blackview logo is shown, and after few seconds a red "FAIL" message is shown by the SN writer tool. It seems that the phone is not able to enter in "meta mode"
4) I have generated an IMEI file named "MP0B_001" and I have copied it in the right place with the root browser, but after the reboot the IMEI are still empty. I remark that when I try to set the write permissions, the root browses pops up an error message saying that the file system doesn't allow changing the permissions of the files. Then I packed the MP0B_001 in a zip file and I installed it with the TWRP recovery. The installation with TWRP doesn't show any error, but then after the reboot the IMEI are still invalid (null). Note: in ALL the posts that describe how to install the MP0B_001, they indicate /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 as the path where the file is stored. But in my phone the path is different, and precisely it is /nvdata/md/NVRAM/NVD_IMEI/MP0B_001. This makes me think that nobody have tried to apply this procedure to BV6000s. Anyhow, I tried to pack and install the zip with both paths, with the same unsuccessful result.
5) The only way I could write something in the 2 IMEI's is with Chamelephon. However there must be an incompatibility between Chamelephon and my phone. In fact, after applying the new IMEI's and rebooting, when reading the IMEI I find random strings instead of null strings. What is odd is that one of the 2 SIM cards succeeds in connecting with to the mobile networks and receive calls and SMS, even with this corrupted IMEI, while the other SIM still gives "invalid IMEI" error. I tried to find newer versions of Chameleon, but it seems that only version 1.0 exists
6) I tried to install all the ROM's that are compatible with MT6737T but the results of attempts 1-5 are the same.
In conclusion, it seems quite impossible to fix the IMEI. I have the impression that nobody tried to fix the IMEI on this specific phone, or that the producer has decided to "punish" whoever tries to root the phone, by preventing the repairing the IMEI. All the forum posts and guides, on which I based the attempts that I have described in this post, are not referring explicitly to BV6000s. Before resigning myself, I decided to create this post. Maybe it could be helpful also to other persons, if a solution exists and is described here.
Best regards
I have solved the issue and I am reporting here the solution for the benefit of those who should face the same problem.
I had to remove the encryption from the phone. I have installed the "no verity" package (no-verity-opt-encrypt-6.1.zip) with TWRP recovery and formatted the data section. This made necessary to reinstall all the applications from scratch. Further information: https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
Then I used ghost phone (from google play store) to fix the IMEI; anyway after removing the encryption also Chamelephon was working.
***
Now I am in doubt whether I should restore the encryption.
If I restore the encryption, I am afraid that this could cause the loss of IMEI's again, or re-introduce some other annoying restrictions.
If I leave it not encrypted, I am afraid that my phone is more vulnerable to rootkits and similar malwares.