I think I've just bricked my phone. I purchased it second hand only half an hour ago. Used the temporary root method, flashed Slimbean, then Gapps, (perhaps) stupidly chose the erase data/wipe factory settings option, hit reboot....
ET VOILA
black screen. No download mode, no recovery, no signs of life whatsoever.
Should I just chuck it in the bin and move on? Or is there actually anything I can do?
leoni1980 said:
I think I've just bricked my phone. I purchased it second hand only half an hour ago. Used the temporary root method, flashed Slimbean, then Gapps, (perhaps) stupidly chose the erase data/wipe factory settings option, hit reboot....
ET VOILA
black screen. No download mode, no recovery, no signs of life whatsoever.
Should I just chuck it in the bin and move on? Or is there actually anything I can do?
Click to expand...
Click to collapse
Since its second hand.....BIN
Sent from my GT-I9100 using xda app-developers app
No life even when plugged in to charge?
Maybe try a USB jig?
If not then game over I'm afraid
Spoiler
Smartphone: Galaxy SII
Rom 1: Paranoid Android v2.54
Rom 2: Stock JB leak(online)
Kernel: DorimanX V7.38
Lol try a jig.Youd still get around £100 for it on eBay so dont bin it.
leoni1980 said:
I think I've just bricked my phone. I purchased it second hand only half an hour ago. Used the temporary root method, flashed Slimbean, then Gapps, (perhaps) stupidly chose the erase data/wipe factory settings option, hit reboot....
ET VOILA
black screen. No download mode, no recovery, no signs of life whatsoever.
Should I just chuck it in the bin and move on? Or is there actually anything I can do?
Click to expand...
Click to collapse
This Might help you
Peaceful Droid said:
This Might help you
Click to expand...
Click to collapse
I get absolutely no signs of life at all. I was in the CWM touch menu, chose the reboot option and it just didn't boot. I've hand no sign of life ever since. When I plug it in to charge it just does nothing.
I've contacted Samsung and arranged a warranty repair. Not sure if it's a good idea or not but I didn't have a custom kernel installed at that stage: I'd tried flashing Slimbean and Gapps straight from the temporary CWM.zip from the original Stock ICS ROM.
My procedure was that I erased user data, installed Slimbean, installed Gapps, wiped cache, wiped Dalvik cache, wiped battery stats, rebooted.
Dead phone.
Related
guys i have a funny issue wonder if i can get some help. I flashed FlappJaxx Beta 3 and had a bad down load or something so anyway tons of reboots and nothing just the non stop vibrate.. well i i finally got it back to the down load screen after pulling the battery several times. and got it Odin back to unrooted and turn on followed the unroot instruction well i left it stock and have had same issue where i click something and it flashes and just vibrates over and over until i pull battery.. well is this phone dead is there a fix?
I odin back again and same thing im going to odin back to stock again then do a stock root and flash another room but its doing the stupid reboot over and over vibrate thing even with the non-rooted stock rom. i just can't seem to find any direction on how to fix this or is it just a lost cause. wanted it to hold on till Note 2 hit shelves but looks like a s3 in my futures.
OK didnt work still FC and boot looping this time i installed Kies and put in download mode and updated the firmware and im getting same thing. GOSH DOGGIT hahaha.. Yea i need some advise i tried everything ive read i must be missing something somewhere.
i guess no one has ever had this before? still no solution i have tried everything format the internal disc but want to know if i do that will i be able to flash odin back to stock any help there?
walkerkd said:
i guess no one has ever had this before? still no solution i have tried everything format the internal disc but want to know if i do that will i be able to flash odin back to stock any help there?
Click to expand...
Click to collapse
First of all, I'm no pro at this stuff but I feel your pain.
It sounds like you are getting stuck in a boot loop of sorts.
What I would do if I was you, after flashing a rom, go back into Recovery mode on the phone and clear out the cache partion, wipe Dalvik cache, and then wipe data/factory reset. After that, reboot your phone - it should start up normally. This is what I do to my phone to get it to function as it should.
Hope that helps
i went in to the advance tab and formatted everything hahah.. it juts wiped and odin back to stock again bout to wipe it and try to odin root see if i can get it done. worth a try ive tried to much stuff im bout to take phone out get my 338 tape to a zombie target and have some fun!
walkerkd said:
i went in to the advance tab and formatted everything hahah.. it juts wiped and odin back to stock again bout to wipe it and try to odin root see if i can get it done. worth a try ive tried to much stuff im bout to take phone out get my 338 tape to a zombie target and have some fun!
Click to expand...
Click to collapse
What language are you using here? I have no idea what you are saying.
kmacsouris said:
First of all, I'm no pro at this stuff but I feel your pain.
It sounds like you are getting stuck in a boot loop of sorts.
What I would do if I was you, after flashing a rom, go back into Recovery mode on the phone and clear out the cache partion, wipe Dalvik cache, and then wipe data/factory reset. After that, reboot your phone - it should start up normally. This is what I do to my phone to get it to function as it should.
Hope that helps
Click to expand...
Click to collapse
Agreed ...
When returning to stock via Odin ...you must reboot into your recovery and wipe data and factory reset the device prior to rebooting.
Even though you wiped prior to flashing the stock Odin .tar image.
These devices stay dirty even after wiping data on occasion ...g
gregsarg said:
Agreed ...
When returning to stock via Odin ...you must reboot into your recovery and wipe data and factory reset the device prior to rebooting.
Even though you wiped prior to flashing the stock Odin .tar image.
These devices stay dirty even after wiping data on occasion ...g
Click to expand...
Click to collapse
Yea i think thats what happen. it was not a clean wipe but i think i got it now i have gotten two fc & reboot i can live with that. thanks you guys for your help.
walkerkd said:
Yea i think thats what happen. it was not a clean wipe but i think i got it now i have gotten two fc & reboot i can live with that. thanks you guys for your help.
Click to expand...
Click to collapse
Boot into your recovery, and "fix permissions "...then reboot.
That should clear up the rest of the issues ...g
gregsarg said:
Boot into your recovery, and "fix permissions "...then reboot.
That should clear up the rest of the issues ...g
Click to expand...
Click to collapse
oh really? wow i didnt even think about that im wiping again and flashing odin to stock but this time after it boots i will wipe factory reset. then root factory reset and fix permissions. thank for the help!
Always welcome ....
Fixing permissions is overlooked a lot ...
And the wrong permissions will cause FC's all over the build ..
I always fix permissions after any flash or modification ....it's just a good habit to get into ...IMHO ...g
Noob here, please bear with me:
Updated my I577 to ICS, then rooted it using this thread: http://forum.xda-developers.com/showthread.php?t=1806118
Worked like a charm, then I picked up ROM Toolbox Lite from PlayStore, which worked fine until I tried to change themes.
Somehow, it got to where boot was stuck at vendor logo. Unfortunately I did not Nandroid backup in time, but I was able to do a Kies backup before rooting, so not worry about the data loss at this time.
Used CWM5, did davlik & cache wipes, factory resets several times, no dice. No stock ROM available so I tried this:
http://forum.xda-developers.com/showpost.php?p=30444507&postcount=6
(flashed system tar through ODIN) Hanged at "system.img.ext4".
Here's where I'm at now:
-- Boot looping at second Samsung logo
-- ODIN 1.85 still reads device at port
-- Battery indicator visible when plugged in & power off.
-- Still able to get to cwm recovery 5.5.0.4
So, IS IT SOFT BRICKED OR HARD BRICKED?
Bonus Question: Is it unbrickable?
Any input or answers are GREATLY appreciated, and a fix will most likely be monetarily compensated through Paypal.
Black-wolf, j3r3goss, or shabbypenguin if you see this, your input is certainly appreciated as well!
Its soft bricked. Hard brick means there is no life at all and won't even power on (through software).
Any soft brick is unbrickable, the only nonunbrickable brick is a hard brick (which is rare)
Sent from my MB508 using xda premium
If you can get into Clockwork Mod Recovery still then select wipe data (Do this twice), then select whipe cache (Do this twice), next select factory reset (Do this twice), finally go back and select reboot system. This should unbrick your phone for you
Sent from my SCH-I535 using xda premium
shimp208 said:
If you can get into Clockwork Mod Recovery still then select wipe data (Do this twice), then select whipe cache (Do this twice), next select factory reset (Do this twice), finally go back and select reboot system. This should unbrick your phone for you
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This.
If you can get into recovery you're only in shallow water
Sent from my MB508 using xda premium
Something's changed
THANKS so far for the input!
I was able to nandroid out of the loop, but now it's back to my original problem--it keeps booting to the "Rethink Possible" AT&T screen & freezing.
Any ideas? I'm thinking I'm gonna be outta luck until I get my hands on a legit Gingerbread Stock tar.
Did you whipe cache, whipe data and preform a factory reset like we suggested? Preforming a nandroid restore won't get you out of your phone hanging on the at&t logo.
Sent from my SCH-I535 using xda premium
Samsung Galaxy Ace GT-S5830i brick
hey there im a noob to all this but i registered to see if someone here could give me advice.
i tried to flash a new rom on my phone (see title) and it doesnt do a thing anymore...
i rooted it and tried to put Retribution beta_2 on it and itlooked to be working till it rebooted..
all i got was the startup screen with galaxy ace gt-s5830i.
i looked around and i found that i could use download mode and odin 1 click download to put in a new rom.
so i tried that and it looked to be working but it stalled at end of install and now it doesnt even turn on anymore...
HELP!!!
hope someone knows whats up and can give me some advice.
i hope i didnr hardbrick it like i saw in this thread...
Emil.warm said:
hey there im a noob to all this but i registered to see if someone here could give me advice.
i tried to flash a new rom on my phone (see title) and it doesnt do a thing anymore...
i rooted it and tried to put Retribution beta_2 on it and itlooked to be working till it rebooted..
all i got was the startup screen with galaxy ace gt-s5830i.
i looked around and i found that i could use download mode and odin 1 click download to put in a new rom.
so i tried that and it looked to be working but it stalled at end of install and now it doesnt even turn on anymore...
HELP!!!
hope someone knows whats up and can give me some advice.
i hope i didnr hardbrick it like i saw in this thread...
Click to expand...
Click to collapse
Are you able to get into recovery mode? Did you flash a custom recovery such as TWRP or Clockwork Mod Recovery?
Samsung Galaxy Ace GT-S5830i brick -
shimp208 said:
Are you able to get into recovery mode? Did you flash a custom recovery such as TWRP or Clockwork Mod Recovery?
Click to expand...
Click to collapse
Hi thanks for your response to my problem,
yes i flashed a custom recovery from clockwork and i rooted it. i cant get in to recovery mode.
after i did that i tried flashing custom rom like i said before but after reboot it didnt do anything.
i just got the startscreen and found that i could use download mode and odin to flash original rom.
i used 1 click downloader from Odin and it started to recover my rom,but at the end it stalled.
after that happened i couldnt do anything anymore.
i thought it was totally dead but i just saw that when i connect to my comp it says unknown device..
im an idiot for trying this stuff without the knowledge..it looked easy in descriptions
but i found different descriptions how to do it..
i cant put links in my posts yet cause i am new..
i used the 1st one.. but after that didnt work i found that other 1 and that is little different...
.android.gs/update-galaxy-ace-s5830i-retribution-gingerbread-2-3-6
.technostall.com/samsung-galaxy-ace-s5830i-installing-retribution-custom-rom-firmware
i hope i have given you enough info
greets Emil
Hmm today i found out smth new,i installed some samsung drivers and now my phone is recognized as a samsung android phone-android composite adb interface its says in device mananger on my laptop.
All Fixed!
shimp208 said:
Did you whipe cache, whipe data and preform a factory reset like we suggested? Preforming a nandroid restore won't get you out of your phone hanging on the at&t logo.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I did all that, but the one thing that finally nailed it was formatting my internal SD. I also formatted my external one, but I don't even think I put it back in the phone.
So, if anybody's reading this in the future, and you're still stuck after wiping the cache, wiping Davlik & performing factory reset,
FORMAT THE SD!
And flash this through Odin: http://forum.xda-developers.com/showpost.php?p=31765274&postcount=59
Huge thanks to j3r3goss!! :good::good::good:
Main Exhilarate thread here:
http://forum.xda-developers.com/showthread.php?t=1926253
Soft bricked my galaxy s4
gagdude said:
Its soft bricked. Hard brick means there is no life at all and won't even power on (through software).
Any soft brick is unbrickable, the only nonunbrickable brick is a hard brick (which is rare)
Sent from my MB508 using xda premium
Click to expand...
Click to collapse
Hey, total noob here but Im having problems with my Galaxy S4 so I was on this thread looking for a fix.I have an AT&T Galaxy s4 (SGH-I337) and I just rooted my phone and installed clockworkmod recovery. I went to backup and then when I rebooted it freezes at the AT&T logo. Ive wiped data/factory reset, wiped caches, etc ive done everything and it freezes at the same spot. I have no ROMS as I had just rooted, just stock 4.2.2. Then I saw a vid on how to unroot/unbrick and it was working perfectly until it went to reboot.(I downloaded 4.2.2 firmware for my model phone) I used ODIN and it said pass then when it was rebooting it froze in the exact same spot (also instead of the normal bootup it still had the "custom" and an unlocked lock that Ive had since I rooted) and now I cant enter recovery mode. It starts booting but then freezes when the blue letters come on! Now even when I try to turn it on normally it freezes at the samsung logo (with unlocked lock and "custom")Please help! I would greatly appreciate it!
Hi am a noob so pls bare with me ( an yes ive watched the noob vid ) with all this droid jargon but thought i'd try anyway an root my g3 i9300 phone. Which I did successfully in Dec using sgs3 toolbox. I never got time to flash a custom rom till yesterday. I found the Omega v44 Jelly Bean rom an thought it looked good so i used it. As I went through the motions of the the installing it thru clockwork recovery CWM. When it came to full wipe or no wipe i clicked no wipe. I was a little unsure, anyway it worked and the rom was installed. It worked fine but stalled on 1 or 2 apps so I thought it must have been because I never fully wiped, so here come's my mistake...............
I thought i'd do the process again ( installing the rom thru CWM ) and do a full wipe see if that helps. It ran its course and then rebooted then got a message saying fix root? I clicked stupidly click yes thinking there was a problem. Rebooted only to find it go back to clockwork CWM.
Now when it reboots and the samsung i9300 logo comes up with no red (!) in top left. Then it reboots to the logo again on its own again with the red (!) this time an goes straight back into CWM. I think ive created two roms on one phone one rooted one not. Is this fixable? I know it sounds pretty bad but we live an learn from our mistakes, even on the epic proportion.
Also its not accessible thru usb anymore.
Thanks for anyone if you can help
Stu :crying:
A very shameful noob
StuDarb said:
Hi am a noob so pls bare with me ( an yes ive watched the noob vid ) with all this droid jargon but thought i'd try anyway an root my g3 i9300 phone. Which I did successfully in Dec using sgs3 toolbox. I never got time to flash a custom rom till yesterday. I found the Omega v44 Jelly Bean rom an thought it looked good so i used it. As I went through the motions of the the installing it thru clockwork recovery CWM. When it came to full wipe or no wipe i clicked no wipe. I was a little unsure, anyway it worked and the rom was installed. It worked fine but stalled on 1 or 2 apps so I thought it must have been because I never fully wiped, so here come's my mistake...............
I thought i'd do the process again ( installing the rom thru CWM ) and do a full wipe see if that helps. It ran its course and then rebooted then got a message saying fix root? I clicked stupidly click yes thinking there was a problem. Rebooted only to find it go back to clockwork CWM.
Now when it reboots and the samsung i9300 logo comes up with no red (!) in top left. Then it reboots to the logo again on its own again with the red (!) this time an goes straight back into CWM. I think ive created two roms on one phone one rooted one not. Is this fixable? I know it sounds pretty bad but we live an learn from our mistakes, even on the epic proportion.
Also its not accessible thru usb anymore.
Thanks for anyone if you can help
Stu :crying:
A very shameful noob
Click to expand...
Click to collapse
Go to recovery holding power, home and vol up.
Go to mounts and storage and formst system, data and cache.
Then go to first page and go to install zip. Select and install your rom. Then go to advanced and clear Dalvik cache. After that reboot.
Drew071
Sent from my GT-I9300 using xda app-developers app
Here's the fact
1. I was running the 12-31-13 CM11 Nightly with KToonz 12-21 Kernel.
2. I had some problem with the screen not turning on after I accept a call. It's been going on for a few months now, despite doing full wipes in between, so I decided I was gonna just do another wipe and hope that it would somehow solves itself.
3. While I was in TWRP 2.5.2.X , I did factory reset
4. I also wipe /system
5. I flashed CM11 1-1-14 / 12-30 GApps / KTkernel / BootAnimation / SuperSU 1.86
6. During the last portion, I get some running message that it failed to mount E:/ something something & Partition and such
7. Thinking it was a fluke, I pressed reboot and... bootlooped at the Samsung logo screen
8. I Power + Vol UP back into Recovery and flashed the 12-31 CM11 nightly, plus GApps etc,
9. Got the same strings of messages telling that it failed to mount partition and E:/ and /data/ and something lost and found/
10. I rebooted and... Bootlooped at the Samsung logo.
11. I tried to get back into recovery and has been unable to.The little blue "Recovery Booting" seems to appear for a very short time before the phone rebooted again. Seems like it's not there anymore.
Part of me thinks that perhaps the phone's internal memory failed. So far the only thing I can do with it is charge the phone.
Anyone with any knowledge of this, please help.
you gotta go to back odin to get a recovery back on your phone. Also the screen not turning on has been an AOSP issue for awhile, it's not just you and reflashing won't do anything to fix it.
Sent from my CIA sanctioned device
joshm.1219 said:
you gotta go to back odin to get a recovery back on your phone. Also the screen not turning on has been an AOSP issue for awhile, it's not just you and reflashing won't do anything to fix it.
Sent from my CIA sanctioned device
Click to expand...
Click to collapse
What would I do with another recovery? Is the one I have on it now doesn't work anymore?
asianrage said:
What would I do with another recovery? Is the one I have on it now doesn't work anymore?
Click to expand...
Click to collapse
well if you can't boot into it, it's not working right?
asianrage said:
What would I do with another recovery? Is the one I have on it now doesn't work anymore?
Click to expand...
Click to collapse
Just a note keep in mind TWRP is not recommended for CM11. Also I am lucky I have MDK device and a version of the no data wipe stock install, whenever things go wonky (like bootloop on Samsung Logo) I Odin back to stock. make sure the phone works, then restart from scratch and re-root, re-install recovery and reflash CM. I am not super technical so sometimes it can take about 1-2 hours from screwing up the phone to going back to having a working CM11 GS4.
All Hail invisiblek
http://forum.xda-developers.com/showthread.php?t=2559335
stein5830 said:
Just a note keep in mind TWRP is not recommended for CM11. Also I am lucky I have MDK device and a version of the no data wipe stock install, whenever things go wonky (like bootloop on Samsung Logo) I Odin back to stock. make sure the phone works, then restart from scratch and re-root, re-install recovery and reflash CM. I am not super technical so sometimes it can take about 1-2 hours from screwing up the phone to going back to having a working CM11 GS4.
All Hail invisiblek
http://forum.xda-developers.com/showthread.php?t=2559335
Click to expand...
Click to collapse
Thanks for the reply. I've already started the process to flash back to stock MDK. I've been using TWRP for a while and have always been annoyed at how long it'll take to go past the logo screen (if I didn't give up and pulled the battery). Wish me luck.
Hey XDA
This all started when I didn't put my phone on charge one night, and the morning after I got a text then I went to read it, my screen flickered and my phone crashed, this was usual when my phone dies.
However this time, when I put my phone on charge, it wouldn't boot up, it would stay at the boot animation screen.
I was running AOKP 4.2.2.
I then thought it was just a corrupt ROM so I went to re-install the ROM.
First, when I went to wipe the dalvik cache it said it had failed, this immediately showed warning signs, then when I went to install the ROM from my SD card it said that had failed also.
This left me only 1 option, to restore back to the stock ROM through Odin.
This seemed to go fine until I got to the end went instead of booting into an "android is updating" type thing, it was stuck on a boot loop.
This now leaves me stumped for ideas, so I turn to you, how do I fix my phone?
I hope I can fix this phone as it is my only phone.
Thanks, Jem
jem.graham said:
Hey XDA
This all started when I didn't put my phone on charge one night, and the morning after I got a text then I went to read it, my screen flickered and my phone crashed, this was usual when my phone dies.
However this time, when I put my phone on charge, it wouldn't boot up, it would stay at the boot animation screen.
I was running AOKP 4.2.2.
I then thought it was just a corrupt ROM so I went to re-install the ROM.
First, when I went to wipe the dalvik cache it said it had failed, this immediately showed warning signs, then when I went to install the ROM from my SD card it said that had failed also.
This left me only 1 option, to restore back to the stock ROM through Odin.
This seemed to go fine until I got to the end went instead of booting into an "android is updating" type thing, it was stuck on a boot loop.
This now leaves me stumped for ideas, so I turn to you, how do I fix my phone?
I hope I can fix this phone as it is my only phone.
Thanks, Jem
Click to expand...
Click to collapse
after you install the stock rom via Odin boot into the stock recovery and do a factory reset and wipe the cache. should boot up after that.
one thing i notice after installing 5 different OTA though odin last night they dont wipe user data you have to do it your self. so i would give that i try im sure that should fix your problem
dray_jr said:
after you install the stock rom via Odin boot into the stock recovery and do a factory reset and wipe the cache. should boot up after that.
one thing i notice after installing 5 different OTA though odin last night they dont wipe user data you have to do it your self. so i would give that i try im sure that should fix your problem
Click to expand...
Click to collapse
Thank you very very much, I didnt see the factory reset option in the stock recovery.
You're a true life saver, thanks
jem.graham said:
Thank you very very much, I didnt see the factory reset option in the stock recovery.
You're a true life saver, thanks
Click to expand...
Click to collapse
no problem at all now if i can just figure out my clients gt-i9300 issue my life would be great hahaha