Database Info

stuck on Google logo

After updating around 20 apps (altogether ), I noticed the phone was not functioning normally so I tried to reboot it but now it is stuck on Google logo. I've never unlocked the phone nor used any custom roms. I'm on the latest stock rom 2.3.4
I tried removing the battery and putting it back but didn't work. Vol. up + power and then Recovery didn't work either. It gives me a triangle with ! in it and stops right there.
I also tried the USB Jig that forces the phone into downloading mode but it gave me a screen that asks (Unlock bootloader?) with some warnings but I don't know how to accept that. Niether Vol buttons nor Power button worked there
I didn't want to mess up with the phone until I hear from you guys. Please help

up.......

You might have to actually root it or use the Samsung exe back to factory. That is if you don't want to mess with it because if I ware in your position I'd be going back for a new phone. You did nothing wrong and you have 1 year warranty on it.

FYI, the triangle with ! actually is recovery. The UI is hidden until you hold power and press vol down.

matt2053 said:
FYI, the triangle with ! actually is recovery. The UI is hidden until you hold power and press vol down.
Click to expand...
Click to collapse
Thanks man, I didn't know about that
Is wiping the data (factory reset) going to delete my stuff stored on my SD card? like pic., music, vid. etc?
and do I need to actually wipe the data or will wiping the chache only work?

Factory reset reverts your phone back to the way it was when you got it.
That means all your account settings, device settings, installed applications etc are gone. Everything stored on your SD card will remain there - it's a different storage. The good thing about our Google phones is that you only have to login to Google once and all your stuff is back.
You can try wiping the cache first and see if that works, it won't harm anything. But if that doesn't work, I'm sure a factory reset will.
Good luck.
Greetz

frutelaken said:
Factory reset reverts your phone back to the way it was when you got it.
That means all your account settings, device settings, installed applications etc are gone. Everything stored on your SD card will remain there - it's a different storage. The good thing about our Google phones is that you only have to login to Google once and all your stuff is back.
You can try wiping the cache first and see if that works, it won't harm anything. But if that doesn't work, I'm sure a factory reset will.
Good luck.
Greetz
Click to expand...
Click to collapse
Thanks a lot. I already tried wiping the Cache but it didn't work. I guess I'm going with the factory reset now
Thanks again

the factory reset didn't work !
still stuck on Google logo
any advice?

farisallil said:
the factory reset didn't work !
still stuck on Google logo
any advice?
Click to expand...
Click to collapse
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?

Try doing a hard reset.

GchildT said:
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Click to expand...
Click to collapse
I'm not an expert in these things ... is there any post I can follow to do the things you talked about? I'm not sure that I have all the drivers needed on my pc
I do appreciate your help

farisallil said:
I'm not an expert in these things ... is there any post I can follow to do the things you talked about? I'm not sure that I have all the drivers needed on my pc
I do appreciate your help
Click to expand...
Click to collapse
One thing you should consider is just returning the phone, especially if you never flashed or rooted or unlocked bootloader.
Sent from my Nexus S using XDA App

matt2053 said:
One thing you should consider is just returning the phone, especially if you never flashed or rooted or unlocked bootloader.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I would if I was in the States

just unlock it and flash a nice CM7 with Trinity on top
Here's a rooting guide: http://forum.xda-developers.com/showthread.php?t=895545
There's another guide out there for the i9023 (European version).

GchildT said:
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Click to expand...
Click to collapse
No. The device doesn't even show up when I type "adp devices"
Is there anything else I should try?

Thanks
I can perform things with Fastboot
I don't want to root or unlock the phone. Is there anything else I can do?
I tried typing Fastboot update update.zip after downloading the stock rom update 2.3.4 and putting it in the SDK tools directory but it gave me the msg "faild to upload update.zip"

Try to reset with Odin.

[Q] Unable to factory reset

Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section

Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).

I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.

Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App

Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?

I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.

I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back

Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.

rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything

DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty

I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric

Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App

rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.

Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.

how can I boot my [i9023] with broken button and usb cable trick not working

Hello.
Thank you in advance for your help. This is my problem. Fews days ago the button-on-off was broken. I somehow managed to live with that problem. Untill I decided to open the phone and see if I can fix it. I noticed then that is if I remove the battery and put it on again; the phone would boot on its own. I opened the phone and checked it from inside I couldn't see anyhing abnormal. Probably the button needs to be replaced.
while I was assembling the phone, the battery was removed while the phone was booting. Afterwards, the phone didn't want to boot anymore given the fact that the button remains useless. I read on some posts that if I plug the Usb cable to the PC the phone would boot, but nothing happened.
So here's where I am stuck. If anyone knows how I can boot the phone despite the button being broken and the USB trick not working. please help

Try using adb reboot fastboot to boot to fastboot and then change with the volume keys to reboot.
Sent from my GT-I9100 using xda app-developers app

stuck on google screen
xDeadaheaDx said:
Try using adb reboot fastboot to boot to fastboot and then change with the volume keys to reboot.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your help, here's what I have done :
I have had the button replaced. the button works now fine. but the phone is stuck on the google screen and doesn't boot. I have access to Fastboot mode. I've tried to unlock it to be able to copy some recovery file. but i got the message (Failed: erase...).
I tried wipe/reset. when I do wipe cache partition, it formats the partition, i don't know what effects does it have. are all the data wiped? including the ROM? ...but it has no effect and the sysgtem just boots and goes back to the frozen google screen and when I perform factory reset it goes back to the robot with the red triangle screen.
Anyway, I tried the only option left which is "apply update from ADB" the phone goes into adb mode and waits for the update to be sent.
the phone is obviously recongnized in my computer as an ADB interface. i wrote the command <adb sideload update.zip> the update.zip is actually the official 4.1.2 ROM downloaded from google sites and renamed. After the execution of the command, the file was sent, I had then a big hope that this would be the end of my nightmare, at the end of the sending. The phone reacts and displays the following
Finding update package
Verifying update package,
Installation aborted
So this is where I am stuck. If any one can Help please. by the way NS is on the officla 4.1.2 ROM and not rooted and locked
Thank you

Try Nexus Root Toolkit from http://wugfresh.com/nrt
It has lots of tools and options which might help you.
Sent from my Nexus S using Tapatalk

opo not booting anymore, fast boot not working either

My phone stopped working 2 days ago, it wasn't unlocked or rooted or anything.
The battery was empty and I needed too send a text so I plugged it in and tried texting but the phone was too empty so it kept rebooting and after 2 tries it just keeps booting.
Won't get past the one plus logo with the text powered by android at the bottom of the screen, just keeps rebooting to this...
I tried the recovery (power + volume down button) and selected all options, nothing changed after this.
The fast boot option i also tried but it just keeps displaying the text fast boot and nothing more....
Can anybody help or should I return it to one plus , i'd rather try myself if it won't void my warranty because I need a phone!!
Thanks

sectial said:
The fast boot option i also tried but it just keeps displaying the text fast boot and nothing more....
Click to expand...
Click to collapse
That's what fastboot does. It's supposed to receive commands / files via USB cable so you don't have a menu to do anything there.
sectial said:
i'd rather try myself if it won't void my warranty because I need a phone!!
Click to expand...
Click to collapse
Software modification (incl. rooting) won't void your manufacturer warranty on OnePlus. So you're good to go either way.
I'd suggest flashing the current (38R) stock rom via fastboot, there are several threads on how to flash ROM's that way so I won't go into any useless details here. It sounds like there was some unfixable corruption in the filesystem. Flashing the system hopefully will solve the issue

Phone does not boot/Screen blacks out.

So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!

After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?

post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
So during fastboot, the screen actually doesn't go black. I am still able to remain communication and That is when I tried flashing the factory image. How do you make sure that the checksum is correct? I didn't receive any errors during the flash indicating that it didn't flash properly.

If you're using Windows, Hashtab is a good, free checksum program with a GUI.
Download
Info/Review
On Google's image download page, copy the SHA-256 listed, and compare it to what you have locally (which you used to flash onto your phone).

how to boot into twrp? almost the same issue to you, adb cant find my phone.
jcd173339 said:
So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!
Click to expand...
Click to collapse

bush911 said:
how to boot into twrp? almost the same issue to you, adb cant find my phone.
Click to expand...
Click to collapse
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.

post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
It looks like your freezer method works. Putting it in the freezer actually gets the phone to boot completely into google's factory image. its usuable for about a minute until the problem of freezing and turning off reoccurs. It feels like the phone warms up while running so maybe i have a hardware problem rather than software.

I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??

thank you sir, I have twrp installed previously. but the screen doesnt turn on so I can't choose the recovery model. and try to hold the power button for a while the phone will become warm. no other response:crying:
jcd173339 said:
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.
Click to expand...
Click to collapse

Thufail19 said:
I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??
Click to expand...
Click to collapse
Maybe try locking the bootloader? I might try to do that since you and i both are experiencing the same problem with an unlocked bootloader. But i can't see why that would impact anything.