Recently I installed maverick 4.5 using safestrap 3.05. Now I am completely unable to access safestrap and the rom is unstable. As soon as I installed safestrap so I could back up my working rom, it automatically switched to the previous broken ROM slot. Is there any way to access safestrap now? When I hit the menu button it just boots into maverick 4.5. I really need help on this as I don't want to lose any of my data from the stock rom I was running. The phone is currently using the XT883 radio so I can use the phone on AT&T, but the acutal model is XT862. It's also running version .906. I know I could just sbf back to .906, but I really need to be able to access safestrap.
EDIT: I actually managed to fix it by using the BP tools option. I'm sure others have had this issue as well, but a mod can now close this.
"The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery."
This is a fairly known issue. The steps you've posted are what most of us do. I've also heard if, when the safestrap splash screen comes up, you wait a few seconds and the screen dims, to then hit the menu key. Some people claim to have a fairly good success rate using this method, although certainly via BP tools is mist dependable
Sent from my XT860 using xda premium
Related
I’ve got an AT&T Captivate that is stuck in 3e recovery, because it won't recognize when I use the power button to select "reboot system now."
Some background:
It was stuck in a boot loop running CM7. I re-installed éclair to take advantage of 2e recovery. Rooted it, and intended to put a version of UCKB1 without 3e recovery, so I could install unsigned files to prep for a re-install of CM. Apparently I flashed the wrong rom or the flash got corrupted. I can’t get it into download mode. Tried using a jig, tried using one-click unbrick. I can’t even use ADB, since it is in recovery.
Any help would be amazing! Thanks in advance.
Does the phone boot all the way to Android or does it still loop?
Did you use the jig while in recovery?
you have to use it on a powered off state.
Just yank the battery and either try the jig while powered off, or if it boots correctly use adb while it's powered up.
Thanks for replying. The phone does not boot into android, it gets stuck in 3e. I used the jig with the phone off. (I did try with it on just for kicks, but no joy.)
The phone "recoginizes" the power button when I try to turn it on, it gets to recovery, and then won't recognize a butten press in order to boot the rest of the way.
Thoughts?
Fixed it
Re-tried with a newly made jig. Must have blown a resister last time. Works now. Thanks for the advice.
I have this same issue intermittently, usually after a modem flash in cwm3. The txt will pop up saying that the back button has been disabled. A battery pull and restart and it reboots fine. Just a mystery to me...
Yeah that happens from time to time.try to Hold both volume buttons. That will sometimes re-enable the back button.
Ionno why that happens....
Some recoveries i've seen used back button or home button to select...just saying might work
Sent from my SAMSUNG-SGH-I897 using xda premium
Yeah some recoveries not all, I know specifically in boog's kernels, you can use the capacitive buttons.
Settings = down
Home = up
Search = select
you have to cycle from the bottom to the top... i don't know why it does this..
Hit down repeatedly until you end at the top. the power button will work.
Hey guys, sorry for the cliche first post, but believe me I have been searching and reading all night and day for a problem similar to mine.
I was running CM9 on my Droid 3 and was having trouble because my phone kept running in safe mode, which was causing some of my apps to not work, and when I turned safe mode off, it ran the stock droid OS, which I didn't want. Therefore, I manually turned my safestrap off (first mistake) so now I can't get into it. Alternatively, my volume down button doesn't seem to be working so I can't select AP Fastboot to flash my phone back to factory settings and eliminate all my woes. When I try to power my phone on manually, all it does is load me into the BP Flash screen, which to my understanding doesn't work (why did they put it in?). I've tried to press the down direction key and power to shortcut into AP Fastboot, as well as power button volume down, neither of which work. I can get into the screen with Normal boot, recovery, etc but cannot select anything, and it just goes to normal boot and proceeds to bootloop. Is there anything I can do in this predicament? Any help is much appreciated.
If you can, try using the keyboard arrow keys to navigate the boot menu.. I've never tried it before but its worth a shot.
Sent from my XT862 using XDA App
Sent from my XT860 using xda premium
I recently bought my xt894 from china and wish to flash it with ics
I've it rooted and installed safestrap
But after I switched to safe mode enable, whatever rom I flashed, I got into the bootloop tht either blank screen or stucked in android logo.
I am new to droid 4, any help would be appreciated!!:beer:
Is it related to my gsm unlocked with chinese rom?
Sent from my DROID4 using XDA
disablewong said:
I recently bought my xt894 from china and wish to flash it with ics
I've it rooted and installed safestrap
But after I switched to safe mode enable, whatever rom I flashed, I got into the bootloop tht either blank screen or stucked in android logo.
I am new to droid 4, any help would be appreciated!!:beer:
Is it related to my gsm unlocked with chinese rom?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
The first time I flashed an ICS ROM on my D4 it bootlooped as well. I had to wipe data and cache and then it booted right up.
Yes I know I gotta wipe both cache and data and I done it twice, but still nothing show up.....it is just the blank black screen, no any animation at all...
Sent from my DROID4 using XDA
Please Help!
disablewong said:
Yes I know I gotta wipe both cache and data and I done it twice, but still nothing show up.....it is just the blank black screen, no any animation at all...
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
I'm freaking out because mine is stuck on the black screen too... I was trying to flash the XML file for Fastboot. and it just went blank (blackscreen) can someone please help. I don't know if letting the battery die is the way to go? I have it connected to a laptop at the moment. I know they said that the XML file takes a whille, but it has been an hour. I do not have any warranty as this was a trial unit given to me.
I'm not that much of a Noob, but I'm not sure what to do at this point. <<<<---- Fixed using Volume down and Power to do a "battery pull" Although I almost Removed the battery physically.
Can you still boot into the unsafe system?
If so, is the unsafe system currently ICS or Gingerbread?
pieeni age
slosho said:
I'm freaking out because mine is stuck on the black screen too... I was trying to flash the XML file for Fastboot. and it just went blank (blackscreen) can someone please help. I don't know if letting the battery die is the way to go? I have it connected to a laptop at the moment. I know they said that the XML file takes a whille, but it has been an hour. I do not have any warranty as this was a trial unit given to me.
I'm not that much of a Noob, but I'm not sure what to do at this point. <<<<---- Fixed using Volume down and Power to do a "battery pull" Although I almost Removed the battery physically.
Click to expand...
Click to collapse
ICS leaks are not fastbootable.AFAIK, unless you just meant that you were trying to fastboot flash to 6.13.219 before flashing to ICS. Either way, here we go.
Go into safestrap, safe mode menu, then disable safe mode, and restart your droid. I am assuming you at least went into safe mode before trying to flash. If so, this is why we love safestrap...makes sure you have a working OS. Let it boot up. Did it work?
If not, don't panic, there is still another solution, even if you didn't safestrap your unmodified OS (just make sure you do this next time!)
If you did backup and safestrap saved you, ignore this block below for now.
Code:
[LIST=1]Download [COLOR="Red"]VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01[/COLOR].
You might already have this if that's what you were trying to fastboot to. It's 1.18GB in size.
Download is here: sbf.droid-developers DOT org/cdma_maserati/VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml.zip
(change DOT to . Can't post links yet.)
[*]dl.dropbox DOT com/u/76950573/RSDLite5.7.msi Download RSDLite and install it.
[*]Download the Droid USB drivers:
motorola DOT com/Support/US-EN/Support-Homepage/Software_and_Drivers/USB-and-PC-Charging-Drivers
Install them. [COLOR="SeaGreen"][B]RESTART YOUR COMPUTER.[/B][/COLOR]
[*]Turn your phone off.
Hold the two side volume buttons down together, press and hold the power button down.
Hold all 3 down until you get to the bootloader.
Press volume down to get to "recovery", press volume up to select it.
You'll see a sick looking android/red triangle icon soon.
When you do see him, press both volume buttons down at the same time.[/list]
[*]Volume down to "wipe data/factory reset", power button to select (not volume up this time.)
Confirm, delete everything. When it finishes, select "reboot system", press the power key to enter that choice.
Immediately press both volume keys together after the reboot begins and hold them until you see the bootloader menu again.
[*]Plug your USB cable into your phone and connect it to your computer.
Use volume down to select "AP Fastboot", volume up to confirm the choice.
Open RSDLite on your PC.
Press the "....." icon in the program, browse to and select the 1GB+ VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01 you downloaded earlier.
[*]Click "decompress/start flashing". Now wait for half an hour or so.
I believe there will be several phone restarts near the end, this is normal.
You're now back to stock GB. You no longer have to fastboot to this in order to go forward to ICS.[/list].
Now to get to ICS...
Go here. droidforums DOT net/forum/droid-4-hacks/212307-droid-4-utility-updated.html and download the tool. You don't need anything else but the main tool.
Grab your preferred ICS leak. 6.16.217 is the most recent: droidforums DOT net/forum/droid-4-roms/218610-ics-leak-6-16-217-update-zip-boot-img-crc.html
Flash to 6.13.219 if you didn't just do that.(follow the steps in the CODE block above).
Open the droid 4 tool (.bat file) after extracting from the archive. Plug your phone into the USB. Set it to debug mode. Install safestrap 1.09, root the droid.
Unzip D4 6.16.217.zip. Rename boot.img to ICSFIX.img and move it into the droid 4 utility subfolder named \files\
Copy Blur_Version.6.13.219.XT894.Verizon.en.US.zip (leave it zipped.) to your SDcard.
Go into safestrap and make a backup. Turn on safe mode. Reboot.
Reboot into Bootloader, select AP Fastboot. USB should still be connected and the droid utility open. Select option 16. (Errors might occur. This is fine.) Flash your blur.zip from sdcard. Follow prompts on utility. It will reboot, do some animations. When you see the motorola logo, let it do its thing. Once the moto logo fades out, force a reboot (hold VOL keys & power down.) Now hold vol down and press power, boot to bootloader, and select recovery. Press both power buttons when you see the dead sick android logo. Update from sdcard. Select the zip.
Let it flash. It'll reboot.
Open the droid utility. If you flash to another ICS version, UNINSTALL safestrap 1.09, and then install; the new version 2 one. Make backups. Root your phone. Use the last option on the droid utility to flash between ICS versions.
You cannot use it to flash between something like AOKP or CM9 to a normal ICS version (Yes I actually tried this, lol).
Sorry for wall of text, hopefully this helps you in some way, whether you're still bricked, or still want to go to ICS after fixing your brick.
Resources/relevant threads:
droidforums DOT net/forum/droid-4-roms/218610-ics-leak-6-16-217-update-zip-boot-img-crc.html
droidforums DOT net/forum/droid-4-hacks/212307-droid-4-utility-updated.html
droidforums DOT net/forum/droid-4-roms/209130-how-install-leaked-android-4-0-4-ics-build-droid-4-xt894.html
droidforums DOT net/forum/droid-4-tech-support/206972-how-restore-your-motorola-droid-4-xt894-stock-windows-only.html
droidforums DOT net/forum/droid-4-hacks/200945-safestrap-guide-droid-4-a.html
blog.hash-of-codes DOT com/how-to-safestrap
Read those. It'll be good information for you. I can't post links yet, but it's pretty clear they're not spam and only meant to help somebody out <3
I installed CM10.1 from this thread and everything went smooth and works great. However, no matter what I do I can't boot into recovery mode. I've tried the hardware key combinations, the power menu in 10.1/4.2.2 and I've also tried ROM Manager from CWM (to install the latest CWM and boot to it). Everything just boots like normal.
From what I've read I'm guessing I have a recovery that isn't compatible with my ROM? If that's the case, what recovery should I use and how can I install it using nvflash???
Finally got ADB working and was able to install gapps using the method found here (with minor adjustments): http://www.keyables.com/2012/05/use-adb-to-install-google-apps-includes.html
Very cool.
It would probably still be nice to be able to get into recovery if I ever need to... oh well.
Power Off
Press Volume+ and Power and HOLD THEM
Select option 2.
Please put questions in the General section as this is for development only.
I am havIng the same issue with recovery but when I press and hold volume+ and power I get the samsung custom screen and I see recovery in very small blue font in the upper left, I am still holding both keys and then the phone just boots up normal. Any ideas?
babydollnyroch said:
I am havIng the same issue with recovery but when I press and hold volume+ and power I get the samsung custom screen and I see recovery in very small blue font in the upper left, I am still holding both keys and then the phone just boots up normal. Any ideas?
Click to expand...
Click to collapse
Why the heck would you be seeing anything "Samsung"?!?
Ya might start there
Sent from my Galaxy Nexus using xda premium
My bad, for some reason this posted to this thread, I had the cyanogen 10.1 for verizon samsung s4 thread up, sorry, don;t know how that happened
So I rooted my droid turbo around April and everything was fine then about 2 weeks ago my phone would go into sleep and the power button does not wake up the screen. Power is still going to the phone since I can feel the vibrate when I press the soft keys. Have to hold down the power button to restart and then sometimes boots up fast other times it takes about 20-30 mins. Finally did a full wipe internal and what not and when i flash roms the phone will respond and boots up fine then I hit the power button to put it in sleep mode and will happen again happens with 3 different roms all the same outcome. Think it might be hardware but when it is in recovery it responds to the power button just fine. I unlocked using sunshine and am using twrp 3.0.0. Any help will be appreciated
hugorod91 said:
So I rooted my droid turbo around April and everything was fine then about 2 weeks ago my phone would go into sleep and the power button does not wake up the screen. Power is still going to the phone since I can feel the vibrate when I press the soft keys. Have to hold down the power button to restart and then sometimes boots up fast other times it takes about 20-30 mins. Finally did a full wipe internal and what not and when i flash roms the phone will respond and boots up fine then I hit the power button to put it in sleep mode and will happen again happens with 3 different roms all the same outcome. Think it might be hardware but when it is in recovery it responds to the power button just fine. I unlocked using sunshine and am using twrp 3.0.0. Any help will be appreciated
Click to expand...
Click to collapse
Try doing the following:
1. Flash a CM-based rom and the appropriate gapps and boot into it.
2. Go back to recovery, format data, wipe system and flash a 100% stock rom. Do not flash any modifications.
3. Boot into the stock rom and get past the setup screen. You should get a notification that says it needs to revert Motorola sensor firmware to a previous version or something like that.
4. Tell it to do that and wait for the phone to reboot (it might take a few minutes)
hugorod91 said:
Think it might be hardware but when it is in recovery it responds to the power button just fine.
I unlocked using sunshine and am using twrp 3.0.0. Any help will be appreciated
Click to expand...
Click to collapse
The recovery should not be an issue, but there's a newer version of TWRP:
[RECOVERY][OFFICIAL TWRP 3.0.2-0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
https://www.androidfilehost.com/?fid=24566454284189749
TheSt33v said:
Try doing the following:
1. Flash a CM-based rom and the appropriate gapps and boot into it.
2. Go back to recovery, format data, wipe system and flash a 100% stock rom. Do not flash any modifications.
3. Boot into the stock rom and get past the setup screen. You should get a notification that says it needs to revert Motorola sensor firmware to a previous version or something like that.
4. Tell it to do that and wait for the phone to reboot (it might take a few minutes)
Click to expand...
Click to collapse
I actually have done that already but i did do a full wipe including internal storage and everything was fine but it just happened again and right before it happened i was running pokemon go and i believe thats my culprit. Pretty lame but im sure of it anybody else experience this?
so unfortunately it happened again where the screen falls asleep and the device will not wake up until I reboot the device. actually had to do a full wipe again and flash another rom to it to actually go pass the bootloading screen. I did not install pokemon go that time.