Related
Nice and easy Tool:
http://www.softsea.com/review/Portmon.html
Maybe someone saw/know the yellow Message "UPLOAD data to pc"...
How to catch Data if "Bluescreen" comes and "UPLOAD data to pc" message appears?
It seems this nuke my Portmon...
Any suggestions please?
Maybe I'm blind or these are not stored in Debug folder...
Best Regards
Edit 1.
Changed title.
If you have a Windows XP machine left, try this to watch the serial port:
ups, i can't post links here. Google for serialmon dot com .....
It's output is a little easier to use than portmons. In general, using a serial port monitor to watch the communication between wave and pc, seems to be very unstable business.
Now I'm closer...
Taken info from Samsung GT-S8500L Wave Training Manual SW.ppt...
If someone needs the Settings to attach handset correct, ask me... in this Thread.
Best Regards
Could you post the settings, found this earlier, but couldn't do anything with it.
Thanks
I'll try to describe "short" steps.
1.
You have to be sure that Debug Level Middle is on. Please read here:
http://forum.xda-developers.com/showpost.php?p=10616930&postcount=3
Level Mode High shows more events...
2.
If you have access to Internal menu:
*#7092463*#
Maybe set to High or go to Debug Settings... described in ...Manual SW.ppt...
site 15
3.
Start WinComm and now check site 16 on *.ppt manual. All settings are on Picture.
4.
On handset I have choose Debug Mode instead Kies... this thingie if you plug cable into Wave... maybe go to Settings and set to ask by connection instead Kies
5.
Be sure you choose the "second" Port. Now Wave have 2 COM Ports activated.
Second one is for incoming Data.
Hope this helps an little bit.
If problems ask again.
Then I'll try to make some Screenshots or maybe some other hints...
Best Regards
Ehm have you found that Wincomm2010.exe
Click to expand...
Click to collapse
2010 no, but 2009 like in this Picture is attached.
WinComm2009.zip
Best Regards
Handset
Under Settings->Connectivity->USB->Ask on connection
To have chance to set USB Debugging
Wincomm
I will try later maybe Open or Close for connect to the port.
Important is to choose second COM Port...
Also important to activate UE Awake in settings like on Picture.
As it seems initial AT command is mandatory AT+WINCOMM...
Best Regards
P.S.:
I'm using XP 32 Bit... no other OS tested by me.
so now you can upload fw files from the phone or what???
so now you can upload fw files from the phone or what???
Click to expand...
Click to collapse
Now you could see internal process like Key press, which files involved... etc...
Many high technical stuff. But this could help to understand more.
For me it is very usefull.
I will soon attach few Log examples... maybe then more clear.
Best Regards
i don't suppose that anything can be done if *#7092463*#
doesn't get me a menu?
http://forum.xda-developers.com/showpost.php?p=12798896&postcount=5
Please read deeper this post and follow Links.
As Internal menu is disabled if you flashed ever Rsrc2_S8500_xxx(Low).rc2
Or if you not use Multiloader, then Kies did for you.
This is internal stuff, you have to "unlock" few things before... so read my instruction prior posted.
Please. This is more for advanced users. This is NO must have for all users.
At your own risk.
Best Regards
It seems also good idea to set Trace Level to High... in Internal Menu.
Best Regards
Edit 1:
Seems difference between Firmwareversions...
On JE7 I can see logging if handset is "off" if battery charge Animation is on.
Then if you press ON you can see parts of Booting sequence...
On JL2 I see first something, if Wave is fully on...
Maybe in higher Build some things disabled/removed...
Code:
3539 2255.054 [B]KEY_EVENT_SIG[/B]: [B]Keycode[/B] = 0x8f, STATUS = 0x0.
3540 2255.054 [LCD C]: INFO - FIMD_Drv_Resume()
3541 2255.054 S6E63M0 : LDI_Pentile_Set_Change Pentile_Value =6c
3542 2255.054 S6E63M0 : LDI_PortInit +
6217 2255.055 P00.T11.D001.G-1.E-01:0000 EXCEPTION > [CPLog]: Sub 0014 2263.372 -1: BOOTMGR > _BmPacketReceiveCallback: Boot command is [0x6]
6218 2255.055 P00.T11.D001.G-1.E-01:0000 EXCEPTION > [CPLog]: Sub 0015 2263.372 -1: EXCEPTION > OemTapiNetworkRadioInfoInd: RSSI refresh as AP's awaken
6219 2255.056 P00.T11.D001.G-1.E-01:0000 EXCEPTION > [CPLog]: Sub 0016 2263.372 -1: EXCEPTION > OemTapiNetworkCellInfoInd: Refresh cell Info as AP's awaken
6220 2255.063 P00.T10.D103.G22.E054:B25B EXCEPTION > SmsSvcRegGetSellOutToBeSent: bToBeSent = [0].
6221 2255.069 P00.T10.D103.G22.E054:B269 EXCEPTION > SmsTapiEventHandler: unknown tapi event type.
[B]3543 2255.085 S6E63M0 : LDI_PortInit -
3544 2255.085 S6E63M0 : LDI_S6E63M0_Power_On +
3545 2255.095 S6E63M0 : LDI_S6E63M0_Power_On [hwrev > [COLOR="Red"]S8200[/COLOR]_UNIV_B7]
3546 2255.095 S6E63M0 : LDI_Pentile_Set_Change Pentile_Value =6c
3547 2255.219 S6E63M0 : LDI_S6E63M0_Power_On -
3548 2255.219 Display_LSI : disp_Main_Wakeup [/B]
3549 2255.219 [TSP] reset acq atchcalst=0, atchcalsthr=0
3550 2255.220 [TSP] clear garbage data : Success!! [read 0 times]
3551 2255.220 [TSP] TSP Wakeup...........!
I was wondering why S8200... but now its more clear.
http://forum.xda-developers.com/showpost.php?p=12797112&postcount=249
What we can do...
Collect Key Events...
Monitoring processes like start JAVA Midlets...
Then we can see infos about Heap size...
Code:
9301 433.174 P00.T10.D094.G52.E103:2D83 EXCEPTION > KJxMemoryAvailable: [B]available memory heap[/B] size is 131268608
9302 433.178 P00.T10.D300.G52.E103:2D83 EXCEPTION > KJxSvcIsFileSystemValid: return TRUE!
9303 433.178 P00.T10.D300.G52.E103:2D83 EXCEPTION > KJavaGetMidletAttributeBySuiteID suiteID = 5 is not found
9304 433.179 P00.T10.D094.G52.E103:2D83 EXCEPTION > KJxSvcIsMemoryFull fmQuotaStat.availableSize(943128576), APP_MEMORY_STATUS_MX_MEMORY_FULL_LIMIT(0)
9305 433.180 P00.T10.D094.G52.E103:2D83 EXCEPTION > KJxSvcIsMemoryFull KJx execute limit size = 16384
9306 433.180 P00.T10.D300.G52.E103:2D83 EXCEPTION > KJxSvcIsFileSystemValid: return TRUE!
Many more things...
Best Regards
adfree said:
Code:
3539 2255.054 [B]KEY_EVENT_SIG[/B]: [B]Keycode[/B] = 0x8f, STATUS = 0x0.
3540 2255.054 [LCD C]: INFO - FIMD_Drv_Resume()
3541 2255.054 S6E63M0 : LDI_Pentile_Set_Change Pentile_Value =6c
3542 2255.054 S6E63M0 : LDI_PortInit +
6217 2255.055 P00.T11.D001.G-1.E-01:0000 EXCEPTION > [CPLog]: Sub 0014 2263.372 -1: BOOTMGR > _BmPacketReceiveCallback: Boot command is [0x6]
6218 2255.055 P00.T11.D001.G-1.E-01:0000 EXCEPTION > [CPLog]: Sub 0015 2263.372 -1: EXCEPTION > OemTapiNetworkRadioInfoInd: RSSI refresh as AP's awaken
6219 2255.056 P00.T11.D001.G-1.E-01:0000 EXCEPTION > [CPLog]: Sub 0016 2263.372 -1: EXCEPTION > OemTapiNetworkCellInfoInd: Refresh cell Info as AP's awaken
6220 2255.063 P00.T10.D103.G22.E054:B25B EXCEPTION > SmsSvcRegGetSellOutToBeSent: bToBeSent = [0].
6221 2255.069 P00.T10.D103.G22.E054:B269 EXCEPTION > SmsTapiEventHandler: unknown tapi event type.
[B]3543 2255.085 S6E63M0 : LDI_PortInit -
3544 2255.085 S6E63M0 : LDI_S6E63M0_Power_On +
3545 2255.095 S6E63M0 : LDI_S6E63M0_Power_On [hwrev > [COLOR="Red"]S8200[/COLOR]_UNIV_B7]
3546 2255.095 S6E63M0 : LDI_Pentile_Set_Change Pentile_Value =6c
3547 2255.219 S6E63M0 : LDI_S6E63M0_Power_On -
3548 2255.219 Display_LSI : disp_Main_Wakeup [/B]
3549 2255.219 [TSP] reset acq atchcalst=0, atchcalsthr=0
3550 2255.220 [TSP] clear garbage data : Success!! [read 0 times]
3551 2255.220 [TSP] TSP Wakeup...........!
I was wondering why S8200... but now its more clear.
http://forum.xda-developers.com/showpost.php?p=12797112&postcount=249
What we can do...
Collect Key Events...
Monitoring processes like start JAVA Midlets...
Then we can see infos about Heap size...
Code:
9301 433.174 P00.T10.D094.G52.E103:2D83 EXCEPTION > KJxMemoryAvailable: [B]available memory heap[/B] size is 131268608
9302 433.178 P00.T10.D300.G52.E103:2D83 EXCEPTION > KJxSvcIsFileSystemValid: return TRUE!
9303 433.178 P00.T10.D300.G52.E103:2D83 EXCEPTION > KJavaGetMidletAttributeBySuiteID suiteID = 5 is not found
9304 433.179 P00.T10.D094.G52.E103:2D83 EXCEPTION > KJxSvcIsMemoryFull fmQuotaStat.availableSize(943128576), APP_MEMORY_STATUS_MX_MEMORY_FULL_LIMIT(0)
9305 433.180 P00.T10.D094.G52.E103:2D83 EXCEPTION > KJxSvcIsMemoryFull KJx execute limit size = 16384
9306 433.180 P00.T10.D300.G52.E103:2D83 EXCEPTION > KJxSvcIsFileSystemValid: return TRUE!
Many more things...
Best Regards
Click to expand...
Click to collapse
Heap size can already be changed by accesing the jwc_properties.ini in the AppEx and the User>Exe folder.
astrotom said:
Heap size can already be changed by accesing the jwc_properties.ini in the AppEx and the User>Exe folder.
Click to expand...
Click to collapse
can you recommend a value for it??
give an example for the change??
thanks in advance
mylove90 said:
can you recommend a value for it??
give an example for the change??
thanks in advance
Click to expand...
Click to collapse
There are three jwc_properties.ini files. 1st one in Appex>SysDefault>Java>jwc_properties.ini, 2nd one in Exe>Java>jwc_properties.ini and 3rd one in SystemFS>User>Exe>Java>jwc_properties.ini. Use trix, TkFile explorer or Stune. Personally, I think the first ini file is fore the default java apps on the phone. I think the 2nd one is useless since I didnt see any java apps in that folder using stune. I think the 3rd file is for user installed java apps. I dont know since I am still in the process of modifying the whole bada firmware as far as possible and then I will later flash my phone with my custom firmware. Maybe you could help me tell which files are used for what? Ok, enough talk. Now here are settings for heap sizes that I used: (You can find heap settings at the end of each file)
## Limited MVM configuration
MAIN_MEMORY_CHUNK_SIZE = 82313216 # (78 * 1024 * 1024) + (500 * 1024), 78.5MB
JAVA_MAX_HEAP_SIZE = 65011712 # (62 * 1024 * 1024) + (0 * 1024), 62MB
JAVA_MIN_HEAP_SIZE = 10485760 # (10 * 1024 * 1024) + (0 * 1024), 10MB
MAX_ISOLATES = 4 # AMS Isolate + One application
The last setting, MAX_ISOLATES is the max number of java apps you can run simultaneously while paused. My setting allows 5 apps to run simultaneously. (Remember, Max_ISOLATES value should be one less than the desired value.) Earlier it wave could run only 3 apps.
I am surprised the Samsung provided low java heap sizes for such a good phone! Anyways enjoy!
Thanx astrotom
I'll try next days.
About WinComm... now I understand what this setting means...
I'll try to find combination to work with both, Qualcomm and WinComm.
To log also via QXDM...
Maybe BT is helpfull...
Best Regards
Uuupsi.
Not realized before. But now I have Modem Port connected with:
Upload data to pc
Hmm. But no idea how to catch Data now...
I've changed Port in WinComm...
Hmmmmmm, mabye 1 day in future.
Best Regards
I've played little bit with old SGH-U700...
It has also few similar things like Upload data to pc...
Via known code *#197328blabla... I can find Upload Funct.:
Enable Upload Funct
Disable Upload Funct
Enable Debug Mode in Low
If I try to enable... Can't enable as Dbg Lvl Low...
This U700 is damaged... (damn Touch keys)... maybe I can repair... maybe I can find out what Upload ... can do.
Best Regards
Edit.
I've set Debug Level to high, then also Enable Upload Funct is available...
But still no idea how to start Upload...
how to send AT commands to the phone? i have the first port of my phone as COM9 and the second one as COM10
Hey guys,
i have a problem when building 4.0.3 from source. When i flash the fresh compiled
OTA package to my device, the device ends in a bootloop stuck at the google logo.
Logcat says:
Code:
I/SystemServer( 238): Power Manager
I/SystemServer( 238): Activity Manager
I/ActivityManager( 238): Memory class: 64
I/SurfaceFlinger( 251): SurfaceFlinger is starting
I/SurfaceFlinger( 251): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/IMGSRV ( 251): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086860 (Bad address).
E/IMGSRV ( 251): :0: OpenServices: PVRSRVBridgeCall failed.
E/IMGSRV ( 251): :0: PVRSRVConnect: Unable to open connection.
E/IMGSRV ( 251): :0: OpenPVRServices: Failed to open services connection
E/IMGSRV ( 251): :0: hal_init: Failed to open services (err=-14)
E/IMGSRV ( 251): :0: hal_open: Graphics HAL not initialized
E/FramebufferNativeWindow( 251): couldn't open framebuffer HAL (Not a typewriter)
E/IMGSRV ( 251): :0: hal_open: Graphics HAL not initialized
E/FramebufferNativeWindow( 251): couldn't open gralloc HAL (Not a typewriter)
E/SurfaceFlinger( 251): Display subsystem failed to initialize. check logs. exiting...
I/ServiceManager( 109): service 'sensorservice' died
I/ServiceManager( 109): service 'power' died
I/ServiceManager( 109): service 'entropy' died
D/AndroidRuntime( 259):
D/AndroidRuntime( 259): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 259): CheckJNI is OFF
I don't know whats going wrong. Can it be a kernel problem? I have tried different 4.0.3 kernels from the dev section, but the result is the same.
The device is a GSM device with PRIMEKK15 unlocked bootloader and I9250XXKK6 baseband.
After pulling the latest 4.0.3 sources with repo and setting up the proprietary files i'have compiled the system without errors:
Code:
~/android/4.0.3$ . build/envsetup.sh
~/android/4.0.3$ lunch full_maguro-userdebug
~/android/4.0.3$ make -j4 otapackage
I really don't understand what i am doing wrong ...
Thanks for any suggestions or answers.
i got this problem when I updated my phone using fastboot.
for me, it was an application installed from market. after wipe everything and redo the flash procedure, everything was fine.
don't know if it is the same problem here.
Did you pull in the proprietary files needed for the build?
At least you've got to the boot animation, my ROM fails at the flashing with a status 7 error mentioning the boot.img
PaulW21781 said:
Did you pull in the proprietary files needed for the build?
Click to expand...
Click to collapse
with ./extract-files.sh .correct?
PaulW21781 said:
Did you pull in the proprietary files needed for the build?
Click to expand...
Click to collapse
Yes, the files are pulled from the device ( if you mean the extract_files.sh from the device folder), compilation finishes without errors.
No boot animation, nothing...
Sent from my Galaxy Nexus using XDA App
Now at this point too, bootloops all the time. I think the code is ****ed
Ok, dmesg gave me this:
Code:
<6>[ 5.367248] PVR: Installing MISR with cookie c0833f74
<6>[ 5.367828] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie c79f5700
<6>[ 5.368255] PVR: OSUnMapPhysToLin: unmapping 65535 bytes from c8be0000
<6>[ 5.368469] PVR: SysFinalise: Version string: SGX revision = 1.2.0
<6>[ 5.369171] PVR_K: (FAIL) SGXInit: Incompatible driver DDK revision (785978)/device DDK revision (780209).
<6>[ 5.369537] PVR_K:(Error): PVRSRVFinaliseSystem: Failed PVRSRVDevInitCompatCheck call (device index: 0) [449, drivers/gpu/pvr/pvrsrv.c]
<6>[ 5.370025] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]
<6>[ 5.552337] max17040 4-0036: online = 1 vcell = 4007500 soc = 77 status = 1 health = 1 temp = 340 charger status = 0
<3>[ 5.643005] init: sys_prop: permission denied uid:1001 name:net.rmnet1.dns1
<3>[ 5.643737] init: sys_prop: permission denied uid:1001 name:net.rmnet1.dns2
<3>[ 5.644287] init: sys_prop: permission denied uid:1001 name:net.rmnet1.gw
<3>[ 5.645263] init: sys_prop: permission denied uid:1001 name:net.rmnet2.dns1
<3>[ 5.645812] init: sys_prop: permission denied uid:1001 name:net.rmnet2.dns2
<3>[ 5.646484] init: sys_prop: permission denied uid:1001 name:net.rmnet2.gw
<6>[ 5.707031] [MODEM_IF] misc_open : umts_boot0
<6>[ 5.707153] omap_hsi omap_hsi.0: HSI clock is now 96000000
<6>[ 5.723510] omap_hsi omap_hsi.0: Entering RX wakeup in 3 wires mode (no CAWAKE)
<6>[ 5.723602] [MODEM_IF] xmm6260_off()
<6>[ 5.723724] [MODEM_IF] xmm6260_on()
<6>[ 5.724456] [MODEM_IF] PA EVENT : reset =0, pa=1
<6>[ 5.724548] [MODEM_IF] umts_ipc0 state changed: OFFLINE
<6>[ 5.835540] [MODEM_IF] PA EVENT : reset =1, pa=0
<6>[ 5.979125] virtio_rpmsg_bus virtio1: creating channel rpmsg-omx addr 0x3c
<6>[ 5.980194] rpmsg_omx rpmsg-omx1: new OMX connection srv channel: 1024 -> 60!
<6>[ 6.087188] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]
<3>[ 6.094604] init: untracked pid 118 exited
Anyone knows how to fix this issue?
Try reflashing the boot.img created by your build..
Did you also install the binaries from the google http://code.google.com/android/nexus/drivers.html#maguro into your AOSP source before building?
I built my own AOSP rom too, but haven't tried it yet.
also
Cleaning up when adding proprietary binaries
In order to make sure that the newly installed binaries are properly taken into account after being extracted, the existing output of any previous build needs to be deleted with
$ make clobber
Click to expand...
Click to collapse
http://source.android.com/source/building-devices.html
sorry if you did all this - I'm a noob to ASOP building
Did you wipe the device before installing the rom and kernel?
Luxferro said:
Did you also install the binaries from the google http://code.google.com/android/nexus/drivers.html#maguro into your AOSP source before building?
Click to expand...
Click to collapse
Hey man, that was the problem! Thank you very much... I didn't knew that such libraries exist for 4.0.3.
After installing the binaries and recompiling the phone boots up. Thanks again, also to all the people who tried to help me.
m0rph3us said:
Hey man, that was the problem! Thank you very much... I didn't knew that such libraries exist for 4.0.3.
After installing the binaries and recompiling the phone boots up. Thanks again, also to all the people who tried to help me.
Click to expand...
Click to collapse
No problem. Glad I can help
I guess that hopefully means my build would work too if I ever tried it. Was hoping official 4.0.3 OTA would be out by now. I might just have to try my build too.
Sent from my Galaxy Nexus using Tapatalk
I ran the script under /device/samsung/toro/
is that the correct place to run it, or should I be running it somewhere else?
Nevermind, I'm dumb. I read the post and got it now lol
I'm having the same issue, except for the toro (CDMA/LTE) galaxy nexus. Are these steps in the right order?
step 0: make clobber, step 1: run the extract-imgtec-toro.sh and make clobber, step 2: extract-files.sh, step 3: build/envsetup.sh, step 4: make?
jab416171 said:
I'm having the same issue, except for the toro (CDMA/LTE) galaxy nexus. Are these steps in the right order?
step 0: make clobber, step 1: run the extract-imgtec-toro.sh and make clobber, step 2: extract-files.sh, step 3: build/envsetup.sh, step 4: make?
Click to expand...
Click to collapse
you don't need to excessively run make clobber. all it really does is delete the out/ directory.
Here's how I was able to get a fully functional build ($ANDROID_SOURCE is your build dir):
0) make clobber; # just for the initial cleansing
1) cd $ANDROID_SOURCE/device/samsung/toro && ./extract-files.sh
2) run extract-imgtec-toro.sh OUTSIDE of your build directory (in a temporary location)
3) copy the contents of $TEMPDIR/vendor/imgtec/toro/proprietary/* into $ANDROID_SOURCE/vendor/samsung/toro/proprietary/
4) cd $ANDROID_SOURCE; . build/envsetup.sh
5) lunch #pick your desired toro build. Probably full_toro-userdebug
6) make
The reality is that extract-files.sh does everything well, except it doesn't include the gpu drivers (so we copy them manually). The make files that extract-files.sh creates DOES reference the gpu drivers, they're just not extracted by the script.
Messing with extract-imgtec-toro.sh will give you make files that don't reference any of the other binaries. Your image will boot, but won't have much else working.
Good luck!
Thanks for the quick reply. Here's my script, let me know if you see any errors.
The reason I did make clobber after the extract-imgtec-toro was because the documentation on google's site recommended doing that.
export TOP=/home/jab416171/android/dev/aosp
export GNEXTEMP=/home/jab416171/gnexproprietaryfiles
cd $TOP
repo sync
make clobber
adb wait-for-device
cd $TOP/device/samsung/toro && ./extract-files.sh
cd $GNEXTEMP && ./extract-imgtec-toro.sh
cp $GNEXTEMP/vendor/imgtec/toro/proprietary $TOP/vendor/samsung/toro/proprietary/
cd $TOP
source build/envsetup.sh
lunch full_toro-userdebug
make -j5
jab416171 said:
Thanks for the quick reply. Here's my script, let me know if you see any errors.
The reason I did make clobber after the extract-imgtec-toro was because the documentation on google's site recommended doing that.
export TOP=/home/jab416171/android/dev/aosp
export GNEXTEMP=/home/jab416171/gnexproprietaryfiles
cd $TOP
repo sync
make clobber
adb wait-for-device
cd $TOP/device/samsung/toro && ./extract-files.sh
cd $GNEXTEMP && ./extract-imgtec-toro.sh
cp $GNEXTEMP/vendor/imgtec/toro/proprietary $TOP/vendor/samsung/toro/proprietary/
cd $TOP
source build/envsetup.sh
lunch full_toro-userdebug
make -j5
Click to expand...
Click to collapse
I think your cp needs a '/*' after the first proprietary. The object is to copy the contents of one proprietary directory into the proprietary directory of another. Unless I'm mistaken, your cp will copy the proprietary source folder into the proprietary destination folder resulting in a $TOP/vendor/samsung/toro/proprietary/proprietary. Either that or error out because you specified to cp a dir without a -R.
You should certainly run a make clobber after extracting new binaries if you have files from a previous build still lying around. if you've already cleaned it out, then its just redundant (and not hurting anything).
Otherwise it looks good to me! Good luck!
Makes sense on the cp command. I haven't actually run the script yet, and thanks for taking your time to overlook it.
And do I need to run extract-files and extract-imgtec-toro *every time* I want to do a build, or can I just extract them once, and copy them from another location on my drive, or will the files they extract just stay in the repository?
jab416171 said:
Makes sense on the cp command. I haven't actually run the script yet, and thanks for taking your time to overlook it.
And do I need to run extract-files and extract-imgtec-toro *every time* I want to do a build, or can I just extract them once, and copy them from another location on my drive, or will the files they extract just stay in the repository?
Click to expand...
Click to collapse
Just once. I usually just tar up my vendor/samsung/toro directory and keep the tar in a safe location. No more extractions once you have it.
I need to power a USB device and communicate with it.
The Android 4.x documentation states that ICS has USB HOST enabled thus allowing other devices connected through USB to the phone, to be discovered/powered...
I have a Desire Z with ICS 4.01 from here: http://forum.xda-developers.com/showthread.php?t=1374927
Is the current ICS alpha USB host enabled?
Thanks
It is my understanding that the USB host isn't working at this time on this ROM.
Thanks,
I thought this IS the default setting in ICS.
Hope it will be out there soon
Usb host function needs hardware support as well. It should be supported by both SOC and the board. I doubt that our hardware included necessery components. sorry.
I'm using MDJ (virtuous?) ICS (4.0.3) and it worked out of the box
Perhaps you could try that one if USB storage is important for you.
EDIT: I misread, sorry! Not sure if USB hosting works with MDJ's rom, haven't tried that.
check this mate
http://forum.xda-developers.com/showthread.php?t=1398493 dont think it will be much help though, we need devs
I was wandering if it could be something similar to how you can enable USB HOST mode in XOOM...
Search for
enable-usb-host-mode-ie-thumb-drives-on-the-xoom
I tried my app both in aosp and in an official nexus s (ICS) at no avail...
Any other thoughts?
Found out more...
Has anyone seen this?
HOWTO: Compile USB Host Enabled Kernel for the G1/Dream
w w w .cs.fsu.edu/~baker/devices/projects/framik/USB-HOST-Kernel.txt
It should be similar to our device, right?
I tried another thing...
I purchased a USB On-The-Go cable, thinking that when connecting my external usb sensor to the phone it will signal the phone to enter USB Host mode.
No luck.
The phone does notice the cable and ICS enters "car mode" (remember that driving wheel icon " it shows on the status bar...)
Is this a step forward or a kick in the but?
dmsgs output when USB OTG cable is plugged in.
<6>[ 4602.157348] [USB] hsusb: ONLINE -> OFFLINE
<6>[ 4602.157592] [USB] handle_notify_offline: notify offline
<6>[ 4602.170227] [USB] lpm enter
<6>[ 4602.170623] [USB] usb_suspend_phy
<6>[ 4602.181701] [USB] send connect type 0
<6>[ 4603.584014] [USB] msm_hsusb: disable pullup
<6>[ 4603.596923] [USB] msm_hsusb: enable pullup
<6>[ 4604.816955] [USB] msm_hsusb: disable pullup
<6>[ 4604.837097] [USB] msm_hsusb: enable pullup
<6>[ 4670.716400] [USB] id interrupt
<6>[ 4670.816864] [USB] carkit_detect: usb ID pin = 0
<6>[ 4670.817138] [USB] lpm exit
- I have no car kit!
<6>[ 4670.926910] [USB] carkit inserted
<6>[ 4670.939697] [USB] carkit: set state 2
<6>[ 4670.940094] [USB] lpm enter
<6>[ 4670.940765] [USB] usb_suspend_phy
<6>[ 4702.414123] [USB] id interrupt
<6>[ 4702.516906] [USB] carkit_detect: usb ID pin = 1
<6>[ 4702.517028] [USB] carkit removed
<6>[ 4702.536956] [USB] carkit: set state 0
<6>[ 4718.810180] [USB] msm_hsusb_set_vbus_state: 1
<6>[ 4718.810211] [USB] hsusb: OFFLINE -> ONLINE
<6>[ 4718.810211] [USB] lpm exit
<6>[ 4718.811340] [USB] hsusb: reset controller
<6>[ 4718.997253] [USB] ulpi: write 0x06 to 0x36
<6>[ 4718.997253] [USB] ulpi: write 0x0c to 0x31
<6>[ 4718.997283] [USB] ulpi: write 0x31 to 0x32
<6>[ 4718.997283] [USB] ulpi: write 0x01 to 0x0d
<6>[ 4718.997283] [USB] ulpi: write 0x01 to 0x10
<6>[ 4718.997314] [USB] handle_notify_offline: notify offline
<6>[ 4718.997344] [USB] msm_hsusb: enable pullup
<6>[ 4719.000366] [USB] suspend
<6>[ 4719.016998] [USB] not AC charger
<6>[ 4719.114501] [USB] reset
<6>[ 4719.114624] [USB] send connect type 1
<6>[ 4719.116790] [USB] portchange USB_SPEED_HIGH
<6>[ 4719.311889] [USB] reset
<6>[ 4719.314178] [USB] portchange USB_SPEED_HIGH
I WANT USB HOST! WAAAAAAAAAAAAAAAAAAA....!
Found more info here
http://forum.xda-developers.com/showthread.php?t=702742&page=17
Might need to apply the patch to the ICS kernel if not already included
Need to find how to get/patch/build the kernel...
great, im not alone with the need of usb host!
as i referred to in this thread -
see: Nexus One USB host mode driver
and youtube videos:
USB host mode on the HTC Desire
Nexus One USB host mode
this way i tried compiling a new kernel with usb host mode in kernel config, but i wasnt able to boot it up...(stucks at htc logo)
im not sure what im doing wrong cause i didnt figure out how to get the bootloader output, maybe im missing the ramdisk..
my linux knowledge doesnt seem to suffice (yet ) for android devices to do development stuff, so im hoping the devs enable usb host mode in another rom-update
Wow! Somebody is interested in USB Host beside me!
Andromadus Alpha v9 now lists USB - UMS.
Could this be IT or is this the feature available only to devices with removable storage card slots?
xperia arc has it
I convinced a colleague to let me try his phone and with the USB OTG cable I bought I've been able to connect a mouse to the phone and click on the icons and also connect my work desktop keyboard to the phone and type like crazy in an edit field...
Thinking about switching...
So here upping the thread, usb host has (probably) been done on G2, but don't get too excited. At the time of the sdk ICS port OdienmanSam (sorry if it's not right spelt), managed to get it to work, if I remember well, as he has deleted all his posts. I've tried to MP him, but no luck. We may contact the devs, I'll do it with Andromadus devs.
Usb host in ICS
I can confirm that
Andromadus Alpha 10
Virtuous Quattro rc 1,2,3
Virtuouw Quattro beta 8,9
all doesn't support usb host with an usb otg cable.
They're all getting the carkitmode
Problem in USB HOST MODE
I am developing application to detect my printer by NOVO 7 Paladin(Android 4.0).
By USB HOST CONTROLLER application(which is available in market) the printer/mouse/keyboard is detected. But in my application(Written in java) these devices are not detected
With the reference of below link this application is developed
developer.android.com/guide/topics/usb/host.html
My Code Sample
mUsbManager = (UsbManager)getSystemService(Context.USB_SERVICE);
HashMap<String, UsbDevice> foundDevices = mUsbManager.getDeviceList();
Iterator<UsbDevice> iterator = foundDevices.values().iterator();
if (foundDevices.size()>0)
{String old = textv.getText().toString();
textv.setText(old +" foundDevices ");
}
The USB-HOST API Solution
Hello Camaradas
I've been searching a lot for this, and couldn't find it. But thanks to all the people who have spent a few moments answering our questions, and the wiki resources on the web I figured it out. So I would do the same in bring back.
There are some missing files in some android builds, like the AINOL NOVO 7 PALADIN. I think this would work in any ICS tablet with the same issue. I understand that the Galaxy Tab has the same issue but I'm not sure, I don't have one but if you do, let me know if it work.
So lets push the files in and see how it goes.
>==================================================================<
Copy some missing files into system drive.
$ adb remount
$ adb push AINOL_FIX/system/etc/permissions/android.hardware.usb.host.xml /system/etc/permissions
$ adb push AINOL_FIX/system/etc/permissions/android.hardware.usb.accessory.xml /system/etc/permissions
NOTE: If an error appears displaying Out of Memory, it's right and you must delete some files from system drive. I recommend some live wallpapers from system/app.
>==================================================================<
I understand that for writing system drive you should have root access, I already had it when I did this so if it doesn't work, root it.
You can get the files from android source builds or from a tablet where USB-HOST API is actually working. I got them from linaro's ICS build for pandaboard.
Let me know when you have your USB-HOST API working.
Hi, I am the happy owner of a DHD for more than a year and a half now, and quickly installed a LeeDroid rom (v2.2 about a year ago, based on Froyo with HTC Sense). It works fantastic, however I wanted to see how the roms evolved since then, so I tried new ones, Gingerbread and ICS based ones.
And here the problems start, whatever new rom I try, the SD card after a not very long time (maybe 10 or 20 minutes) stop being recognized by the new system. If I unplug it, the system goes off, so I restart, but then the same problem happen anyway.
The SD card I am using is a 32GB model I bought about a year ago. I never had any problem with LeedDroid rom with it, and actually still have no problem with it (thanks to ClockworkRecovery here, I could revert to the working rom)
Has any one heard of a problem of this kind ? I googled quite a bit but didn't find anything ... Could it be that this big SD card (32GB is quite big) needs more power, and newer kernel try to save a bit too much of it ?
I'll make more test, maybe there is a specific action I do at the moment where I lost the SD card, but I haven't identified it yet ...
Any help or suggestion is welcome !
Some informations about what I found in kernel traces :
It starts with :
<4>[ 524.603302] [BATT] [x0]3 [x8]16 90 9 80 64 a0 f6 f6 e 5c
<4>[ 524.603546] [BATT] V=3928(64a) I=-228(fffffdbe) C=954.0/1230(e5c) id=1(98) T=340(169) KADC=802
<4>[ 524.603668] [BATT]S=2 P=776 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137676592]
<6>[ 525.652435] [VIB] Binder Thread #(parent:zygote): vibrates 0 msec
<6>[ 525.652740] [VIB] Binder Thread #(parent:zygote): vibrates 15 msec
<6>[ 525.653717] [ATS][set_vibration][successful]
<6>[ 525.667907] [VIB]vibrator_timer_func
<6>[ 525.668945] [VIB] er.ServerThread(parent:zygote): vibrates 0 msec
<4>[ 554.611755] [BATT] [x0]3 [x8]16 90 9 90 64 80 f7 b6 e 57
<4>[ 554.611999] [BATT] V=3923(648) I=-209(fffffdee) C=952.0/1230(e57) id=1(99) T=340(169) KADC=786
<4>[ 554.612213] [BATT]S=2 P=774 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137706600]
<6>[ 565.466949] [VIB] InputReader(parent:zygote): vibrates 0 msec
<6>[ 565.469573] [VIB] Thread-87(parent:zygote): vibrates 10 msec
<6>[ 565.470153] [ATS][set_vibration][successful]
<6>[ 565.479705] [VIB]vibrator_timer_func
<6>[ 565.500000] [VIB] Thread-87(parent:zygote): vibrates 30 msec
<6>[ 565.500976] [ATS][set_vibration][successful]
<6>[ 565.530212] [VIB]vibrator_timer_func
<6>[ 568.204559] binder: 1333:1339 transaction failed 29189, size 4-0
<6>[ 568.204803] binder: send failed reply for transaction 40612, target dead
<6>[ 573.939361] [VIB] Binder Thread #(parent:zygote): vibrates 0 msec
<6>[ 578.933837] [VIB] Binder Thread #(parent:zygote): vibrates 0 msec
<4>[ 584.621307] [BATT] [x0]3 [x8]16 90 9 80 64 20 f4 d8 e 52
<4>[ 584.621337] [BATT] V=3908(642) I=-282(fffffd36) C=950.0/1230(e52) id=1(98) T=340(169) KADC=796
<4>[ 584.621368] [BATT]S=2 P=773 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137736609]
<4>[ 611.101196] Return_dpc value is : 0
<4>[ 614.632995] [BATT] [x0]3 [x8]16 80 9 80 64 20 f6 24 e 4c
<4>[ 614.633148] [BATT] V=3908(642) I=-249(fffffd89) C=947.0/1230(e4c) id=1(98) T=340(168) KADC=782
<6>[ 614.633361] [BATT] ds2746_notify: 1 77 at 610429628432 (2012-06-05 05:03:15.677851169 UTC)
<6>[ 614.633697] [BATT] power_supply_changed: battery at 610429964125 (2012-06-05 05:03:15.678186862 UTC)
<4>[ 614.647460] [BATT]S=2 P=770 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137766635]
<6>[ 631.344360] microp_led_pwm_brightness_set, data[1] = 255
<6>[ 638.891937] request_suspend_state: sleep (0->3) at 634688051285 (2012-06-05 05:03:39.936365574 UTC)
<7>[ 638.892333] [LS][ISL29028] lightsensor_ioctl cmd 2
<6>[ 638.892456] [LS][ISL29028] lightsensor_disable
<6>[ 638.892761] [R] early_suspend start
<6>[ 638.893096] sleep_stat.0: 0ms 0 0ms 0 - 0 0 0 - 0 0 - 0 0 0 0 0(2012-06-05 05:03:39.937586277 UTC)
<6>[ 638.893310] [DISP]lcdc_blank: ()
<4>[ 638.893432] [lcm]spade_sharp_panel_blank
<7>[ 638.896453] [LS][ISL29028] lightsensor_release
<6>[ 638.897125] microp_led_pwm_brightness_set, data[1] = 0
<6>[ 638.900238] [COMP] Compass disable
<4>[ 638.909484] dhd_get_dtim_skip bcn_li_dtim=3 DTIM=1 Listen=10
<6>[ 638.913208] [VIB] er.ServerThread(parent:zygote): vibrates 0 msec
<6>[ 638.924102] [DISP]lcdc_suspend: suspending
<4>[ 638.924652] [lcm]spade_sharp_panel_uninit
<4>[ 638.925231] [lcm]spade_sharp_panel_power(0):
<6>[ 638.945770] [GSNR] Gsensor disable
<6>[ 638.996826] [R] early_suspend: sync
<7>[ 639.397155] [COMP][AKM8975] AKECS_GetOpenStatus:
<6>[ 639.472778] [R] early_suspend end
<4>[ 644.660858] [BATT] [x0]3 [x8]16 80 9 90 64 b0 f9 38 e 47
<4>[ 644.661010] [BATT] V=3930(64b) I=-171(fffffe4e) C=945.0/1230(e47) id=1(99) T=340(168) KADC=780
<4>[ 644.661224] [BATT]S=2 P=769 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137796649]
<4>[ 674.690887] [BATT] [x0]3 [x8]16 90 9 b0 65 40 fc 44 e 44
<4>[ 674.691009] [BATT] V=3952(654) I=-94(ffffff11) C=944.0/1230(e44) id=1(9b) T=340(169) KADC=779
<4>[ 674.691223] [BATT]S=2 P=768 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137826679]
<4>[ 704.712310] [BATT] [x0]3 [x8]16 90 9 a0 65 40 fc 6d e 41
<4>[ 704.712432] [BATT] V=3952(654) I=-90(ffffff1c) C=943.0/1230(e41) id=1(9a) T=340(169) KADC=778
<4>[ 704.712646] [BATT]S=2 P=767 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137856701]
<4>[ 734.732086] [BATT] [x0]3 [x8]16 90 9 b0 65 50 fc 38 e 3f
<4>[ 734.732421] [BATT] V=3955(655) I=-95(ffffff0e) C=942.0/1230(e3f) id=1(9b) T=340(169) KADC=783
<4>[ 734.732940] [BATT]S=2 P=766 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137886721]
<3>[ 761.839172] mmc2: Data timeout
<3>[ 761.839324] mmc2: DMA channel flushed (0x80000004)
<3>[ 761.839447] Flush data: 0000c003 2ad35120 00000000 00400040 00400040 00000003
<6>[ 761.839752] mmc2: Controller has been reset
<6>[ 761.839965] mmc2: Worked around bug 1535304
<4>[ 761.840209] mmcblk1: retrying using single block read
<3>[ 762.058135] mmc2: Data timeout
<3>[ 762.058258] mmc2: DMA channel flushed (0x80000004)
I get for a few seconds lots of error of this kind :
<3>[ 762.807312] mmc_blk_issue_rq failed!!
<3>[ 762.814666] mmcblk1: error -123 sending read command, response 0x0
<4>[ 762.814788] mmcblk1: retrying using single block read
<3>[ 762.814971] mmcblk1: error -123 sending status comand
<3>[ 762.815093] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 762.815368] end_request: I/O error, dev mmcblk1, sector 27564800
<3>[ 762.815612] mmc_blk_issue_rq failed!!
Then eventually I get this :
<3>[ 763.182128] end_request: I/O error, dev mmcblk1, sector 27564800
<3>[ 763.182342] mmc_blk_issue_rq failed!!
<6>[ 763.190399] spade_sdslot_switchvdd: Disabling SD slot power
<6>[ 763.191040] mmc2: mmc_remove_sd_card exit
<4>[ 764.740875] [BATT] [x0]3 [x8]16 90 9 a0 64 f0 fa 9 e 3d
<4>[ 764.740997] [BATT] V=3940(64f) I=-150(fffffe83) C=941.0/1230(e3d) id=1(9a) T=340(169) KADC=786
<4>[ 764.741210] [BATT]S=2 P=765 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137916729]
<3>[ 765.404113] FAT: Directory bread(block 28471360) failed
<3>[ 765.404266] FAT: Directory bread(block 28471361) failed
Copy the content off the card, format it in recovery and put everything back. Have you done that already?
Sent from my Desire HD using xda premium
Before putting the content back, try it without....
After a while then try it with the content.
Formatting and putting things back on...well, you know.
Sent from a dream.
I didn't try that , but it will take a long long time since I have about 20GB of data on this card
Ok I'll start to make a backup. What is the recommended type of filesystem to format a big SD card ?
When I see the kernel log, I don't think it is a problem at the filesystem level, but rather at a lower level, so I am not quite sure it will help.
Just format it in recovery, it'll format it correctly. If you want to do it manually then format it to Fat32 with 32kB cluster size. That'll increase your read and write speed when copying large files between the phone and computer, rather than use the 'default allocation side's in Windows.
Also try this, first make a backup and format the card in recovery, then go to tools-check filesystem and follow through. Skip the first two steps if you don't want to create a sd-ext and swap partition. My SD card was acting funny and this helped it. It said my partition wasn't properly aligned. If it says it's properly aligned for you then no need to do this.
I don't know if this option is there in CWM, but it's there in 4ext.
Sent from my Desire HD using xda premium
Thanks for the reply. So I reformatted the disk, even added an app partition, though I probably won't use it ... And now it seems to work with cm7.1
I have however a very annoying issue now, USB transfers to the SD card under cm7.1 are very very slow. apparently I am not the only one to experience this (forum.cyanogenmod.com/.../33323-very-slow-usb-sd-transfer-rates/), but I haven't found a solution, if there is one ...
Yeah I've heard of that too. But I never used CM7.1. I started using CM from 7.2 RC0, and I think that was fixed. I remember my USB transfer speed was fine, the same as it was when transferring through recovery or through a memory card reader. Try CM 7.2 RC3. It's the latest. It's a bit misplaced in the Desire HD section of the CM downloads website. You'll find it under 'nightly' instead of 'experimental releases'.
Sent from my Desire HD using xda premium
rkDumper
Utility for backup firmware of RockChip's devices
Version 1.1.1.0 Windows
1. Makes dump of NAND by partitions according "parameter" information (RKFW/RKAF formats)
2. Creates config.cfg for RKAndroidTool (1.xx, 2.xx)
Notes:
1. All drivers must be installed
2. Administrator rights are required
Known bugs:
-
Old versions:
View attachment rkDumper_091.zip
View attachment rkDumper_092.zip
View attachment rkDumper_093.zip (604)
View attachment rkDumper_094.zip (1810)
View attachment rkDumper_095.zip (226)
View attachment rkDumper_100.zip (1480)
View attachment rkDumper_101.zip (716)
View attachment rkDumper_102.zip (4400)
View attachment rkDumper_103.zip (792)
View attachment rkDumper_104.zip (2630)
View attachment rkDumper_105.zip (3812)
View attachment rkDumper_106.zip (8948)
View attachment rkDumper_107.zip (426)
View attachment rkDumper_108.zip
View attachment rkDumper_1.1.0.0.zip
Tested on:
WinXP (32), WinVista (32), Win7 (32/64), Win10 (64)
0bb4:2910 MSC device (USB debug off)
0bb4:0c02 MSC device (USB debug on)
2207:0000 MSC device (USB debug off)
2207:0010 MSC device (USB debug on)
2207:350A RK3566 x88 Pro
2207:330D RK3308/RK3326/RK3388/PX30 Evoo EV-A-81-8-1
2207:330C RK3399/PX6 CSA96
2207:330A RK3368/PX5 Artway X6/HCT MTCD (Car head unit) SOM
2207:320C RK3318/RK3328/PX4 A5X Plus mini
2207:320B RK3229 MXQ 4K
2207:320A RK3288 Jesurun T034
2207:310D RK3126 Proscan PLT9650G
2207:310C RK3128 CS918-rk3128
2207:310B RK3188/PX3 PIPO Max M9 Pro
2207:301A RK3036 Wecast E8
2207:300B RK3168 Starmobile Engage7+
2207:300A RK3066/PX2 UG802
2207:292C RK3026/RK3028 ONYX BOOX C67SML COLUMBUS/?
2207:292A RK2928 Lexibook Tablet Master 2
2207:290A RK2906 TeXeT TB-138
2207:281A RK2818 ChinaLeap M3
If you have another Rockchip SoC send me result of "rkDumper scan" and name of device. I'II send you personal version for test
rkDumper
Utility for backup firmware of RockChip's devices
New version (0.92 Windows) ready
! pre-Release #2;
~ "4GB" bug fixed;
+ support of "USB debug on" mode added;
+ support of RK3026 added;
+ support of RK2906 added;
+ support of VID=0bb4 (HTC? Rockchip devices) added.
Hello,
I have run your utility, but the file sizes of the output differ compared to when I use rktool 2.1 (with finless instructions).
Here's the scan..
Code:
C:\temp\1>rkDumper.exe scan
rkDumper (version 0.92)
Utility for Rockchip's firmware backup
(c) RedScorpio, Moscow, 2014
[email protected]
==========================[ START ]==========================
-- Devices emumerating --
Devices table (found 8 USB devices):
1 Device #0: USB Root Hub
2 Device #1: USB Root Hub
3 Device #2: USB Root Hub
4 Device #3: USB Root Hub
4.1 Device #4: BT-253
VID = 0x0b05, PID = 0xb700
5 Device #5: USB Root Hub
5.2 Device #6: USB Composite Device
VID = 0x2207, PID = 0x0010
Disk #1
5.8 Device #7: USB Composite Device
VID = 0x04f2, PID = 0xb071
==========================[ STOP ]==========================
Thank you.
nevoz said:
I have run your utility, but the file sizes of the output differ compared to when I use rktool 2.1 (with finless instructions).
Click to expand...
Click to collapse
Some types of files have own length in header. This information used for cutting (real size, not whole partition)
here's is mine.
C:\RKDumper>rkdumper scan
rkDumper (version 0.92)
Utility for Rockchip's firmware backup
(c) RedScorpio, Moscow, 2014
[email protected]
==========================[ START ]==========================
-- Devices emumerating --
Devices table (found 7 USB devices):
1 Device #0: USB Root Hub
1.1 Device #1: USB Hub
VID = 0x8087, PID = 0x0024
1.1.1 Device #2: XBOX 360 Controller For Windows
VID = 0x045e, PID = 0x028e
1.1.2 Device #3: Rockusb Device
VID = 0x2207, PID = 0x300b
1.1.4 Device #4: USB Composite Device
VID = 0x09da, PID = 0x90a0
2 Device #5: USB Root Hub
2.1 Device #6: USB Hub
VID = 0x8087, PID = 0x0024
==========================[ STOP ]==========================
wertzPH said:
here's is mine
Click to expand...
Click to collapse
Please tell me the name of the device and the name of SoC
RedScorpioXDA said:
Please tell me the name of the device and the name of SoC
Click to expand...
Click to collapse
thanks for the reply
Starmobile Engage7+, its advertised as RK3066 based on cpu-z, but the loader is rk3168.
wertzPH said:
Starmobile Engage7+, its advertised as RK3066 based on cpu-z, but the loader is rk3168.
Click to expand...
Click to collapse
You can find link to personal version in "Private Messages". I'll wait your report
rkDumper
Utility for backup firmware of RockChip's devices
New version (0.93 Windows) ready
! pre-Release #3;
+ support of RK3168 added;
+ administrator's rights checking added.
rkDumper (version 0.93)
Utility for Rockchip's firmware backup
(c) RedScorpio, Moscow, 2014
[email protected]
==========================[ START ]==========================
-- Devices enumerating --
Devices table (found 10 USB devices):
1 Device #0: USB Root Hub
1.1 Device #1: USB Composite Device
VID = 0x045e, PID = 0x00db
1.2 Device #2: USB Input Device
VID = 0x046d, PID = 0xc05a
2 Device #3: USB Root Hub
3 Device #4: USB Root Hub
3.5 Device #5: Rockusb Device
VID = 0x2207, PID = 0x292c
4 Device #6: USB Root Hub
5 Device #7: USB Root Hub
6 Device #8: USB Root Hub
7 Device #9: USB Root Hub
==========================[ STOP ]==========================
this is mine, and when I try to do "dump" I get:
rkDumper (version 0.93)
Utility for Rockchip's firmware backup
(c) RedScorpio, Moscow, 2014
[email protected]
==========================[ START ]==========================
--- Firmware dumping ---
The utility requires administrator rights
==========================[ STOP ]==========================
I am an administrator, and the device is a RK3026
also, is there a way to dump the loader of these tablets?
Thanks
niabi said:
I am an administrator, and the device is a RK3026
Click to expand...
Click to collapse
Do you run tool as administrator (Ctrl+Shift+Enter on cmd string)? Try to use /admin key
niabi said:
also, is there a way to dump the loader of these tablets?
Click to expand...
Click to collapse
No. But sometime you can found loader in backup.img partition (use imgRePackerRK)
Kudos to RedScorpio!
Great work RedScorpio!
It never hasn't be that easy to create a dump for rockchip devices!
But I still see some room for improvements and also have some questions:
Can I create a full dump of a device including the user partition? I appreciate to create full dumps - so I can play with my devicesm flash different firmwares and finally I'm able to restore everything to the former state - in case it's not possible to create a full dump at the moment it would be great if you could add it!
Another great addition would be if you could simplify the installation of the drivers in windows 8.1 - please take a look at this post: http://forum.xda-developers.com/showpost.php?p=55529498&postcount=56
Basically Microsoft decided to change the behaviour of the usb stack in windows 8.1 and so it's not possible to install the rockchip driver that easily - you need to figure out 3 details of your device and create an exception-rule in the windows registry so your device is handled as it has been with the previous usb stack.
To create this registry key you'll need VID, PID and REV from the usb device - maybe you can display REV also in your output of 'scan' ? (windows device manager don't even display those details...)
Finally it would be great if you could create this registry key automatically (or with another command) in case you notice that the os is windows 8.1 and the device isn't recognized properly - in my case I'll get the following output when I connect my rockchip device without the registry entry:
C:\Users\roland\Desktop\Rockchip Tools\rkDumper_093>rkDumper.exe scan
rkDumper (version 0.93)
Utility for Rockchip's firmware backup
(c) RedScorpio, Moscow, 2014
[email protected]
==========================[ START ]==========================
-- Devices enumerating --
Devices table (found 11 USB devices):
1 Device #0: USB Root Hub
1.1 Device #1: USB Hub
VID = 0x8087, PID = 0x8009
2 Device #2: USB Root Hub
2.4 Device #3: USB Hub
VID = 0x0424, PID = 0x2514
2.4.1 Device #4: USB-Eingabegerät
VID = 0x1bcf, PID = 0x0005
2.4.2 Device #5: USB-Verbundgerät
VID = 0x045e, PID = 0x00db
2.11 Device #6: Unbekanntes USB-Gerät (Fehler beim Anfordern einer Gerätebeschreibung.)
VID = 0x2207, PID = 0x290a
2.14 Device #7: USB-Verbundgerät
VID = 0x041e, PID = 0x30df
2.15 Device #8:
3 Device #9: USB Root Hub
3.1 Device #10: USB Hub
VID = 0x8087, PID = 0x8001
==========================[ STOP ]==========================
I've also attached my debug-log so you can check how to identify a blocked device - the hardware id is displayed as 'USB\DEVICE_DESCRIPTOR_FAILURE' in device manager in windows.
After creating the registry key as explained in the linked post above everything is working fine in windows 8.1, the drivers get installed and I can create a dump with your tool :good:
Finally it would great if you could add an automatic request for administrative permissions in your application - I think this would simplify the execution a little bit more.
Keep up the good work!
nalor said:
Can I create a full dump of a device including the user partition?
Click to expand...
Click to collapse
I still can't find a simple method of determining the full size of the NAND (it need to count user partition size)
nalor said:
To create this registry key you'll need VID, PID and REV from the usb device - maybe you can display REV also in your output of 'scan' ?
Click to expand...
Click to collapse
I have used USB_DEVICE_DESCRIPTOR for detection VID and PID:
Code:
typedef struct _USB_DEVICE_DESCRIPTOR {
UCHAR bLength;
UCHAR bDescriptorType;
USHORT bcdUSB;
UCHAR bDeviceClass;
UCHAR bDeviceSubClass;
UCHAR bDeviceProtocol;
UCHAR bMaxPacketSize0;
USHORT idVendor;
USHORT idProduct;
USHORT bcdDevice;
UCHAR iManufacturer;
UCHAR iProduct;
UCHAR iSerialNumber;
UCHAR bNumConfigurations;
} USB_DEVICE_DESCRIPTOR, *PUSB_DEVICE_DESCRIPTOR;
So what is revision in this structure?
nalor said:
Finally it would great if you could add an automatic request for administrative permissions in your application
Click to expand...
Click to collapse
Sorry, I'm not a programmer. I can't find example for C (CodeBlocks + gcc)
RedScorpioXDA said:
So what is revision in this structure?
Click to expand...
Click to collapse
Solved. Revision detection will be added into new version
rkDumper
Utility for backup firmware of RockChip's devices
New version (0.94 Windows) ready
! pre-Release #4;
+ support of RK3288 added;
+ manifest file added;
+ detection of device revision added;
~ administrator's rights checking algorithm changed.
rkDumper
Utility for backup firmware of RockChip's devices
New version (0.95 Windows) ready
! pre-Release #5;
+ support of RK3128 added;
+ /user key added;
+ ROM size/vendor/ID determinetion added ("info" command);
~ bug of incorrect determination of disks in multi-CD systems fixed.
Just thank you !
rkDumper
Utility for backup firmware of RockChip's devices
New version (1.00 Windows) ready
! Release;
+ /incl key added;
+ /excl key added;
~ some algorithms improved.
Hello, one question, is possible to use this tool with Rockchip/Intel sofia platform? Thanks in advance