What 's your battery manufactory and how is it - Focus General

maybe its hard for you to input them
then
a : 三星SDI
b: 三星视界
c: 三星 伊连特有限公司
and what's the date of manufacture
and how is it work, good or bad~

Related

I-mate & caller ID picture patch

Just in case you don't know. Looks lke there is a small problem with the caller ID. Carrier Devices (I-mates) have released a patch. I installed it and not a problem. Looks like other MDA/O2 devices might have the same problem but no offical release and don't think this patch works but for imates. Read the posts @
http://discuss.pocketnow.com/showth...511d51&threadid=14516&perpage=12&pagenumber=2
The patch download is here (large 10mb!)
http://www.imate.com/imate/files/Gitex_Update.cab
Here is the important part of the post.
Here is the tech support post.
Please download the patch from
http://www.imate.com/imate/files/Gitex_Update.cab. Please copy this file to the i-mate Pocket PC and run the file using File Explorer on the device. Backup or synchronize with your PC any data on the device.
Perform a Hard Reset by holding down the Power button while using the Stylus to press the small hole on the bottom left of the device. The Hard reset does erase all user data on the device, so backup or synchronies your device to your PC first to save your data.
Align the screen and perform the cut and past training, and set
the timezone. Then a list of operators settings should appear. Chose one and then accept the Arabic EULA. Let all the applications install, the device will reset automatically when this has been completed.
Actually it is related to the Country Code and Area Code. I have mine working. Goto Setting, Connection, Advanced and Select Location. Put the appropiate country code and area code and it should work well.
My XDA II Device Info:
ROM Version: 1.03.00 USA
ROM Date: 09/24/03
Radio Version: 10513A0
Protocol Version : 1337.13Q

[webOS] [GUIDE] Unbrick the Touchpad

UPDATE:
if you want to get your stock webos back you just need to start
webosdoctorp302hstnhwifi.jar ( find it with google / its the newest webos 3.02)
get the device into developer mode reset (power button + middle button ) and then ( power button + volume up )
follow the instructions of webosdoctor
to get into developermode in the webos just type webos20090606
If you want to mod your webos or want some good software for it, like an Fileexplorer ( internalz pro ) and things like that:
start WebOSQuickInstall-4.2.3.jar ( google it )
if you want a videoplayer just install kalemsoft media player for touchpad
( can be found on the homepage of kalemsoft)
have fun people.
ps: i heard someone trying to port mplayer to the webos, thats great. with that you can play mkv files with subtitles
Updated 1st Post
jlove said:
i just found a solution for everyone with the same issue.
if you press power button and middle button together for abou 10 sec - 15 sec. the device will hard reset.
now press power and wolume button up --> now it is in usb developer mode
start webos doctor and istall the new os.
Click to expand...
Click to collapse
I don't have an issue, but it was very nice of you to come back with a response to your own issue. Now a search will wield an actual resolution. Too many unsolved cases here.
if you have a hd touchpad tablet, then some day, maybe tomorow maybe in a year, you will have that issue.
and then smile and lean back, because now you know the solution
What version is out now? Im on 3.0.2
jlove said:
i just found a solution for everyone with the same issue.
if you press power button and middle button together for abou 10 sec - 15 sec. the device will hard reset.
now press power and wolume button up --> now it is in usb developer mode
start webos doctor and istall the new os.
Click to expand...
Click to collapse
Good post, will save a lot of people. Have a sticky
jlove said:
i just found a solution for everyone with the same issue.
if you press power button and middle button together for abou 10 sec - 15 sec. the device will hard reset.
now press power and wolume button up --> now it is in usb developer mode
start webos doctor and istall the new os.
Click to expand...
Click to collapse
So then, is this a way I can completely reset the device to be like new if I want to sell or give it to someone?
Where do I get a complete copy of the OS to keep on my computer for a possible reload?
Risks of hacking
I have a similar question - and I've checked the boards and wiki, but didn't have much luck finding a simple answer.
What are the risks of modding, hacking, or jailbreaking? I'm assuming that as long as I don't physically impact the hardware (overheating or otherwise) that there will be some way to get the device back to the original state through reinstalling / reset. Can I screw up with software enough that it permanently bricks the device?
I'm new at this, but looking forward to doing some playing around. I just wanted a better idea of what I'm getting into.
From what I've read the web doctor can cure it.
Thanks for the info. Hopefully these devices prove hard to brick. =D Means we don't have to worry as much about beta software.
The longtime webOS folks in the precentral forums are claiming it's impossible to brick a TouchPad.
if you want to get your stock webos back you just need to start
webosdoctorp302hstnhwifi.jar ( find it with google / its the newest webos 3.02)
get the device into developer mode reset (power button + middle button ) and then ( power button + volume up )
follow the instructions of webosdoctor
to get into developermode in the webos just type webos20090606
If you want to mod your webos or want some good software for it, like an Fileexplorer ( internalz pro ) and things like that:
start WebOSQuickInstall-4.2.3.jar ( google it )
if you want a videoplayer just install kalemsoft media player for touchpad
( can be found on the homepage of kalemsoft)
have fun people.
ps: i heard someone trying to port mplayer to the webos, thats great. with that you can play mkv files with subtitles
From the number of reports of android bricks I have seen I would say that is not true. Then again its pretty hard to brick a iPhone
Longtime WebOS user here, it is impossible to brick a palm pre or other webOS devices. The only devices that actually brick are ones that have hardware damage (bad motherboard, etc). Has to do with the bootloader and it's ability to survive just about anything short of nuclear winter. Rwhitby is the man to ask about this stuff but I've done about everything possible to my devices and they still work :-D
It hangs at 12% :-( looks like dead ...
Please OP change the Title. You can not brick a Touchpad unless you play with something that you will never play...
blah
Anyone having trouble restoring the device with the webosdoctorp302hstnhwifi.jar download and run webosdoctorp300hstnhwifi.jar
I tried this after being unsuccesfull after a friend suggested that some people have a different/earlier build
Thats the only thing that worked for me. 3.02 did not
I get stuck with both webdoc jar files ... no idea why.
I can connect via novaterm ... no problem but what´s next to "manually" put the image into the device.
"Once connected to the device, type:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
"
that does not work...
logs:
LOG 1
HTML:
26.08.2011 00:13:25 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Start cluster beyond limit (2845090973 > 901667). Truncating file.
26.08.2011 00:13:25 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: /.palm/=2R3UM52A=/=2TLV4Y===/=2T745F5Q=/=2R3UM552M6BWYD57ZYKCQ====/=2RT35HNKV6JQJQESQJQSIUNJGBL65XXM7F3ZYVJHYJY======/=2QL45P5I=/=2TT34X2KG6Y======/=2QL45T6S77JRJA===/=2RP65R6SQ754LB6MARNITEKQ=/=2RL3A====/=2T745T7Q4/\014\215¶XÃñ\214°.\007\212(
LOG 2
HTML:
Trenchcoat: /.palm/=2R3UM52A=/=2TLV4Y===/=2T745F5Q=/=2R3UM552M6BWYD57ZYKCQ====/=2RT35HNKV6JQJQESQJQSIUNJGBL65XXM7F3ZYVJHYJY======/=2QL45P5I=/=2TT34X2KG6Y======/=2QL45T6S77JRJA===/=2RP65R6SQ754LB6MARNITEKQ=/=2RL3A====/=2T745T7Q4/FSCK0015.REN
26.08.2011 00:13:22 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Directory has non-zero size. Fixing it.
26.08.2011 00:13:22 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: /.palm/=2R3UM52A=/=2TLV4Y===/=2T745F5Q=/=2R3UM552M6BWYD57ZYKCQ====/=2RT35HNKV6JQJQESQJQSIUNJGBL65XXM7F3ZYVJHYJY======/=2QL45P5I=/=2TT34X2KG6Y======/=2QL45T6S77JRJA===/=2RP65R6SQ754LB6MARNITEKQ=/=2RL3A====/=2T745T7Q4/FSCK0015.REN
Log 0
HTML:
26.08.2011 00:13:29 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: /.palm/=2R3UM52A=/=2TLV4Y===/=2T745F5Q=/=2R3UM552M6BWYD57ZYKCQ====/=2RT35HNKV6JQJQESQJQSIUNJGBL65XXM7F3ZYVJHYJY======/=2QL45P5I=/=2TT34X2KG6Y======/=2QL45T6S77JRJA===/=2RP65R6SQ754LB6MARNITEKQ=/=2RHVA====/s"\012);\012\000\000.\000\000\000
26.08.2011 00:13:29 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Bad file name.
26.08.2011 00:13:29 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Auto-renaming it.
26.08.2011 00:13:29 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Renamed to FSCK0001.REN
26.08.2011 00:14:38 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Unknown trenchcoat error
26.08.2011 00:14:38 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: retrying trenchcoat
26.08.2011 00:14:38 com.palm.nova.installer.core.stages.TrenchcoatStage$TrenchcoatReaderThread run
There is a Quote icon to add codes guys...
Just like this:
<html>
</html>
Click to expand...
Click to collapse
TravisAntonio said:
There is a Quote icon to add codes guys...
Just like this:
Click to expand...
Click to collapse
you can also use the
Code:
tag like so:
[code]
this is code;

[Q] Decrypt the userdata ?

Hi there,
I am actually trying to find a way to decrypt my phone (which was encrypted by a password, not a PIN code, which I set up, and I remember the password, no worries for that).
I actually have a root shell using adb, so I can dump everything on the phone.
My problems is that I don't really know how can I do it ?
I was thinking about a kind of brute-force in offline mode, to guess the secret password, but, the only tools I already found :
Edit: Sorry, i can't post the links, but :
Are both based on a PIN code, and I don't really know where I can find the required file (the footer, and the header), so it seems not working
Is someone already done that before, on a Galaxy S4 ?
Thanks in advance,
Regards,
4m0ni4c.
Ok, so i'm progressing !
Now I successfully found where is the major information I need to execute my script, i got :
Magic : 0xD0B5B1C5
Major Version : 1
Minor Version : 0
Footer Size : 216 bytes
Flags : 0x00000008
Key Size : 256 bits
Failed Decrypts: 0
Crypto Type : aes-cbc-essiv:sha256
Encrypted Key : 0x0000000000000000000000000000000000000000000000000000000000000000
Salt : 0x00000000000000000000000000000000
----------------
But because the Encrypted Key and the Salt seems not really good (Oh really ?) the next step is also not working well !
If someone have any idea why, I am not refusing any help ^^
Regards.

New Update OWINCE C500 Android 7.1.1 with Key Files - Release 2017-08-22

Hello All,
Sorry for my bad english.
NB : i can't put correctly the link ( Add dot and http. I am new to this forum i must have 10 post.
You will find in this post the last update sent by the manufacturer of Onwince through Krando sellers.
i have in autoradio like this video : youtube.com/watch?v=Q8N3TzipBv4
the Key File is used for program the keys for this type of radio
How Upgrade :
Unzip the file and copy the two files in the root of your SD card or USB key formatted in 32 format
3561.bin
3561.upd
mega nz/#!8cRBSLZK!KQab7gauIwNpdg7ajoHuUEkSAeL880Inq8ki7W2zBl0
NB : don't rename the files.
click on the reset button and just after touching the touch screen many times until you see in the display on the top left the word upgrade.
the upgrade will be done automaticly
How the INstall Key File :
Key files : mega nz/#!lEAyjYSB!Ia4oSRLTn55-BSf9Da752j1e61BcJlQDPYfUvMZWE1o
youtube com/watch?v=YUPBmD6Bf3E&feature=youtu.be
Best Regards
Akram (Alias : FuTuR)
Is there any bugs after upgrading to this Firmware ?
This Firmware suitable for octa core Head unit ?

[CODES] Documented secret codes for OnePlus 5T

There was a thread noticing all the codes but they are not documented so this might be useful.
Disclaimer: I am neither resposible to accuracy of description of these codes nor any damage/loss caused by using codes improperly/recklessly.
Notice: Codes here are based on H2OS (which is the stock ROM in China rather than OxygenOS), so some of the codes may not be available in OxygenOS.
Language
*#008# : Change system language to zh-CN immediately.
*#67760044# : Change system language to en-US immediately.
Diagnostic
*#10000# : Show diagnostic results. If you have never cleared them manually or messed with diagnostic menu or functions before, this is your in-factory test result, which should be all OK.
*#800# : System logging menu.
*#808# :Don't operate functions recklessly in this menu. Diagnostic mode main menu.
*#802# : GPS test.
*#803# : Wi-Fi test.
*#804# : Mobile network searching test.
*#805# : Bluetooth test.
*#806# : Don't use this code recklessly since it would take long and may cause other issues if being stopped forcefully. Burn-in quality test.
*#807# : Auto test, which tests lot of things one by one.
*#809# : Microphone Loopback test.
*#814# : TD-SCDMA network searching test.
*#824# : WCDMA network searching test.
*#834# : LTE network searching test.
*#900# : Rear camera test.
Information
*#1234# : Show a dialog box about SoftwareVersion.
*#66# : Show IMEI and encrypted IMEI.
*#6776# : Show more about software version compared to 1234 code.
*#888# : Show motherboard PCB ID and it's QR code.
*##*37847# : Show hardware components' model and suppliers.
Engineering
*#36446337# : Don't operate functions recklessly in this menu. Engineering mode main menu.
*#268# : Don't use this code recklessly as it may damage baseband. NV param testing and calibration.
*#801# : Switches for enginners.
*##*8110# : OTA test mode switch. This switch could probably be used for blocking OTAs.
Others
*#8778# : Factory reset. You will lose all your data.
*#911# : You may lose all your data. This would send you back to first-time setup page after reboot.
*#99# : Screen always on. Enter the code again to disable.
Easter Egg
Not sure if ever presented in OxygenOS.
Game Space - Options - Fnatic Mode - Click the Fnatic icon repetitively - Type "alwaysfnatic" in the textbox poped up - New hidden wallpapers !
Thanks for sharing

Categories

Resources