so recently my droid decided to take a **** on me
it was going in a bootloop so i decided to sbf_flash the 2.3.0 sbf since it was already updated and it successfully completed flashing as well as rebooting and everything
but now it goes from the motorola logo straight into the bootloader screen and it just says
Bootloader 3.25
Battery OK
OK to program
Connect USB
Data Cable
i tried multiple data/cache wipes and even multiple flashes and i still get this damn bootloader screen
im about ready to toss this thing hahahaha
help please?
I'm having the same issue but mines says D2.37 Battery Ok, etc.
Booted into Windows on a Macbook.
Downloaded the droid root charge kit stickied in this forum.
Installed the samsung drivers. Loaded Odin.
Flashed the voodoo kernel in seconds, no problem.
Then, when I try to flash a ROM, it gets about 75% done, either hanging during the systemfs.rfs phase, or all the way up to movin???.dll (i don't recall the exact name). The phone says, "RX_TIMEOUT". It never gets past this point.
I've tried flashing back to factory stock, using both Odin and the samsung flasher, loading up the PIN and stock EE4. Same thing. Hangs at 9%. Sometimes just crashes and says 'Error, download cancel'.
I'm waiting for my wife to come home, since she has a PC laptop. I'm really, really hoping I just need to flash it from an actual Windows machine.
Stuck with a soft bricked phone. I've tried everything possible to flash back to factory (or anything, for that matter), but it's always the same. Hangs halfway through. Can someone please assist me?
sushi_stalker said:
Booted into Windows on a Macbook.
Downloaded the droid root charge kit stickied in this forum.
Installed the samsung drivers. Loaded Odin.
Flashed the voodoo kernel in seconds, no problem.
Then, when I try to flash a ROM, it gets about 75% done, either hanging during the systemfs.rfs phase, or all the way up to movin???.dll (i don't recall the exact name). The phone says, "RX_TIMEOUT". It never gets past this point.
I've tried flashing back to factory stock, using both Odin and the samsung flasher, loading up the PIN and stock EE4. Same thing. Hangs at 9%. Sometimes just crashes and says 'Error, download cancel'.
I'm waiting for my wife to come home, since she has a PC laptop. I'm really, really hoping I just need to flash it from an actual Windows machine.
Stuck with a soft bricked phone. I've tried everything possible to flash back to factory (or anything, for that matter), but it's always the same. Hangs halfway through. Can someone please assist me?
Click to expand...
Click to collapse
your best bet seems to be what you're trying to do, try and odin back to stock on a windows pc and work your way from there if you wanna root or put roms on
blazing through on my VZ Droid Charge 4G
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.
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.
Please help, ive read almost every post about this but none seems to work for me, i was on LEGORom, and today i decided to go back to 4.0.4, the susprise was when i got stuck on the M logo(the one with the waves) its moves three times and then i just see the M logo and nothing more, im able to get into fastboot, and conect to Rsdlite, i have flashed multiple times and the problem still there, also i did a factory reset via the stock recovery and the same issue, also i did the other method to flash the tom, and also to flash only the system and nothing seemed to work out.
Please i need some help.
Something that i notice watching the how to flash via rsd lite video on youtube is that my phone doesnt show up anything in the "device properities" part, is blank but that does not stop the flashing.
Thats everything that i did today, i hope someone can help me
edit1: on my pc it shows on devices properities all N/A but still the M logo stuck
Did you wipe everything before flashing?