Related
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Seriously???
pastorbob62 said:
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Click to expand...
Click to collapse
Not to be negative or anything but I think this is the least responsive forum on this site. I have spent hours searching for possible solutions to various problems I've encountered over the past several months, asked several questions and received little if any help. I was only able to get back from a bricked phone to where I am now by using information found on other websites. Pretty sad if you ask me.
In contrast, whenever I have asked a question on my tablet's forum I've received fast workable solutions/answers to my problems/queries. The threads are informative, well organized and contain answers to any situation I have encountered.
Granted, my current problem with my phone is my own fault for trying to customize it. And I suspect part of the problem is due to the age of this phone thus most of the "experts" have moved on to other ventures. It is also hindered by the lack of information available from Huawei and the service providers.
All of that said, if anybody has any suggestions for how I can repair the ESF partition or whatever is causing this lack of mobile service issue I would be extremely grateful. It isn't the end of the world since i have a new phone (Consumer Cellular) that I am currently using but it would be great to get this one working since it's much faster and more streamlined than my stock Consumer Cellular version.
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
Thank you very much for your reply. It seems that you have found the answer to my problem. But unfortunately, I don't have a copy of the original stock ROM. My phone is the -51 version and any links I have found to the stock ROM are broken. There is a version I found but it is for Venezuela and I don't think it will work. I am leery to try it and totally brick my phone. My backup is apparently corrupted. I backed up my new working phone with Disk Image and attempted to restore it to the broken phone but all that did was cause it to come up to the ATT logo screen for a few seconds and then shut down. It wouldn't do anymore than that. So I restored the Stallion 3.5 image I made and am back to a great fast tablet with no phone service. I also tried backing up my IMEI on the working phone and restoring it to the broken phone but that had no effect.
It is my understanding that the -Pro version of the ROM will work, but I don't have the stock image of that either. I suspect it work might since I was able to use the -Pro version of GB on it. All of my internet searches have only turned up custom ROMs and other desperate people looking for fixes for similar problems or worse. I agree 100% with your assessment of Huawei's lack of meaningful support. It really is a shame, because these phones aren't half bad when they have been customized and OC'ed a little.
I have just about given up on it and resigned myself to using it as an MP3 player for my car system. I have learned my lesson and am leaving the working phone stock. It is rooted and I have cleaned off all of the bloatware, and set it up so most apps run from my SD card, so it really isn't half bad. At least it works.
Again, thank you for your reply and advice.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
ggunzio said:
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
Click to expand...
Click to collapse
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Blefish said:
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Click to expand...
Click to collapse
i have exactly the same phone than you, because i installed that backup too. After installed it, the IMEI SV is 36, after installing B518 it says it is 18, but before it was 17, and i had 3g signal, but not now.
My question is, wich SV is your phone reporting?
Thank you
I also have a problem like this, but I think it's a bit more severe. My phone got stuck while charging. Couldn't reboot. Was getting stuck on the aurora loading screen(using DZO 5u20). Than reinstalled whole rom. But now I don't any signal and the phone doesn't even see a SIM card. Showing 'baseband unknown' and the IMEI and IMEI SV are also unknown. Not 0's but just unknown. Is this is a similar problem? And can something be done to fix it.
I had some backups on my sd card, untill the sd-card got fried in the phone a couple of months ago.
II don't want to be an alarmist but back on 17th June 2016 I created this thread DM Verification failure , Please flash ENG binary then install DNK
At the time I wasn't sure what had caused the problem but last night with a different phone I used KingoRoot and it corrupted a second phone of mine. Now two out of three of my Verizon Note 4's have the dm-verification-failure.
The symptoms of the problem are when I am navigating some of the swipes lag. Sometimes when typing there is a lag delay before it is entered. Sometimes Wifi lags before it is turned on and the phone forgets my wifi password.
I found this thread How to solve dm-verity verification failed/need to check drk first on samsung devices but I don't have the experience to do it. Can a developer create the fix for the Verizon Note 4 , PLEASE, Thanks
doctor-cool said:
II don't want to be an alarmist but back on 17th June 2016 I created this thread DM Verification failure , Please flash ENG binary then install DNK
Now two out of three of my Verizon Note 4's have the dm-verification-failure.
Click to expand...
Click to collapse
I am at the end of consolidating all the info I can to determine if I should get a Note 4. Root is the thing that matters to me, but I have learned that regardless of 4.4.4 or 5.1.1 you have to unlock the bootloader which is the challenge.
Just as I think I have it all together and that the methods provided (on XDA only) are the only only ones available and apparently stable, I read this.
Am I COMPLETELY MISUNDERSTANDING your post? Is your post from here http://forum.xda-developers.com/not...bilized-process-to-unlock-bootloader-t3375527 which I've saved as reference for rooting a device no longer accurate?
I'm overwhelmed from so much research and think I've curated the posts that matter, then I see this. Can you offer anything on this? Again, I may not be understanding. I am NOT a developer or programmer. I've rooted a few devices, but it has been a long time with the most recent not requiring the seeming complication of this one (thanks a lot, Verizon!).
jecilop said:
I am at the end of consolidating all the info I can to determine if I should get a Note 4. Root is the thing that matters to me, but I have learned that regardless of 4.4.4 or 5.1.1 you have to unlock the bootloader which is the challenge.
Just as I think I have it all together and that the methods provided (on XDA only) are the only only ones available and apparently stable, I read this.
Am I COMPLETELY MISUNDERSTANDING your post? Is your post from here http://forum.xda-developers.com/not...bilized-process-to-unlock-bootloader-t3375527 which I've saved as reference for rooting a device no longer accurate?
I'm overwhelmed from so much research and think I've curated the posts that matter, then I see this. Can you offer anything on this? Again, I may not be understanding. I am NOT a developer or programmer. I've rooted a few devices, but it has been a long time with the most recent not requiring the seeming complication of this one (thanks a lot, Verizon!).
Click to expand...
Click to collapse
The stabilized-process-to-unlock-bootloader I posted is still valid. I recommended using Kingroot. I found the dm-verity problem with KingORoot. We need more feedback to be sure. I never had the problem with Kingroot. I removed the link to KingORoot from my guide today.
doctor-cool said:
The stabilized-process-to-unlock-bootloader I posted is still valid. I recommended using Kingroot. I found the dm-verity problem with KingORoot. We need more feedback to be sure. I never had the problem with Kingroot. I removed the link to KingORoot from my guide today.
Click to expand...
Click to collapse
Hmmm..ok..thanks for the reply.
That's interesting as I've read so many posts that say KingRoot is not the way to go but rather KingOroot is the correct on to use. Specifically, a lot of people seemed to have tried it unsuccessfully in the process.
I was also hoping to avoid KR as I've read it is a bit sketchy. I've used it twice before doing that and found a Nextbook tablet it worked great on with seemingly no apparent problems since. Another Samsung phone was rooted with it (I was actually searching for KOR, but didn't remember the name exactly and ended up with KR on a search). Unfortunately, the security pop-up keeps coming up trying to remove it. The user who didn't know what they were doing inadvertently gave it the OK to remove it, and now I haven't been able to re-root with it...arrggh..
I recently thought to install their Purify app (which they push when doing KingRoot) separately, but the permissions in the app say that you give it the ability to analyze the content on the screen in an window...I can't figure how THAT is needed to block startup programs or background one to save battery!
So, I was hoping this meant the KOR was good to go with the process after the bootloader is unlocked and stable per your post. I wonder if anyone else is running into problems. I know this is all very new still.
I don't suppose you could tell me:
1) Is permaroot available (with these new methods) only on 5.1.1 , or is it also available on 4.4.4 ? I haven't been able to decipher that.
I kind of prefer KitKat over the material design changes that are just wasting space on my screen in JellyBean. The Note 4 I got to purchased recently (unfortunately, it was a sketchy phone now being returned), had notifications on constant screen overflow because they waste SO MUCH SPACE with them and with unnecessary notifications that I cannot stop from showing (Power Saving, Wif connected, Blocking on). I know a good bit of that is Samsung, but the non-compact use of the notifications is Android ( Google's changes). It was better on my SG3 with 4.4.4 even though they still has persistent notifications.
I'm hoping to root and find a mod to stop showing those. I'm aware enough to check my connections via the settings when needed.
Thanks Again.
jecilop said:
Hmmm..ok..thanks for the reply.
That's interesting as I've read so many posts that say KingRoot is not the way to go but rather KingOroot is the correct on to use. Specifically, a lot of people seemed to have tried it unsuccessfully in the process.
I was also hoping to avoid KR as I've read it is a bit sketchy. I've used it twice before doing that and found a Nextbook tablet it worked great on with seemingly no apparent problems since. Another Samsung phone was rooted with it (I was actually searching for KOR, but didn't remember the name exactly and ended up with KR on a search). Unfortunately, the security pop-up keeps coming up trying to remove it. The user who didn't know what they were doing inadvertently gave it the OK to remove it, and now I haven't been able to re-root with it...arrggh..
I recently thought to install their Purify app (which they push when doing KingRoot) separately, but the permissions in the app say that you give it the ability to analyze the content on the screen in an window...I can't figure how THAT is needed to block startup programs or background one to save battery!
So, I was hoping this meant the KOR was good to go with the process after the bootloader is unlocked and stable per your post. I wonder if anyone else is running into problems. I know this is all very new still.
I don't suppose you could tell me:
1) Is permaroot available (with these new methods) only on 5.1.1 , or is it also available on 4.4.4 ? I haven't been able to decipher that.
I kind of prefer KitKat over the material design changes that are just wasting space on my screen in JellyBean. The Note 4 I got to purchased recently (unfortunately, it was a sketchy phone now being returned), had notifications on constant screen overflow because they waste SO MUCH SPACE with them and with unnecessary notifications that I cannot stop from showing (Power Saving, Wif connected, Blocking on). I know a good bit of that is Samsung, but the non-compact use of the notifications is Android ( Google's changes). It was better on my SG3 with 4.4.4 even though they still has persistent notifications.
I'm hoping to root and find a mod to stop showing those. I'm aware enough to check my connections via the settings when needed.
Thanks Again.
Click to expand...
Click to collapse
I can only report my findings. We need more feedback.
The only real negative I've noticed with KingRoot is that it's erased the serial numbers from both of the phones I've used it on. Thankfully it didn't affect the IMEI, but whenever I try to check the serial number on those two devices, it just shows a bunch of zeros. Back up your EFS partition first (if you can without being rooted, I'm not sure), or at least make a note of the serial number. You can manually edit /efs/FactoryApp/serial_no to restore your serial number as long as you know what it is. I don't believe the serial number is used for anything (except maybe warranty-related things), just annoys me that KingRoot erased it.
As far as removing KingRoot, after you unlock the bootloader you can flash a modified stock firmware file for the phone (one that has had aboot.mbn removed) and still retain an unlocked bootloader. Flashing anything with an aboot.mbn will re-lock your bootloader, so be sure you remove that from any Odin tars before flashing. I had access to the full factory firmware for the device (containing the PIT file and a couple of other partitions not found in the home firmware files hosted by sites like SamMobile) so I stripped aboot.mbn from it and flashed that to make sure I started with a clean, KingRoot free device.
blindmanpb said:
The only real negative I've noticed with KingRoot is that it's erased the serial numbers from both of the phones I've used it on. Thankfully it didn't affect the IMEI, but whenever I try to check the serial number on those two devices, it just shows a bunch of zeros. Back up your EFS partition first (if you can without being rooted, I'm not sure), or at least make a note of the serial number. You can manually edit /efs/FactoryApp/serial_no to restore your serial number as long as you know what it is. I don't believe the serial number is used for anything (except maybe warranty-related things), just annoys me that KingRoot erased it.
As far as removing KingRoot, after you unlock the bootloader you can flash a modified stock firmware file for the phone (one that has had aboot.mbn removed) and still retain an unlocked bootloader. Flashing anything with an aboot.mbn will re-lock your bootloader, so be sure you remove that from any Odin tars before flashing. I had access to the full factory firmware for the device (containing the PIT file and a couple of other partitions not found in the home firmware files hosted by sites like SamMobile) so I stripped aboot.mbn from it and flashed that to make sure I started with a clean, KingRoot free device.
Click to expand...
Click to collapse
Thanks, I like the way you think.
Is there some file I can take from a good working Note 4 and repair the DM verification issue ? Do you think I could do it with efs Profestional. Just wondering.
I initially used KingRoot, and it failed 20 out of 20 times to root my phone. I used KingOroot on my laptop (in a VM) and it rooted my phone first try. I don't have any Wifi issues and I don't see any "DM Verity" messages anywhere on my phone.
raduque said:
I initially used KingRoot, and it failed 20 out of 20 times to root my phone. I used KingOroot on my laptop (in a VM) and it rooted my phone first try. I don't have any Wifi issues and I don't see any "DM Verity" messages anywhere on my phone.
Click to expand...
Click to collapse
I think, You would only see the DM Verity" messages when you are in stock recovery. Once you log into your google account, it remembers your passwords. But on my phoneS, I still get the other lagging problems. What ROM are you on?
blindmanpb said:
The only real negative I've noticed with KingRoot is that it's erased the serial numbers from both of the phones I've used it on. Thankfully it didn't affect the IMEI, but whenever I try to check the serial number on those two devices, it just shows a bunch of zeros. Back up your EFS partition first (if you can without being rooted, I'm not sure), or at least make a note of the serial number. You can manually edit /efs/FactoryApp/serial_no to restore your serial number as long as you know what it is. I don't believe the serial number is used for anything (except maybe warranty-related things), just annoys me that KingRoot erased it.
As far as removing KingRoot, after you unlock the bootloader you can flash a modified stock firmware file for the phone (one that has had aboot.mbn removed) and still retain an unlocked bootloader. Flashing anything with an aboot.mbn will re-lock your bootloader, so be sure you remove that from any Odin tars before flashing. I had access to the full factory firmware for the device (containing the PIT file and a couple of other partitions not found in the home firmware files hosted by sites like SamMobile) so I stripped aboot.mbn from it and flashed that to make sure I started with a clean, KingRoot free device.
Click to expand...
Click to collapse
That why I kept the original box with the serial numbers on it lpl
Sent from my SM-N910V using Tapatalk
raduque said:
I initially used KingRoot, and it failed 20 out of 20 times to root my phone. I used KingOroot on my laptop (in a VM) and it rooted my phone first try. I don't have any Wifi issues and I don't see any "DM Verity" messages anywhere on my phone.
Click to expand...
Click to collapse
Same here, only I used the Kingoroot APK, no issues on either the retail or DE. On JasmineROM (6.0 on the DE and 7.0 on the retail)
fz798 said:
Same here, only I used the Kingoroot APK, no issues on either the retail or DE. On JasmineROM (6.0 on the DE and 7.0 on the retail)
Click to expand...
Click to collapse
The lag is most apparent on stock rom that I rooted with KingOroot apk. On CyanogenMod it is more like a hesitation. The damage is so far as I know irreversible.
The other phone that has only been rooted with KingRoot is a a factory DE it does not have the DM Verification issue and it runs as smooth as silk on every ROM I have tried. So I say the problemS came from KingOroot. But we need more data points/ feedback to be sure.
pfcland said:
That why I kept the original box with the serial numbers on it lpl
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Verizon Note 4 does not list serial number on the box, unfortunately.
Can you post a short video detailing the issues and is there something I can do to immediately verify if there is a dm verification problem with my device? I also used Kingoroot on my Note 4 due to KingRoot not working after several tries, but I don't notice anything out of the ordinary, just the usual ocassional lag that is on every Android device.
Only noticeable issues I've experienced have been the "Unauthorized Actions Detected" issue and Wifi passwords not saving using PaulPizz 6.0.1/OscarKernel, but that was corrected with the freezing of a couple Samsung security apps and a build.prop edit.
NeoandGeo said:
Can you post a short video detailing the issues and is there something I can do to immediately verify if there is a dm verification problem with my device? I also used Kingoroot on my Note 4 due to KingRoot not working after several tries, but I don't notice anything out of the ordinary, just the usual ocassional lag that is on every Android device.
Only noticeable issues I've experienced have been the "Unauthorized Actions Detected" issue and Wifi passwords not saving using PaulPizz 6.0.1/OscarKernel, but that was corrected with the freezing of a couple Samsung security apps and a build.prop edit.
Click to expand...
Click to collapse
I'm working this now FIx DRK/dm-verity, Factory CSC and Serial Number So far I have been able to restore my serial#. after I turned on the hidden menu.You have to be in stock recovery to see the dm-verity verification failed message. You would have to Odin back to stock to see it.
Lag is not normal unless you have a ton of apps running. ., Wifi passwords not saving is not normal not even once , I bet you got the bug.
Maybe, but I don't have the wifi passwords issue unless I flash OacarKernel over either Jasmine or Paulpizz, stock kernels are OK in that regard.
How bad of a lag are we talking about? Slight hesitation or full on freezes for more than a second at a time?
After a few weeks of using the device with custom ROMs, no lag spikes have been out of the ordinary for me, feels more responsive than my Note 3 and noticeably better than both the Nexus 6/Moto X I've previously used.
The only truly frustrating lag spikes I've noticed are trying to use this site without any form of adblock on Chrome.
NeoandGeo said:
Maybe, but I don't have the wifi passwords issue unless I flash OacarKernel over either Jasmine or Paulpizz, stock kernels are OK in that regard.
How bad of a lag are we talking about? Slight hesitation or full on freezes for more than a second at a time?
After a few weeks of using the device with custom ROMs, no lag spikes have been out of the ordinary for me, feels more responsive than my Note 3 and noticeably better than both the Nexus 6/Moto X I've previously used.
The only truly frustrating lag spikes I've noticed are trying to use this site without any form of adblock on Chrome.
Click to expand...
Click to collapse
The Best example is scrolling lagging on this site with Chrome. My phone without the issue is as smooth as silk. No hesitation. The phones with the bug maybe two swipes work then the third swipe lags then the page jumps to catch up. It is uncomfortable to use.
XDA forums have been fine for me in Chrome since I installed an ad blocker not too long ago. Before that I would get annoying pauses and skips, like you're talking about. Though this also happened on my Note 3/Moto X/Nexus 6 as well on this site.
Is there any way to see if any running processes have large latency spikes when these lags/pauses occur?
Also is there another kernel I can try on PP 6.0.1 ROM or a way to easily flash the stock kernel on it without restoring a backup? Seems like the minor issue with Wifi only crops up with OscarKernel.
doctor-cool said:
I'm working this now FIx DRK/dm-verity, Factory CSC and Serial Number So far I have been able to restore my serial#. after I turned on the hidden menu.You have to be in stock recovery to see the dm-verity verification failed message. You would have to Odin back to stock to see it.
Lag in not normal unless you have a ton of apps running. ., Wifi passwords not saving is not normal not even once , I bet you got the bug.
Click to expand...
Click to collapse
Verizon devices do not have the typical Samsung serial number. The only serial number your device uses in the last 32 bits of your eMMC CID. The EFS serial number is supposed to be 00000000, and will not affect any functionality of your device. You had your DRK (Device Root Key) erased. It could have been from damage to the EFS partition or something else benign. You'll want to flash complete stock Odin, reboot to recovery and wipe data, and reboot. This should fix your issue, but if it doesn't, let me know and we'll cross that bridge.
In response to OscarKernel not saving WiFi passwords, it's an issue related to ROMs and not my kernel. It does not use secure_storage, so setting ro.secure_storage=false is necessary, and once done, everything will go back to normal and save fine.
ryanbg said:
Verizon devices do not have the typical Samsung serial number. The only serial number your device uses in the last 32 bits of your eMMC CID. The EFS serial number is supposed to be 00000000, and will not affect any functionality of your device. You had your DRK (Device Root Key) erased. It could have been from damage to the EFS partition or something else benign. You'll want to flash complete stock Odin, reboot to recovery and wipe data, and reboot. This should fix your issue, but if it doesn't, let me know and we'll cross that bridge.
Click to expand...
Click to collapse
The tutorial I was following was for the SM-N910C not the SM-N910V . For that device, magix01 has a tutorial to fix DRK. I was working on the premise that if I could repair the serial number, I could then use emergency software recovery. Thanks for straightening me out about the serial number. Put that aside for now.
I did Odin N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar several times downloaded directly from SamMobile and did the data wipe and rebooted every way possible I think. I still get the dm-verity failure and more importantly, It still has the lag bug. I have in my possession another SM-N910V that does not have any issues. I was wondering if I could take a file from the good phone and use it to fix the defective phone. Thanks, for your help, I am ready to cross that bridge.
The Story
Don't even know where to start. Okay so I have a SM-935W8 (Canadian Version) and it was working perfectly fine running Project Dream rom the S8 one. I decided to flash angelo's Pixel rom for S7 Edge and for some reason when it booted, the network had a cancel sign meaning no network. Once I finished the initial setup, calling, messaging , and data weren't working. Luckily I have a backup for EFS and RADIO in tar, img. and tar.gz formats. So I downloaded the Partitions Backup app and restored the EFS and Radio files, it said successfully restored. I rebooted my device and the issue was still there, no network. So then I installed the stock ROGERS (Provider) rom from SAM MOBILE and it came up with some DRK error and my phone would not boot. So then I quickly used ODIN to flash twrp and then flash Superman Rom (Love it) and use dm-verity bypass.zip to get past the drk error. Then I attempted many other things but to no avail such as flashing the EFS tar through ODIN which caused a "Software Error" and phone to be stuck on a light blue software error screen so I had to use smart switch to FULLY restore the phone back to booting up, then once again I flashed twrp and Superman rom with dm-verity so I atleast have root and a decent rom to work from.
The Problem and What I Have at Disposal
So essentially, I currently have a new section in settings under Connections called "SIM card manager" for managing sim cards even tho I only have 1 slot, it shows that the SIM is ROGERS and LTE/3G/2G in there, but it can't connect to a network and keeps saying Not Registered on a Network. Also, there are 2 IMEI's since my phone thinks theres 2 SIM slots but I really only have 1 slot. BUT HERE IS THE MAIN ISSUE, THE ROOT OF ALL PROBLEMS, the IMEI is reading as "000000000000000" and the IMEISV is "01". Hence im getting Not Registered on a Network. No secret codes such as *#06# are working, keeps giving the Not Registered on a Network error.
I have the EFS and RADIO backups in img, tar, and tar.gz formats as well as screenshots of all my MAC and Bluetooth addresses, IMEI and Serial #'s and all that information. So essentially I feel fully ready to solve the problem but everything I try keeps failing. My EFS restoration says successful in the APP but upon reboot, theres no change. Flashing the EFS through ODIN messes up phone harder. When I use EFS Professional Tool, where do I place the partitions so they show up in the tool?
I used this post to try to fix it: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
BUT when I'm flashing the combination through ODIN in AP, it goes to NAND write or whatever and gets stuck, sometimes it gets stuck on Analyzing files or something. I tried every single ODIN version. I really could use some expertise on this issue. A step by step written tutorial, some method anything!!!! Help on this post or even teamviewer or skype for live help would be appreciated. Please help and I'm willing to compensate for successfully helping me fix my issue..
Did you ever sort this out? I'm in a similar situation, except that it does occasionally show my IMEI but also 'baseband unknown'. But still no network access.
i hope i dont risk a warning, but you can use xposed and with root you can change your imei and baseband info.
012345678 said:
i hope i dont risk a warning, but you can use xposed and with root you can change your imei and baseband info.
Click to expand...
Click to collapse
Thanks, I've done so much to this phone now...
I did try xposed and have tried a different IMEI, it seems like it's a modem issue but there doesn't seem to be a firmware solution - I have tried so many stock roms(All the way back to the first Marshmallow and a bunch in between) and different custom roms too but in the end the error is always there: Not registered to Network.
I saw somewhere in my troubleshooting that some kind of cert needs to be patched because the phone did an update on a modified rom without the OEM unlock being on and then the EFS data was messed up or something like that (all of the research and troubleshooting is starting to blur). It seems like that fix isn't doable without a rather expensive piece of hardware (expensive if your just fixing your one phone I guess) and there isn't any firmware-only fix that can accomplish this patch so I'm stuck again.
jamesroodney said:
Thanks, I've done so much to this phone now...
I did try xposed and have tried a different IMEI, it seems like it's a modem issue but there doesn't seem to be a firmware solution - I have tried so many stock roms(All the way back to the first Marshmallow and a bunch in between) and different custom roms too but in the end the error is always there: Not registered to Network.
I saw somewhere in my troubleshooting that some kind of cert needs to be patched because the phone did an update on a modified rom without the OEM unlock being on and then the EFS data was messed up or something like that (all of the research and troubleshooting is starting to blur). It seems like that fix isn't doable without a rather expensive piece of hardware (expensive if your just fixing your one phone I guess) and there isn't any firmware-only fix that can accomplish this patch so I'm stuck again.
Click to expand...
Click to collapse
i think i can help you out with that. install that with odin, it should get your efs and imei back:
Samsung S7 Edge Cert and Efs (SM-G935F)
https://drive.google.com/file/d/0B5829G4TER3CZmZYVU9PY21qT2c
012345678 said:
i think i can help you out with that. install that with odin, it should get your efs and imei back:
Samsung S7 Edge Cert and Efs (SM-G935F)
https://drive.google.com/file/d/0B5829G4TER3CZmZYVU9PY21qT2c
Click to expand...
Click to collapse
Sorry, I should have clarified. I have an S7 (SM-G930W8). I only tried this thread because the issue was identical to mine and I couldn't find anything similar referencing the S7 specifically.
For anyone coming across this thread in the future, although mine was an S7 I think the issue would apply to both. I ended up ordering a z3x in order to use the patch certificate. But it wasn't that easy; the firmware had to be downgraded to marshmallow first which wouldn't work in Odin until I tried just flashing the BL and CP files first, then rebooting and flashing the AP and CSC files separately. In fact, the AP file froze the first time but passed on the second attempt. After that, everything was downgraded to android 6 and then the patch certificate option worked and my s7 connects to the network again.
I'm having a similar problem with my sm-g935w8 Rodgers but has been unlocked. A couple days ago i looked at my phone and it was showing a no signal symbol and I look for my phones information and it showed unknown in all categories, the imei say unknown, and it's not reading the sim. Help me
I am having the same problem after installing TGP ROM.
Graschuk said:
I am having the same problem after installing TGP ROM.
Click to expand...
Click to collapse
Did u Found any solution? am still in the same position as u r in.. i have also installed TGP ROM ... I Have Also Posted there my issue that i selected the latest bootloader nd modem blah blah
Wipe everything in twrp advanced and..
Flash latest stock rom for your model and it'll fix the issue
I think u need to see this
https://forum.xda-developers.com/showthread.php?p=78868375#post78868375
These two threads are the fountains of info :
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
This one specifically for S7 edge, whole lots of info.
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965
This one for advanced users who know what they are doing.. it isn't specifically for s7 series but has a universal approach to understand concepts.. don't use the provided drk (prov data) and csc restoring files, they aren't for s7 edge.
Always backup efs and all radio/serial related info firstly after rooting. Good luck
Sent from my S7 Edge using XDA Labs
Hi all, as the title says, my efs folder is inaccessible. Firstly let me explain. I bought a phone, it had the Paul pizz rom in it and I didn't like it. So I flashed the resurrection remix rom. It didn't have all the bells n whistles I wanted, so I tried the official res remix rom. Somehow I ended up with an efs problem. I ended up with an efs invalid argument error and from what I read, I did the whole adb efs fix. The error was gone. I ended up flashing a repair firmware back to bog5 and started from scratch. I worked my way back up to installing the modest rom and it works 99% flawlessly and I am happy enough to keep it. Here is the catch, I used kingo root and have ended up with a bad keyboard lag that's driving me nuts. It is unknown to me if the kingoroot caused the efs corruption or if it was just a bad flash going from one rom to another. I have tried several root browsers, made sure they all had root privileges, and no matter what, I can NOT get access to what's hidden in my efs folder. They always say it's empty. Now, here is the kicker, I got another note 4 for my son. Downgraded from 6.01 to 5.01 bog5, then up to 5.11 and flashed the modest rom on his. Instantly his phone has access to the efs folder. My note 4 works, can make calls, text etc. Imei is shown in settings, all info shows in settings as normal except one thing, on my phone it says configuration version not available whereas on my sons phone it gives a configuration version. I just can't figure out how to gain access to the efs folder to try to fix this extremely annoying lag. I DID make a complete backup of my system from when it had the Paul pizz rom, so the efs partitions should be intact there but I don't know if that would help or even where to start. Can someone please help?
Well, I just fixed my phone and thought I would share what happened. It seems that the guy that loaded the paulpizz rom on the phone before I bought it used a different version of twrp. He used a version for n910f, whereas when I began my rom search, I used one for a n910v because thats what the phone is. I was having a hard time with it so I reverted to stock, rooted, installed verizon twrp, and bam! No efs access. The difference in recovery programs is what screwed me up in the first place. I figured it out when I tried to restore his rom backup I made. The efs files were not working when it restored. I remembered what version of rom it was, and tried a twrp for 910f, and voila! So, now I have all functions working as blazing speeds, can actually access the efs folder, and no more damned lag! Big thumbs up button to me!
Hey there folks,
here I am now too on the forum, trying to find a solution for an old sticky problem.
So far a some people here on the forum a while ago have had the problem that when they flashed a custom OS on their Zenfone 3 while data roaming was turned off in the stock rom, they could never get it working unless reverting back to the stock OS and switching it on there before reinstalling the custom OS. Until then only normal calls and SMS work.
I'm having the same problem now and trying to avoid going back to stock, so I wonder if somebody has found another solution by now? Any help would be really appreciated, and I think a lot of other EU people who will run into this problem in the future will be grateful too if this could be solved easier somehow :fingers-crossed:
Update: I took a look at the firmware partition and there is a folder image/modem_pr which seems to include the configuration how the phone connects to mobile networks. I don't claim to have any special knowledge about it but i would expect this is where the stock rom most probably makes its change about data roaming.
So maybe, as long as what the firmware partition contains is generic firmware, could somebody who has data roaming working on their Zenfone3 send a copy of their /firmware/image folder so I can compare the two and hopefully find the missing puzzle piece to get data roaming working?
I would of course post the solution here for everyone in case I figure it out! Would be great if we can solve it
I have the same problem. Please help.
So, here's an update:
After going crazy searching for a possible fix I gave up yesterday and re-installed the stock rom in order to turn on data roaming (since my TWRP backup won't boot that is something I had been trying to avoid, because the only way I found to do this was to either install a recovery from somewhere on the internet that is claimed to be the original Asus recovery but has no way to be integrity-checked for possibly including malware, or to install software designed to bypass Google's SafetyNet and other system integrity checks. Nah.)
Today I took a look at comparing a TWRP backup of the modem partition (contents identical to the one that mounts as "firmware"), and the persist partition. I wrote a script that would calculate the md5 checksum for each file and then compare for any changes.
On the modem partition, only binary files named Widevine changed, for whatever reason :silly:
And here is a list of the files that were changed on the persist partition:
persist/coresight/qdss.functions.sh
persist/coresight/qdss.log
persist/coresight/qdss.log.old
persist/data/gxflag
persist/data/gxfp/0_0/105885283
persist/data/gxfp/0_0/105885284
persist/data/gxfp/0_0/gxfeature_table
persist/data/gxfp/0_0/gxfeature_table
persist/data/gxfp/0_0/gxflag
persist/data/gxfp/1_0/gxfeature_table
persist/data/gxfp/1_0/gxflag
persist/data/gxfp/calibration_data
persist/data/gxfp/calibration_data
persist/data/gxfp/gxflag
persist/data/gxfp/mptest/gxflag
persist/data/gxfp/raw/0_0/gxflag
persist/data/gxfp/raw/0_0/tpl_index_table
persist/data/gxfp/raw/1_0/gxflag
persist/data/gxfp/raw/1_0/tpl_index_table
persist/data/ifaa_fplist
persist/data/ifaa_fplist
persist/data/widevine/UZT8uT7lR1wsAoECBZWk4+aPFLDG92yRsy5vX3eX
persist/data/widevine/UZT8uT7++lR1wsAoECBZWk4+aPFLDG92yRsy5vX3eX.bak
persist/data/widevine/widevine
persist/dmclient/dm_client_info
persist/dmclient/dm_client_token
persist/dmclient/hash_sn
persist/rfs/msm/mpss/server_check.txt
persist/rfs/shared/server_info.txt
persist/sensors/error_log
persist/sensors/sensors_settings
persist/sensors/sns.reg
persist/time/ats_1
persist/time/ats_12
persist/time/ats_13
persist/time/ats_15
persist/time/ats_16
persist/time/ats_2
persist/.twrps
persist/sensors/sns.reg
persist/time/ats_1
persist/time/ats_12
persist/time/ats_13
persist/time/ats_15
persist/time/ats_16
persist/time/ats_2
Unfortunately, mostly binary files making it impossible for me to dig deeper into the changes. But maybe somebody spots something odd that could lead to the solution.
My next step will be to go abroad again in early March and see if the data roaming now works. If it does, I will restore a TWRP backup of all partitions I could back up before returning to stock. If it still works then, then the stock rom made its change somewhere on one of the partitions TWRP does not back up. If it stops working, then the answer lies hidden somewhere on the TWRP-backuped partitions.
Either way, I'm sure there must be a manual solution, what happens on the stock rom cannot be black magic
Will keep you updated.
Alright, it's the 1st of March and I'm back abroad! I finally have data roaming working and got a little further in my investigation: Restoring partitions one by one, i figured out that the change by the stock concerning the data roaming is made somewhere on the efs partition (which one of the two I can't say yet, as TWRP only lets me restore them both together). Now I haven't succeeded yet how to mount the efs.emmc TWRP backup or otherwise dump the contents of the efs partition, but if someone here knows I'll go dig deeper and track down the specific entry that is changed
Can you tell how to restore the original partition without flashing the asus rom? Thanks
If you ever had data roaming working and created a Nandroid (TWRP) backup at the time, you can simply restore the efs partitions from back then. Just be sure to use the latest TWRP version and make a fresh backup before you go, as there used to be a version some time ago that corrupted efs partition backups.
If you don't, well, as long as I can't read out my efs I can't tell you what to modify in there and how Maybe somebody
I think my only option is to flash the original Asus rom. It is waste time if only to turn on the data roaming.