63 replies to this topic

[arcanexvi]

I keep getting an error when I try to flash cdt.bin_16G. It says "unknown partition" and "cannot determine image filename for cdt.bin_16G" HELP!!!!!!!!!!!!

moto-fastboot flash cdt.bin cdt.bin_16G

[theonlycosmic]

moto-fastboot flash cdt.bin cdt.bin_16G

THANKS SOOOOOOO MUCH. BTW, there is a new update out that is now .85 not .84 on rombot. IDK if anyone has tested this but it is on rombot so I hope DH or DT tried it.

EDIT: The file is only 223MB....IDK what MOTO did but it looks like they effd up.

[arcanexvi]

THANKS SOOOOOOO MUCH. BTW, there is a new update out that is now .85 not .84 on rombot. IDK if anyone has tested this but it is on rombot so I hope DH or DT tried it.

EDIT: The file is only 223MB....IDK what MOTO did but it looks like they effd up.

Please don't install it til we get a bunch of testers on it.

[arcanexvi]

And I take it you're back up and running?

[EmericanX]

Is it possible to make images from someone thats up and running? I think the problem I'm running into is that I attempted a revert on matts tool.. that failed on cdt.bin but continued on others... so even if the corrected cdt.bin for .84 is flashed... there are inconsistencies... which leads to the boot logo to black screen..

thats my feeling atleast.. all of the commands cleared btw.

[arcanexvi]

Is it possible to make images from someone thats up and running? I think the problem I'm running into is that I attempted a revert on matts tool.. that failed on cdt.bin but continued on others... so even if the corrected cdt.bin for .84 is flashed... there are inconsistencies... which leads to the boot logo to black screen..

thats my feeling atleast.. all of the commands cleared btw.

This would be correct. And matt has images. But they're for .85 so we'll have to see if this works first then proceed. I'll update the OP to reflect that this will only work for people who used RSD.

[theonlycosmic]

Is it possible to make images from someone thats up and running? I think the problem I'm running into is that I attempted a revert on matts tool.. that failed on cdt.bin but continued on others... so even if the corrected cdt.bin for .84 is flashed... there are inconsistencies... which leads to the boot logo to black screen..

thats my feeling atleast.. all of the commands cleared btw.

I used RSD Lite 5.7 and I still failed. I am back on .84 though because of the fix. Maybe we should try flashing via moto-fastboot and do all files except cdt.bin and THEN try it via RSD. Idk just another theory.

[theonlycosmic]

And I take it you're back up and running?

And yes I am. Thanks a lot you are a life saver.

EDIT: BTW I still have to use BP Tools to boot up. And I used RSD

[arcanexvi]

And yes I am. Thanks a lot you are a life saver.

EDIT: BTW I still have to use BP Tools to boot up. And I used RSD

Same. But it makes the phone functional and thank you for the confirmation.

[arcanexvi]

I used RSD Lite 5.7 and I still failed. I am back on .84 though because of the fix. Maybe we should try flashing via moto-fastboot and do all files except cdt.bin and THEN try it via RSD. Idk just another theory.

cdt is a mapping file... pretty sure that's going to fail regardless. You're welcome to try though

[nailbomb3]

Arc I rsd the other day and then took the OTA and rooted. Dirty said he had no problems reverting five devices.

Sooooo... Do you want me to try it out for science? Sounds like I can at least get back on the leak.

If you don't think it's a good idea to even try I won't... Cheers

Sent from where I sent it from......

[arcanexvi]

Arc I rsd the other day and then took the OTA and rooted. Dirty said he had no problems reverting five devices.

Sooooo... Do you want me to try it out for science? Sounds like I can at least get back on the leak.

If you don't think it's a good idea to even try I won't... Cheers

Sent from where I sent it from......

I wouldn't. This fix doesn't resolve the issue that you can't charge the phone when it's off as the failed flash is still triggered. It just makes your phone bootable/usable.

[theonlycosmic]

Nvm

[DarkOverDroid]

This build runs good, but I would like to get back on path. I have faith in Arc, and the rest of these guys. We`ll be good to go before long. Thanks for all your work Arcanexvi and DD. Get some rest man. Night peeps.

[nailbomb3]

I wouldn't. This fix doesn't resolve the issue that you can't charge the phone when it's off as the failed flash is still triggered. It just makes your phone bootable/usable.

Roger that, and thanks for your hard work!

[theonlycosmic]

Hey do you guys think motorola has a new tool out for the leak or something? I just checked their developer site and it is currently down...idk

[nailbomb3]

I wouldn't. This fix doesn't resolve the issue that you can't charge the phone when it's off as the failed flash is still triggered. It just makes your phone bootable/usable.

Well I went the 'science' route to help figure this out

Failed at step 6 like everyone else in RSD.

Ran your fixes, was able to reboot into leak.

However, it LOOKS to me that I CAN charge with the phone powered down. I'm looking at the thermometer now dude. If it goes up from 70 to 80 percent I'll know....

ETA: yes, it went from 70 to 80 percent.

ETA2: Booting into AP Fastboot it shows "AP Fastboot Flash Mode (S)" I don't see "Flash Failed" like I did post RSD.

[nailbomb3]

Okay, so still looks like charge while OFF works for ME: went from 70 to 80 and then to 90 on the thermometer. Booted into leak and checked Battery Monitor Widget and it was showing 85 percent (the thermometer rounds up, ie 85 percent charge will show 90 on the thermometer, 84 would show 80 percent).

So, Arc IF I were to full discharge would you still say it wouldn't take a charge?

[arcanexvi]

Mine is stuck @ flash failed. If yours isn't, you can charge fine.

Fixed. See the post following this one.

[arcanexvi]

Update: If you get stuck on the fastboot-failed menu every time you plug your phone in when it's powered down, I found a fix. It just needs a successful flash of the first 5 steps. It should reset the failed flag. Once you're done with the first 5 steps, rather than flash the cdt file again just execute command moto-fastboot reboot. Without the period obviously. The phone should reboot normally into your .84 leak without hiccuping and requiring you to use the BP menu to boot the phone. This also re-enables charging with the phone off. This doesn't fix any other issues. Just those that are able to get back up and running on .84 but were having to go through the menu every reboot.

[rexboe]

Worked for me

[jawse]

i assume no one has ics fastboot files?

[jawse]

i used matt's utility so can't really go back get back to leak this way

[mugsy77]

i used matt's utility so can't really go back get back to leak this way

Ditto. Guess I won't bother to try to revert back. Bummer...

[porkshanker]

I am stuck as well..... "prays there will be a fix". Although my wifes upgrade is available... lol

[PWn3R]

arcane, when you guys were testing did you install with the app we don't speak of? Also, which SBF did you use and what version of RSD?

[theonlycosmic]

Okay so i just thought of a solution. What happens if we delete the files that fail when we fastboot on our phone through ES File manager etc. Like the cdt.bin file, what happens if we find the file/files that it installed on our phone so we can just delete that and it SHOULD go through. However, for the people that are using Matt's Utility said that it failed on more than just the cdt.bin file. SOMEONE TELL ME IM RIGHT! LOL

[EmericanX]

The problem is this. When you fast boot back the partitions that go through are flashed but the ones that fail remain updated to the leak. This leaves you with a mixed file system where obviously there are conflicts. The fast boot files are failing to flash due to the upgraded files during the upgrade. So until resolution to that issues you're stuck where you are. If we were miraculously able to find the update fast boot(ics) files I think we would be able to flash over what we have to move forward. But being that this is a leak there's no telling when that will happen! Upgrading to ICS is not just a maintenance update as the other OTA's have been. It is an upgraded OS... so I'm betting they will have fast boot imgs for it once it becomes official. So right now I'd say its a matter of time. Time until someone figures out how to get past the file verification reverting to GB... or time until we get the images to fast boot forward. I don't think you'll be able to find the files you're referencing in es file explorer... and even if you were.. I would leave them untouched for now.

Sent from my Galaxy Nexus using Tapatalk 2

[arcanexvi]

The problem is this. When you fast boot back the partitions that go through are flashed but the ones that fail remain updated to the leak. This leaves you with a mixed file system where obviously there are conflicts. The fast boot files are failing to flash due to the upgraded files during the upgrade. So until resolution to that issues you're stuck where you are. If we were miraculously able to find the update fast boot(ics) files I think we would be able to flash over what we have to move forward. But being that this is a leak there's no telling when that will happen! Upgrading to ICS is not just a maintenance update as the other OTA's have been. It is an upgraded OS... so I'm betting they will have fast boot imgs for it once it becomes official. So right now I'd say its a matter of time. Time until someone figures out how to get past the file verification reverting to GB... or time until we get the images to fast boot forward. I don't think you'll be able to find the files you're referencing in es file explorer... and even if you were.. I would leave them untouched for now.

Sent from my Galaxy Nexus using Tapatalk 2

Pretty much this. We sit around on. 84 til we get ICS fastboot files.

[kaplac]

so I'm going to be sitting on a bricked phone for over a month?