My droid X2 stuck at the M logo with "starting RSD protocol support" on top. I can get to recovery or boot up. I try couple of SBF and it still stuck there.
When I SBF, it goes through and say PASS but it still won't boot up and stuck and the M logo.
Any solutions?
Mine use to loop the droid eyeball sometimes after RSD but it was telling me to manually reboot the phone so I battery pull, put back, get into recovery, wipe data and cache, reboot and its fine. See of that does it?
Sent from my MB865 using xda premium
Have you tried just pulling the battery and then Let it set for a few minutes.
I've had my SFB hang sometimes.
Also this is in. The wrong section
Sent from my DROID X2 using Tapatalk 2
This is the wrong forum to be posting in. You should have had this in the General Section or in Q&A.
SBF'ing and then wiping data and cache is the only way to get out of that. If you can get into RSD, then you should have no problems resetting your phone.
your best bet to fix this is to pull battery, go into android recovery, wipe data/cache and reboot; and if that doesnt work then throw the phone out the window and get a better phone
Questions should be asked in Q&A forums, not Development forums.
Thread moved.
I can't even get to recovery, I pull the battery and wait for couple hours and try again. it still stuck on the logo.
metriod said:
I can't even get to recovery, I pull the battery and wait for couple hours and try again. it still stuck on the logo.
Click to expand...
Click to collapse
Not our custom BSR, stock Android Recovery. Hold the Volume Down + Power Button until "Fastboot" shows up. Then use the Volume Down key to go to Android Recovery. Once the picture in the stock recovery shows up, press both Volume Buttons at the same time. Wipe Data and Cache there.
Related
So. I was on 1.4a of CherryBlur. Flashed the newest FULL WIPE with Webtop version 1.4d. Flashed using Tenfar's Recovery and it said flashing was successful. Now, when I turn the phone on, at the motorola logo screen, with "Dual Core Technology" below it, the screen starts flashing after a few seconds (about 20 seconds) and the white "Unlocked" in the top left of the screen is gone during the flashing. What the hell? I can still get into the recovery mode, but none of the options seem to help my problem, even the factory reset.
And a battery pull is the only way to get the screen to stop blinking and restart.
Any ideas? Could the download have been incomplete/corrupted?
Err0xx said:
So. I was on 1.4a of CherryBlur. Flashed the newest FULL WIPE with Webtop version 1.4d. Flashed using Tenfar's Recovery and it said flashing was successful. Now, when I turn the phone on, at the motorola logo screen, with "Dual Core Technology" below it, the screen starts flashing after a few seconds (about 20 seconds) and the white "Unlocked" in the top left of the screen is gone during the flashing. What the hell? I can still get into the recovery mode, but none of the options seem to help my problem, even the factory reset.
And a battery pull is the only way to get the screen to stop blinking and restart.
Any ideas? Could the download have been incomplete/corrupted?
Click to expand...
Click to collapse
Hold the volume down while the phone keeps restarting. Then try to enter recovery and do a wipe.
Ps: are you on tenfars cwm or rom managers cwm? Only tenfars cwm wipes data.
Sent from my MB860 using XDA Premium App
Aye. On Tenfar's and wipe did nothing for me.
Boot into recovery and reflash Cherryblur. Sounds like your other rom you downloaded didnt finish or is corrupted.
As unbelievable as it may sound, tried this. Have 3 different versions of CherryBlur saved on my SD Card. tried reflashing the newest version (1.4d FULL WIPE) about 5 times and even tried older versions (back to 1.2) out of desperation. All result in this same hang at the motorola screen. This is one of the most amazing things that I've seen. Something buggered royally.
Hello,
I was working with a rom (eclipse) and must have done something wrong, I do have a nandroid back up on my sd card and I also saved it to my pc.
The problem is that now my phone is in a bootloop and I dont know how to restore with nandroid.
Does anyone know how to restore with a nandroid when the phone is in a bootloop?
Any help is appreciated.
If it's in a bootloop, you'll more than likely have to sbf.
Sent from my DROID X2 using Tapatalk
Turn Off Phone. Plug Your Charger Into The Wall. Plug The Phone Into The Charger. Let The Charger Turn On The Phone Don't Manually Power On. It Should Bring Up The CWM Screen. If It Doesn't After 5 Minutes, It's In Need Of An SBF.
if you can't get it into recovery, you need to sbf, then re root, and bootstrap. then you can restore your nandroid. had to do that twice with my OG.
I was able to fix the bootloop with a battery pull then doing a fast boot and selecting restore. It did not go back into 2.2.2 instead I was still with gingerbread and still rooted. Then I tried installing the rom again and this time it.worked.
Sometimes when it bootloops after installing eclipse if you pull the battery and then after putting it back boot into regular recovery ( hold power and vol down then cycle to it with vol down button) and do a data wipe everything may come up, new I.stall and all. I do see you have it fixed but if it ever happens again (hold it will) then try this first, it has worked for me more than once.
Im curious as to how long u were in a bootloop. As it took my phone quite some time to load past the boot screen after new eclipse for first boot. Patience before people just go pulling batteries.
ashclepdia said:
Im curious as to how long u were in a bootloop. As it took my phone quite some time to load past the boot screen after new eclipse for first boot. Patience before people just go pulling batteries.
Click to expand...
Click to collapse
True! It took a long time for me as well. Only pulled battery after I got the DROID eye and it kept starting over there.
Anotha'newb said:
True! It took a long time for me as well. Only pulled battery after I got the DROID eye and it kept starting over there.
Click to expand...
Click to collapse
First boots after flashing always take a while whilst the os builds cache etc.
Sent from my DROID X2 using Tapatalk
Never thought I will write about helping, but I do it.
I got photon which is not working well with pudding.
1. I can't flash normally 154 firmware. I get stuck on "Switching device to BP pass through mode" and I get black screen in the phone, pulling battery doesn't help somtimes, sometimes helps. I didn't get when it makes sense and phone boots.
2. Same message I get when I flash pudding. Same black screen. However pudding flashes normally, I can unlock bootloader. But I get another ****! When I choose reboot device or shutdown in CWM, in CM7 or CM9, I get black screen of death again. 5-20 battery repulling helps to boot phone again.
3. After flashing stock 198_7, with stock bootloader, I never have troubles with booting phone and there is no death screen on reboot/power off.
4. if I flash no pudding, i have no black screens.
5. If the phone was dead in black after reboot, and I don't pull the battery out, it'll use (still) battery and after night it may go from 100% to 0%.
6. Changing the battery didn't help.
Please help somebody!
are you factory resetting before flashing the sbf's if you dont they have a tendency to screw up also which rsd are you using?
spleef said:
are you factory resetting before flashing the sbf's if you dont they have a tendency to screw up also which rsd are you using?
Click to expand...
Click to collapse
Yes, factory reset. Tried rsd 5.3.1,, 5.5,5.6
Sent from my MB855 using xda premium
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Failed to boot, sounds like hardware failure
but you can try ezSBF, link in my list, might work.
sd_shadow's [Collection] of Links for Droid X2
Sent from my Clear using xda premium
vernon428 said:
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Click to expand...
Click to collapse
im not completely sure why you sbf'd after rooting the first time? no need for that. i would read up a bit more if you do get it working, watch tomsgt123 's videos on youtube so you know what youre doing. and you used the Gapps for cm10.1 not our version. that is why keyboard didnt work. read read read.
after reading abain, i guess you were on 2.3.5. and thats why you sbf'd. but rooting was not needed before sbf. hope you have better luck next time .
flash will fail if battery is too low, should be a low battery error though, but maybe not every time.
if it is low battery, you will need a charged battery or a tbh programing adapter
link to TBH adapter and dx2 external charger in my list
Sent from my XT862 using xda premium
Lorenzo VonMatterhorn said:
im not completely sure why you sbf'd after rooting the first time? no need for that. i would read up a bit more if you do get it working, watch tomsgt123 's videos on youtube so you know what youre doing. and you used the Gapps for cm10.1 not our version. that is why keyboard didnt work. read read read.
after reading abain, i guess you were on 2.3.5. and thats why you sbf'd. but rooting was not needed before sbf. hope you have better luck next time .
Click to expand...
Click to collapse
Do you have any advice on where I should go from here then? My phone is basically a useless hunk of technology until i can get it to boot back into cyanogen 10, or sbf it back to an android operating system. The RSD mode always fails when I try to normally sfd, but i have not tried EZ sbf yet..... any other suggestions?
vernon428 said:
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Click to expand...
Click to collapse
mine did the fail to boot thing back in september, i have to get a new x2. Try using a different computer, good luck
vernon428 said:
Do you have any advice on where I should go from here then? My phone is basically a useless hunk of technology until i can get it to boot back into cyanogen 10, or sbf it back to an android operating system. The RSD mode always fails when I try to normally sfd, but i have not tried EZ sbf yet..... any other suggestions?
Click to expand...
Click to collapse
With it powered off, hold power and volume up . See if you can get it into rsd mode . If so, sbf from there . Hope it works .
Lorenzo VonMatterhorn said:
With it powered off, hold power and volume up . See if you can get it into rsd mode . If so, sbf from there . Hope it works .
Click to expand...
Click to collapse
I can get into RSD mode, and the phone seems to SBF okay, until the SBF on the computer displays "failed", and the phone displays an error message. I am also using a fully charged battery during the whole process (my friend has the same phone so i swap batteries out with him to charge).
vernon428 said:
I can get into RSD mode, and the phone seems to SBF okay, until the SBF on the computer displays "failed", and the phone displays an error message. I am also using a fully charged battery during the whole process (my friend has the same phone so i swap batteries out with him to charge).
Click to expand...
Click to collapse
and you tried EZsbf?
try ezSBF
if you can't get it to work, you can go back, try using rsd lite, and look for Driver issues
I rooted my phone without any trouble for months, and its been working just fine, until now! Then, I had to do a factory reset. The normal procedure, SETTINGS> PRIVACY> factory reset. The phone then never got past the boot logo. It starts to load, and just gets stuck at the Samsung logo, and nothing else. there's two lights glowing from the capacitive buttons, and that's all. I'm on 4.1.2 JB stock rom. Later, I tried to enter recovery mode, and did a wipe, and cleaned cache partition also. AND, the phone just sprung to life, the whole first time set up thing. I started filling in stuff and the phone just shut down again, and if I tried to reboot again, it doesn't get past boot logo. But if I wipe n do it, it happens but shuts down immediately Please help!!
Sent from my GT-I9003 using xda app-developers app
Boot into download mode, get a stock rom from Samfirmware, flash it with Odin (How ? Thread stickied near top of Q&A).