Related
I have been hearing a lot that the DROID 4 and the DROID Razr are very simaliar... If thats true then is there a Possibility that the Razr fastboot files cold work on the DROID 4?
The hardware is identical.....
EXCEPT for the keyboard (maybe the screen, too??). If you have a spare Droid 4 laying around, why not?
For even the above casual user this might be a little much. I haven't had much luck with getting my fully functioning Droid 4 to be recognized by RSDLite.
Although, I do want to know from the developer here, HOW CAN I HELP??
I don't want to just take take take, some of us want to give back.
I bricked my spare Droid 4, and everyone should be really careful with SafeStrap, and backup everything (including the webtop).
RueTheDayTrebek said:
EXCEPT for the keyboard (maybe the screen, too??). If you have a spare Droid 4 laying around, why not?
For even the above casual user this might be a little much. I haven't had much luck with getting my fully functioning Droid 4 to be recognized by RSDLite.
Although, I do want to know from the developer here, HOW CAN I HELP??
I don't want to just take take take, some of us want to give back.
I bricked my spare Droid 4, and everyone should be really careful with SafeStrap, and backup everything (including the webtop).
Click to expand...
Click to collapse
Droid RAZR fastboot files would probably work on the Droid 4, IF we had unlocked bootloaders. I have tried every combination of DR fastboot files on the D4 and the /system/ partition is never properly signed for the D4.
We need a full Droid 4 update or Droid 4 fastboot files to get back to working order, the Razr won't cut it.
Without trying to sound too stupid here(lol), but could we not make a stock nandroid backup and dump the image in the fastboot file by chance, and change the md5 inside zip?
The problem is not hardware, but rather encryption. Quite simply, we need a properly signed and encrypted software bundle to load on the locked bootloader. If we could sign and encrypt the bundle ourselves, the locked bootloader would not be an issue. The Droid Razr is a different phone with a different encryption key, so we can't use those fastboot files on a D4. We also can't sign our own Nandroid, so we can't load that either.
Sent from my DROID4 using XDA
Is there anything that I can do to help?
I'm really eager to get into Android development, and would be willing to pursue the path in getting these signed drivers.
I don't think this will be a problem for much longer. http://www.droid-life.com/2012/03/20/motorola-razr-gsm-bootloader-bypass-discovered-could-work-on-lte-razr/
problematic said:
I don't think this will be a problem for much longer. http://www.droid-life.com/2012/03/20/motorola-razr-gsm-bootloader-bypass-discovered-could-work-on-lte-razr/
Click to expand...
Click to collapse
Yeeeeeeeeehaaaaaaaaa!!!!!!! Oh, this would be EXCELLENT.
GOOGLE IT!!!! Fastboot files are now out for the Droid 4!!!!!
OK, I have a Droid 3, that I messed up. I spent the last week searching to find a solution, but this has only left me more confused than ever. When I find what looks promising the links to the file don't work. I am a bit overwhelmed now and need help.
Here is what happened. I installed ClockWorkMod Rom Manager on my rooted Droid 3. I tried to make a backup, this did not work. I then found ClockWorkMod Droid 3 Recovery Bootstrap, this worked then I made a backup. I then tried to load cyanogenmod this failed. Now the phone is stuck on the Motorola Logo, I left it on overnight and it was still stuck. Now I can reboot +X , but I only get the Android System Recovery, but it doesn’t see the backup made by Droid 3 Recovery. The phone does not boot to the Droid 3 Recovery menu (or atleast I don’t know how).
I can also get to the “Boot Mode Selection Menu 0A.64” but I am more confused about all these options. I tried looking for file to flash but I can’t figure this out. The options I have on this menu are;
Normal Powerup
Recovery
AP Fast Boot
BP SBF Flash Mode
BP Only
BP HW Diag & Boot AP
BP Tools
I was able to connect my phone to the pc, but I don’t know how to use any of these options or what software I need on the PC to make this work. Yes I am a noob and this is my first post.
So, how can I get my phone to work again?
Please help, Thanks
The best idea is to use RSD Lite with AP Fastboot to restore an SBF to bring the phone to scratch.
sd_shadow has a great resource here: https://docs.google.com/document/d/...gVAeQXxSkaLPlBAAw/edit#heading=h.lpb8vdlj146l
But, to save some time, you'll find the SBF files that you want here: https://docs.google.com/document/d/...gVAeQXxSkaLPlBAAw/edit#heading=h.lpb8vdlj146l
You want the download link in the third line, under build number 5.5.1_84_D3G-66_M2-10
Blur_Version.5.7.906.XT862.Verizon.en.US
To get to AP fastboot mode, follow this: https://docs.google.com/document/d/...AeQXxSkaLPlBAAw/edit#bookmark=id.xj82g0jvczjr
For RSD Lite instructions, see this: https://docs.google.com/document/d/...AeQXxSkaLPlBAAw/edit#bookmark=id.77zigoazhz70
And give a big thanks to sd_shadow for collecting all of those instructions in one place. Totally awesome.
Thanks, that worked great. My phone is working again.
Now on a slightly paranoid note, how can you be sure that the file that was used to program the phone is truely the stock version from verizon and does not contain any malware?
sheatrek said:
Thanks, that worked great. My phone is working again.
Now on a slightly paranoid note, how can you be sure that the file that was used to program the phone is truely the stock version from verizon and does not contain any malware?
Click to expand...
Click to collapse
The locked bootloader prevents anything that isn't official motorola from being flashed to the phone
Sent from my XT860 using xda premium
doogald said:
And give a big thanks to sd_shadow for collecting all of those instructions in one place. Totally awesome.
Click to expand...
Click to collapse
thanks doogald
I started my list, for a few reasons, because like you I post on several other forum's, good threads don't get stickied, stickied threads get outdated very fast and don't get updated because the OP, has moved on to another device
I'm also working on uploading sbfs and xml file to
dev host and android file host
Sent from my XT862 using Tapatalk 2
Did you figure it out if not I did the sane to this phone and fixed it and I'll help you if you didn't fix it
Sent from my DROID3 using xda app-developers app
Sounds like he fixed it.
I was messing around with my Atrix HD and got myself into an endless bootloop and no custom recovery installed. I downloaded RSD Lite but my device wasn't recognized. I did the command "fastboot devices" in CMD and my device shows up while in AP Fastboot mode. I tried downloading an sbf file from the Droid Developers website but the website has been down for a couple days. Does anyone have any mirrors to the stock sbf files or have one that they could send to me? Thanks!
Check out this website http://motofirmware.com/files/category/31-qinara/. I haven't tried anything from this website but looks legit.
Just to let you know, i was also looking for the sbf files to restore the phone. I was afraid that I wasnt legit, but the worst thing that could happen is that the A HD died and I had green light to buy a LG G2 !!
But they work, so I still have the Atrix
neondunker said:
Just to let you know, i was also looking for the sbf files to restore the phone. I was afraid that I wasnt legit, but the worst thing that could happen is that the A HD died and I had green light to buy a LG G2 !!
But they work, so I still have the Atrix
Click to expand...
Click to collapse
Poor guy...
I can help you to brick your device lol
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.
Hoping someone has a minute to inform me of how to repair my bionc from vzw. I had safestrap 3.73 on and upgraded to safestrap 3.75 with rooted stock moto image from way back when. I saw a lineage 14.1 image install and thought what the heck. couldnt hurt. so I did a nandroid backup with compression to the external sdcard of all partions(securedata,system,data,webroot). did another backup to the internal partion. had the prefrered storage device as intenrnal memory. I then wiped system-data-cache-dalvik and left webtop and secure partion alone. I tried unlocking the bootloader from moto bye getting my device info in fastboot but fastboot did not understand the "oem" command. I remember I was able to boot multiple boots but it had to share the same kerenl so I firgured what the the heck. I could always safestrap back and restore if lineage os failed. my mistake. I assumed. I then found there was a file called moto-fastboot but not sure if it was any different than google's fastboot. before I get things anymore screwed up I thought I would kindly ask for someone to throw me a lifepreserver because I wanna get me and the brick outta the water.
anyhow now it tries to boot, reboots and gets a dead android bmp screen. I can get into fastboot still
any help greatly appreciated. I have not used rsdlite in a while nor can I find the cdma_targa_9.8.2O-72_VZW-22_1ff.xml.zip file to manually doit through fastboot. (my own diagnoses but hey I'm an advnace noob with super cape and no superpowers)
yes my weaknesses are no-fear and stupidity based on not reading, reading and then reading a little more.
rp201 said:
Hoping someone has a minute to inform me of how to repair my bionc from vzw. I had safestrap 3.73 on and upgraded to safestrap 3.75 with rooted stock moto image from way back when. I saw a lineage 14.1 image install and thought what the heck. couldnt hurt. so I did a nandroid backup with compression to the external sdcard of all partions(securedata,system,data,webroot). did another backup to the internal partion. had the prefrered storage device as intenrnal memory. I then wiped system-data-cache-dalvik and left webtop and secure partion alone. I tried unlocking the bootloader from moto bye getting my device info in fastboot but fastboot did not understand the "oem" command. I remember I was able to boot multiple boots but it had to share the same kerenl so I firgured what the the heck. I could always safestrap back and restore if lineage os failed. my mistake. I assumed. I then found there was a file called moto-fastboot but not sure if it was any different than google's fastboot. before I get things anymore screwed up I thought I would kindly ask for someone to throw me a lifepreserver because I wanna get me and the brick outta the water.
anyhow now it tries to boot, reboots and gets a dead android bmp screen. I can get into fastboot still
any help greatly appreciated. I have not used rsdlite in a while nor can I find the cdma_targa_9.8.2O-72_VZW-22_1ff.xml.zip file to manually doit through fastboot. (my own diagnoses but hey I'm an advnace noob with super cape and no superpowers)
yes my weaknesses are no-fear and stupidity based on not reading, reading and then reading a little more.
Click to expand...
Click to collapse
Howdy! Sorry it's taken three months for your question to get any attention. Bionic forum's pretty dead, eh? I'm amazed it's still an officially supported Lineage device. Go team!
Sadly, the no one ever found a bootloader unlock, as a fellow informed me here two years ago. Unless some clever hacker happens upon a Bionic and decides to crack it for kicks, it's not likely to happen. But at least we have SafeStrap and Lineage!
You may know this already, but you didn't mention it in your post, so I'll go ahead and say: when installing a ROM like Lineage on the Bionic with SafeStrap, you need to install it on ROM Slot 1, not the Stock ROM Slot. I imagine that might be why you bricked your phone (I've done it myself a few times too ).
Now that I've given you the skinny on the Bionic's limitations, let's see if we can't get you back afloat. Whenever I bricked mine, I never used RDS Lite—I found a utility called House of Moto. You can find the home page here, but you'll need to create an account to see the important stuff and the downloads (you'll also need to install Java). But if you're more familiar with RDS Lite, feel free to use that instead
System images for the Bionic are hard to find nowadays. I seem to have found one link to an article with a direct download link to an update file at the bottom, which I'll link to here. Whether the update file is the same as an FXZ file RDS Lite/House of Moto requires, I'm not sure. Give it a try and see how it goes! If not, I may have a copy of the file on my old computer at my parents' house. If the linked update file doesn't work, I'll see if I can't get ahold of my image file.
Finally, if you do happen to get things up and running happily, I've got a list of optimizations that help Lineage run more smoothly.
Best of luck! :good: