Database Develop

[Q] wrong sbf? need proper one for (RTGB)

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 ;]]]

[Q] LG Thrill GB w/ClockworkMod Recovery

(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick

Rick Tillery said:
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Click to expand...
Click to collapse
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD

The Dark Lestat said:
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
Click to expand...
Click to collapse
Thank you for your help!
Rick

Trojan?
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick

There is no virus, Lestat would never do that
Sent from my LG-P925 using XDA

Just my .02 .....Get rid of Symantec !! They are known for scaring people into a virus frenzy.. Yes, it is possible that it is seeing it as a potential virus because shttp is a workaround from the usual porting of windows ip services. ...
Correct me if i'm wrong somebody please !!
Get yourself Comodo and save your money...
Regards,
Dwayne
PS: somebody on here has written a script that just uses shttp temporarily while
your doing the flash procedure, and then reverts your host files back automatically after your done. You should try it.

dwaynedman said:
Just my .02 .....Get rid of Symantec !!
Click to expand...
Click to collapse
Symantec isn't really a choice on work PC.
Get yourself Comodo and save your money...
Click to expand...
Click to collapse
I'm sorry I can't give the link yet, but if you'll Google you'll see Comodo classifies shttp3.exe as "ApplicUnwnt.Win32.ServerWeb.SmallHTTP.~A" or "UnclassifiedMalware" (I guess depending on the version). A number of scanners find issues with shttp3.exe. I'm not saying it is infected, only that it is doing something suspicious.
Rick

Rick Tillery said:
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
Click to expand...
Click to collapse
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.

Back to square one
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick

The Dark Lestat said:
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Click to expand...
Click to collapse
Thank you, sir. I hope it didn't seem accusing.
Rick

Rick Tillery said:
Thank you, sir. I hope it didn't seem accusing.
Rick
Click to expand...
Click to collapse
It's cool, my friend.
Sent from my Samsung Galaxy S II w/ CM9

Rick Tillery said:
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
Click to expand...
Click to collapse
Is it safe to ignore the su version update?
Short of this, can I override the MD5 checksum? I realize that image could be corrupt, but if I'm just going to replace it with the GB release, does that matter?
Rick

You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne

dwaynedman said:
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
Click to expand...
Click to collapse
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick

Rick Tillery said:
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Click to expand...
Click to collapse
Remove your battery and keep the phone unplugged
Launch the mobile updater tool
Hold the volume+ button plug the phone in and keep holding the volume+ till the computer downloads the drivers your phone is now in download mode
Once the phone is picked up go to customer support on the LG updater tool and click on recovery phone put your imie number in click check (make sure its the right model) an let the updater tool do its job. Once its done flashing launch into recovery volume- plus power plus 3D button do a complete wipe and factory reset and reboot your phone ... you'll lose cwm and root and be back to full stock
Sent from my LG-P925 using XDA

Bricked?
No joy. Following the steps, the upgrade stopped at 6%. Trying a number of times, it eventually forced me to exit the program (no more restarts). Rerunning the updater (and downloading the 420 MB image yet again on a VERY slow connection) I tried again and again, with different combinations of battery and plug order with power and volume buttons, but nothing worked. Checking elsewhere I found some issues had been reported with Windows Vista/7, so I tried on an XP machine. Now the "Start Updating" bar is red (it was always gray with W7). But now when I try to restore (or even update for that matter), it asks for my S/N (it never did that before) and then says it is "no longer able to upgrade." Reading around, it seems this is an indication of the device being bricked.
Rick

It sounds like you are very close to getting it working Rick.
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Should Rick be trying to run LG Updater as administrator ? I didn't, but it might not hurt.
Regards & Luck,
Dwayne

http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Sent from my ****ty supported LG Thrill

dwaynedman said:
It sounds like you are very close to getting it working Rick.
Click to expand...
Click to collapse
I wouldn't have believed you early this morning, but now maybe...
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Click to expand...
Click to collapse
I tried a bunch of different combinations...none seemed to make the app happy. I finally punted Windows 7 and moved to an XP machine, only to get the "no longer able to update" message. At that point I assumed I was screwed (effectively bricked).
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Click to expand...
Click to collapse
It never really vibrated, but I was able to get back into CMR. Unfortunately NONE of my backups work at all. They all have MD5 checksum failures. I tried a trick I found online and got past that step, only to have it say a failure restoring /system. So much for CMR.
JReeher said:
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Click to expand...
Click to collapse
Which step? As I mentioned above, I can't even get the first step of the first section (updating the su binary). And if I start at the 3rd section, Symantec prohibits me from using shttp3.exe (I tried to unquarantine it, but it gives a permission error, even as Administrator, when I try to run it), so I'll have to use a different machine.
I was able to reinstall the CM7 3/15 release, so that's something. I was going to restore the stock recovery backup I made, but even that doesn't seem to work. I'm having issue with backups :-(
Rick

i have never been able to restore a backup. i dont know why... but i have tried several times in several different instances.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
rick tillery, if you want to get your phone back to alive and well i'd suggest doing this:
http://forum.xda-developers.com/showthread.php?t=1558723&page=3
4th post i think

Just downgraded. (Accidentally). Now I have some questions

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.

Issues after trying to Root : Bootloader Code 3 : Soft Bricked?

Using this guy's guide for the Nexus 5 I had no issues, bought a N6 today and was giddy to flash on Cataclysm for N6 and figured might as well use same person's guide for next phone up.
http://www.androidrootz.com/2014/12/how-to-root-nexus-6-windowsmaclinuxubun.html
Was able to unlock bootloader, then installed TWRP but now am getting the 'corrupt phone' message, however unlike others like I have read on XDA, am unable to boot up by just letting it sit. Screen turns off and that's that. Before beginning entire process I enabled "enable/allow oem unlocking". I'm assuming that when the phone factory resets after the bootloader unlock I need to go back in and recheck 'allow oem unlock' in dev options, but I didn't as I assume/ed that it wasn't necessary and the guide doesn't tell you to.
Tried relocking the bootloader to maybe get phone to open up, but terminal tells me that I need to have 'allow oem unlock' checked. Nice Catch-22 http://puu.sh/moOUf/d0f8fa9050.png
Tried formatting data from within TWRP and factory resetting/wiping everything but it tells me that it is unable to mount '/data'
Have since tried WugsToolkit and flashing to stock with 'softbricked' option enabled the shamu-mmb29k-fact....tgz image that I downloaded and imported myself into Wugs (was taking 10 minutes to dl 1%). That seemed to work and told me it was a success, however when I then went back to re-enable the bootloader via wugs it fails and reboots with the lock sign still open and boots again onto 'corruption' screen that then flashes off and turns phone off, left it for 30 minutes at one point and didn't boot so don't think I'm lucky enough to be able to sit if through like others who had that issue
Where to go from here? Really hoping I didn't brick this phone less that 3 hours after getting it. I can still boot and see the Google screen and can get onto the bootloader and used to be able to get into recovery (since wugs have been getting the android with red triangle)
Been rooting/rom'ing since day one that I've had androids. Had a Samsung Apollo with CM on it, same for the Nexus S, then the Galaxy Nexus, then the N5 and looks like my chain of no issues ended tonight
Anything you can do for guys would be greatly appreciated. No clue where to go from here....

So from what I gathered, I think you are in luck. It sounds like your bootloader is unlocked. This is a very good thing. Under no circumstances do you want to try to re lock it right now or do you ever when stuck not being able to boot or any issues like that. If you lock it while stuck, thats when you are soft bricked. If I remember correctly, I got myself in the same situation , although maybe with out a custom recovery installed. None of that matters though. The way to fix this is to reflash the the factory image. Here are the guides for that.
https://www.youtube.com/watch?v=K_m6bYNKrXQ
This is the video I used the first time. A bit rough but, It did the job.
https://www.youtube.com/watch?v=2hao_Yf-gaw
Here is a bit of a nicer one. I used it the second time around.
and lastly here is an xda post http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I would recommend reading and watching all of these and maybe doing more research so you really knows whats going on. The flash-all script is not going to work from what I've read and I've always done it manual so go with that. It may also be a good idea to keep the custom recovery, so look into to keeping that. Maybe it is as simple as not erasing the recovery partition and not flashing the recovery image. This is what should save your nexus.
Now, I am fairly new to the Rooting and ROMming, really only started 2 months ago, so I would really appreciate if any of the more experienced guys on XDA can confirm what I said. Please don't try any of this without confirmation from another member here, I do not want to be responsible for sending your device past the point of no return. I recently had to order a new Nexus 6 as the screen is dead, so I know it's frustrating to have that loss. In your case, as long as that boot loader is unlocked, you should be safe. Best of luck to you.

DO NOT RELOCK THE BOOTLOADER!!!!! I cannot emphasize how critical it is that you do not relock the bootloader, given the position you are in. If you somehow manage to relock the bootloader and "enable OEM unlock" is toggled off and Android will not boot (even after attempting a factory reset), then you are 100% bricked with no way to fix your phone. Personally, I leave my bootloader unlocked 100% of the time so that I can fix anything that may go wrong with my phone. Additionally, I (as well as many other users on here) will always advise against using Wug's or any other toolkit in order to do stuff to your phone. While they do provide a nice GUI as well as an easy way to install the necessary drivers, using the regular platform-tools command line method isn't all that hard to figure out, and it allows you to know exactly what you have done to your phone. With Wug's and the like, you never really know what commands that they are running and exactly at what point in the process a flash may fail. Right now, I would advise you to read up on using the platform-tools method to flash stock images. After you have all of the necessary drivers, platform-tools, etc. working properly on your computer, I would strongly advise that you download MMB29S (the latest official update) from the Google Developer page and flash it using the platform-tools method, NOT with Wug's. And whatever you do, I repeat, DO NOT LOCK YOUR BOOTLOADER!
---------- Post added at 07:03 AM ---------- Previous post was at 06:51 AM ----------
triguyrn said:
So from what I gathered, I think you are in luck. It sounds like your bootloader is unlocked. This is a very good thing. Under no circumstances do you want to try to re lock it right now or do you ever when stuck not being able to boot or any issues like that. If you lock it while stuck, thats when you are soft bricked. If I remember correctly, I got myself in the same situation , although maybe with out a custom recovery installed. None of that matters though. The way to fix this is to reflash the the factory image. Here are the guides for that.
https://www.youtube.com/watch?v=K_m6bYNKrXQ
This is the video I used the first time. A bit rough but, It did the job.
https://www.youtube.com/watch?v=2hao_Yf-gaw
Here is a bit of a nicer one. I used it the second time around.
and lastly here is an xda post http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I would recommend reading and watching all of these and maybe doing more research so you really knows whats going on. The flash-all script is not going to work from what I've read and I've always done it manual so go with that. It may also be a good idea to keep the custom recovery, so look into to keeping that. Maybe it is as simple as not erasing the recovery partition and not flashing the recovery image. This is what should save your nexus.
Now, I am fairly new to the Rooting and ROMming, really only started 2 months ago, so I would really appreciate if any of the more experienced guys on XDA can confirm what I said. Please don't try any of this without confirmation from another member here, I do not want to be responsible for sending your device past the point of no return. I recently had to order a new Nexus 6 as the screen is dead, so I know it's frustrating to have that loss. In your case, as long as that boot loader is unlocked, you should be safe. Best of luck to you.
Click to expand...
Click to collapse
Regarding the flash-all script, my friend and I just used the script included with MMB29S and it worked fine. In addition, I was able to use the one with MMB29K, MRA58K and MRA58R, all of which worked fine. I'm not sure if these scripts always work for some users and never work for others, but I always recommend that people who are new to flashing simply try them, as they are quite convenient when they work. In addition, I have only been in the rooting and ROMing scene for about a month or two as well, but I would consider myself pretty seasoned by now considering all the different ROMs, rooting methods, etc. that I have tried. All the advice that you gave to the OP is excellent and I agree with it all.

matthew2926 said:
Regarding the flash-all script, my friend and I just used the script included with MMB29S and it worked fine. In addition, I was able to use the one with MMB29K, MRA58K and MRA58R, all of which worked fine. I'm not sure if these scripts always work for some users and never work for others, but I always recommend that people who are new to flashing simply try them, as they are quite convenient when they work. In addition, I have only been in the rooting and ROMing scene for about a month or two as well, but I would consider myself pretty seasoned by now considering all the different ROMs, rooting methods, etc. that I have tried. All the advice that you gave to the OP is excellent and I agree with it all.
Click to expand...
Click to collapse
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff

triguyrn said:
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
Click to expand...
Click to collapse
No problem! It's too bad to hear about your device but at least you got a new one on the way. There is really no harm to at least trying the flash-all script. It will either work and save you time or fail halfway through and force you to flash everything manually.

triguyrn said:
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
Click to expand...
Click to collapse
Flash-all script is still broken, flash the img files individualy in fastboot.

gee2012 said:
Flash-all script is still broken, flash the img files individualy in fastboot.
Click to expand...
Click to collapse
You guys are life savers, thank you so much
Got it to work after I was getting ready to phone it in and bring it to a repair shop and eat whatever the charge might've been

messed up my bionic

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: