Related
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?
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.
Thanks to @HypoTurtle for providing the .img files!
Root privilege allows users to download and use apps such as Titanium Backup. It also allows easier modification of settings.
I thought some of you would like a step-by-step to root the most recent .403 Remix OS. I have tried here to put together a procedure that even new members can follow. Please let me know how it works for you.
PLEASE REMEMBER THAT MESSING AROUND MIGHT RESULT IN PROBLEMS IF YOU DO NOT FOLLOW INSTRUCTIONS EXACTLY.
This is only for 64 bit. Please note that you MUST type all command line commands Exactly as shown (including spaces and caps)
To root you will need only two files: one is a modified ramdisk.img that you will install while in Windows; and one is a superuser su.img to add to the data partition from the Remix OS command line.
1 First, if you haven't already, download and install Remix OS Version .403 from their website. Go through the complete installation.
2 Next, from Windows, using your favorite browser, download ramdisk-403.img and su.img from:
https://drive.google.com/folderview?id=0B3gcDbDvV4MkVWRxU3pYMzVUWEU
3 To substitute the new ramdisk.img:
a Open the File Explorer and copy the ramdisk-403.img file.
b From the File Explorer, click on the Drive with your Remix OS.You will see a "RemixOS" folder.
c Click on it to open it. Now you should see the files including one named ramdisk.img.
d Click on the ramdisk.img and select rename the ramdisk.img to ramdiskorig.img to save it "just in case"
e Now rename the ramdisk-403.img to ramdisk.img
4 To finish you need to restart and boot into Remix OS.
a First thing to do in Remix is go to Settings/Experimental features/Enable terminal debug console and activate it.
b Open the File Manager and click on the Disk with Windows installed (usually Disk 1 or Disk 2)
c Click on "Users" and then on your user ID folder
d Find the "Downloads" folder and click on it. You should see the su.img that you downloaded while in Windows
e Click on the su.img file and drag it to the Download folder on the left. It will copy the su.img to your Download folder
5 Now you are ready to copy the su.img into your /data partition.
a Press ALT&F1 to open the command line. You should see a line of text with the # symbol.
b To copy su.img into /data, at the command line type: cp /data/media/0/Download/su.img /data/su.img
c Note that there are spaces ONLY after cp and img
d Press ENTER. If you receive no error message then you did it correctly.
Press ALT&F7 to leave the command line. Play it safe and reboot. You now can download and run any app that requires root access.
Set to go! Have fun. Let me know how it works for you.
Working
Works with 402???
My WiFi didn't broke with 402, so I'll not upgrade to 403...
Regnas said:
Works with 402???
My WiFi didn't broke with 402, so I'll not upgrade to 403...
Click to expand...
Click to collapse
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!
lollyjay said:
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!
Click to expand...
Click to collapse
Yeah, it's funny...
Anyway,I'll try that later..
Cheers..
lollyjay said:
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!
Click to expand...
Click to collapse
Any chance you have an lsmod from both. I know the issue in 402 was that both wl and b43 were both loaded - it might be viable to create a broadcom switch to flick between the two [one's proprietary and the other is open-source]
HypoTurtle said:
Any chance you have an lsmod from both. I know the issue in 402 was that both wl and b43 were both loaded - it might be viable to create a broadcom switch to flick between the two [one's proprietary and the other is open-source]
Click to expand...
Click to collapse
Yes, do you just want an lsmod output or do you want more specific?
lollyjay said:
Yes, do you just want an lsmod output or do you want more specific?
Click to expand...
Click to collapse
Both outputs or a diff 402-dmesg 403-dmesg > 402-403_diff would be fine. For some reason I'm still on 402 -- haven't gotten the 403 ota yet.
HypoTurtle said:
Both outputs or a diff 402-dmesg 403-dmesg > 402-403_diff would be fine. For some reason I'm still on 402 -- haven't gotten the 403 ota yet.
Click to expand...
Click to collapse
I don't have 402 any more. Here is one from 403. Maybe @Regnas can give you the other.
Module Size Used by Tainted: P
binfmt_misc 9163 1
hid_sensor_als 4217 0
hid_sensor_incl_3d 4947 0
hid_sensor_accel_3d 4768 2
hid_sensor_rotation 4683 0
hid_sensor_magn_3d 5925 0
hid_sensor_gyro_3d 4755 0
hid_sensor_trigger 3417 12 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d
industrialio_triggered_buffer 1874 6 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d
kfifo_buf 3374 1 industrialio_triggered_buffer
industrialio 45973 11 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_trigger,industrialio_triggered_buffer,kfifo_buf
hid_sensor_iio_common 5514 7 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_trigger
hid_sensor_custom 9846 0
rtsx_pci_ms 8248 0
memstick 9812 1 rtsx_pci_ms
rtsx_pci_sdmmc 15489 0
mac_hid 3843 0
bsd_comp 4698 0
ppp_deflate 3798 0
ppp_async 6285 0
pppoe 8725 0
pppox 2638 1 pppoe
ppp_generic 22934 5 bsd_comp,ppp_deflate,ppp_async,pppoe,pppox
slhc 5081 1 ppp_generic
wmi 8736 0
wl 6426390 0
cfg80211 477899 1 wl
uvcvideo 66519 1
snd_hda_codec_hdmi 38342 1
videobuf2_vmalloc 4693 1 uvcvideo
videobuf2_memops 2716 1 videobuf2_vmalloc
videobuf2_v4l2 19150 1 uvcvideo
videobuf2_core 21313 2 uvcvideo,videobuf2_v4l2
snd_hda_codec_realtek 67326 1
snd_hda_codec_generic 53744 1 snd_hda_codec_realtek
thinkpad_acpi 66626 1
nvram 6533 1 thinkpad_acpi
soc_button_array 2418 0
snd_hda_intel 28041 1
snd_hda_codec 105597 4 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel
snd_hda_core 53903 5 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel,snd_hda_codec
snd_hwdep 5785 1 snd_hda_codec
snd_pcm 87019 5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
snd_timer 20488 1 snd_pcm
snd 65356 9 snd_hda_codec_hdmi,snd_hda_codec_generic,thinkpad_acpi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6615 1 snd
shpchp 23487 0
rtsx_pci 41858 2 rtsx_pci_ms,rtsx_pci_sdmmc
r8169 61453 0
mii 4910 1 r8169
psmouse 101828 0
pcspkr 2158 0
lpc_ich 14290 0
intel_rst 2468 0
i915 1084918 9
drm_kms_helper 108824 1 i915
drm 311256 11 i915,drm_kms_helper
fb_sys_fops 1759 1 drm_kms_helper
syscopyarea 3185 1 drm_kms_helper
sysfillrect 3485 1 drm_kms_helper
sysimgblt 2562 1 drm_kms_helper
i2c_algo_bit 5421 1 i915
i2c_i801 16755 0
hid_sensor_hub 11145 9 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_custom
hid_multitouch 10208 0
coretemp 6156 0
hwmon 4404 2 thinkpad_acpi,coretemp
btusb 31833 0
btrtl 4762 1 btusb
btbcm 7000 1 btusb
btintel 8387 1 btusb
bluetooth 444084 9 btusb,btrtl,btbcm,btintel
Sent from my on Z00A using XDA Labs
Hi @lollyjay, the method is simple and easy and is working great....Thanks a lot for that.....But how do we enable system r/w because it did not let me edit build.prop to enable brigntness slider... in earlier version I used modified initrd.img....it there any other way to achieve system r/w... Thanks...
lollyjay said:
I don't have 402 any more. Here is one from 403. Maybe @Regnas can give you the other.
Click to expand...
Click to collapse
I would like to help but I don't know how to generate this info..
What is this?
ssanjy said:
Hi @lollyjay, the method is simple and easy and is working great....Thanks a lot for that.....But how do we enable system r/w because it did not let me edit build.prop to enable brigntness slider... in earlier version I used modified initrd.img....it there any other way to achieve system r/w... Thanks...
Click to expand...
Click to collapse
They have removed the brightness slider in 402 at least.
I'm not sure which ramdisk this is; check getprop and see what ro.remixos.box is set to.
I'll upload my ramdisk if you want to check if the slider was readded in 403 [if its set to true].
I also have the modified initrd.img on my thread; where these .imgs are from. But ideally it's best not to use it; the only downside being needing to modify ramdisk.img itself for ro.* prop entries.
HypoTurtle said:
They have removed the brightness slider in 402 at least.
I'm not sure which ramdisk this is; check getprop and see what ro.remixos.box is set to.
I'll upload my ramdisk if you want to check if the slider was readded in 403 [if its set to true].
I also have the modified initrd.img on my thread; where these .imgs are from. But ideally it's best not to use it; the only downside being needing to modify ramdisk.img itself for ro.* prop entries.
Click to expand...
Click to collapse
remixos.box is set to true and when I tried to change it to false I couldn't save it... While in 402 I had found modified initrd which did let me change value of build prop... Anyway thanks for the info
Sent from my S II using XDA Labs
ssanjy said:
remixos.box is set to true and when I tried to change it to false I couldn't save it... While in 402 I had found modified initrd which did let me change value of build prop... Anyway thanks for the info
Click to expand...
Click to collapse
Hi you might try Root Browser from Play Store it can change permissions
Sent from my on Z00A using XDA Labs
lollyjay said:
I don't have 402 any more. Here is one from 403. Maybe @Regnas can give you the other.
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
It would need both from the same device; think I found a 402 that you posted elsewhere.
Code:
[b]Removed[/b]
b43 375752 0
mac80211 504422 1 b43
ssb 45258 1 b43
rng_core 7153 1 b43
bcma 43126 1 b43
efivars 7470 0 [efi variables]
[b]Added[/b]
intel_rst 2468 0 [rapid storage tech]
psmouse 101828 0 [touchpad]
would be the module difference between 402 and 403; so perhaps just blacklisting b43 on 402 would have sufficed [the others are dependant on it]
ssanjy said:
remixos.box is set to true and when I tried to change it to false I couldn't save it... While in 402 I had found modified initrd which did let me change value of build prop... Anyway thanks for the info
Sent from my S II using XDA Labs
Click to expand...
Click to collapse
The 402 initrd should work fine [attach the 403 here just so I can compare to 402 just to see if anything was changed] if you want to modify it that way; but the slider is gone. Only options would be to add a shortcut to the brightness activity from SystemUI or a brightness app.
Hey guys, I'm using an HD install of remix os 403 - replaced the ramdisk - went back into Remix but couldn't access the ALT+F1 terminal for whatever reason. Eventually I managed to get the su.img into the right folder in the data.img and nothing happens. How would I be notified that it has worked? Would I see something different on startup? I assume the su.img is being mounted etc by the modified ramdisk.img.
Would it be a possibility to just make a fresh, clean data.img with just that su.img file already in? That way I could try just replacing the data.img and starting fresh. At this moment I can't see any change from the su.img and ramdisk.img being in place. Probably it's a problem at my end - but i'm confused why the ALT+F1 root terminal doesn't work for me?
I'm using a UK keyboard on an Alienware M17x R4 - any suggestions would be very welcome.
By the way I used Paragon ExtFS for Windows to access the data.img and insert the su.img file (which I verified in the terminal of remixos (not the root terminal, I couldn't get that working) but I can use the LS command in /data and I see that su.img is there.
Thank you for any suggestions
mrpras said:
Hey guys, I'm using an HD install of remix os 403 - replaced the ramdisk - went back into Remix but couldn't access the ALT+F1 terminal for whatever reason. Eventually I managed to get the su.img into the right folder in the data.img and nothing happens. How would I be notified that it has worked? Would I see something different on startup? I assume the su.img is being mounted etc by the modified ramdisk.img.
Would it be a possibility to just make a fresh, clean data.img with just that su.img file already in? That way I could try just replacing the data.img and starting fresh. At this moment I can't see any change from the su.img and ramdisk.img being in place. Probably it's a problem at my end - but i'm confused why the ALT+F1 root terminal doesn't work for me?
I'm using a UK keyboard on an Alienware M17x R4 - any suggestions would be very welcome.
By the way I used Paragon ExtFS for Windows to access the data.img and insert the su.img file (which I verified in the terminal of remixos (not the root terminal, I couldn't get that working) but I can use the LS command in /data and I see that su.img is there.
Thank you for any suggestions
Click to expand...
Click to collapse
Did you remember to go into settings/experimental features to enable terminal debug console? If so try Alt&right arrow for entry/egress
Sent from my on Z00A using XDA Labs
lollyjay said:
Did you remember to go into settings/experimental features to enable terminal debug console? If so try Alt&right arrow for entry/egress
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
I hadn't enabled the console/debug option thank you for that!
Now I'll go and try again. Thanks for the fix, and the systemless root files. I'll be back if it doesn't work, otherwise thanks again!
---------- Post added at 05:50 PM ---------- Previous post was at 05:28 PM ----------
Okay thanks, so that works - Just a small suggestion that somewhere in your description (where you mention the Alt+F1) it could be worth mentioning about enabling the debug console because I didn't find that information when scouring around. Maybe would be helpful to others as ignorant as me
mrpras said:
I hadn't enabled the console/debug option thank you for that!
Now I'll go and try again. Thanks for the fix, and the systemless root files. I'll be back if it doesn't work, otherwise thanks again!
Click to expand...
Click to collapse
My pleasure. You can test root by downloading an app that requires root such as Titanium Backup. It will immediately let you know if it cannot acquire root privilege
Sent from my on Z00A using XDA Labs
Just wanted to note here that the Lenovo ThinkPad Twist is a great dual Windows /Ubuntu and Remix OS daily driver. Great touchscreen display and can be used as a (heavy) tablet with Remix OS. Look at this on eBay http://www.ebay.com/itm/162121987813
I bought three from a school for $99 each.
Sent from my on Z00A using XDA Labs
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war.
Please do some research if you have any concerns about using custom ROMs/Kernels.
You are choosing to make these modifications, and if you point the finger at me for
messing up your device, I will laugh at you.
Lambda Kernel was my development start point in the LG G2 glorious period, now you're looking at a new "horizon of possibility" for the LeEco device family. This Kernel has been written from scratch since January 2017, resulting in a small, polished and minimal core that's migratable across Kernel revisions.
It follows the flash n' go principle, everything packed in the Kernel is already tweaked and ready to be used as a daily driver for everyone.
The downloads, contributors and source code are at the bottom of this post, it is recommended to read everything before flashing.
DEVEL: My own testing builds for certain features and tests. They aren't normally shared, although sometimes I publish them. If you see one of them, don't forget they are recommended for advanced users/developers only because of their potential changes that must be debugged before publishing a NIGHTLY version.
NIGHTLY: They are closer to the proper release version but still can have some errors or bugs to be reported and tested, they should be generally stable. Nightly doesn't mean it builds every night here since I don't use a build server, it means that is the regularly updated version.
SNAPSHOT: That's the version for the ones that don't want their devices to be lab rats for new features and staging changes. I don't know whether or not to say something is stable enough to be a SNAPSHOT but if you see one it's because it's been sometime running well.
Pretty straightforward once you get used to it, isn't it?
A general panorama for Lambda Kernel, always matching the latest release, in this case the NIGHTLY from 03-23-2018.
HOT ↠ Source-code changes for Lambda Kernel.
COLD ↠ Environment changes for Lambda Kernel.
Latest LA.HB Kernel base from CAF's upstream HOT
Minimal device tree stubs and OEM code HOT
Modular approach for EUI compatibility HOT
Built with Paranoid's patched GCC compiler HOT
Latest Wi-Fi qcacl-2.0 driver from CAF's upstream HOT
Refactored and update OEM sound code to catch up with CAF HOT
Removed the old WCD9330 sound driver dependencies HOT
Removed most of the OEM useless drivers to use the original ones from CAF HOT
Tailored down the preset configuration to reduce Kernel size HOT
Own headset detection code built on top of CAF HOT
Backports of the Android USB driver and gadget from LA.UM.5.5 (N) HOT
Patched battery type adjustments during charger code execution HOT
Corrected charging constants to charge safer with less heat dissipation HOT
Read this twice before flashing/posting!
Cod. 000:
State: Placebo!
Priority: Urgent.
Overview: The thread is under construction here as well.
Read this twice before flashing/posting!
Q. How to install this Kernel?
A. Download the version you'd like to use and flash using a custom recovery like TWRP.
Q. What ROMs does this Kernel support?
A. It supports the version explicitly mentioned in the file name and its "forks".
Q. Will this Kernel support my ROM in future?
A. I've no clue, will it probably be the default Kernel of those in future? You tell me...
Click the Downloads button above to go straight to Github releases page, find the appropriate file for your variant and flash it in recovery.
Many developers and people helped to bring the pieces of code needed to build the Lambda Kernel Project, some of them are listed below.
AlexDNS
Codeworkx
Dorimanx
Faux
FranciscoFranco
Myfluxi
SultanXDA
Source for Kernel at Github.
Source for AnyKernel2 at Github.
Guide and introduction to Lambda Kernel development at Github.
~ All project resources were built with free and open source software. ~~ Lambda Kernel trademark and logos are copyleft. ~~ This is a development thread, be polite. ~
Reserved
Reserved.
Reserved
Reserved.
For EUI, right? I'm curious how it runs but I'm on CM13 atm.
Sent from my LEX727 using XDA-Developers Legacy app
benjmiester said:
For EUI, right? I'm curious how it runs but I'm on CM13 atm.
Sent from my LEX727 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm not sure if there are device and Kernel trees for CM13 on this device available (open source) to check whether it'd work or not. The Kernel shouldn't diverge much from stock and it may worth the shot. If it boots on stock, it boots on CM probably.
GalaticStryder said:
I'm not sure if there are device and Kernel trees for CM13 on this device available (open source) to check whether it'd work or not. The Kernel shouldn't diverge much from stock and it may worth the shot. If it boots on stock, it boots on CM probably.
Click to expand...
Click to collapse
Alright, I'll test it on a X727 (20s EUI). Just need to make a backup and cross my fingers lol.
Edit: The zip flashed correctly, but the phone just sits on the splash screen. I waited for about 10-12 minutes and didn't boot up or even reach the boot animation.
Ace42 said:
Alright, I'll test it on a X727 (20s EUI). Just need to make a backup and cross my fingers lol.
Edit: The zip flashed correctly, but the phone just sits on the splash screen. I waited for about 10-12 minutes and didn't boot up or even reach the boot animation.
Click to expand...
Click to collapse
Yeah, that was expected, that CAF merge introduced some pretty intrusive changes in device tree side of things, although none of them seem to hurt, splash screen stuck issues are usually something "minor" as the Kernel is still alive, probably trying to probe certain codec up but not being able to do so.
I may push another zip without the merge to query...
UPDATE: I'll be rolling a couple compilations with different changes, flashing in the version order will give better results. Please, check if /data/kernel_output.txt is present.
GalaticStryder said:
Yeah, that was expected, that CAF merge introduced some pretty intrusive changes in device tree side of things, although none of them seem to hurt, splash screen stuck issues are usually something "minor" as the Kernel is still alive, probably trying to probe certain codec up but not being able to do so.
I may push another zip without the merge to query...
UPDATE: I'll be rolling a couple compilations with different changes, flashing in the version order will give better results. Please, check if /data/kernel_output.txt is present.
Click to expand...
Click to collapse
I can't find that file. These are the only files in /data besides the folders.
Ace42 said:
I can't find that file. These are the only files in /data besides the folders.
Click to expand...
Click to collapse
So I wasn't generated at the ramdisk generation step, I've allocated the file, it will be in root right now.
Could you output the following:
Code:
ls -l /dev/block/bootdevice/by-name/boot
Code:
ls -l /system/lib/modules/
I'll push all builds to Drive, attachments aren't working quite well...
GalaticStryder said:
So I wasn't generated at the ramdisk generation step, I've allocated the file, it will be in root right now.
Could you output the following:
I'll push all builds to Drive, attachments aren't working quite well...
Click to expand...
Click to collapse
$ su
[email protected]_zl1:/data/data/com.termux/files/home # ls -l /dev/block/bootdevice/by-name/boot
lrwxrwxrwx root root 1970-03-22 08:01 boot -> /dev/block/sde18
[email protected]_zl1:/data/data/com.termux/files/home #
[email protected]_zl1:/data/data/com.termux/files/home #
ls -l /system/lib/modules/
-rw-r--r-- root root 11484 1970-03-10 00:35 ansi_cprng.ko
-rw-r--r-- root root 21644 1970-03-10 00:35 br_netfilter.ko
-rw-r--r-- root root 319628 1970-03-10 00:35 core_ctl.ko
-rw-r--r-- root root 7612 1970-03-10 00:35 evbug.ko
-rw-r--r-- root root 30740 1970-03-10 00:35 ghci-hcd.ko
-rw-r--r-- root root 32588 1970-03-10 00:35 gxhci-hcd.ko
-rw-r--r-- root root 62076 1970-03-10 00:35 jnl.ko
-rw-r--r-- root root 13916 1970-03-10 00:35 lcd.ko
-rw-r--r-- root root 56948 1970-03-10 00:35 mmc_block_test.ko
-rw-r--r-- root root 43732 1970-03-10 00:35 mmc_test.ko
-rw-r--r-- root root 2640 1970-03-18 01:00 modules.dep.bb
drwxr-xr-x root root 2017-01-05 15:31 qca_cld
-rw-r--r-- root root 19028 1970-03-10 00:35 rdbg.ko
-rw-r--r-- root root 20940 1970-03-10 00:35 spidev.ko
-rw-r--r-- root root 32116 1970-03-10 00:35 test-iosched.ko
-rw-r--r-- root root 45228 1970-03-10 00:35 ufs_test.ko
-rw-r--r-- root root 632820 1970-03-10 00:35 ufsd.ko
-rw-r--r-- root root 296948 1970-03-10 00:35 wil6210.ko
lrwxrwxrwx root root 2017-01-05 15:32 wlan.ko -> /system/lib/modules/qca_cld/qca_cld_wlan.ko
[email protected]_zl1:/data/data/com.termux/files/home #
Ace42 said:
$ su
[email protected]_zl1:/data/data/com.termux/files/home # ls -l /dev/block/bootdevice/by-name/boot
lrwxrwxrwx root root 1970-03-22 08:01 boot -> /dev/block/sde18
[email protected]_zl1:/data/data/com.termux/files/home #
[email protected]_zl1:/data/data/com.termux/files/home #
ls -l /system/lib/modules/
-rw-r--r-- root root 11484 1970-03-10 00:35 ansi_cprng.ko
-rw-r--r-- root root 21644 1970-03-10 00:35 br_netfilter.ko
-rw-r--r-- root root 319628 1970-03-10 00:35 core_ctl.ko
-rw-r--r-- root root 7612 1970-03-10 00:35 evbug.ko
-rw-r--r-- root root 30740 1970-03-10 00:35 ghci-hcd.ko
-rw-r--r-- root root 32588 1970-03-10 00:35 gxhci-hcd.ko
-rw-r--r-- root root 62076 1970-03-10 00:35 jnl.ko
-rw-r--r-- root root 13916 1970-03-10 00:35 lcd.ko
-rw-r--r-- root root 56948 1970-03-10 00:35 mmc_block_test.ko
-rw-r--r-- root root 43732 1970-03-10 00:35 mmc_test.ko
-rw-r--r-- root root 2640 1970-03-18 01:00 modules.dep.bb
drwxr-xr-x root root 2017-01-05 15:31 qca_cld
-rw-r--r-- root root 19028 1970-03-10 00:35 rdbg.ko
-rw-r--r-- root root 20940 1970-03-10 00:35 spidev.ko
-rw-r--r-- root root 32116 1970-03-10 00:35 test-iosched.ko
-rw-r--r-- root root 45228 1970-03-10 00:35 ufs_test.ko
-rw-r--r-- root root 632820 1970-03-10 00:35 ufsd.ko
-rw-r--r-- root root 296948 1970-03-10 00:35 wil6210.ko
lrwxrwxrwx root root 2017-01-05 15:32 wlan.ko -> /system/lib/modules/qca_cld/qca_cld_wlan.ko
[email protected]_zl1:/data/data/com.termux/files/home #
Click to expand...
Click to collapse
Thanks, that should be enough, see if the latest Experimental 3 boots after the quick fixes in anykernel. I'll add a wrapper to symlink the wlan module if needed. But first we need to force it boot up.
GalaticStryder said:
Thanks, that should be enough, see if the latest Experimental 3 boots after the quick fixes in anykernel. I'll add a wrapper to symlink the wlan module if needed. But first we need to force it boot up.
Click to expand...
Click to collapse
Success! It booted up.
Ace42 said:
Success! It booted up.
Click to expand...
Click to collapse
Thanks for testing it. The file kernel_output.txt is present in rootfs (/)?
Code:
cd /
cat kernel_output.txt
Code:
lsmod
Code:
dmesg
These should help to gather more on what is working or not.
http://pastebin.com/A3nBZ7gm
Ace42 said:
Success! It booted up.
Click to expand...
Click to collapse
and it boots with CM 13 but no wifi
Boots on slim rom as well
booted up here on my lex 720 Google Edition as well...[emoji122]
Sent from my LEX720 using XDA-Developers Legacy app
Okarina26 said:
booted up here on my lex 720 Google Edition as well...[emoji122]
Sent from my LEX720 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yup, seems that everyone is using the LeEco base Kernel so far, I know darkobas has a different Kernel source with a different tag from LA.UM (nougat) CAF tag, so I'd not encourage using this Kernel with Omni 7.1 if that's the case.
The modules didn't get injected, for some reason, I'll manage to patch this and then get rid of them.
New build 0.4 is up...
Could you be kindly so nice to talk about the features we will get with these kernel? Which configuration tool is recommended? Will it work with Cydras Rom?
... sent from my LEX720 with Tapatalk
GalaticStryder said:
Yup, seems that everyone is using the LeEco base Kernel so far, I know darkobas has a different Kernel source with a different tag from LA.UM (nougat) CAF tag, so I'd not encourage using this Kernel with Omni 7.1 if that's the case.
The modules didn't get injected, for some reason, I'll manage to patch this and then get rid of them.
New build 0.4 is up...
Click to expand...
Click to collapse
0.4 hangs on the splash screen just like 0.1. As soon as I revert to 0.3 it boots up to Android.
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!