Database Develop

[Q] Restore from Fastboot or other method?

So basically Im stuck.
After goofing around with this thing I wanted to restore to stock. I didnt back up any bloat software and attempted this.
Now im stuck where it wants you to add accounts, upon hitting next it asks for my location permissions, then it crashes because of myaccount.apk, then that loops.
After playing around im totally botched...
Booting normally leads me to a "AP Fastboot Flash Mode (Last Flash Failed)" screen. I can kill that and get to the "Boot Mode Selection Menu" as well. Selecting recovery from that menu will erboot to the typical dual core boot screen, then back to "invalid flash mode"
Long story short - is there a file or method that will get me back to factory from here?

You can use psouza4s tools to restore your /system/app.
Sent from my DROID3 using xda premium

From what boot mode though? I cant get IN to android so I cant connect via ADB.
Boot Menu results:
Normal Mode: Invalid Flash Mode
Recovery Mode: Invalid Flash Mode
AP Fastboot: ALL GOOD
BP SBF Flash: ALL GOOD
BP Only: Sits at the M Dual Core Screen - But device is detected
AP BP USB Bypass: Sits at the M Dual Core Screen - But device is detected
BP Tools: Invalid Flash Mode
My guess is I need to flash a recovery file somehow to get to a proper recovery, then some kind of update.zip or such I can flash.

edru said:
From what boot mode though? I cant get IN to android so I cant connect via ADB.
Boot Menu results:
Normal Mode: Invalid Flash Mode
Recovery Mode: Invalid Flash Mode
AP Fastboot: ALL GOOD
BP SBF Flash: ALL GOOD
BP Only: Sits at the M Dual Core Screen - But device is detected
AP BP USB Bypass: Sits at the M Dual Core Screen - But device is detected
BP Tools: Invalid Flash Mode
My guess is I need to flash a recovery file somehow to get to a proper recovery, then some kind of update.zip or such I can flash.
Click to expand...
Click to collapse
First of all . . . don't wipe. Second of all, have you tried the booting into bp tools method with your terminal/power shell set to:
Code:
adb wait-for-device shell

rynosaur said:
First of all . . . don't wipe. Second of all, have you tried the booting into bp tools method with your terminal/power shell set to:
Code:
adb wait-for-device shell
Click to expand...
Click to collapse
Too late. Wiping is how I ended up in this position :/ - And Im unable to do the adb wait command because BPTools gives me invalid flash mode.

if there was a way to get a backup in a recovery update.zip form place on a sd card and use the recovery menu

Again here is what happens when selecting different boot modes.
Boot Menu results:
Normal Mode: Invalid Flash Mode
Recovery Mode: Invalid Flash Mode
AP Fastboot: ALL GOOD
BP SBF Flash: ALL GOOD
BP Only: Sits at the M Dual Core Screen - But device is detected
AP BP USB Bypass: Sits at the M Dual Core Screen - But device is detected
BP Tools: Invalid Flash Mode
So recovery is not an option as you can see.

Boot to where your phone is detectable use psouza4s tools get the system restore apps he provides his tools will install them ... all bloatware will be back..

Anyone who has a bricked DROID 3 phone (Verizon only), I may have a solution for you.
Requirements:
Windows platform
7-zip installed (and know how to extract files)
ability to follow all instructions exactly
willingness to factory reset/lose data on their phone
This unbrick method is NOT guaranteed to work, but it's very hopeful for most situations where other methods aren't working. If you are in desperate need of a fix, send me a PM and I'll link you some files to try.
Lastly: I will not be walking through anyone step by step on how to run this procedure -- the included instructions should be more than enough for most people. If you read the instructions and are thoroughly confused, then this fix isn't for you.

[Q] Cant fix phone, help??

Hi,
I ran into a bootloop on my phone so I was trying the FXZ fix. I have tried flashing both the complete and the minimal one. The minimal works fine, however I still cannot boot. So I have been retrying the complete FXZ numerous times and it cannot for the life of me get past 14/15 with the grfs.img webtop. So I tried using ADB to flash just that file and I get the same error both ways. It says the phone is not expecting the size of the grfs.img file and just says fail. "Sending 'grfs' <1364736 KB>... FAILED (remote: too much data to fit into memory)"
Anyone have any idea what I can possibly do, or is my phone "bricked".
Here is what happens when I try to just normally boot, it'll show the M with dual core logo for a minute, then it goes into "invalid Flash Mode (s) (Boot Failure)
battery OK
OK to program
Connect USB
Data Cable
Invalid CG OTV (CG: cdrom):invalid SP Data
Invalid CG OTV(CG: system): Invalid SP Data
Invalid CG OTV (CG: webtop): Invalid SP Data
Invalid CG HAB (CG: webtop, status: 0X004E)
Invalid CG OTV (CG: webtop)
And that's it. Any help would be greatly appreciated as I really would not like to go back to the only phone i have left... an LG chocolate -_-
EDIT: FIXED! I kept trying to flash, no joking i flashed it around 100+ times and it FINALLY got past 14/15... so happy c: Thread can be deleted if moderator sees... since it wasnt terribly useful as it happened soon after i posted.
thank you!

Glad it worked out for you. Why did you need to FXZ in the first place?
Also, if I had to go back to my old Chocolate, I'd kill myself in the most painful way possible. I had to bring my Chocolate back under warranty 7 times for nothing that I did to it, all equipment failures.

snael said:
EDIT: FIXED! I kept trying to flash, no joking i flashed it around 100+ times and it FINALLY got past 14/15... so happy c: Thread can be deleted if moderator sees... since it wasnt terribly useful as it happened soon after i posted.
Click to expand...
Click to collapse
Ahhhh, that's amazing! Thanks for posting that, I ran `fastboot flash webtop vendor.img` like 15 times and it worked the 16th
---------- Post added at 11:58 AM ---------- Previous post was at 11:05 AM ----------
Actually, that didn't fix it for me--if you're using fastboot:
The webtop img file apparently needs to be sent and written in chunks because of its size, which the moto-fastboot will do correctly and the standard fastboot will not. Get moto-fastboot here: http://forum.xda-developers.com/showthread.php?t=1138092

So, if fail...try, try again?

http://db.tt/AveMC40y
You need an updated fastboot binary that supports the larger image sizes used on Motorola devices.
Use either the fastboot.exe or mfastboot.exe from the zip above and it will work.

{Fix} CG:boot / Flash Failure / Status 7 / sideload/package.zip / ro.build.product

Timmy10shoes - you are the man.
Over the last few years I have owned a few OG Droids, Droid 2, Droid 3, Droid X, Droid X2, and my Droid Bionic. Never during those years have I been in a pickle like I was with my Bionic, trying to rid myself of some cheesecake. I have traveled from end to end on the world wide web searching for the elusive fix to my nightmare.
Started out like many other days over the last few years of rooting droids, never satisfied always wanting more. I had 4ever root on cheesecake .893 and decided to install the .901 update from a zip. Bingo lost root, don't really use the benefits of root to often, but of course I wanted what I couldn't have. So I decided to use P3's one click and that's when me and my Bionic got to know each other inside and out.
Timmy10shoes your write up and links, were my reason for a happy dance today. Over the last 24 hours I have seen failed RSD flashes, failed updates, failed programs, failed dos commands, failed root, and my favorite - permenant in your face Fastboot screen reminding me of a Failed Flash with the awesome CG:boot error.
Timmy10shoes Original Post:
rootzwiki.com/topic/13485-unbrick-your-bionic-here
Thanks to Timmy10shoes, P3, BBB and all others that make tinkering with our big boy toys possible.
Here is a link to my file that fixed all my woes:
megaupload.com/?d=AL3PQ3PN
Its a zip'd file, 673.58 MB, of all the links in Timmy10shoes original post, with the modifications per hs instructions. Open RSD and point to default_flash_targa.xml and push start in RSD. May others experiences be as good as mine.
#################
Some Errors This Should Fix:
Flash Failure / Invalid CG Version CG; boot
Installing Update...
assert failed: getprop ("ro.product.device") == cdma-targa" ||
getprop ("ro.build.product") == "cdma-targa ||
Error in /sdcard/update901.zip
(Status 7)
Installation aborted.
Error load file: could not allocate 1397489664 bytes error: connot load grfs.img
No 3g or 4g
flash cdt.bin "cdt.bin" phone returned fail
Error in /tmp/sideload/package.zip (status 7)
and many others
#################

Failed
I get a
"Failed flashing process 1/14 erase cache"
My phone powers up to the
AP Fastboot Flash Mode (S) (Invalid CDT)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG Version (CG: cdt)
Invalid CG Version (CG: cdt)
It will not boot to recovery goes strait to Fastboot at power up .Any ideas?

I have had success fixing the CDT error with this file from BBB:
megaupload.com/?d=JHSHG1G0
Plug your phone in via usb, click on 901fix.bat and it should reboot your phone.

figured out it needed the .901 cdt bin flashed with the help of others here. Now at least I have a working phone but no data. Doh! data back all good now.

Since this is really just a thank you thread I am posting the steps I will be following to update my second bionic from what I found worked consistently after my 14+ hour pathsaver marathon where I got all the errors in the title of the thread. Happy to also share my trial/error if anyone wants it.
Run pathsaver from p3droid with BBB fix2 files to replace default ones
Install 893 and 901 updates from stock recovery by pressing both volume buttons
Normal boot into 901
Rooted 901 = yes = awesome
No rooted 901 = continue on
Run pathsaver again with BBB fix2 files to replace default ones
Install 893 update only from stock recovery by pressing both volume buttons
CDT error on fastboot after 893 install = no = awesome
Normal boot into 893, rota 893 from BBB, reboot into recovery by holding both volume buttons, install 901 update, keep root
CDT error on fastboot after 893 only install = continue on
Manually flash boot.img (from “fastboot images” zip file for “Stock 5.5.1_84_DBN-55” ) and cdt.img (from BBB root fix2) using commands found in BBB post 3 of Invalid CG version thread
- “moto-fastboot flash cdt.bin cdt.901” and “moto-fastboot flash boot boot.img”
*OR flash 893 fxz which will fail at cdt (step 6) then manually flash cdt from BBB root fix2 (this will also clear both CG and CDT errors)
Hold power after flashing both to turn off
Hold power AND both volume buttons when turning on
Normal boot into 893, rota 893 from BBB, reboot into recovery by holding both volume buttons, install 901 update which should keep root
* I found all of the above to work consistently for me (whether it makes sense or not). YMMV

Thank you so much mrazwolverine for posting this
You are the saver of my bionic
I was having major problems with p3 1 click to a point that I don't have radio to setup the bionic and stuck at for awhile
Tried every method out there like forever root recover, fastboot files etc and nothing work, until I saw this post
Work like a charm
I do notice that after update from. 893 to. 901 I lost root
So I just went ahead and do it again
After .893 update I use forever root to root and install forever root before I update to. 901 and it kept root this time
So for anyone doing this to update to .901 I highly recommed you to forever root .893 before updating to .901 to keep root
Thanks again mrazwolverine

Happy to hear you were able to fix your issues.

Thank you!
This restored my phone perfectly...like it came from the factory and that's exactly what I was looking for! I really appreciate you posting this. Extremely useful!!!

How do we do this on a MAC?

My Optimus Dead Help me

First a good afternoon,
my phone is faulty, it no longer starts when I turn on my phone it goes into recovery mode, volume tightening down and put the cable into your computer boots into recovery mode, the worst that he would not let me do anything in recovery, because it the error
E: Can not mount CACHE: recovery / command
E: Can not mount CACHE: recovery / log
E: Can not open CACHE: recovery / log
Formatting MISC: ...
room for the chuck norris I can install but not work so back to the recovery, I have a doubt with chuck norris in the installation I get into the system and see the folders inside the cache cell type, root etc., if I do a arrumasse backup of the original cell or coerce people to copy to my phone work?
Help me please, I do not know what to do, my phone is not even 1 month of use.
If you have any idea really need help because I can not connect to the phone can not put debugging usb or anything.

remove battery to 5 min and try again... i hope will be fine...

robsonverly said:
First a good afternoon,
my phone is faulty, it no longer starts when I turn on my phone it goes into recovery mode, volume tightening down and put the cable into your computer boots into recovery mode, the worst that he would not let me do anything in recovery, because it the error
E: Can not mount CACHE: recovery / command
E: Can not mount CACHE: recovery / log
E: Can not open CACHE: recovery / log
Formatting MISC: ...
room for the chuck norris I can install but not work so back to the recovery, I have a doubt with chuck norris in the installation I get into the system and see the folders inside the cache cell type, root etc., if I do a arrumasse backup of the original cell or coerce people to copy to my phone work?
Help me please, I do not know what to do, my phone is not even 1 month of use.
If you have any idea really need help because I can not connect to the phone can not put debugging usb or anything.
Click to expand...
Click to collapse
Remove the Battery.Plug in the USB to the computer.while keeping the Volume Down key pressed Attach the USB to the Phone.it should take you to the Software Update Mode.Flash A KDZ file(look for tutorials on XDA) and your phone SHOULD be back to Normal.

Either u can use NV flash
manasgirdhar said:
Remove the Battery.Plug in the USB to the computer.while keeping the Volume Down key pressed Attach the USB to the Phone.it should take you to the Software Update Mode.Flash A KDZ file(look for tutorials on XDA) and your phone SHOULD be back to Normal.
Click to expand...
Click to collapse
Either u can use NV flash, follow the link http://forum.xda-developers.com/showthread.php?t=1229407

Try flashing using another computer. It did work for me...happy flashing

Question Can't Load Bootloader

First off, I'm a little out of my depth here.
I had originally wanted to root my A8, but stopped short because it isn't officially supported by TWRP. I wanted to roll things back but botched the Odin process. I flashed the AP file but didn't include any of the others. As a result, I can't get into the bootloader. I'm not sure what my options are at this point, or if I have any.
I've already wiped the cache partition and done a data/factory reset.
Output on my Recovery screen is as follows:
Code:
Failed to load locales from the resource files, Failed to compare
#Reboot Recovery Cause is [UNKOWN]#
#Reason is []#
E:Failed to load bitmap installing_text for locale en-US (error -1)
Supported API: 3
# MANUAL MODE v1.0.0#
No command specified.
I'm hoping there's a procedure for completing loading in the other files, or getting back into the bootloader.
Do I have any hope or did I truly brick this thing?

Ok, I got it back by using vol up/down and plugging in the USB. Wasn't able to do it from the recovery, but the physical method worked. Odin worked, I'm back in business.