Related
first post, yes, i'm new to this... (forum, not flashing, not entirely anyway, i did fiddle with Sony Ericssons and stuff, kindergarden compared to androids)... but not an idiot, to the point:
firmware config. version seems to be RTGB, great britain, right? wrong, a RTUK is not it. I am sort of lost, i bought the phone with 2.1-update1, the 2.2.1 update has not yet been rolled out in my backwards country, so i did an official update over the internet with motorola app etc etc. I have no idea what was the 2.1 fw config. ver., but it strikes me as weird that i have a RTGB one now, the packaging/box/manuals all were German or something that looks like German. And now, i got myself RTUK sbf file, and RDS lite fails to do anything. I require assistance, and an explanation if possible as to why this didnt work? if i chose the wrong sbf, why does it show me having RTGB? and finally which sbf to take and from where (two german one's are available on this forum), but i've seen only one RTGB and it was only 2.1. For comparison, the friend bought the same phone on the same day, but she got one with a qwertz keyboard, mine is normal qwerty, fw config. ver. shows VFDE, did not update hers, it's still 2.1-update1. I can only assume that VF is german for RT and that her phone did not come from an unknows source. The phone company selling these obviously imports them, possibly even from random countries or EU countries at least...
however something did happen, my battery in the notification seems to be not present, there's just a question mark inside what appears to be an empty battery... apps that show battery levels work fine... although, scratch this last one, a reboot fixed it, even though i have not seen it before.
also, help me rack up some posts ^^ ask for info or whatever, i'd like to give a shot at improving my android...
Check the link below. You will get both service and non-service versions of 2.2.1 sbf's.
http://and-developers.com/sbf:milestone221
VF would be vodafone ( service version) while RT would be retail version.
Sent from my Milestone using Tapatalk
Thanks, gonna try asap, will come crying if it explodes in my face...
SuicideTree said:
Thanks, gonna try asap, will come crying if it explodes in my face...
Click to expand...
Click to collapse
It wont. I have done it many times and my face is still intact, as you can see from my avatar.
Sent from my Milestone using Tapatalk
now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]
SuicideTree said:
now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]
Click to expand...
Click to collapse
which version of rsdlite and what OS? rsdlite should not cause your OS to crash.
oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.
SuicideTree said:
oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.
Click to expand...
Click to collapse
Try it and see if it works.
Just finished. Seems to be good. Gonna Continue with the guide then ^^ Many thanks.
instead starting a new topic IDIOT QUESTION but... can someone give me a detailed dumbed down version of this instruction bellow:
If you applied an OTA update before, there is a script run at every system boot that checks and re-flashes the recovery when its checksum doesn't match. In such case, you have to avoid booting to android after the vulnerable recovery flash. Boot directly to recovery when RSD Lite restarts the phone (hold camera button) and from there remove the /system/etc/install-recovery.sh file.
rm -f /system/etc/install-recovery.sh
i am getting this
E:Cant open /cache/recovery/command
just upon entering AOR (power+x)
trying to apply the update regardless i get this
- install from sdcard
finding update package
opening update package
verifying update package
E:EOCD marker occurs after start of EOCD
E:signature verification failed
Instalation aborted
what is the meaning of this?
possible solutions:
"It seems that the key to successful recovery flash in some cases is to not let the phone to boot to android or recovery until the RSD Lite will signal PASS. When the RSD Lite is restarting the phone during flash, hold the D-Pad Up, so the phone enters the bootloader again immediately."
does this work? DIDNT WORK, so i still need help
i'm still combing through many threads mentioning this... either please tell me this works or point me in the right direction -_- thanks
Once you flash the official sbf, you need to flash the vulnerable recovery to enable you to run openrecovery which is used to flash custom roms and much more.
There is a script which checks your recovery image everytime it boots and replaces it with the original if it finds any changes. So you need to remove that script.
Procedure would be as follows.
1. Download and extract androidiani openrecovery to the root if your sdcard. You should have a update.zip file and openrecovery folder.
2. Flash official sbf.
3. Flash vulnerable recovery sbf. When the phone restarts and before it displays Moto logo, press and hold the 'x' key on your keyboard. You should see a triangle with exclamation mark. Press volume up + camera button and choose apply update menu option.
AOR should load up. Choose console option and type the following commands.
rm - rf /system/etc/install-recovery.sh
reboot
That's all.
Sent from my Milestone using Tapatalk
okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?
SuicideTree said:
okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?
Click to expand...
Click to collapse
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.
I suppose there's no harm in trying that, i already had to rename it to something shorter, cause it wouldnt even give me the Start button.... brb
skadude66 said:
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.
Click to expand...
Click to collapse
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
You helped me out with that sileshn!
Yeah, I'll keep this thread up and I'll see what issues he's got.
sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moved files around, renamed and stuff... weird
EDIT2: by the way, is it normal for the vulnerability file not to show any file properties in RSD Lite?
SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moves files around, renamed and stuff... weird
Click to expand...
Click to collapse
Once you get VR, rooting and flashing a custom ROM is a piece of cake, so it shouldn't be that bad once you get there.
SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
Click to expand...
Click to collapse
If you want to flash CM, just install GOT 2.2.1 from here and forget about VR. GOT has VR injected into it. Use the Retail UK sbf.
Once you have CM, you have root.
@skadude : Didn't know it was me.
is cm7 much better over cm6? cause i was looking into that ^^ however if the end goal can be achieved easier with got cm6 i should give that a try, but, what if i wanna play around with this stuff later or something? i'd like to understand what's happening at the moment... anyway, if i go with got solution what are the steps? flash uk sbf, then got or... then cm?
also, got or is better than aor? except apparently having vulnerability alreay in it... anything else?
thanks for all the help, sorry for being not too enlightened, i'll get there ;]]]
Apologies if this has been answered before, I searched the other threads and it seems so one has my exact same problem. I bought an Atrix HD from a local seller, unaware of this little problem that it boots into fastboot mode after powering down and back up. (seems he had been tinkering around with it with no success) I found out I could do the pwr+vol.up+vol.dwn trick, causing it to go to the boot menu screen and then booting up normally. I figured I could live with that small annoyance.
But after doing more research I found out that this AHD had been updated with the most recent OTA that irreversibly locks the bootloader and disables any possible rooting. I just dont want to keep this phone anymore if Im going to be stuck on stock JB ROM, and no flashing capabilities. And I really want to have that HDMI overscan option that apparently was in ICS and they took it away. (I know, stupid me for not researching this before buying). I just want to be able to sell this phone WITHOUT having to warn the buyer of this fastboot problem, which I think would really decrease the value of the phone.
Any ideas of a method to fix this?
Have you tried the Myth Tools?
moebius_2033 said:
Have you tried the Myth Tools?
Click to expand...
Click to collapse
I had checked that out, and noticed it uses motochopper and motopocalypse for rooting and unlocking bootloader. I had already tried those methods with no success, and figured it was because of the July OTA locking it all up. But I got a private message from a member who said he was in my same situation and able to flash a ROM back with myth tools. So maybe I just wasnt doing it right. I'll try again, paying attention to detail...
Update: still no joy. Installed JDK and the adb-fastboot-apk I cant root or unlock BL with myth tools. It just hangs. Even tried just flashing a couple ROM's listed in the myth tools instructions thread, because hey, what could it hurt now? No success, just kind of formats my phone but still the same version.
If it's of any use, system version is: 98.4.20.MB886.ATT.en.US
build number: 9.8.0Q-97_MB886_FFW-20
Are you sure the bootloader was unlocked. Once unlocked, it can't be relocked.
have you tried flashing Mex retail using rsd lite to downgrade a version
I didn't know the atrix got an update. I thought it was only for the razr. To fix that issue re flash the boot image.
Sent from my PACMAN MATRIX HD MAXX
Checkout my post on this thread. Just skip making a backup.
http://forum.xda-developers.com/showthread.php?t=2394238
PM me and click Thanks if I helped.
Sent from my Atrix HD
Ya need to restore using rsd lite
To start off with
1. No im not Boot loader Unlocked ( i forgot to Unlock Boot loader )
2. i used to be rooted? ( not sure now? )
3. i got phone it was on 4.0.4 Stock i got OTA now its on 4.1.1 Stock with Root ( not sure any more? )
4. its AT&T US
so right now what im looking at is this
I Can Charge battery with ICON %Battery
I can access Recovery ( Slandered ) Not Custom Rooted One booo
i can access Fastboot & well that white menu by holding VOL - & VOL +
i can see it telling me Device Locked Statue 0
now what happen to get to this point was this
i wanted to change the AT&T Carrier Logo to something else i download app off internet and i was stupid to give it ROOT ACCESS.... ya i know
next thing i know poof it tells me to reboot i reboot and now i see Moto Logo then nothing but Black screen.....
i try to use RSD Lite and use the .XML.zip files all 3 of them but no luck
i try everything no luck.... im freaking out..... with no luck lol.....
can someone help with this?.....
when i try to RSD LITE it i got many errors
some forums told me to Edit 2 to 3 lines to remove a VAR or somthing it started to work bu then got stuck at Boot.img and other system.img and anohter called NON-HLOS.bin?
i try to use another file called Blur_Version.77.12.22.MB886.ATT.en.US.zip
its got some strange files in it? ..... ill upload photo but i place it on sd card and try to update it but tells me somehting about ro.build pro 4.0.4 release keys ro.build pro 4.1.1? makes no since to me?
View attachment 2802750
I'm helping a friend on the same situation.
Phone doesn't boot.
Stuck on M logo.
Locked bootloader.
Able to go to AP fastboot
No custom recovery.
Particularly this is my first time dealing with a motorola phone. Have flashed HTC and have owned mostly samsung phones.
But I know my way a bit on adb and fastboot.
Anyways I'll keep an eye on this thread and let you know if I find something on my own.
I'll try with RSDLite, Myth tools and fastboot.
Maybe one of them will work.
Good luck.
Silenus21 said:
I'm helping a friend on the same situation.
Phone doesn't boot.
Stuck on M logo.
Locked bootloader.
Able to go to AP fastboot
No custom recovery.
Particularly this is my first time dealing with a motorola phone. Have flashed HTC and have owned mostly samsung phones.
But I know my way a bit on adb and fastboot.
Anyways I'll keep an eye on this thread and let you know if I find something on my own.
I'll try with RSDLite, Myth tools and fastboot.
Maybe one of them will work.
Good luck.
Click to expand...
Click to collapse
from what i can tell..... RSD LITE is not gonna work.... but im sure if i get the New 4.1.1 Update zip file that u add to SD CARD and Flash update through there it will work as long as its singed. i have 4.0.4 but keeps crashing durning install telling me ro.buildprop 4.0.4 & ro.buildprop.4.1.1 so i think that i has a 4.0.4 update file when i need a 4.1.1 but unsure where to get it? ..... so mad i spent $250 bucks on this thing to have a Rouge App do this to me lol...... next time NO more root for me lol
Have you tried mythtools??
Sent from my ATRIX HD using XDA Free mobile app
Silenus21 said:
I'm helping a friend on the same situation.
Phone doesn't boot.
Stuck on M logo.
Locked bootloader.
Able to go to AP fastboot
No custom recovery.
Particularly this is my first time dealing with a motorola phone. Have flashed HTC and have owned mostly samsung phones.
But I know my way a bit on adb and fastboot.
Anyways I'll keep an eye on this thread and let you know if I find something on my own.
I'll try with RSDLite, Myth tools and fastboot.
Maybe one of them will work.
Good luck.
Click to expand...
Click to collapse
From fastboot, I recommend unlocking the bootloader, install Philz, and flash a custom KK ROM.
Manual fastboot didn't work. Always stuck on flashing boot.img and system.img
The same happen on that step in rds lite and myth tools.
Phone said can't downgrade or something like that.
So I haven't had any luck yet.
Open to suggestions.
Sent from my SM-N900V using XDA Premium 4 mobile app
Silenus21 said:
Manual fastboot didn't work. Always stuck on flashing boot.img and system.img
The same happen on that step in rds lite and myth tools.
Phone said can't downgrade or something like that.
So I haven't had any luck yet.
Open to suggestions.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im just gonna sell it on Craigslist & let it be someone else issue!
News
so i went to here http://sbf.droid-developers.org/phone.php?device=7 to just see if they added a new Update file and Poof they did.
they added: Android 4.1.1
Blur_Version.98.5.38.MB886.ATT.en.US
so i ran RSD LITE nothing fail, i edit the xml, nothing fail... i used the Mytool thing that people keep saying to use for Moto phones and Poof it worked now my phone works again and i did not has to sell it on craglist dead.... but now there is an issue that was not there before... 4 times a day i get a RED CROSS with no signal and no bars and no service telling me emergancy calls only so i do air plane mode and works again for a while? does any one know why it does this?
any way back to sell it to craglist lol....
Maybe have to flash a modem.
Thanks for the update, I gave the phone back to my friend but will tell him to bring it back to me to test.
Hopefully this works for that phone too.
This is NOT a how-to or anything. Don't try to follow in my footsteps of stupidity and brick your phone.
That being said...
XT 1060 (Verizon)
I have been running 4.4.4 for quite a while now. Right after JCase released sunshine for our phones. (I have an unlocked bootloader.)
I had it rooted, and tried out the 5.0 ROMs a while ago. Flashed back to stock to wait for the update when we heard it was coming "very soon". But tonight I got impatient and decided I was going to re-root and switch back to CM12. So, I opened Moto X Toolkit (love that tool) and installed TWRP. When I manually rebooted I forgot to boot into recovery. Don't know if that had anything to do with the ensuing problems or not, but after that, I couldn't get it to boot into recovery.
So, I flashed back to stock 4.4.4 again. Tried rebooting into stock recovery... no joy.
So off I go again... one more attempt to flash stock 4.4.4. This time, when it asked me if I wanted to reboot into bootloader or android, I tried to boot into android. Sadly I missed the "a" and typed "ndroid". The toolkit began doing something... looks like it was running the flash all over again. I let it do its thing, then very carefully typed "android" so I wouldnt screw it up again.
It rebooted perfectly, but once it was up and running, I noticed all of my icons were blue. I quickly jumped into the "about phone section and noticed it said "4.2.2".
This is not supposed to be possible, so at this point I was half panicking and half curious... so I decided to do an even more stupid thing and accept the updates.
I am now updated completely to 4.4.4. Zero issues... recovery works fine, radio is fine, wifi and BT are fine.
This leads me to two questions (Directed to developers)...
1) Is there a possibility this is repeatable?
2) My curiosity is about to get me into trouble... I have two more Moto X's that are 4.4.4. Locked BL. I would like to know what the worst case scenario is. I know there is a possibility of "bricking", but that term has not, for a long time, meant what it originally did. How badly "bricked" might it be? Bootloops? Chance of recovering by flashing stock firmware or RSD? Or truly bricked?
You are lucky you didn't bricked it by installing ota
updates. Whatever you do please don't install any ota updates. Simple wait for the sbf and manually flash it with rsd. Don't even even attempt to downgraded
I know I got lucky, but that didn't answer either of my questions.
I wouldn't try to repeated it if I were you. Go to moto x bricked phones thread and read the comments. That will satisfy and answer your questions http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Fadelight said:
This leads me to two questions (Directed to developers)...
1) Is there a possibility this is repeatable?
2) My curiosity is about to get me into trouble... I have two more Moto X's that are 4.4.4. Locked BL. I would like to know what the worst case scenario is. I know there is a possibility of "bricking", but that term has not, for a long time, meant what it originally did. How badly "bricked" might it be? Bootloops? Chance of recovering by flashing stock firmware or RSD? Or truly bricked?
Click to expand...
Click to collapse
1) I would NOT try to repeat it. You are lucky.
What likely happened is the toolkit flashed 4.2.2 via mFastboot, errored on GPT.BIN and Motoboot.img, and continued flashing the rest. Taking an OTA in this state USUALLY bricks the phone, however we have seen a few, like yourself, who reported it didn't brick.
Due to the sheer number of people and threads from those who have bricked doing this, the warnings have been... do NOT try it unless you don't mind if you turn your phone into a paper weight!
To be safe at this point, I would consider downloading the Verizon 4.4.4 SBF, and re-flashing it using Option 5 (and its pre-reqs) at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html to make sure everything is back to stock/consistent. Its your choice if you don't want to.
2) Worst case is you turn your phone into a paperweight.
Some have screwed it up very badly but have been able to recover following these instructions -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 It is the last resort. You'll also see many in that thread who followed those instructions and were unsuccessful, leaving their phone unusable.
We've also seen a few who were able to reflash the latest rom (currently 4.4.4) via mFastboot, with a few "extra" commands and have been able to recover, but that is a very small number compared to those who have bricked.
That's the odd thing... it DIDN'T error on anything. I would've thought the same thing... error on motoboot and gpt.
I don't mind screwing up a phone and taking a day or two to get it back to operable. As long as there is a way to fix it, I'm good. I just don't want to completely brick the phone. That's why I asked if people meant truly bricked or the new standardized "bricked" which usually means nothing more than having to RSD.
Fadelight said:
That's the odd thing... it DIDN'T error on anything. I would've thought the same thing... error on motoboot and gpt.
I don't mind screwing up a phone and taking a day or two to get it back to operable. As long as there is a way to fix it, I'm good. I just don't want to completely brick the phone. That's why I asked if people meant truly bricked or the new standardized "bricked" which usually means nothing more than having to RSD.
Click to expand...
Click to collapse
I haven't used that tool kit. I do everything manually. So I don't know exactly what processes it runs, or what steps it takes when flashing. IF while flashing it does try to flash all parts, it should have given an error on GPT.BIN if it tried to downgrade, but at the same respect, if its a batch file that just runs the fastboot commands one after the other, if fastboot errors, it will just go to the next line in the bat file, so unless you are paying attention and watching it from start to finish, you could have missed the error.
Another possibility would be if you, or someone who had your phone, upgraded to 4.4.4 by flashing only system.img, and the older bootloader and partition table remained on your phone, then attempting to "downgrade" would not have failed (depending on the bootloader/gpt.bin on your phone).
As said... there are enough that have NOT been able to recover their phones, even after following the instructions in -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 which are usually the last resort.
Yeah, the second it started running again after I typed "ndroid" by accident, I was in full-on panic mode, so my eyes were glued to the phone and the computer. I saw them flash.
As far as upgrading, I was on 4.4.0 until Sunshine was released... at which point I unlocked my BL and took all of the OTA updates. So it was on full 4.4.4.
This is the oddest thing I have seen in a long time. I was tempted to send a DM to JCase and ask him, but I figured that would probably go over like a fart in church.
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: