Xperia Ion bricked. Any fix? - Sony Xperia S, Acro S, Ion

My ion did a ramdisk check, after it finished, it shows the internal memory (all 2gb) was filled, even though i only had a few programs installed. It kept restarting itself with a notification saying low memory. I did the power + volume up to restart it a few times and it keep powering off before I can reach the reset buttons. Now the power + volume up method is not working and the charge indicator light wont come on when being charged. Is my phone bricked? Any fix? Thanks.
Edit: I also tried the SEUS repair fix and tried to flash it with flashtool with no luck. No response from computer or the phone when i plugged in the usb with the volume down button. The phone wont go into flash mode.

Try to charge for couple hours first, maybe it just run out of battery

athris said:
Try to charge for couple hours first, maybe it just run out of battery
Click to expand...
Click to collapse
Thanks for the reply.
Do you know if the phone is being charged when the charge indicator light will not turn on?

maybe try to charge without looking the indicator light for about 15 mins, then pull cable and charge it again, see if the light goes on. It might be your phone battery was completely drained.

What were you doing before all this happened?
Sent from my LT28at using Tapatalk 2

Spectre51 said:
What were you doing before all this happened?
Sent from my LT28at using Tapatalk 2
Click to expand...
Click to collapse
I was just installing programs from the play store. The apps i was installing were all installed on my galaxy nexus before, so i don't think those caused it.
After a few hours of charging, the red LED lit up, but still wont turn on, hard reset, or go in flash mode. The red led lights up when the charger is plugged in and turns off when removed. Any ideas? Thanks.

wei94519 said:
I was just installing programs from the play store. The apps i was installing were all installed on my galaxy nexus before, so i don't think those caused it.
After a few hours of charging, the red LED lit up, but still wont turn on, hard reset, or go in flash mode. The red led lights up when the charger is plugged in and turns off when removed. Any ideas? Thanks.
Click to expand...
Click to collapse
Had that happen with my XS when I rooted and installed CWM that had battery charging issues (cwm not the phone) had to let it sit for a while charging before it finally showed the charging screen and would boot loop at the bootanimation. Did you do any mods to your ion?
Sent from my LT28at using Tapatalk 2

Spectre51 said:
Had that happen with my XS when I rooted and installed CWM that had battery charging issues (cwm not the phone) had to let it sit for a while charging before it finally showed the charging screen and would boot loop at the bootanimation. Did you do any mods to your ion?
Sent from my LT28at using Tapatalk 2
Click to expand...
Click to collapse
No mods, but last night I did received an OTA update on the phone, it's like 8.6mb size. Not sure what it did because my phone's firmware stayed the same (2.3.7) after the update. Thanks.

Lt28i or at?
Sent from my LT28at using Tapatalk 2

it's the AT&T version.
Manage to turn it back on after a couple hours of charging, shows low battery. Thank you everyone :laugh:
Now the original problem is back , the phone shows low memory even though i have less than 10 apps installed. It keeps restarting to ramdisk dump and then error. It wont even give me enough time to select factory reset before it crashes. When I flash it with flashtool, it gets stuck on flashing loader.

wei94519 said:
it's the AT&T version.
Manage to turn it back on after a couple hours of charging, shows low battery. Thank you everyone :laugh:
Now the original problem is back , the phone shows low memory even though i have less than 10 apps installed. It keeps restarting to ramdisk dump and then error. It wont even give me enough time to select factory reset before it crashes. When I flash it with flashtool, it gets stuck on flashing loader.
Click to expand...
Click to collapse
Have you tried using the Sony Update Service program:http://www.sonymobile.com/gb/tools/update-service/ ?
When you were trying to flash it with flashtool did you select it to wipe everything?

Spectre51 said:
Have you tried using the Sony Update Service program:http://www.sonymobile.com/gb/tools/update-service/ ?
When you were trying to flash it with flashtool did you select it to wipe everything?
Click to expand...
Click to collapse
Yes I tried the sony software, it said no updates are available.
I had all the wipes selected on flashtool.
It also just went back to brick mode after a ramdump. sigh this phone is driving me crazy. Guess i'' have to charge it like 5 to 6 hours to wake it back up again to fix the memory problem.

It happened to my XS before about stuck on flash loader. I just put the phone on charge around 7-8 hrs (just to make sure it has enough battery to make a full clean flash), then flashing loader problem disappear.

wei94519 said:
Yes I tried the sony software, it said no updates are available.
I had all the wipes selected on flashtool.
It also just went back to brick mode after a ramdump. sigh this phone is driving me crazy. Guess i'' have to charge it like 5 to 6 hours to wake it back up again to fix the memory problem.
Click to expand...
Click to collapse
Yeh it should say no updates are available but if you continue from there it does a repair flash of the software to restore the phone to factory condition.

Related

Did I just BRICK my G Nexus?

So, last night I was out and about - just having a good time. Noticed that the battery on my GSM Galaxy Nexus was getting low. Went "Meh, wasn't the first time it's died." It got to 1% battery power and shut-off, like it normally does. Me being who I am, I turned it back on to see just how much more juice I could get out of it.
Phone booted up alright. Finished the boot animation, and then a couple seconds later turned off.. not a big deal. I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
I'm not talking about the regular charge screen. After the battery gets 'filled' twice, it completely restarts. Black screen for 2 or so seconds, and then it goes through the charge animations as it would if you had just pluggied it in. I CAN get into bootloader, but that's about it. I'm just curious.. has anyone seen this before? Or know what my problem might be?
I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Try going into recovery and wiping cache and dalvik. If that doesn't work reflash your rom
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
i.vt3c.d0hc said:
[snip]
I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
Click to expand...
Click to collapse
Turn it off. Leave it charging for a few hours before turning it on.
i.vt3c.d0hc said:
[snip] I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Click to expand...
Click to collapse
You do not need to have USB debugging enabled to use fastboot.
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
It doesn't take long at all to install the drivers. Look for a thread with "universal" in the title. I think it is in GN General. Once you do install the fastboot driver, download the fastboot.exe file and reflash the stock ROM.
Diger36 said:
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
Click to expand...
Click to collapse
It's volume up and the power button.
Sent from my Galaxy Nexus using Tapatalk
The problem I have is that the charge animation doesn't change... i.e. It'll constantly refill the battery and all, but it always starts from the bottom (While when a phone is say... half charged, the little battery is half filled and the animation continues.
I'm not sure it's even charging at all.
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
i.vt3c.d0hc said:
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
Click to expand...
Click to collapse
Power down phone, do a long battery pull, place it inside again, let it charge for a few hours without powering it on, when it is fully charged (or after a few hours) pull battery again and then take charger out the phone. After a few minutes, place battery inside phone again and start it up without the charger.
Hope that works.
Sent from my Galaxy Nexus using xda premium
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
i.vt3c.d0hc said:
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
Click to expand...
Click to collapse
You could always try a new battery
Sent from my Galaxy Nexus using xda premium
+1 for the new battery thought.
Battery test
I am having a similar problem, I get the boot loop.
Difference is that I had started with a new battery so that could be your problem or unrelated. I went to a mobile shop yesterday and they let me use a new battery to see if the loop would start. It did not so there seems to be at least one other failure path. I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
I posted to this thread #192
http://forum.xda-developers.com/showthread.php?t=1490815
My Galaxy Nexus phone from WIND went into a reboot loop yesterday. It had been charged to 98%, used to make a call and then put away. Wireless was enabled. Noticed vibration periodically and say it was rebooting every 6 - 7 seconds. Pulled battery to stop reboot. Saw references to fully charged battery via USB stops reboot loop so tried that. Battery voltage was 4.17V and still went into reboot loop.
Tried to boot into safe mode but still goes into a loop
I went into recovery mode and tried all options but factory reset because I am hoping to recover some pictures
reboot system now
apply update from cache (but did not have an update to install as only options were ../ lost+found/ recovery and when I selected these was in a loop as well)
wipe cache partition
Can't tell what version of Andorid I have as the phone never finishes booting.
Boot console gives the following information
Product Name – tuna
Variant – maguro
HW version – 9
Bootloader version – PRIMEKK14
Baseband version – I9250UGKL1
Have installed SMS backup because I was planning to do a backup after a trip. Also have two GPS tracker apps installed.
GNMO15 said:
[snip]
I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
Click to expand...
Click to collapse
If you can boot into recovery, you may be able to get your pictures off your device.
1) Make sure you have the drivers for your device properly installed on your computer.
2) Download the attachment and unzip it to a directory on your computer.
3) Open a command prompt in the same directory.
4) Reboot your device into recovery and plug into your computer.
5) Make sure your computer sees your device by typing: adb devices
6) Pull the data off your device by typing: adb pull /data/media
Note: depending on how much data you had on /sdcard, this could take a while, so be patient.

[Q] Galaxy Nexus won't turn on after attempting a flash stock + Unroot???

So I'm not sure what happened with my girlfriend's Gnex, she updated to 4.2 a couple days ago, then her battery died. So she went to charge it and when it finished charging, she went to turn it on normally, but it went into a reboot loop? So i was talking to someone else on another thread that i saw similar, so i tried to do a flash stock + unroot, it connected i got into recovery menu and everything, went to do it, and then the screen started going staticy, and it said it failed then it said it should take 5-10 minutes or something. So i guess it froze or something, so i took the battery out and the screen was still staticy, and then i unplugged it from the USB, and now it won't turn back on. Did i brick the device? :/ Thanks in advance for future answers.
you cant get into to recovery either? or fastboot mode?
k786 said:
you cant get into to recovery either? or fastboot mode?
Click to expand...
Click to collapse
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
AdmiralAqbar said:
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
Click to expand...
Click to collapse
Then I am afraid you're hard bricked pal
Sent from my GNexus
AdmiralAqbar said:
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
Click to expand...
Click to collapse
what about fastboot mode?
Same
AdmiralAqbar said:
So I'm not sure what happened with my girlfriend's Gnex, she updated to 4.2 a couple days ago, then her battery died. So she went to charge it and when it finished charging, she went to turn it on normally, but it went into a reboot loop? So i was talking to someone else on another thread that i saw similar, so i tried to do a flash stock + unroot, it connected i got into recovery menu and everything, went to do it, and then the screen started going staticy, and it said it failed then it said it should take 5-10 minutes or something. So i guess it froze or something, so i took the battery out and the screen was still staticy, and then i unplugged it from the USB, and now it won't turn back on. Did i brick the device? :/ Thanks in advance for future answers.
Click to expand...
Click to collapse
I'm having a similar issue. I wanted to flash the memory so i relocked the phone using the wugkit, then unlocked and rooted. For some reason, it wouldn't load a new rom. I kept getting the triangle exclamation point android graphic. I pulled the battery and that was it. Black screen. Won't turn on. A cpl of times, it was almost recognized by the computer via USB, but just kept failing. This sucks.
cyberelli said:
just a thought: are you sure it's charged up enough to boot? i know i've mistakenly thought my phone was messed up when the battery was just dead
Click to expand...
Click to collapse
Yes the battery is charged. Occassionally, when I plug it into the computer, it makes the new device notification and then fails over and over again. I keep trying to get a glimpse of a lock so i can adb it.

[S/SL/AS/Ion]General bricked device thread

So, I've been seeing A LOT of threads regarding bricked devices (be it soft or hard bricks). So, I decided to create this thread, so everyone with bricked devices post here for help, instead of filling our forums and XDA servers with a load of topics with the same stuff.
If someone knows of a general unbricking thread, please PM me or tag me with a link so I can post on this post.
I will PM a mod to pin this thread to top.
To all brickers,
Before posting, try this thread:{RECOVER SOFT-brick}[2012 XPERIA's]Recover ALL 2012 XPERIAs from SOFT-brick
Remember to give the author thanks
Xperia S Return Back To Stock!
Pre-Requisites
For All The New Users..
If You Did Something Wrong
If nothing is working out
Not Able to Fix
Need to Return Back To Original Firmware?
Here is the Guide For You
Click to expand...
Click to collapse
Return Back To Stock
GUIDE for Better Understanding With Pictures And Images For New Users
Explained Step By Step
Click -- [HERE]​
Just a tip: Try downloading Sony Update Service and following the instructions if you get a green LED blink on your phone, which is way simpler to recover without any problems.
Guys My ION LT28h got bricked during a recovery using CWM.
First It was a soft brick, i did something , random pressing of buttons made it worse. its on HARD BRICKED STATE now. Its been more than 5 weeks.
So after some research i found out that my Kernel is ****ed up. My phone is Boot loader Locked, so i cant flash the Kernel separately.
Now few of our fellow xda members told me to unplug the battery cable from the motherboard.
I have successfully disconnected the battery cable from motherboard, i kept it disconnected for one whole night.
Whats the next step ?
Will i be able to flash it with flash tool after connecting the battery to motherboard back ?
Will i be able flash the busted Kernel to a working stock kernel ?
Accidentally messed up and soft bricked Ion- LT28h.
xperia Ion LT28h
ROM: JB 4.1 Pure CyanogenMod Based on CM 10 FXP 218
kernel: GI Kernel v3 or v5
Recovery: TWRP and CWM
Rooted and Unlocked Bootloader
Hi guys, above mentioned were my previous settings. Had occassional reboots and sometimes it was kinda laggy that's why i decided to flash it to another ROM - supposedly to ParanoidAndroid. After following steps to install PA, my phone was on bootloops, was in a hurry then freaked out, i tried soft and hardreset, and tried booting on recovery both on twrp and cwm to flash properly as what was instructed however i may have flashed the wrong zips interchangeably with other roms and kernels resulting to a total messed up ion. i could have restored immediately to a saved CWM or TWRP backup right away however, i only stopped resetting when my phone suddenly stopped responding, no Sony logo, no Xperia logo, no boot, just backlight on, does not turn off, soft and hard reset no nothing. i guess until the battery went dead, then i charged it the whole night.
after reading most threads on recovering softbricked phone, mainly this {RECOVER SOFT-brick}[2012 XPERIA's]Recover ALL 2012 XPERIAs from SOFT-brick thread, and after a couple of days of red led, i constantly charged, i patiently waited(2days) still no green led, however i found out that i can access fastboot. (blue led).. i managed to get to this fastboot mode(blue led) ONLY after i soft reset or power+vol.up/1 vibrate the phone once the backlight lits up- on&off - for about less than a minute then it goes back to red led. (i'll be calling that stage as backlit-on&off-then-back-to-solid-red-led cycle) but then again if i go to fastboot, it will stay in fastboot mode during flashes and it stays there until the battery runs out and goes back to red led. then i charge my phone again, but
during fastboot mode, i have tried flashing the kernel, system and boot image. all via Fastboot command prompt.
and all were successful. there were combinations like, flashing only the kernel, tried flashing kernel and system, tried boot image only, tried all the same time, tried system only, tried different kernels, system and boot img, BUT STILL my phone wont even give me the sony logo screen.
then i thought i may need to wipe cache and userdata so i also erased cache and userdate a couple of times via fastboot mode command prompt. and yes fastboot does detects my phone. it can reboot to bootloader or just the normal fastboot reboot. so i have no issues regarding phone and pc via using fastboot command prompt. and Same thing - all flashes were successful,
i have flashed i think more or less than a total of 50 times, flashing different combinations. Still it goes back to brick mode.. backlit-on&off-then-back-to-solid-red-led cycle.
i'd like to add that i have also tried flashing via fastboot mode using Flashtool. (thunder icon+selecting 'fastboot mode'). i have flashed the kernel and system, tried kernel only, tried both same time, tried system with boot.img tried flashing kernel with boot.img too, tried different combinations. again, all were successful, but still same result.
it only goes back to backlit-on&off-then-back-to-solid-red-led cycle.
a couple of days after it went to green. flashmode finally! thinking everything will now be alright, i decided to flash it using flashtool via flashmode. I connected phone to pc, after the solid red led and after backlit-on&off-then-back-to-solid-red-led cycle. and the it goes back to red led then the backlit on&off cycle, after observing my phone for hours i then knew that after, i guess about a hundred cycle of backlit on&offs it really does go to green led by itself and if i'm connected to the pc and flashtool it stays on green led or flashmode, however if im connected only on a wallcharger it goes to green led but will only stay there for like 1-2 seconds then goes back to red led and then the backlit on&off cycle.
then i thought just maybe my battery really needs to die as mentioned, since upon plugging my phone on to a wall charger it goes immediately to red led and there's really no response on the phone except only if you gonna wait for the backlit on&off cycle the n press power + vol up then it will respond and go to fastboot mode or power+vol down which goes to flashmode. then i decided to reset the battery by carefully unplugging the ribbon cable and i did. well, initially it did (led was off for a moment then changed to blinking red then solid red) but i have to go to work that time and had to continue only after coming home from work, and that did not resolved it.
i may have flashed my ion a hundred times or so to this date, still no luck. i have finally decided to re-locked my bootloader- and yes it is successfully locked now. - thinking PCC/SEUS/SUS would get it back to life but i'm wrong - it just cant detect my phone. PC companion detects it as Phone/Tablet only then after selecting Ion on the phone list it always says my device is upto date and no available software. (sad)
I also noticed that flashtool does not detect my phone as LT28h. It only says that it is connected to flashmode. Is that an issue too. I have tried diff versions of flashtool from 9.6 to 9.11 all same. i have also installed fastboot and adb as well as flashtool drivers, it sayas all were successfully installed however if im connected via flashtool flashmode, none seems to be detected on device manager, tried reinstalling and manually installing the sony sa0103 adb interface driver however after installing i get an error unable to start device. even if my phone is connected still the device on devicemanager still has an excalamation point. i'm using windows 8. i have flashed successfully before when my phone was in good state, however now that im on brick mode it seems that all flashes i've done did not push thru. also those times that i have flashed my ion via flashtool it says something like:
phone should be connected with usb debugging on and enabled install on unknown sources. i have tried flashing it using win7 pc phone was not detected still, however flashtool stated and detected my device was connected on usb debugging mode, but have has errors during flashing though.
since my bootloader is now locked im unable to flash now via fastboot. before bootloader status says- rooted now bootloader status is- ROOTABLE.
i previously owned xperia neo and have managed to flash it successfully without any issues, also this is the 3rd time i had bricked my ion and managed to fix it before..
i also want to ask regarding flashing back to stock - does that mean any stock firmware can be selected? can be .233 / .68 /.20 or the latest ICS 6.1.E.3.7? coz i have basically tried to all of those mentioned. also is the reason that my flashes were not successful is it because i was currently on 4.1 JB ROM and im flashing 4.0 ICS stock? I also have TWRP and CWM backups on my PC and on internal SD card, is there a way for me to flash or restore those backups via flashtool?
I'm running out of options, i'm desperate and on the verge of giving up.
i dont want to believe that i have totally messed up and hard bricked my phone. I do believe that there is a solution to this, and my phone can be recovered without sending it over to repairshop.. Today is the 3rd week and still struggling to get my phone back to life (even just the sony logo) . any suggestions before i unlock again my bootloader? please help. Any help will be gladly appreciated, and many thanks to everyone for spending time on reading my messed up and soft/hardbrick ion experience.
If you brick your device while flashing kernel and device do not respond any way then follow this little difficult but 100% sure method.
- Dissemble your phone.
- Disconnect battery ribbon from motherboard.
- Reconnect battery ribbon.
- Fastly connect USB cable while holding vol +/-
- Flash Kernel or FTF FW.
Just looking for some direction on my Xperia Ion that recently got bricked while attempting to update to JB software.
Currently, it has no response except for plugging into charger giving a solid red light. I am unable to get it into flashmode and have already disassembled and disconnected/reconnected the battery to reset it.
Im gonna guess that the kernel is royally efed up at this point, Im unable to get it into a bootloop either.
What is the next step to solve this issue? Any help is greatly appreciated!
Droiiiiiiiiid said:
Just looking for some direction on my Xperia Ion that recently got bricked while attempting to update to JB software.
Currently, it has no response except for plugging into charger giving a solid red light. I am unable to get it into flashmode and have already disassembled and disconnected/reconnected the battery to reset it.
Im gonna guess that the kernel is royally efed up at this point, Im unable to get it into a bootloop either.
What is the next step to solve this issue? Any help is greatly appreciated!
Click to expand...
Click to collapse
Did you try SUS ? Official update service ?
Droiiiiiiiiid said:
Just looking for some direction on my Xperia Ion that recently got bricked while attempting to update to JB software.
Currently, it has no response except for plugging into charger giving a solid red light. I am unable to get it into flashmode and have already disassembled and disconnected/reconnected the battery to reset it.
Im gonna guess that the kernel is royally efed up at this point, Im unable to get it into a bootloop either.
What is the next step to solve this issue? Any help is greatly appreciated!
Click to expand...
Click to collapse
I think that you should charge it more to be able to go into flashmode. Maybe until the red light will go off or it'll turn into green. Then try to go into flashmode. Good luck
MozzieZ said:
Did you try SUS ? Official update service ?
Click to expand...
Click to collapse
I was going to but that requires my device be in Flashmode.
Droiiiiiiiiid said:
I was going to but that requires my device be in Flashmode.
Click to expand...
Click to collapse
Read this, maybe it will help you.
http://forum.xda-developers.com/showthread.php?t=2344896
This is my first time got hard brick on my phone. I'm flash wrong ROM (it made for S but I flash it on SL) now my phone totally dead. When I put on wall charger it show constant red led and off several minutes later, try disassemble phone and disconnect and connect ribbon doesn't help to get flashmode and fastboot mode. Any help would be very appreciated.
EDIT: After disconnect ribbon battery I got notification on flashtool "device connected with usb debugging off" but led remains on constant red. Should I try rubber band tricks?
ahlulnugraha said:
This is my first time got hard brick on my phone. I'm flash wrong ROM (it made for S but I flash it on SL) now my phone totally dead. When I put on wall charger it show constant red led and off several minutes later, try disassemble phone and disconnect and connect ribbon doesn't help to get flashmode and fastboot mode. Any help would be very appreciated.
EDIT: After disconnect ribbon battery I got notification on flashtool "device connected with usb debugging off" but led remains on constant red. Should I try rubber band tricks?
Click to expand...
Click to collapse
After disconnecting and connecting back the battery cable , you wont get access to flashboot/flashmode instantly. disconnecting the cable will reset the phone.
If you are getting red led means , its charging on low power. You should keep on wall charging for some hours , say 12 + hours.
After that try flashing the kernel alone , first . you will have to hold the flash mode button for sometime. say 5-10 minutes. then if u have enough charge in your phone it will flash the kernel alone. if u are successful in flashing the kernel, then charge again for some hours , 2-4 hours then try to flash the entire ROM.
Read the Thread Recovering Bricked Phones. This will help. I recovered my phone following the method shown in that thread.
Be patient bro, you can recover your phone, just that it will take some time
Captain Droid said:
After disconnecting and connecting back the battery cable , you wont get access to flashboot/flashmode instantly. disconnecting the cable will reset the phone.
If you are getting red led means , its charging on low power. You should keep on wall charging for some hours , say 12 + hours.
After that try flashing the kernel alone , first . you will have to hold the flash mode button for sometime. say 5-10 minutes. then if u have enough charge in your phone it will flash the kernel alone. if u are successful in flashing the kernel, then charge again for some hours , 2-4 hours then try to flash the entire ROM.
Read the Thread Recovering Bricked Phones. This will help. I recovered my phone following the method shown in that thread.
Be patient bro, you can recover your phone, just that it will take some time
Click to expand...
Click to collapse
Thanks for your fast reply, but I'm already put on wall charger 1 day, and the red led got turn off (no led at all). I think I'll try rubber band trick tonight and leave it till morning.
Hey guys I'm having a problem with my Acro S... It's bootloader is unlocked.
It was soft bricked due to a command I ran on Terminal Emulator (dd if=/dev/zero of=/dev/block/mmcblk0). After inputting that command I safely turned off the phone (Long press Power button, Choose Power off). After turning off, phone was completely dead, no response. It was on 80% battery for sure. It happened last week Saturday (July 20). I then charged my phone for 2days+. On the first day (July 21), no red LED appeared, on the 2nd day (July 22), constant red LED appeared, 3rd day (July 23), red LED disappeared. I then prepared my flashtool for flashing the JB firmware .211 KERNEL ONLY. So I plugged in my phone with volume down pressed, I pressed it for 15mins! My finger was f*cked, after 15mins... nothing happened, RED LED just disappeared and I just heard the Windows USB sound. Flash process didn't start, phone didn't give me a GREEN LED. I tried it again and again and miserably same thing happens, can't go to flash mode. Tried the same with volume up button for fastboot mode but still nothing happens, the RED LED just disappears!
Should I just leave my phone charging on the wall socket even if the RED LED disappeared? To get green LED?
SOMEBODY PLEASE HELP ME! I NEED MY PHONE SO BAD! :crying:
i was installing the prerooted/deodexed stock lt28h rom through cwm in the middle of instalation my phone rebooted and came into a sony bootloop i forced it shutdown by pressing power and volume up now its not starting not even charginig what to do please help :crying::crying:
Flash Tool
Be calm and sit back now put your phone to charger for whole night and then next day download flashtool and a firmware for you device and fladh it your device will breath again.......
tejasvi1 said:
i was installing the prerooted/deodexed stock lt28h rom through cwm in the middle of instalation my phone rebooted and came into a sony bootloop i forced it shutdown by pressing power and volume up now its not starting not even charginig what to do please help :crying::crying:
Click to expand...
Click to collapse
we have desame problem my phone is not charging no ligths/led and cant power on after pressing power and up because im stuck in boothllop after afgrading via OTA.
theprint said:
we have desame problem my phone is not charging no ligths/led and cant power on after pressing power and up because im stuck in boothllop after afgrading via OTA.
Click to expand...
Click to collapse
thks for sharing but i have alraedy solved my hard brick problem my phone is back and running normally

[Q] Samsung Note N7100 stuck boot loop when unplug,but when charging loads the KitKat

Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
Ive just encountered the same problem. Were u able to find a solution?
Shahin7631 said:
Ive just encountered the same problem. Were u able to find a solution?
Click to expand...
Click to collapse
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
anish100 said:
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
Click to expand...
Click to collapse
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
GStriker said:
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
Click to expand...
Click to collapse
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
GStriker said:
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Click to expand...
Click to collapse
Ive literally tried everything .even repartioned the phone . it works fine in recovery and download mode but as soon as i want too boot to android unplugged it restarts . when plugged it has no problem
Funny thing. I have a factory Sprint Note 2 with the latest kitkat updat and I am experiencing the same problem. Phone has not been rooted or messed with. If anybody come across a solution let me know. I booted the phone and unplugged the power button to verify and it does the same thing. Only stays on when in airplane mode or charging.
One more thing. I tried somewhat to do what was posted above about performance / cpu power. I put the phone in powersave mode and checked limit cpu and is is fully operation. problem gone. If I turn power save mode off I'm back to square one.
To late. Took a picture by mistake and phone jumped into boot loop.
i have GT-N7100 and same problem phone is stuck on boot loop when unpluged
---------- Post added at 04:22 PM ---------- Previous post was at 03:24 PM ----------
i just tought maybe it needs new battery. cause before i unpluged it it showed 67% then bootlooped 2x then i pluged back in and it shows me only 5%. i think its battery cause it cant dishcharge in 1 or 2min
My initial problems were that it would drop signal and show an x with no bars intermittently. then i started having problems anytime the phone demanded use. Picture, internet, video. tried a few things listed above. Still would go into a boot loop when not plugged in. Battery would charge normally and show it percentage like normal. It would reach 100% with no difference in charge time. When battery saver is on it would not have a problem unless I use an app that demands more cpu usage, network connection, battery consumption. Put a new battery and problem is gone. some people say the battery show swelling but my battery looks identical to the new one. no swelling and it is not deformed in any way.
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Shahin7631 said:
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Click to expand...
Click to collapse
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
dcmobiletech said:
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
Click to expand...
Click to collapse
Ive tried already with another battery ....its a very strange situation while everything works fine in download or recovery mode when its unplugged ...i have ordered a third party battery to see if it'll make a difference or not ....i'll keep u updated tomorrow
GStriker said:
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
Click to expand...
Click to collapse
Where is the Preferences section? I am unable to find that on my Note 2 settings.
Experienced the same thing and this is the first time I had this. I was playing a game after I fully charged my battery and suddenly it turns off. So I waited for it to turn on where I noticed that it keeps on turning on and off and stuck on the " Samsung Galaxy Note 2" logo screen. Then I tried several things like clearing the cache and dalvik but it just do the same thing. I re-flashed the 4.4 ROM that I was using but sadly it does the same thing. I then noticed that if I plug in the charger it works normally and does not boot loop. And as soon as I remove the charger it will keep on restarting on and off on that screen. I was thinking that it might be a hardware failure or the battery itself. So I went to recovery mode and unplugged the charger, it stays on. Went to download mode without the charger and it stays on. Freakin' weird. I am about to flash a different ROM and will wipe everything and see what happens...
Fully charged the battery to 100%, unplugged the charger and it started to boot loop again. I allowed it to boot loop once and immediately went to recovery mode and saw that my fully charged battery went down to 3%. Tried different ROMS (Omega, DN3, and Phoenix), I still have this issue. Now can use my Note2 as long as the charger is plugged in...
Change your battery and solve the problem ?
Sent from my GT-N7100 using XDA Free mobile app
I did. Case closed!
red_hanks said:
I did. Case closed!
Click to expand...
Click to collapse
is it working fine after battery change? does it still get stuck in boot loop? mobile networks?
It works perfectly !

T999 Won't boot/start

Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
maelstromm said:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Click to expand...
Click to collapse
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
LarsonJayz said:
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
Click to expand...
Click to collapse
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
DocHoliday77 said:
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
Click to expand...
Click to collapse
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
This is pretty strange. Woke up to my phone with the Galaxy s3 boot logo. And it wouldn't go past it. Tried flashing different backups I had but none of them let me go past the boot logo. Flashed CM10 since my version of TWRP recovery is so old that it can't flash anything higher up, and it goes past the boot logo finally after 2 hours then goes to the cyanogen boot logo but doesn't go past that. I'm going to try with ODIN tonight.
Seems very strange that there are others that had this happen to them to. My phone has never done this before, and it happened randomly.
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
LarsonJayz said:
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
Click to expand...
Click to collapse
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
crazexr7 said:
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
Click to expand...
Click to collapse
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
DocHoliday77 said:
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
Click to expand...
Click to collapse
Yeah factory reset unfortunately didn't work for me when I needed it before I had to ODIN to root66. But I was able to do a nandroid after I couldn't get it to boot and extract my sms from Titanium backup. What an awesome app, super thankful to that dev for making it.
DocHoliday77 said:
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
Click to expand...
Click to collapse
Turns out it was the battery sir. I've tested it with another battery from 2 different phones and it worked fine. While the phone i tested with the defective battery didn't event get passed the samsung logo. I've suspected it might be having the low voltage causing the phone to shut down.
Anyways, after that i bought a new battery immediately and everything seems ok. thanks for the reply doc.
DocHoliday77 said:
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
Click to expand...
Click to collapse
I can confirm that it is likely a bad power button, I have tried everything including dismantling it and seeing if I could dislodge any dirt that may be causing the problem but it didn't work. Looks like I have to find a local repair shop or ebay to get it resolved. Anyone recommend a good place to get this fixed. Funds are limited
Im not sure exactly how difficult the repair is most people seem so do it themselves and have given indications that its pretty easy. You can find the part online for a few bucks.

Categories

Resources