Hi all. Today I just found THIS. It is apparently many months old... however it's new news to me! Hashcode has developed a bootstrap for the Droid 3 that allows you to boot into CWM from "BP Tools" in the boot selection menu (power + both volume buttons).
It warns you to not use it on ANY other phone because of key filesystem differences. So unless you want to probably flash the fxz, then don't install it. (READ: you shouldn't install it, but you'll get a big thanks if you do install it )
@lfaber06/jimbridgman: do you guys think this can be ported to the A2?
cogeary said:
Hi all. Today I just found THIS. It is apparently many months old... however it's new news to me! Hashcode has developed a bootstrap for the Droid 3 that allows you to boot into CWM from "BP Tools" in the boot selection menu (power + both volume buttons).
It warns you to not use it on ANY other phone because of key filesystem differences. So unless you want to probably flash the fxz, then don't install it. (READ: you shouldn't install it, but you'll get a big thanks if you do install it )
@lfaber06/jimbridgman: do you guys think this can be ported to the A2?
Click to expand...
Click to collapse
No need, use the one from the razr on boot from j.y.daddy..... It has been posted and used in here for quite some time... I use it and I love it.
Here is the link to the post, to get said boot script:
http://forum.xda-developers.com/showthread.php?t=1385283
You still need the Atrix 2 bootstrap, that is here:
http://forum.xda-developers.com/showthread.php?t=1346977
jimbridgman said:
No need, use the one from the razr on boot from j.y.daddy..... It has been posted and used in here for quite some time... I use it and I love it.
Here is the link to the post, to get said boot script:
http://forum.xda-developers.com/showthread.php?t=1385283
You still need the Atrix 2 bootstrap, that is here:
http://forum.xda-developers.com/showthread.php?t=1346977
Click to expand...
Click to collapse
I know, I have used the Razr Recover on Boot many times before.... it's just really annoying to press the "reboot" button and wait through the red "M" again in order to boot up.
The reason that this is nice is because it makes you normally boot up like it normally does, and then you can press+hold Power/Volume to get to the boot menu to choose "BP Tools."
cogeary said:
I know, I have used the Razr Recover on Boot many times before.... it's just really annoying to press the "reboot" button and wait through the red "M" again in order to boot up.
The reason that this is nice is because it makes you normally boot up like it normally does, and then you can press+hold Power/Volume to get to the boot menu to choose "BP Tools."
Click to expand...
Click to collapse
Are u talking about it being in your power down menu?
Deliberate said:
Are u talking about it being in your power down menu?
Click to expand...
Click to collapse
Yes. What we have now is something that hijacks the boot every time you boot up, and if you want to keep booting you press a button. What this does is make it so that we can boot into CWM from holding power and the volume buttons and then scrolling down to "BP Tools".
However @jim I understand that we have a completely functional CWM on boot working now. It would just be really convenient to have this. I was just pointing it out for if anyone smart enough wanted to port it (i.e. nitroglycerin33... where did he go anyways? I thought he said he would continue to develop stuff for the A2?).
cogeary said:
Yes. What we have now is something that hijacks the boot every time you boot up, and if you want to keep booting you press a button. What this does is make it so that we can boot into CWM from holding power and the volume buttons and then scrolling down to "BP Tools".
However @jim I understand that we have a completely functional CWM on boot working now. It would just be really convenient to have this. I was just pointing it out for if anyone smart enough wanted to port it (i.e. nitroglycerin33... where did he go anyways? I thought he said he would continue to develop stuff for the A2?).
Click to expand...
Click to collapse
I will talk to hashcode.... that is where safestrap came from. Right now though, since we have a working way to get to cwm on boot, this is a low priority for us.
I will pull it apart and see if it is possible. But since we are having some issues with hardware buttons in 2.3.6, I am not 100% sure right now.
Jim
Sent from my MB865 using xda premium
to bad with this script it seems like holding down volume and power for 5 secs doesn't work on our phones
iB4STiD said:
to bad with this script it seems like holding down volume and power for 5 secs doesn't work on our phones
Click to expand...
Click to collapse
It absolutely does, that's how we get into fastboot mode... to get to the boot selection menu hold both volume buttons and power button. To go straight to fastboot hold power and volume down for a couple seconds then let go.
There are a couple other cool combinations that will freeze the bootloader and cause you to pull the batter to turn your phone on
Related
So when I was trying to FXZ to 2.3.5 (from 2.3.6) to install ICS, my flash kept failing because I hadn't patched the FXZ with the necessary files.
Well I am up and running on ICS now comfortably, but on EVERY reboot my phone automatically boots into fastboot. Just like CWM on boot. I get the fast boot screen, and in the corner it says "Flash failure." But all I do is hit the power button to power down, hold down both volume keys and hold the power button. This brings me to the boot menu, and I merely select boot normally and everything starts fine.
At first this was an annoyance, now I'm used to it. And it got me thinking...
Could this be useful to us guys? Could this somehow save us in the future if we could figure out why my phone is doing it? Is it good to automatically boot into fastboot?
I'll be happy to PM my system.img to someone if they can tell me how to pull it without hardbricking my phone lol.
Thoughts? Devs?
-Fall
Fall of Enosis said:
So when I was trying to FXZ to 2.3.5 (from 2.3.6) to install ICS, my flash kept failing because I hadn't patched the FXZ with the necessary files.
Well I am up and running on ICS now comfortably, but on EVERY reboot my phone automatically boots into fastboot. Just like CWM on boot. I get the fast boot screen, and in the corner it says "Flash failure." But all I do is hit the power button to power down, hold down both volume keys and hold the power button. This brings me to the boot menu, and I merely select boot normally and everything starts fine.
At first this was an annoyance, now I'm used to it. And it got me thinking...
Could this be useful to us guys? Could this somehow save us in the future if we could figure out why my phone is doing it? Is it good to automatically boot into fastboot?
I'll be happy to PM my system.img to someone if they can tell me how to pull it without hardbricking my phone lol.
Thoughts? Devs?
-Fall
Click to expand...
Click to collapse
Well the reason is because some part of the fxz actually did not flash correctly... there is a check in the bootloader, and it will throw you into fastboot every time, if any of those checks don't pass. The ONLY way out is to use RSDlite and do the fxz again... but since you are on ICS you don't have much of chance to try it now... just wait and we will see if we can get it all fixed up for fxz again... all of us devs are working togther on this and bunch of other things now.
Perfect. Thanks Jim. As always. I just wasn't sure if it would help or not.
your work and all the other devs work is appreciated man.
Sent from my MB865 using xda premium
Hey people my first post so you can call me whatever you want
Here is the thing:
I rooted the phone, installed a custom ROM and such, on the process I guess I installed this Clockwork Mod Recovery v5.8.3.1.
Well I wanted to change the ROM so I downloaded the new one (lastest trickdroid) and follow the steps, BUT!, when trying to acces the fastboot thing on that menu that can't remeber the name of, I jsut can't get into it.
When I tart the phone pressing volume down + power, instead of going to that menu it goes to clockwork mod. I was suposed to "Flash the stock boot.img from the ROM with fastboot", but well I dont know what I did or wahtever, I can't aces that menu.
What should I do?
bobyd said:
Hey people my first post so you can call me whatever you want
Here is the thing:
I rooted the phone, installed a custom ROM and such, on the process I guess I installed this Clockwork Mod Recovery v5.8.3.1.
Well I wanted to change the ROM so I downloaded the new one (lastest trickdroid) and follow the steps, BUT!, when trying to acces the fastboot thing on that menu that can't remeber the name of, I jsut can't get into it.
When I tart the phone pressing volume down + power, instead of going to that menu it goes to clockwork mod. I was suposed to "Flash the stock boot.img from the ROM with fastboot", but well I dont know what I did or wahtever, I can't aces that menu.
What should I do?
Click to expand...
Click to collapse
I am having what seems like the same issue with my phone. Just posted a thread not too long ago asking for help. One person (a SR. Member) informed me to try to restore using a NANDROID backup (which I dont have). Going off of his advice, if you have the backup, try that. If not, we both seem to have the same problem. Good luck with your issue, I will be checking both our threads for solutions from now on!
fragkiller1 said:
I am having what seems like the same issue with my phone. Just posted a thread not too long ago asking for help. One person (a SR. Member) informed me to try to restore using a NANDROID backup (which I dont have). Going off of his advice, if you have the backup, try that. If not, we both seem to have the same problem. Good luck with your issue, I will be checking both our threads for solutions from now on!
Click to expand...
Click to collapse
Well, it seems we have the same problem then, we could make a club or something.
Extra Help (Maybe)
Hey again, I found some useful information that allowed me to get into my bootloader! If you are still stuck in CWM, use the volume down button to go down to the "advanced" button at the bottom of the list. Since this is a button that leads to another list and not a direct action, you can hold down the power button when highlighted over it and turn the phone off. From there, just hold Volume Down and Power as you would normally do to boot into the bootloader. Hope this helps since it worked for me!
So:
-Navigate to "advanced" (Just highlight over it)
-Hold power button for 10-15 seconds
-Phone should power off
-Volume Down + Power to boot into Bootloader
-Profit?? (Just Kidding )
Again, hope I could be of some assistance!
fragkiller1 said:
snip!
Click to expand...
Click to collapse
well I dont know what I did. I just turned the phone off normally. Then did the power + b down, held it for about 6 seconds, relesead the power then the volume and BOM, bootlader appeared, hmmm okay I guess
Have a look at fragkiller1 thread for fixing your issue.
well now I can't even get into CWM sigh
A brief flash of a screen appears now while booting it, but it just skips to the actual OS. I have the fast boot disabled ohh man what do now? DId I mess up something?
fragkiller1 said:
Hey again, I found some useful information that allowed me to get into my bootloader! If you are still stuck in CWM, use the volume down button to go down to the "advanced" button at the bottom of the list. Since this is a button that leads to another list and not a direct action, you can hold down the power button when highlighted over it and turn the phone off. From there, just hold Volume Down and Power as you would normally do to boot into the bootloader. Hope this helps since it worked for me!
So:
-Navigate to "advanced" (Just highlight over it)
-Hold power button for 10-15 seconds
-Phone should power off
-Volume Down + Power to boot into Bootloader
-Profit?? (Just Kidding )
Again, hope I could be of some assistance!
Click to expand...
Click to collapse
I did what you told me but when highlighting advanced and pressing the power button it enters the menu advanced, then the phone just noramll reboots and the OS loads.
I would have edited the post but I can't.
bobyd said:
I did what you told me but when highlighting advanced and pressing the power button it enters the menu advanced, then the phone just noramll reboots and the OS loads.
I would have edited the post but I can't.
Click to expand...
Click to collapse
Try holding Vol- when turning it off and keep hold of it but quickly let go of power when it turns off.
Darknites said:
Try holding Vol- when turning it off and keep hold of it but quickly let go of power when it turns off.
Click to expand...
Click to collapse
thanks it worked perfectly. I thought it only worked powering off and turining it on and holding volume down.
edit: sigh now I have another problem, after using fastboot usb with the Boot_Flash_Script from trickdroid, the phone is stuck at the the screen that says"this build is for development pourpuses only..." and it won't go further
edit2: I think I falshed a ROM for VilleC2 when I have a Ville, is there a way to fix this? the phone now is stuck at loading the screen with red words
bobyd said:
thanks it worked perfectly. I thought it only worked powering off and turining it on and holding volume down.
edit: sigh now I have another problem, after using fastboot usb with the Boot_Flash_Script from trickdroid, the phone is stuck at the the screen that says"this build is for development pourpuses only..." and it won't go further
edit2: I think I falshed a ROM for VilleC2 when I have a Ville, is there a way to fix this? the phone now is stuck at loading the screen with red words
Click to expand...
Click to collapse
Ya, make sure you got the right rom and get yourself back into the bootloader and you should see recovery there then do a full wipe and flash the rom and also if you feel you might of flashed the wrong boot.img reflash it to make sure.
So it's over, all solved.
I tried to install a new ROM but CWM got me an error mounting the SD, then I installed another recovery (TWR) and installed the new ROM (viper one s) flashed the boot.img and now everthing works wonders, for now.
Thanks a lot Darknites for trying to help me I really appreaciate that
bobyd said:
So it's over, all solved.
I tried to install a new ROM but CWM got me an error mounting the SD, then I installed another recovery (TWR) and installed the new ROM (viper one s) flashed the boot.img and now everthing works wonders, for now.
Thanks a lot Darknites for trying to help me I really appreaciate that
Click to expand...
Click to collapse
Np dude glad you got it sorted but ya TWRP is way better for the sd mount and if you have 1.09 or lower Hboot it can also flash boot.img.
Got a buddy that has a S3 and he ODIN back to stock and hes rooted but everytime he goes to flash CWM recovery it does the process like normal but when he goes to recovery, its just the stock recovery
any help?
http://forum.xda-developers.com/showthread.php?t=2046439
Make sure you have USB debugging on and allow unknown applications before trying to flash the recovery. Just a simple check that I have forgotten in the past myself lol
Sent from my SCH-I535 using xda premium
yo
Jason Roach said:
Make sure you have USB debugging on and allow unknown applications before trying to flash the recovery. Just a simple check that I have forgotten in the past myself lol
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
what he said. Also, some of the videos were a bit confusing, but the more reading I did, I found that it may be important to wait for a "Pass" green sign to show up at the end of each ODIN step, THEN wait 10-15 minutes after you get the pass before moving on to the next step. I had messed up one device once, and did these extra steps (debug mode and waiting for pass patiently) and was successful the second time around.
olufadi1 said:
what he said. Also, some of the videos were a bit confusing, but the more reading I did, I found that it may be important to wait for a "Pass" green sign to show up at the end of each ODIN step, THEN wait 10-15 minutes after you get the pass before moving on to the next step. I had messed up one device once, and did these extra steps (debug mode and waiting for pass patiently) and was successful the second time around.
Click to expand...
Click to collapse
I always unplugged the phone and restart Odin for each flash or Odin get stuck or something
Sent from my SCH-I535 using xda premium
steve0mac,
I'm embarrassed to admit what mistake I made... but maybe it will help you and someone else. After I flashed my choice of custom recovery in ODIN and got a “Pass,” I pulled the battery/usb, etc... and then went to boot back into the custom recovery…
Here’s the silly mistake I made -- I would continue to hold in the power button along with the volume up and home button... thinking that I needed to have all of them pressed in until the custom recovery booted up. I finally figured out that you have to let go of all the buttons after you see the Samsung logo briefly appear on the screen. (Alternately, you can also just let go of the power button after the Samsung logo flashes quickly across the screen and then continue to hold down the volume up and home buttons until the custom recovery boots up--- this isn't necessary, but it doesn't seem to hurt anything).
mattnmag said:
steve0mac,
I'm embarrassed to admit what mistake I made... but maybe it will help you and someone else. After I flashed my choice of custom recovery in ODIN and got a “Pass,” I pulled the battery/usb, etc... and then went to boot back into the custom recovery…
Here’s the silly mistake I made -- I would continue to hold in the power button along with the volume up and home button... thinking that I needed to have all of them pressed in until the custom recovery booted up. I finally figured out that you have to let go of all the buttons after you see the Samsung logo briefly appear on the screen. (Alternately, you can also just let go of the power button after the Samsung logo flashes quickly across the screen and then continue to hold down the volume up and home buttons until the custom recovery boots up--- this isn't necessary, but it doesn't seem to hurt anything).
Click to expand...
Click to collapse
That is a common mistake and is posted several times in the root thread. Hold too long and it skips recovery. :laugh:
Running CM 10.1, 06/08 Nightly
I did search the threads and google, but could not find any posts about a phone that works normally except for download and recovery.
Problems:
1. Can't boot into recovery (via apps, power menu, or manually). It gets to the boot logo, and then blank screen and resets. It will keep resetting trying to go into recovery (a battery pull will put it back to normal).
2. Can't stay in download mode. When I put the phone in download mode, it turns off after a couple seconds. I can't ODIN it if it keeps turning off.
3. Power button doesn't work properly (sometimes it works, most of the times it doesn't). Example: I press the power button to close the screen. No response. A few minutes later I might press it, and the screen will close, but come back on and this time with power menu. I took out the button to verify that it wasn't stuck, and tried pressing the actual button inside the phone with the stick. I can feel it click, but it still has the same problems. Pretty sure it's not a stuck button.
What's working:
-Everything else. If I let the phone boot normally, it loads perfectly fine and into cyanogenmod. No issues with voice/data, any apps, or instability. No battery issue. No lag. No crashes. The only issue is with the power button, and my inability to boot into recovery or go into download mode.
History:
-I was experiencing a random reboot problem (and power button issue) from an earlier nightly, and I waited a couple months for a more stable version. The CWM recovery for some reason only worked sometimes. When I did get it to work, I flashed RC5 (format and wipe data, dalvik, cache, factory reset, etc.), which fixed my reboot problem, but not my power button.
-I came across this thread: at plus.google(.com)104277415207525128383/posts/iAVpVPYqMtM and updated the radio, even though the RC5 fixed my random reboot.
-I did try flashing CWM, TWRP, and Stock recoveries (the latest ones, and from CWM/EZ recovery apps), but have not tried CWM Touch. It doesn't seem to matter, it won't boot into recovery.
Perceived Solution:
-I have a plan with Best Buy - I am considering smashing the phone and getting it replaced with a refurb, but would like to avoid that if possible.
Anyone have any ideas? I am okay with the phone as is, but I would like to be able to update CM or to another ROM in the future
Thanks for helping me out!
Can you get into recovey just long enough to do a system wipe?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
DarkMenace said:
Can you get into recovey just long enough to do a system wipe?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
Thanks for responding; It doesn't boot into recovery at all. Right after holding Vol. Up, Menu + Power, I get the screen with the small text in the corner, so you know it's going to enter recovery. Then the logo appears, except after that the phone either hangs with a blank screen, shuts off, or resets itself.
I think something got corrupted, but I'm not sure how to find out what, or what steps I could take to fix it.
phospholipid1 said:
Thanks for responding; It doesn't boot into recovery at all. Right after holding Vol. Up, Menu + Power, I get the screen with the small text in the corner, so you know it's going to enter recovery. Then the logo appears, except after that the phone either hangs with a blank screen, shuts off, or resets itself.
I think something got corrupted, but I'm not sure how to find out what, or what steps I could take to fix it.
Click to expand...
Click to collapse
Unfortunately if you can't get into the recovery mode or the Odin mode then you would need to replace the phone. It's bricked.
DarkMenace said:
Unfortunately if you can't get into the recovery mode or the Odin mode then you would need to replace the phone. It's bricked.
Click to expand...
Click to collapse
Thanks for the response.
Yeah, that's what I thought. I've never really heard or seen someone with a "functionally bricked" phone, so I'm not sure what to do.
Before I go ahead and smash it for the insurance replacement, I want to see if anyone else has any ideas..
Like I said, the phone boots normally just fine. Is there some kind of app that can flash files? Or maybe some commands I can enter in the terminal emulator?
phospholipid1 said:
Thanks for the response.
Yeah, that's what I thought. I've never really heard or seen someone with a "functionally bricked" phone, so I'm not sure what to do.
Before I go ahead and smash it for the insurance replacement, I want to see if anyone else has any ideas..
Like I said, the phone boots normally just fine. Is there some kind of app that can flash files? Or maybe some commands I can enter in the terminal emulator?
Click to expand...
Click to collapse
Have you tried Odin Mobile Pro? I've never used it myself, but I've heard a lot of good things about from some friends.
It sounds to me like a faulty power button, it isn't hardbricked because your phone is able to boot into recovery and download mode. But If for some reason your power button is stuck in the on position, it will skip booting into recovery and eventually boot out of download mode. Just because the power button physically moves and clicks doesn't mean it can't get stuck, there's obviously something funny going on with it that isn't rom/kernel regulated.
You can try terminal emulator to see if it will work, but I honestly wouldn't do anything in any menu because your phone has the potential to reboot during a process and destroy your phone. Commands are:
su
reboot recovery
su
reboot download
If it's a power button issue, best buy should replace it anyways, you shouldn't have to smash it. Samsung will also fix it under your manufacturer warranty despite it being rooted.
Sent from my SCH-I535 using Tapatalk 2
Thanks for responding, guys
rellomar said:
Have you tried Odin Mobile Pro? I've never used it myself, but I've heard a lot of good things about from some friends.
Click to expand...
Click to collapse
Yes, I did. This brings me back into download mode, at which the phone just turns off.
BadUsername said:
It sounds to me like a faulty power button, it isn't hardbricked because your phone is able to boot into recovery and download mode. But If for some reason your power button is stuck in the on position, it will skip booting into recovery and eventually boot out of download mode. Just because the power button physically moves and clicks doesn't mean it can't get stuck, there's obviously something funny going on with it that isn't rom/kernel regulated.
You can try terminal emulator to see if it will work, but I honestly wouldn't do anything in any menu because your phone has the potential to reboot during a process and destroy your phone. Commands are:
su
reboot recovery
su
reboot download
If it's a power button issue, best buy should replace it anyways, you shouldn't have to smash it. Samsung will also fix it under your manufacturer warranty despite it being rooted.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the commands; they ended up just shutting the phone off.
Yeah, I did ponder the idea that even though the power button "clicked," it might not necessarily be working. I google searched "galaxy s 3 broken power button" and there was a video with a description where the guy mentioned something about the circuit always being switched "on"
But his phone experienced different symptoms than mine (because the circuit was always switched on, the phone actually restarted itself while in normal operation. This hasn't happened to me).
Is there an app for me to definitely determine which buttons are being registered as they are pressed? Similar to programs that tell you what buttons you're pressing on your keyboard.
I would take it back to Best Buy, but I just don't want to give them any reason to say it was my own fault since I rooted and put a custom ROM on it.
Haha, I'll dunk it in salt water in favor of smashing it
Thanks again for your suggestions and ideas :cyclops:
I got this phone used. (Droid Razr HD) Not sure of its history. As far as I know it was all stock until today.
When I found out I could root and unlock the bootloader I did so. Then I wanted to go into recovery and make a backup (yea I know...did that backwards) I powered the device off...hit the volume rocker switch and the power button at the same time and it entered into the Boot Mode selection menu. I hit the volume down to move to the recovery option and then hit the volume up button to select recovery.
At this point the big red M & Dual Core Technology logo appears. Stays there for 1.5 minutes then disappears briefly, comes back on for 15 seconds and then boots the phone normally.
So....I downloaded and installed Rom Manager and had it flash the latest CMW Recovery, turned the phone off to access the newly flashed recovery and the phone again went to the big red M & Dual Core Technology logo set there for 1.5 minutes, disappeared briefly and then booted the phone normally.
So.....I downloaded the lasted CMW Recovery image and used ADB and Fastboot to flash the recovery. Same result. Cannot access the recovery.
So....I downloaded a Stock recovery image and used ADB and Fastboot to flash the stock recover. Same result....cannot access the recovery.
Can someone tell me what I am missing or what I am doing wrong? Or what I can do access recovery.? A rooted phone with an unlocked bootloader isn't much good if you can't access recovery.
Thanks for reading and for any advice you might be able to give.
Jeff
I believe when in the boot loader menu, you need to Volume down to your choice, then Volume up to select the highlighter choice. Pressing power just resets the phone as you experienced.
ESCollins90 said:
I believe when in the boot loader menu, you need to Volume down to your choice, then Volume up to select the highlighter choice. Pressing power just resets the phone as you experienced.
Click to expand...
Click to collapse
Sorry....my op is wrong and has been corrected. You are right, the volume up selects the highlighted choice. Which is the way I was doing it, I just described it wrong.
And my problem still exists, I can't access recovery. Thanks for your reply.
jlstark1 said:
Sorry....my op is wrong and has been corrected. You are right, the volume up selects the highlighted choice. Which is the way I was doing it, I just described it wrong.
And my problem still exists, I can't access recovery. Thanks for your reply.
Click to expand...
Click to collapse
If you haven't tried it already, since you seem to have ADB setup and working, try to use "adb reboot recovery" and see if you have change in luck. If not, my knowledge does not go much further, I hope someone knows how to answer this for you. I can imagine how distraught I'd be.
The only other thing is to ensure you've installed the correct recovery:
Google Dhacker29 and choose the AndroidHosting site, choose msm8960.
(I can't post url's because i've had less than 10 posts... spam thing)
Since you seem to have unlocked bootloader with the most recent case of KitKat make sure you have the "TWRP2710-RAZR-HD_M-KITKAT.img" file.
I will say I didn't use ADB to push mine, I'm not home often, I used Flashify from the Google Play Store. I had no problem with this method.
Hope you can figure it out! Good luck!
ESCollins90 said:
Since you seem to have unlocked bootloader with the most recent case of KitKat make sure you have the "TWRP2710-RAZR-HD_M-KITKAT.img" file.
I will say I didn't use ADB to push mine, I'm not home often, I used Flashify from the Google Play Store. I had no problem with this method.
Click to expand...
Click to collapse
Thanks!! Your 2 suggestions made the difference. Works like a charm!
jlstark1 said:
Thanks!! Your 2 suggestions made the difference. Works like a charm!
Click to expand...
Click to collapse
Awesome! Enjoy your new phone!![emoji1]