Just bought my phone a couple of days ago, I was looking to root it as I had an Incredible but stepped up to this. Rooting went pretty good, failed first time but went through the second. Then I installed rom manager and flashed clockwork. I then went into the recovery but saw that I had an issue with with it about signatuire verification so I figured I still had the stock recovery. I went in and got the modded recovery file and just renamed the old one. Rebooted into recovery and the phone would lock at the samsung screen and not go anywhere. So i booted it back up like regular and flashed clockwork again and tried to boot into recovery again with the same issue but now I can't get the phone to boot up regularly. Its just hanging at the samsung screen, I have the battery pulled while I wait just to make sure its not an issue like that. Did I miss something when I was doing this? I watched the videos on how to root and install the recovery but I'm lost as to what is going on now. I thought my only issue was the stock recovery was still installed for some reason so I replaced that with the modded version. Thanks for you help and I hope I don't have to redo everything again.
Alright, delete this as I got inpatient and figured my phone was screwed anyways so I went ahead and used odin and I'm in clockwork right now. Sorry for creating a useless thread.
Related
Hi guys, reasonable newbie here. My Galaxy S2 has stopped displaying anything after the initial logo. In fact it seems to turn the phone off as you can make repeated attempts to boot it within a few seconds.
I started by flashing an insecure sgs2 kernel from this site with odin, then used s2root.
I then played around with rom managed but found it wouldn't boot into clockworkmod (orange exclamation mark in a white triangle every time) I booted into it manually and started trying to flash cm7 which I had downloaded earlier.
I wiped the data etc and flashed the cm7 zip (plus the google apps zip). Rebooted and got into cm7 with everything seeming fine.
Next I thought I should probably flash back to the stock version of the insecure kernel. I rebooted the phone but got distracted and didn't start it up in download mode, I looked just in time to see the normal logo (with the yellow insecure triangle) and then nothing....just blank.
I tried rebooting afew times and nothing, even after yanking the battery. Then I tried getting back into clockworkmod to reflash cm7. Nope, same thing happens.
I can still get back into download mode but nothing I flash makes the slighest difference. Tried reflashing clockworkmod, insecure and stock kernels of various versions but I'm stuck.
This is almost a new phone and I can't believe I've already killed it I would be so grateful for any tips, I've included as much info as I can think of from the top of my head but I will do my best to answer anything you gurus might need.
Again, very grateful for any help...I don't want to have to explain to Orange how I've managed to brick this after 4 days
Ok after trying over and over again to get into recovery mode, it booted into the original (3e) recovery. I've just flash cwmod to it again and have just flash cm7.
After reading some posts about cyanogenmod sometimes not flashing correctly first time, I did it twice (and it did indeed take longer the second time) and twice for google apps.
Next I'll try to get back to the stock kernel. This is where it went wrong before but i'll cross my fingers.
Edit: Well, multiple reboots didn't cause a problem but flashing the stock kernel back does kill the handset again. I'm sure this stuff is all obvious to those with experience I guess I'll have to sit with an insecure kernel and the yellow triangle for the forseeable future. On a side note, s2root doesn't see the phone connected with cm7 (yes usb debugging was turned on). I'm hoping that it is pre-rooted but I haven't tested that yet.
i have rooted my g2x several time but after i shut if off to charge at night i tuirned it on and it went straight to the cwm recovery screen i wiped it and restarted it and it went right back to it i flashed several other roms and when i went to reboot it it still rebooted to recovery screen i formated everything i new of what am i doing wrong. i had a stable rom in it and it was working for like 3 weeks before this happened . I hope someone can help me on this i love my phone and dont want to lose it. My computer is running on windows 7 i have tried these
http://forum.xda-developers.com/showthread.php?t=1056847
http://forum.xda-developers.com/show....php?t=1056847
and i even tried one where i tried to flash it back to stock and and now it stuck on a white box with an arrow coming out of it with and android robot in front of it
Did i brick this can it be saved i hope someone can help me one this i just pray i didnt brick it
STANC1 said:
i have rooted my g2x several time but after i shut if off to charge at night i tuirned it on and it went straight to the cwm recovery screen i wiped it and restarted it and it went right back to it i flashed several other roms and when i went to reboot it it still rebooted to recovery screen i formated everything i new of what am i doing wrong. i had a stable rom in it and it was working for like 3 weeks before this happened . I hope someone can help me on this i love my phone and dont want to lose it. My computer is running on windows 7 i have tried these
http://forum.xda-developers.com/showthread.php?t=1056847
http://forum.xda-developers.com/show....php?t=1056847
and i even tried one where i tried to flash it back to stock and and now it stuck on a white box with an arrow coming out of it with and android robot in front of it
Did i brick this can it be saved i hope someone can help me one this i just pray i didnt brick it
Click to expand...
Click to collapse
I don't exactly know how to fix your problem, but to shine some light, your not bricked. If u were, u wouldn't be able to access anything
Sent from my LG-P999 using XDA
STANC1 said:
i have rooted my g2x several time but after i shut if off to charge at night i tuirned it on and it went straight to the cwm recovery screen i wiped it and restarted it and it went right back to it i flashed several other roms and when i went to reboot it it still rebooted to recovery screen i formated everything i new of what am i doing wrong. i had a stable rom in it and it was working for like 3 weeks before this happened . I hope someone can help me on this i love my phone and dont want to lose it. My computer is running on windows 7 i have tried these
http://forum.xda-developers.com/showthread.php?t=1056847
http://forum.xda-developers.com/show....php?t=1056847
and i even tried one where i tried to flash it back to stock and and now it stuck on a white box with an arrow coming out of it with and android robot in front of it
Did i brick this can it be saved i hope someone can help me one this i just pray i didnt brick it
Click to expand...
Click to collapse
Use this to put cwm and then flash the rom you like.
If phone still boots into recovery you may have a stuck vol- button.
http://forum.xda-developers.com/showthread.php?t=1590523
Sent from my LG-P999 using XDA
i cant get into recoveery now im stuck in it relaoding as i tried to flash the recovery again and its stuck
try and flash again, if it doesn't stick, then try again. If it gives you an error report the error. Try what mansa_noob posted, it usually works for everyone, it fixes everything (partition and issues) and then flashes the recovery for you.
Aight, so here's what happened, installed a custom boot animation, but it's in a loop, it keeps playing, cold boot doesn't work, recovery gives me the dead android, can't rly acces my tab in any way. The only thing I can do right now is getting it recognized as fastboot, everything else I tried results in my Hardware manager not even recognizing my tablet.
I got a rooted JB, not unlocked.
Rly got no idea what to do now, is it perma bricked or can I find a way out again?
Update: just left it bootlooping while I went for a spliff and voila, seems like it's done a factory reset or so
Looks like i lost EVERYTHING on the tablet but seems like it's working again, probably lost root etc though :/
Update 2: google is reinstalling all my apps now, gonna take a while
Update 3: at first looks, I still got root, rootchecker says I still have root, don't know what should happen with like ES file explorer if I don't have root but so far it all seems to work. Got it figured out what happened too, it wasn't a boot loop, it was just the custom animation that sorta ****ed up and kept rolling, I then started a recovery but didn't let it finish, so when I finally decided to stop tampering and just let the battery die out, it had enough time to actually finish that recovery.
Update 4: first reboot got me again, still the same animation, well, let's hope I still got root after next recovery, so I can fix that.
Update 5: all is good again, besides that everything from tab is gone, aah well, kinda wanted a fresh start with jb anyway
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.
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.