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.
Related
I have somehow messed up my folio 100, and its BCT and bootloader information.
So im hoping someone else with little experience, knows how to use the nvflash utilities and dump the information for me and send me a link on where to get it.
the combo to get into bootloader mode is: POWER button pressed 4 times + VOL- key and it will go into bootloader mode.
I can extract these tomorrow evening.
Can you be clearer with the bootload sequence?
Tried to get the booload seq. Ended up with a partial reset of settings...
tshoulihane said:
I can extract these tomorrow evening.
Can you be clearer with the bootload sequence?
Tried to get the booload seq. Ended up with a partial reset of settings...
Click to expand...
Click to collapse
well, i dont think you should try it..!!
another user did, he ended up with a semi-bricked device too.. so thanks but now the fun stops.. it seems that Toshiba included a very,very bad key combo that terminates the device to a deadlocked machine..
so ill just figure out another way to get the partitions off it.. but my 4xpower + vol- is really scary, do NOT try it
at least until is cleared on how to get out of this bootloader state again.
I dumped the partitions which are visible from android already. Don't quite know what got resentment with your key sequence - DATA wiped? Some of the preloaded apps are broken now, but they were a bit broken before.
tshoulihane said:
I dumped the partitions which are visible from android already. Don't quite know what got resentment with your key sequence - DATA wiped? Some of the preloaded apps are broken now, but they were a bit broken before.
Click to expand...
Click to collapse
so you mean, you can extract all partitions from a shell?
ie. bootloader of partition2 and so forward?
i didnt notice that all 8 partitions were accessable there?
can you upload the dump of them somewhere?
A guy made the dumps of the ROM (not the recovery image though) on the forum of Frandroid DOT fr but I cannot post you the link directly here (anti spam as I do not have many messages on the forum).
I will PM you (if it allows me)
bootoo said:
A guy made the dumps of the ROM (not the recovery image though) on the forum of Frandroid DOT fr but I cannot post you the link directly here (anti spam as I do not have many messages on the forum).
I will PM you (if it allows me)
Click to expand...
Click to collapse
i have the dump of the /system i need all of the other partitions ie. 0 to 8
i cannot restore system, as i got no bootable tablet at all, i need raw partition dumps which i hope can be used using nvflash
Is it possible to extract opera mobile 10.1 apk?
toca79 said:
Is it possible to extract opera mobile 10.1 apk?
Click to expand...
Click to collapse
look for it here
Dexter_nlb said:
look for it here
Click to expand...
Click to collapse
Thx a lot found it.
I think the resolution is too high though.
Hi Dex, did you was able to restore your bricked folio?
roglio said:
Hi Dex, did you was able to restore your bricked folio?
Click to expand...
Click to collapse
decided to get another one..
ok!
I was hoping you did it because I'm a little tired of android (apple fan ).
My idea was to build and flash linux (ubuntu 10.10 works on toshiba AC100).
But if there isn't a way to restore the factory default (bootloader, etc.), I'll give up.
roglio said:
My idea was to build and flash linux (ubuntu 10.10 works on toshiba AC100).
Click to expand...
Click to collapse
when i was debugging bootloader configs, i was provided some config files that Ac100 users said would work on our folio, but i see now partition setup is very different, so we need to make proper configs for our folio before experimenting with the bootloader..
again, as you metion backup seems to do , when recover seems unavailable currently. it will be hard to verify if the parition table layout is working.
Hi,
sorry, maybe I missunderstood someting, but I cannot understand your problem in reading out the whole flash.
1. I have opened / disassembled my Filio 100. And like I have suspected there is a 16GB micoSD card connected (soldered) to the PCB and fixed with glue. One could read out the whole flash in a card reader.
2. You have fully access to the microSD card out of Android:
/dev/block/mmcblk0
sh-4.1# cd /dev/block
cd /dev/block
sh-4.1# pwd
pwd
/dev/block
sh-4.1# ls -l
ls -l
brw------- root root 254, 1 2010-12-07 08:46 dm-1
brw------- root root 254, 0 2010-12-07 08:46 dm-0
drwxr-xr-x root root 2010-12-07 08:45 vold
brw------- root root 179, 17 2010-12-07 08:45 mmcblk1p1
brw------- root root 179, 16 2010-12-07 08:45 mmcblk1
brw------- root root 7, 7 2010-12-07 08:45 loop7
brw------- root root 7, 6 2010-12-07 08:45 loop6
brw------- root root 7, 5 2010-12-07 08:45 loop5
brw------- root root 7, 4 2010-12-07 08:45 loop4
brw------- root root 7, 3 2010-12-07 08:45 loop3
brw------- root root 7, 2 2010-12-07 08:45 loop2
brw------- root root 7, 1 2010-12-07 08:45 loop1
brw------- root root 7, 0 2010-12-07 08:45 loop0
brw------- root root 179, 8 2010-12-07 08:45 mmcblk0p8
brw------- root root 179, 7 2010-12-07 08:45 mmcblk0p7
brw------- root root 179, 6 2010-12-07 08:45 mmcblk0p6
brw------- root root 179, 5 2010-12-07 08:45 mmcblk0p5
brw------- root root 179, 4 2010-12-07 08:45 mmcblk0p4
brw------- root root 179, 3 2010-12-07 08:45 mmcblk0p3
brw------- root root 179, 2 2010-12-07 08:45 mmcblk0p2
brw------- root root 179, 1 2010-12-07 08:45 mmcblk0p1
brw------- root root 179, 0 2010-12-07 08:45 mmcblk0
sh-4.1#
Regards, Artem
Hi DerArtem! Nice first post indeed!!!!
Thank you for your information.
A micro SD soldered is a nice gift from toshiba!!! This means upgrades, full dumps, etc.
Great
A request: could you please post some pictures?
DerArtem said:
sorry, maybe I missunderstood someting, but I cannot understand your problem in reading out the whole flash.
Click to expand...
Click to collapse
did i write i had problem dumping the entire mmc device? not really.
Yes, you misunderstood,Writing a proper cfg file describing the different areas is required.. dumping is easy part, documenting is harder..
but feel free to contribute and document the .cfg file for bootloader, that is of course appreciated...
I just got back from my business trip, and finally had some more time to take a closer look at the device.
roglio said:
Hi DerArtem! Nice first post indeed!!!!
Thank you for your information.
A micro SD soldered is a nice gift from toshiba!!! This means upgrades, full dumps, etc.
Great
A request: could you please post some pictures?
Click to expand...
Click to collapse
The device has a warranty seal inside. If you open the device completly the seal will break. I have just opened the device soo far, that the seal will not break. To make photos I will have to open it copletly. I will think about it....
Dexter_nlb said:
did i write i had problem dumping the entire mmc device? not really.
Yes, you misunderstood,Writing a proper cfg file describing the different areas is required.. dumping is easy part, documenting is harder..
but feel free to contribute and document the .cfg file for bootloader, that is of course appreciated...
Click to expand...
Click to collapse
Ok, I see. I have duped the mmc and mounted the partitions on my pc:
Here is the partition table on my PC:
Code:
[email protected] ~/bin/folio $ /sbin/fdisk -u -l folio.img
Platte folio.img: 15.9 GByte, 15920005120 Byte
1 Köpfe, 63 Sektoren/Spur, 493551 Zylinder, zusammen 31093760 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Gerät boot. Anfang Ende Blöcke Id System
folio.img1 2048 526335 262144 83 Linux (/system)
folio.img2 526336 2623487 1048576 83 Linux (/cache)
folio.img3 2623488 2627583 2048 83 Linux (/misc)
folio.img4 2627584 31093759 14233088 5 Erweiterte
folio.img5 2628608 2644991 8192 83 Linux (???)
folio.img6 2646016 4743167 1048576 83 Linux (/data)
folio.img7 4744192 4754431 5120 83 Linux (???)
folio.img8 4755456 31093759 13169152 83 Linux (13G - storage)
Now you can mount the partitions on your pc:
Code:
sudo mount -o loop,ro,offset=$((512*2048)) folio.img /mnt/floppy/
I was not able to find the kernel or the bootloader or the root partition in the dump. I have also checked it with a hex editor.
Is the Folio using an other storage for kernel and bootloder? Does it have more NOR/NAND flash inside?
While looking at the size of the microSD (15920005120 bytes) I think that the bootloader is hiding a part of the microSD from the OS where the kernel and the bootloader are...
Where is the .cfg file you are talking about located?
DerArtem said:
Where is the .cfg file you are talking about located?
Click to expand...
Click to collapse
its a file assoiciated with the nvflash utility. search for the toshiba AC100 or here for more details for them it works fine.
the part 5 and 7 are boot kernel(8Mbyte) + recovery kernel(5Mbyte) , bootloader is as i know from ac100 on part0 , but thats not 100% yet.
Dexter_nlb said:
the part 5 and 7 are boot kernel(8Mbyte) + recovery kernel(5Mbyte) , bootloader is as i know from ac100 on part0 , but thats not 100% yet.
Click to expand...
Click to collapse
So, I have checked part 5 and 7. The content is the same like in boot.img and recovery.img. So the BCT is somewhere else...
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?
I'm still running Task's 7/3 ICS - yes, I'm going to go to the Tasks JB sometime soon, but I was waiting for things to get fixed and settle down before I switched.
I did a nandroid backup today and the files that were generated are different than the ones from a previous version of Task's ICS - all the .tar files are zero size and there are files with ".a" appended to the filename that have all the data in them. The previous version of Task's ICS didn't generate the .a files, just .tar files. CWM version is 5.5.0.4.
Code:
-rwxr-xr-x. 1 root root 8388608 Oct 21 21:09 boot.img
-rwxr-xr-x. 1 root root 0 Oct 21 21:12 cache.ext4.tar
-rwxr-xr-x. 1 root root 11776 Oct 21 21:12 cache.ext4.tar.a
-rwxr-xr-x. 1 root root 0 Oct 21 21:10 data.ext4.tar
-rwxr-xr-x. 1 root root 479716352 Oct 21 21:12 data.ext4.tar.a
-rwxr-xr-x. 1 root root 510 Oct 21 21:13 nandroid.md5
-rwxr-xr-x. 1 root root 8388608 Oct 21 21:09 recovery.img
-rwxr-xr-x. 1 root root 0 Oct 21 21:09 system.ext4.tar
-rwxr-xr-x. 1 root root 289286144 Oct 21 21:10 system.ext4.tar.a
I did some google searches but didn't find much about this. Are these files going to restore properly if I need to do a restore? I'm somewhat concerned about this because I want to be able to go back to ICS if JB has some issues that I would rather wait until they are fixed before I switch to JB. And I'd like to get some advice before trying to do a restore and finding out it messes up my phone (the phone is owned by my employer so I need to keep it in working order in case I get an after-hours call).
mvi57 said:
I'm still running Task's 7/3 ICS - yes, I'm going to go to the Tasks JB sometime soon, but I was waiting for things to get fixed and settle down before I switched.
I did a nandroid backup today and the files that were generated are different than the ones from a previous version of Task's ICS - all the .tar files are zero size and there are files with ".a" appended to the filename that have all the data in them. The previous version of Task's ICS didn't generate the .a files, just .tar files. CWM version is 5.5.0.4.
Code:
-rwxr-xr-x. 1 root root 8388608 Oct 21 21:09 boot.img
-rwxr-xr-x. 1 root root 0 Oct 21 21:12 cache.ext4.tar
-rwxr-xr-x. 1 root root 11776 Oct 21 21:12 cache.ext4.tar.a
-rwxr-xr-x. 1 root root 0 Oct 21 21:10 data.ext4.tar
-rwxr-xr-x. 1 root root 479716352 Oct 21 21:12 data.ext4.tar.a
-rwxr-xr-x. 1 root root 510 Oct 21 21:13 nandroid.md5
-rwxr-xr-x. 1 root root 8388608 Oct 21 21:09 recovery.img
-rwxr-xr-x. 1 root root 0 Oct 21 21:09 system.ext4.tar
-rwxr-xr-x. 1 root root 289286144 Oct 21 21:10 system.ext4.tar.a
I did some google searches but didn't find much about this. Are these files going to restore properly if I need to do a restore? I'm somewhat concerned about this because I want to be able to go back to ICS if JB has some issues that I would rather wait until they are fixed before I switch to JB. And I'd like to get some advice before trying to do a restore and finding out it messes up my phone (the phone is owned by my employer so I need to keep it in working order in case I get an after-hours call).
Click to expand...
Click to collapse
Why not just make another backup? Or test restore and have you return to stock files ready
Bleh
122ninjas said:
Why not just make another backup? Or test restore and have you return to stock files ready
Bleh
Click to expand...
Click to collapse
I've done 3 or 4 backups with the same results, and no errors reported by CWM. I will probably end up testing it but I thought I'd ask about it first in case it does cause a problem so I don't have to do a complete wipe/reflash to recover from a busted restore.
mvi57 said:
I've done 3 or 4 backups with the same results, and no errors reported by CWM. I will probably end up testing it but I thought I'd ask about it first in case it does cause a problem so I don't have to do a complete wipe/reflash to recover from a busted restore.
Click to expand...
Click to collapse
Did you try restoring one of the backups yet, to see if it restores properly?
0p3nsrc said:
Did you try restoring one of the backups yet, to see if it restores properly?
Click to expand...
Click to collapse
Yes, I did that a few days ago before I upgraded to Task's AOKP JB. The restore worked.
So..... I've been fussing with the kernel these days.
I managed to add cwm recovery just by editing initramfs.
also, I could enable init.d support
I had a repacker script that only involves original zImage and edited initramfs folder and it made my work easier.
Now, I became greedy and I wanted to add cpu governor.
If I want to do so, I 've gotta actually compile the kernel from source.
I first used this command
export ARCH=arm
export CROSS_COMPILE=/home/xxxxxxxx/arm-2009q3/bin/arm-none-eabi
make venturi_kor_defconfig #I have Korean device
make menuconfig # at the menu, i located my initramfs folder
make -j2
I've got numerous errors no matter what toolchain I used.
arm-eabi-4.4.0
arm-eabi-4.4.3
arm-eabi-4.7
arm-2009q3
arm-eabi-linaro 4.6.2
arm-eabi-linaro 4.7
all the zImages created had similar sizes as the original ones but none of them passed samsung logo (they do boot into recovery though)
4.4.3 and 4.7 didn't even make zImage so I guess that's guaranteed failure.
But Samsung's YP-GB70 Opensource zip says that I should use arm-2009q3 and when I do, it still gives me error
I use 12.04 LTS 64bit
any suggestion please? I'm dire
stylemate said:
So..... I've been fussing with the kernel these days.
I managed to add cwm recovery just by editing initramfs.
also, I could enable init.d support
I had a repacker script that only involves original zImage and edited initramfs folder and it made my work easier.
Now, I became greedy and I wanted to add cpu governor.
If I want to do so, I 've gotta actually compile the kernel from source.
I first used this command
export ARCH=arm
export CROSS_COMPILE=/home/xxxxxxxx/arm-2009q3/bin/arm-none-eabi
make venturi_kor_defconfig #I have Korean device
make menuconfig # at the menu, i located my initramfs folder
make -j2
I've got numerous errors no matter what toolchain I used.
arm-eabi-4.4.0
arm-eabi-4.4.3
arm-eabi-4.7
arm-2009q3
arm-eabi-linaro 4.6.2
arm-eabi-linaro 4.7
all the zImages created had similar sizes as the original ones but none of them passed samsung logo (they do boot into recovery though)
4.4.3 and 4.7 didn't even make zImage so I guess that's guaranteed failure.
But Samsung's YP-GB70 Opensource zip says that I should use arm-2009q3 and when I do, it still gives me error
I use 12.04 LTS 64bit
any suggestion please? I'm dire
Click to expand...
Click to collapse
Hmmm. First make sure you downloaded source for the gingerbread kernel (2.6.35) and not froyo (2.6.32) - it should also be a zip.
Second 4.4.3 is what I use, so that's quite strange. I'll need complete output to see what the problem is.
Mevordel said:
Hmmm. First make sure you downloaded source for the gingerbread kernel (2.6.35) and not froyo (2.6.32) - it should also be a zip.
Second 4.4.3 is what I use, so that's quite strange. I'll need complete output to see what the problem is.
Click to expand...
Click to collapse
Hmm sorrry for not clarifying that. I'm certain that I got Gingerbread source and it said to use G++ toolchain for EABI. Which is arm-2009q3-68
I made a mistake saying that It gave me an error. they were warnings. zImages were succesfully made along with other modules but it just doesn't boot.
btw, do you know how to fix bootloop when recovery can't locate cache partition and can't even factory reset?
stylemate said:
Hmm sorrry for not clarifying that. I'm certain that I got Gingerbread source and it said to use G++ toolchain for EABI. Which is arm-2009q3-68
I made a mistake saying that It gave me an error. they were warnings. zImages were succesfully made along with other modules but it just doesn't boot.
btw, do you know how to fix bootloop when recovery can't locate cache partition and can't even factory reset?
Click to expand...
Click to collapse
Do you have the initramfs packed into the rom because Samsung kernels have the initramfs inside them.
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
Do you have the initramfs packed into the rom because Samsung kernels have the initramfs inside them.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
....... hmmmmmm I'm having quite hard time comprehending that....... sorry
i first extracted initramfs from zImage, (you know by using magic number like 30 37 30 37)
Then I added cwm recovery from Entropy's source.
I repacked it to modified_ramdisk.cpio
Then I tried to compile kernel by samsung's open source zip (inside there were one tar.gz for platform and another for kernel)
I used those commands at the first post, using the right toolchain that the opensource specified.
I even located my initramfs directory in the GUI section of config.
What did I do wrong?
stylemate said:
....... hmmmmmm I'm having quite hard time comprehending that....... sorry
i first extracted initramfs from zImage, (you know by using magic number like 30 37 30 37)
Then I added cwm recovery from Entropy's source.
I repacked it to modified_ramdisk.cpio
Then I tried to compile kernel by samsung's open source zip (inside there were one tar.gz for platform and another for kernel)
I used those commands at the first post, using the right toolchain that the opensource specified.
I even located my initramfs directory in the GUI section of config.
What did I do wrong?
Click to expand...
Click to collapse
Oh sorry I meant kernel instead of ROM. Hmm why don't you take an initramfs from another source or copy-paste the scripts from your device and add the cwm binaries from entropy's?
Sent from my Nexus 7 using Tapatalk HD
stylemate said:
Hmm sorrry for not clarifying that. I'm certain that I got Gingerbread source and it said to use G++ toolchain for EABI. Which is arm-2009q3-68
I made a mistake saying that It gave me an error. they were warnings. zImages were succesfully made along with other modules but it just doesn't boot.
btw, do you know how to fix bootloop when recovery can't locate cache partition and can't even factory reset?
Click to expand...
Click to collapse
stylemate said:
....... hmmmmmm I'm having quite hard time comprehending that....... sorry
i first extracted initramfs from zImage, (you know by using magic number like 30 37 30 37)
Then I added cwm recovery from Entropy's source.
I repacked it to modified_ramdisk.cpio
Then I tried to compile kernel by samsung's open source zip (inside there were one tar.gz for platform and another for kernel)
I used those commands at the first post, using the right toolchain that the opensource specified.
I even located my initramfs directory in the GUI section of config.
What did I do wrong?
Click to expand...
Click to collapse
As far as I know, you didn't do anything wrong. The issue must be somewhere in the init scripts (init.<whatever>, recovery.rc, ueventd.<whatever>). Did you copy those from Entropy's ramdisk too? Which ones?
zaclimon said:
Oh sorry I meant kernel instead of ROM. Hmm why don't you take an initramfs from another source or copy-paste the scripts from your device and add the cwm binaries from entropy's?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I think I'm the only one with korean SGP5 initramfs source.....
anyway, I had a repacking script which doesn't bother with compiling the actual kernel.
I could make a kernel with just CWM recovery and it worked.
But I figured out that I had to compile the actual kernel to add governor or OC stuff... so......
Mevordel said:
As far as I know, you didn't do anything wrong. The issue must be somewhere in the init scripts (init.<whatever>, recovery.rc, ueventd.<whatever>). Did you copy those from Entropy's ramdisk too? Which ones?
Click to expand...
Click to collapse
Ho Thanks for your suggestion. I didn't copy the actual files of those scripts, I looked at his commit and saw those lines changed when he was adding CWM. So I just added or replaced few lines at recovery.rc
Then I copied bunch of files in sbin, which seemed necessary for the recovery.
I copied the clockworkmod image file
Then finally i copied the recovery.fstab
to misc/
I edited recovery.fstab several times to get mount and storage work.
So I think initramfs itself has no problem....... It got me a working kernel with CWM recovery.
But it's the problem when I actually try to compile kernel from the scratch.....
stylemate said:
Ho Thanks for your suggestion. I didn't copy the actual files of those scripts, I looked at his commit and saw those lines changed when he was adding CWM. So I just added or replaced few lines at recovery.rc
Then I copied bunch of files in sbin, which seemed necessary for the recovery.
I copied the clockworkmod image file
Then finally i copied the recovery.fstab
to misc/
I edited recovery.fstab several times to get mount and storage work.
So I think initramfs itself has no problem....... It got me a working kernel with CWM recovery.
But it's the problem when I actually try to compile kernel from the scratch.....
Click to expand...
Click to collapse
When you were just modifying the initramfs, did it boot normally then?
Mevordel said:
When you were just modifying the initramfs, did it boot normally then?
Click to expand...
Click to collapse
yes. very smoothly
I used linaro tool chain 4.6.2 and also arm-eabi-4.7 both worked fine when i just modified the initramfs with a simple script.
stylemate said:
yes. very smoothly
I used linaro tool chain 4.6.2 and also arm-eabi-4.7 both worked fine when i just modified the initramfs with a simple script.
Click to expand...
Click to collapse
Can you boot into CWM and (using adb shell) give me the output of
Code:
cat /proc/cpuinfo
ls -la /
Thanks.
Mevordel said:
Can you boot into CWM and (using adb shell) give me the output of
Code:
cat /proc/cpuinfo
ls -la /
Thanks.
Click to expand...
Click to collapse
Sorry I couldn't do anything because my device was hard bricked and I fixed it today 0.0
Hope you are still around here.
I can't run adb shell with my newly compiled kernel
computer does not detect my device and i tried plugging it in and out several times, killing adb server each time.
interesting thing is that i can't mount USB storage, system, efs or anything else in CWM recovery.
Only cache partition is mounted which is strange. I used same initramfs source for both working kernel and newly compiled kernel,
but i don't know what happened during the compiling process.
I tried compiling with the original intiramfs folder (not modified one) and <3e> recovery also gave me numerous errors like can't mount where, where, where, where.
so there mustn't be a problem in both init.rc-like scripts and ultimately initramfs. It's probably the compiling process and how I set up the compilation.
Do i have to check all lines in venturi_kor_defconfig......?
oh btw, sdcard can be mounted with original ramdisk compiled kernel also, just checked it now.
stylemate said:
Sorry I couldn't do anything because my device was hard bricked and I fixed it today 0.0
Hope you are still around here.
I can't run adb shell with my newly compiled kernel
computer does not detect my device and i tried plugging it in and out several times, killing adb server each time.
interesting thing is that i can't mount USB storage, system, efs or anything else in CWM recovery.
Only cache partition is mounted which is strange. I used same initramfs source for both working kernel and newly compiled kernel,
but i don't know what happened during the compiling process.
I tried compiling with the original intiramfs folder (not modified one) and <3e> recovery also gave me numerous errors like can't mount where, where, where, where.
so there mustn't be a problem in both init.rc-like scripts and ultimately initramfs. It's probably the compiling process and how I set up the compilation.
Do i have to check all lines in venturi_kor_defconfig......?
oh btw, sdcard can be mounted with original ramdisk compiled kernel also, just checked it now.
Click to expand...
Click to collapse
I mean from CWM on your repacked-but-not-compiled kernel -- the one you said worked.
Also, which exactly zip did you download from Samsung's site? You don't need to go through the defconfig as long as you got the right one.
Third, please only compile with 4.4.3 or the one Samsung recommends. Anything newer will probably not work.
Fourth, as to partitions, they are all formatted to RFS, right? And can you run in CWM (where everything mounts and is mounted):
Code:
mount
fdisk -l /dev/block/mmcblk0
Mevordel said:
I mean from CWM on your repacked-but-not-compiled kernel -- the one you said worked.
Also, which exactly zip did you download from Samsung's site?
Third, please only compile with 4.4.3 or the one Samsung recommends. Anything newer will probably not work.
Click to expand...
Click to collapse
1st
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 99.40
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc08
CPU revision : 2
Hardware : SMDKC110
Revision : 0000
Serial : 08c5603ec1690711
-rw-r--r-- 1 system system 118 Dec 25 12:19 default.prop
drwxr-xr-x 9 root root 2840 Jan 23 01:26 dev
drwxrwxr-x 1 radio system 0 Jan 23 01:26 efs
drwxr-xr-x 2 root root 0 Jan 23 01:26 emmc
lrwxrwxrwx 1 root root 11 Jan 23 01:26 etc -> /system/etc
-rwxr-xr-x 1 system system 1876 Dec 25 12:19 fota.rc
-rwxr-xr-x 1 system system 168364 Dec 25 12:27 init
-rw-r--r-- 1 system system 1677 Dec 25 12:19 init.goldfish.rc
-rwxr-xr-x 1 system system 30941 Dec 28 08:32 init.rc
-rwxr-xr-x 1 system system 30931 Dec 25 17:46 init.rc~
-rwxr-xr-x 1 system system 4489 Dec 25 12:19 init.smdkc110.rc
drwxr-xr-x 3 system system 0 Dec 25 12:19 lib
-rwxr-xr-x 1 system system 1419 Dec 25 12:19 lpm.rc
drwx------ 2 system system 0 Dec 26 16:21 misc
drwxrwxr-x 3 root root 0 Jan 23 01:26 mnt
drwxr-xr-x 2 root root 0 Jan 23 01:26 preload
dr-xr-xr-x 60 root root 0 Jan 1 1970 proc
-rwxr-xr-x 1 system system 410344 Dec 25 12:19 recovery
-rw-r--r-- 1 system system 2182 Dec 25 12:39 recovery.rc
drwxr-xr-x 3 system system 0 Dec 25 12:40 res
drwxr-xr-x 2 system system 0 Dec 26 16:31 sbin
drwxr-xr-x 2 root root 0 Jan 23 01:26 sdcard
drwxr-xr-x 12 root root 0 Jan 23 01:26 sys
drwxr-xr-x 1 root root 0 Jan 23 01:26 system
drwxrwxrwt 2 root root 60 Jan 23 01:26 tmp
-rw-r--r-- 1 system system 0 Dec 25 12:19 ueventd.goldfish.rc
-rw-r--r-- 1 system system 4245 Dec 25 12:19 ueventd.rc
-rwxr-xr-x 1 system system 1749 Dec 25 12:19 ueventd.smdkc110.rc
drwxrwxr-x 3 system system 0 Dec 28 08:33 vendor
init.rc~ file is the autocreated backup file that i forgot to erase
2nd
I downloaded YP-GB70-WW GB Opensource.zip
3rd
Yes I've been using the right toolchain that the readme file specified.
I have tried 4.4.3 too and many other toolchains.
4th
{
"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"
}
it's very normal... I had to fix this part of partition cause my partition was messed up beginning from block 12 but now it's perfect.
picture stolen from Siraki......
stylemate said:
1st
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 99.40
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc08
CPU revision : 2
Hardware : SMDKC110
Revision : 0000
Serial : 08c5603ec1690711
-rw-r--r-- 1 system system 118 Dec 25 12:19 default.prop
drwxr-xr-x 9 root root 2840 Jan 23 01:26 dev
drwxrwxr-x 1 radio system 0 Jan 23 01:26 efs
drwxr-xr-x 2 root root 0 Jan 23 01:26 emmc
lrwxrwxrwx 1 root root 11 Jan 23 01:26 etc -> /system/etc
-rwxr-xr-x 1 system system 1876 Dec 25 12:19 fota.rc
-rwxr-xr-x 1 system system 168364 Dec 25 12:27 init
-rw-r--r-- 1 system system 1677 Dec 25 12:19 init.goldfish.rc
-rwxr-xr-x 1 system system 30941 Dec 28 08:32 init.rc
-rwxr-xr-x 1 system system 30931 Dec 25 17:46 init.rc~
-rwxr-xr-x 1 system system 4489 Dec 25 12:19 init.smdkc110.rc
drwxr-xr-x 3 system system 0 Dec 25 12:19 lib
-rwxr-xr-x 1 system system 1419 Dec 25 12:19 lpm.rc
drwx------ 2 system system 0 Dec 26 16:21 misc
drwxrwxr-x 3 root root 0 Jan 23 01:26 mnt
drwxr-xr-x 2 root root 0 Jan 23 01:26 preload
dr-xr-xr-x 60 root root 0 Jan 1 1970 proc
-rwxr-xr-x 1 system system 410344 Dec 25 12:19 recovery
-rw-r--r-- 1 system system 2182 Dec 25 12:39 recovery.rc
drwxr-xr-x 3 system system 0 Dec 25 12:40 res
drwxr-xr-x 2 system system 0 Dec 26 16:31 sbin
drwxr-xr-x 2 root root 0 Jan 23 01:26 sdcard
drwxr-xr-x 12 root root 0 Jan 23 01:26 sys
drwxr-xr-x 1 root root 0 Jan 23 01:26 system
drwxrwxrwt 2 root root 60 Jan 23 01:26 tmp
-rw-r--r-- 1 system system 0 Dec 25 12:19 ueventd.goldfish.rc
-rw-r--r-- 1 system system 4245 Dec 25 12:19 ueventd.rc
-rwxr-xr-x 1 system system 1749 Dec 25 12:19 ueventd.smdkc110.rc
drwxrwxr-x 3 system system 0 Dec 28 08:33 vendor
init.rc~ file is the autocreated backup file that i forgot to erase
2nd
I downloaded YP-GB70-WW GB Opensource.zip
3rd
Yes I've been using the right toolchain that the readme file specified.
I have tried 4.4.3 too and many other toolchains.
Click to expand...
Click to collapse
Thanks. I edited my post after you quoted it. But from what you posted, everything looks in order. (A minor OCD is that you should delete init.rc~, but it shouldn't make a difference.)
It's somewhat a hunch, but try downloading the "YP-G1 US" source and compiling it with venturi_kor_defconfig,
And I'm not sure, as I don't have any of the Korean devices, but isn't there a difference between YP-G70 and YP-GB70? If so, then venturi may not even be the right config.
Mevordel said:
Thanks. I edited my post after you quoted it. But from what you posted, everything looks in order. (A minor OCD is that you should delete init.rc~, but it shouldn't make a difference.)
It's somewhat a hunch, but try downloading the "YP-G1 US" source and compiling it with venturi_kor_defconfig,
And I'm not sure, as I don't have any of the Korean devices, but isn't there a difference between YP-G70 and YP-GB70? If so, then venturi may not even be the right config.
Click to expand...
Click to collapse
DMB function and Camera is the major and maybe the only difference. But That doesn't really matter.
As long as i get bootable kernel I will be fine with it. Haha
Thank you, I will try with YP-G70 later.
{
"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.