212 replies to this topic

[RaSuRaDoRa]

Please Login or Register to see this Hidden Content

um can this proably be the solution to our problems!?

[spryte]

holding PWR+Vol DWN+Vol UP brings up a menu, correct? Plug your phone in after having that up & navigate to BP Tools. It should charge after you select that.

Yeah, it should, I have already tried every opiton from this menu, but the result is the same.
I only see the red M for half a second and afterwards I see the screen I posted above, which tells me: Invalid Flash Mode: Boot Error

[TwoBuells]

Try this,
Hold all three buttons for over ten seconds, until the screen flashes. It’s a ¼ inch high flash across the screen. Before the phone boots plug in the AC wall charger. If you see the moto logo do it again. You want to see the battery hourglass with a question mark. It will go dark. Press one of the volume buttons and the hourglass will come on again and show you the % the battery is charged. Do not unplug, do not hit the power button.
Its real tricky to do this and I’m not sure where you phone is coming from, I mean try this from the reboot menu or try this from the AP Fastboot mode.
The trick is to get the phone off and plug into a AC charger.

[MartyChubbs]

It is NOT possible to charge it, because of the boot error. I have somehow managed to screw up the software completely so that nothing works anymore, neither charging, nor entering the recovery... will have to return it...

Only shot is to make a factory cable. If the system image is corrupted, it won't charge. If you make a cable, it powers the phone to fast boot, the battery will not charge from the cable nor can you use it as a usb transfer cable.

Please Login or Register to see this Hidden Content

Please Login or Register to see this Hidden Content

: a similar idea, but a different cable and solder points.

Please Login or Register to see this Hidden Content

The tools cost me less than $10 and I used one micro usb cable

Good luck!

[spryte]

Thanks for your support, today, my ordered factory cable from China was shipped (~10$ incl. shipping).

I will wait until it arrives (~4 weeks) and then I will try to flash my previous build,
but I am afraid it won't work, as everything (even the RECOVERY ^^) is screwed up (Do I get it right, when I assume, that even fastbooting back, won't provide me a working recovery.img due to the signature failures?)

[MartyChubbs]

Thanks for your support, today, my ordered factory cable from China was shipped (~10$ incl. shipping).

I will wait until it arrives (~4 weeks) and then I will try to flash my previous build,
but I am afraid it won't work, as everything (even the RECOVERY ^^) is screwed up (Do I get it right, when I assume, that even fastbooting back, won't provide me a working recovery.img due to the signature failures?)

It will allow you to flash on a dead battery, that is your only roadblock IMHO

[Devil390464087]

Mattlgroff's Droid RAZR

Please Login or Register to see this Hidden Content

1.6 This file can't download ?

[tradke14]

Currently running the ICS .84 leak and hosed up my phone this morning and got stuck in the boot animation. Used this method to bring my phone back. It takes a little time, but works great!

Thanks for posting your solution!

[footballbmb9]

After trying mant many times and doing the exact same thing over and over I finally once again downloaded fresh files and finally this method worked for me! thank you

[EmericanX]

Don't worry man. I went through the same thing. Ended up formatting my sdcard then it flashed the first time!

Sent from my DROID RAZR using Tapatalk 2

[djuniah]

Just wanted to say thanks for this! Came in handy. I was trying to port a rom and completely hosed my /system. This recovered it nicely.
(restored with this, re-rooted, bootstrapped, restored backup)

[londonfire93]

possible solution if you made a nandroid backup of a previous version such .181 restore it on top of the ics build. this might overwrite the system enough to be able to fastboot/rsd back to .173. i have not tried this but it could work so if someone is willing to try this let me know what the results are.

[footballbmb9]

possible solution if you made a nandroid backup of a previous version such .181 restore it on top of the ics build. this might overwrite the system enough to be able to fastboot/rsd back to .173. i have not tried this but it could work so if someone is willing to try this let me know what the results are.

has anyone tried this method? curious to see if this would even work...

[mattlgroff]

has anyone tried this method? curious to see if this would even work...

This shouldn't work. The cdt.bin and device_tree.bin from ICS would stick and see the system.img as invalid.

[footballbmb9]

This shouldn't work. The cdt.bin and device_tree.bin from ICS would stick and see the system.img as invalid.

So what if you used CWM on boot mod and then flashed the cdt.bin and the device_tree.bin from GB using the command prompt and moto-fastboot and then tried to restore the nandroid backup then sbf back to 181.... just trying to think here...

[theonlycosmic]

This shouldn't work. The cdt.bin and device_tree.bin from ICS would stick and see the system.img as invalid.

Is it possible to delete the files and replace them somehow? Idk just throwin stuff out there

[footballbmb9]

Is it possible to delete the files and replace them somehow? Idk just throwin stuff out there

haha yeah thats what i was saying...

[wyld]

Just me spit balling idea's like everyone else. Lol What if the necessary files were taken from .75 and put into a custom rom for .84/.85 and then flashed in CWM would the files overwrite that way?

Sent from my DROID RAZR using Tapatalk 2

[EmericanX]

Is it possible to delete the files and replace them somehow? Idk just throwin stuff out there

Tried deleting from fastboot... of coarse! Feature blocked... lol

Sent from my DROID RAZR using Tapatalk 2

[mattlgroff]

If you managed to delete the partitions you'd probably be screwed over...

[xlightwaverx]

So now everyone is trying to do what I have been trying to do one week ago? You guys gotta catch up


I was thinking, .181 boot.img and cdt.bin, and .85 dev_tree.bin and system.

But we'll have to design it the OTA way using WinMerge and .75 OTA vs .85 OTA.

There's lots of lines of code that needs to be changed, specially for cdt.bin but we can just use .75 cdt.bin, renamed to one of the .85s (8g, 16g) so devtree.bin works.

Kabeesh?


X

[cconcepts]

So now everyone is trying to do what I have been trying to do one week ago? You guys gotta catch up


I was thinking, .181 boot.img and cdt.bin, and .85 dev_tree.bin and system.

But we'll have to design it the OTA way using WinMerge and .75 OTA vs .85 OTA.

There's lots of lines of code that needs to be changed, specially for cdt.bin but we can just use .75 cdt.bin, renamed to one of the .85s (8g, 16g) so devtree.bin works.

Kabeesh?

I too have been thinking about the same for awhile myself but no test phone to try it on....the cdt8g has the exact code as the gb cdt.bin in all otas....the 16g has the same code but also contains a few more lines of code.....so im thinking 16g is our main culprit...... maybe rename 16g to just cdt.bin and replace the one from .181 in the fastboot file?


X

Sent from my DROID RAZR using Tapatalk

[xlightwaverx]

Sent from my DROID RAZR using Tapatalk

I am not sure which one is used, but i found the update script in the .85 ota and .75 ota and there is a script that deciphers which cdt.bin to use on the .85 and renames it to cdt.bin. Hence, we can use use old cdt.bin from .75 and use the old code in the new update script of .85. I am thinking about creating a drop box account for this process so i can have some collaboration on this. Maybe Drive since it has more security.

X

[xlightwaverx]

I am not sure which one is used, but i found the update script in the .85 ota and .75 ota and there is a script that deciphers which cdt.bin to use on the .85 and renames it to cdt.bin. Hence, we can use use old cdt.bin from .75 and use the old code in the new update script of .85. I am thinking about creating a drop box account for this process so i can have some collaboration on this. Maybe Drive since it has more security.

X

Also if we use the old cdt.bin, we would have to use the old bootloader as well. But this is where issues supposedly arise but the vets should be able to comment on that.

[xlightwaverx]

Also if we use the old cdt.bin, we would have to use the old bootloader as well. But this is where issues supposedly arise but the vets should be able to comment on that.

Anywho, I am going to get started on this after today. Big dance recital for the fam, and I need to focus on that. Then I might try with the above projections. By the end of the day today we should have some more ideas and comments going on to what will and wont work.

X

[StealthFox13]

Ok so i tried going back to .173 from .84 again and it did not work. is this what i do to get rid of my funk and get a working phone again? (nOObing it up again)

[kboss805]

Ok so i tried going back to .173 from .84 again and it did not work. is this what i do to get rid of my funk and get a working phone again? (nOObing it up again)

Can you provide some details on the errors you received?

[StealthFox13]

locked at the boot animation. when i run utility it tells me that cdt.bin, devtree, boot, recovery, and cdrom all say INFOPreflash validation failure

[mattlgroff]

locked at the boot animation. when i run utility it tells me that cdt.bin, devtree, boot, recovery, and cdrom all say INFOPreflash validation failure

Yes, they will. You have to upgrade to 84/85 from the Recovery... read the OP.

[StealthFox13]

so will this work with utility 1.42?