Fastboot on boot? - Motorola Atrix 2

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

Related

Can't get my G1 into recovery mode.

Hi to all,
I been trying to upgrade to JF 1.14 rc33 and haven't been able to get to the recovery mode to process the update.zip file. Im not a noob but also not and expert i rooted my my phone so i know basics. When i try to hold the home butoon and power button the g1 logo keeps reappearing for as long as i hold it from 10 seconds to 2 minutes. any ideas of what im doing wrong, i dont care if i have to wipe i just want rc33. Thanks.
I currently have Fimware 1.0
Build #:1.0 TC-4 RC30
Custom Theme: Windows beta 7
Just to make sure, with the phone off you press and hold the home button and then press and hold (while still holding the home button) the power button. It should take ~20 seconds for the recovery mode screen to come up.
Dharkaron said:
Just to make sure, with the phone off you press and hold the home button and then press and hold (while still holding the home button) the power button. It should take ~20 seconds for the recovery mode screen to come up.
Click to expand...
Click to collapse
i tried and did not work
natienn said:
Hi to all,
I been trying to upgrade to JF 1.14 rc33 and haven't been able to get to the recovery mode to process the update.zip file. Im not a noob but also not and expert i rooted my my phone so i know basics. When i try to hold the home butoon and power button the g1 logo keeps reappearing for as long as i hold it from 10 seconds to 2 minutes. any ideas of what im doing wrong, i dont care if i have to wipe i just want rc33. Thanks.
I currently have Fimware 1.0
Build #:1.0 TC-4 RC30
Custom Theme: Windows beta 7
Click to expand...
Click to collapse
Flash back to the original G1 theme, then try the update. Your theme may be preventing you from upgrading.
andonnguyen said:
Flash back to the original G1 theme, then try the update. Your theme may be preventing you from upgrading.
Click to expand...
Click to collapse
how do you flash to the original theme? do you know of any links? thanks
Start holding the Home button before you press the Power button.
jashsu said:
Start holding the Home button before you press the Power button.
Click to expand...
Click to collapse
i tried that in different time lentghs from 10 seconds holdin both to 2 minutes, of course pressing the home key 1 sec before the power and holding both
Same problem
Need to bump this thread as I'm having the same issue. Have a HTC Dream with CyanogenMod-5.0.7-DS, trying to go to 5.0.8, but cannot get into Recovery Mode.
Yes, I am completely powering the phone off, holding Home just prior to pressing & holding Power. I keep both depressed for a few minutes and no joy, just sits at the G1 splash screen. I can remove the battery and press Power to bring the phone up normally. Have even dropped to the console, switched to root and issued "reboot recovery". The phone restarts and sits at the G1 splash screen as well.
Can anyone offer advice on how to restore my Recovery Mode? Many thanks...
You can try to reflash (or flash another) recovery with adb, fastboot or in terminal. Btw this thread is in wrong section. It should be in Q & A section.
You could even flash a recovery image from within your rom...you said you could boot the phone normally correct?
So drop into terminal and flash it if you don't want to mess with adb.
The Amon Ra 1.7 Recovery thread has the commands you need to flash through terminal...
These people apparently are no help. If you hold down the home key and it stays at the G1, try fastboot by holding down the camera button on the side while you power it on. You only need to hold the home key until it vibrates. It should instantly boot into fast boot, if you're holding down camera when powering on.
... if you can get into fastboot, you might need to unroot your phone and reroot it.
... if you can't get into fastboot or recovery mode, then you probably bricked your G1 and you'll need a jtag or scrap it. Or if it's under insurance, tell them you updated and your phone is stuck on the G1 screen....
You could also try taking out your battery then powering it on into fastboot/recovery but odds are that wont help at all.
Hope this was some help.
yutsoku said:
These people apparently are no help. If you hold down the home key and it stays at the G1, try fastboot by holding down the camera button on the side while you power it on. You only need to hold the home key until it vibrates. It should instantly boot into fast boot, if you're holding down camera when powering on.
... if you can get into fastboot, you might need to unroot your phone and reroot it.
... if you can't get into fastboot or recovery mode, then you probably bricked your G1 and you'll need a jtag or scrap it. Or if it's under insurance, tell them you updated and your phone is stuck on the G1 screen....
You could also try taking out your battery then powering it on into fastboot/recovery but odds are that wont help at all.
Hope this was some help.
Click to expand...
Click to collapse
Why would you need to reroot it, just flash a new recovery through fastboot.
fastboot flash recovery <name>.img
misread, yeah he could do that too but it would be easier to reroot if he knows how to do that... instead of learning a whole new method.
You're right though, that would be better.
Update
I am able to fastboot by holding the camera button in and powering on. It sounds like I just need to do the Amon Ra Recovery procedure in order to restore my recovery partition. I assume that I'll need to re-root, but I'm sure there are instructions there for that as well.
Thanks for all the quick replies!
So here's what I found....
I had the exact same problem, but first a little history then how I fixed it.
I purchased an 8GB MicroSD card so I could use Apps2SD and was quite pleased with the ability to do so. Until my battery life dropped to 5mins. It was already down from when I bought it last year.
The battery was severely screwed on my. If I used ANYTHING for more than 5 mins, it would die and would NOT boot up. Oh I could pres the power button and it would try to boot but then die somewhere in the boot process. That is until I plugged it into some charger (car or wall) and then it would boot, showing anywhere from 70 to 90% battery life.
After much research I found that it was the battery and so ordered a replacement off eBay from Hong Kong. $3.96 shipped to my door. Works great, and I am incredibly thankful for that.
So just prior to getting the battery I had done an upgrade to 5.0.8 with the vain hopes that it might help limp along but to no avail. The battery was gone.
Ok, so in comes the new battery. Great! I'll just reflash the ROM to make sure there are no lingering issues and we'll be good to go! Little did I realize that I did an 'upgrade' from CM Updater and when I booted into Recovery I flashed th zip file that was there....which was 5.0.7. DOH! No biggie, everything was working so I didn't worry too much.
Then I installed Clockwork's ROM Manager 1.8.x. A few days later there was an update, so I updated to 2.0.1.3. So I updated that. It went fine.
Few days later, and a few more apps re-installed, the system was running slow.
Apps2SD was greyed out. Huh?
Checked the card....Ubuntu was only mounting it Read Only. And the old swap partition, which I thought I had deleted, was still there. Dammt. But this s a side story I think.
So I wanted to reflash but there was no way I could do it because I could not get into Recovery mode. Ugh.
ROM manager had an update to 2.0.1.4. Ok, maybe that'll work. Nope. It said it updated fine but stuck at G1 logo like many others.
Doing some googling around I saw that it was a ROM Manager issue and that you should flash back down to 1.4.x. Well, since I knew it was working at 1.8.x I decided to reflash to 2.0.0.3. I could get into recovery mode now!
While this kinda solves one issue....I'll have to go into another thread to figure out the Read Only problem so I can re-partition my card again.
Thread closed. Please post questions in the Questions and Answers forums and not in the development forum.

update.zip

hey guys, i need the update.zip that comes stock on the sd card.
if anyone needs anymore information:
my d2g freezes at the bootlogo
my bootloader never worked so it has a blank screen.
There is no stock update zip on the SD card. Make sure your phone is completely off turn on the phone by holding on the power button and up arrow at the same time. When the screen glows softly, let go of the buttons and you will be in the bootloaders sbf flash mode. If you get this far reply back
for gingerbread = http://www.multiupload.com/ZGUOERGZNT
D2GxNiNjA said:
hey guys, i need the update.zip that comes stock on the sd card.
if anyone needs anymore information:
my d2g freezes at the bootlogo
my bootloader never worked so it has a blank screen.
Click to expand...
Click to collapse
kurpter said:
for gingerbread = http://www.multiupload.com/ZGUOERGZNT
Click to expand...
Click to collapse
would this work if i had froyo when it happened?
i was installing venusX 3.2 just like your using but i got stuck at the splash and my bootloader is busted.
rootfan said:
There is no stock update zip on the SD card. Make sure your phone is completely off turn on the phone by holding on the power button and up arrow at the same time. When the screen glows softly, let go of the buttons and you will be in the bootloaders sbf flash mode. If you get this far reply back
Click to expand...
Click to collapse
theres probably something saying something about double posting but....
When i purchased my global from verizon, i immediately rooted it, but before, there was infact an update.zip included and its even on my friends global and he has never rooted his ever.
hi mate, was you on the froyo build when you upgraded to venus? if you did, this is why you are boot looping as venus needs the gingerbread build. if this is the case, you need to follow my update guide from here =
http://forum.xda-developers.com/showthread.php?t=1263722
its the last comment on the end, reflash that, then do an ota update, this will take you to the new GB version, then use oneclickroot, then you can upgrade to venus
kurpter said:
hi mate, was you on the froyo build when you upgraded to venus? if you did, this is why you are boot looping as venus needs the gingerbread build. if this is the case, you need to follow my update guide from here =
http://forum.xda-developers.com/showthread.php?t=1263722
its the last comment on the end, reflash that, then do an ota update, this will take you to the new GB version, then use oneclickroot, then you can upgrade to venus
Click to expand...
Click to collapse
your really helpful and i know for sure that works, but my "BOOTLOADER" IS BLANK.
therefore RSD isnt picking up any connection for me to SBF.
instead of saying:
Bootloader D0.11
Battery OK to program or something like that, the backlights just light up, nothing appears, and 3 seconds later it goes back to booting and staying there.
I knew about it needing gingerbread the minute i forgot to cancel the update in Rom manager. now i cant do anything but go into stock recovery.
and when i try to install a signed update from motorola it says:
--Install From SD Card...
...Finding update package...
...Opening update package...
.Verifying update package...
...Installing update package...
assert failed: file_getprop("/system/build.prop". "ro.build.fingerprint") == "verizon/droid2we_vzw/cdma_droid2we/droid2:2.2.S273/2.4.330:user/ota-rel-keys" || file_getprop(/system/build.prop", "ro.build.fingerprint") == "verizon/droid2we_vzw/cdma_droid2we:2.3.3/4.5.1_57_D2G-37/110722:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted.
AND!!! my power button is jammed so it doesnt work but whenever my battery is in the phone it turns on.
Is your power button not working at all? if you can get the device to boot up, you need to hold the up and down power volume button together, this will get you in to the boot loader mode, if not see if you can hold x and the power button this will take you in to the recover mode.
if you can get in to the boot loader, then you can sbf if not, and you get in to the recover mode, you will need to copy the zip file to the root of sd card, but dont use the ginger bread zip file as it wont work, you will need the update.zip from your friends phone if he is still on froyo and then in the menu just apply the update. let me know how you get on.
kurpter said:
Is your power button not working at all? if you can get the device to boot up, you need to hold the up and down power volume button together, this will get you in to the boot loader mode, if not see if you can hold x and the power button this will take you in to the recover mode.
if you can get in to the boot loader, then you can sbf if not, and you get in to the recover mode, you will need to copy the zip file to the root of sd card, but dont use the ginger bread zip file as it wont work, you will need the update.zip from your friends phone if he is still on froyo and then in the menu just apply the update. let me know how you get on.
Click to expand...
Click to collapse
1. No, my power button is not working at all.
2a. I pushed both rockers and the BLANK screen appeared
2b. Up on Arrow Keys shows a blank screen too.
3. i have access to stock recovery but thats the ONLY thing i can access.
4. (WTF) He upgraded via the OTA and formatted his SD Card...
5. If ANYONE CAN HELP, I NEED ALL FROYO update.zips that are SIGNED so i dont waste time. my contract ends in 10 days but i havent used the phone in 3 months. ive just been using some crappy feature phone.
Hi mate, i think i have the old zip file you need, i backed up my stuff age's ago and i think this is the one = http://www.mediafire.com/?whlxcbqvhzpnczd
(dont worry it is a D2G update, i just cant remember if this is the ginger bread on of froyo.
if it isnt let me know and then i'll take my phone back do to froyo and get the update .zip for you.
Regards
Scott
kurpter said:
Hi mate, i think i have the old zip file you need, i backed up my stuff age's ago and i think this is the one = http://www.mediafire.com/?whlxcbqvhzpnczd
(dont worry it is a D2G update, i just cant remember if this is the ginger bread on of froyo.
if it isnt let me know and then i'll take my phone back do to froyo and get the update .zip for you.
Regards
Scott
Click to expand...
Click to collapse
Nope, But like the post of the log, something was different.
it had 2.4.29 and 2.4.330 in it.
is there anyway i could get my bootloader to show up again?
its been blank ever since i had it.
make sure the phone is switched off, then press and hold in the volume up and down rocker together (make sure you dont let go until it you see the bootloader menu) and plug the phone in to usb (so it powers it up) and then you should be in bootloader mode, i dont know of anyother way of doing it. Also make sure your phone is at least 70% charged.
kurpter said:
make sure the phone is switched off, then press and hold in the volume up and down rocker together (make sure you dont let go until it you see the bootloader menu) and plug the phone in to usb (so it powers it up) and then you should be in bootloader mode, i dont know of anyother way of doing it. Also make sure your phone is at least 70% charged.
Click to expand...
Click to collapse
This DOES NOT work because my bootloader doesnt show anything, (no function whatsoever.) this is what happens.
1. I hold both volume rockers
2. Backlight activated (bootloader)
3. No Words
4. Turns back off
5. No RSD or Win7 notification sounds
6. goes back to Venus bootlogo
7. Stays there until it dies
now what confuses me:
if it boots up but theres no bootloader how does it boot?
otherwise, if it does use the bootloader, why does it show up blank?
it was blank when i first got it because i was wanting to root it then.
The bootloader is launched by powering the phone on while holding the up arrow key on the physical keyboard.
Gasai Yuno said:
The bootloader is launched by powering the phone on while holding the up arrow key on the physical keyboard.
Click to expand...
Click to collapse
i already knew that,
it does the exact same thing as when i hold both rockers.
my problem is that when the backlight comes on the screen doesnt show anything.
Soooo.... No SBF to fix/
And you're sure the battery is charged?
(It doesn't charge if it can't boot.)
Gasai Yuno said:
And you're sure the battery is charged?
(It doesn't charge if it can't boot.)
Click to expand...
Click to collapse
i got my friends og droid and the battery is 100%. its been a week and it still didnt do it. oh well.... on the 11th my contract is up and i dont want to get another phone but... sprint's iphone 4s is looking pretty good now!

[D3] Boot into CWM from POWER OFF! Applicable on the A2?

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

Droid 2 Global Bootloader Missing

Hoping someone here may have some ideas. ..
Picked up a couple Global's the other day on eBay. Two of the three work great. Was able to get them unlocked, rooted, and band unlocked. They are working great on T-mobile! The issue I'm having is with the third one. When I enter the bootloader, I get nothing but a black backlit screen with no writing. When I attempt to use RSD Lite, I can't get it to recognize the phone at all.
So next I tried booting the phone normally, and then hooking it to the PC. RSD Lite does recognize it that way. When I begin the flash process, the phone attempts to reboot into flash mode, screen goes black, same backlit screen with no writing. I would like to point out that I am doing all this with a 5-wire factory cable, so none of the usual button combo mistakes, undercharged battery issues, etc. apply here. If you have on of these, you don't need a battery in the phone at all. With and without battery, with and without factory cable...hasn't mattered, no bootloader no matter what. The issue is that the bootloader acts as if it just isn't even on the phone. I know there are several ways to reload that consumer replacement to a droid 1, but I haven't found anything for a 2. The other thing limiting what I am able to do is that the phone is running .629, which means no root or CWM, so those couple tricks are out the window at this point also, and because of the bootloader issue I am unable to downgrade using RSD Lite or any of the bootable CD options that usually work for phone stuck on .629.
So at this point I'm figuring the phone is just stuck the way it is, but I thought I'd throw it out there and see if any of you guys had any similar experiences. Thanks
strabo231 said:
Hoping someone here may have some ideas. ..
Picked up a couple Global's the other day on eBay. Two of the three work great. Was able to get them unlocked, rooted, and band unlocked. They are working great on T-mobile! The issue I'm having is with the third one. When I enter the bootloader, I get nothing but a black backlit screen with no writing. When I attempt to use RSD Lite, I can't get it to recognize the phone at all.
So next I tried booting the phone normally, and then hooking it to the PC. RSD Lite does recognize it that way. When I begin the flash process, the phone attempts to reboot into flash mode, screen goes black, same backlit screen with no writing. I would like to point out that I am doing all this with a 5-wire factory cable, so none of the usual button combo mistakes, undercharged battery issues, etc. apply here. If you have on of these, you don't need a battery in the phone at all. With and without battery, with and without factory cable...hasn't mattered, no bootloader no matter what. The issue is that the bootloader acts as if it just isn't even on the phone. I know there are several ways to reload that consumer replacement to a droid 1, but I haven't found anything for a 2.
Click to expand...
Click to collapse
maybe bricked, could try manually installing update.zip from android recovery, if you can get to that
How to enter Android system recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the power button.
Once you see a warning sign with an android robot appear, press the Search button on your physical keyboard if you're running froyo/2.4.x firmware. For gingerbread/4.5.x firmware, press Volume Up and Down buttons.
and be sure you are using
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
The other thing limiting what I am able to do is that the phone is running .629, which means no root or CWM, so those couple tricks are out the window at this point also, and because of the bootloader issue I am unable to downgrade using RSD Lite or any of the bootable CD options that usually work for phone stuck on .629.
Click to expand...
Click to collapse
.629 has been rootable since 16 April 2012
just use ezSBF & Root 2.3.4/ 4.5.629
So at this point I'm figuring the phone is just stuck the way it is, but I thought I'd throw it out there and see if any of you guys had any similar experiences. Thanks
Click to expand...
Click to collapse
sd_shadow said:
maybe bricked, could try manually installing update.zip from android recovery, if you can get to that
How to enter Android system recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the power button.
Once you see a warning sign with an android robot appear, press the Search button on your physical keyboard if you're running froyo/2.4.x firmware. For gingerbread/4.5.x firmware, press Volume Up and Down buttons.
and be sure you are using
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
.629 has been rootable since 16 April 2012
just use ezSBF & Root 2.3.4/ 4.5.629
Click to expand...
Click to collapse
Ah Shadow! I was hoping you'd see this. Let me clarify a little bit.
1. I am able to get phone to boot into OS. I did try to install the update.zip already but I'm still having the same problem with the boot loader.
2. I know about the easy sbf, and tried that with this particular phone, but because of the problem with the boot loader when easy sbf or RSD Lite switch the phone, or attempt to switch into flash mode, the computer no longer recognizes the phone.
3. I did think about rooting the phone to try to open up a few other options to at least get around the problem. Since it's on .629 already though I'm limited to rooting using easy sbf as far as I've understood, but again since I'm having the issue with the boot loader that hasn't been an option I have been able to successfully use.
4. The power button on the phone isn't working, so I'm unable to use the key combo to access the boot loader; however, I have a factory cable...now I say factory cable not meaning the stock charging cable...but the 5-wire factory cable. Typically with Motorola phones using this cable you simply remove the battery, and then with no battery in the phone hold down both volume buttons and plug the factory cable in and it automatically reverts to the boot loader.
I know that there is a consumer replacement boot loader for the droid 1 to fix issues like this, but I haven't seen one for the two. The other issue is that the replacement is an sbf file which ill be unable to use, and didn't know if that was something that would exist as an update.zip that could be flashed through the stock recovery
don't need power button
with phone off, hold up arrow and connect usb cable
should boot directly to bootloader
sd_shadow said:
don't need power button
with phone off, hold up arrow and connect usb cable
should boot directly to bootloader
Click to expand...
Click to collapse
yeah we're on the same page there. When I do that, instead of getting the bootloader like I normally would, I'm just getting a blank black backlit screen, like the boot loader isn't there. Instead of getting bootlader D0.11 ect, It's just a blank screen. It doesn't matter which method I use to access it, both volume buttons and usb, up arrow and usb, whether there is a battery in the phone or not, I'm still getting the same result. If I boot the phone normally, and then try to let RSD switch it for me, it does it, and then I get the same black screen and the flash mode failure error. Like I said there is a consumer replacement bootloader for the 1 that I've been able to use to fix this problem in the past, but if one exists for the two I haven't been able to locate it. So at this point I have a working OS, a working stock recovery, and no boot loader
think there was a 608 bootloader file, can't remember where i saw it
but it didnt work on 629 anyways
you might be able to root with http://forum.xda-developers.com/showthread.php?p=37438602
Root Droid 2 on Gingerbread 2.3.4 [WINDOWS]
i havent got it to work, but it only takes a few mins to download and run
Sent from my XT862 using xda premium
sd_shadow said:
think there was a 608 bootloader file, can't remember where i saw it
but it didnt work on 629 anyways
you might be able to root with http://forum.xda-developers.com/showthread.php?p=37438602
Root Droid 2 on Gingerbread 2.3.4 [WINDOWS]
i havent got it to work, but it only takes a few mins to download and run
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
Yeah I tried that last night. I saw where you were having problems with it too. I had seen where a few months back there was someone else that was having this issue that you were trying to help walk them through, but the thread kinda died off, so I wasn't sure if there was ever a resolution to it. Ok well thanks for your time. I'll be sure to post an update for people coming behind me if I manage to get anywhere with it.
strabo231 said:
yeah we're on the same page there. When I do that, instead of getting the bootloader like I normally would, I'm just getting a blank black backlit screen, like the boot loader isn't there. Instead of getting bootlader D0.11 ect, It's just a blank screen. It doesn't matter which method I use to access it, both volume buttons and usb, up arrow and usb, whether there is a battery in the phone or not, I'm still getting the same result. If I boot the phone normally, and then try to let RSD switch it for me, it does it, and then I get the same black screen and the flash mode failure error. Like I said there is a consumer replacement bootloader for the 1 that I've been able to use to fix this problem in the past, but if one exists for the two I haven't been able to locate it. So at this point I have a working OS, a working stock recovery, and no boot loader
Click to expand...
Click to collapse
if you are still working on this a Bootloader Only
HS_S_signed_AP_BL_D11_cdma_droid2we_Consumer_replacer.zip
has been posted here http://sbf.droid-developers.org/cdma_droid2/list.php
If you're still looking to root, try Framaroot from here. It worked for me on .629. No idea about the bootloader however . Good luck though!

S3 wont flash custom recovery

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:

Categories

Resources