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?
Everytime I update past 886, I get this error:
Ap fastboot flash mode s (invalid cdt)
0a.61
Battery OK
OK to program
Connect usb
data cable
Invalid cg version (cg: cdt)
Invalid cg version (cg: cdt)
--
At that stage I can't even boot into recovery (holding volume up+down then power), I tried running fixcdt, it makes it so I can boot into recovery, but if I flash anything, I get taken back to the same screen above.
Does anyone know how I can fix this? I've been up all night trying to. Thanks.
If your using the path saver, if you go directly to .901 without rebooting, you won't get that error.
If you want to stay on .893, install the 901fix file and the cdt.bin directly into the same folder with the path saver and do not close the command window after update, stay plugged in. After .893 install it'll boot to fast boot cdt failure. Now click on the 901fix, it will install and reboot back into your system.
Hi - I've started receiving a bunch of errors on my phone indicating a lot of processes are failing. Have tried resetting app preferences after searching through a lot of forums but these problems still persisted. Factory reset didn't help either. I'm bootloader unlocked and rooted so thought I'd flash a new ROM via RSDLite. I am unable to do this either. I receive the error "Failed flashing process. 1/12 flash gpt "gpt_signed" -> Phone returned FAIL.." (see attached screenshot). On the phone itself I see the following:
E: Can't read /dev/block/misc
(I/O error)
E: Failed to get BOX sync msg from MISC
Fastboot Reason: Reboot to bootloader
fastboot: max download size: 100Mb
USB connected
Getvar max-download-size
Downloading ...
Flashing gpt ...
E: re-partition failed: Device or resource busy
Fastboot command failed
I fear this means I have a corrupted internal SD card so no way to fix... however I'm no expert on this. Any idea how to fix please?
Thanks,
UPDATE
Without any further tinkering on my part the phone is no longer able to boot up. It's now alternating between the "intel inside" logo and motorola logo. Also feels pretty warm. I'm kind of giving up on the device and have ordered a new phone already. If anyone has a quick fix to revive it then feel free to let me know else will use it as a nice paperweight. Thanks.
Hi - I've started receiving a bunch of errors on my phone indicating a lot of processes are failing. The OS version is Android 4.1.2 Jelly bean. Have tried resetting app preferences after searching through a lot of forums but these problems still persisted. Factory reset didn't help either. I'm bootloader unlocked and rooted so thought I'd flash a new ROM via RSDLite. I am unable to do this either. I receive the error "Failed flashing process. 1/12 flash gpt "gpt_signed" -> Phone returned FAIL..". On the phone itself I see the following:
E: Can't read /dev/block/misc
(Bad file number)
E: Failed to get BOS sync msg from MISC
Fastboot Reason: Flash Failure
fastboot: max download size: 100Mb
USB connected
Getvar max-download-size
Downloading ...
Flashing gpt ...
E: re-partition failed: Device or resource busy
Fastboot command failed
Fastboot menu disabled
I fear this means I have a corrupted internal SD card so no way to fix... however I'm no expert on this. Any idea how to fix please?
Thanks,
U copy/pasted another forum post , ah well it works.
It is indeed that your phones memory is corrupted.
I maybe have a solution, but first i need to know what firmware u are using.
Hazou
Hi everyone.
I am having a problem getting my atrix hd to load stock rom.
I have downloaded the stock att rom (MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml_.zip)
I use fastboot and the sd card to install cm roms but this does not work it says (installing update... then installation aborted...)
What i dont understand is what to do with the xml file before i flash it. Or do i flash multiple files from the xml.
Any help or a point in the right direction would be greatly appreciated.
Another acceptable fix would to be able to unlock my network from cm 10.1 everything i have read says it cant be done but i dont see why.
Follow up
Ok so I found that the .xml file can be loaded with RSD lite in windows. Since I use linux I found the script for flashing xml files with fastboot from root junkie. I followed the instructions and got it to start flashing. During the first file upload it returns an error md5 mismatch. So I found another "stock" image and tried again to the same end. I then compared the md5 sums to the ones in the .xml file and they are correct so there downloading to the pc fine.
Today I borrowed a windows computer and downloaded RSD lite and the "stock" roms. When RSD tries to flash to the phone I get the same md5 mismatch but it adds "phone returned fail". I can still flash back to cwm useing fastboot and boot in to cm just like before I started this.
Any ideas as to why the stock images won't flash?
I'm beginning to wonder if the usb cable could be questionable. Is it posable that it may load cwm over a kinda bad cable?
I tried removing the md5 sums from the xml file. It then flashed to the device with a few errors. Now the phone just boots directly to fastboot it says reason flash fail. But now I can't flash cwm back I keep getting FAILED (data transfer failure (value too large for defined data type)).
Now I have bought another motorola atrix hd rooted ubl and installed cwm. I created a zip of its image from cwm and installed it on my old atrix. I know thats a little much to have to do but i couldnt find a working image for the atrix hd. Now the phone comes on and most things work good But I have now LTE radio no WiFi and no bluetooth they worked in cm before all of the trying to get back to stock. Im not sure if the problem was caused by the install from the cwm zip or from some of the messing around i did first. I have found info about flashing "NON-HLOS.bin" but when i try i get the following.
$ fastboot flash modem NON-HLOS
.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28172 KB)...
OKAY [ 2.509s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 4.414s
I have read that there is a special mfastboot for windows but i only have ubuntu. I suppose this could be why the flash from RSD for linux didnt work. Could that be possible?
Am i going to have to get a windows computer to do this?
After trying to reboot post failure of modem flash I had fastboot forced because of a failed flash. I tried to flash the logo file from the same image as the modem file and the logo worked fine then the phone booted fine but still no radios