Database Users

Need Galaxy owner near Aachen (Germany)

Hi,
i am looking for a Galaxy owner near Aachen (Germany) which helps me to bring my device to recovery or download mode. Download mode works (see here http://forum.xda-developers.com/showthread.php?t=781958&page=1) but now i need some help. I will visit somebody, if the distance is not to long
kind regards
srkonus

i live a little far from aachen (near hamburg) but german galaxies are standard GT-I9000's and i have seen none which would fail to enter download mode. the steps are always a bit confuse in all the posts (and in the thread where you have replies)
Just follow these EXACT steps, don't do anything differently, really !:
- Remove the phone's back cover
- Remote the battery
- Remove the SIM card
- Remove the SDCARD (if any)
- Remove the USB cable (if any plugged)
Push Volume UP and the home button; keep them pushed.
Insert the battery (ask help if you can't manage alone) - keep other buttons pushed!
If the phone doesn't boot:
- keep the buttons pushed, and also push the power button
- wait until the phone starts, it says "GT-I9000 blabla" then a few seconds later the screen flashes and some text scrolls - RELEASE ALL BUTTONS QUICKLY
- you are now in recovery mode. Use volume up / down to select "wipe data/factory reset" and use the home button to select that. After this reboot, it probably fixes it.
IF it never shows up the recovery mode, it doesn't even scroll text etc: your recovery is broken (maybe you broke it with whatever tool). No need to panic, download mode must always work.
Download mode procedure:
- Remove the phone's back cover
- Remote the battery
- Remove the SIM card
- Remove the SDCARD (if any)
- Remove the USB cable (if any plugged)
Push Volume DOWN and the home button; keep them pushed.
Insert the battery (ask help if you can't manage alone) - keep other buttons pushed!
If the phone doesn't boot:
- keep the buttons pushed, and also push the power button
The phone should boot quickly and pass from black screen to the yellow screen with "downloading..." if you use GT-I9000 its already too late (you can reboot again by removing the battery or pushing the power button for more than 10s)
IF none of this works: verify your buttons are working properly and not broken or having wrong contacts.

bilboa1 said:
i live a little far from aachen (near hamburg) but german galaxies are standard GT-I9000's and i have seen none which would fail to enter download mode.
Click to expand...
Click to collapse
Ouuuh,
if you take a look into the "android-hilfe.de" board, you will see lots of people who cannot get into download mode!

Fr4gg0r said:
Ouuuh,
if you take a look into the "android-hilfe.de" board, you will see lots of people who cannot get into download mode!
Click to expand...
Click to collapse
oh **** ^^
one beer per galaxy recovered by pressing stuff properly
xD
i've got like 10 galaxy s coming from germany in my hands (all had JF3) including mine none had issues going into download modes when done properly
even when the partitions are broken it still goes into download mode (ofc not recovery then, that only works with a working system)
if any of them is in the north of hamburg and think they need a hand u can tell them to pm me here. my german is not very good but it works out
if they're skilled and theres a real issue, ive never encountered that on my friends phone/providers or mine (mine was not carrier sponsored)
maybe there's a specific carrier that has those modified phones like bell which i'm unaware about ?

Hi,
i recovered my phone but it is maybe a good idea to know if there is a user near aachen to exchange know-how by a beer

Stuck at Omnia7 Logo

Hi,
Omnia 7 had been working fine up until now, steps leading up to the event:
* Debranded registry using chevron tool to install a regedit app.
* received pre nodo update and installed
* Used vpn workaround to install nodo update
* Phone worked fine for a month then when the 'walsh tool' was released I ran that. Went through OK and phone was still useable.
* A few hours later I was browsing the market place and phone rebooted itself and was stuck at the Omnia7 logo. Started phone in USB mode and connected to Zune to restore - got to 34% and errored saying "phone not responding".
* Power cycled again into usb mode and connected to PC but now the device is not recognised at all in Windows (nothing showing in device manager)
* restore mode is disabled but I have ordered a 'jig' tool.
My concern is that if USB mode is no longer picked up in Windows, that restore mode won't be picked up either. I should have the 'jig' in the next day or so.

I had the same problem about a week after I got my Omnia 7 in October last year.
Obviously I hadn’t used any tools for debranding or anything then, It seems like a fault with the phone to begin with, not due to anything you done.
I rang Orange and they sent me a brand new phone the next day. So try ringing your provider.

I tried connecting the phone again tonight and zune picks it up, gets to 99% complete on restore then stops. Seems the USB is being detected again - I did have the battery out of it overnight.

I have the same exact problem but without any jailbreaking
please I you find any solution just tell me
beacuse I don't have warranty I bought it via Ebay

Using the "jig" tool, I was able to enter download mode and reflash the device. I now have a "Welcome to your Samsung Omnia7" screen.
So I can confirm this method works.

Hi
In the Microsoft answer forum someone wrote that the problem was form the battery. So, I will go first with this one.
Regarding the download mode I have problem as well. When I hold pressing the volume up, camera and the power button it display the USB connection logo same as the one in the update. I don't know why!!!

Abd654 said:
Hi
In the Microsoft answer forum someone wrote that the problem was form the battery. So, I will go first with this one.
Regarding the download mode I have problem as well. When I hold pressing the volume up, camera and the power button it display the USB connection logo same as the one in the update. I don't know why!!!
Click to expand...
Click to collapse
That is because your bootloader does not support the Download Mode and enters the Zune Recovery Mode instead.

Hi! try with this
http://windowsteamblog.com/windows_...spx?utm_source=twitterfeed&utm_medium=twitter

Did you try Hard reset?
1. Press and hold down the Power button + Volume down button + Camera button all at the same time until the device vibrates, then let go of the Power button while continuing to hold down the Volume down button and the Camera button.
2. Shortly you should see the message displaying "Are you sure you want to format?", you can now release the Volume down button + Camera button.

I just formated and same problem appear again and again
I don't what to do
please help
in addition to that I don't have the download mode

You will have to get the jig tool to enter download mode to reflash, or send away for repair.
My phone is still playing up, random crashes then stuck at Omia logo. To get it started again I have to reinsert the battery and even then sometimes it gets stuck at the Windows Phone logo. I will try one more flash and if I still have problems I will be raising a warranty claim.

This happened to my phone this morning. Tried to open Beezz, but it wouldn't start (went right back to home screen).
I obviously tried a reboot, but it got stuck at the Samsung Omnia 7 -screen.
So far I have:
(no difference between the steps)
Installed the samsung update patch\fix
Hard reset
Reflash via download mode to KB2
Hard reset
Reflash via download mode to JK1
No success so far. At the moment I'm letting it stay turned on, and every minute or so it flashes black, but returns to the logo screen.
Any help would be appreciated :d

Mine seems to work for a day or so after a reflash, then starts playing up again. Sometimes stuck at logo until I take the battery out and then put back in. I had a problem opening the messaging app, would get the tile animation then back to homescreen. I have arranged to have my Omnia sent back under warranty so will see what they find.

After a power surge, my Omnia hanged then when I rebooted, its now stuck at that Logo Screen. Did everything possible (hard reset, flash rom, go into recovery mode which gets stuck after zune reboots the phone....)
Used the windows support tool and I get this message: The phone is not in the 'Connect to PC' state. Please, make sure that you follow the instructions and your phone shows the 'Connect To PC' image
Any help would be greatly appreciated

Sounds like you have tried everything I would have already. I would send it for repair / warranty.
Turns out my phone WAS faulty and it has been replaced - should receive replacememnt today (Has taken over a month)

Android phone auto-brick itself overnight

When I woke-up this morning, my android phone (Galaxy SII Plus - Default kernel android 4.1.2 - not rooted) was off. I turned it on and it did some "Application optimisation". It automatically rebooted a few times, than I tried to used it. It was very unresponsive. Android keep popping up messages saying that apps like Skype, Google Plus, Google Play Store, etc. crashed. I was really pissed, I never asked for that "update" (or whatever that was) in the first place (I set it to NOT do any update automatically)...
It was completely unusable. It was constantly automatically rebooting. Eventually it popped up the "Application optimisation" message again, the screen turn black and never came back. I waited for about 30 minutes thinking it might be doing something hardcore... but nothing happen.
- Buttons -
I tried to remove the battery, press any combination of "Home" + "Volume up / down" + "Power" buttons but nothing works. The screen stays black, no sound, no vibration, nothing. I can't even go into "Download mode".
What was that update??? How come an automatic Android core update brick my phone??? Did someone manage to steal Android private keys using the OpenSSL Heartbleed bug and impersonalised Android to push malicious updates? I bought my phone in an other country, so I can't go back to the shop. What can I do?
BTW I'm on Ubuntu. I have been using almost exclusively Linux for the last 20 years so feel free to give hardcore suggestions / command lines. I'm also willing to put the screwdriver in the phone if that can help...
Thanks
Gael
------ EDIT ------
- Heimdall / OneClick.jar -
I just tried the OneClick.jar method. It didn't work. I think I have to go into Download mode which is currently impossible.
http://forum.xda-developers.com/showthread.php?p=15330252
------ EDIT ------
- Odin / Kies -
I installed the USB Drivers, Odin and Kies Files on a VM. When I put the battery in the phone, I can see the USB device in the VM (at lease I know that the VM can see the phone) but it's identified as "Unknown device 0A5C:E720 [0202]". The device vanish after about 2 minutes. I assume that the phone run something very low level, like a BIOS, than shutdown the whole thing for some reason. Neither Odin nor Kies can see the phone during that 2 minutes.
But the good news is, something actually happen when I put the battery in. There is no sign of life on the device itself but I can see something from the computer... There is life inside, so there is still hope. If I could put it in Download mode, that would give me more options.
How likely is a USB JIG device to work on such phone state? It's sending something through the USB port, so maybe it would listen to the JIG and go into Download mode...
------ EDIT ------
- USB JIG -
I made a USB JIG from a 270k ohm resistor, some hair thin copped cable and piece of cardboard. It's not pretty, and I don't think I will be able to use it more than once, but it worth a try...
The micro USB female connector is tiny. I'm pretty sure the 2 cables were on the right spot, and I tested the JIG to be sure the 2 copper cables do not short cut themselves before putting the battery in. The reading from my electric tester was 270k exactly, so the bundle is safe. I put the battery back in, waited a few seconds, but nothing happen...
I'm not 100% sure that my JIG works (maybe the copped cable were not pressing down hard enough). But I don't think any JIG can save my phone at this point.
- JTAG ? -
I had a look at some JTAG. That looks over complicated, but that's probably the only way I can reset the boot loader. Those things are very expensive. I will think about it. I'm not even sure the boot loader has been modified. My phone is not rooted, as long as I know, that partition is RO so even a virus could not mess with it...
Would I see the Samsung Galaxy logo if I boot the phone and the boot loader were ok? Or is that logo part of the OS?

Wow...hope everything works out well for you
Sent from my T-Mobile myTouch Q using xda app-developers app

"Your device is corrupt. It can't be trusted and may not work properly." (Red)

"Your device is corrupt. It can't be trusted and may not work properly." (Red)
I was on a phone call when my phone crashed and then displayed the following message:
"Your device is corrupt. It can't be trusted and may not work properly."
There was a URL which directed me to the following site for further information:
https://support.google.com/nexus/an...6399943843044-1589582643&p=verified_boot&rd=1
Has anyone else experienced this?

I also got that message when I first got device. Set up my Google account and then let it sit and charge. Looked 30 mins later that message appeared. It was also followed up by another screen talking about unsecure boot or something and powered it self off. It said can not boot when I tried to restart phone and I tried again and no response from the phone at all.waited 5 mins and it booted fine and never seen the messages again .

that screen appears when the bootloader is unlocked. did you guys unlock your bootloader? or, did you purchase from T-Mo/someone else?

Bl still locked and bought online from tmobile never even loaded any apps yet

anoymonos said:
Bl still locked and bought online from tmobile never even loaded any apps yet
Click to expand...
Click to collapse
if you reboot to bootloader mode, does your screen look like the picture below:

Posted a thread with the same error so you're not the only one. Phone booted fine once it went through it's rolodex of error screens and shut off. Had to manually power it back on.

maruichan said:
Posted a thread with the same error so you're not the only one. Phone booted fine once it went through it's rolodex of error screens and shut off. Had to manually power it back on.
Click to expand...
Click to collapse
if your phone screen in bootloader mode does not look like the one in my post, you purchased the phone direct from T-Mobile/Other Retailer and you didn't unlock the bootloader, i'd ask for a replacement. if your phone screen in bootloader mode looks like the one in my post, the bootloader has been unlocked somehow/by someone...

cortez.i said:
if you reboot to bootloader mode, does your screen look like the picture below:
Click to expand...
Click to collapse
Power + Vol Dwn gives me this screen...

maruichan said:
Power + Vol Dwn gives me this screen...
Click to expand...
Click to collapse
that's not bootloader/fastboot mode.... that's the Factory Reset/Recovery mode. i enter bootloader/fastboot mode using ADB commands (from windows command prompt) while the phone is connected to my laptop. steps to enter fastboot mode:
1. power off device - make sure your phone is not connected to laptop via USB cable
2. hold the Volume Down Key for a few seconds
3. while holiding Volume Down Key connect the Micro USB cable to your device.
4. release Volume Down key as soon as phone goes into Fastboot Mode (screen similar to my post above)
What does your screen say in fastboot mode? to get out of fastboot mode, unplug the USB cable from laptop, hold volume down + power key until blank screen, release all buttons and phone will proceed with boot process.

cortez.i said:
that's not bootloader/fastboot mode.... that's the Factory Reset/Recovery mode. i enter bootloader/fastboot mode using ADB commands (from windows command prompt) while the phone is connected to my laptop. steps to enter fastboot mode:
1. power off device - make sure your phone is not connected to laptop via USB cable
2. hold the Volume Down Key for a few seconds
3. while holiding Volume Down Key connect the Micro USB cable to your device.
4. release Volume Down key as soon as phone goes into Fastboot Mode (screen similar to my post above)
What does your screen say in fastboot mode? to get out of fastboot mode, unplug the USB cable from laptop, hold volume down + power key until blank screen, release all buttons and phone will proceed with boot process.
Click to expand...
Click to collapse
K, will try it in a bit

maruichan said:
K, will try it in a bit
Click to expand...
Click to collapse
by the way, do you have a Korean or US version of the G6? i have the T-Mo version.

cortez.i said:
by the way, do you have a Korean or US version of the G6? i have the T-Mo version.
Click to expand...
Click to collapse
T-mobile US. It is a pre-order
Here is the screen. It is not unlocked.

maruichan said:
T-mobile US. It is a pre-order
Here is the screen. It is not unlocked.
Click to expand...
Click to collapse
i'd request a replacement since your phone is unlocked (based on picture) and you're getting the "...corrupt.." message. maybe go to a corp store show them the problem and request to keep the phone until a replacement is received. good luck.

See still locked

cortez.i said:
i'd request a replacement since your phone is unlocked (based on picture) and you're getting the "...corrupt.." message. maybe go to a corp store show them the problem and request to keep the phone until a replacement is received. good luck.
Click to expand...
Click to collapse
It doesn't seem to effect the function of the phone. So perhaps it is just a bug. Doing a little bit of light research, some other people have had issues with this popping up even with stock on Nexus.
I have until the 17th to exchange/return.

maruichan said:
It doesn't seem to effect the function of the phone. So perhaps it is just a bug. Doing a little bit of light research, some other people have had issues with this popping up even with stock on Nexus.
I have until the 17th to exchange/return.
Click to expand...
Click to collapse
true, but i'd at least make T-Mo aware of the issue. personally, i'd ask for a replacement.

BTW, did anyone get a second screen saying contact customer support (some kind of language like that)? It is very similar to the red error screen, but it read like the device was basically bricked. It disappeared after a while and the phone turned off while I was trying to get a picture.

Got both screens

cortez.i said:
true, but i'd at least make T-Mo aware of the issue. personally, i'd ask for a replacement.
Click to expand...
Click to collapse
I did, that is how I got the return date. They notated my account massively and it looks like it'll be a root canal to a exchange.
I'm not sure that it's anything more than a bug... it hasn't stopped the phone from working and possibly may be an oversensitive security measure on Android's part. So far it seems only related to Nexus(?) that I could find... I am only posting here so others can inform themselves. Maybe others with similar errors who have owned a Nexus could enlighten us.
Either case, doing a factory reset in a little bit. I also received the latest update and applied it. So maybe that'll help too...

franki_667 said:
I was on a phone call when my phone crashed and then displayed the following message:
"Your device is corrupt. It can't be trusted and may not work properly."
There was a URL which directed me to the following site for further information:
Has anyone else experienced this?
Click to expand...
Click to collapse
Yes I have had this happen 2 different times and 4 days apart on my AT&T LG G6, U.S. Variant. NO I don't unlock my devices ever. And I only install well known apps from the Play store. One possible pattern I noticed was that both times it happened relatively soon after turning OFF the always on display. Then when I rebooted the AOD was turned back on by itself. No other settings appear to be changed and my Nova launcher is running normal.
Did you happen to turn off your AOD as well?

"Unfortunately, system UI has stopped" - and that's just the start!!

Hi all,
Hope I might be able to get some advice. Excuse me up front if I butcher the jargon and/or description of the issue, I am but a simple (very, some might say) mobile phone user. I know nothing of the mystical world of 'rooting', and other Andriody black art.
So, here goes.
My wife owns a Samsung Galaxy S5 which hasn't been modified (except for the installation of a few extra apps) since the day it left the Vodafone shop. Today, for no apparent/obvious reason, the following is happening:
Switch phone on, boots into home screen when "Unfortunately, system UI has stopped” message is displayed. Click 'OK', messages disappears for approx 2 seconds and then comes back. Too short a time to do anything else with the phone.
After around a minute, the phone then reboots itself.
Once rebooted -> home screen -> "Unfortunately, system UI has stopped” -> repeat.
The only thing I could see happening, in between pressing the 'OK' button dozens of times, was some automatic App updates (Facebook Messenger and Facebook Pages Manager, were the two I saw).
The back of the phone is also getting pretty damned hot - related?
I've read a few 'Help me' pages online and managed to get the phone into Safe Mode thinking I could at least have a little look around while it was stabile. Wrong. The message and endless reboot cycles still occurred.
I'm loathed to do a full reset as I can't extract the photos from the phone - the phone won't stay 'up' long enough for me to copy them onto my laptop. The phone connects and is recognised but when it reboots itself Windows Explorer cracks it.
I know a lot people say "I didn't do anything", the only thing I've done to the phone prior to this issue was to remove the rear cover and re-seat the SD card (Sandisk Ultra 32Gb, if that's any use).
I really appreciate the time you hopefully take to read this and (hopefully) help out an old boy like me. Thanks heaps in advance.

simarjoshlib said:
Hi all,
Hope I might be able to get some advice. Excuse me up front if I butcher the jargon and/or description of the issue, I am but a simple (very, some might say) mobile phone user. I know nothing of the mystical world of 'rooting', and other Andriody black art.
So, here goes.
My wife owns a Samsung Galaxy S5 which hasn't been modified (except for the installation of a few extra apps) since the day it left the Vodafone shop. Today, for no apparent/obvious reason, the following is happening:
Switch phone on, boots into home screen when "Unfortunately, system UI has stopped” message is displayed. Click 'OK', messages disappears for approx 2 seconds and then comes back. Too short a time to do anything else with the phone.
After around a minute, the phone then reboots itself.
Once rebooted -> home screen -> "Unfortunately, system UI has stopped” -> repeat.
The only thing I could see happening, in between pressing the 'OK' button dozens of times, was some automatic App updates (Facebook Messenger and Facebook Pages Manager, were the two I saw).
The back of the phone is also getting pretty damned hot - related?
I've read a few 'Help me' pages online and managed to get the phone into Safe Mode thinking I could at least have a little look around while it was stabile. Wrong. The message and endless reboot cycles still occurred.
I'm loathed to do a full reset as I can't extract the photos from the phone - the phone won't stay 'up' long enough for me to copy them onto my laptop. The phone connects and is recognised but when it reboots itself Windows Explorer cracks it.
I know a lot people say "I didn't do anything", the only thing I've done to the phone prior to this issue was to remove the rear cover and re-seat the SD card (Sandisk Ultra 32Gb, if that's any use).
I really appreciate the time you hopefully take to read this and (hopefully) help out an old boy like me. Thanks heaps in advance.
Click to expand...
Click to collapse
sorry to hear about your luck mate, but im sure we can figure a way around this issue. The first thing id try is wiping the cache and dalvik cache. that can be done by turning the phone completely off (in your case, probably just pull the battery and put it back after a few seconds), then hold volume +, the home button and power. the phone should vibrate and when it does, continue holding the first two, but release the power button. then itll boot into factory recovery. You use the volume buttons to navigate the menu, and power to select. Go to wipe cache, confirm wipe and reboot

Hi, thanks for the reply. I've just followed your suggested action but unfortunately the phone is still doing exactly the same thing.

simarjoshlib said:
Hi, thanks for the reply. I've just followed your suggested action but unfortunately the phone is still doing exactly the same thing.
Click to expand...
Click to collapse
np. ok, so you should be able to connect the phone to your computer in recovery and mount it so you can get the pictures off. After youve grabbed everything you need from the phone, then nuke it with Odin and the correct tar.md5 file and see what s what at that point

I agree. You might as well root it at that point.

youdoofus said:
np. ok, so you should be able to connect the phone to your computer in recovery and mount it so you can get the pictures off. After youve grabbed everything you need from the phone, then nuke it with Odin and the correct tar.md5 file and see what s what at that point
Click to expand...
Click to collapse
Assume you mean the 'mount/system' option from the system menu (hold volume +, the home button and power)? If so, I select this option and it doesn't appear to do anything. It seems to accept the entry by confirming the action at the bottom of the screen. So, I select 'boot' (top option), the phone starts as usual and then begins the cycle of - error message -> reboot, etc, etc after approx 15-20 seconds.
Is there no way to access the internal physical memory of the phone (even by force) to access the data stored there? Thanks again.

simarjoshlib said:
Assume you mean the 'mount/system' option from the system menu (hold volume +, the home button and power)? If so, I select this option and it doesn't appear to do anything. It seems to accept the entry by confirming the action at the bottom of the screen. So, I select 'boot' (top option), the phone starts as usual and then begins the cycle of - error message -> reboot, etc, etc after approx 15-20 seconds.
Is there no way to access the internal physical memory of the phone (even by force) to access the data stored there? Thanks again.
Click to expand...
Click to collapse
wait, you can actually see this stuff on the screen to select from?