Hi all
I was looking around to find a way to unlock my bootloader. I tried almost everything and got no results, my phone just reboots. But now i find THIS PAGE and was wondering if THIS COMMIT can help us out (people who cant unlock the damm bootloader). I have no experience with this, but if anyone can take a look and just say if im saying crap here, it would be awesome.
Thanks in advance
shucrut said:
Hi all
I was looking around to find a way to unlock my bootloader. I tried almost everything and got no results, my phone just reboots. But now i find THIS PAGE and was wondering if THIS COMMIT can help us out (people who cant unlock the damm bootloader). I have no experience with this, but if anyone can take a look and just say if im saying crap here, it would be awesome.
Thanks in advance
Click to expand...
Click to collapse
What happened? Did you do what i told you?
Sent from my LG-P769 using Tapatalk 4
@omgbossis21 you should take a look at this...
sent from my locked rooted P769 v20f
I'm on YouTube (BioDesigner48)
geeshiet said:
What happened? Did you do what i told you?
Sent from my LG-P769 using Tapatalk 4
Click to expand...
Click to collapse
Nothing happened, i found this by coincidence. I did what u said and replied your post here
Well, maybe its nothing, but i logcat when i went to check bootloader lock menu (http://forum.xda-developers.com/showthread.php?t=2394274)
Code:
V/xt9input_alpha( 573): alpha_setAttribute(context(5C39F788))...success
V/xt9input_alpha( 573): alpha_hasLdb(context(0x5C39F788))...
V/xt9input_dbregistry( 573): DBRegistry::get_ldb_path(0x0109)...LG_902_r1-16_ENubUN_xt9_ALM.ldb
V/xt9input_alpha( 573): alpha_hasLdb(context(0x5C39F788))... 0x0109=>1
V/xt9input_alpha( 573): alpha_hasLdb(context(0x5C39F788))...
V/xt9input_dbregistry( 573): DBRegistry::get_ldb_path(0x0109)...LG_902_r1-16_ENubUN_xt9_ALM.ldb
V/xt9input_alpha( 573): alpha_hasLdb(context(0x5C39F788))... 0x0109=>1
V/xt9input_alpha( 573): alpha_hasLdb(context(0x5C39F788))...
V/xt9input_dbregistry( 573): DBRegistry::get_ldb_path(0x0109)...LG_902_r1-16_ENubUN_xt9_ALM.ldb
V/xt9input_alpha( 573): alpha_hasLdb(context(0x5C39F788))... 0x0109=>1
D/LGPhoneStatusBarPolicy( 483): ACTION_SIGNAL_STRENGTH_CHANGED!!!
I/SIMContacts( 972): Dialog|onSavedInstanceState()falsefalsefalse
I/LGE_CallLogFragment( 972): [moo] onStop()
I/LGE_CallLogFragment( 972): [moo] updateOnExit()
D/wpa_supplicant( 470): nl80211: survey data missing!
D/ViewRootImpl( 1965): ViewRoot TouchDown(Absolute) DOWN (369 , 128)
I/AudioService( 350): checkPlayConditions streamType:1 mMode:0 mRingerMode:2 result:true
E/BootLoader Unlock( 1965): swrv_fused_status=16
E/BootLoader Unlock( 1965): readNV(36): 16
D/LvOutput( 146): initCheck: 0
D/LvOutput( 146): attachEffects: attach processing to output 2, stream 1, session 58, mode 0
D/LvOutput( 146): attachEffects: no output processing needs to be attached to this stream
W/MemoryDealer( 146): madvise(0x43b3e000, 8192, MADV_REMOVE) returned Operation not supported on transport endpoint
D/AudioResampler( 146): forcing AudioResampler quality to 3
D/SurfaceFlinger( 143): createSurface for (1 x 1), name=com.lge.hiddenmenu/com.lge.hiddenmenu.bootloadunlock.BootLoader_Unlock
D/KeyguardViewMediator( 350): handleTimeout
D/LvOutput( 146): initCheck: 0
D/LvOutput( 146): detachEffects: detach processing for output 2, stream 1, session 58
D/LvOutput( 146): detachEffects: no output processing was attached to this stream
D/LGPhoneStatusBarPolicy( 483): ACTION_SIGNAL_STRENGTH_CHANGED!!!
D/ViewRootImpl( 1965): ViewRoot TouchDown(Absolute) DOWN (336 , 557)
I/AudioService( 350): checkPlayConditions streamType:1 mMode:0 mRingerMode:2 result:true
D/LvOutput( 146): initCheck: 0
D/LvOutput( 146): attachEffects: attach processing to output 2, stream 1, session 59, mode 0
D/LvOutput( 146): attachEffects: no output processing needs to be attached to this stream
W/MemoryDealer( 146): madvise(0x43b3a000, 12288, MADV_REMOVE) returned Operation not supported on transport endpoint
D/AudioResampler( 146): forcing AudioResampler quality to 3
W/InputMethodManagerService( 350): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
D/LvOutput( 146): initCheck: 0
D/LvOutput( 146): detachEffects: detach processing for output 2, stream 1, session 59
D/LvOutput( 146): detachEffects: no output processing was attached to this stream
D/wpa_supplicant( 470): nl80211: survey data missing!
D/LGPhoneStatusBarPolicy( 483): ACTION_SIGNAL_STRENGTH_CHANGED!!!
Maybe looking into com.lge.hiddenmenu/com.lge.hiddenmenu.bootloadunlock.BootLoader_Unlock can give us more information about the bootloader unlocking, since this process is able to know if the bootloader is unlocked or not
They've actually have dug deeper than that.
Have you seen this thread?
http://forum.xda-developers.com/showthread.php?t=2374554
Might be some stuff your interested in
sent from my locked rooted P769 v20f
I'm on YouTube (BioDesigner48)
BioDesigner48 said:
They've actually have dug deeper than that.
Have you seen this thread?
http://forum.xda-developers.com/showthread.php?t=2374554
Might be some stuff your interested in
sent from my locked rooted P769 v20f
I'm on YouTube (BioDesigner48)
Click to expand...
Click to collapse
I've already seen. I think my help wasnt needed, im not experienced like they are, in fact im not a dev, i just found that and thought that could help them
shucrut said:
I've already seen. I think my help wasnt needed, im not experienced like they are, in fact im not a dev, i just found that and thought that could help them
Click to expand...
Click to collapse
Ayee, the more help the better :thumbup:
sent from my locked rooted P769 v20f
I'm on YouTube (BioDesigner48)
BioDesigner48 said:
@omgbossis21 you should take a look at this...
sent from my locked rooted P769 v20f
I'm on YouTube (BioDesigner48)
Click to expand...
Click to collapse
All that is for custom uboot/uboot mods. The uboot partition among many others are signed by LG and checked, hence a locked bootloader. For that reason we can't boot from a modified partition be it x, recovery, boot etc. I have tried many different things from flashing unlockable (signed) partitions,optimus 3d leaked sign tools, unlock command from loaded kernel without system boot etc etc. Unfortunately my ram in my PC is dying so I can barely scroll through disassembled files or even build paranoid android in Ubuntu for the time being.
Sent from my LG-P769 using xda app-developers app
---------- Post added at 09:24 PM ---------- Previous post was at 09:18 PM ----------
shucrut said:
Well, maybe its nothing, but i logcat when i went to check bootloader lock menu (http://forum.xda-developers.com/showthread.php?t=2394274)
Code:
V/xt9input_alpha( 573): alpha_setAttribute(context(5C39F788))...success
V/xt9input_alpha( 573): alpha_hasLdb(context(0x5C39F788))...
V/xt9input_dbregistry( 573): DBRegistry::get_ldb_path(0x0109)...LG_902_r1-16_ENubUN_xt9_ALM.ldb
V/xt9input_alpha( 573): alpha_hasLdb(context(0x5C39F788))... 0x0109=>1
V/xt9input_alpha( 573): alpha_hasLdb(context(0x5C39F788))...
V/xt9input_dbregistry( 573): DBRegistry::get_ldb_path(0x0109)...LG_902_r1-16_ENubUN_xt9_ALM.ldb
V/xt9input_alpha( 573): alpha_hasLdb(context(0x5C39F788))... 0x0109=>1
V/xt9input_alpha( 573): alpha_hasLdb(context(0x5C39F788))...
V/xt9input_dbregistry( 573): DBRegistry::get_ldb_path(0x0109)...LG_902_r1-16_ENubUN_xt9_ALM.ldb
V/xt9input_alpha( 573): alpha_hasLdb(context(0x5C39F788))... 0x0109=>1
D/LGPhoneStatusBarPolicy( 483): ACTION_SIGNAL_STRENGTH_CHANGED!!!
I/SIMContacts( 972): Dialog|onSavedInstanceState()falsefalsefalse
I/LGE_CallLogFragment( 972): [moo] onStop()
I/LGE_CallLogFragment( 972): [moo] updateOnExit()
D/wpa_supplicant( 470): nl80211: survey data missing!
D/ViewRootImpl( 1965): ViewRoot TouchDown(Absolute) DOWN (369 , 128)
I/AudioService( 350): checkPlayConditions streamType:1 mMode:0 mRingerMode:2 result:true
E/BootLoader Unlock( 1965): swrv_fused_status=16
E/BootLoader Unlock( 1965): readNV(36): 16
D/LvOutput( 146): initCheck: 0
D/LvOutput( 146): attachEffects: attach processing to output 2, stream 1, session 58, mode 0
D/LvOutput( 146): attachEffects: no output processing needs to be attached to this stream
W/MemoryDealer( 146): madvise(0x43b3e000, 8192, MADV_REMOVE) returned Operation not supported on transport endpoint
D/AudioResampler( 146): forcing AudioResampler quality to 3
D/SurfaceFlinger( 143): createSurface for (1 x 1), name=com.lge.hiddenmenu/com.lge.hiddenmenu.bootloadunlock.BootLoader_Unlock
D/KeyguardViewMediator( 350): handleTimeout
D/LvOutput( 146): initCheck: 0
D/LvOutput( 146): detachEffects: detach processing for output 2, stream 1, session 58
D/LvOutput( 146): detachEffects: no output processing was attached to this stream
D/LGPhoneStatusBarPolicy( 483): ACTION_SIGNAL_STRENGTH_CHANGED!!!
D/ViewRootImpl( 1965): ViewRoot TouchDown(Absolute) DOWN (336 , 557)
I/AudioService( 350): checkPlayConditions streamType:1 mMode:0 mRingerMode:2 result:true
D/LvOutput( 146): initCheck: 0
D/LvOutput( 146): attachEffects: attach processing to output 2, stream 1, session 59, mode 0
D/LvOutput( 146): attachEffects: no output processing needs to be attached to this stream
W/MemoryDealer( 146): madvise(0x43b3a000, 12288, MADV_REMOVE) returned Operation not supported on transport endpoint
D/AudioResampler( 146): forcing AudioResampler quality to 3
W/InputMethodManagerService( 350): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
D/LvOutput( 146): initCheck: 0
D/LvOutput( 146): detachEffects: detach processing for output 2, stream 1, session 59
D/LvOutput( 146): detachEffects: no output processing was attached to this stream
D/wpa_supplicant( 470): nl80211: survey data missing!
D/LGPhoneStatusBarPolicy( 483): ACTION_SIGNAL_STRENGTH_CHANGED!!!
Maybe looking into com.lge.hiddenmenu/com.lge.hiddenmenu.bootloadunlock.BootLoader_Unlock can give us more information about the bootloader unlocking, since this process is able to know if the bootloader is unlocked or not
Click to expand...
Click to collapse
Actually I wish you had posted this in the other thread any logcat bootloader related is helpful. Tomorrow I will add this to my list of notes. Can you share your l9 variant/software version from this logcat?
Sent from my LG-P769 using xda app-developers app
omgbossis21 said:
All that is for custom uboot/uboot mods. The uboot partition among many others are signed by LG and checked, hence a locked bootloader. For that reason we can't boot from a modified partition be it x, recovery, boot etc. I have tried many different things from flashing unlockable (signed) partitions,optimus 3d leaked sign tools, unlock command from loaded kernel without system boot etc etc. Unfortunately my ram in my PC is dying so I can barely scroll through disassembled files or even build paranoid android in Ubuntu for the time being.
Sent from my LG-P769 using xda app-developers app
---------- Post added at 09:24 PM ---------- Previous post was at 09:18 PM ----------
Actually I wish you had posted this in the other thread any logcat bootloader related is helpful. Tomorrow I will add this to my list of notes. Can you share your l9 variant/software version from this logcat?
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure what variant he has but I'm definitely sure he's on v20b EU. Since he told me he reflashed it.
Sent from my LG-P769 using Tapatalk 4
My variant is P768 and i was on V20B europe open
Please post your log in the bootloader thread under development that's goin on. I don't want to lose sight of this and would like lelus to see it. My PC is down and can't copy and paste from this app (at least not that log) .
Sent from my LG-P769 using xda app-developers app
Related
Hi @all,
maybe some of you guys could help me with my problem.
I updated my Hero to the Cronos 1.4 (I think) a month ago.
Last week, I recognized that the USB mass storage connection does not work anymore.
I tried it on another PC, but no connection.
I tried another Hero with my PC, usb connection worked.
I found this link to the modaco forum:
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
So I followed the instructions of the first post on page 5.
Everything worked till that point where I should flash the RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe.
So, here is what I have done so far:
- created a goldcard (with another hero, a friend has one).
- extracted the rom.zip from HTC Hero RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
- flashed it via fastboot
- then I wanted to try the fastboot oem eraseconfig, but like it's said in the post, the eraseconfig command is not included
- so I extracted the rom.zip from RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe
- tried to flash it, downgrade should be possible because of the goldcard
- but I now get the error "INFOchecking main version... FAILED (remote: 43 main version check fail)"
What can I do?
Could I extract the hboot from the 1.76.405.1_R3 and replace the one of 2.73.405.5 just to have the eraseconfig command?
Every kind of help is appreciated.
Thanks
André
Goldcards are handset specific as it has something to do with the serial number.
This MIGHT be the issue.
Really? On another post I read that they are specific to the sd-card, as one has to identify the unique id of the sd card and not of the handset.
Here's the link to the thread:
http://forum.xda-developers.com/showthread.php?t=648102
You sure?..... Ask your pal to do the "cat /sys/class/mmc_host/mmc1/mmc1:*/cid" bit using two different SD cards (yours and his own one) to see if the code is the same of or not.
..... or backup the goldcard your pal done you,... then make a new one yourself using whatever guide your using at the mo,... along with this one,..... http://thatsbadass.com/android/tag/cid/ ... <--that guide shows how to get your CID without plugging your phone in.
I tried it with another card and its another code. So I think it depends on the sd-card.
So, I think I tried flashing before I created the goldcard and that process stopped at the very beginning, saying something like cid check failed or so and not with that "main version check fail" message.
EDA-One said:
I tried it with another card and its another code. So I think it depends on the sd-card.
So, I think I tried flashing before I created the goldcard and that process stopped at the very beginning, saying something like cid check failed or so and not with that "main version check fail" message.
Click to expand...
Click to collapse
Aha,... OK,... You must be right,... apologies.
.... Have you tried using flashrec already?....
If I remember correctly, you cannot flash this version directly since it is actually a downgrade. I don't remember clearly how I managed to bring it up, either it was thanks to a Goldcard (I did experiment with that), or it was enough to patch the custom recovery image (see http://android.modaco.com/content/h...android-modaco-com-index-phpshowtopic-292396/).
Click to expand...
Click to collapse
not yet. but i will try now.
But I don't know, what should I try to flash with flashrec.
A new recovery rom? I think flashrec only allows *.img, or am I missing something?
...
...
...
OK,that worked.
Now I will try to flash the RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed.
updating or rather downgrading with the cyanogen recovery does not work. it says: Can't open /sdcard/HEROIMG_.......release_signed.zip(bad).
so i will try flashing via fastboot
Did you get this resolved?
No, it doesn't work.
Now I even got no wifi. Could not activate it.
Does there exist a custom rom, that I could flash and that contains a newer hboot, which contains the eraseconfig command?
Hi,
I had exactly the same problem and used that post from modaco to get out of it. As I understand it, you have reflashed the first RUU, so you have SD access but still no USB, right?
When I got to that stage, I didn't use the 2nd RUU at all, I just reflashed the new SPL (update-hero-hboot-1.76.2007-signed.zip) which opened up the fastboot oem eraseconfig option. I was on 1.76.0007 already (check the S-OFF is displayed on the fastboot screen, that means the goldcard is working AFAIK)
Flashing that SPL was enough, I think the oem commands are in there rather than the ROM itself (since in fastboot mode, the SPL is the only thing that is running).
Hope that helps.
Where can I get this one?
OK, found it and will try it.
OK, i could update the SPL.
But eraseconfig does not make any change.
Now that I got the engineering SPL, I hopefully find a solution.
I will dive deep inside the forum and try to find a way to get my USB up and running.
Many thanks till now.
I can't find a solution, usb and adb still do not work.
What I've done:
- Tried "fastboot oem eraseconfig" --> no change
- "fastboot oem readconfig" gives:
INFOindex:0x0, value:0x0
INFOindex:0x1, value:0x0
INFOindex:0x2, value:0x0
INFOindex:0x3, value:0x0
INFOindex:0x4, value:0x0
INFOindex:0x5, value:0x0
INFOindex:0x6, value:0x0
INFOindex:0x7, value:0x0
INFOindex:0x8, value:0x0
INFOindex:0x9, value:0x0
OKAY [ 0.023s]
finished. total time: 0.023s
-"fastboot oem boot" gives:
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8F0841F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 32
INFOTAG:hwid 0x1
INFOTAG:skuid 0x20800
INFOTAG:hero panel = 0x3
INFOTAG:engineerid = 0x3
INFODevice CID is not super CID
INFOCID is T-MOB101
INFOsetting.cid::T-MOB101
INFOserial number: HT97xxxxxxxx
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =350
INFOactive commandline: board_hero.disable_uart3=0 board_hero.us
INFOb_h2w_sw=0 board_hero.disable_sdcard=0 smisize=32 androidbo
INFOot.baseband=6.35.06.18 androidboot.cid=T-MOB101 androidboot.
INFOcarrier=TMD androidboot.mid=HERO10000 androidboot.keycaps=qw
INFOertz androidboot.mode=normal androidboot.serialno=HT97xxxxxxxx
INFO71 androidboot.bootloader=1.76.2007 no_console_suspend=1 con
INFOsole=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFO0
INFO0
INFO69466957
INFO69784520
INFO69007473
INFO7473
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
FAILED (status read failed (Too many links))
finished. total time: 6.158s
Hmm, all the uart_disable and sdcard_disable are set to 0, so it looks like the eraseconfig has done its job (in that sense).
Just throwing a few ideas around here.
Do you have access to the SD card now and/or wi-fi now? I guess we really need a way to get access to the logs, but without USB you might need to use a file manager and try to find them... you want the equivalent of adb logcat basically...
when you plug-in a USB cable to the device, do any of the notifications come up on the hero and what does it say under the charging info, is it charging(AC) or charging(USB)?
Could just be the PC drivers if the device is detecting USB now?
Charging works in both cases (AC/USB).
Still got no USB-Connection, no connection notification is coming up on the device.
On the device I can access the sdcard.
WiFi is not working anymore.
Just flashed Modaco 3.2 and WiFi works again.
Now i have root access with a file explorer.
OK, I installed that aLogcat-App that saves the log to SD. I will try to create some logs, plugging in the usb cable.
So, heres the log. There's something strange going on, I think.
See my comments
I connected the USB-cable:
D/UsbConnectedReceiver( 248): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 248): unplugged = 1
//--> unplugged = 1 ?!?!
D/dalvikvm( 234): GC freed 2834 objects / 153480 bytes in 138ms
D/dalvikvm( 183): GC freed 315 objects / 14504 bytes in 91ms
D/dalvikvm( 143): GC freed 215 objects / 8544 bytes in 133ms
D/KeyguardUpdateMonitor( 95): receive ACTION_BATTERY_CHANGED
D/HtcLockScreen( 95): onRefreshBatteryInfo: 100
D/KeyguardViewMediator( 95): pokeWakelock(15000)
I/HtcLockScreen( 95): updateStatusViewByPriority
I disconnected the cable:
D/UsbConnectedReceiver( 248): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 248): unplugged = 0
//-> unplugged = 0 ?!?!
D/UsbConnectedReceiver( 248): USB Disconnected.
D/UsbConnectedReceiver( 248): Catch USB Disconnect Event, USB cable does really not exist.
D/UsbConnectedReceiver( 248): ADB Enable = true
// --> enable adb on disconnect ?
D/UsbConnectedReceiver( 248): ADB StartByMe = false
D/UsbConnectedReceiver( 248): Try to stop PSService.
Here is the log of a friend that has the hero too:
D/StatusBarPolicy( 136): cable plugged, mPluggedBatteryLevel=58
D/UsbConnectedReceiver( 300): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 300): unplugged = 1
D/KeyguardUpdateMonitor( 136): receive ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 300): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 300): unplugged = 2
D/UsbConnectedReceiver( 300): USB Connected.
D/UsbConnectedReceiver( 300): mObexServerStarted=true
D/UsbConnectedReceiver( 300): mAtCommandServerStarted=false
D/UsbConnectedReceiver( 300): Try to start ATCommandService.
D/PSService( 300): onStart()
D/UsbConnectedReceiver( 300): Show Notification...
D/UsbConnectedReceiver( 300): Server Start Up. ServerType=1 ServerStatus=1
D/UsbConnectedReceiver( 300): mObexServerStarted=true mAtCommandServerStarted=true
D/UsbConnectedReceiver( 300): Show Notification...
D/MountListener( 136): handleEvent ums_connected
D/dalvikvm( 2363): GC freed 1621 objects / 82560 bytes in 129ms
D/dalvikvm( 300): GC freed 3754 objects / 615400 bytes in 106ms
D/dalvikvm( 300): GC freed 4448 objects / 776848 bytes in 101ms
D/MountListener( 136): handleEvent ums_disabled
D/MountListener( 136): handleEvent ums_disconnected
D/KeyguardUpdateMonitor( 136): receive ACTION_BATTERY_CHANGED
D/HtcLockScreen( 136): onRefreshBatteryInfo: 33
D/KeyguardViewMediator( 136): pokeWakelock(15000)
I/HtcLockScreen( 136): updateStatusViewByPriority
D/UsbConnectedReceiver( 300): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 300): unplugged = 0
D/UsbConnectedReceiver( 300): USB Disconnected.
D/UsbConnectedReceiver( 300): Catch USB Disconnect Event, USB cable does really not exist.
D/UsbConnectedReceiver( 300): ADB Enable = true
D/UsbConnectedReceiver( 300): ADB StartByMe = false
D/UsbConnectedReceiver( 300): Try to stop PSService.
I/ActivityManager( 136): Stopping service: com.htc.android.psclient/.PSService
D/UsbConnectedReceiver( 300): Server Start Up. ServerType=1 ServerStatus=0
D/dalvikvm( 2318): GC freed 8615 objects / 518960 bytes in 121ms
D/dalvikvm( 383): GC freed 3095 objects / 170360 bytes in 112ms
D/dalvikvm( 206): GC freed 2271 objects / 398152 bytes in 140ms
Hi all,
I have a t-mobile phone and tried to install android 2.2. there. I used mdeejay's and darkStone's builds, but wifi didn't work at any of them. I've found a person who uses T-mobile hd2 too and installed the same versions of rom and radio. It didn't helped. In windows mobile wifi works well.
Could you please advice how to hande it? Did anyone face the same problem?
Thank you in advance.
#did some debug via adb:
I suppose that the red line below tells about reason.. But I haven't dealt with WPA on android before.. Any help is appreciated.
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
I/WifiHW ( 1916): wifi_load_driver enter
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
I/WifiHW ( 1916): wifi_load_driver end right 3
I/WifiHW ( 1916): wifi_start_supplicant enter
I/WifiHW ( 1916): wifi_start_supplicant end right 2
D/WifiService( 1916): ACTION_BATTERY_CHANGED pluggedType: 2
I/wpa_supplicant( 2771): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00
:00:00
E/wpa_supplicant( 2771): Failed to disable WPA in the driver.
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/PowerManagerService( 1916): New lightsensor value:40, lcdValue:90
D/lights ( 1916): set_light_buttons
D/lights ( 1916): set_light_keyboard
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x6257a8), index=0, pid=2298,
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x4ca268), index=0, pid=2298
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
V/WifiStateTracker( 1916): Supplicant died unexpectedly
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/WifiStateTracker( 1916): Disabling interface
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/WifiStateTracker( 1916): Disabling interface
I/WifiHW ( 1916): wifi_stop_supplicant enter
I/WifiHW ( 1916): wifi_stop_supplicant end right 1
I/WifiHW ( 1916): wifi_unload_driver enter
I/WifiHW ( 1916): wifi_unload_driver end right 2
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
how to set up MAC address for android builds (except startup.txt)?
Hi again,
I did some search and found that the core of the problem is in getting MAC address for wifi. (as dmsg says). Exactly the same problem was for Touch2, Tilt and other devices (http://forum.xda-developers.com/showthread.php?p=9211659) and it was resolved after they corrected wifi-nvram.txt. This file is responsible for setting up MAC address there, but I couldn't find it at builds for hd2.
if anybody knows what file is used to set up MAC address for wifi, I would be very appreciated.
Thanks!
I believe they just checked for their WiFi mac address from one of the following locations:
Settings->About phone->Status
Wireless & Networks -> WiFi Settings -> Menu Button -> Advanced
Then they edited the nvram.txt file @ /system/lib/hw/wifi/nvram.txt to include the proper MAC address.
Thanks for the answer!
Unfortunatelly wireless settings are not available until wifi is turned on.
I investigated the problem deeper and found that the reason could be in wifi hardware initialization. I did dmesg and saw the following:
wlan: wifi_set_power = 1
htcleo_wifi_power: 1
wlan: wifi_set_carddetect = 1
htcleo_wifi_set_carddetect: 1
mmc0: card_present 1
mmc0: Slot status change detected (0 -> 1)
wlan: Dongle Host Driver, version 4.218.204.2
mmc0: queuing CIS tuple 0x91 length 3
mmc0: new high speed SDIO card at address 0001
wlan: DHD: dongle ram size is set to 294912(orig 294912)
wlan: dhd_bus_rxctl: resumed on timeout
wlan: firmware version: ver
wlan: Return_dpc value is : 0
wlan: stop poll
wlan: dhd_bus_rxctl: resumed on timeout
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
wlan: dhdsdio_probe: failed
Since in windows mobile wifi does work I used the firmware files from WM: nvram.txt and rtecdc1.bin. As it turned out nvram in android is located in /proc/calibraion. But unfortunatelly it didn't help. So, I think that the problem is in bcm4329.ko driver. I'm not sure why other people with the same hd2 (t-mobile US) and the same ROM/RADIO/Android have no such issue. Perhaps my broadcomm hardware has a problem which is bypassed in windows, but not in Android.
I wonder if there is a way to get more detailed info than dmesg and logcat give (except building andoid sources of course ).
I don't know if it can help, but still, I'll say it anyway.
I think i had the same problem some times ago.
Wifi in android wouln't work, but was perfectly working in winmo.
it seems that if wifi is on in winmo when you boot on android, the wifi device seems to be blocked in some way.
Do you have wifi enabled in winmo? if yes, try to disable it, and boot on android to see if it works.
Hi kushulain,
Thanks for the advice! (I've almost started to build andriod by myself to find out the reason..) Unfortunatelly wifi was turned off when android was booting.
But this is another point to play around. I haven't tried to boot andriod with wifi turned on.
Thanks!
Just tried to boot andriod with wifi turned on. The device hangs at the beginning of the booting (even before screen with 'htc' appears). I think it is connected to my problem.
Did someone have similar problems?
Hey, I have the same problem, did you find any solution ?
Guys have you tried to change the radio part of the phone with a suitable one?
canavaro said:
Hey, I have the same problem, did you find any solution ?
Click to expand...
Click to collapse
hi, I didn't fix it actually due to lack of time. I tried to use wm hw init files in Android, but it didn't help. There is a score of my posts on this forum regarding this topic so you can find exactly what I tried. The funny thing is that WiFi works in wp7.
To stealth21
yes, that was the first thing I tried.
Here's how to use logcat..There are two main ways to do a logcat, within android, and through adb. Logcat within android can be done one of two ways, through a Logcat app..Here are two good examples are either aLogcat or CatLog I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb.
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Please do NOTE: : I am just sharing. Original post is Here.
Don't be a noob. Be a newbie..!!
Details here.
Great guide! I am glad that I can help you by logcat. Thanks.
Sent from my E10i using xda app-developers app
How long take the. Logcat?
Sent from my E10i using xda premium
ruben21 said:
How long take the. Logcat?
Sent from my E10i using xda premium
Click to expand...
Click to collapse
Whatever you want.
Sent from my E10i using xda app-developers app
Well and how I finish the logcat because I leave them all the night and still run
Sent from my E10i using xda premium
ruben21 said:
Well and how I finish the logcat because I leave them all the night and still run
Sent from my E10i using xda premium
Click to expand...
Click to collapse
Just press CTRL + C
Thanks bro.
☜ Sent from my X10 MP U20i ☞
Hi all,
I've got a little problem here and i was wondering if anyone can help please.
when i install CM10 or any other custom roms i get such an issue that power button works great, it can even lock my screen but when i press it for unlocking screen it doesn't unlock the screen is still black but pressing volume buttons makes sounds, i think screen is unlocked but it's stays black till i don't reboot with longpressing power button.
when i go back to ICS this problem is solved, but it's terrible OS so please someonehelp me
here is the logcat if someone can find out what the problem is
05-31 20:51:40.180 I/PowerManagerService( 406): Going to sleep by user request...
05-31 20:51:40.250 I/Choreographer( 406): Skipped 39 frames! The application may be doing too much work on its main thread.
05-31 20:51:40.250 D/MPLSensor( 406): handle : 4 en: 1
05-31 20:51:40.250 D/MPLSensor( 406): enabled_sensors: 16 dmp_started: 0
05-31 20:51:40.250 D/MPLSensor( 406): MLSetMPUSensors: 70
05-31 20:51:40.250 I/MPL-ml ( 406): Actual ODR: 25 Hz
05-31 20:51:40.250 D/MPLSensor( 406): set_power_states > MLDmpStart()
05-31 20:51:40.250 I/ ( 406): mpu3050_resume: Resuming to 0070
05-31 20:51:40.250 I/ ( 406): mpu3050_suspend: suspending sensors to 0000
05-31 20:51:40.250 I/ ( 406): mpu3050_suspend: Will resume next to 0070
Click to expand...
Click to collapse
At first sight it looks okay, are you sure you have the US bootloader installed?
DefQoN_BE said:
At first sight it looks okay, are you sure you have the US bootloader installed?
Click to expand...
Click to collapse
no i'm not. can u give me a link that i should flash?
I found out that the problem appears after rooting the device
FLaMpeR said:
no i'm not. can u give me a link that i should flash?
I found out that the problem appears after rooting the device
Click to expand...
Click to collapse
If you live in europe you probably have a UK bootloader installed, if you want to install cm 10.1 you need a US ICS bootloader, you can find the files for your device on www.droidbasement.com, click on your device name, download the US_LPL_4.0.4_bootloader.zip and flash it under PDA slot in ODIN
thanks a lot this worked for me
Sent from my Nexus 4 using Tapatalk 4 Beta
FLaMpeR said:
thanks a lot this worked for me
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
No problem
Hi,
Internation Pardus v15 image on rooted i9300, works very well except for this really odd USB connection error when connecting it to my Sony BT3900u car stereo, it was previously connecting without issue on the v15 Pardus build but for unknown reasons to myself now always presents an error.
Does anyone have any ideas as to what might be causing this issue? Any help would be greatly appreciated.
After getting this issue the first time, I ran through a full rebuild, wiped phone/cache/dalvick and error still persisted post rebuild.
Model:
GT-i9300
Android Version:
4.2.2
Baseband
I9300XXEMA5
Kernel version:
3.0.31-702147
Build Number:
Pardus HD Rom XV XXUDME7
Logcat:
E/MTPRx ( 8982): Read Error Came false
E/ ( 8982): read error [0] [Success]
E/MTPRx ( 8982): state from USB_STATE eventDISCONNECTED
E/MTPRx ( 8982): /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt: open failed: ENOENT (No such file or directory)
E/MTPRx ( 8982): stop observing and calling usbRemoved
E/MTPRx ( 8982): In usbRemoved Status bar enabled
E/MTPRx ( 8982): Sending Broadcast
E/MtpService( 8982): onDestroy.
E/MtpService( 8982): Unregister Mtp disable Receiver
E/MtpService( 8982): Receiver not registered: [email protected]
E/MtpService( 8982): unregistering mtpMediaReceiver in UnregisterAllIntent
E/MtpService( 8982): Receiver not registered: [email protected]
E/MTPJNIInterface( 8982): noti = 3
E/ ( 8982): ****** [mtp_usb_mtp_finalize] mtp_close_fd Calling
E/ ( 8982): [mtp_close_fd] fd = 50...
E/ ( 8982): [mtp_close_fd] USB endpoint [50] closed...
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Updating the gInitializeFlag Flag to FALSE
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Calling mtp_stop_io
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input1/enabled: No such file or directory
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input8/enabled: No such file or directory
E/videowall-TranscodeReceiver(10572): broadcastMSG : android.intent.action.ACTION_POWER_DISCONNECTED
E/MTPRx (10600): In MtpReceiverandroid.hardware.usb.action.USB_STATE
E/MTPRx (10600): check value of boot_completed is1
E/MTPRx (10600): check booting is completed_sys.boot_completed
E/MTPRx (10600): Sd-Card path/storage/extSdCard
E/MTPRx (10600): Status for mount/Unmount :mounted
E/MTPRx (10600): SDcard is available
E/MTPRx (10600): The value of first_boot is 1
E/MTPRx (10600): [ 662] The value of first_boot is 1NORMAL SEQUENCE
E/MTPRx (10600): Received USB_STATE with sdCardLaunch = 0
E/MTPRx (10600): configured is false
I'm guessing this is the correct part of the log that pretains to the MTP/USB part. If not I have attached a full log.
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
xpmode said:
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
Click to expand...
Click to collapse
Hi, thanks for the reply.
I did that as quoted, nothing seems to have changed, What should I be looking for?
Thanks!