[Q] I think I really do have a brick! - Verizon Samsung Galaxy S III

All right. I messed up. I installed PureMotive's v15 and after Aroma was finished, I clicked "reboot" and....nothing. It briefly flashed the Samsung splash screen, but never did anything past that. It wont boot. It won't boot into recovery. It won't even boot into Download mode to try to Odin back....
It DOES display a charging icon when plugged in via USB. ODIN DOES recognize that something has been plugged in to a COM port; however, it hangs on trying to connect to device (i figured it would, as i can't get into download mode...)
FWIW:
Came from Jovy's last release. Was on Mastamoon's 10.1 prior
Full wipe, cache wipe, dalvik wipe.
I did select custom option, Verizon s3, and the bottom kernel on the Aroma list (forget which one....Ktoonz?)
Not sure what to do, as I have never been here before...
EDIT: ADB not working either....very strange. when trying to run a logcat, it just says waiting for device. Maybe I'm doing something wrong? I'm not terribly proficient at ADB...I am getting a bit concerned though....

i5aac said:
All right. I messed up. I installed PureMotive's v15 and after Aroma was finished, I clicked "reboot" and....nothing. It briefly flashed the Samsung splash screen, but never did anything past that. It wont boot. It won't boot into recovery. It won't even boot into Download mode to try to Odin back....
It DOES display a charging icon when plugged in via USB. ODIN DOES recognize that something has been plugged in to a COM port; however, it hangs on trying to connect to device (i figured it would, as i can't get into download mode...)
FWIW:
Came from Jovy's last release. Was on Mastamoon's 10.1 prior
Full wipe, cache wipe, dalvik wipe.
I did select custom option, Verizon s3, and the bottom kernel on the Aroma list (forget which one....Ktoonz?)
Not sure what to do, as I have never been here before...
EDIT: ADB not working either....very strange. when trying to run a logcat, it just says waiting for device. Maybe I'm doing something wrong? I'm not terribly proficient at ADB...I am getting a bit concerned though....
Click to expand...
Click to collapse
Pull battery hold down power home and vol ip button simultaneously to get to recovery. Hopefully you made a back up prior.
Sent from my SCH-I535 using xda app-developers app

i5aac said:
All right. I messed up. I installed PureMotive's v15 and after Aroma was finished, I clicked "reboot" and....nothing. It briefly flashed the Samsung splash screen, but never did anything past that. It wont boot. It won't boot into recovery. It won't even boot into Download mode to try to Odin back....
It DOES display a charging icon when plugged in via USB. ODIN DOES recognize that something has been plugged in to a COM port; however, it hangs on trying to connect to device (i figured it would, as i can't get into download mode...)
FWIW:
Came from Jovy's last release. Was on Mastamoon's 10.1 prior
Full wipe, cache wipe, dalvik wipe.
I did select custom option, Verizon s3, and the bottom kernel on the Aroma list (forget which one....Ktoonz?)
Not sure what to do, as I have never been here before...
EDIT: ADB not working either....very strange. when trying to run a logcat, it just says waiting for device. Maybe I'm doing something wrong? I'm not terribly proficient at ADB...I am getting a bit concerned though....
Click to expand...
Click to collapse
You didn't brick your phone as it would cease to function.

jmxc23 said:
You didn't brick your phone as it would cease to function.
Click to expand...
Click to collapse
It really has ceased to function. Battery pull to recovery doesn't work. Battery pull to download mode doesn't work. the only sign of life whatsoever is the samsung splash (just for a second), then nothing. plugging the phone in shows a charging animation, but nothing from there.

I've never ran into this but will the phone boot into recovery or download mode if the battery is down to a certain percent? Maybe the battery is dead. Charge it for a few hours and try again.

bobAbooE said:
I've never ran into this but will the phone boot into recovery or download mode if the battery is down to a certain percent? Maybe the battery is dead. Charge it for a few hours and try again.
Click to expand...
Click to collapse
battery is nearly full

jmxc23 said:
You didn't brick your phone as it would cease to function.
Click to expand...
Click to collapse
+1
Bricked phone is a lifeless paper weight.
I believe the correct term for your phone is soft bricked?
Sorry for having no help though :/
sent from that young galaxy on clean ROM!

~ $ adb devices (You have adb setup on your computer right???)
~ $ adb reboot recover # this obviously will get you into recovery
~ $ adb reboot bootloader # this will boot you into download mode
If none of this works im pretty sure Adam Outer has a work around to unbrick the S3. Google is your friend.

Related

Fixing a bricked Nexus S

I had a Vibrant before and flashed it constantly. I soft bricked it several time and it was easy just to Odin back to stock and try again. Before I begin to flash Roms on this phone I would like to know how one would fix a bricked Nexus S. I searched "bricked Nexus S" and didn't come up with much.
Sent from my Nexus S using XDA App
Flash a stock img thru fastboot/adb. Just as painless as Odin was if not easier.
Sent from my Nexus S
Yeah I figured that much but I have never used ADB before. What are the commands to flash a stock img and where can I get a stock img? I already have ADB set up, serial # comes up when I enter - adb devices. I'm ready to root and flash but I want to be prepared for anything. I don't want to panic for ten minutes like I did the first time I bricked my Vibrant.
Sent from my Nexus S using XDA App
You should be able to snag a stock image from the development section. As far as what adb commands to use check out any of the root tutorials in development.
Sent from my Nexus S
bricking the phone is not easy... everything can be wiped and reinstalled with ease. Recovery is your friend.
leyvatron said:
bricking the phone is not easy... everything can be wiped and reinstalled with ease. Recovery is your friend.
Click to expand...
Click to collapse
That's why I love this phone. When I first rooted my wife's phone she was a nervous wreck about me ruining it. Now, she jokingly cheers when it boot loops or hangs on the google splash screen.
kenvan19 said:
That's why I love this phone. When I first rooted my wife's phone she was a nervous wreck about me ruining it. Now, she jokingly cheers when it boot loops or hangs on the google splash screen.
Click to expand...
Click to collapse
Coolest wife ever? haha
risegeek said:
Coolest wife ever? haha
Click to expand...
Click to collapse
hehe why'd'ya think I married her
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Van_Dyke said:
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Click to expand...
Click to collapse
not enough information is present. you can attempt to get into bootloader / recovery, plug USB to the computer. When plugged, does the computer make a plugged in noise? if it does.. try turning it on, try using adb on it, etc.
as a last resort: if its not rooted or modified in any way, you can go back to best buy and exchange it since you said you've only had it for 3 days
Van_Dyke said:
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Click to expand...
Click to collapse
First thing to do is pull the battery, let it sit a minute or two, then put the battery back in and try to boot.
Also, try booting into recovery or fastboot. With power off, press and hold volume up button, then press/hold power on switch. You should enter fastboot mode. From fastboot menu, select boot to recovery. The phone will reboot and you'll get to a screen with an "!" and an android robot on it. At that point you press hold power, then press/hold volume up (make note that this is the reverse of what you did earlier).
Once in Recovery, try wiping cache from the menu.
Reboot.
If still no good, then repeat the process but pick factory reset/wipe from the menu in recovery. Note that this will wipe all personal data and apps off the phone but it won't touch your sdcard contents.
The case with pull battery - not working.
I can't enter fastmode using 2 keys combination.
Computer don't recognize the phone. It's brick...
Van_Dyke said:
The case with pull battery - not working.
I can't enter fastmode using 2 keys combination.
Computer don't recognize the phone. It's brick...
Click to expand...
Click to collapse
Last option is to try to trick it into Samsung's Download Mode (see the Odin thread in Development section), but if the keys aren't recognized you can't soft boot into it so you'll need a dongle with a resistor to get there.
Sounds like it's truly a brick at this point. You'll probably have to return it, but I'm concerned about returning a phone that has your personal data on it without being able to wipe it. Doesn't seem like much way around that at this point if you can't get fastboot or download.
get the 301k resistor JIG and then you can go into the download mode even without the 2 keys + usb plug
you can always make your own JIG if you have the materials at home or a nearby Radio shack
Thx for all Your advices
Problem was with the dead battery. The battery died during the night - i don't know why. I think the system waren't able to boot up ant start charging process.
My solution:
I took 9V battery, 2 wires and charged dead battery for a while from 9V battery. Then a put it into phone and plug in to wall charger. Charging process started
Now everything is ok
That's pretty scary that it wouldnt take a charge if run down completelty. But hey handy to know incase it happens to any of us,
If you get any repeat i would take it back to get a fresh battery of course (only right to do so).
here's hoping you never need to though
Van_Dyke said:
Thx for all Your advices
Problem was with the dead battery. The battery died during the night - i don't know why. I think the system waren't able to boot up ant start charging process.
My solution:
I took 9V battery, 2 wires and charged dead battery for a while from 9V battery. Then a put it into phone and plug in to wall charger. Charging process started
Now everything is ok
Click to expand...
Click to collapse
That is scary......
Sent from my Nexus S using XDA App
Bricked
Tried unlocking nexus s last night, now it appears bricked. Cannot connect to computer to reflash as it seems to have wiped the driver. Any ideas on how to bring it back from the dead? thanks
I have managed to see the phone with fastboot. I was hoping that fastboot update, would re-image the brick. Can anyone let me know the correct syntax. I am not able to copy an image onto the phone. Thanks again
Noob {MAC User}... Please be gentle
Greetings Everyone,
Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I reboot.
Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.
What I've done so far:
- wiped cache
- wiped/factory data reset
- retraced my steps by using terminal to setup superuser permission from this post (http://forum.xda-developers.com/showthread.php?t=927838)
What I think:
- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.
This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).
Eagerly waiting for a reply... no cell phone if this can't be fixed.
Tamara
warrenb said:
Tried unlocking nexus s last night, now it appears bricked. Cannot connect to computer to reflash as it seems to have wiped the driver. Any ideas on how to bring it back from the dead? thanks
I have managed to see the phone with fastboot. I was hoping that fastboot update, would re-image the brick. Can anyone let me know the correct syntax. I am not able to copy an image onto the phone. Thanks again
Click to expand...
Click to collapse
It would be easier to help you if we knew exactly what you did that caused the problem. You said you tried to unlock it...you mean fastboot oem unlock or something else?
If you can get into fastboot, you're not totally lost, but the computer needs to see the phone to do it.
I'm working in a vacuum here on what your real problem is, but without further details, the things you can try are boot into recovery (from the fastboot mode select boot recovery)...if you're stock recovery, press/hold power, then volume up once you see the android "!". From there wipe cache and whatever else it will let you wipe. Try rebooting. IF that didn't work go back to recovery and try a factory reset of the phone (will delete all your apps and stuff on the phone, but not on the sdcard (pics and stuff).
If none of that works, you can still try getting Clockwork recovery on the phone via fastboot. Boot phone to fastboot and then on computer type the command "fastboot flash recovery <put file name of recovery version you're flashing here>"
Once in clockwork, you should have access to adb via the computer. On your computer go to the Development section here and download any of the various nandroid images posted there. Now you use clockwork mounts and storage menu to mount the sdcard. Then use adb to "adb push <insert path and filename of your nandroid image here> /sdcard"
Unmount the sdcard with the clockwork mounts and storage menu. Now go to the backup menu, select advanced restore and find the nandroid image and restore it.
With any luck, you should be able to boot into a fresh phone.

[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.

[Q] Bootloop! Tried ODIN

Hi,
So I got a bootloop after wiping battery status on recovery. But first I wiped cache and dalvik cache (i dont know why i did this). Now, Im on a boot loop and I cant even turn the phone off. I take the battery out and plug it back in and it just loops. Same with taking the battery out and plugging a usb. SO I successfully got to Download mode and got ODIN to recognize the phone. I installed Clockwork
Mod Touch 5.8.1.3 Odin tar. and it says it was succesful, but no luck! Still loops. Is there another .TAR file I can install???
PS: I cant get into Recovery because phone does not turn off.
Please any input is much appreciated, this is driving me nuts.
Wiping battery stats, cache and Dalvik shouldn't cause a bootloop. Wiping Dalvik does cause a very long boot cycle, though, as it causes the system to think it's got all-new apps, and it has to re-process and re-cache them. Are you sure that's not what's going on? How long are you letting it sit for?
Also, are you sure you don't have a stuck power button? I doubt it because you were able to get into download mode and flash a recovery img, but have you tried mashing the button down over and over, even cleaning around the edges of the button with a needle?
mex2309 said:
Hi,
So I got a bootloop after wiping battery status on recovery. But first I wiped cache and dalvik cache (i dont know why i did this). Now, Im on a boot loop and I cant even turn the phone off. I take the battery out and plug it back in and it just loops. Same with taking the battery out and plugging a usb. SO I successfully got to Download mode and got ODIN to recognize the phone. I installed Clockwork
Mod Touch 5.8.1.3 Odin tar. and it says it was succesful, but no luck! Still loops. Is there another .TAR file I can install???
PS: I cant get into Recovery because phone does not turn off.
Please any input is much appreciated, this is driving me nuts.
Click to expand...
Click to collapse
U should definitely go back to stock via odin first before even trying to install cwm and flashing a custom rom.
Sent from my SGH-I727 using xda app-developers app
T.J. Bender said:
Wiping battery stats, cache and Dalvik shouldn't cause a bootloop. Wiping Dalvik does cause a very long boot cycle, though, as it causes the system to think it's got all-new apps, and it has to re-process and re-cache them. Are you sure that's not what's going on? How long are you letting it sit for?
Also, are you sure you don't have a stuck power button? I doubt it because you were able to get into download mode and flash a recovery img, but have you tried mashing the button down over and over, even cleaning around the edges of the button with a needle?
Click to expand...
Click to collapse
I left it on the loop for about 2:30 hours. Still nothing- I cleaned around the power button by taking the case off. Everything looked fine but it still loops. Once I was able to get to Recovery mode but I could only scroll down one line before the phone flashes and goes back to the first command line. This leads me to believe that theres something wrong with the power button, its stuck or a short. Also, I still can't turn if off, as soon as I put the battery in- it turns on w/o me pressing the power button.
I think its a gonner...
I left it on the loop for about 2:30 hours. Still nothing- I cleaned around the power button by taking the case off. Everything looked fine but it still loops. Once I was able to get to Recovery mode but I could only scroll down one line before the phone flashes and goes back to the first command line. This leads me to believe that theres something wrong with the power button, its stuck or a short. Also, I still can't turn if off, as soon as I put the battery in- it turns on w/o me pressing the power button.
mex2309 said:
I think its a gonner...
Click to expand...
Click to collapse
It's alive! Finally i got it to boot up. I don't know how or why. I tried to go to Recover mode and this time I got in and was able to cycle through the menu. I reinstalled the latest ROM I used and it booted up. Strange.... but I'm happy.
mex2309 said:
I left it on the loop for about 2:30 hours. Still nothing- I cleaned around the power button by taking the case off. Everything looked fine but it still loops. Once I was able to get to Recovery mode but I could only scroll down one line before the phone flashes and goes back to the first command line. This leads me to believe that theres something wrong with the power button, its stuck or a short. Also, I still can't turn if off, as soon as I put the battery in- it turns on w/o me pressing the power button.
It's alive! Finally i got it to boot up. I don't know how or why. I tried to go to Recover mode and this time I got in and was able to cycle through the menu. I reinstalled the latest ROM I used and it booted up. Strange.... but I'm happy.
Click to expand...
Click to collapse
Glad you got back into your phone. I am starting to see this happening a lot lately with ROMS. Which particular one were / are you on when it started the boot loop?
MasterDecker said:
Glad you got back into your phone. I am starting to see this happening a lot lately with ROMS. Which particular one were / are you on when it started the boot loop?
Click to expand...
Click to collapse
Sounds similar to what I just went through... Except I didnt do anything in recovery before mine started looping. Curious to know what rom you were running as well.
MasterDecker said:
Glad you got back into your phone. I am starting to see this happening a lot lately with ROMS. Which particular one were / are you on when it started the boot loop?
Click to expand...
Click to collapse
I was on the Seanscreamz' ICS ROM. I never had a problem with his ROMs before and I've been using them for about a year. They are pretty solid and I recommend them. It had to do something with me wiping caches and wiping battery stats because it happened shortly after. But I'm just guessing.
mex2309 said:
I was on the Seanscreamz' ICS ROM. I never had a problem with his ROMs before and I've been using them for about a year. They are pretty solid and I recommend them. It had to do something with me wiping caches and wiping battery stats because it happened shortly after. But I'm just guessing.
Click to expand...
Click to collapse
I'm trying to wrap my head around that, and not coming up with anything valid. Wiping the caches would cause a much longer boot time, battery stats, at most should only cause you to need to remove and reinsert the battery.
Just about the only thing I could come up with would be that when you wiped the caches, was that your phone was trying to reload all that data back into the cache and was getting brain dead.
More information is needed from others that have had the same issue, on the same ROM, or different does not matter, but detailed info as to what exactly was done prior to the boot loop issues.
If my phone gets stuck in a boot loop, usually after I flash someting in Odin or whatever, if I hit factory reset it fixes itself.
It doesn't bother me since all my stuff is backed up though.
You should Odin back to stock then flash cwm
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
just got a phone off of craigslist.. saw that it booted up, so i figured i might be able to fix it. cost me $100.
just finished ODINing it, but it just continues to bootlop. not sure what to do next.
Flash a recovery in Odin and see if you can enter recovery. Wipe data/factory reset if you get there.
hechoen said:
Flash a recovery in Odin and see if you can enter recovery. Wipe data/factory reset if you get there.
Click to expand...
Click to collapse
already did that.. flashed CWM, ran recovery and installed rom. no go. now i see the cyanogen boot screen, but it won't get past that. this is kind of strange.
i think the issue with this phone is hardware related. constantly the phone turns itself off. i eventually was able to get stock rom to work (not sure how), but it goes haywire. wifi works, but for whatever reason, i can't download from the play store.
also, when im in CWM.. it reboots randomly. sometimse pressing the power button hits twice too. my old i777 has gone haywire too.. i might have to rethink what i will be choosing for my next phone.
mistabeo said:
i think the issue with this phone is hardware related. constantly the phone turns itself off. i eventually was able to get stock rom to work (not sure how), but it goes haywire. wifi works, but for whatever reason, i can't download from the play store.
also, when im in CWM.. it reboots randomly. sometimse pressing the power button hits twice too. my old i777 has gone haywire too.. i might have to rethink what i will be choosing for my next phone.
Click to expand...
Click to collapse
I did what I could to try to replicate your situation. Which version of CWM are you installing? I went through several different versions up to the latest and found that the phone was having an issue with CWM itself. (possibly corrupted driver, but not 100% sure on that, as the phone does get recognized by the computers.)
But when I got to the latest CWM, and it started doing similar to yours, what I did was the following.
#1 : reinstall drivers
#2 : plugged the phone into the USB 2.0 slot on my laptop.
#3 : removed the battery, sim card, SD card
#4 : tried to power on the phone holding the power button for approximately 20 seconds. (nothing)
#5 : put in the battery while still plugged in, and powered on.
#6 : After phone booted up, and computer recognized the phone, I removed the battery. Phone stayed on.
#7 : waited while the computer re installed the ADB drivers, after driver install success, I unplugged the phone. Of course it powered down.
#8 : Restarted the laptop, put the battery back in the phone, and held vol + and - and power. Phone rebooted into recovery, but got into a boot loop when trying to recover.
#9 : downloaded TWRP recovery and put it on the SD card for the phone. Restarted the phone into recovery and installed TWRP recovery.
#10 : Rebooted phone into TWRP recovery. wiped all cache, installed latest STOCK ROOTED ROM.
The phone has been stable and working just fine, no wifi or blue tooth issues, calls are as normal, texting is as normal. LTE speeds as normal.
I have since switched all my devices over to TWRP recovery and have had ZERO issues.

[Q] Now I am at a point I want to keep, but...

Hi and Thanks to all the help that I have found here since my problem started a week ago. I am a Noob. I
PHP:
am becoming an informed Noob.
I am copying my response post from http://forum.xda-developers.com/showthread.php?p=37915235#post37915235 her as it outlines my trail;
Begin cut n paste:
Quote:
Originally Posted by MrKickstand View Post
Are you rooted?
Sent from my SGH-I997 using xda app-developers app
Same response:;
[B]Infuse 4G Firmware 2.3.6 ;Baseband 1977UCLB3;Kernal 2.6.35.7-1997UCLB3-CL997492; Build Gingerbread.UCLB3[/B]
[I]Superuser present and active. ADB Root response same= "adbd cannot run as root in production builds"
[I]When I power off and and press the power button, all I get is the progress wheel and an empty battery logo, over and over. Remove battery, count to 10, reinsert battery, after a couple of seconds the progress wheel then nothing.Press and hold power button same as previous. I can not enter recovery, I can enter download and that's the only way I can boot currently is by re-flashing with ODIN the 1997UCLB3.tar.md5. I can reboot with adb reboot. (Nothing happens when I use the 3 button to get into recovery since before the first Odin Flash.)
History: First occurrence Thursday 2/21/13 with no charging when plugged into the charger (3 tried) Read most of the posts here regarding no charge and boot loop (never got to SAMSUNG logo). Downloaded ODIN and the above ROM and re-flashed when my phone booted, I had everything and was rooted. I was happy until I turned it off and tried to turn back on. same progress wheel and empty battery, I re-flashed and did a hard reset, re-flashed and now my data was gone, reinstalled some things, turned the phone off, same no start. Used heimdall back to stock and when running, as expected, but when off, no start.
Yesterday I downloaded SDK and could ADB reboot. Then I dismantled my phone and cleaned what little just had gotten inside, inspected the power button with magnification and noted nothing wrong reassembled inserted battery and pressed power, same results. Re-flashed to get up and tested all functions which seem to working. I have dropped the phone intentionally several time to no avail.
I can turn the screen off with the power button and wake it up. I can lock the camera with the power button and wand unlock it. I don't know if there is an additional circuit connected to the power button for start and I really need to re-solder ( a little scary for me) with a sharp tip and steady hand. I am considering purchasing a cracked screen phone on eBay and swapping mother boards.
At present, I just don't turn the phone off and use Airplane mode at night. I appreciate the work that I see on this forum and will be grateful for any solutions.[/I]
End cut n paste:
Since that date: I have factory reset a few times due to rebooting via download mode and flashing via Odin because upon reflash I lose my mobile connectivity (No wireless service, IMEI as if the Sim was not in) Reset fixed that but of course I had to reinstall all my Apps, google acct. etc (My restore will not come up to clear cache and reboot. I do not have a Recovery mode nor a back up and numerous attempts to get CWM have failed.
I do not intend to turn this phone off until I get a replacement which should be in my hands Tuesday. I am asking for a clean GB rom for Odin that will let me reboot without changing anything. I have jscott30's unbrick Roms that have gotten me where I am and don't want to reflash back to stock anymore, Thanks a 1 to the 1oth power jscott 30 and to qkster for his guides. Without the recovery, I am at a loss of what to do. So I will be cool with a point to a clean UCLB3 Rom to reflash should my phone freeze before Tuesday
Thanks and Make a woman Happy today for Valentines
After you go back to stock and flash a working cwm kernel make sure you release power on logo keep holding vol buttons for at least a min,sometimes it takes a few.I'm sure you did but some people don't.
Sent from my SGH-I997 using Tapatalk 2
I never get to the Logo
Thanks, but I never get to the LOGO.
I tried to flash a CWM kernal and it failed with an error on reboot about something not being formatted, At each "return to stock" Odin, I select the format button and since I can't get to recovery on my own, use the Settings, Privacy, Factory reset with Fromat USB, I have the 1997UCLB3-roo.tar.md5 that I will use if my phone turns off or goes dead to reflash back to life.
TJj33p3rz said:
After you go back to stock and flash a working cwm kernel make sure you release power on logo keep holding vol buttons for at least a min,sometimes it takes a few.I'm sure you did but some people don't.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Oldbutnew said:
Thanks, but I never get to the LOGO.
I tried to flash a CWM kernal and it failed with an error on reboot about something not being formatted, At each "return to stock" Odin, I select the format button and since I can't get to recovery on my own, use the Settings, Privacy, Factory reset with Fromat USB, I have the 1997UCLB3-roo.tar.md5 that I will use if my phone turns off or goes dead to reflash back to life.
Click to expand...
Click to collapse
if you can use odin,
flash jesse's option c.
this will give you the base rom with lidroid boot into recovery option
download this: http://forum.xda-developers.com/showthread.php?t=1702026
flash it in cwm. use the back up the whole rom option.
this will back up just about your whole setup at any one point and make restoring easier.
you had mention about not being able to get into recovery...
what i was wondering is: while running the rom, if you use the pull down status bar menu, go to the far right, there are some reboot options..one of which is recovery..what happens if you choose that option?
Thanks qkster!
I think I tried Option C a couple of days ago and something didn't go right. I figured it was because I couldn't wipe the cache in recovery. I had aslso attempted your kernal flash using the program you recommended. On reboot I got the something not formatted right. I had used my laptop and USB to copy the kernal file to a folder I made in the Infuse. But to be clear. Since I can't clear the caches in recovery, just flas option c, selecting PDA? (No PIT or phone?)
I do want to get the C.
As for the infuse Toolkit, you mean after I get CWM vis Jesse's option C?
You ask about the pull down status bar "when running ROM" is that in ODIN it self? I am not sure where you mean,
Thanks for your patience,
qkster said:
if you can use odin,
flash jesse's option c.
this will give you the base rom with lidroid boot into recovery option
download this: http://forum.xda-developers.com/showthread.php?t=1702026
flash it in cwm. use the back up the whole rom option.
this will back up just about your whole setup at any one point and make restoring easier.
you had mention about not being able to get into recovery...
what i was wondering is: while running the rom, if you use the pull down status bar menu, go to the far right, there are some reboot options..one of which is recovery..what happens if you choose that option?
Click to expand...
Click to collapse
Oldbutnew said:
Thanks qkster!
I think I tried Option C a couple of days ago and something didn't go right. I figured it was because I couldn't wipe the cache in recovery. I had aslso attempted your kernal flash using the program you recommended. On reboot I got the something not formatted right. I had used my laptop and USB to copy the kernal file to a folder I made in the Infuse. But to be clear. Since I can't clear the caches in recovery, just flas option c, selecting PDA? (No PIT or phone?)
I do want to get the C.
As for the infuse Toolkit, you mean after I get CWM vis Jesse's option C?
You ask about the pull down status bar "when running ROM" is that in ODIN it self? I am not sure where you mean,
Thanks for your patience,
Click to expand...
Click to collapse
I'm wondering if you may have several things confuse..or at least the terminology anyway.
In order to flash Jesse's option C, you have to be in DOWNLOAD mode (DL or dl) and flashed with Odin on your PC.
When you have the phone running, if you touch the top of the screen and pull it down, you have the status bar menu. You can sweep the icons to the right for additional options.
if you are looking to wipe cache for what ever reason, here is one option without using recovery menu:
https://play.google.com/store/apps/...251bGwsMSwxLDEsIm1vYmkuaW5mb2xpZmUuY2FjaGUiXQ..
if you are looking for an easy way to get into recovery, here is another app:
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en
It's making progress
qkster said:
I'm wondering if you may have several things confuse..or at least the terminology anyway.
In order to flash Jesse's option C, you have to be in DOWNLOAD mode (DL or dl) and flashed with Odin on your PC.
When you have the phone running, if you touch the top of the screen and pull it down, you have the status bar menu. You can sweep the icons to the right for additional options.
if you are looking to wipe cache for what ever reason, here is one option without using recovery menu:
[I can't post links yet}
feature=search_result#?t=W251bGwsMSwxLDEsIm1vYmkuaW5mb2xpZmUuY2FjaGUiXQ[/url]..
if you are looking for an easy way to get into recovery, here is another app:
{del} /play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en[/url]
Click to expand...
Click to collapse
It's most likely my attempt to communicate with unfamiliar terms:
I can and always have been able to get into Download Mode, and flashed Jesse's C via Odin that way. Originally back at the beginning, It was Odin and Jesse's B that got my phone up. but it didn't solve the problem of not being able to turn the phone on with the power button. It was Wednesday evening that I attempted to load the kernel you had to add CWM, that's when it failed and then the Jesse C failed on Odin and I had no wireless connection or IMEI etc. Back to your unbrick then the factory reset with phone running and using the Privacy menu.
Until I downloaded the Quick Boot at your recommendation, I have not been able to enter Recovery from a phone in the off status. (Recovey ran at the end of each Odin flash). Thanks also for the Cache Cleaner.
Now when I pull down my top bar, nothing scrolls left to right or right to left and I don't ever recall seeing that happen in the last 1.5 years.MIne just shows L-R Wifi; Blue T; GPS; Flight Mode; Screen rotation.
Now I am good as long as the phone doesn't freeze and I have to remove the battery. I have in those cases I have re flashed Jesse's B to bring the phone up. Only the last time I ended up with no wireless (No Sim recognized and it was installed), and I went back to stock to regain it. So I am a bit paranoid about re-flashing anything new now. But knowing me I will before the weekend is done. The Reboot app is what I have been trying to figure out how to do. When I get the new phone and get it up and running and stable, I'll attempt to re melt the on button solder and possible the USB connector solder too. USB connection now dies if the screen time out turns the screen off. (If i keep the screen alive by doodling on it no problem transferring files.)
Thanks for your help I am a bit compulsive so all of this is my current obsession.:laugh::laugh:
Oldbutnew said:
Now when I pull down my top bar, nothing scrolls left to right or right to left and I don't ever recall seeing that happen in the last 1.5 years.MIne just shows L-R Wifi; Blue T; GPS; Flight Mode; Screen rotation.
Thanks for your help I am a bit compulsive so all of this is my current obsession.:laugh::laugh:
Click to expand...
Click to collapse
you're right about the status bar..looking over jesse's description, you would have to flash the lidroid as an extra
http://forum.xda-developers.com/showthread.php?t=1698972
there is something odd about your phone though...possible hardware issues...you should not have to keep screen on to complete a background task.
under Display..there should be an option to keep the screen on longer than default if you it
gl
I do believe it's hardware too.
qkster said:
you're right about the status bar..looking over jesse's description, you would have to flash the lidroid as an extra
http://forum.xda-developers.com/showthread.php?t=1698972
there is something odd about your phone though...possible hardware issues...you should not have to keep screen on to complete a background task.
under Display..there should be an option to keep the screen on longer than default if you it
gl
Click to expand...
Click to collapse
I set it on 2 minutes and touch the screen often. Funny it doesn't have an issue in DL mode, Sometimes I wiil have SUB Connected and no charging and It'll connect in the back ground, lose connection repeatedly and all of a sudden show the charging Icon, which I haven't see since all this began 9 days ago.
This phone has had some big drops. last one about 4 days before this began, vibrated off my table saw onto the concrete floor,
Thanks.
New phone works as advertised
Oldbutnew said:
I set it on 2 minutes and touch the screen often. Funny it doesn't have an issue in DL mode, Sometimes I wiil have SUB Connected and no charging and It'll connect in the back ground, lose connection repeatedly and all of a sudden show the charging Icon, which I haven't see since all this began 9 days ago.
This phone has had some big drops. last one about 4 days before this began, vibrated off my table saw onto the concrete floor,
Thanks.
Click to expand...
Click to collapse
Ok eBay phone arrived this afternoon. Factory reset, Odined, Jesse's C option. Yeah, CWM recover. I loaded most of my programs and backed up my ROm. I will experiment on my old one now.
New thing happening. I still can't start the phone from Off. BUT if I plug in the charger and hold down the on button and the down volume button after a few cycles of the dead battery icon, I get a charging icon and the phone is charging. Now with that icon working I can hold the power button down and the phone starts. Charger or USB need to be plugged in for that to work.
Update on the Start button.
Oldbutnew said:
Ok eBay phone arrived this afternoon. Factory reset, Odined, Jesse's C option. Yeah, CWM recover. I loaded most of my programs and backed up my ROm. I will experiment on my old one now.
New thing happening. I still can't start the phone from Off. BUT if I plug in the charger and hold down the on button and the down volume button after a few cycles of the dead battery icon, I get a charging icon and the phone is charging. Now with that icon working I can hold the power button down and the phone starts. Charger or USB need to be plugged in for that to work.
Click to expand...
Click to collapse
Thursday Update:
Recap of current state:
Factory Reset from phone/security/fatory reset.
Flashed Jesse's C option with odin https://www.facebook.com/jennifer.waddell.963/photos_stream?ref=ts and let it boot all the way. Next I down loaded Quickboot (see qksters link above) and restarted in Recovery. Voila Red CWM. Cleared cache; factory reset; Advanced cleared davlik cache. Rebooted and let it fully load. Turned off to enter download.mode and Odined a second time Option C.Everything looked good on all accounts, reentered Google data etc. like a factory reset requires. Re installed Quickboot and booted to CWM and backed up my ROM.
I turned the phone off and the start button wouldn't work still, but I held it a long time with the down volume button (not sure this is necessary, just what I did) and all of a sudden instead of the dead battery logo, I got a charging battery logo and it was 87% charged. First time I had seen this in while. I pressed and held the power button and the Samsung Logo came up and the phone booted. (Slow boot compared to the new Infuse I now have.) So now my old phone was working, but not up to 100%.
I charged the battery to 100% and turned it off and left it off for the day/night. Yesterday I got it to turn on with all the buttons pressed and it booted, said connect battery charger/low battery 1%, h'mmm. I charged again to 100% and turned it off all day and night. Same issue this morning. Something is draining the battery when fully off. SO I still have a hardware issue I believe, just not sure what it is.
Thanks for any insight, I'll keep experimenting.
Oldbutnew said:
Thursday Update:
Recap of current state:
Factory Reset from phone/security/fatory reset.
Flashed Jesse's C option with odin https://www.facebook.com/jennifer.waddell.963/photos_stream?ref=ts and let it boot all the way. Next I down loaded Quickboot (see qksters link above) and restarted in Recovery. Voila Red CWM. Cleared cache; factory reset; Advanced cleared davlik cache. Rebooted and let it fully load. Turned off to enter download.mode and Odined a second time Option C.Everything looked good on all accounts, reentered Google data etc. like a factory reset requires. Re installed Quickboot and booted to CWM and backed up my ROM.
I turned the phone off and the start button wouldn't work still, but I held it a long time with the down volume button (not sure this is necessary, just what I did) and all of a sudden instead of the dead battery logo, I got a charging battery logo and it was 87% charged. First time I had seen this in while. I pressed and held the power button and the Samsung Logo came up and the phone booted. (Slow boot compared to the new Infuse I now have.) So now my old phone was working, but not up to 100%.
I charged the battery to 100% and turned it off and left it off for the day/night. Yesterday I got it to turn on with all the buttons pressed and it booted, said connect battery charger/low battery 1%, h'mmm. I charged again to 100% and turned it off all day and night. Same issue this morning. Something is draining the battery when fully off. SO I still have a hardware issue I believe, just not sure what it is.
Thanks for any insight, I'll keep experimenting.
Click to expand...
Click to collapse
it could be your battery that is bad.
try a new one if you have not tried several others:
http://www.ebay.com/itm/New-Premium...902705?pt=PDA_Accessories&hash=item27ca3fca31
qkster said:
it could be your battery that is bad.
try a new one if you have not tried several others:
http://www.ebay.com/itm/New-Premium...902705?pt=PDA_Accessories&hash=item27ca3fca31
Click to expand...
Click to collapse
I have tried several other batteries now with the same results.
Yesterday, I decided it would be a good idea to use this phone as a practice platform for a Jelly Bean upgrade.with scott.hart.bti's http://forum.xda-developers.com/showthread.php?t=1776129
Everything went as advertised and I was pretty happy for a while. I was following the instructions quite literally and after flashing the CM9, I removed the external SD card and that messed up getting back into recovery, but I got there. From reading, I understand that I need the IC flash to preserve the EFS file, but not absolutely sure that I can't remove the SD card before starting the process altogether. CM9, then CM10.
Since all my programs needed to be re-downloaded and installed, I had the "Bright idea" to restore the backup in CWM that I did just before the upgrade. Bad idea, now I had a phone that would not boot.
Is there a way to upgrade to JB and not have to re-install all my programs? I will try the Nandroid backup in CWM
To get back working again, I could get into download mode, but not recovery, so I did J scotts back to stock, then the option C to get CWM and used quick boot to get into recovery and reflashed with an experiment of using your Quick wipe in stead of factory reset on this go. Again when I took the SD out at the finish of the CM9 I had a little trouble getting into the recovery to continue. When it did get to recovery, I finished flashing per the instructions, but when it booted I only had a partial group of programs, Google play was the most notable omission. I took a deep breath and did a factory reset, and managed to get into recovery and started with a flash of CM10 again and this time all ok.
I did a couple of boots with quick boot and powered down for the night with it plugged into the charger. This morning I can not get anything up. Battery charging icon shows and goes away (CM10 battery logo) I can get into download, but not recovery and don't really want to Odin back to stock and go from there, but may do that and leave it in GB while I update the new phone.
My conclusion is that it's hardware and possibly USB connector. IN GB the USB cable wouldn't connect so I used Software data cable. In JB it worked. Still confusing, but I'll keep at it.
Thanks for your patience and my learning curve!

Stuck at Boot Logo After Flashing Firmware via ODIN

Nevermind fixed it. I am a dumbass lol I booted into stock recovery and factory reset, and now I am good to go.
Silicon Knight said:
Nevermind fixed it. I am a dumbass lol I booted into stock recovery and factory reset, and now I am good to go.
Click to expand...
Click to collapse
this happens buddy you just have to boot into recovery and do a factory reset and wipe cache and there will be no problem
HAPPY NEW YEAR
So I had the same issue it sounds like, tried to flash PhilZ recovery over Odin seemed fine I put the PhilZ file and superSU files on the device to continue through and now I am unable to get into recovery mode only download and my tab does not turn off, it sits on the Samsung Galaxy Tab 2 10.1 logo unless I hold the power then it turns off and then right back on again.
Any ideas? I cant seem to find anything
Does your device boot up completely or just sit at the Samsung bootscreen?
swrght13 said:
Does your device boot up completely or just sit at the Samsung bootscreen?
Click to expand...
Click to collapse
Just the boot screen, not even past the first logo
You must have missed a step. Try the process again using this video tutorial: http://www.youtube.com/watch?v=sO3y7JCqfc8
Follow the directions step by step.
This is actually the video I was using, but, I have tried again and I cant get it to boot into PhilZ. I am able to get to download screen so I have tried a different version as well, but after it gets the pass it disconnects to reboot and then never boots or reconnects until I put it into download and reconnect the device.
Weird. This is the way I installed Phil's touch. I had no issue with it. Make sure your usb is disconnected from your device before rebooting. On the p5113, to get into recovery, hold down power + volume-down, when you see first Samsung big-screen, release power button and continue to hold the volume-down button.
Sent from my GT-P5113 using XDA Premium 4 mobile app
That's what I've been doing and it does nothing. Device sits at that Samsung Galaxy Tab 2 10.1 screen. The only way I can turn it off is to plug it into my computer and restart it until the battery symbol comes up and disconnect. That's it.
Not sure what route to take now, but, it still connects to odin and after flashing the PDA to it, it disconnects.
Ok. Tell me. Are you rooted? Can you boot up to your home screen at all? You must be rooted in order to flash a custom recovery.
Sent from my P5113 using XDA Premium 4 app
Rooted, running CM 10.2 [4.3.1]
I didn't even get to that step, I was flashing philz recovery in order to backup before rooting. I was unable to boot anything except the download mode, no recovery mode to factory reset and not able to boot the actual system at all.
I ended up trying CWM and flashing that to the device through Odin and was able to open recovery mode after that and have since flashed Cyanogen to the device and have everything good to go.
I dont know what was wrong with philz, but, I tried multiple downloads of the version we need and none did anything.
Problem is solved, but, there's got to be something wrong with philz recovery for this device or my tablet just doesn't like philz.
Thanks for your suggestions though I appreciate your efforts!
No problem. I'm glad you found a way to fix it!

Categories

Resources