Database Develop

RSD Error: Phone(0000) Not Compatible with super-file. (ox703b)

Full error message: Failed flashing process. phone(0000) Phone is not compatable with multi-interface super-file. (ox703b): phone connected
This is information only hopefully for someone who experienced the same issue that I did.
Long story short, I ended up boot looping my X by replacing a system file through Root Explorer and not setting the permissions properly before. Going into a panic, I started gathering the files to re-flash 2.1. When I tried to run RSD, I received the above error message. I tried different versions of RSD, different "gifts", different computers and operating systems. I hit google and was unable to find anything to help. I ended up returning my phone to Wal*Mart and got a new one (told them it bricked during an OTA update...)
After sending some messages to rootzwiki and alldroid for some help, I found that it was because the battery was not at 50% or higher (which makes sense because I let the phone loop for a couple hours disconnected from the PC in HOPES that it would come back). I'm not saying this may be the fix for all issues with the above error message, but it may be something else to try if you have tried everything and just about pulled your hair out...
Hope this helps!

FYI the only version of RSD Lite that will work with the X is veriosn 4.7, but you also have to have the OMAP patch file installed otherwise it will still not work. That said I'm not sure which version you tried or if you had it setup correctly but that could be why you wer having issues also besides the battery not being charged enough.

will2live said:
FYI the only version of RSD Lite that will work with the X is veriosn 4.7, but you also have to have the OMAP patch file installed otherwise it will still not work. That said I'm not sure which version you tried or if you had it setup correctly but that could be why you wer having issues also besides the battery not being charged enough.
Click to expand...
Click to collapse
I started with 4.7 and worked backwards with RSD. I have been able to flash my second X with the same config settings on 4.7. The only thing that changed was the charge on the battery

Where can I find the omap patch file is it the ini file located in the rdslite 4.7+patch.zip? Im getting the same error above but my battery is 96% full. This is happening on two differnt Windows 7 32 bit machines..
Sent from my DROIDX using XDA App
Never mind it is the patch and its now restoring.

I can upload my version of RSD and the patch I have when I get home from school.
It is going to be about 3 hours.

No need, found here: http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X/Page-3.html
Direct link to SBF: http://www.wikifilez.com/Root Files/MotoDroidX/RSDLite-4.7+patch.zip

uninstall all the moto drivers and re-install them again. see if that works.

[Q] Overheating? Logcat attached

All,
I received a replacement N1 yesterday from HTC as my previous one developed an earpiece issue. After unlocking the bootloader for the first time, it seems that the phone is overheating and randomly rebooting. I reflashed to stock, with the only exception being the unlocked bootloader using a guide found on this forum.
This was my first experience unlocking the bootloader and trying to flash a rom. I've attached a logcat to see if any info can be provided.
Thanks.
EDIT:
N1 - 1 day old HTC refurb
2.2.1
FRG83
Baseband - 32.41.00.32U_5.08.00.04
Kernel - 2.6.32.9-27240-gbca5320

Is the phone actually getting hot?
This is why I don't get why people get a phone and IMMEDIATELY start loading custom ROMs and such on it.. Use it stock for a few days to make sure it's good.

No it's not getting overly hot. My original N1 got much hotter.
Its my fault for not waiting, I do realize this.
I did wait 6 hours or so, but I know it wasn't enough. Got a bit anxious to load CM6.1.
I had first accidentally loaded Insecure boot which made the rebooting much more common, but went back to stock, and loaded superboot. Everything was fine for a little while, then the rebooting started again.
Just trying to see if I can figure out the issue before giving HTC a call.

etacv said:
No it's not getting overly hot. My original N1 got much hotter.
Its my fault for not waiting, I do realize this.
I did wait 6 hours or so, but I know it wasn't enough. Got a bit anxious to load CM6.1.
I had first accidentally loaded Insecure boot which made the rebooting much more common, but went back to stock, and loaded superboot. Everything was fine for a little while, then the rebooting started again.
Just trying to see if I can figure out the issue before giving HTC a call.
Click to expand...
Click to collapse
when i got my nexus back in early january, i dont think that i waited more than a hour before i unlocked the bootloader anyways, your phone seems fine. iy could just be the stock rom you flashed or kernel panics(i doubt). flash cyanogenmod and see if you still get the reboots. unlocking the bootloader doesnt have anything to do with a phone overheating and rebooting. besides, what is overheating? how hot does it get? ive gotten mine to 49C(120F) before

Well that's the thing, it really hasn't gotten that hot. I was just assuming it could be related as it was rebooting after sitting on the charger for a while or trying to download multiple apps from the Market. I was able to get as far as downloading ROM Manager and was part way through the CM6.1 download when the reboots from hell came back.
I used the Signed Passion FRG83 images to reflash.
I'm now attempting to format the SD card to see if it changes anything.

etacv said:
Well that's the thing, it really hasn't gotten that hot. I was just assuming it could be related as it was rebooting after sitting on the charger for a while or trying to download multiple apps from the Market. I was able to get as far as downloading ROM Manager and was part way through the CM6.1 download when the reboots from hell came back.
I used the Signed Passion FRG83 images to reflash.
I'm now attempting to format the SD card to see if it changes anything.
Click to expand...
Click to collapse
it sounds like youre stressing the phone(kernel). try to download 1 thing at a time for now. are you overclocked by chance?

I am not. The phone is bone stock at the moment.
Hm, it looks like i'm on FRG83 not 83D. The SD card is having some issues unmounting and i'm not receiving the OTA update to 83D

Yes - it is overheating!
My original phone did not have the problem. Every replacement phone I got from HTC crashes after 5 minutes or less on every application that made my original phone warm to the touch.
Applications that cause this:
RoboDefense
Tower Raiders
Speed Pi (run multiple times)
Curling
I am trying to get HTC to send me a 3rd replacement!

So as an update I formatted the SD card, and it seemed to have helped for a while.
I had the phone in the charger last night and was speaking on the phone for about 10-15 minutes until it started rebooting again. This time it was stuck on the X so i had to remove the battery.
Not sure what's going on...

So looking through the logcat's i've noticed these lines as failed:
E/Zygote ( 58): setreuid() failed. errno: 17
W/DevicePolicyManagerService( 78): failed parsing /data/system/device_policies.xml java.io.FileNotFoundException: /data/system/device_policies.xml (No such file or directory)
D/SntpClient( 78): request time failed: java.net.UnknownHostException: north-america.pool.ntp.org
I'm not sure if it means anything.
The firmware was downgraded to FRG33 and OTA updated to FRG83D
Will probably be sending this back and hoping the unlocked bootloader won't make it cost a fortune to repair...

[Q] Really messed up and need help bad

Hi guys I screwed my phone up by clicking on the wrong thing in Bonic safestrap. I have tried several times to use RSD to bring it back to stock and it fails on the system.img. I downloaded the flashme zip twice in case it was corrupt and it always fails. DESPERATE here is there any hope for me. Starting to really sweat it.
Thanks
UPDATE "Happy Dance" Well after about 1 1/2 hours pulling my hair out and aging about 10 years I am back in business. STUPID mistake on my part the version of RSDLite I was using was too old, finally found a youtube video that said I should be using v 5.5. Big Sigh of releife ......

[Q] Very frustrated

Okay, so I'm about ready to destroy my phone.
I'm on 902, and I keep getting an error when I try to let the phone update to 905. I'm pretty sure this is because I've deleted all of the Bloatware.
I've looked through all of the FXZ tutorials I can find, but to no avail. I'm running a Mac system, and every time I try to run pathsaver, nothing happens.
I hit 1-6 and I get: "bash: /Volumes/The: No such file or directory"
What does that mean? Can anyone please just give me a walk-through that an idiot can understand on getting back onto the upgrade path using Mac?
Please!

Best bet is to borrow a pc or go to a computer lab and fxz with RSD lite. I spent countless hours trying to do it with a Mac, but had to break out the old DELL with XP to finally do it.
pathsaver has a Mac version, but i couldn't for the life of me get it to work
Sent from my DROID BIONIC using Tapatalk 2

agree...
You have to install Moto windows drivers, install RSD 5.7 and Download the 902.zip. 20 minutes to flash and delete all files from your friends (borrowed) computer.
The link:
http://androidforums.com/bionic-all-things-root/480176-how-flash-5-9-902-rsdlite.html

It's crazy where I live in a world where I do not have access to a Windows computer. Times certainly have changed. I ended up getting a refurbished one from Big Red. I sold the refurb and bought a Galaxy Nexus. Thanks for all your help.

Can Somebody lend me a quick hand??

Im posting here because I am not sure this is phone specific issue, but if you guys could help me that would be great.
Long story short i screwed up my phone, cant recover with rsd so used fastboot...blah blah blah Its up and running except one thing.
WHen the phone boots I see the motorola Logo....but thats it, I hear the droid doing the weird machine startup,,,i plug the phone in to the computer and it recognizes it, i even called from another phone and it rings...
I just cant see anything it black, I also get haptic feedback on the buttons.
I fxz'd with the latest update from verizon...I boot into recovery and i see the little android man, i Islo see the white letters on bootloader, its just when the rom actually loads its a black screen?
If anybody could help i would appreciate it.
Phone is a bionic

Reinstall your android. Your os must hav corrupted. Flash it again.

i have re-installed over 20 times, i think maybe the phone is done??? i accidentally tried flashing a GB fxz before the JB one.....the phone s running but soon as the bootanimation starts for the phone i get nothing on the screen only sound.

SomebodyPleaseHelp said:
i have re-installed over 20 times, i think maybe the phone is done??? i accidentally tried flashing a GB fxz before the JB one.....the phone s running but soon as the bootanimation starts for the phone i get nothing on the screen only sound.
Click to expand...
Click to collapse
from my understanding once you go to JB there is no going back.. Were you getting any errors when you fxz? mine would get an error at step 5 and stop. their was a separate image file for that error which I used and it worked fine. It's on the page. I have bricked mine 3 or 4 times and it always came back to life. I really like this phone. wish it wasn't nearing the end of it's life for support. Times I thought mine was a gonner but it always came back. try redownloading the fxz file.