Related
Hi everyone. I'm the proud owner of a new Droid 3, and I have some questions about ROMs and stuff that I'm hoping someone can answer:
1. As I understand, the Droid 3's bootloader is locked. As I understand it, the /boot partition is signed and we can't modify it, right? Are any other partitions signed this way? What about any kind of encryption or something on the partitions? I read somewhere that certain Motorola phones with OMAP chipsets have encrypted stuff. Is the Droid 3 one of these devices? If so, what is encrypted?
2. What ways around whatever verification on the device exist? Is 2nd-init a technique used on this device, like on the Droid 2 and other Motorola phones?
3. As I understand it, SafeStrap boots the phone from /preinstall, not system, and leaves /system intact when flashing stuff. Is this correct? What's the point? Every other Android device I've used doesn't have anything like that (afaik). And why doesn't it do the same for /data?
4. On the topic of SafeStrap, if I wanna dual boot Motoblur and Cyanogenmod, can I? (I know this is possible on the Bionic, so I'm assuming the same is true for the Droid 3) How?
5. This phone supports fastboot commands, which is unusual for Motorola devices, right? What would happen if I issued it a "fastbook oem unlock" command?
6. What is "BP," as in "BP Tools?"
Thanks a ton
-Zane
ZaneKaminski said:
Hi everyone. I'm the proud owner of a new Droid 3, and I have some questions about ROMs and stuff that I'm hoping someone can answer:
1. As I understand, the Droid 3's bootloader is locked. As I understand it, the /boot partition is signed and we can't modify it, right? Are any other partitions signed this way? What about any kind of encryption or something on the partitions? I read somewhere that certain Motorola phones with OMAP chipsets have encrypted stuff. Is the Droid 3 one of these devices? If so, what is encrypted?
2. What ways around whatever verification on the device exist? Is 2nd-init a technique used on this device, like on the Droid 2 and other Motorola phones?
3. As I understand it, SafeStrap boots the phone from /preinstall, not system, and leaves /system intact when flashing stuff. Is this correct? What's the point? Every other Android device I've used doesn't have anything like that (afaik). And why doesn't it do the same for /data?
4. On the topic of SafeStrap, if I wanna dual boot Motoblur and Cyanogenmod, can I? (I know this is possible on the Bionic, so I'm assuming the same is true for the Droid 3) How?
5. This phone supports fastboot commands, which is unusual for Motorola devices, right? What would happen if I issued it a "fastbook oem unlock" command?
6. What is "BP," as in "BP Tools?"
Thanks a ton
-Zane
Click to expand...
Click to collapse
Hi Zane,
1. Yes, the bootloader is locked. And more than just the boot partition are signed. Recovery, System and a few others as well. I don't know about encryption support for the OMAP chipsets, but I do know that the chips can enforce the signatures and md5 type verification of partitions. I'm not sure that the Droid 3 is actually making use of this feature. I believe the signature is currently stored in a table on the cdt.bin partition. Several people have tried to edit that partition by hand, erasing the check for signatures on certain partitions and none have been successful.
2. For custom AOSP ROMs we are using a logwrapper hijack to 2nd-init the Droid 3 just like the D2.
3. You are correct. Safestrap uses the /preinstall partition as a 2nd-system. And I'm not sure why it's never been done before, but the idea behind Safestrap is fairly simple:
3a. How do we protect our ability to enter recovery (even after flashing system) when in almost all cases any system flash will over-write the hijack needed to enter recovery in the first place? Flashing a ROM on a locked phone is a touchy issue. And I can't count the # of "I'm bootlooped" or "I'm bricked" posts that you see on these boards because of that. This isn't the case with unlocked bootloaders. They ALWAYS have access to recovery and have a way out. And that makes flashing ROMs alot more fun.
3b. Enter Safestrap which is essentially a 2nd-system Bootstrap. It does the hijack to provide access to recovery and custom ROM booting. The ROMs don't have to worry about it. Safestrap is still in very early stages. The interface isn't as easy as it should be to use. I'll work on that as I get more time.
3c. You bring up a good point about "data". MotoBlur and CM7 have very different sets of userdata, and in some ways they're incompaible. Moto likes to throw security information on the /data partition in various spots and CM7 obviously doesn't do that. I have actually hung at the boot when swapping systems and not changing my user data around. I know there's a video of Deodexed doing this exact thing on his Bionic, but in most cases you can't just "flip the switch" on 2nd-system and boot up correctly. Currently, in Safestrap you need to backup your current ROM's data and then restore/wipe the data you want for the new ROM your going to. This process is time consuming and will be ironed out with the next release. It will perform a mini system-specific backup/restore of just userdata when you enable/disable the 2nd-system. I would have stuck the 2nd-system data on another partition ... if we had another spare one to use.
4. This is the current "default" setup for Safestrap. MotoBlur on the primary system and people are testing CM7 on the 2nd-system. You can download the files here:
http://hash-of-codes.blogspot.com/2011/10/beta-testing-safestrap-w-cm7.html
5. The fastboot oem unlock command doesn't work. Been tried.
6. BP = Baseband Processor. "BP-Tools mode" is special boot mode which opens access to the BP via Motorola Software and a USB cord. Most will never use it.
EDIT: Sorry for the wall of text.. good questions.
-delete- realized Hashcode gave a far better response that I could even dream up.
Sent from my DROID3 using xda premium
That was the best answer to any question (or, well, a bunch of questions) I've read in a long time. Thanks so much.
-Zane
jjhiza said:
-delete- realized Hashcode gave a far better response that I could even dream up.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Such good questions and such a good response are worthy of a sticky/faq imo
Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
jgardner said:
Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
Click to expand...
Click to collapse
Why not do the nandroid with safestrap?
I didn't think safestrap was working with the D4?
jgardner said:
I didn't think safestrap was working with the D4?
Click to expand...
Click to collapse
I dont know whats going on lol.....everyone is coming with all these different stories. I used the root exploit that was out and used the safestrap for recovery. I dont think I did anything different than anyone else. And then i took a chance flashing a Razr rom
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
jgardner said:
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I took it out until Hashcode brings it out for Droid 4. I've been corresponding with him and if the maker of Safestrap tells you it isn't safe to use on Droid 4 yet then you usually should listen.
All up to your risk though.
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
mattlgroff said:
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
Click to expand...
Click to collapse
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
As far as the warnings i didnt see the warning to not use safestrap till i got on here and it was to late. I figured since i was able to boot into recovery and make a backup i would be ok
Briteyez83 said:
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
Click to expand...
Click to collapse
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Which FASTBOOT error are you seeing? It should be referencing one of the partitions.
Sent from my DROID4 using XDA App
greekchampion04 said:
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Click to expand...
Click to collapse
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Briteyez83 said:
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Click to expand...
Click to collapse
I cant help unless I know what your error message says when you turn on the phone. :/
Sent from my DROID4 using XDA App
Send me your email addy in a message and ill send you a pic of it
Briteyez83 said:
Send me your email addy in a message and ill send you a pic of it
Click to expand...
Click to collapse
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Hashcode said:
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Click to expand...
Click to collapse
No, i dont. Im new to root, just rooted in nov. If you give me something thst would fix it that would be awesome.
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Hashcode said:
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Click to expand...
Click to collapse
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Briteyez83 said:
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Click to expand...
Click to collapse
If it works, I'll create a new thread with the instructions as I believe there are a few in your situation.
Yes there is quite a few. Ill let you know as soon as i can
Can't get into recovery or anything can someone help or point me into the right place to fix this just need to get the phone up and running the rest i can do root ect,,,,,
mobgod said:
Can't get into recovery or anything can someone help or point me into the right place to fix this just need to get the phone up and running the rest i can do root ect,,,,,
Click to expand...
Click to collapse
Does your phone turn on at all?
i can get into fastboot but thats about it
mobgod said:
i can get into fastboot but thats about it
Click to expand...
Click to collapse
maybe the correct files to flash or what i can do to just get the phone back to stock
mobgod said:
i can get into fastboot but thats about it
Click to expand...
Click to collapse
You will have to use RSD and fxz you phone back to stock. I was in you situation once tried using the bootstrap built for the razor. As long as you can access fast boot mode your alright. Here's the link where you can find the file you need. http://forum.xda-developers.com/showthread.php?t=132810
Get the. 902 fastboot file.
nobe1976 said:
You will have to use RSD and fxz you phone back to stock. I was in you situation once tried using the bootstrap built for the razor. As long as you can access fast boot mode your alright. Here's the link where you can find the file you need. http://forum.xda-developers.com/showthread.php?t=132810
Get the. 902 fastboot file.
Click to expand...
Click to collapse
I've tried that keeps failing with rsd step 6 I believe the first time I got to step 20 than all hell broke lose I believe it was something about web top. Should I just try 902 again is what your telling me ? Also big question is how can I charge the battery I'm getting low battery in fastboot ??
Sent From My Rooted 3D
mobgod said:
I've tried that keeps failing with rsd step 6 I believe the first time I got to step 20 than all hell broke lose I believe it was something about web top. Should I just try 902 again is what your telling me ? Also big question is how can I charge the battery I'm getting low battery in fastboot ??
Sent From My Rooted 3D
Click to expand...
Click to collapse
You might have bad partitions. That might be pretty hard to fix with only rsd light you might have to make your own fxz flashable zip to repartition your phone. That would take some good coding skills.
androidifyme said:
You might have bad partitions. That might be pretty hard to fix with only rsd light you might have to make your own fxz flashable zip to repartition your phone. That would take some good coding skills.
Click to expand...
Click to collapse
you RSDd over safestrap didnt you..
nitephlight said:
you RSDd over safestrap didnt you..
Click to expand...
Click to collapse
Not sure trying to fix my buddy's phone but I think the battery is to dead now how can I charge it ??
Sent From My Rooted 3D
mobgod said:
Not sure trying to fix my buddy's phone but I think the battery is to dead now how can I charge it ??
Sent From My Rooted 3D
Click to expand...
Click to collapse
goto radio shack and buy one of those chargers that works for most batteries like phones and cameras or you can try the usb cable hack.
once charged you will need to FXZ through RSDLite.
RSDLite 5.7
http://d-h.st/Wja
FXZ 905 - Please read the README.txt for more info
http://d-h.st/W6A
Motorola Device Manager (up-to-date USB drivers for Windows)
http://www.adrive.com/public/ABQ6M2/MotorolaDeviceManager_2.2.26.exe
mobgod said:
Can't get into recovery or anything can someone help or point me into the right place to fix this just need to get the phone up and running the rest i can do root ect,,,,,
Click to expand...
Click to collapse
mobgod said:
i can get into fastboot but thats about it
Click to expand...
Click to collapse
mobgod said:
I've tried that keeps failing with rsd step 6 I believe the first time I got to step 20 than all hell broke lose I believe it was something about web top. Should I just try 902 again is what your telling me ? Also big question is how can I charge the battery I'm getting low battery in fastboot ??
Sent From My Rooted 3D
Click to expand...
Click to collapse
twinkyz1979 said:
goto radio shack and buy one of those chargers that works for most batteries like phones and cameras or you can try the usb cable hack.
once charged you will need to FXZ through RSDLite.
There is a program that SamuraiHL has posted called House of Bionic. It's on the droidforums web site and you should be able to search for it there. Either that or google House of Bionic. It should bring up the thread where you can download this program. It's definitely a lifesaver. I would post the link myself but I haven't posted here enough yet to do that.
Hope this helps you out!
Cindy
Click to expand...
Click to collapse
cindylike24 said:
twinkyz1979 said:
goto radio shack and buy one of those chargers that works for most batteries like phones and cameras or you can try the usb cable hack.
once charged you will need to FXZ through RSDLite.
There is a program that SamuraiHL has posted called House of Bionic. It's on the droidforums web site and you should be able to search for it there. Either that or google House of Bionic. It should bring up the thread where you can download this program. It's definitely a lifesaver. I would post the link myself but I haven't posted here enough yet to do that.
Hope this helps you out!
Cindy
Click to expand...
Click to collapse
Link to usb hack http://www.droidforums.net/forum/dr...-code-corrupt-battery-low-cannot-program.html
Link to House of Bionic. http://www.droidforums.net/forum/mo...wngrade-902-no-app-data-loss.html#post2173723
Make sure you download the latest drivers and the right rsd to be used. Link to find both http://www.droidhive.com/forums/ind...nks-in-op-updated-dailyformerly-whats-in-dev/
The reason for it error in out is because the phone doesn't have enough juice to do the fxz process. Make sure that battery has over 50% charge before attempting or do the usb hack with a cord that you will no longer be using.
Click to expand...
Click to collapse
I had this same problem. I used my warranty and got a new bionic. I blame Verizon and Motorola for not giving us what we want with an unlocked bootloader. Personally, I feel they should support the rooting community and be able to reinstall the operating system when we mess up, similar to how we can reinstall windows on a computer. They can even charge $50 for the service and be able to do it in-store from a computer. Not only could they make more money, they wouldn't have to replace as many devices.
Sent from my DROID BIONIC using Tapatalk 2
smokedkill said:
I had this same problem. I used my warranty and got a new bionic. I blame Verizon and Motorola for not giving us what we want with an unlocked bootloader. Personally, I feel they should support the rooting community and be able to reinstall the operating system when we mess up, similar to how we can reinstall windows on a computer. They can even charge $50 for the service and be able to do it in-store from a computer. Not only could they make more money, they wouldn't have to replace as many devices.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
You blame Verizon because you voided the warranty and ****ed up your own phone? Blame yourself for buying a phone that was known to have a locked bootloader to begin with.
smokedkill said:
I had this same problem. I used my warranty and got a new bionic. I blame Verizon and Motorola for not giving us what we want with an unlocked bootloader. Personally, I feel they should support the rooting community and be able to reinstall the operating system when we mess up, similar to how we can reinstall windows on a computer. They can even charge $50 for the service and be able to do it in-store from a computer. Not only could they make more money, they wouldn't have to replace as many devices.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
I would have to say that this is the reason there will most likely never be an unlocked phone sold again for VZW. By doing this you are making everyone look bad! You break, void warranty, then you should have to buy another one. If you don't like my statement don't try something you apparently have no knowledge to do.
Relax guys don't jack the thread for people that need the info
Sent From My Rooted 3D
i hada bricked phone i installed ics 235 and tryed to reflash it after data failed from safestrap . first i used a script it failed bad to reflash stuck in fastflash. so i found house of bionic(hob) of course cell battery was dead before i found it. crap i found online u can stick usb cable after cuttinfg it open and use red(pos)+ n black(neg)- wires to battery sandwhich it in phone . and it work 15min later battery ok used hob to reflash 235 used update 235 on sd card bang its alive.
....this order is my back aka new rsd flash ....no worryes
I'm probably not going to get an answer, but I'm going to ask anyway. My wife's phone was running an old version of CM, I can't remember which one it was though. But anyway, it was running like crap. She would tap an icon and it would take forever to load the app or it would just freeze totally.
So I thought about it and installed safestrap on it and flashed CM12 to slot 1. I guess I flashed the other older rom to the stock slot. I don't know how I did that, I thought only stock goes there. It's been a long long time since I messed with her phone.
So now she has the first crap rom on the stock slot and CM12 on slot 1. The problem now, is that CM12 runs like crap on her phone too. It's like old people screwing in molasses.
My question now, is do I just find the original stock rom and flash it to the stock slot? It won't let me wipe the data from the stock slot, so I guess I have to dirty flash the stock rom over top of it. Is that a good idea? And also, where do I find the correct stock rom to install? It's pretty old and I don't know what the last known stock rom for it is called or where to find it.
She's stuck to this phone for sentimental reasons, she won't give it up. I'd at least like to make it run smooth again. If anyone helps me with getting her phone back to normal, I would truly appreciate it.
Thank you.
You could find an fxz file for jellybean it's like 98.2 or something boot into fastboot and use red lite to flash the fxz, that would put you back to stock, then if you look in the razor droid section they have one click root that works for our phone too I believe, then you can reinstall safestrap and have it back to normal,
Also speeds can decrease with your older sdcard if the ROM slot is on SD are, I am not sure if its on emmc or sdcard but if it is on sdcard it could slow down as the card has aged, better cards faster read
I
thanks for the response. I just found Blur_Version.5.9.905.XT875.Verizon.en.US(67246). move this zip over to my external card and then boot into recovery. I was then going to delete slot 1 and flash this rom into the stock slot. Would this work?
It all depends what boot loader your on, if you are on the new safestrap 3.7 no it won't work, if your on old like 2 something or gingerbread still it will, but if you flash a ROM from before jellybean and updated to jellybean you will have to use fastboot to flash no !after what, most people would call it a BRI l cause they can't figure out how to use rsdlite and fast lot, and it probably won't work because you need to flash that using rd
Sdlite
1. Google rsdlite fastboot flash tool
2. Google droid bionic jellybean fxz file
3. Download both files and programs
4 place a working folder on your desktop
5. Turn droid bionic on if fuilly charged into fastboot mode with power + down I believe, might be power plus + volume up and down, might be power plus volu!e+ up you can google that to how to boot into bionic fastboot
6. Once bionic is booted into fastboot and you have the fxz file and rsdlite open rsdlite
Make sure your bionic is connected to your computer rsdlite will see its in fastboot mode, then you can flash the fxz
I would do so!e research how to do it before I did, I ha e flashed a lot of fxz but if your new you can mess up, with a bionic its almost impossible to brick it because it has fast lot and can flash an fxz, but still if you don't know what your doing you might give up trying to fix it.
There are some fxz out there made to not flash data, or have a fix for a cpommom error, when trying to flash fxz sometimes you get an error because of fb_mode_set and fb_mode_clear you have to google how to remove those lines if you get an error there is an fxz out there with those lines already removed you just gotta find it
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
OK, I will try what you said tomorrow. But for now though, do I just boot into safestrap and delete rom slot 1 and then shut the phone off? Then boot to fastboot like you said and flash Blur_Version.5.9.905.XT875.Verizon.en.US(67246) with rsdlite? It's been a while since I've done this, it's really hazy, but familiar. I appreciate you taking the time to help me out with this. Thank you very much.
DroidisLINUX said:
You could find an fxz file for jellybean it's like 98.2 or something boot into fastboot and use red lite to flash the fxz, that would put you back to stock, then if you look in the razor droid section they have one click root that works for our phone too I believe, then you can reinstall safestrap and have it back to normal,
Also speeds can decrease with your older sdcard if the ROM slot is on SD are, I am not sure if its on emmc or sdcard but if it is on sdcard it could slow down as the card has aged, better cards faster read
I
Click to expand...
Click to collapse
I got around to reflashing it to day, worked great, just had to edit 2 lines in the .xml of my rom, but it worked great. would you mind pointing me in the direction of the razr one click root? all I'm seeing is install a virtual machine on my pc, I did that before I remember, but if there's an app I can install to the phone and it would do everything, that would be great. thanks for all the help.
Its in the razor forum moto razor one click root Google should find it, or look threw xda razor forum for it, it should work on bionic if not then use the virtual box tiny Linux install methld
Sent from my DROID BIONIC using XDA Free mobile app
DroidisLINUX said:
Its in the razor forum moto razor one click root Google should find it, or look threw xda razor forum for it, it should work on bionic if not then use the virtual box tiny Linux install methld
Sent from my DROID BIONIC using XDA Free mobile app
Click to expand...
Click to collapse
I don't think that first one you mentioned works for the bionic. However, the virtual machine does work and saferoot also works.
OK, so I've had my Droid 4 since it came out in 2012, and finally replaced it with a Galaxy S7 and the keyboard case.
I wanted to play around a bit with RSD Lite and flash all the different firmware versions, as part of a wallpaper dump project I'm doing. I knew at the time that once you updated to ICS, you could not go back to Gingerbread. But it's now four years later, and I'm just curious what the technical reason for this is... it just tells me "flash failed"
With the original Droid you were able to go from 2.0 to 2.3 and vice versa easily, it was just a matter of putting the phone in flash mode and using the .sbf. Is it possible to use the 2.3 system.img with the newer baseband or whatever?
The Droid 4 has a locked bootloader. It prevents older firmware from being flashed, kind of how on newer Samsung devices, you can't downgrade the version because of KNOX and a qfuse trip. I'm not sure of the specifics on the Droid 4, but it should be a similar concept.
Don't the other Droids (1 and 2) have locked bootloaders too? It's a GOOD thing so you don't perma-brick by trying to flash garbage code to it.
drfsupercenter said:
Don't the other Droids (1 and 2) have locked bootloaders too? It's a GOOD thing so you don't perma-brick by trying to flash garbage code to it.
Click to expand...
Click to collapse
The Droid 2 and Droid 2 Global had locked bootloaders, but the OG Droid didn't. It had a fully unlocked bootloader. I have two of them, and it was nearly impossible to brick them. As long as you don't mess with the bootloader, then you have one way to restore it, even if the system and recovery become corrupted (fastboot, or RSD Lite in this case).
eragon5779 said:
The Droid 2 and Droid 2 Global had locked bootloaders, but the OG Droid didn't. It had a fully unlocked bootloader. I have two of them, and it was nearly impossible to brick them. As long as you don't mess with the bootloader, then you have one way to restore it, even if the system and recovery become corrupted (fastboot, or RSD Lite in this case).
Click to expand...
Click to collapse
Ah yeah, I noticed that.
I was trying to collect SBF files recently and wanted to verify all the ones I had... on the original Droid I was able to go back and forth between the original 2.0 and the latest 2.2.3 update; on my Droid 2 anything older than the most recent would leave me with a "MEM_MAP Blank" error in the bootloader.
However, the part that I don't understand... isn't the "OK to Program, Connect USB Data Cable" part of said bootloader? If it was fully unlocked, you could write a bunch of zeroes to it and you'd be left with a brick you couldn't recover from. That, to me, is the benefit of the locked bootloaders...
Similarly, you can flash ClockworkMod to both the D1 and D2, but on the D2 it requires a "bootstrap" which I imagine is similar to Safestrap on the Droid 4. I assume the custom recovery on the original Droid replaces the stock recovery, but it leaves that bootloader intact so you can flash back to 100% unrooted stock. So how is that any different than what the D2 bootstrap and D4 Safestrap do?
And furthermore... even using the bootstrap/Safestrap, if you try to flash a nandroid backup from an older version, it won't boot, you'll just get a black screen. I don't get that part either, because the bootloader is left intact during that process, wouldn't that be like live-booting Windows XP on a Windows 7 computer by plugging in an external hard drive? (Especially so with the Droid 4 and Safestrap, where you literally store all the partitions as files on the internal storage)
drfsupercenter said:
Ah yeah, I noticed that.
I was trying to collect SBF files recently and wanted to verify all the ones I had... on the original Droid I was able to go back and forth between the original 2.0 and the latest 2.2.3 update; on my Droid 2 anything older than the most recent would leave me with a "MEM_MAP Blank" error in the bootloader.
However, the part that I don't understand... isn't the "OK to Program, Connect USB Data Cable" part of said bootloader? If it was fully unlocked, you could write a bunch of zeroes to it and you'd be left with a brick you couldn't recover from. That, to me, is the benefit of the locked bootloaders...
Click to expand...
Click to collapse
Technically, yes. You could brick it by doing that. But I never once touched the bootloader, or even used RSD Lite, until I got to the Droid 2 Global. Even then, I never touched the bootloader. You shouldn't ever have to (unless you unlock it through an exploit on a device, like some newer phones).
Similarly, you can flash ClockworkMod to both the D1 and D2, but on the D2 it requires a "bootstrap" which I imagine is similar to Safestrap on the Droid 4. I assume the custom recovery on the original Droid replaces the stock recovery, but it leaves that bootloader intact so you can flash back to 100% unrooted stock. So how is that any different than what the D2 bootstrap and D4 Safestrap do?
Click to expand...
Click to collapse
I don't remember how the Droid 2 worked in terms of exploits, but I know that the Droid 4 uses kexec, or kernel execution. Check here for some info on kexec (for regular Linux).
And furthermore... even using the bootstrap/Safestrap, if you try to flash a nandroid backup from an older version, it won't boot, you'll just get a black screen. I don't get that part either, because the bootloader is left intact during that process, wouldn't that be like live-booting Windows XP on a Windows 7 computer by plugging in an external hard drive? (Especially so with the Droid 4 and Safestrap, where you literally store all the partitions as files on the internal storage)
Click to expand...
Click to collapse
Untouched systems require the corresponding bootloader or older. The Galaxy S5 could run a newer system on an older bootloader, but not vice versa. Even Cyanogenmod requires a specific bootloader sometimes (Droid 2 Global, for example).
eragon5779 said:
Technically, yes. You could brick it by doing that. But I never once touched the bootloader, or even used RSD Lite, until I got to the Droid 2 Global. Even then, I never touched the bootloader. You shouldn't ever have to (unless you unlock it through an exploit on a device, like some newer phones).
Click to expand...
Click to collapse
I used RSD Lite even back then, because I had rooted my phone and wanted to unroot it for something. Also if I recall, before ROM Manager had a nice recovery install feature, the only way to do it was to flash a .sbf file with the recovery partition to the phone.
Either way, I see people complaining about locked bootloaders and it makes me wonder why that's a bad thing. With the Droid 2 and 4 (and I assume 3 as well, I don't have one), you can only really "soft brick", it's always repairable via RSD Lite, and that's what Motorola themselves would do too. If you somehow bricked an original Droid by corrupting the bootloader, I don't think even THEY could fix it! Never hurts to have some sort of brick recovery.
eragon5779 said:
Untouched systems require the corresponding bootloader or older. The Galaxy S5 could run a newer system on an older bootloader, but not vice versa. Even Cyanogenmod requires a specific bootloader sometimes (Droid 2 Global, for example)
Click to expand...
Click to collapse
I guess I'm fundamentally mis-understanding what exactly a bootloader does, then. You would think if the encryption changed, the older versions would still work but NOT the newer versions.
Would this be of any use?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
drfsupercenter said:
I used RSD Lite even back then, because I had rooted my phone and wanted to unroot it for something. Also if I recall, before ROM Manager had a nice recovery install feature, the only way to do it was to flash a .sbf file with the recovery partition to the phone.
Either way, I see people complaining about locked bootloaders and it makes me wonder why that's a bad thing. With the Droid 2 and 4 (and I assume 3 as well, I don't have one), you can only really "soft brick", it's always repairable via RSD Lite, and that's what Motorola themselves would do too. If you somehow bricked an original Droid by corrupting the bootloader, I don't think even THEY could fix it! Never hurts to have some sort of brick recovery.
I guess I'm fundamentally mis-understanding what exactly a bootloader does, then. You would think if the encryption changed, the older versions would still work but NOT the newer versions.
Would this be of any use?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
Not really. The bootloader always has been and always will be locked on the Droid 4. Once kexec was achieved, unlocking wasn't looked at anymore.
And in terms of what a bootloader is, read around on XDA. There are plenty of threads on it.
Just an idea, I'm thinking there's a difference between a bootROM and the bootloader on a phone.
I'm thinking of the Nintendo 3DS as an example because I've done a bit of 3DS hacking. The 3DS has a bootROM, which means it cannot be overwritten and as a result Nintendo cannot update it even if they wanted to. They update other bits of code, but the bootROM is and always will be the same because it's readonly memory.
From what I gather, since the Motorola phones have had updates that reprogram (and update) the bootloader, meaning it has to be flashable somehow. What people have done with the 3DS is actually solder some wires to the NAND which lets you read/write it like an SD card. Could something like that be done on a Motorola phone? Even if the fastboot stuff isn't the full code, you could probably dump the oldest version of the bootloader from a phone that hasn't been upgraded (if there even are any out there in the wild...) and others could use it on theirs.
Given that you can buy a Droid 4 on eBay for like $40 it's probably not even a big deal, but it would be an interesting undertaking nonetheless. Especially for those who know how to solder. I don't know if phones actually use a NAND or not, but given "nandroid" I was assuming.
drfsupercenter said:
Just an idea, I'm thinking there's a difference between a bootROM and the bootloader on a phone.
I'm thinking of the Nintendo 3DS as an example because I've done a bit of 3DS hacking. The 3DS has a bootROM, which means it cannot be overwritten and as a result Nintendo cannot update it even if they wanted to. They update other bits of code, but the bootROM is and always will be the same because it's readonly memory.
From what I gather, since the Motorola phones have had updates that reprogram (and update) the bootloader, meaning it has to be flashable somehow. What people have done with the 3DS is actually solder some wires to the NAND which lets you read/write it like an SD card. Could something like that be done on a Motorola phone? Even if the fastboot stuff isn't the full code, you could probably dump the oldest version of the bootloader from a phone that hasn't been upgraded (if there even are any out there in the wild...) and others could use it on theirs.
Given that you can buy a Droid 4 on eBay for like $40 it's probably not even a big deal, but it would be an interesting undertaking nonetheless. Especially for those who know how to solder. I don't know if phones actually use a NAND or not, but given "nandroid" I was assuming.
Click to expand...
Click to collapse
That's a process called JTAGing and is used on a lot of phones. But at this point, doing so is kind of pointless. All ROMs are made using kexec, and unless you can a) figure out the pin layout for the JTAG without killing the phone and b) build a kernel that doesn't use kexec, then there isn't much point to it at this point. We have working 6.0 ROMs, and I can deal with the extra boot time that kexec takes (which is, in my opinion, the only thing that would be improved from unlocking the bootloader).
Yeah, JTAG is basically the same thing I'm talking about, just that on a 3DS the pinout is such that it can be read/write like an SD card instead of needing a parallel connection.
I was thinking more for being able to flash any SBF (or in the case of the Droid 3/4, the XML and image files) to the phone. There probably aren't many people interested in actually downgrading, since the newest OTA update can be rooted and you can use kexec, but I'm more of a hobbyist and it was something I was interested in doing.
Plus, you could probably redo the SBF/XMLs to not update the bootloader (if it really can run newer code as you said) so that way you can just go back and forth between the first version of the OS to the newest freely, instead of being locked to the newest as you are now.