Related
My brother tried to SBF stock froyo rom over Liberty. When the battery went dead he brought the phone to me. Changed batteries and SBF to the stock froyo rom he used. Phone is caught in boot loop. Holding Home and powering on only brings up motorolla splash and proceeds to boot loop. I have tried flashing every SBF for this Verizon but it seems that the recovery was deleted when he tried to original install and the battery died. The roms SBF fine but start a boot loop. I have pulled the battery holding home+power but the droid will not go into the recovery. CWM also does not boot so I assume it was deleted when he did the first SBF. Wondering if there is a way to SBF the Recovery Partition since all I can get to is the bootloader. 30.04. Any suggestions?
Depending on the SBF you flashed, you should be able to hold home and power (from a completely powered off state) and get the android with the triangle.
From there you will have to either press search (Froyo) or both volume buttons (Gingerbread).
Sent from my Transformer TF101 using XDA App
infazzdar said:
Depending on the SBF you flashed, you should be able to hold home and power (from a completely powered off state) and get the android with the triangle.
From there you will have to either press search (Froyo) or both volume buttons (Gingerbread).
Sent from my Transformer TF101 using XDA App
Click to expand...
Click to collapse
That is the problem. Regardless of which SBF I flash Home+Power just hangs Moto Logo and eventually starts the boot loop. It's almost as if the Recovery is not longer accessible.
Continue to hold both buttons even when it is on the Motorola logo.
Also, try reSBFing with .602 in Linux. For a nice clean start.
Sent from my Transformer TF101 using XDA App
Holding the buttons from a powered down phone it sits on M logo for about 8 seconds then starts the boot loop. This is with me Holding both Power and Home, Holding power and home and releasing power at logo. The only key on command that seems to work is the Bootloader.
Ill DL the 602 and Nix-SBF it and report back. Thanks.
InsanityLivz said:
Holding the buttons from a powered down phone it sits on M logo for about 8 seconds then starts the boot loop. This is with me Holding both Power and Home, Holding power and home and releasing power at logo. The only key on command that seems to work is the Bootloader.
Ill DL the 602 and Nix-SBF it and report back. Thanks.
Click to expand...
Click to collapse
Try doing the FULL .340 SBF and then when that finishes do the SYSTEM ONLY SBF. See if that does anything
Tried 604, 340 and 340 system. I SBF'd all form linux starting with 602. Rebooted holding home and power and after a few seconds it went straight into boot loop again. Same with the .304 and .304 overwritten with system files. I flashed 304 then immediately flashed the 304 system only. Still same symptoms. I ask my brother and he said the phone and all the buttons were working when he tried restoring it to factory so broken Home key is not the answer. I am fairly sure if there were another way to push a Wipe/reset to the phone it would stop looping and boot into any flavor firmware. You would think it would be easy to run a wipe/reset command from bootloader. Any more suggestions because i'm about to give up on this beast.
From what I can tell, every possible recovery option has been exhausted.
Sent from my Transformer TF101 using XDA App
infazzdar said:
From what I can tell, every possible recovery option has been exhausted.
Sent from my Transformer TF101 using XDA App
Click to expand...
Click to collapse
So it is Officially Bricked. Oh well.
They're almost never bricked. Did you try SBFing from the bootloader?
Boot into bootloader mode by holding down Volume Down, the Camera & the Power buttons.
Hey guys, I need your help. My phone battery died and the phone wouldn't boot past the M screen. I could get to bootloader but not recovery. So I SBFd. Same issue. Here is what I've done, I'm at my wits end.
1. Put phone in bootloader
2. Connected it, recognized by pc, used RSD 5.44 to flash .602
3. RSD says please manually power up the phone. Disconnect USB. (Also tried with usb still connected)
4. Battery pull, put it back in bootloader
5. Re connected, RSD says pass.
6. Pulled battery, tried to restart, same stuck at M screen issue.
7. Can't access recovery. Sometimes it will get there, but it won't let me access the menu.
8. Tried pressing both volume buttons a million times, nothing.
9. Once, menu in recovery flashed up, but disappeared immediately.
10. Put it back into bootloader and SBF'd again, with redownloaded file.
11. Repeat all of this 3x.
WHAT AM I DOING WRONG! HELP!
Make sure your battery is charged and SBF using the Linux method.
Sent from my Transformer TF101 using Tapatalk 2
So you think the SBF's aren't working for some reason? Should I still be using .602 or should I try .340?
Downloading the linux iso now...
Okay, sbf'd with linux method, same issue.
I can get to recovery by holding down the home and power buttons and then hitting the vol up/down buttons. It won't bring me to recovery unless i actually hit the volume buttons. Once in recovery, it doesn't respond to the volume buttons being pressed so I can't pull up the menu.
Any ideas?
What rom were you using when this happened?
Sent from my DROIDX using XDA
None! It was totally stock.
lunchbox2 said:
None! It was totally stock.
Click to expand...
Click to collapse
If you were on stock .621, you have to SBF to .621.
Sent from my Transformer TF101 using Tapatalk 2
It was stock .605, I had to SBF back in march.
I guess my issue now is this: I can sometimes get to the recovery screen, but the menu never appears. I've tried pressing the search button and hitting vol. up/down at the same time, and I haven't once gotten the menu to pop up so I can clear data.
Is there some way to wipe cache through adb using the bootloader?
I have tried at least 10 times with no results. I power down the device, hold both volume buttons and the power button, and nothing. I do get a vibrate after about 2 seconds, but nothing on the screen and then it vibrates every 6-7 seconds until I let go of the buttons. Kind of disappointed as I was all nice and comfortable on the couch, ready to use the Nexus 10 toolkit to do the all-in-one.
Anyone else experience this problem?
Sent from my SCH-I535 using Tapatalk HD
jmcharles said:
I have tried at least 10 times with no results. I power down the device, hold both volume buttons and the power button, and nothing. I do get a vibrate after about 2 seconds, but nothing on the screen and then it vibrates every 6-7 seconds until I let go of the buttons. Kind of disappointed as I was all nice and comfortable on the couch, ready to use the Nexus 10 toolkit to do the all-in-one.
Click to expand...
Click to collapse
Try releasing then power button (but hold the other two) when you feel the first vibration. I've found that holding the power button can make a continuous reboot happen.
Sent from my Galaxy Nexus using Tapatalk 2
Tried that, but no luck. I also went a different route and tried to do it using mskip's toolkit in original android development. After installing the drivers and choosing the options to boot into fastboot, the device vibrated once and nothing showed up on the screen. BUT...when I refreshed the main menu the toolkit recognized the device as in fastboot mode. Really weird happenings with this, and starting to be concerned that my device has some issues. What point is a Google device if I can't unlock or root it?!
Sent from my SCH-I535
I've had the best luck holding the vol up/down button down first, then while that's down, pressing and holding power until the fastboot menu comes up.
Well, I am at a complete loss. Is this cause for replacement?
Sent from my Nexus 10 using Tapatalk HD
Hold all three buttons at the same time and wait for the vibration and release. It should work.
Sent from my DROID RAZR HD using xda premium
Ok, so, I'm not sure what to make of the recent events. Bottom line, I was booting to fastboot mode, but the screen was just blank. I followed the instructions via the toolkit just by selecting the buttons and hoping it was making the correct selections in fastboot mode. Now unlocked, rooted, and a happy man! Still not sure why the fastboot menu would not show up though.
Sent from my SCH-I535 using Tapatalk HD
jmcharles said:
Ok, so, I'm not sure what to make of the recent events. Bottom line, I was booting to fastboot mode, but the screen was just blank. I followed the instructions via the toolkit just by selecting the buttons and hoping it was making the correct selections in fastboot mode. Now unlocked, rooted, and a happy man! Still not sure why the fastboot menu would not show up though.
Sent from my SCH-I535 using Tapatalk HD
Click to expand...
Click to collapse
I cant get the toolkit to recognize my tablet in fastboot mode. Is there a soluton to the black screen?
If the toolkit does not recognize the device in fastboot, then there's a good chance you didn't install the drivers correctly. Did you follow the directions correctly to get the toolkit to recognize the device?
Sent from my SCH-I535
jmcharles said:
If the toolkit does not recognize the device in fastboot, then there's a good chance you didn't install the drivers correctly. Did you follow the directions correctly to get the toolkit to recognize the device?
Sent from my SCH-I535
Click to expand...
Click to collapse
I got my device unlocked and the device did install the drivers. However, the problem was not that. But here's the thing, my N10 never showed me the fastboot menu. But connected to the PC it does show its connected. I never saw the screen that confirms "do you want to unlock the bootleader" (it goes completely black and vibrates every 5 seconds).
Workaround to unlock: For anyone with this problem, I just had to "guess" that menu (I think its clicking the vol button down once and then the power button). For me it bootlooped. so I pressed the Vol+ and power and in fastboot I booted to stock recovery, from there just wipe factory settings, and voila.
Weird tho that my fastboot screen was completely black
El Niche said:
I got my device unlocked and the device did install the drivers. However, the problem was not that. But here's the thing, my N10 never showed me the fastboot menu. But connected to the PC it does show its connected. I never saw the screen that confirms "do you want to unlock the bootleader" (it goes completely black and vibrates every 5 seconds).
Workaround to unlock: For anyone with this problem, I just had to "guess" that menu (I think its clicking the vol button down once and then the power button). For me it bootlooped. so I pressed the Vol+ and power and in fastboot I booted to stock recovery, from there just wipe factory settings, and voila.
Weird tho that my fastboot screen was completely black
Click to expand...
Click to collapse
This is exactly how I had to do it. It's a 50/50 shot, since I think the options are yes or no. Apparently the problem is a little more common, as evidenced by this thread I started in Android General, http://forum.xda-developers.com/showthread.php?t=2018777
Sent from my Nexus 10 using Tapatalk HD
I am stuck at the flashing X....with the toolkit. Kinda at a lose right now.
mike02vr6 said:
I am stuck at the flashing X....with the toolkit. Kinda at a lose right now.
Click to expand...
Click to collapse
Reboot into boot loader, choose recovery, press all three buttons at top at same time if you don't have options to select, then factory reset. This will solve your boot loop.
Sent from my SCH-I605 using Tapatalk 2
The post above is correct. Same thing happened to me. Just factory reset and you should be good to go
Sent from my Nexus 10 using xda app-developers app
I accidentally,... . unknowingly wiped the RED "system" button in Safestrap 3.12 on my Droid RAZR M today. (I was suppose to be wiping the cash and dalvik, but missed) I'm a retard I know. :crying:
Now I cant get into AP Fastboot to restore the phone from this hard brick!
When I press the power button along with the volume buttons, the only thing that happens is the red Motorola 'M" appears for a few seconds then the safe strap screen appears with the little sad robot, but that's it no AP Fastboot. Pressing the on screen buttons to enter Safestrap Recover do not respond. Oh boy I'm afraid I really did it this time. Its on the charger but i don't know if its even charging with out as OS?
Battery power was at 60% before i bricked it (i think). RSD Lite or my PC for that matter don't even see the phone when its plugged in.
Can this be saved? Or do I need to take a trip down to the Verizon Wireless store?
Droid RAZR M
4.1.2 OTA
Rooted
Locked Bootloader
Safestrap 3.12
Partitioned 64GB SD card utilizing Linked2SD
You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2
sloosecannon said:
You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Really? Well I hope your right. It gives me some hope. lol So do you have any idea of what alternative key combo i might have to use? Thank you for the reply.
Try holding power & volume down until the screen flickers then hold power and both volume buttons. You gotta be quick
If your boot loader is locked you won't be able to fast boot back until the new fast boot files come out though if your on 4.1.2
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:
sloosecannon said:
You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! You were right! was able to get into AP Fastboot with a different button combo like u said. :victory:
shane1 said:
Try holding power & volume down until the screen flickers then hold power and both volume buttons. You gotta be quick
If your boot loader is locked you won't be able to fast boot back until the new fast boot files come out though if your on 4.1.2
Click to expand...
Click to collapse
Shane you were right on the money brother!!! Thank you so very much. It worked perfectly. I'm up and running again.
much respect
bigrob1015 said:
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:
Click to expand...
Click to collapse
It worked! I utilized the NEWER version of Mat's utility and it did it!!! Woo Hoo!! Thank you so very much. Thank you all for all the speedy help.
SARM1084 said:
Shane you were right on the money brother!!! Thank you so very much. It worked perfectly. I'm up and running again.
much respect
Click to expand...
Click to collapse
hey no prob! i try to help as much as i can !
bigrob1015 said:
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:
Click to expand...
Click to collapse
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min
Halp
This thread saved my life, then killed me. The suggestion about the different keys was spot on, i got into fast boot mode, then ran that utility. It totally failed me, I must have killed my phone pretty dead, and now there are no more key combos (the suggested one worked at first but now its just making the screen go blank) to try to get back into fast boot to try again. any more suggestions? on the up side verizon just pushed that update so i figure i can blame that to attempt an exchange
Did you take the update before using that utility? If you did, which version did you use? If you were already updated, then you needed to run 1.20. If you ran the wrong utility, that will cause issues. Now, since you can't boot, it sounds like your battery is dead. When you get to the blank screen, plug it in and leave it to charge for a while.
I'm no expert by any means but I'll try to help as best i can. If not me I'm confident someone else will. Now, I apologize because I didn't understand your original post.
Could you elaborate a little more please?
1. What were you trying to do with your phone prior to things going wrong, if they went wrong at all.
2. you mentioned AP Fastboot. So IM going to assume that at least you can access it. (not the same problem that I was having) that's a good thing! lol
3. Are you utilizing a utility like the one by Matt? Or are you doing something else? Like flashing firmware etc.
4. What were you in Fastboot for? What were your intentions?
I hope this doesn't come over a condescending. Just trying to get a Clearer understand of your issue so we can help.
Sent from my XT907 using xda app-developers app
Sorry double post
PartyOnINSANE said:
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min
Click to expand...
Click to collapse
Look at my previous post
Sent from my XT907 using xda app-developers app
Sorry, my post musnt have updated. As you can see I managed to fix my problem. If there's any issues in the future for anyone I will be sure to advise as best I can.
Sent from my XT907 using xda app-developers app
PartyOnINSANE said:
Sorry, my post musnt have updated. As you can see I managed to fix my problem. If there's any issues in the future for anyone I will be sure to advise as best I can.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No problems brother. Glad to see your up and running.
Sent from my XT907 using xda app-developers app
Stuck in a Boot Loop
PartyOnINSANE said:
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min
Click to expand...
Click to collapse
Could you help me please?
I changed 2 lines in my build.prop file so i could see if I could get touchless control.
After I changed it, I restarted my phone. Now it is stuck in the Red M Boot, and it stays there, dosent black screen, dosent boot. I can get to the boot selection menu, but i cant choose anything, they all end up at the Red M. I Read that I can fix it in AP Fastboot, but I can get there. Also if i force it off (with power button and volume button) It just goes back to the Red M.
Everything I do ends up at the Red M
Help fast please, its my only phone, and I just got rid of my house phone
I have a
Droid Razr M
Rooted, no custom Roms or Recovery.
Changed my build.prop from XT907 to XT1087
Changed My Boot Animation to R2D2
A: 4.1.2
8gb Sd card on it.
gjhkl said:
Could you help me please?
I changed 2 lines in my build.prop file so i could see if I could get touchless control.
After I changed it, I restarted my phone. Now it is stuck in the Red M Boot, and it stays there, dosent black screen, dosent boot. I can get to the boot selection menu, but i cant choose anything, they all end up at the Red M. I Read that I can fix it in AP Fastboot, but I can get there. Also if i force it off (with power button and volume button) It just goes back to the Red M.
Everything I do ends up at the Red M
Help fast please, its my only phone, and I just got rid of my house phone
I have a
Droid Razr M
Rooted, no custom Roms or Recovery.
Changed my build.prop from XT907 to XT1087
Changed My Boot Animation to R2D2
A: 4.1.2
8gb Sd card on it.
Click to expand...
Click to collapse
Holding the combination of buttons will only cause it to reboot, every time. Holding the power button down will make it shutdown. With that being said, what was your battery like before you started all of this? If it's below 50%, you're going to have a hard time. Shut the phone down and charge the battery ovenight, prior to attempting to fastboot.
If your battery is good, then you can fastboot. Hold all three buttons down, until you get the phone to power off. As soon as power goes off, you'll see a quick line flash at the top of the screen. As soon as you see this flash, quickly let go of the power button and then re-press it. If you got it right, you'll go into the fastboot menu. If you got it wrong, it will attempt to reboot. If it reboots, just try the button combo again. Once you get into the fastboot menu, use the vol- key to get to the option you need, and then hit the vol+ to choose that option.
RikRong said:
Holding the combination of buttons will only cause it to reboot, every time. Holding the power button down will make it shutdown. With that being said, what was your battery like before you started all of this? If it's below 50%, you're going to have a hard time. Shut the phone down and charge the battery ovenight, prior to attempting to fastboot.
If your battery is good, then you can fastboot. Hold all three buttons down, until you get the phone to power off. As soon as power goes off, you'll see a quick line flash at the top of the screen. As soon as you see this flash, quickly let go of the power button and then re-press it. If you got it right, you'll go into the fastboot menu. If you got it wrong, it will attempt to reboot. If it reboots, just try the button combo again. Once you get into the fastboot menu, use the vol- key to get to the option you need, and then hit the vol+ to choose that option.
Click to expand...
Click to collapse
I have done your steps and I get the menu up, but when I try to scroll down with the volume down button, it doesn't move. It just stays on "normal powerup". How can I fix this?
So I don't have my computer with me just an iPhone so bear with me please.
I had CWM on my G2 and in a sleepless haze flashed me some PA 4.0 beta.
Now the phone boots up but right after the I get two notifications about galley and camera crashing it reboots.
I try to get the phone into recovery via the phone menu but it won't work just let's me turn it off.
What can I do without a computer at the moment?
illyfilly said:
So I don't have my computer with me just an iPhone so bear with me please.
I had CWM on my G2 and in a sleepless haze flashed me some PA 4.0 beta.
Now the phone boots up but right after the I get two notifications about galley and camera crashing it reboots.
I try to get the phone into recovery via the phone menu but it won't work just let's me turn it off.
What can I do without a computer at the moment?
Click to expand...
Click to collapse
Manually boot into recovery. Power the device off and hold the power+volume up releasing the volume up key when you see the LG logo, then press it again while still holding power button. Once you see a white screen talking about factory resetting the phone hit the power button to confirm and you will enter recovery.
If that doesn't work Google the exact instructions "how to manually boot into recovery LG G2, xda"
And don't forget to plug off the USB cable
Sent from my LG-D802 using xda app-developers app
And flash correct gapps next time
Sent from my LG-G2 using Tapatalk