Database Develop

Trouble booting in cwm recovery?

I recently found out that i was using the wrong d3 bootstrap. It was the first one hashcode created. So i uninstalled recoverys and deleted it. I downloading koush's bootstrap and installed it (the one with the red skull) I CAN get in cwm recovery when i click reboot recovery in his app. I CANT when i click on bp tools. Any suggestions? Am i missing anything?
Sent from my DROID3 using Tapatalk

jarzy00 said:
I recently found out that i was using the wrong d3 bootstrap. It was the first one hashcode created. So i uninstalled recoverys and deleted it. I downloading koush's bootstrap and installed it (the one with the red skull) I CAN get in cwm recovery when i click reboot recovery in his app. I CANT when i click on bp tools. Any suggestions? Am i missing anything?
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
Hashcode actually made the "second" version of the Droid 3 Bootstrap, and it is this tweaked version by Hashcode that allows us to boot into BPtools by pressing the power button + M when booting the phone.
Koush's Bootstrap is what we find on the Android Market, and it does not allow manual booting into BPtools. So, either you got the Dev names mixed up or you have the apps mixed up. They both have the red skull icon.
Hashcode's Tweaked app is what you should definitely use, as Koush's will only boot you into Recovery if a bootloop is detected (but many have said that more often than not, the detection doesn't work 100% of the time, leaving you with a soft-brick).
EDIT: Here's the link found in the Droid 3 Development Forums to Hashcode's Tweaked Bootstrap.
http://forum.xda-developers.com/showthread.php?t=1289254
SECOND EDIT: Make sure to uninstall your current Bootstrap and delete your current Nandroid backups prior to installing this one and making a Nandroid with it.

Slightly off topic, but not totally. The other day when trying to flash a zip from the uot kitchen,I had the CWM get kinda buggy on me. When I selected reboot all I got was the pic of the box and the little Droid dude. Had to batt pull to get out of CWM. Anyone know why. I've flashed several zip from the kitchen and that's never happened before.
Sent from my rooted xt860

Wow this was exactly the type of answer i was looking for. Thanks alot i appreciate it. Everything works perfectly. Oh and thanks for the second edit: that helped too!
Sent from my DROID3 using Tapatalk

jarzy00 said:
Wow this was exactly the type of answer i was looking for. Thanks alot i appreciate it. Everything works perfectly. Oh and thanks for the second edit: that helped too!
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
You're very welcome! I'm fairly new at this myself but I learn a lot everyday just from reading the threads around here. Glad I could help.

[Q] Finallly rooted my N1 - so what is next for a new ROM?

Well after having my N1 for two years (I bought it on launch day) I finally got up the never to root it using this process.
http://forum.xda-developers.com/showthread.php?t=1319653
Had a few heart stopping moments as the script hung until I realised that while I had download the SDK to get the USB driver I hadn't actually installed the driver for the phone.
Confirmed that it was rooted by downloading Titanium Backup and doing a backup.
For a new ROM (as yet undecided) is a Titanium Backup good enough or should I also do the cyanogenmod clockworkmod recovery?
Should I be able to restore my apps and settings after the new ROM using the Titanium Backup?

You wanna do a Nandroid or Full Image Backup with Clockwork. Titanium is just as you said apps and data. Although, I think CWM has a system bu option. Don't use CWM anymore use Amon_Ra. So not up on steps. The post 3.0 CW's have had issues and are documented.
You can restore apps and data at any time with Titanium, but I think to do system stuff you need to be restoring to same rom.
I highly recommend Nandroids and sdcard backups before doing any new flashing.
Start with CM7 roms the stable ones, then move on. Read OP pages fully and scan threads front to back for info/problems etc
Ken

Which recovery is user friendly for newbies like me.
Sent from my Nexus One using Tapatalk

n1newbie said:
Which recovery is user friendly for newbies like me.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Download rom manager from the market and install clockwork recovery.
Sent from my Nexus One using XDA App

camalus said:
Download rom manager from the market and install clockwork recovery.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Clockwork is probably the best and easiest to use.

scgolfer7 said:
Clockwork is probably the best and easiest to use.
Click to expand...
Click to collapse
But i hv read many ppl complaining abt the problem with their sd card partition due to cwm? ??
Sent from my Nexus One using Tapatalk

use the pre 3.0 versions

Let's try Amon_RA Recovery
Best recovery by far. Never any issues. Been using this version for months and months. Perfect with flashing, backing up, restoring, and partitioning.

are you experienced with fastboot commands adb etc

The downside with Amon_RA is it doesn't give you the option to wipe the /system partition. I have stuck with a pre-3.0 version of ClockworkMod for this reason. There is a new recovery out there called 4EXT that is based on ClockworkMod, but doesn't have the issue with corrupting partitions. He has also added a TON of new features. This does seem to be the best on out there now. He even just released a touch-based version. The thread is in the development section.

[Q] How safe is safestrap?

I think I understand how safestrap works (it installs some kind of hijack to boot /preinstall instead of booting /system) but I have been reading a number of users who have bricked their phone...
I basically have the SafeStrap install screen up, but am hesitant to do this...
Just a few questions before I take the plunge
1) Why are so many users having problems with safesrap? I download the Droid3 version 1.08 for use on my Bell Motorola XT860 4G
2) What exactly does safestrap do in the boot loading sequence? If this is not public knowledge (and might be worked out "against" please, no harm, I'm just wondering, so if I could get an idea as how the hijack works, either in the thread or PM that would help greatly)
3) If you restore the original system and disable the hijack, will that really bring me back to complete original stock? What if they patch the boot partition as they did last time?
Thanks for all your help guys! I know a lot of you have been using custom roms, I really want to load up ICS on here, and it's almost ready for prime-time so I just want to be prepared!

First off, I have an XT862 not the XT860. The hijack is a 2nd init hijack. Safestrap does this hijack itself as opposed to with bootstrap where whatever ROM you flash has to do the hijack. Safestrap also as you mentioned uses /preinstall to store /system of the ROM you flash. This means that nothing other than safestrap itself touches your stock /system. This allows safestrap to protect itself so you can always get back to recovery even if there is a bad flash it can't overwrite the hijack and recovery so you can try again.
I also don't remember seeing much of problems with safestrap itself other than a partition size problem. I think I remember seeing that some update took care of that problem. I have seen people having more problems with ROMs on the XT860 than other versions of the phone.

danifunker said:
I think I understand how safestrap works (it installs some kind of hijack to boot /preinstall instead of booting /system) but I have been reading a number of users who have bricked their phone...
I basically have the SafeStrap install screen up, but am hesitant to do this...
Just a few questions before I take the plunge
1) Why are so many users having problems with safesrap? I download the Droid3 version 1.08 for use on my Bell Motorola XT860 4G
2) What exactly does safestrap do in the boot loading sequence? If this is not public knowledge (and might be worked out "against" please, no harm, I'm just wondering, so if I could get an idea as how the hijack works, either in the thread or PM that would help greatly)
3) If you restore the original system and disable the hijack, will that really bring me back to complete original stock? What if they patch the boot partition as they did last time?
Thanks for all your help guys! I know a lot of you have been using custom roms, I really want to load up ICS on here, and it's almost ready for prime-time so I just want to be prepared!
Click to expand...
Click to collapse
First off, the most common problem I have seen people have with safestrap is not understanding what it does and even more common is not knowing how to use it, basically a lot of user error. The previous poster summed up pretty well how it works. Finally, uninstalling safestrap will NOT bring you back to original stock, it will remove itself and the secondary ROM it allowed you to install. Since you have to be rooted to even install it, if you uninstall it you will still be rooted, not stock.
Just so you are clear, you can have whatever ROM you want on your phone BEFORE installing Safestrap and this will become the Safe system by default. You will no longer be able to change this ROM as long as Safestrap is installed. Instead, it allows you to put another ROM, basically a dual-boot, in addition to the original rom you have. Now you have a Safe system and a Non safe system. The Non safe system is the only one Safestrap will allow you to change (and brick for that matter). So if/when you install a ROM that boot loops or crashes, you simply can revert back to your safe system and now your phone works again, neat huh?

AFAIK, he does have the XT860, since the XT862 is the Verizon Droid 3 (3G, not Bell Canada 4G). Also, using it on my 862, I have not been able to brick it. If flashing the experimental system fails, you can just reboot into the Safestrap menu and flash something new. I don't see why it wouldn't work on the 860, as all it does it modify the booting. Any issues would most likely be caused by a ROM flashing issue, not safestrap.

I took the plunge this afternoon... Installed SafeStrap and CM9 nightly on my device... Not sure if everything is working just yet, but will be doing testing throughout the day
No problems were reported with the installation or instructions, so that's great. Thanks a lot!

I'm using a XT860 (Brazilian Vivo, but I'm not sure if it's 4G - LTE - compatible, I know that it works with 3.5G).
I have Safestrap 3.0.5 installed and I'm using all the 4 slots (MavROM, Minimoto, CM9 e CM10). All of then runs well (with their particular issues), none of them caused any trouble on the phone.

Thiago AmP said:
I'm using a XT860 (Brazilian Vivo, but I'm not sure if it's 4G - LTE - compatible, I know that it works with 3.5G).
I have Safestrap 3.0.5 installed and I'm using all the 4 slots (MavROM, Minimoto, CM9 e CM10). All of then runs well (with their particular issues), none of them caused any trouble on the phone.
Click to expand...
Click to collapse
Same here. I'm using it on a Brazilian TIM, no problems at all. I have two active slots( Stock, Gummy 0.90) and two for testing.
It is in fact the best recovery that I've used, so far.

Thiago AmP said:
I'm using a XT860 (Brazilian Vivo, but I'm not sure if it's 4G - LTE - compatible, I know that it works with 3.5G).
I have Safestrap 3.0.5 installed and I'm using all the 4 slots (MavROM, Minimoto, CM9 e CM10). All of then runs well (with their particular issues), none of them caused any trouble on the phone.
Click to expand...
Click to collapse
None of the d3 variants are LTE capable
Sent from my DROID3 using xda premium

Endoroid said:
None of the d3 variants are LTE capable
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Yeah, I realize that before reviewing its radio specs.
Munckster said:
Same here. I'm using it on a Brazilian TIM, no problems at all. I have two active slots( Stock, Gummy 0.90) and two for testing.
It is in fact the best recovery that I've used, so far.
Click to expand...
Click to collapse
@Munckster
Actually, after trying to acess a SD Card partition with Link2SD, I lost acess to Recovery. I'm stuck on the stock ROM (root keeps on, but SafeStrap 3.05 doesn't work).
Installed Titanium Backup to keep my data safe, but it isn't working too. I'm going to reinstall it later.
I'm afraid that I'll have to uninstall all my root apps, unroot the phone and do all the process again...
I'm very newbie at linux and Android and I'm doing all that by reading (a lot). I'd apreciate if someone could tell how to deal with this problem.

Thiago AmP said:
Yeah, I realize that before reviewing its radio specs.
@Munckster
Actually, after trying to acess a SD Card partition with Link2SD, I lost acess to Recovery. I'm stuck on the stock ROM (root keeps on, but SafeStrap 3.05 doesn't work).
Installed Titanium Backup to keep my data safe, but it isn't working too. I'm going to reinstall it later.
I'm afraid that I'll have to uninstall all my root apps, unroot the phone and do all the process again...
I'm very newbie at linux and Android and I'm doing all that by reading (a lot). I'd apreciate if someone could tell how to deal with this problem.
Click to expand...
Click to collapse
Try shutting the phone off and powering up while holding m, then using vol down select bp tools from the list that appears, and confirm with vol up.
Sent from my DROID3 using xda premium

Endoroid said:
Try shutting the phone off and powering up while holding m, then using vol down select bp tools from the list that appears, and confirm with vol up.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
I've already tried it, but without success... I'll keep searching what to do in this situation...

Thiago AmP said:
Actually, after trying to acess a SD Card partition with Link2SD, I lost acess to Recovery. I'm stuck on the stock ROM (root keeps on, but SafeStrap 3.05 doesn't work).
Installed Titanium Backup to keep my data safe, but it isn't working too. I'm going to reinstall it later.
I'm afraid that I'll have to uninstall all my root apps, unroot the phone and do all the process again...
Click to expand...
Click to collapse
Unrooting seems like overkill. If you are "stuck" on stock, I would just start the Safestrap app. Click the button to uninstall recovery and restart the phone. Then open Safestrap again, click the button to install recovery, and restart the phone. Hopefully the Safestrap menu will show and you can then activate recovery.
So long as you do not erase anything on the internal storage, your slots should still be there.

doogald said:
Unrooting seems like overkill. If you are "stuck" on stock, I would just start the Safestrap app. Click the button to uninstall recovery and restart the phone. Then open Safestrap again, click the button to install recovery, and restart the phone. Hopefully the Safestrap menu will show and you can then activate recovery.
So long as you do not erase anything on the internal storage, your slots should still be there.
Click to expand...
Click to collapse
I've tried it several times before I came with the idea of unroot my phone and redo the process. Here is my dicoveries http://forum.xda-developers.com/showthread.php?t=2082292
I know that it's obvious, but I guess that just few people knew that it would work.

SafeStrap problems
Odd problem, I can't get the menu button to work. In order to get back to my "safe" rom I have to start safestrap,and select uninstall recovery.
Then reboot, and it will bring up my "Safe" rom. If I then go back to SafeStrap, and re-install the recovery, and reboot, it will again bring up SafeStrap, but if I hit Menu, it doesnt' bring up any options it again boots up my non-safe ROM (minimoto 1.6)
Anyone have any ideas...I guess I can try to remove the safestrap directory on the sdcard after I uninstall the recover, and then try to reinstall the App, and try all over again?

Guide?

A friend of mine has Droid 3 on Verizon. I'm want to know what I need to do to flash a recovery on it so I can backup and flash roms on it. I'm not sure if I need a custom bootloader for it aswell. I found this thread with recovery as a sticky but it doesn't have much explanations in it. I also see you guys don't have a sticky with a guide anywhere besides just the one click root.
Can anyone point me in a direction?
Thank you.

On my phone so I can't give links. But you need safestrap. It's a bootstrap that will essentially allow your phone to boot into recovery even with the locked bootloader.
Safestrap is unique because it does not touch your primary system. You can back it up, but you flash everything to a "safe" system. It is ideal because no matter what you doing to your safe system, your primary will always be there. Even if you flash something that you know will brick your phone, all that will happen is that you won't be able to boot into your safe system. You can still load up your custom recovery and switch back to your primary system where you can download a different ROM.
Sent from my DROID3 using xda premium

slayer621 said:
On my phone so I can't give links. But you need safestrap. It's a bootstrap that will essentially allow your phone to boot into recovery even with the locked bootloader.
Safestrap is unique because it does not touch your primary system. You can back it up, but you flash everything to a "safe" system. It is ideal because no matter what you doing to your safe system, your primary will always be there. Even if you flash something that you know will brick your phone, all that will happen is that you won't be able to boot into your safe system. You can still load up your custom recovery and switch back to your primary system where you can download a different ROM.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
So how do I install this safe strap and where do I get it. I assume this will also let me flash a custom recovery like CWM?

Everything you need to know on installing safestrap can be found here
There are 2 versions. One is the standard version in the link, the other is a "tweaked" version found on the forums here. While the tweaked version has a few extra features, from what I've read, it can be a bit unstable. Use the version provided in the link.

Yeah what he said ^^^ then once u have the safestrap you just download the rom u want and flash it and your good to go
Sent from my XT883 using Tapatalk

Ok. So far I can understand that the Moto Droid 3 has a locked boot loader which can not be unlocked. Correct?
I can understand using a bootstrap instead. Can someone explain what happens to your first system when the safe mode is turned on? Does it move the contents into the available internal SD card? What kind of memory is emmc? Also, I'm not clear on what is hijack. Is that just the initial hack from the apk on 1st system? I assume one can install it again in the 2nd system and mess things up.

obsanity said:
Ok. So far I can understand that the Moto Droid 3 has a locked boot loader which can not be unlocked. Correct?
I can understand using a bootstrap instead. Can someone explain what happens to your first system when the safe mode is turned on? Does it move the contents into the available internal SD card? What kind of memory is emmc? Also, I'm not clear on what is hijack. Is that just the initial hack from the apk on 1st system? I assume one can install it again in the 2nd system and mess things up.
Click to expand...
Click to collapse
The 1st system gets renamed to systemorig and is otherwise left untouched. /reinstall gets renamed to /system and becomes your safe mode system. Im not 100% on hijack but as I understand it, it quite literally hijacks the boot sequence at a certain point by killing all the processes and inserting its own in order to give us a custom recovery
Sent from my XT860 using xda premium

OK. So why not just backup the original system and overwrite it? If the partition gets renamed why is there a need to keep it? Wouldn't deleting it give more room for roms? Is there even enough room for 2 partitions on the emmc?

The whole idea was that you keep your original system intact so you can still receive OTA updates. I've never had an issue with not having enough room for roms. They are only about 150 MB.
Many of us actually use this to dual boot. The common way is to have a stable rom on your /systemorig and test new roms on safe system.
There is a plain old bootstrap that installs regular old cwr and just overwrites /system. Everything should be compatible with it. I think I have a copy of it in my dropbox
The main reason for using safestrap(in my view) is that when you're messing around in safemode its next to impossible to brick your phone so bad you can't access recovery, since when it first boots it still boots from /system, and then redirects to the safe system. You should never have to fastboot flash your phone
Sent from my XT860 using xda premium

So can you dual boot? And how do you boot into your orig 1st system? Don't you have to toggle the safe mode each time? Also, how much total room is there on emmc on D3?

try here :
http://forum.xda-developers.com/showthread.php?t=1436380

The internal SD memory is roughly 11GB. The phone stores which system was last booted and then you can backup and restore between them though the SafeStrap pre-boot recovery. Once you try it, it's really simple and effective. I was hesitant to leave old faithful bootstrap, but now that I'm on safestrap, I wonder why I ever hesitated.

So the 1st system is simply copied to SD storage when the safe mode is turned on?

Also, do I download ver 1.09 which says Droid 4? I have a Droid 3.

obsanity said:
So the 1st system is simply copied to SD storage when the safe mode is turned on?
Click to expand...
Click to collapse
It creates a backup of /system and /data when you switch between safe and non safe. And I think also /cache. However as I mentioned before it renames /system to systemorig.
Sent from my XT860 using xda premium

It runs off the /preinstall partition IIRC. You should/can DL the original from Hash's blog or get Rick's tweaked version from the Dev section.

I downloaded and installed ver 1.0.8 because the other 1.0.9 said Droid 4.

obsanity said:
I downloaded and installed ver 1.0.8 because the other 1.0.9 said Droid 4.
Click to expand...
Click to collapse
I do believe that's the correct version. I'm running a tweaked version that includes a bash console and a redesigned ui but its kinda buggy atm so for now I would recommend the one you've got
One other thing I should point out, as this is a common mistake, the first time you switch to safe mode you HAVE to flash a rom. Because you're now running off the /preinstall, there is no safe mode rom yet. A lot of ppl switch to safe then boot up straight away and all you get is a blank screen cause you're booting...well nothing
Also I'm not sure if you have a rom in mind already but mavrom is the only gb rom that still gets updates. Everyone else is deving ics, however all ics roms are beta and have more or less the same bugs/missing features
Sent from my XT860 using xda premium

Endoroid said:
I do believe that's the correct version. I'm running a tweaked version that includes a bash console and a redesigned ui but its kinda buggy atm so for now I would recommend the one you've got
One other thing I should point out, as this is a common mistake, the first time you switch to safe mode you HAVE to flash a rom. Because you're now running off the /preinstall, there is no safe mode rom yet. A lot of ppl switch to safe then boot up straight away and all you get is a blank screen cause you're booting...well nothing
Also I'm not sure if you have a rom in mind already but mavrom is the only gb rom that still gets updates. Everyone else is deving ics, however all ics roms are beta and have more or less the same bugs/missing features
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
I just did it on his phone. All worked OK. Thanks for all your help. I'm used to the nexus devices which are much easier and straightforward. I installed nightly CM9 from hashcode. I'm not sure what works yet. Is there a better version of CM9 besides that one? He really wants ICS and CM.

All of the ICS roms are currently limited in the same way: no HW codecs, bluetooth on but not connected = loss of audio, etc. There's a thread here in the general section that compares all of the ICS roms. I would advise looking through it and deciding which one suits you best.
EDIT: to answer your question, the may 7 build of Hashcode's CM9 is a good build. They just brought back the theme engine so that opens up possibilities.
Sent from my DROID3 using xda premium

I'm an idiot please help

So in my infinite wisdom I deleted com.android.providers.media using titanium backup. I thought I had backed the file up but apparently I didn't. Either that or it didn't actually back the file up. Either way elements of my phone are now totally burned as you would imagine. No gallery, no music in my music player, and no ringtones. So my question is even if I do a factory reset will that help? Yes this was the stock ROM yes I tried installing a stock image on top of the ROM but the installation froze and I had to reboot and restore my nan droid. No I didn't have a nandroid of before I started dicking around. And finally yes I am a complete idiot. Any help would be much appreciated.
Sent from my MB886 using xda premium

Actually if some one would just be willing to use titanium backup to backup that file then post it here I could probably just restore it? Hope some one can help
Sent from my MB886 using xda premium

Odexed\deodexed....ICS\JB...Stock\Custom....Bell\ATT\Other...not much to go on...either way, go to the Batakang FTP and download which rom you need and you'll always have a backup copy of all the files needed (the bottom two). If your not AT&T, then you can get deodexed versions on my Goo.im page or odexed versions directly from the fastboot.

Sweet thanks man. So would u say that I should safely be able to install over the stock ROM? Or should I wipe then install? Also since these are stock I can install them to ROM slot stock right?
Sent from my MB886 using xda premium

skeevy420 said:
Odexed\deodexed....ICS\JB...Stock\Custom....Bell\ATT\Other...not much to go on...either way, go to the Batakang FTP and download which rom you need and you'll always have a backup copy of all the files needed (the bottom two). If your not AT&T, then you can get deodexed versions on my Goo.im page or odexed versions directly from the fastboot.
Click to expand...
Click to collapse
Hey, so I've been doing a lot of research on safe strap and apparently you cannot overwrite the stock ROM slot which would be why I couldn't flash anything to it. So what I did was create a new slot (slot 1) with the stock image. I installed safestrap to that new ROM. My question now would be, If I create a nandroid of that ROM and restore it to the stock slot will that work? Or will it bork due to not having safestrap recovery installed to the system partition anymore and there for stop it from booting along with killing safestrap? Hoping some one can chime in on this one as I'm quite anxious to get back to normal phone use. at least for now all my sounds are back but having a 1 gig system partition is a major bummer.

metalmike6 said:
Hey, so I've been doing a lot of research on safe strap and apparently you cannot overwrite the stock ROM slot which would be why I couldn't flash anything to it. So what I did was create a new slot (slot 1) with the stock image. I installed safestrap to that new ROM. My question now would be, If I create a nandroid of that ROM and restore it to the stock slot will that work? Or will it bork due to not having safestrap recovery installed to the system partition anymore and there for stop it from booting along with killing safestrap? Hoping some one can chime in on this one as I'm quite anxious to get back to normal phone use. at least for now all my sounds are back but having a 1 gig system partition is a major bummer.
Click to expand...
Click to collapse
That's where I'm at. On my stock rom, /system/etc/safestrap was added, logwrapper was modified to execute 2nd-init. AFAIK, that's all that was added. I'm so used to the Defy bootstrap method that I'm having a hard time getting used to SS - Defy BS was clearly laid out on what was executed and when that was done -- I've even looked at the SS source and its scripts and still can figure out what's the first script called by the 2nd-init loader....makes me feel super noob .

Well supposedly hash code said that after every restore and flash to the safe slot (stock) safe strap will reinstall itself on /system so if that's the case restoring any backup to that safe slot should be OK. But if that were the case no one would be able to brick. And I've seen people brick with and lose safestrap, and have to use RSD. Which is the road I don't want to have to go down. Really wish I had a definite answer because it seems like it should work but I don't want to do it unless some one who knows more about this than me confirms it.
Sent from my MB886 using xda premium