yashsingh1/xdaforums huggingface dataset:
[MDA, XDA, 1010 General] md2020:
How to recover the SX56 from a failed upgrade to Pocket PC

http://supportattws.primus.com/aws/knowledgebase/ATTW14947.html

How to recover the SX56 from a failed upgrade to Pocket PC 2003. (ATTW14947)

SUBJECT:

How to recover the SX56 from a failed upgrade to Pocket PC 2003.

FACT:

Microsoft Pocket PC 2003 Phone Edition

Siemens SX56 Pocket PC 2003

SYMPTOM:

The Siemens SX56 will not function after a failed attempt to load PPC 2003.

Unable to upgrade the Siemens SX56.

FIX:

Pre-requisites:

* A blank 32 megabyte SD (secure data) card.

* A SD card reader.

1. Hard reset the SX56 and press the Power button.

2. A color screen stating "Wallaby Boot" will appear with the version number. A check of the GSM service will be run.

3. Download the XDA (the other name for our phone) OS Image Tool, at http://wiki.xda-developers.com/wiki/XDAtools.

4. Plug in the SD Card Reader with the SD Card inserted in it to the PC.

5. Once download, open "XDA Tools XDA OS Image Tool" from the Start Menu.

* Do NOT use the fix broken boot loader option from the sub folder.

6. In the Source pull down (the top section) click the "..." next to the pull down and go to C:\Program Files\SX56 upgrade utility\english\NK.nbf

* This is the location of the Windows Mobile 2003 Operating System Image that was installed when it was downloaded and ran the initial upgrade process.

7. In the "Destination" pull down, select the SD Card Reader.

8. Click the Copy button.

9. Once the procedure is complete in Image Tool Program, disconnect the SD Card Reader and remove the SD Card.

10. The SX56 should still be at the Boot loader page, if not hard reset the SX56 again and press the Power button to bring it back to the boot loader screen.

11. Hold the Power button and use the stylus to press in the soft reset button (both at the same time).

12. This will bring up a 'Copy Image from SD to ROM' selection.

13. Select "To copy from SD to ROM", (this will take a few minutes).

14. Once the upload completes, soft reset the device.

15. Verify the version number of the device.

* Either from the device menu:

o ROM Version A.30.09 ENG

o ROM Date 01/01/04

o Radio Version A.33.02

o Protocol Version 1.3.3

* Or from the inital boot up screen:

o G1.3.3

o A.30.09

o RA.33.02

16. If problems persist, please contact Siemens at 888-777-0211

Hope this helps

MD2020
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
I hate to create threads, but I haven't seen this issue anywhere. First, I know all phones are not created equal. But, they ought to be somewhere in the ballpark, I'd hope. Currently, I'm running Slim 4.2.2, 3.0-based, no problems. However, I wanted to try out a few different 3.4-based ROMS to see how unstable/stable they were and what they had to offer, as I'm sure Slim will be moving to 3.4 in the future. The problem is that I can only run CM10.1's newest nightly. I don't have any problems with that. Now, any other 3.4-based ROM causes all sorts of problems. This includes, but is not limited to, AOCP, Task's AOKP, and PA (all the newest versions as of today in the Development thread). What happens is when I flash - and I always wipe EVERYTHING except external SD... data, factory reset, cache/dalvik, internal SD, EVERYTHING - the phone boots, but as soon as it boots, everything starts crashing. I can't even get past the setup wizard. I've tried fixing permissions, reflashing over and over, different recoveries, you name it. I've tried different 3.4 kernels figuring it was kernel related. Same thing. Nearly every app on the thing starts crashing. Does this sound like a case where my phone just doesn't like the 3.4 bases yet? And if so, why no problems with CM? I'm not flashing anything besides the ROM base and the GAPPS. I'm just curious if anyone else is having these issues. I understand there's some problems with 3.4 at this time, but from what I've read in the threads, most people are able to boot and get things set up. Any help is appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ragz:
Not at all sure if this is your problem but are you sure your using the right gapps package. Just a suggestion.
[Samsung Epic 4G Touch] deviouskind:
Hey guys, my wife is having an issue with her phone. Its not on the charger and its saying "phone charging voltage too high". I have a feeling this has been asked before so sorry :-/ Let me know what this is all about. Phone is refurbished, about 2 months old. Thanks
[Samsung Epic 4G Touch] gamepro602:
I had this problem before, your charging pin is bent

Laughing at you while eating Jellybeans
[Samsung Epic 4G Touch] deviouskind:
The phone is not on the charger... Its when its off charger.

What she did was took out battery, wiped off device and its been doing fine.
[Galaxy S III Accessories] VulguM:
I'm about to buy one of the i9300 compatible external batteries, such as the Anker Astro 2, Anker Astro 3 or one of the Powergen brand (The 12000 mAh one looks AWESOME). But before I do that, I was wondering if the charge ratio from this kind of batteries to the device is similar to the PC USB (Which takes forever) or the AC charger (That would be very nice).

The aim is to avoid running out of power in a long trip with heavy use of the device.

Anyone of you have experience with this kind of stuff? any recommendations?

Thanks for your time guys.
[Galaxy S III Accessories] moto211:
It should be similar to the charge rate of the wall charger. The astro3 has dual 5v 2A outputs and the astro2 has a 5v 1A and a 5v 2A output. The stock wall wart outputs 5v 1A.

Sent from my SGH-T999
[Galaxy S III Accessories] ristokoo:
I recently bought this for traveling:

Anker® Astro3E Mobile Battery Pack 10000mAh

I'm very happy with it, the charging is fast and the capacity seems to be as advertised. Not too big, and even looks pretty nice :)
[HTC One X] okkie:
hello ...

i have One X with stock JB 3.18 and now i make it unlocked but i dont have recovery at all

only red tingle ...!!!

i want to flash stock recovery to make root then flash touch recovery cause i want to flash custom ROM.

plz help ... thnx
[HTC One X] okkie:
or any 1 add link for Stock JB ROM
[HTC One X] TToivanen:
The red triangle is the stock recovery :eek:

You need a custom recovery both for rooting and flashing ROMs.

Sent from my IceCold One X
[HTC One X] Mr Hofs:
Flash a custom recovery first, then make a nandroid backup, then install a custom rom.

You can't do anything with the stock recovery
[HTC One X] okkie:
thnx for reply ... but if u plz can you tell me where is the custom recovery that i can flash and who will make my phone rooted ?
[HTC One X] Mr Hofs:
You better read up first before you start. You don't have a clue as far as i can see !

Learn fastboot/adb....and all the steps you need to take.....
[HTC One X] TToivanen:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img

Additionally you need superuser.zip that will root your phone, just Google for it.

Sent from my IceCold One X
[HTC One X] Mr Hofs:
And if you want to go straight to a custom rom you can safe yourself from doing the superuser thing. A custom rom is already rooted

Read up in here first please

http://xdaforums.com/showthread.php?t=1592355

:thumbup:
[HTC One X] okkie:
thnx guys, i installed a custom ROM.

its so easy , but with few search and reading :)
[Galaxy S II General] jaykresge:
NOTE: I prefer being on the stock ROM and using KIES. Please either steer your suggestions towards that, or avoid responding. Any posts telling me to dump Kiest and/or go with a custom ROM will be reported as off-topic, as I want this thread to be useful for others like me.

With that said, the main reason that I like the UK ROM is that the stock apps are in English by default, and there aren't TOO many of them (many can be removed/disabled as well). My issue with the unlocked UK firmware is that Samsung UK is bound by the carriers there, so they don't release the XEU firmware until after several carriers have released theirs. We're likely another month away from JB on the UK SGS2.

I once tried another ROM, and while the system language could be set to English, it had some odd quirks and stock apps were limited to the native language of that firmware's country. So, are there any non-carrier ROMs that are predominantly English without too much additional bloatware? I'm likely going to try Poland next. If I have to, I'll remain on UK if it is the best option, even if the wait does suck.
[Galaxy S II General] jr866gooner:
LSN is latest build of JB. I've downloaded but yet to take the plunge. Was going to just wait a few more weeks and see. The main reason i haven't yet is because i use the memo feature. I realised once on JB you can sync it online. You can also back it up with kies but when/if going back to ICS you can't just sync from online (not available with ICS version) plus if you backup with kies you can't wipe after install with JB connect to kies and restore it!
[Galaxy S II General] jaykresge:
I understand that LSN is the latest build, but when you download builds from different countries, you get different language limitations with built-in apps, as well as different built-in apps. IE, the UK firmware has BBC Iplayer built-in, but other countries don't have this.
[Galaxy S II General] kranti2064:
By your requirements, Nordic firmware should suit you fine. Has no extra apps/bloatware apart from stock Samsung (not even Video Hub).

And the above implies that there are no foreign language apps, none at all. Also, Samsung Apps market/Playstore automatically configures themselves to your locale, so you can download the BBC app from wherever it is available.

This will also ensure that Kies compatibility remains as is.
[Galaxy S II General] jr866gooner:
Ah i thought kies wouldn't work? When i flashed Spain im sure you couldn't connect to kies to restore some data! That's a result if it doesn't effect the use of kies!
[Galaxy S II General] mckeowngoo:
Don't want to be reported for going off topic (God forbid in this forum! ) but how do you install another ROM using Kies other than recovery or updates of the base ROM that was originally installed on the phone? I'm really interested to know.
[Galaxy S II General] jr866gooner:
Odin is the only way to do that- i think it picks up firmware and csc(?) codes when connected then checks against Samsung servers.
[Galaxy S II General] mckeowngoo:
So how is the author of the original post moving between ROM's from other countries using Kies?

Yes, Kies is useless and so unfortunately then is this thread.

You need to use Odin.

So what is the point of a discussion on the use of stock, country specific ROM releases if the author of the OP doesn't want to use or discuss the use of anything other than Kies to install the ROM, something that Kies won't do anyway?

And now I fear I will be reported for going off topic in this misleading thread.
[Galaxy S II General] jaykresge:
Once you use Odin to switch to another country's ROM, you can stick with KIES for further updates and device management if that is your preference (as it is with me). A moderator was kind enough to remove one post that was off-topic, but I'm not going to spam the moderators with delete requests. As was stated in the original post; if you don't like stock ROMS and/or Kies, this thread is not for you. Move along.
[Galaxy S II General] jaykresge:
Kranti, thank you for this. I'll try them next.
[Galaxy S II General] mckeowngoo:
I'm not saying I don't like stock firmware. I'm currently using the stock UK Vodafone release myself. What I am saying is that you want this thread to be helpful to others but you claim to only want to use Kies, something which you can't do if you want to try other countries stock ROM releases. This may be misinterpreted or misleading for new members. At least explain that in the OP instead of slamming down a blanket warning and threatening the wrath of the mods for off topic comments. Far from being off topic, I'd say the use of Odin and not Kies was pretty relevant.
[Galaxy S II General] jaykresge:
The desire is to remain on stock partially for Kies usage. Odin for country swapping is a requirement. Since you now understand the distinction, get on topic or please leave the thread.
[Galaxy S II General] mckeowngoo:
I already understood what was required. It's just a pity you haven't made the use of Odin clear in your original post.

As I said, I'm using the Vodafone LSD release. Before that I was using the Nordic LSN firmware. Before that I was using the Spanish LS8 ROM. Apart from the Vodafone bloat and a network connection failure with LSN release, I found very little difference in performance with each of the firmware releases.

I am disappointed that the UK unlocked JB update hasn't been released yet, but if you're limiting yourself to Kies then until it is released and you're not on Vodafone then ICS is the only game in town.
[Galaxy S II General] Jonny:
Ok Gent, thats enough, back on topic please
[Galaxy S II General] HACKDROID_X:
my o2 hanset got jb update yesterday via OTA but i did it through kies
[Galaxy S II General] iowntheworld:
Flashed Indian!

Just flashed stock Indian Firmware and it gives me no trouble! Thanks SamMobile.
[Galaxy S II General] jaykresge:
Nordic firmware ended up being perfect. Much less bloat than the UK firmware a no language issues. Thanks again for the recommendation.
[Galaxy S II General] kranti2064:
May I recommend using the "Thanks" button.. ;)
[Galaxy S II General] jaykresge:
The one downside to this ROM is the lack of Kies support. If I roll back to the March update, I can regain that. The benefit to Kies support for me is that I can then get updates as they roll out, instead of having to search and use Odin. I'll have to see if I can find the differences between the March LSN update and the April LSN update for Nordic countries.

What I'll probably end up doing is waiting for the next Nordic Kies update and flashing that, which should kill two birds with one stone (Kies support and latest version/fewest bugs).
[Galaxy S I9000 Q&A, Help & Troubleshooting] xXJaSoN21Xx:
Hi my gps won't lock on satellites using waze or igo... Anyone knows how I can fix that?
[Galaxy S I9000 Q&A, Help & Troubleshooting] darsik:
You could try top ntp from the play store. It worked for me on my i9001 with cm9.

Read the instructions&Good luck!
[Galaxy S I9000 Q&A, Help & Troubleshooting] nestul:
You could try faster fix app to change the ntp servers and something else, search for it. Also GPS Status or GPS Test app has an option to update your A-GPS data for a much faster fix.
[Raspberry Pi Q&A, Help & Troubleshooting] Lemmiwinx:
Has anyone seen or heard of possibly using an old smartphone touchscreen as a monitor for the pi?

Seems like everyone has old spare phones laying around. Maybe the adaptation is too difficult, but thought I'd just put it out there.
[Raspberry Pi Q&A, Help & Troubleshooting] MpB907:
VNC Is the solution!

I suggest you to setup a VNC Server on the raspberry pi, download a VNC Client on the smartphone, and connect the client to the server. Now you will be able to use your touch phone as both screen, mouse and keyboard for the raspberry pi. You can also just use it as a screen, but it will be pretty low resolution, depending on how large the screen is.

If you don't know what VNC is, it is basically a "remote screen control thing", as I like to call it.

Check out some links here:

Phone VNC Client (Android): play.google.com/store/apps/details?id=android.androidVNC&hl=en

VNC Server for Raspberry Pi: gettingstartedwithraspberrypi.tumblr.com/post/24142374137/setting-up-a-vnc-server

Just a tip, lol.

(Any questions/problems setting up vnc, pm me or email me: x.bluebanana@gmail.com)

-Mpb907#

Source: en.wikipedia.org/wiki/Vnc
[Raspberry Pi Q&A, Help & Troubleshooting] Lemmiwinx:
I was thinking more of inline of just hardware. Ive got a GS3 that bricked, so i was thinking of taking apart and hooking up the screen that way. plus ive got another half dozen phones that arent in use. Didnt know if anyone ever tried it before, seems like such an obvious idea.
[Raspberry Pi Q&A, Help & Troubleshooting] ph87:
Not from a smartphone but you can search for Siemens S65 or Nokia 6610/3310 for Raspberry Pi...

Those are working!

I had not found someone who has got make a smartphone display work...

Gesendet von meinem GT-I9100
[Raspberry Pi Q&A, Help & Troubleshooting] MpB907:
So, hardware...

I don't really know what to do here, but I saw some people hook up a broken smartphone (With working screen) to the raspberry pi via GPIO cables.

Maybe this'll help you: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26&t=34469
[Raspberry Pi Q&A, Help & Troubleshooting] 1911:
If you know what you are doing then I do not think it should be any problem to do so.
[Raspberry Pi Q&A, Help & Troubleshooting] Sithdown:
I was looking for something like this, because I have some old phones with good screens that would come in handy as status screens (I'm already using VNC)

¿Has someone tried to drive any phone screen with the bare GPIO or is a shield needed?
[Raspberry Pi Q&A, Help & Troubleshooting] Lemmiwinx:
Thanks for the link. Its definitely going to work for one of my many pi projects. Love this this community !
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] clarinch:
Hello.

My i727 was working seemingly fine. I left it to charge overnight. In the morning it was off and would not boot past the black and white samsung logo.

I have tried various battery swaps and power combinations. The recovery mode does not load past the samsung logo.

I can load the 'download OS' menu, when I continue, the text reads:

1, ddi : mmc_read failed

ODIN MODE

PRODUCT NAME: SGH-I727

CUSTOM BINARY DOWNLOAD: NO

CURRENT BINARY: SAMSUNG OFFICIAL

I don't know if that means it is completely bricked? I have never attempted to root or flash custom firmware onto this device.

However, it is out of warranty, so if loading a ROM might bring this back to life, then I'm certainly willing to try.

If there is any other information you need to help me troubleshoot this please let me know.

If anyone has any advice, I would appreciate it!

Thanks!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jd1639:
Do a factory reset in recovery mode. If you can't do that you'll probably have to flash the stock rom with odin.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] clarinch:
I don't believe the recovery mode works either.

Holding VOLup + VOLdown + POWER when the device is off simply brings me to the same b/w samsung logo and does not go further.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jd1639:
Can you get into download mode? Have you ever used Odin?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] clarinch:
I was looking at flashing the stock rom as an option. I downloaded Odin3 v1.85 and the suggested stock rom via this guide:

http://xdaforums.com/showthread.php?t=1342348

But, this happens.

So, I found this guide

http://xdaforums.com/showthread.php?t=2023328

but including the pit file doesnt matter. Odin still crashes.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jd1639:
For some reason the pics don't show up. But go to the development forum for the i957 and look for vincom's stickies on odin.

---------- Post added at 05:44 PM ---------- Previous post was at 05:40 PM ----------

Ok the pics did show up. The file you're trying to flash on odin is the problem

---------- Post added at 05:49 PM ---------- Previous post was at 05:44 PM ----------

Go to sammobile.com and download the stock rom. You'll have to register but it's free. It'll walk you through getting the Rom. Download the oldest. It'll be a zip file. From that zip extract the .tar.md5 file using 7-zip. Use that in Odin, PDA. Have auto reboot and f.reset checked
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] clarinch:
Thank you for your time.

The sammobile site has 3 firmwares listed.

The oldest doesn't list a version #, is that still safe to download?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jd1639:
Get ucjk2. If you don't see that get uclf6
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] clarinch:
Did all you said.

Odin still crashes at PIT mapping.

If I add the PIT file as well, it auto-checks re-partition, is that the next step?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] vincom:
if you got "1, ddi : mmc_read failed" u could have nand(memory) hardware failure

when trying to flash the pit file, actually called "celox.pit", repartition should not be checked, but not to sure on that for flashing the pit file

u can try asking cschmitt for clarification

also go through the odin troubleshooting section in the restore to stock sticky
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] clarinch:
Same thing. If it is a hardware failure, then that's the end of the line I guess?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] vincom:
I would still go through the odin ts section

can also read this http://xdaforums.com/showthread.php?t=1704646
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] coronelac:
AH jijo

I have a similar problem and I thought I'd share my experience.

I have two of these phones: one is white and the other black; the black is liquid damaged, stuck in a boot loop and the white was working fine.

I have/had one goal; to transfer raw EMMC data from one phone to the other. The information on the black damaged phone is very important.

Now, I successfully made a complete backup of the damaged phone's EMMC. I then pushed that raw data onto the working white phone's EMMC.

When I tried powering on the phone with the new info the phone had the same symptoms as the black damaged device.

I then attempted to just get the white device back to its working state by trying to flash multiple stock images WITH a PIT file.

There is where I received the same error message in Odin as the OP. I then tried a 3.+ version of Odin and it finished successfully but the device still does not power up.

I am short in time so I will stop here.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Don't use a pit file. Just Odin a stock tar
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Then it's user error
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] 01r6cle:
Does the SAMSUNG logo go out and the phone keeps vibrating every few seconds? My roomates did that and nothing I did fixed it. Finally found somewhere that the power buttons on the Skyrocket gets stuck. So after about 10-15 minutes of installing the battery while flicking the button with my finger, it finally booted.

Don't know if yours is doing the same but worth a shot.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] coronelac:
Just an update to my previous experience. I successfully restored the phone back to it's original state.

For anyone curious; externally re-partitioning the EMMC took care of the issue.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] vincom:
im curious, explain in more detail
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] coronelac:
Used JTAG to access the EMMC and execute a re-partition.
[General Questions and Answers] gvfc2:
ive tried superone click and it didnt work. I tried bin4rys root method and it didnt work i need some help please

EDIT: FYI its LS840ZVK
[General Questions and Answers] gvfc2:
i retried super one click and it still didnt work. any advice?
[General Questions and Answers] Sanjay:
Try root unlock.exe, more effective it is...:thumbup:

................................................................................................
[General Questions and Answers] gvfc2:
it never ran for me so cant use that one either
[Sony Xperia T, TL, TX, V] aman12:
my phone xperia v doesn't start, charge, enter in flashmod or recognised by PC pllz help me
[Sony Xperia T, TL, TX, V] gregbradley:
please post in the correct section.

Please read the thread on soft brick in the general section

Then read the all in one thread in the questiona nd answer section

(Both of them are sticky threads)

Then please provide us with more information than "My phone does not boot" so we can help you

ROM?

Root status?

Bootloader status?

Kernel?

What mods have you flashed?

What did you do just before this happened?
[Sony Xperia T, TL, TX, V] aman12:
am sorry i didnt flash anything its on stock rom and suddenly dead sorry for bad english