So, I've been looking at installing some different ROM's on my rooted D3 and have seen reference to the following bootstrappers on different forum posts and websites.
I've seen:
"Droid 3 Safestrap" Bootstrap
Koush's Bootstrap
hashcodes modified bootstrap
My question(s) are:
Is there any advantage/disadvantage to using one of the above over another?
I currently have the Droid 3 Bootstrapper installed on my phone, is there a anyway for me to determine if the bootstrapper that I have is anyone of the above?
Thanks.
Koush's bootstrap is the "normal" bootstrap. It has a bunch of red in the image and some.crazy looking android dude. The modded says [tweaked] on the lower portion of the screen but otherwise looks the same as the aforementioned . I've never used the safestrap as its more meant for flashing ROMs and my device has no ROMs but I believe it looks much different
Sent from my rooted xt860
Related
Im working on 4 or 5 roms right now, and seem to be having some strange errors, and issues while trying to use CWM to flash roms and kernals.
Kernals Im using
Boushh's Khasmek Voodoo v4, v405, v409, and v5.0
In that I get various builds of CWM
I have also used whatever CWM comes with the Verizon Bootstrap Program.
Roms I am working with are Based on DJ11, ECO2, and a Gingerbread port to hopefully be released this week.
Now, couple things...
If I do a manual recovery boot by holding power+Vol Up I get no sd card support, and will have to go to Advanced/Reboot Recovery in order to not only see an SD Card, but to install something, kernal or Rom
I also, upon typing this have seemed to have noticed a new bug where I choose to reboot system after install, only to have it go back to cwm no matter what I clear.
Also, I noticed various CWM's will also just not allow me access at all, period. It will appear on the screen for 3 sec, then black, but pressing the power button only brings it back up for 2 seconds.
Any ideas as to whats going on?
Nevermind. I had a bad cwm from a cdma cm7port that i forgot to flash back over
Sent from my SCH-I800 using XDA App
Recovery help
I just purchased a VZW Galaxy Tab with EC02 installed. I got it rooted and would like some help to move further. I have read many threads and different forums but I can not find a definitive way to install CWM. I see you mentioned Verizon Tab Bootstrapper and wanted to know if this worked for you. I purchased it for $2.99 in the Market but I am hesitant on proceeding. I have read too many issues after installing the bootstrapper. Screen rotation, camera issues, etc..... Did you encounter any issues?
I would really appreciate any help you can provide.
Thank you in advance.
I know people hate these threads, but I have done as much research as I could before posting, and just want to confirm if my understanding is right...
I have a Canadian (Bell) XT860 -- don't worry, it's fine.
We now have options to restore this phone from a bricked state by flashing (using RSDlite?) either a Brazillian 2.3.5 image, the ME863 image, or a third that was mentioned but I could never find.
My understanding of this as far as development goes is that we don't have a safestrap that works yet, which prevents truly custom android f/w from being made for our phones... but as we do have an option for recovering from a bricked state, people can be more adventurous without worrying nearly as much.
Am I missing or wrong on anything here?
Yes, RSDLite is the program you would use to flash a stock SBF to your XT860.
There is the Chinese ME863 rom, and most recently the Brazilian XT860 rom. What is this 3rd one you heard of... where is it from, which carrier?
Safestrap didn't seem to work for XT860 (I think) or ME863 rom users (this one I'm sure of, as I tried it myself), but I recall when I was on my stock Bell XT860 rom, Bootstrap worked (problem was, there weren't any ROMS to play with - and I believe there still aren't any roms yet.) Hopefully this Brasil stock rom will help move things forward.
Until we get "SBF" that can bring us back to original Bell firmware, we can't really get truly "adventurous", since there is no way to bring phone back to factory state if you have to send it for service. Let's hope such recovery will be leaked/found for us soon and we can really get adventurous.
Accophox said:
My understanding of this as far as development goes is that we don't have a safestrap that works yet, which prevents truly custom android f/w from being made for our phones... but as we do have an option for recovering from a bricked state, people can be more adventurous without worrying nearly as much.
Am I missing or wrong on anything here?
Click to expand...
Click to collapse
I've been talking to Hashcode on and off on IRC for the past few weeks and we've been messing around with my bell xt860 when he's had the time. Unfortunately with his ICS port, patching safestrap (Hashcode mentioned just last night that he believes he's traced down the problem with safestrap on the xt860) etc he's extremely busy. He's mentioned a few times that he's working on a project or two for the xt860 that should get us moving along (ie patching safestrap I think), hopefully it's enough to know that devs(Hashcode) are still looking into the issues we have on the xt860.
With that being said, I have an idea or two I'm gonna try out here. I'll post results when I'm done. There are also a lot of other bright people who are giving things a shot, a few people are recompiling modules and trying to get cm7 working etc, it's ongoing but no ones had any progress to report yet unfortunately. It is ongoing though
Edit:No love, bricked for the moment. I've tried building and flashing a few roms, some I knew wouldn't work but a few had no reason not too, like a bell xt860 rom but for some reason all end with same results, sitting at the "M", not reaching the boot animation. Some difference between the verizon and our model in terms of boot.
Okay, thanks for the clarification everybody.
So - we're just missing a way to get back to Bell XT860 from Brazil/China XT860, but the workaround seems like it's just a matter of getting recovery to work and flash backups of the original software.
And - it sounds like we're fairly close to a breakthrough in getting bootstrapping enabled, which means that we're hopefully not too far off from a de-blur'd XT860.
Accophox said:
Okay, thanks for the clarification everybody.
So - we're just missing a way to get back to Bell XT860 from Brazil/China XT860, but the workaround seems like it's just a matter of getting recovery to work and flash backups of the original software.
And - it sounds like we're fairly close to a breakthrough in getting bootstrapping enabled, which means that we're hopefully not too far off from a de-blur'd XT860.
Click to expand...
Click to collapse
One of the problems we might run into is not being able to flash back to our bell kernel without an sbf from bell.
..as well as the Radio Firmware. Those can only be restored by SBF
Just to thank willis and endoroid I succesfully installed safestrap and liberty rom
the only thing its that it gives me an error when I switch to spanish language (I'm from mexico) on com.android.settings when selecting applications menu..
And also market closes.
XT860 Liberty ROM rooted and overclocked to 1200
goalando said:
Just to thank willis and endoroid I succesfully installed safestrap and liberty rom
the only thing its that it gives me an error when I switch to spanish language (I'm from mexico) on com.android.settings when selecting applications menu..
And also market closes.
XT860 Liberty ROM rooted and overclocked to 1200
Click to expand...
Click to collapse
I saw.on the liberty thread some other ppl have had market FC issues. Apparently the.solution is to just keep reflashing until it fixes. Although you may.wish to try clearing market data.first to see.if that clears it up
Sent from my XT860 using xda premium
Clearing market data doesn't help, along with force closing.
Happens when you start trying to download an app... then just cyclic FC.
It's just reflashing and praying. (I got it on the second attempt)
Well now im using steeldroid it works perfect
So I rooted my old milestone today with intentions of installing a custom rom. After not being able to install rom manager I searched for other options. I tried adb and droid explorer but nothing is working.. I attempted installing a vulnerable img with rsd lite until I discovered it was for a853 milestones not a854. Anyways, does anyone have any idea how to get rom manager or at least clockwork recovery on the milestone? Its not on the market and wont install using the apk so I'm stumped. If not, does anyone have any other ideas of how to get a custom rom on here? I have the android sdk and adb installed, busybox installed, droid explorer installed, but I cant figure this out. Thanks in advance..
blackhous3 said:
So I rooted my old milestone today with intentions of installing a custom rom. After not being able to install rom manager I searched for other options. I tried adb and droid explorer but nothing is working.. I attempted installing a vulnerable img with rsd lite until I discovered it was for a853 milestones not a854. Anyways, does anyone have any idea how to get rom manager or at least clockwork recovery on the milestone? Its not on the market and wont install using the apk so I'm stumped. If not, does anyone have any other ideas of how to get a custom rom on here? I have the android sdk and adb installed, busybox installed, droid explorer installed, but I cant figure this out. Thanks in advance..
Click to expand...
Click to collapse
WRONG FORUM urs is milestone 2 this is for A853 and A855
Are you sure? Mine is identical in looks to the og Droid... its an a854 I don't think its a milestone 2.
Sent from my Nexus S using XDA App
A853=MILESTONE & A855 =DROID now how can A854 be the same?
Do you want me to take some pictures? I'm not retarded. Its a Canadian CDMA version of the Droid and they call it the Milestone. If you don't know what I'm talking about then GTFO.
Sent from my Nexus S using XDA App
http://forum.xda-developers.com/showthread.php?t=912490 here's a basic guide i found on the web to root and install roms on your phone
A855 = Droid - CDMA (custom kernel bootable)
A853 = Milestone - GSM (no custom kernel bootable due to signature check)
A854 = later, non-Verizon Droid that is (unfortunately) also called Milestone - CDMA (custom kernel bootable)
If you have an A854, follow the guides for Droid, not for Milestone.
Btw., if you really have an A854 that is GSM, then you're really special and alone on the planet .
Meant CDMA sorry.
I've looked at a few Droid guides but just can't get a custom recovery to flash.
Sent from my Nexus S using XDA App
The screen backlight on my D3 took a crap so I called it in and got a replacement. To my surprise, they gave me a brand new one instead of a refurbished or "reconditioned" phone. To my *even greater* surprise, the .906 update was already installed. My question is this: do safestrap and AOSP ICS or AOKP ICS support the .906 update? Also, what do I do if something happens? I am not aware of any available SBF for the .906 system. What needs to happen for the fastboot files to be made available? Any answers are much appreciated.
Hello I don't know about ICS but I've allready updated my droid 3 too with .906 and then I install safestrap and voila I've been back to Maverick ROM(my back up)
I guess safestrap has boot my droid 3 to my back up partition. I will try installing ics on this safe system.
You have to root with the D4 root tool I believe. Other than that, IIRC, it's no different.
yes i have tried many things before posting here....
used to have a droid x and ran liberty on it.
um, lets see i tried to boot my droid 3 with a ROM based on 4.2 (i think it said its compatible with my version, 5.7.906.XT862.en.US.
its like cyanogenmod 10 or something like that.
here is what i did after having rooted of course:
-installed droid 3 bootstrap
-backed everything up using said app
-downloaded the ROM i wanted
-installed ROM manager
-installed the ROM i wanted.
to my surprise when the phone booted back up it was basically stock. it had all the stock apps that come with the phone, except certain things were not working right even then. i could not access google play. i could not access 3g i dont think, it seemed to be running on 1x or something.
tried holding m+power button and i tried a few options in that menu, none of which would properly boot my droid 3 bootstrap.
any idea what the heck happened?
Hello.
The CM10 roms can not work with bootstrap. You need safestrap 3.0x to install them.
I would suggest you go back to stock using SBF:http://forum.xda-developers.com/showthread.php?t=1686911
After that, root, and install safestrap 3.05.
From there you can install any rom you want (GB, ICS, JB).
Do note that only GB roms are fully functional. None of the JB builds have camera and the ICS builds aren't nearly finished
DoubleYouPee said:
Hello.
The CM10 roms can not work with bootstrap. You need safestrap 3.0x to install them.
I would suggest you go back to stock using SBF:http://forum.xda-developers.com/showthread.php?t=1686911
After that, root, and install safestrap 3.05.
From there you can install any rom you want (GB, ICS, JB).
Do note that only GB roms are fully functional. None of the JB builds have camera and the ICS builds aren't nearly finished
Click to expand...
Click to collapse
yea i dont necessarily use the camera on mine, but i did note that before trying to install it. thank you for your help i am installing the SBF right now. hopefully this works.
Don't use rom manager for the D3
Sent from my DROID3 using xda premium
Yeah you need Safestrap 3.0.5 not bootstrap you can grab it here, http://goo.im/devs/hashcode/solana , make sure to uninstall bootstrap before installing safe strap
okay i got steeldroid a gb version of it installed and it works fine
but how do i get ICS and JB versions installed? i tried both in slot 1 and neither would work properly i just got boot loops im assuming i need firmware but i havent seen any downloads or ways to update my phone.