Recently when downgrading my phone to an earlier version of Android, dummy me accidentally formatted the entire phone, which took the entire NVRAM etc with it. Now I managed to restore the IMEI numbers, but the notch, navigation bar and WiFi/Bluetooth MAC addresses are completely messed up (see pictures for display stuff, the others are diagnosed by NVRAM error 0x10). Upon some googling people suggest to use
Code:
adb shell wm overscan a,b,c,d
to fix navigation- and statusbar, but that's not exactly a fix in my book. So I'm wondering if there's another way, maybe even editing something in NVRAM (I checked but couldn't find much) or if I could do something with ADB or 4A Settings Database Editor. I'm willing to try anything really as I kind of like this phone? Well I don't but it's nice to have a functional device at the very least...
Maybe even a dump of someone's NVRAM (with the IMEI, MACs and anything else that not necessary removed, I can add my own later) would help a lot.
I have the same problem with the notch
I have the exact same problem, does anyone know any solution to this?
Related
Ok... I'm ready to ask for help... I'm new enough to this that I'm willing to say please go easy on me.
So Im working with a rooted Epic 4G Touch. It's the EL29 root that seems highly recommended, nothing special, no special considerations there.
So moving along..
I accessed the efs with qpst to pull 0 and 1943. Locked, but visible.
Continued with the open sesame door instruction, rebooted, and tried to re-access the efs through the same manner (qpst efs explorer). Nothing. EFS explorer can't see, won't find it, nothing. Completely hidden. Including the open sesame door folder. It (the efs) hasn't been deleted. The phone still accesses all the normal information (Phone reports a normal imei, bluetooth mac, wireless mac, etc). But to save my life, I personally cannot access this directory to even see, let alone pull these two files for any type of modification. Nothing. I tried root file managers including Root Explorer as well in following other guides, nothing. DFS can access part of the hidden efs that I cant see with EFS explorer, (basically anything that wasn't locked before the directory became completely hidden - including the created open sesame door folder, [deleting it does not fix the issue], but nothing that was locked - such as the 0 and 1943 files I was seeking in the first place - is visible to DFS), however, DFS can access the information through NV Read range and the information is good, (that is, its accurate from the information I have for the device) (but its just the demo so it can't be edited directly, but it does tell me I suppose that the information is there and valid still?).
Anyway, so this is basically what's going on. I'm just trying to put this phone on metro, it seemed fairly straightforward.
I suppose the core questions are
1.) WHAT THE $&#@ happened to the efs, and is there something I can do to.. I guess normalize this? Any answers as to what, why, or recourse are humbly appreciated.
2.) Is there another route to accomplishing what I'm trying to do? I was contemplating reading the information from DFS (read range 0-1 and 1943-1944 which spit out item 0 and item 1943 respectively) saving these and editing them manually with a hex editor and then importing them back in the same way through DFS, since you can save them, but I don't know if the import is going to work, or even if that particular procedure will work. Is there another another method someone is willing to point out? I feel like Im drastically overcomplicating this...
I've been at this for awhile now... Any and all help is most graciously appreciated.
2.) Is there a simpler route to accomplish what I'm trying to do? Like shouldn't I be able to use CDMA workshop
Other questions that may be asked...
Do I have an efs backup... A proper backup? I'm going to say no. Not with all the content that I know is in there, though I have been able to pull what I can see (which is everything that dfs can see minus the locked items dfs won't show me -- which is more than what root explorer can see... if that makes any sense at all...)
You cannot try the open sesame door method on this phone. I think it is only used on htc phones. What you are trying to accomplish is not something that can be talked about due to it not being legal in some cases. The best way to do it is having the epic touch's esn added to metro then flash for data and mms.. There is a easy method to do it you just have to search
chivasjose09 said:
You cannot try the open sesame door method on this phone. I think it is only used on htc phones. What you are trying to accomplish is not something that can be talked about due to it not being legal in some cases. The best way to do it is having the epic touch's esn added to metro then flash for data and mms.. There is a easy method to do it you just have to search
Click to expand...
Click to collapse
Some cases unless I'm mistaken being the operative phrase. If I've honestly broken a rule already I will withdraw completely with my apologies. But if not, I am very much perplexed. Yes, I did eventually figure out that the open sesame method was not appropriate for this device. The metroflash method you speak of is ending/ended. This is no longer an option in most cases.
Ok well for informational purposes ---
The aforementioned importing of the two nv ranges was successful. For the life of me I can't figure out why the efs was invisible for so long and through so much effort and despite many attempts to read it, but after the procedure, it is visible again.
Any explanations for educational purposes are welcome.
I don't think you've broken a rule so don't worry. It is sometimes hard to talk about it. Most people use the terms donor phone or esn repair. The metroflash is ending or ended it is still not known. I live here in Dallas and stores are still flashing phones to metro. It is still possible you just need to look around to find the resources available. I forgot to mention that i have my e4gt to metro. Just pm me and ill direct you to the places you need.
chivasjose09 said:
I don't think you've broken a rule so don't worry. It is sometimes hard to talk about it. Most people use the terms donor phone or esn repair. The metroflash is ending or ended it is still not known. I live here in Dallas and stores are still flashing phones to metro. It is still possible you just need to look around to find the resources available. I forgot to mention that i have my e4gt to metro. Just pm me and ill direct you to the places you need.
Click to expand...
Click to collapse
Chivas thank you ~ I was attempting to keep the post free from such terms. I did actually get the phone up on metro using the aforementioned process using the proposed method I had outlined, (I was actually surprised the demo was able to do this because NOTHING could read those items once they disappeared on me, and then as soon as I finally did successfully edit them everything, including EFS explorer could read them again. I was very confused as to what had happened and am still interest if anyone has a proposed explanation). I appreciate your consideration. If perhaps you can direct me to a decent mms guide you can confirm working I would appreciate it because I dont think I've been able to send and even receiving seems highly dodgy at best. I would ask you if you could recommend a prl as there seems to be some contention on this subject as well, but as you're in Dallas I would assume I need to play with them to find the best one. I'm working on the GPS as well, but believe I've found the correct method as outlined here: http://forum.xda-developers.com/showthread.php?t=1750366.
What would also be nice some additional information with regard to the following:
The device is connected to metro with a metro prl however, when in service going to about phone - status - mobile network shows "Sprint"
And similar with the drop down notification drawer (IM using the new senzation rom at time of writing fyi though unless I am attempting to flash), it also reads either "not in service" if searching for signal, or "Sprint". more information
Thank you again, all consideration is appreciated
@ChemicalM How did you get to open EFS and NV items folder?
Wow... we're goin back pretty far here but if I remember correctly, DFS was successfully able to read the two NV ranges and after new ones were successfully imported the folders simply appeared, I don't believe I ever truly figured out why, but by that point the work was done so I didn't necessarily need it anymore.
Hey all,
So I've been working on this for quite some hours now for two nights, but I'm done for and hope someone can give me clarity:
HTC One m9, running stock, latest update VDF Germany, Android 6.0.
Problem occured last week. I was using the phone quite extensively (yeah, tbh I was playing Pokemon Go... like a lot). With it being constantly on wifi/4g/GPS and all, charging it all the time, the battery also became quite warm.... And then while walking about it crashed and rebooted. I never had such a crash before tbh. After Reboot HTC Error Report even popped up and I also sent it. Then I found that the Bluetooth and Wifi Connections were off, which I usually both have activated all the time. And now I cannot turn them on anymore. No matter which shortcut is used. Wifi displays "error" after some minutes, while BT is just greyed out after triggering. Wifi Mac is showing with a 02:00:00:00:00 now as well.
So I did my research and performed quite some things, trying to get it fixed, because I am still not sure wether this is a Hardware or Software issue. A lot of people reported the issue at least for the wifi part. Less people reported it for both, wifi and BT, but I would guess that not too many people use BT regularly anyway. I found one person mentioning, that if both is not working it is most probably a hardware related issue. Which was my first thought exactly, thinking it overheated, something had gone loose internally and now the antenna is killed or at least not connected anymore.
As for the physical methods, I only tried the "whacking the back part of the device"-technique, which did not do anything. I haven't gone through "freezer" or "hair dryer" yet....
Some people were able to fix it via draining the battery and then restarting and draining again and what not.. but that all sounded weird to me.
I am still hoping it is software related so I went:
- Wifi Fix and Rescue App
- Unlock
- TWRP
- Root
- Reflashing stock
- numerous factory and network settings resets
Because I read about the /persist partition or folder and that it should contain wifi or mac address related info. Some guy had simply deleted those files and they were recreated upon reboot. But those files are not existing in my /persist folder (checked via Root Explorer - got the paid version) and I have Root - as stated above. Still that folder only lists:
\data
\display
\hlos_rfs
\lost+found
\rfs
\tee
I found a thread in google's cache of someone on how to recreate or fix that folder and contents, based on a nexus 5 however and that is probably not working on the HTC one m9 I was presuming.
So, what do you guys think?
Is there any way to get the wifi back to work? Would you say it even might be software related, looking at the persist partition/folder contents? Or am I totally wrong and the fact that BT AND Wifi are not working, rules everything else out and only leaves a Hardware Issue?
Looking forward to hearing your thoughts on this.
Thanks in advance!
- Arne
I'd bet a bollock its the hardware popped. Bluetooth and wifi are on the same board, probably the same rf chip. A local phone repair shop should ve able to fix it seeing as it's out of warranty.
Beamed in by telepathy.
Im using a HTC 10 (EU variant). Today i was scrolling through "Netguard" (if you dont know it, its an app to prevent other apps from internet access), since i configured it to show system apps it displays way more apps than the normal app overview in the settings. In there i found an app called "RootPA" and one called "root", which seems strange since i didnt unlock the bootloader or root on my own. The details in the RootPA entry say "com.gd.mobicore.pa", no idea if thats helpfull to determine the origin of this mysterious app.
Can you help me with this?
Did you Google it?
I did, but the results were not realy usefull. I found someone with a modded Galaxy S3 who deleted a RootPA on accident and broke stuff, but that ssems unrelated. Are there any things i could do to find out more about the app installed on my phone without root?
I cant say its something I've ever seen. If this person in the past removed it, and it broke stuff, that would suggest that it may have been a system app and he was rooted. From what I managed to find on google, it is part of a security suite (mobicore) used by networks to monitor what the state of the phone is, presumably incase something happens, and it was the user fault, and they know for a fact because they have logs of what the phone has done.
[ACCESS_NETWORK_STATE] Allows applications to access information about networks
[INTERNET] Allows applications to open network sockets. (i.e send information)
[READ_EXTERNAL_STORAGE] Allows an application to read from external storage.
[READ_PHONE_STATE] Allows read only access to phone state.
A friend of mine got his HTC 10 2 days ago, ill ask him to look for this app. Its unlikely we would have the same virus/whatever installed.
Edit: He just reseted his 10 (due to missing language options, but thats another topic), but still found "root" and "rootPA" on his phone, so its preinstalled (although i still dont understand whats its purpose).
RootPA is provides service for provisioning secure applications that run on ARM trustzone and t-base OS (formerly mobicore). It is preinstalled in some vendors Android devices (search for this string on the internet: htc-devices-to-incorporate-trustonic-t-base-tee), but mostly unused as far as I know. The source code of some versions is available on the Internet (e.g. on github /Faryaab/android_hardware_samsung_slsi_exynos5410/tree/master/mobicore/rootpa).
It has nothing to to with rooting or unrooting the device.
PA route is very dangerous I had some I have somebody who has hacked into my phone through this particular program so to speak I have a lot of issues right now with my phone trying to get them off of my phone and this seems to be the root cause or the start of it have anybody knows how I can clear my phone and my Ram from the Vicious hacker I appreciate it I'm tired of being watched and recorded everything I do
Illfidusoon12 said:
PA route is very dangerous I had some I have somebody who has hacked into my phone through this particular program so to speak I have a lot of issues right now with my phone trying to get them off of my phone and this seems to be the root cause or the start of it have anybody knows how I can clear my phone and my Ram from the Vicious hacker I appreciate it I'm tired of being watched and recorded everything I do
Click to expand...
Click to collapse
PA route..... .rootPA ......2 different things. Hacked ? Unlikely, I think some OCD is kicking in. Want to be clean? RUU the device and do not restore anything
So here's a difficult question and hardly anyone has done what I did...
I wanted to restore my old G3 on my new G3 (both D852 models). I had dd images from my old phone and dd'd them back onto the new phone.
I restored userdata(44), cache(43), System(42), boot(18) and modem(1) of course. Then I booted and everything started quickly. However, the ROM (Fulmics 6.9) settings are totally gone or reset (like the settings menu is back to tab view instead of my preferred list view). Not sure what else might be screwed.
I then also restored sbl1(2) and misc(32), booted again and no change.
What is going on here? Why are the settings gone? Where are they stored? Could it be the fact that it's a different device and IMEI that resets the settings?
I thought settings are in system or data and all these weird partitions like EFS are not used to store any settings that are generally accessible from a ROM? Someone knowledgeable here to educate me, please?
Things are getting really weird. First I found this really weird problem and solution.
But all things are not good as my VPNs are completely greyed out under the "More" page below "Mobile Networks". I haven't found anyone with this problem.
The other problem is that I get the message "Wi-Fi is not available in airplane mode" whenever I want to turn on Wifi with cell signal off. One guy had that issue but no solution.
I also restored the tz partition and got a strange status page after booting up, but no other effects or improvements noted..
figured it out, a whole bunch of environment variable went missing somwhere - wish I knew where they are stored.
For the wifi without airplane mode it is airplane_mode_toggleable_radios that has to be there and that fixed VPN as well for some reason.
Described in more detail here
Hello, I really hope somone can help with this problem - I know the obvious answer is to get the screen repaired but I cant afford it. I've tried looking at other posts as well but am not getting anywhere.
Last year the screen went on my OP3 after being dropped and the screen is now blank with quite a few cracks. The phone still works - all the buttons work and I think I've even managed to enter the PIN. I now need to retrieve a file from the phone.
The phone hasn't been rooted or modded in any way (it's as it came from the factory). When I plug it into my PC i can see the drivers folder and the 5 files in there, but nothing else.
I was hoping I could access the phone remotely but OTG was not enabled, though I did in the past enable developer options. I believe hope is not lost, as the phone can be put into fastboot (or something like that - I'm not terribly techy but can work things out) but without being able to see the screen..... I've looked ADB devices and there's nothing after "list of devices attached".
Is there any way of being able to do something? I've looked for screenshots to see if I can operate the phone blind, but can't find anything. I am patient and will keep trying until i get it or save the money for a repair, but I really need the file asap. The phone itself isn't important to me (I've replaced it since) - only the data on it.
Very grateful for any help anyone can offer.
edit: Wifi enabled solutions are not an option sadly as I've changed my ISP since so can't amend the settings on the phone (unless I get extremely lucky)
You're screwed, just buy another screen.
It will be easier to just lend a money.
Rwjk said:
Hello, I really hope somone can help with this problem - I know the obvious answer is to get the screen repaired but I cant afford it. I've tried looking at other posts as well but am not getting anywhere.
Last year the screen went on my OP3 after being dropped and the screen is now blank with quite a few cracks. The phone still works - all the buttons work and I think I've even managed to enter the PIN. I now need to retrieve a file from the phone.
The phone hasn't been rooted or modded in any way (it's as it came from the factory). When I plug it into my PC i can see the drivers folder and the 5 files in there, but nothing else.
I was hoping I could access the phone remotely but OTG was not enabled, though I did in the past enable developer options. I believe hope is not lost, as the phone can be put into fastboot (or something like that - I'm not terribly techy but can work things out) but without being able to see the screen..... I've looked ADB devices and there's nothing after "list of devices attached".
Is there any way of being able to do something? I've looked for screenshots to see if I can operate the phone blind, but can't find anything. I am patient and will keep trying until i get it or save the money for a repair, but I really need the file asap. The phone itself isn't important to me (I've replaced it since) - only the data on it.
Very grateful for any help anyone can offer.
edit: Wifi enabled solutions are not an option sadly as I've changed my ISP since so can't amend the settings on the phone (unless I get extremely lucky)
Click to expand...
Click to collapse
Unless you enable 'USB Debugging' in Developer Options and install the required drivers, your phone will not be 'seen' by your PC. Without your phone being 'seen' by your PC, nothing can be done.