Database Info

so i think i bricked?! help please..

..so yesterday i was going to switch roms from darky's to cm7 and i went into recovery and when i flashed cm7..it never loaded, i cant get past the samsung logo. i Tried flashing like 7 roms that i have on my sd card and nothing, still stuck on the recovery (red) or samsung logo?
any ideas? this happened to me last week but i just flashed an old rom and it finally booted but now no luck.

mainguy21 said:
..so yesterday i was going to switch roms from darky's to cm7 and i went into recovery and when i flashed cm7..it never loaded, i cant get past the samsung logo. i Tried flashing like 7 roms that i have on my sd card and nothing, still stuck on the recovery (red) or samsung logo?
any ideas? this happened to me last week but i just flashed an old rom and it finally booted but now no luck.
Click to expand...
Click to collapse
edit: my bad..wrong link.
http://forum.xda-developers.com/showthread.php?t=1437548
my guess it's odin or heimdall time

Had same issue but with different rom (Zeus).
I pulled the battery for 15 minutes(that helped to get into recovery/past Samsung flash screen).
Booted into red recovery,full wipe,reinstalled rom from SD card.no issues since.
However,when I tried any backup,it didn't work.so...
Restart with full wipe,and load off of sdcard?might work.
Sent from my HTC Glacier using XDA App

cm7 double flash
that's par for the course. the op claims you need to double flash the cm7 rom. gtg unbrick will fix her up.

Flashing Rom ends up in Loop

Hi was wondering if anyone could help me. I rooted my friends phone awhile back and it was all fine and hunky dorry until he fudged up. I guess he got a new phone so he tried to give the Optimus V to his son but he did a factory reset from the settings menu you. No the phone won't do anything. Try to power it on but it just shows the first LG logo then off again. If I plug the phone in CWM comes up but I've tried installing a new rom but it winds up doing the same thing. Also I can't get it to show up in adb or fastboot.

PorkMoon587 said:
Hi was wondering if anyone could help me. I rooted my friends phone awhile back and it was all fine and hunky dorry until he fudged up. I guess he got a new phone so he tried to give the Optimus V to his son but he did a factory reset from the settings menu you. No the phone won't do anything. Try to power it on but it just shows the first LG logo then off again. If I plug the phone in CWM comes up but I've tried installing a new rom but it winds up doing the same thing. Also I can't get it to show up in adb or fastboot.
Click to expand...
Click to collapse
Flash the stock rom
http://forum.xda-developers.com/showthread.php?t=1324105

[Q] Bricked/Boot Loop Galaxy Note 10.1!!

Hello fellow XDA members! I am a Noob.
So I believe I have a Bricked Galaxy Note 10.1. Model GT-N8013
I Rooted Stock ROM, and flashed Collective Edition 5 Dark Side.
So heres what happened, everything seemed fine, until I made a mistake, I was Pimping my ROM with the PimpMyRom app. Every change seemed fine and my note worked, but when i saw the double boot screen slide in the app, i did what it said, i have the imf support or something like that. Then after i had the ''support'' needed, i clicked install button on the double boot slide, it seemed to do something and requested nothing, so i went ahead chose a second clip, and clicked set as second boot screen. It said it wont take effect until the 3rd boot, so i rebooted 3x, but at the third time, it was stuck at the boot screen with the galaxy note 10.1 logo ! It did not start or did anything, over time it would turn off and automatically reboot, but it would get stuck again !.
To attempt to fix it, I Booted into recovery (CWM) and did everything i could. I wiped nearly all cache, factory reseted, then out of fear, i flashed the stock firmware ROM from Sammobile website, with ODIN, and to my knowledge, it got worse!! It booted, seemed to do something then in the logo screen it got stuck once again!! Stock recovery says unable to mount /efs, i don't believe EFS is completely corrupted, I left it stuck for awhile and it shut down in like an hour. Help, what can i do to fix this!?!?!?!
Device cannot boot up.
I could boot into recovery and download mode only.

I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.

jusliloleme said:
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
Click to expand...
Click to collapse
i did what u said...but all i got is i able to get through the logo but without seeing anything only able to hear the sound. any other tip? i got the same problem as above.

[Q] Galaxy S2 Soft Bricked after root....

Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!

addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
Try flash a stock firmware by using flashtool, it will work 100%:angel:

revernwe therefore
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.

I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll

brandonarev said:
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
Thanks for the advice! Should i flash it back to ICS then try to root again via Odin before i upgrade back to JB? I'm guessing there's something that isn't getting wiped. Since i can run CWM and Root with Odin without a hitch. it's the initial reboot after all that is done that I go into the boot loop.

tainiun rioters
pierm said:
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
Click to expand...
Click to collapse
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?

One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!

addamT989 said:
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
Click to expand...
Click to collapse
addamT989 said:
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
Click to expand...
Click to collapse
Hi
TWRP and the 'one touch recovery, better than CWM.
The backup kies can not recover from CWM
steps:
install odin, after recovery, nandroid backup, ROM, and root.
hi

Flash the stock firmware using odin!!..it will work!
Sent from my GT-N7100 using xda premium

freezes then booted
Hello I have this problem with my galaxy s2 i9100. After reboot the phone wasn't booting something like "boot loop" so I re flashed the firmware and now the phone boots up but after the boot it freezes immediately. So I decided to install clock work mod recovery and install cyanogen mode 11 with cyanogen mode the phone boots up and are able to be used again until the screen goes to sleep mode or the power button is pressed then the screen goes black and doesn't turn on after long pressing the power button it reboots. So I don't know what else to do I have tried kernels, operating systems re flashing reseting and nothing helps. No need to tel me to do resettings. Also my galaxy s2 i9100 chip has insane chip bug but I don't know if it has to do something with my problem.

Tabled is dead

My device has been bricked for 3 month then just a few days ago someone here on xda posted a fix and it worked for me I was really happy.
Flashed custom recovery, then tried all new roms (missed 3 month).
Then yesterday I decided to sell it to my friend and wanted to revert all back to stock. Got US_10_6_1_15_3 from asus webpage. Flashed blob all went well.
All booted up fine, and just to be sure all is 100% clean i went to do a factory reset within the rom, it did its thing then rebooted.
Now its dead, Asus logo appears for 2 sec then reboot, same thing over and over. I cant even shut it down. Apx mode is available I think.
Hopefully this doesn't happen to anyone else Can anyone give me some tips?

echohack said:
My device has been bricked for 3 month then just a few days ago someone here on xda posted a fix and it worked for me I was really happy.
Flashed custom recovery, then tried all new roms (missed 3 month).
Then yesterday I decided to sell it to my friend and wanted to revert all back to stock. Got US_10_6_1_15_3 from asus webpage. Flashed blob all went well.
All booted up fine, and just to be sure all is 100% clean i went to do a factory reset within the rom, it did its thing then rebooted.
Now its dead, Asus logo appears for 2 sec then reboot, same thing over and over. I cant even shut it down. Apx mode is available I think.
Hopefully this doesn't happen to anyone else Can anyone give me some tips?
Click to expand...
Click to collapse
can you boot to fastboot?

Nope, this time its dead for good i think. Just a warning to all then.
Was on V10.6.1.27.1 bootloader running makelegs nightly builds. Then I flashed back to V10.6.1.15.3.
Then when booted up, went into settings and choose factory reset.
Baang bootloop.
Can only get Apx and thats usless since I don't have Nvflash.
I'm kinda sad, I just recovered it from the brick we all had back in may-apr. The new bootloader wrong recovery crap.
Then 2 days later This happens.

I think wiping from the settings is like wiping from the bootloader but what about trying this mate http://forum.xda-developers.com/showpost.php?p=44574476&postcount=9
Sent from my Nexus 7 using Tapatalk 4