Hi
I have an unlocked SGSII and everything is fine, I love the phone, but now I have a strange problem...
A few days ago I was in an foreign country and the phone entered in roaming. Everything went ok, I was able to use the phone normally but when I come back home my carrier name didn't change. I mean, I'm using my carrier network (not in roaming anymore) but the name didn't change!!!!
It doesn't affects the phone use but is annoying to see the wrong name of the carrier
Does anybody has a suggestion to solve this? Factory reset?
Thanks
JC
Have you tried going into Settings > Mobile Networks > Network Operators ?
Sent from my GT-I9100
fekken said:
Have you tried going into Settings > Mobile Networks > Network Operators ?
Sent from my GT-I9100
Click to expand...
Click to collapse
Yes, I did Fekken. Manual and automatic search!!! I can't my carrier's name
JC
In the same boat
Hello,
Allthough I cannot help you , i just wanted to let you know that you are not alone ....
I own a HTC One S, which yesterday since the roaming yesterday is stuck on the foreign operator name too
I can confirm that i am actually no longer roaming as my numeric Operator ID is back to "27001" which is LUXGSM , but the Operator name is still listed as "Orange F"
To make things worse , ( maybe you can check if it's the same on your phone ) if I go to manual Network selection , my starred ( Home ) Network is listed as "Orange F" , so it looks as if the phone has completely replaced the name
Everything is working , but it is certainly quite annoying to see the wrong name everywhere
Cheers,
Claude
Hi Garlfield
That's exactly what is happening with my SGS II. My real carrier is TMN (I know that because everything is working, like Internet and other services of the carrier) the name is Orange.
By the way, where did you find your Operator ID, just to be sure...
I would try tur5ning off and removing the battery for a few minutes.
If that doesn't work I would wipe the cache.
Erlanderterv said:
I would try tur5ning off and removing the battery for a few minutes.
If that doesn't work I would wipe the cache.
Click to expand...
Click to collapse
Hi
Thanks for the tip. Just removed the battery, in a few minutes I'll came back to tell if that worked
Well, the battery thing didn't work... To do wipe the cache I need to do a factory reset? My phone isn't rooted, so I don't have CWM.
Thanks
Turn off. Then go into recovery mode (Home+Volume Up+Power) Select Wipe cache by moving the highlight up and down with the volume keys and press power to select.
Then select Reboot.
Erlanderterv said:
Turn off. Then go into recovery mode (Home+Volume Up+Power) Select Wipe cache by moving the highlight up and down with the volume keys and press power to select.
Then select Reboot.
Click to expand...
Click to collapse
Thanks Erlanderterv, but that didn't work either. Still wrong carrier name after a cache wipe.
I guess I'm going to try the factory reset now...
jcustodio said:
Thanks Erlanderterv, but that didn't work either. Still wrong carrier name after a cache wipe.
I guess I'm going to try the factory reset now...
Click to expand...
Click to collapse
Download a carrier name app and type in your carrier name?
iXanza said:
Download a carrier name app and type in your carrier name?
Click to expand...
Click to collapse
Hi iXanza
That's an option, but it really doesn't solve the problem, just hide's it
Hi,
I'm running "Traffic Monitor" from RadioOpt , that app has a device tab where you can see a lot of info about your device , one of which is the Network ID
27001 is in fact LUXGSM , but shown by the phone as Orange F ....
I did some testing , as i live quite close to the belgian border
1) got to manually select network ( Here I do NOT see LUXGSM , but Orange F )
2) register on a Belgian network manually , I see the "R" popping up for roaming , and the Carrier name is properly displayed as "BEL Proximus"
3) go back to manually set network ( This time I see LUXGSM , and i thought already YESSS )
4) register on LUXGSM , the "R" disappears and the carrier name is "Orange F" again
Aaaaarrgh
I don't really want to factory reset, unless that's last option , so i'll continue searching ;-)
Hi Garfield1970
Thanks for the app. I just confirmed that my carrier's numeric code (TMN Portugal 268 06) is the one that phone is using. Now I'm absolutely sure that I'm not in roaming
Here, even if I do a manual search I never see my carrier's name, only 2 "Orange", the one from Spain and the one that's a false Orange.
I was trying to avoid the factory reset too, but I think I'm going to do it to see if it works...
JC
Woot Woot
Did I say I don't like factory resets
I managed to get mine working again , without reset or whatsoever ... YAY!
Here's what I did , bear in mind that this is what worked for a *rooted* HTC One S running ICS 4.03 stock , so I cannot guarantee it will work for you , and as usual :
<disclaimer>You do everything at your own risk!</disclaimer>
1) Connect USB Cable then go on the phone by using ADB SHELL
2) su
3) cd /data/property
4) ls -al
-rw------- root root 1 2012-06-26 16:08 persist.radio.adb_log_on
-rw------- root root 1 2012-06-26 16:09 persist.radio.clir
-rw------- root root 8 2012-06-24 15:41 persist.radio.nitz_lons_0_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_lons_1_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_lons_2_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_lons_3_0
-rw------- root root 9 2012-06-24 15:41 persist.radio.nitz_plmn_0
-rw------- root root 8 2012-06-24 15:41 persist.radio.nitz_sons_0_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_sons_1_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_sons_2_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_sons_3_0
-rw------- root root 9 2012-06-24 12:20 persist.radio.pdn.profile
-rw------- root root 0 2012-06-19 22:29 persist.service.adb.enable
-rw------- root root 2 2012-06-19 22:30 persist.sys.country
-rw------- root root 2 2012-06-19 22:30 persist.sys.language
-rw------- root root 0 2012-06-19 22:30 persist.sys.localevar
-rw------- root root 1 2012-06-26 16:08 persist.sys.profiler_ms
-rw------- root root 15 2012-06-26 16:10 persist.sys.timezone
-rw------- root root 3 2012-06-19 22:39 persist.sys.usb.config
In my case , the files : "persist.radio.nitz_lons_0_0" and "persist.radio.nitz_sons_0_0" contained the incorrect Carrier name : "Orange F" and the file persist.radio.nitz_plmn_0 contained the Network If for which it was displayed "270 01"
so for the 3 files i did the following : ( if you want to verify the contents before editing , use the <cat> command to list the contents of the files )
5) rm persist.radio.nitz_lons_0_0
( delete the file )
6) touch persist.radio.nitz_lons_0_0
( recreate empty file )
7) chmod 600 persist.radio.nitz_lons_0_0
( change the rights back to the original ones )
8) rm persist.radio.nitz_sons_0_0
9) touch persist.radio.nitz_sons_0_0
10) chmod 666 persist.radio.nitz_sons_0_0
11) rm persist.radio.nitz_plmn_0
12) touch persist.radio.nitz_plmn_0
13) chmod 666 persist.radio.nitz_plmn_0
14) ls -al
-rw------- root root 1 2012-06-26 16:08 persist.radio.adb_log_on
-rw------- root root 1 2012-06-26 16:09 persist.radio.clir
-rw------- root root 0 2012-06-26 16:05 persist.radio.nitz_lons_0_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_lons_1_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_lons_2_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_lons_3_0
-rw------- root root 0 2012-06-26 16:05 persist.radio.nitz_plmn_0
-rw------- root root 0 2012-06-26 16:05 persist.radio.nitz_sons_0_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_sons_1_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_sons_2_0
-rw------- root root 0 2012-06-24 15:41 persist.radio.nitz_sons_3_0
-rw------- root root 9 2012-06-24 12:20 persist.radio.pdn.profile
-rw------- root root 0 2012-06-19 22:29 persist.service.adb.enable
-rw------- root root 2 2012-06-19 22:30 persist.sys.country
-rw------- root root 2 2012-06-19 22:30 persist.sys.language
-rw------- root root 0 2012-06-19 22:30 persist.sys.localevar
-rw------- root root 1 2012-06-26 16:08 persist.sys.profiler_ms
-rw------- root root 15 2012-06-26 16:10 persist.sys.timezone
-rw------- root root 3 2012-06-19 22:39 persist.sys.usb.config
So now , all the concerned files were 0 byte long , and all I had to do was reboot the phone to get everything back to normal
The timestamp of the modified files indicates they were modified when I was roaming in the "Orange F" Network , I was in France at that time ....
For now , I'm happy to be back with correct display without resetting the phone , let's hope it will stay that way !
If you are not rooted , a factory reset should do the trick , as I think it clears those settings aswell from the data partition
Cheers,
Claude
Hi Claude
I'm glad you did it, but that is too much for me
I decided to root my phone and install a custom rom on it and everything is ok now, my carrier name my real carrier. I went to Spain again and when I was back to Portugal the carrier and his name changed correctly.
JC
Hi to all!
I have the same problem like explained above, but I have Samsung Galaxy S2 with GB 2.3.5 and I don't have the listed files in /data/property. So I try to find what files in my system (I have rooted phone) have the wrong carrier name. I find that the file with wrong carrier is
/data/data/com.android.providers.telephony/optable.db
So I try to delete the file (to be honest I rename the file) and reboot the phone. The optable.db file is recreated and now all is ok and work ok with correct carrier names :good:.
Regards
Damjan G.
damjang said:
Hi to all!
I have the same problem like explained above, but I have Samsung Galaxy S2 with GB 2.3.5 and I don't have the listed files in /data/property. So I try to find what files in my system (I have rooted phone) have the wrong carrier name. I find that the file with wrong carrier is
/data/data/com.android.providers.telephony/optable.db
So I try to delete the file (to be honest I rename the file) and reboot the phone. The optable.db file is recreated and now all is ok and work ok with correct carrier names.
Click to expand...
Click to collapse
I was very happy to read this post at first, as I thought I had finally solved this issue that had been bugging me for months. But alas This fix didn't work for me. I have a Galaxy W (i 8150). Also on gingerbread 2.3.x. I've had the wrong carrier name stuck since I went to the USA in the spring. I always get " Virgin" showing even though there is no such network here in the UK. I Can see i'm connected to my providers preferred network - EE. (formerly T-Mobile).
I've rooted my phone using the 'recovery mode method' and using a super-user shell gone in and deleted the optable.db file. No luck. Still says "Virgin". I checked for the other method described above and like Damjang didn't have those files. I've tried using various file explorers to search for "Virgin" but I can't find it anywhere.
Does anyone else have any thoughts or as to how to fix this pretty annoying but ultimately unimportant bug?
Update - even factory reset won't work
OK so I kept playing with it, demoving databases in the com.androis.providers.telephony directory etc. And all did a cache clearance. Ultimately I moved too many things around at once and it hosed the operating system somehow. May have been a bad unroot...
Anyway I did a factory reset. And then a restore using the backup I had made with Kies. Before I did the restore the carrier name was displaying properly for once! So I thought yay, despite the annoyance of the reset at least I solve the problem. No luck again... After the restore it reverted to saying "Virgin".
So I thought I better try to do it without the full restore but only a partial restore. So I factory reset again, and then did a restore on just contacts, messages, email etc. Nothing with settings. Damned "Virgin" still came back after a bit!
So I am thinking something wrong with the i8150 system that Samsung created. I noticed that when I did reset in the set up process I got a settings question asked with the title "SIM services" and the options of either "T-Mobile" or "Virgin". Naturally I selected T-Mobile since I have a T-Mobile SIM. I can only guess that somehow that setting selection failed to be programmed properly and that the phone defaults back to "Virgin". Must be that the handset was destined for both North American or British markets and that the system set up was just not done right. Unless I am jump;ing to wrong conclusions.
Hi to all! Today I have again the operator wrong name (after being in roaming). But I must say that now I have no more GB, but JB 4.1.2 NeatRom light 4.3 (on my SGII) and the trick to delete the /data/data/com.android.providers.telephony/optable.db and reboot for me work also in JB. I'm very disappointed that old bugs from GB is also present in JB :crying:
BTW: is there some trick to set the roaming operator priority, if I want to instruct the phone to use the roaming operator XY if possible?
Related
Very bad news.
I appear to have had an accident with /efs. Not 100% sure what I did but suspect it related to a product code change.
My SGS2 now will not show an IMEI or connect to the cell network.
I connected with /adb and saw a number of files were updated earlier today
drwxrwxr-x 5 root root 4096 Jan 1 2000 .files
drwxrwxr-x 2 radio radio 4096 Jan 1 2000 imei
-rw-rw-rw- 1 radio radio 832 Jan 1 2011 nv.log
-rw-rw-rw- 1 radio radio 1 Jan 1 2011 .nv_state
-rwx------ 1 radio radio 32 Jan 1 2011 .nv_data.bak.md5
-rwx------ 1 radio radio 2097152 Jan 1 2011 .nv_data.bak
-rwx------ 1 radio radio 32 Jan 1 2011 .nv_core.bak.md5
-rwx------ 1 radio radio 1048576 Jan 1 2011 .nv_core.bak
-rw-r--r-- 1 root root 1 Jan 1 2011 cryptprop_rebootMode
drwx------ 3 system system 4096 Jan 1 2011 dmp
-rw-r--r-- 1 system system 14 Jan 1 2011 cryptprop_persist.sys.timezone
-rw-r--r-- 1 system system 9 Jan 1 2011 cryptprop_applied_result
-rwxrwxr-- 1 radio radio 880 Jan 1 2011 redata.bin
-rw-rw-rw- 1 system system 6 Aug 12 22:43 calibration_data
-rw-rw-rw- 1 system system 256 Oct 4 15:55 edk_p
-rw-r--r-- 1 system system 3 Nov 2 01:27 cryptprop_persist.sys.language
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lockscreen.patterneverchosen
-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lockscreen.password_type
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_visible_pattern
-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lock_pattern_tactile_feedback_ena
bled
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_autolock
-rw-r--r-- 1 root root 3 Nov 2 21:08 cryptprop_securewipedata
-rwx------ 1 radio radio 32 Nov 3 17:44 nv_data.bin.md5
-rwx------ 1 radio radio 2097152 Nov 3 17:44 nv_data.bin
-rw-r--r-- 1 system system 0 Nov 3 18:02 cryptprop_onetimeboot
drwxrwx--x 5 radio system 4096 Nov 3 21:23 .
drwxr-xr-x 21 root root 0 Nov 3 21:58 ..
You can see the changes to nv_data.bin.md5 and nv_data.bin -- I have no idea what crptprop_onetimeboot is but it looks a little suspicious.
Firstly I have a copy of the above as
- a directory on my sdcard
- a dd'd image on my sdcard
- a file copy on my PC (!)
I also see I still have backup files, so with a lot of difficulty (fs kept going read only when trying to copy files, so I ended up renaming the old name to the new name)
ie
.nv_data.bak -> nv_data.bin
.nv_data.bak.md5 -> nv_data.bin.md5
This didn't work (still no service/no imei), so I removed(renamed) the .md5 file -- but it still doesn't work
so it now looks like
# ls -latr
ls -latr
drwxrwxr-x 5 root root 4096 Jan 1 2000 .files
drwxrwxr-x 2 radio radio 4096 Jan 1 2000 imei
-rwx------ 1 radio radio 32 Jan 1 2011 nv_data.bin.md5.orig
-rwx------ 1 radio radio 2097152 Jan 1 2011 nv_data.bin
-rw-rw-rw- 1 radio radio 832 Jan 1 2011 nv.log
-rw-rw-rw- 1 radio radio 1 Jan 1 2011 .nv_state
-rwx------ 1 radio radio 32 Jan 1 2011 .nv_core.bak.md5
-rwx------ 1 radio radio 1048576 Jan 1 2011 .nv_core.bak
-rw-r--r-- 1 root root 1 Jan 1 2011 cryptprop_rebootMode
drwx------ 3 system system 4096 Jan 1 2011 dmp
-rw-r--r-- 1 system system 14 Jan 1 2011 cryptprop_persist.sys.timezone
-rw-r--r-- 1 system system 9 Jan 1 2011 cryptprop_applied_result
-rwxrwxr-- 1 radio radio 880 Jan 1 2011 redata.bin
-rw-rw-rw- 1 system system 6 Aug 12 22:43 calibration_data
-rw-rw-rw- 1 system system 256 Oct 4 15:55 edk_p
-rw-r--r-- 1 system system 3 Nov 2 01:27 cryptprop_persist.sys.language
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lockscreen.patterneverchosen
-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lockscreen.password_type
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_visible_pattern
-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lock_pattern_tactile_feedback_ena
bled
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_autolock
-rw-r--r-- 1 root root 3 Nov 2 21:08 cryptprop_securewipedata
-rwx------ 1 radio radio 32 Nov 3 17:44 nv_data.bin.md5.bk
-rwx------ 1 radio radio 2097152 Nov 3 17:44 nv_data.bin.bk
-rw-rw-rw- 1 root root 0 Nov 3 20:55 p
drwxrwx--x 5 radio system 4096 Nov 3 21:48 .
-rw-r--r-- 1 system system 0 Nov 3 21:52 cryptprop_onetimeboot
drwxr-xr-x 21 root root 0 Nov 3 21:58 ..
#
[/FONT]
I DID NOT BACKUP EFS beforehand (only just learnt I need to) and know this may now be screwed, but I'm still hopeful I have the original file and just made a silly error.
I could also
- try recreating the whole fs and copying files back
- checking the prod code within the rom (but why?)
- flashing original firmware
- modifying the dd'd image *offline*, swapping the files, and dd'ing the image back
Any advice. PLEASE....
if you have a backup the easiest way I have found is to use root explorer.
go in to the /efs folder, set to read/write, mark everything and delete (not scrictly necessary simply copying over will work) but if you have been tinkering probably better.
then paste all the back up files and folders in
finally reboot (in my experience when something has gone wrong even this is not necessary)
Root explorer is worth every penny
and keep multiple backup's of your /efs on different drives
If this does not work you are screwed. The file contains your IMEI encrypted and the only way to get that restored is by returning it.
oh I just realised you are saying the back up you have is only of it in the current state?
If that's the case you are probably screwed, have you ever used any apps like nitrality or any unlocking tools? they will create copies of your efs folder on the scard in various locations. have you run a file seach on you sdcard to see if there is any copies at all?
if you have no backups of this folder then I think you will find its a return to manufacturer / sevice centre / provider issue.
I *think* I have restored the files -- and the dates look reasonable, as if they were the originals.
I've now flashed an old ROM (KE5) for good measure, but still no signal
One discrepancy I did notice is that after installing a rom there was some bootup message about csc and XEU when copying files.
My original sales code was VOD (UK vodafone). I had then run XEU firmware and just recently tried to set the sales code to XEU using a *# code. I subsequently flashed back to vodafone firmware today.
So somewhere there's a lingering reference to XEU -- this prod code incompatability could be causing the error?
I definately feel I should have the data to fix this -- after all I have the encrypted file, but am not quite sure of all the factors involved (one being "you're stuffed I know")
type *#06# this should display you IMEI number
if this does not match your IMEI from the box then you have not fixed this
if it shows all zeros or 004999010640000 then you are on a generic IMEI number
strangely when I screwed mine up and got the generic one above I was still able to use mine with a vodafone (UK) sim but not an orange on
if this is the case, and there is no efs backup prior to this you might well be screwed.
if this backup is all you have an you believe the .bak file is intact then I believe you will find solutions for deleting the primary version of the file and keeping only the backups and rebooting
the log file should give you more information on how successful this was, but if this was the result of flashing you probably overwrote both primary and backup
*#1234# is returning a reasonable CSC I9100VODKE2
Checking the nv data files, it appears
- the new ones modded today contain XEU
- the original ones contain VOD
This is consistent with what happened, so I am still confused why the renamed original files do not work, and why there's a reference to multi-csc XEU during bootup.
Some remnant of XEU?
*#06# is currently showing blank -- but those .bak files looked fine.
Annoyed and frustrated...
In that case I would try deleting nv_data.bin and nv_data.m5 and rebooting
(assuming you have copies of everything
with just nv_data.bak nv_data.bak.md5
At least with the SGS1 this would work provided those bak files are the originals but the nv.log file will tell you more after the boot.
HOWEVER the SGSII has a lot more in this folder and I do not claim to fully understand them all but if you have a back up it's worth a shot
planetf1 said:
*#1234# is returning a reasonable CSC I9100VODKE2
Checking the nv data files, it appears
- the new ones modded today contain XEU
- the original ones contain VOD
This is consistent with what happened, so I am still confused why the renamed original files do not work, and why there's a reference to multi-csc XEU during bootup.
Some remnant of XEU?
Click to expand...
Click to collapse
Took some inspiration from http://www.communityhosting.net/sgsunlock/i9000.html and decided to check permissions & recreation of md5.
md5 wasn't recreated, so no matter, I had a backup. that is restored, but I don't know if the .bak files are needed. Yet trying to create them I get:
# mv nv_data.bin.md5.orig nv_data.bin.md5
mv nv_data.bin.md5.orig nv_data.bin.md5
# cp nv_data.bin .nv_data.bak
cp nv_data.bin .nv_data.bak
cp: write error: Read-only file system
#
This isn't a space issue.
There could be another cause -- /efs/imei/mps_info.dat contains the 3 characters "XEU" even though the file is dated Jan 2011
So either
- the date has been manually fudged
OR
- the code always was XEU -- unlikely.
I'm currently working on the basis that fundamentally the IMEI is intact, that the original nv_data.bin is intact & that the phone is validating the CSC in mps_info.dat (XEU) against nv_data.bin (VOD) and failing.
Though this wouldn't explain why before the fix, with XEU in the nv_data.bin, it wasn't working
Unless the issue is the filesystem itself. could it be corrupt? Is this in fact why it switched to R/O mode each time? I've tried multiple kernels including insecure. surely they wouldn't all "protect" this fs.
But if this is the case where is fsck? maybe I need to copy the fs image to another linux box with ext4 & inspect/correct before shipping back and dd'ing
Continuing.
Found /system/bin/e2fsck -- ran this against /efs with
# /system/bin/e2fsck /dev/block/mmcblk0p1
/system/bin/e2fsck /dev/block/mmcblk0p1
e2fsck 1.41.11 (14-Mar-2010)
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determini
ng whether /dev/block/mmcblk0p1 is mounted.
/dev/block/mmcblk0p1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create<y>? y
yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(3202--3203) +4104
Fix<y>? yes
/dev/block/mmcblk0p1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p1: 60/1280 files (1.7% non-contiguous), 2188/5120 blocks
**** >>> I NOW HAVE AN IMEI <<< ****
AND SIGNAL
LOGGED ONTO VODAFONE
WOOOHAY.
THIS HAS BEEN FUN. LOOK AND LEARN..
and seriously thanks to all the other articles and some moral support here tonight.
Going to put back proper firmware , remove dodgy kernels and GET A BIG BEER OR THREE
planetf1 said:
Continuing.
Going to put back proper firmware , remove dodgy kernels and GET A BIG BEER OR THREE
Click to expand...
Click to collapse
and make several backups of the /efs folder in its current state one would assume
Phone seems working. restoring over a HSPA connection happily, recognized voda sim.
now reinstalling titanium backup and copying down from dropbox...
The final step was restoring from titanium backup.
I had erased my sdcard -- though my backup was on dropbox.
However titanium backup is awful at copying files to/from dropbox -- as is IMO the phone when in "phone/kies" mode.
Finally I simply copied the dropbox directory back in USB debug=mass storage mode which was quick and reliable -- and then restored most items en-masse (I have a pro license).
For the record so far phone is fine - and indeed I've since run a new efs backup
The key takeaways from this are
* Backup efs and save it somewhere offline
* get titanium backup pro. it's good (better if it backed up efs too!)
* usb mass storage mode is the most reliable way for file xfer
* backup efs (again)
* don't get complacent
And of course if you do get a similar problem to mine
a) take a backup of efs with dd if=/dev/mmcXXX of=/mnt/scard/myefs.img (check name - I forget)
b) copy files you can to sdcard
c) copy both of this to a seperate pc
d) Just try running fsck (as above) - If I'd done this sooner I'd have saved hours. I should have gone with the obvious -- I've seen this on enough linux systems in the past to know what was happening but was thrown by no kernel messages.
Thanks for letting us know, might be a nice reference for future problems, especially the filesystem check.
Writing about it also helped keep me sane.giving up and hitting the beer was becoming increasingly attractive.
I do think making the warning about efs clearer would help.backup really should be a must at the earliest opportunity
Sent from my GT-I9100 using Tapatalk
Another thought.do unmount /efs before fsck
Sent from my GT-I9100 using Tapatalk
Unable to restore
I know I had a valid IMEI during the last week or so.
I have flashed several ROM's during the last month.
Last night lost IMEI
Now , no matter what I try, I can't seem to restore my IMEI. I have the fake one that ends in a bunch of zero''s
My SDCARD has a folder called EFS_BACKUP with multiple efs_xxxxxxx.tar.gz files in it. If I extract any of these and try to restore them to the /EFS folder I still have the fake IMEI number.
Please help - I didn't understand all the adb code in this post
Hi there,
/efs is fairly new to me too, to be honest it took hours of careful rooting before I gained some useful knowledge in how that area works.
-- what I would suggest before *anything else* is to copy anything you do have left in /efs. You will need to be root to do this. I found the gui root explorer type tools a bit clunky so I used the android SDK (adb is one of the tools in this package) to help. IF YOU NEED HELP WITH THIS SAY. You need to copy the files to multiple places for safety. Someone OFF your phone, ie on a PC. This is just in case things get worse. Do the same with any of those .gz backups you have. Maybe you'll need them *if* you make things worse...
If you're familiar with linux/unix systems this is all fairly easy, but if you're not it can be quite scary. For example you have to be able to write to /efs as well as list files and move them around. One wrong step and you could make things worse.
If you're unsure perhaps you could find a friend who knows *nix well to help you out. The bottom line is that you need to
a) ensure the right files are in there
b) The filesystem itself was intact
I definately suffered from b -- less sure about a.
What you need to do will depend a fair bit on what files you find in there, and what dates they are.
You said you had some backup files. Are you sure you have some from before the problem started? Can you look inside those backup files (I think winzip or similar will expand them for you). WIthout divoluging the actual contents (since you don't want to share your IMEI with anyone), is there an nv_data.bin file in there? Out of all the files it seems to be the most critical. When's it dated (mine was Jan 2011). If you cant' find that file how about .nv_data.bak - is that a good size, and again an old one.
If you have either of these -- even without anything else I think you can probably recover.
If you can get up and running with adb, a good start would be
adb shell
ls -laR /efs
Thank you very much, fsck method fixed my efs. Phone just broke it while doing nothing :/
I love you
You just saved my Galaxy S2
Yay. Brilliant news
Must be on VRUEMJ7 build and unrooted first!
Give these two a try and let us know which one works.
mod edit, vroot and kingo links removed per admin decision, site wide.
thought VROOT was a scam...
Yep
open1your1eyes0 said:
Just wanted to confirm you were on 100% stock not-rooted VRUEMJ7 build before?
Click to expand...
Click to collapse
Yes, its 100% stock. In fact, I had just reloaded to stock using the Verizon Repair tool becuase of my last failed attempt.
View attachment 2371104
TheJumpingBean said:
Yes, its 100% stock. In fact, I had just reloaded to stock using the Verizon Repair tool becuase of my last failed attempt.
View attachment 2371104
Click to expand...
Click to collapse
Excellent! :good:
Let's get a few more success posts and see which is the preferred method and I will make an official post about it.
???
wonger007 said:
thought VROOT was a scam...
Click to expand...
Click to collapse
This worked great for me. What do you mean by scam exactly?
---------- Post added at 12:24 PM ---------- Previous post was at 12:20 PM ----------
Also, this does not trip the Knox counter.
wonger007 said:
thought VROOT was a scam...
Click to expand...
Click to collapse
I heard the same. I would like to hear more feed back before trying it.
TheJumpingBean said:
Im trying to update the SU Binary, and it keeps failing. Is there a way to do this manually?
Click to expand...
Click to collapse
Possibly not since SELinux is likely blocking it. You might be able to do this with adb shell.
Also be aware you may have malware on your PC/phone now.
TheJumpingBean said:
Im trying to update the SU Binary, and it keeps failing. Is there a way to do this manually?
Click to expand...
Click to collapse
the process completed using the first method, but i dont see the chinese SU installed in my app drawer and no root access. I was able to install Super Su but it will not update as stated above.
Hmmm
joderme said:
Possibly not since SELinux is likely blocking it. You might be able to do this with adb shell.
Also be aware you may have malware on your PC/phone now.
Click to expand...
Click to collapse
Im still confused. The site that the file comes from is well known, has change logs and everything... Doesnt seem like it would be malware. Weird.
VRoot works, but like most are experiencing, cannot edit certain system files due to that pesky SELinux service. Maybe freezing the app/service with Titanium Backup would help.
However, I decided to use Kingo, seeing as everyone else had some success with VRoot, and I don't get any problems editing system files. Works perfectly. I used the emergency recovery wipe file and cleared the entire phone to MJ7, but I don't know how I stopped getting those notifications. I was actually getting them even when I didn't have root.
Anyone have the SuperSU Binary
joderme said:
Possibly not since SELinux is likely blocking it. You might be able to do this with adb shell.
Also be aware you may have malware on your PC/phone now.
Click to expand...
Click to collapse
Does anyone have the su binary for the latest SuperSU? Im willing to give it a try in shell.
Thx,
Maria
Also: Looks like the SU application is: com.noshufou.android.su-1.apk in the /data/app directory.
dothog said:
VRoot works, but like most are experiencing, cannot edit certain system files due to that pesky SELinux service. Maybe freezing the app/service with Titanium Backup would help.
However, I decided to use Kingo, seeing as everyone else had some success with VRoot, and I don't get any problems editing system files. Works perfectly. I used the emergency recovery wipe file and cleared the entire phone to MJ7, but I don't know how I stopped getting those notifications. I was actually getting them even when I didn't have root.
Click to expand...
Click to collapse
Did Kingo trip the knox warranty trigger?
Same results here. VROOT was successful, however SuperSU cannot update it's binaries.
Kingo
dothog said:
VRoot works, but like most are experiencing, cannot edit certain system files due to that pesky SELinux service. Maybe freezing the app/service with Titanium Backup would help.
However, I decided to use Kingo, seeing as everyone else had some success with VRoot, and I don't get any problems editing system files. Works perfectly. I used the emergency recovery wipe file and cleared the entire phone to MJ7, but I don't know how I stopped getting those notifications. I was actually getting them even when I didn't have root.
Click to expand...
Click to collapse
Did you reroot with Kingo? Didn't you try the other one first?
joderme said:
Did Kingo trip the knox warranty trigger?
Click to expand...
Click to collapse
No, not for me. Knox still shows 0x0 so far. I guess its where I have a totally clean slate. Im really thinking most people's problems is due to them using incomplete wipes, or by using recovery-done factory resets. Safestrap's factory reset tries to keep root, and itself, intact, so anyone who used that in preparation for update to MJ7 might have problems.
---------- Post added at 07:10 PM ---------- Previous post was at 07:05 PM ----------
TheJumpingBean said:
Did you reroot with Kingo? Didn't you try the other one first?
Click to expand...
Click to collapse
Yeah, I did VRoot, then reflashed the emergency recovery with Odin, then tried again with Kingo. I did that because I didn't see any people bothering with Kingo because VRoot worked fine for the most part.
I've just asked the mods to delete this thread as it's very likely causing people to infect their PCs and their phones.
VRoot and Kingo install a SuperSU program that has a network backdoor to China. You've given someone full control of your phone.
They also modify your PC's IE configuration, apparently for the same thing.
Why you can't replace the hacked SuperSU is because the malware won't let you.
These rooting programs may work, but they're closed-source and have behavior that can't be explained.
If I had installed this mistakenly, I'd wipe my phone *and* my PC and reinstall from scratch.
k1mu said:
I've just asked the mods to delete this thread as it's very likely causing people to infect their PCs and their phones.
VRoot and Kingo install a SuperSU program that has a network backdoor to China. You've given someone full control of your phone.
They also modify your PC's IE configuration, apparently for the same thing.
Why you can't replace the hacked SuperSU is because the malware won't let you.
These rooting programs may work, but they're closed-source and have behavior that can't be explained.
If I had installed this mistakenly, I'd wipe my phone *and* my PC and reinstall from scratch.
Click to expand...
Click to collapse
I think the less paranoid explanation is that the su app has an auto-update feature and since the app isn't hosted in the Play Store, a connection to a chinese server doesn't see all that unexpected.
Do not install
At this point I have every reason to believe there is a huge threat with rooting this way. The su binary starts a listening server and remains connected:
unix 3 [ ] STREAM CONNECTED 5629 3127/su /dev/com.mgyun.shua.su.daemon/server
unix 3 [ ] STREAM CONNECTED 11730 3118/.suv
---------- Post added at 01:55 PM ---------- Previous post was at 01:52 PM ----------
[email protected]:/dev # ls -la
ls -la
---------- root root 0 1970-03-11 22:45 .coldboot_done
drwx--x--x system system 1970-03-11 22:45 .secure_storage
-rw-r--r-- root root 66560 1970-03-11 22:45 __properties__
crw-rw-r-- system radio 10, 25 1970-03-11 22:45 alarm
crw-rw---- adb adb 10, 30 1970-03-11 22:45 android_adb
crw-rw-rw- root root 10, 21 1970-03-11 22:45 ashmem
crw------- nfc nfc 10, 34 1970-03-11 22:45 bcm2079x
crw-rw-rw- root root 10, 22 1970-03-11 22:45 binder
drwxr-xr-x root root 2013-11-04 13:26 block
crw------- bluetooth bluetooth 10, 224 1970-03-11 22:45 btlock
drwxr-xr-x root root 1970-03-11 22:45 bus
crw------- root root 10, 28 1970-03-11 22:45 ccid_bulk
crw------- root root 10, 29 1970-03-11 22:45 ccid_ctrl
drwxrwx--- u0_a247 u0_a247 2013-11-04 13:26 com.mgyun.shua.su
drwxr-xr-x root root 2013-11-04 13:43 com.mgyun.shua.su.daemon
crw------- root root 5, 1 1970-03-11 22:45 console
In all fairness that could be an update daemon.
DroidHaxxor said:
At this point I have every reason to believe there is a huge threat with rooting this way. The su binary starts a listening server and remains connected:
unix 3 [ ] STREAM CONNECTED 5629 3127/su /dev/com.mgyun.shua.su.daemon/server
unix 3 [ ] STREAM CONNECTED 11730 3118/.suv
---------- Post added at 01:55 PM ---------- Previous post was at 01:52 PM ----------
[email protected]:/dev # ls -la
ls -la
---------- root root 0 1970-03-11 22:45 .coldboot_done
drwx--x--x system system 1970-03-11 22:45 .secure_storage
-rw-r--r-- root root 66560 1970-03-11 22:45 __properties__
crw-rw-r-- system radio 10, 25 1970-03-11 22:45 alarm
crw-rw---- adb adb 10, 30 1970-03-11 22:45 android_adb
crw-rw-rw- root root 10, 21 1970-03-11 22:45 ashmem
crw------- nfc nfc 10, 34 1970-03-11 22:45 bcm2079x
crw-rw-rw- root root 10, 22 1970-03-11 22:45 binder
drwxr-xr-x root root 2013-11-04 13:26 block
crw------- bluetooth bluetooth 10, 224 1970-03-11 22:45 btlock
drwxr-xr-x root root 1970-03-11 22:45 bus
crw------- root root 10, 28 1970-03-11 22:45 ccid_bulk
crw------- root root 10, 29 1970-03-11 22:45 ccid_ctrl
drwxrwx--- u0_a247 u0_a247 2013-11-04 13:26 com.mgyun.shua.su
drwxr-xr-x root root 2013-11-04 13:43 com.mgyun.shua.su.daemon
crw------- root root 5, 1 1970-03-11 22:45 console
Click to expand...
Click to collapse
if we uninstall the Chinese SU app is the phone clean.. or do i need a full wipe?
Also my PC appears to RUN OK. looking for any malware but don't see any.
DroidHaxxor said:
At this point I have every reason to believe there is a huge threat with rooting this way. The su binary starts a listening server and remains connected:
unix 3 [ ] STREAM CONNECTED 5629 3127/su /dev/com.mgyun.shua.su.daemon/server
unix 3 [ ] STREAM CONNECTED 11730 3118/.suv
---------- Post added at 01:55 PM ---------- Previous post was at 01:52 PM ----------
[email protected]:/dev # ls -la
ls -la
---------- root root 0 1970-03-11 22:45 .coldboot_done
drwx--x--x system system 1970-03-11 22:45 .secure_storage
-rw-r--r-- root root 66560 1970-03-11 22:45 __properties__
crw-rw-r-- system radio 10, 25 1970-03-11 22:45 alarm
crw-rw---- adb adb 10, 30 1970-03-11 22:45 android_adb
crw-rw-rw- root root 10, 21 1970-03-11 22:45 ashmem
crw------- nfc nfc 10, 34 1970-03-11 22:45 bcm2079x
crw-rw-rw- root root 10, 22 1970-03-11 22:45 binder
drwxr-xr-x root root 2013-11-04 13:26 block
crw------- bluetooth bluetooth 10, 224 1970-03-11 22:45 btlock
drwxr-xr-x root root 1970-03-11 22:45 bus
crw------- root root 10, 28 1970-03-11 22:45 ccid_bulk
crw------- root root 10, 29 1970-03-11 22:45 ccid_ctrl
drwxrwx--- u0_a247 u0_a247 2013-11-04 13:26 com.mgyun.shua.su
drwxr-xr-x root root 2013-11-04 13:43 com.mgyun.shua.su.daemon
crw------- root root 5, 1 1970-03-11 22:45 console
In all fairness that could be an update daemon.
Click to expand...
Click to collapse
That's not a listening network server, it's a local RPC daemon. That may be how the su program talks to the new SuperSU program.
What do you see if you try
$ netstat -an | grep LISTEN
That will show you any existing network listeners that anyone could connect to.
$ netstat -an | grep ESTAB
will show you established connections.
Hi,
recently I tried to make my MP T2 a bit smoother so I've decide to go with a root, clear some apps and maybe oc the cpu. So I've unlocked the bootlader, ported TWRP and finally rooted the device but I've stayed with stock rom (of course couple of times I had that feeling that now i have a nice plant pad).
Everything was looking great but at some point my WIFI got broken and I don't really know when, if it was after unlocking bootloader, after modifying it or after flashing the TWRP recovery. Currently when I click on wifi it doesn't turn on, it's just grayed and the MAC Address has changed to 02:00:00:00:00:00. I am out of ideas so maybe someone will be able to give me a hint, things that I've tried were:
taking out the sim card and rebooting
wiping caches
checking for the WCNSS_qcom_wlan_nv.bin file in the /persist (I've went through it with a hex editor and tried to find my MAC address but I don't see anything looking like a MAC)
installing stock boot.img and recovery.img extracted from the official firmware.
I've found 3 different MAC addresses trails that could be mine
EMUI Recovery, in EMUI 4 I am able to boot into recovery (even though I have TWRP) and there's an option to download and restore the firmware, here my WIFI starts and connects to my home network and I was able to check the MAC with fing.
/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini Intf0MacAddress
logcat mac_param
From the logcat (bellow) it seems that the driver wasn't loaded but I don't have a clue why. Especially that it's being loaded fine in the recovery.
I would appreciate for any hints.
Additional info:
Content of /persist is as follows:
Code:
-rw------- bluetooth bluetooth 9 1970-01-01 01:00 .bt_nv.bin
-rw-rw-r-- system system 128 1970-01-01 15:29 .sn.bin
-rw------- system system 3 1970-01-01 12:23 RUNIN.FLG
-rw-r--r-- root root 31723 2016-10-11 14:10 WCNSS_qcom_wlan_nv.bin
-rw-r--r-- root root 10419 2016-10-11 14:10 WCNSS_wlan_dictionary.dat
-rw------- system system 12 1970-01-01 01:03 acc_avg
drwxr-xr-x root root 2016-10-11 14:10 aost
drwx------ system system 1970-01-01 01:00 data
drwxrwx--- system graphics 1970-01-01 01:00 display
-rwx------ root root 1 1970-01-01 21:32 log_flag
drwx------ root root 1970-01-01 01:00 lost+found
-rw------- system system 2 1970-01-01 01:04 prox_avg
LogCat:
Code:
I/ToolBoxView( 1535): onItemClick name=com.android.systemui.statusbar.toolbox.control.WifiTracker
I/ConnectPermission( 1221): allowOpenWifi blocked:false
D/WifiService( 1221): setWifiEnabled: true pid=1535, uid=10024, name=com.android.systemui
D/WifiHW ( 1221): Check driver status: not loaded
I/ ( 1221): hw_wifi_get_mac enter;
E/ ( 1221): get_decryption_wifi_mac:decrypt_wifi_mac in.
D/OEMINFO_NVM_SERVER( 262): Accept connection from pid 1221 (******), uid: 1000, gid: 1000
D/OEMINFO_NVM_SERVER( 262): Receive: opr = 2, idx = 52, len = 128, name()
I/OEMINFO_NVM_CORE( 262): compat_oeminfo_read: version v6
E/BD.Reporter( 1535): Can't getService HwBDService
I/OEMINFO_NVM_CORE( 262): find oeminfo device /dev/block/mmcblk0p9
I/OEMINFO_NVM_CORE( 262): read oeminfo 52, offset 0x33000, total byte: 128
E/OEMINFO_NVM_SERVER( 262): pid 1221, opration oeminfo_read OK
E/ ( 1221): hw_wifi_get_mac:read nv and decrypt mac successfully.
E/ ( 1221): mac_check enter mac is:208;
E/WifiHW ( 1221): qcom_wifi_load_customcode domain_param ok, value is 1;
E/WifiHW ( 1221): hw_wifi_load_driver mudule_arg is mac_param=D0:XX:XX:XX:XX:XX country_code=DE domain_param=1 ;
E/WifiHW ( 1221): get_driver_debug_level open the config file:data/misc/wifi/wifi_log_level.conf failed
W/WifiHW ( 1221): load modle :/system/lib/modules/wlan.ko mac_param=D0:XX:XX:XX:XX:XX country_code=DE domain_param=1 module_debug_param=
E/WifiStateMachine( 1221): Failed to load driver
W/ContextImpl( 1221): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:869 com.android.server.wifi.WifiStateMachine.startWifiFailed:3877 com.android.server.wifi.WifiStateMachine.access$4600:171 com.android.server.wifi.WifiStateMachine$InitialState.processMessage:6052 com.android.internal.util.StateMachine$SmHandler.processMsg:968
I/SendBroadcastPermission( 1221): action:com.android.server.wifi.action.START_WIFI_FAILED, mPermissionType:0
Fixed
In the end I've re-flashed the stock rom through dload and WIFI started to work. Formated userdata as it was encrypted went into bootloop, flashed TWRP and then SuperSu. It seems that supersu flash fixes userdata partition which made the phone go out of loop so now I have WIFI and Root :victory:. Time for kernel tweaks to ramp up the cpu limits . Qualcomm claims this cpu should be working at 1.7 while it's working on 1.5 so it's underclocked.
genesiscoupe said:
In the end I've re-flashed the stock rom through dload and WIFI started to work. Formated userdata as it was encrypted went into bootloop, flashed TWRP and then SuperSu. It seems that supersu flash fixes userdata partition which made the phone go out of loop so now I have WIFI and Root :victory:. Time for kernel tweaks to ramp up the cpu limits . Qualcomm claims this cpu should be working at 1.7 while it's working on 1.5 so it's underclocked.
Click to expand...
Click to collapse
Is there any custom ROMs for our tablet??
huawei mediapad t2-8 pro
Thanks
Hi,
This is actually my first post/reply. I was wondering if you could let me know which twrp you flashed? I tried the one for the t2 7 pro but it did not work.
Thanks I appreciate it.
genesiscoupe said:
Hi,
recently I tried to make my MP T2 a bit smoother so I've decide to go with a root, clear some apps and maybe oc the cpu. So I've unlocked the bootlader, ported TWRP and finally rooted the device but I've stayed with stock rom (of course couple of times I had that feeling that now i have a nice plant pad).
Everything was looking great but at some point my WIFI got broken and I don't really know when, if it was after unlocking bootloader, after modifying it or after flashing the TWRP recovery. Currently when I click on wifi it doesn't turn on, it's just grayed and the MAC Address has changed to 02:00:00:00:00:00. I am out of ideas so maybe someone will be able to give me a hint, things that I've tried were:
taking out the sim card and rebooting
wiping caches
checking for the WCNSS_qcom_wlan_nv.bin file in the /persist (I've went through it with a hex editor and tried to find my MAC address but I don't see anything looking like a MAC)
installing stock boot.img and recovery.img extracted from the official firmware.
I've found 3 different MAC addresses trails that could be mine
EMUI Recovery, in EMUI 4 I am able to boot into recovery (even though I have TWRP) and there's an option to download and restore the firmware, here my WIFI starts and connects to my home network and I was able to check the MAC with fing.
/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini Intf0MacAddress
logcat mac_param
From the logcat (bellow) it seems that the driver wasn't loaded but I don't have a clue why. Especially that it's being loaded fine in the recovery.
I would appreciate for any hints.
Additional info:
Content of /persist is as follows:
Code:
-rw------- bluetooth bluetooth 9 1970-01-01 01:00 .bt_nv.bin
-rw-rw-r-- system system 128 1970-01-01 15:29 .sn.bin
-rw------- system system 3 1970-01-01 12:23 RUNIN.FLG
-rw-r--r-- root root 31723 2016-10-11 14:10 WCNSS_qcom_wlan_nv.bin
-rw-r--r-- root root 10419 2016-10-11 14:10 WCNSS_wlan_dictionary.dat
-rw------- system system 12 1970-01-01 01:03 acc_avg
drwxr-xr-x root root 2016-10-11 14:10 aost
drwx------ system system 1970-01-01 01:00 data
drwxrwx--- system graphics 1970-01-01 01:00 display
-rwx------ root root 1 1970-01-01 21:32 log_flag
drwx------ root root 1970-01-01 01:00 lost+found
-rw------- system system 2 1970-01-01 01:04 prox_avg
LogCat:
Code:
I/ToolBoxView( 1535): onItemClick name=com.android.systemui.statusbar.toolbox.control.WifiTracker
I/ConnectPermission( 1221): allowOpenWifi blocked:false
D/WifiService( 1221): setWifiEnabled: true pid=1535, uid=10024, name=com.android.systemui
D/WifiHW ( 1221): Check driver status: not loaded
I/ ( 1221): hw_wifi_get_mac enter;
E/ ( 1221): get_decryption_wifi_mac:decrypt_wifi_mac in.
D/OEMINFO_NVM_SERVER( 262): Accept connection from pid 1221 (******), uid: 1000, gid: 1000
D/OEMINFO_NVM_SERVER( 262): Receive: opr = 2, idx = 52, len = 128, name()
I/OEMINFO_NVM_CORE( 262): compat_oeminfo_read: version v6
E/BD.Reporter( 1535): Can't getService HwBDService
I/OEMINFO_NVM_CORE( 262): find oeminfo device /dev/block/mmcblk0p9
I/OEMINFO_NVM_CORE( 262): read oeminfo 52, offset 0x33000, total byte: 128
E/OEMINFO_NVM_SERVER( 262): pid 1221, opration oeminfo_read OK
E/ ( 1221): hw_wifi_get_mac:read nv and decrypt mac successfully.
E/ ( 1221): mac_check enter mac is:208;
E/WifiHW ( 1221): qcom_wifi_load_customcode domain_param ok, value is 1;
E/WifiHW ( 1221): hw_wifi_load_driver mudule_arg is mac_param=D0:XX:XX:XX:XX:XX country_code=DE domain_param=1 ;
E/WifiHW ( 1221): get_driver_debug_level open the config file:data/misc/wifi/wifi_log_level.conf failed
W/WifiHW ( 1221): load modle :/system/lib/modules/wlan.ko mac_param=D0:XX:XX:XX:XX:XX country_code=DE domain_param=1 module_debug_param=
E/WifiStateMachine( 1221): Failed to load driver
W/ContextImpl( 1221): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:869 com.android.server.wifi.WifiStateMachine.startWifiFailed:3877 com.android.server.wifi.WifiStateMachine.access$4600:171 com.android.server.wifi.WifiStateMachine$InitialState.processMessage:6052 com.android.internal.util.StateMachine$SmHandler.processMsg:968
I/SendBroadcastPermission( 1221): action:com.android.server.wifi.action.START_WIFI_FAILED, mPermissionType:0
Click to expand...
Click to collapse
Hello how can I root my phone Huawei JDN-L01?
Please teach me thank you!
Hello xda
Seems like I cannot erase all partitions properly. My phone have random reboots problem, and once it boots then it gets stuck at bootloader, so on every reboot I have to re-install OS. It does not matter whichever rom I try it still have same problem.
So what I tried is to erase all partitions in fastboot by command fastboot erase cache, system, etc etc and all other with success.
Then I use FlashOne1.9 to restore my phone completely to zero using QFIL with success installation but phone still kept rebooting, I tried to goto Recovery and here I still see TeamSpain TWRP 3.0.2 installed.
What can be wrong?
I erased all partitions manually + QFIL restore I thought completely erases everything but as I see still no.
Is there a way where I can delete all partitions and then recreate them one by one so there is not even a bit of any preinstalled softwares left.
I read deleting partitions in fastboot but felt it can be risky so I thought to ask a second opinion before proceeding.
Thank you
craftsvision said:
Hello xda
Seems like I cannot erase all partitions properly. My phone have random reboots problem, and once it boots then it gets stuck at bootloader, so on every reboot I have to re-install OS. It does not matter whichever rom I try it still have same problem.
So what I tried is to erase all partitions in fastboot by command fastboot erase cache, system, etc etc and all other with success.
Then I use FlashOne1.9 to restore my phone completely to zero using QFIL with success installation but phone still kept rebooting, I tried to goto Recovery and here I still see TeamSpain TWRP 3.0.2 installed.
What can be wrong?
I erased all partitions manually + QFIL restore I thought completely erases everything but as I see still no.
Is there a way where I can delete all partitions and then recreate them one by one so there is not even a bit of any preinstalled softwares left.
I read deleting partitions in fastboot but felt it can be risky so I thought to ask a second opinion before proceeding.
Thank you
Click to expand...
Click to collapse
here´s the patition table, if it is of any use for you...
lrwxrwxrwx 1 root root 16 Jan 1 00:12 aboot -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 Jan 1 00:12 abootbak -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 Jan 1 00:12 apdp -> /dev/block/sde29
lrwxrwxrwx 1 root root 16 Jan 1 00:12 bluetooth -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 Jan 1 00:12 boot -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 Jan 1 00:12 bootconfig -> /dev/block/sdf7
lrwxrwxrwx 1 root root 15 Jan 1 00:12 cache -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 Jan 1 00:12 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlib -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlib64 -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlib64bak -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlibbak -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 Jan 1 00:12 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 Jan 1 00:12 devcfg -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 Jan 1 00:12 devcfgbak -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 Jan 1 00:12 devinfo -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 Jan 1 00:12 dip -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 Jan 1 00:12 dpo -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 Jan 1 00:12 dsp -> /dev/block/sde13
lrwxrwxrwx 1 root root 15 Jan 1 00:12 factory -> /dev/block/sdf6
lrwxrwxrwx 1 root root 15 Jan 1 00:12 frp -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Jan 1 00:12 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 Jan 1 00:12 fsg -> /dev/block/sde7
lrwxrwxrwx 1 root root 15 Jan 1 00:12 fsg_gap -> /dev/block/sde8
lrwxrwxrwx 1 root root 15 Jan 1 00:12 hyp -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 Jan 1 00:12 hypbak -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 Jan 1 00:12 kernellog -> /dev/block/sdf14
lrwxrwxrwx 1 root root 16 Jan 1 00:12 keymaster -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 Jan 1 00:12 keymasterbak -> /dev/block/sde24
lrwxrwxrwx 1 root root 15 Jan 1 00:12 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letvconfig -> /dev/block/sdf10
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letveui -> /dev/block/sdf11
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letvreserve -> /dev/block/sdf13
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letvsecure -> /dev/block/sdf12
lrwxrwxrwx 1 root root 16 Jan 1 00:12 mdtp -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 Jan 1 00:12 misc -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Jan 1 00:12 modem -> /dev/block/sde12
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst1_gap -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst2_gap -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 Jan 1 00:12 msadp -> /dev/block/sde30
lrwxrwxrwx 1 root root 15 Jan 1 00:12 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 Jan 1 00:12 pmic -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 Jan 1 00:12 pmicbak -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 Jan 1 00:12 recovery -> /dev/block/sde20
lrwxrwxrwx 1 root root 15 Jan 1 00:12 recoveryconfig -> /dev/block/sdf9
lrwxrwxrwx 1 root root 15 Jan 1 00:12 reserve -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 Jan 1 00:12 rootconfig -> /dev/block/sdf8
lrwxrwxrwx 1 root root 15 Jan 1 00:12 rpm -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 Jan 1 00:12 rpmbak -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 Jan 1 00:12 sec -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 Jan 1 00:12 splash -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 Jan 1 00:12 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 Jan 1 00:12 sti -> /dev/block/sde33
lrwxrwxrwx 1 root root 16 Jan 1 00:12 system -> /dev/block/sde19cmd
lrwxrwxrwx 1 root root 15 Jan 1 00:12 xblbak -> /dev/block/sdc1
never blank partitions if you don´t have a backup anywhere, meaning: not part of qfil, stockrom customrom (zip or fastboot), not pulled from the/a phone(x820/29)
i would pull any single partitiom first (that are not part of roms etc.) and save it, you shoud be safe to restore the phone to the condidtion as it is now at least.
if you think one of theese could cause the problem, be sure to get the partition images from a working phone before you erase those!
also, backup your efs/qcn!
from what you tell it sounds like a harrdware fault but try! i would also try everything, had success the last time.
it bet it´s a x829, isn´t it?
i have some spare time the rest of the week and already helpded some xda users remotely. if you want i could (try) to help you too.
i´m an it guy, so this is my nature.
good luck
Yes you are correct i have x829, I bought it online from gearbest.com.
I dont know how this partition table can be useful and I dont even know how to use it.
I have backup of CN26s bootloader and Firmware made via TWRP. Stragnely CN26s boots everytime but have alot of random reboots.
If I install Hexagon Rom from here then it works fine for a day or two https://forum.xda-developers.com/le-max-2/development/rom-hexagonrom-nougat-t3594858
but as soon as its rebooted then I have to restore CN26s bootloader via TWRP then install Hexagon***.zip again and it will start again.
One more thing is that if I only restore bootloader of cn26s while already installed Hexagon then it is not stuck at bootloader screen anymore where it says LeeCo I am not jut a mobilephone blah blah but it also proceeds to Hexagon OS loading Animation but then its stuck there forever...!
If you can help then please tell me, I am willing too to try new things.
craftsvision said:
Yes you are correct i have x829, I bought it online from gearbest.com.
I dont know how this partition table can be useful and I dont even know how to use it.
I have backup of CN26s bootloader and Firmware made via TWRP. Stragnely CN26s boots everytime but have alot of random reboots.
If I install Hexagon Rom from here then it works fine for a day or two https://forum.xda-developers.com/le-max-2/development/rom-hexagonrom-nougat-t3594858
but as soon as its rebooted then I have to restore CN26s bootloader via TWRP then install Hexagon***.zip again and it will start again.
One more thing is that if I only restore bootloader of cn26s while already installed Hexagon then it is not stuck at bootloader screen anymore where it says LeeCo I am not jut a mobilephone blah blah but it also proceeds to Hexagon OS loading Animation but then its stuck there forever...!
If you can help then please tell me, I am willing too to try new things.
Click to expand...
Click to collapse
if you want, install teamviewer and send me your id and password in pm.
connect the phone to pc directly (no hub) and put into edl mode. i know you already did that procedure but i´d like to start from scratch - just to be sure.
we can save the qcn also with qpst so you don´t have to worry about loosing your imei.
open the folder where alll your files are.
i´ll have to check some things on your pc and download some files.
i´m cooking my meal now, then i´m ready. just keep pc and teamviewer on and i´ll login asap.
A.N.Droid said:
if you want, install teamviewer and send me your id and password in pm.
connect the phone to pc directly (no hub) and put into edl mode. i know you already did that procedure but i´d like to start from scratch - just to be sure.
we can save the qcn also with qpst so you don´t have to worry about loosing your imei.
open the folder where alll your files are.
i´ll have to check some things on your pc and download some files.
i´m cooking my meal now, then i´m ready. just keep pc and teamviewer on and i´ll login asap.
Click to expand...
Click to collapse
It would be really helpful of you make a video about the complete fix. I have a x821 in which I forgot to remove encryption before flashing a custom ROM and now in twrp there is a system image partition which is 4GB in size and is non accessible. I want to delete that but being inaccessible I an unable to do so.
Can you guide me on how to do that? Can you at least give me the step by step procedure to fix this issue?
Thanks in advance.
I have also problem of random reboots and fcs no mater what rom I flash.
Any one guide me what to do?
I have clean flashed though twrp.
Didn't use fastboot method? Any one can guide me on this ?
azzammalik said:
I have also problem of random reboots and fcs no mater what rom I flash.
Any one guide me what to do?
I have clean flashed though twrp.
Didn't use fastboot method? Any one can guide me on this ?
Click to expand...
Click to collapse
Heyyo, first off... Can you please state which version of TWRP you are running and if it is official or not?
Second, have you tried using wipe > format data > yes? I'd recommend doing that... But be warned it completely reformists the internal storage so you'll want to backup everything important off the device first and also have a PC with USB ready to flash ROM and Gapps.
Third, I would recommend flashing new device firmware to ensure it is proper for any ROM you install. I recommend for stability purposes to use x820 CN 30s which can be found on my LineageOS 15.1 for x2 thread.
Fourth, flash the ROM of choice and Gapps (and optionally root program of choice if you want Su rights).
For Oreo ROMs? I highly recommend MindTheGapps arm64 as OpenGapps is still of beta quality for Oreo ROMs and says so when you select it on the OpenGapps website as shown in the picture below. MindTheGapps link can also be found on my LineageOS for x2 thread.
As for which Oreo ROM I'd recommend? Every one has a little bit of difference from the last so I say try them out and see which suits your needs the best. They're all pretty darn good... Except for Resurrection Remix official. The maintainer of that put out one build and then bought a new smartphone and abandoned it lol so yeah avoid the official RR release...
Good luck! :good:
Thanks a lot brother
ThE_MarD said:
Heyyo, first off... Can you please state which version of TWRP you are running and if it is official or not?
Second, have you tried using wipe > format data > yes? I'd recommend doing that... But be warned it completely reformists the internal storage so you'll want to backup everything important off the device first and also have a PC with USB ready to flash ROM and Gapps.
Third, I would recommend flashing new device firmware to ensure it is proper for any ROM you install. I recommend for stability purposes to use x820 CN 30s which can be found on my LineageOS 15.1 for x2 thread.
Fourth, flash the ROM of choice and Gapps (and optionally root program of choice if you want Su rights).
For Oreo ROMs? I highly recommend MindTheGapps arm64 as OpenGapps is still of beta quality for Oreo ROMs and says so when you select it on the OpenGapps website as shown in the picture below. MindTheGapps link can also be found on my LineageOS for x2 thread.
As for which Oreo ROM I'd recommend? Every one has a little bit of difference from the last so I say try them out and see which suits your needs the best. They're all pretty darn good... Except for Resurrection Remix official. The maintainer of that put out one build and then bought a new smartphone and abandoned it lol so yeah avoid the official RR release...
Good luck! :good:
Click to expand...
Click to collapse
Million times thanks to you bro for answering with lot of details.
1. It's official latest twrp
2. Yes formatted a lot of times.
3. Yeah this is the method I didn't try yet. I will goto your thread and will download official firmware and will let you know after flashing official and afterwards any oreo rom.
4. Never tried any gapps other then opengapps maybe this will solve my problem. I will definitely try this method now.
I have almost flashed all oreo roms and every oreo rom is almost perfect for me except for this annoying bug. I am now heading towards your rom and will report you back after few hours because my mobile data is not that super fast and will download all required files and will flash it later in evening.
Thank you once again.
:fingers-crossed:
azzammalik said:
Million times thanks to you bro for answering with lot of details.
1. It's official latest twrp
2. Yes formatted a lot of times.
3. Yeah this is the method I didn't try yet. I will goto your thread and will download official firmware and will let you know after flashing official and afterwards any oreo rom.
4. Never tried any gapps other then opengapps maybe this will solve my problem. I will definitely try this method now.
I have almost flashed all oreo roms and every oreo rom is almost perfect for me except for this annoying bug. I am now heading towards your rom and will report you back after few hours because my mobile data is not that super fast and will download all required files and will flash it later in evening.
Thank you once again.
:fingers-crossed:
Click to expand...
Click to collapse
Heyyo, by chance is your TWRP version 3.2.1-2? That's the latest one I made and is required for the latest versions of LineageOS 15.1 for x2 as it has quota storage support for a minor boost to storage performance.
https://twrp.me/leeco/leecolemax2.html
Hope she works good for you!
ThE_MarD said:
Heyyo, by chance is your TWRP version 3.2.1-2? That's the latest one I made and is required for the latest versions of LineageOS 15.1 for x2 as it has quota storage support for a minor boost to storage performance.
https://twrp.me/leeco/leecolemax2.html
Hope she works good for you!
Click to expand...
Click to collapse
Hey,
I am here after 12 hours of usage.
Yes, I am using twrp 3.2.1-2.First flashed 30s firmware then flashed rom and gapps which you recommended and then magisk.
And to my amazement I had only 3 fcs right now which are too less then which I have faced before.
Also didn't reboot once in 12 hours but suddenly got 2 reboots in quick succession.
But still it's a lot more usable now as a daily driver for me just because of ya. Maybe problem will come back in a day or two as that happened before too.
But until then it's all OK for now.
A big thanks to you. .
Have a good day ahead
Cheers
Update: not even a single reboot or fc even after installing system less xposed. NO WORDS FOR YA. A BIG THANKYOU
2nd Update: 2nd day of usage. No more fcs. Single reboot. Perfect now.
Hello everyone!
Does anybody know please, if it's somehow possible to dump/extract messages from the Facebook messenger application which have been already deleted by the user (read correctly as a 'cheating girlfriend') and which maybe left stored somewhere on device within the internal messenger's CACHE memory?
I am pretty sure that they still must have be stored somewhere secretly in the phone, because within the Apps -> Messenger -> Storage -> It still shows that some space is used as following: Application - 100MB, Data -325 MB, Cache - 60.14 MB Total - 486 MB. -> That's a clear evidence that application is using some internal cache storage somewhere...
I've already read many articles found on internet about how to 'very simply' recover deleted messages from the phone saying that you just need to check for subfolder "fb_temp" within the "com.facebook.orca" and WOALA - That's it!
But in fact, it's not so easy at all, because that folder always displays as empty, no matter whether I check it with windows explorer (when the phone is plugged to PC via USB) or using ADB shell.....the subfolder "fb_temp" always appears as an empty folder. Maybe it's because the phone is not yet rooted? I don't know.
Code:
hero2lte:/storage/self/primary/[COLOR="Blue"]com.facebook.katana/fb_temp[/COLOR] $ ls -la
total 8
[COLOR="DarkOrange"]drwxrwx--x 2 root sdcard_rw 4096 2019-02-02 22:51 .
drwxrwx--x 3 root sdcard_rw 4096 2018-08-08 20:03 ..[/COLOR]
-rw-rw---- 1 root sdcard_rw 0 2018-08-08 20:03 .nomedia
hero2lte:/storage/self/primary/com.facebook.katana/fb_temp $
hero2lte:/storage/self/primary/com.facebook.katana/fb_temp $
hero2lte:/storage/self/primary/com.facebook.katana/fb_temp $ cd ../../com.facebook.orca/fb_temp/
hero2lte:/storage/self/primary/[COLOR="Blue"]com.facebook.orca/fb_temp[/COLOR] $ ls -la
total 8
[COLOR="DarkOrange"]drwxrwx--x 2 root sdcard_rw 4096 2019-07-18 23:14 .
drwxrwx--x 3 root sdcard_rw 4096 2017-11-27 00:29 ..[/COLOR]
-rw-rw---- 1 root sdcard_rw 0 2017-11-27 00:29 .nomedia
hero2lte:/storage/self/primary/com.facebook.orca/fb_temp $
hero2lte:/storage/self/primary/com.facebook.orca/fb_temp $
Does anybody have any experience with similar problem ? Maybe it's more for Interpol to ask instead of here ...but ... you never know :laugh:
I've also read several articles about how to correctly root the phone in different fashions, what are the pros and cons... but, if possible, I'd prefer rather to avoid of rooting the phone at all, because it always carries a a high risk of loosing the data / because during the rooting process (for example with combination of latest TWRP and Magisk) it is necessary to wipe all the data - Obviously really I cannot afford go ahead with that option. But anyway, the rooting method does not guarantee me the results which I need to achieve (extract the deleted messages).....OR? Please feel free to correct me if I was wrong.
Any ideas how to figure this issue out?
Some technical facts:
Is phone already rooted?: No.
Phone model: Samsung Galaxy S7 Edge (SM-935F)
Android version: 8.0.0
KNOX version: 3.1 , api level 25 , TIMA 3.3.0
FB messenger version: 224.1.0.18.117
has no SD card, only phone's internal memory is used
Your any feedbacks / hints or advices will be highly appreciated! :good:
PS: any advices like: "find a new girlfriend" are not accepted! :laugh: ...