When attempting to SBF to upgrade to Cyanogen 10 A2 something went wrong.
Ive tried several versions of RSD Lite and several SBF Files.
Currently I am using RSD Lite 5.7 with the 2.3.4 SBF File
This is the error message on the phone
Download code Started...
rsd mode...
Partition Tables did not match: Backup PDS and repartion memory...
ERR: hardware/tegra/prebuild/make/../../core/system/rdl/rdl_main .c: 492 StartPartionConfigurion( 25 ): 3
When booting up i get the message Failed to boot 4 -
The phone then automaticlly starts up RSD mode
When holding the volume down or up key while powering on nothing happens... no fast boot and no recovery.
So any advise would be much appreciated. Ive found a few other posts that people have have similar issues but none exactly the same.
Im interested in any advice on which RSD lite version.. which SBF file... and anything else.
Until I get some help my next thing will be to try to SBF using linux.
And obviously Id like some help with repartioning the internal phone memory, it does the same thing whether the phone has the sd card in it or not.
This section is not made for questions just so you know. I'm just going to link you here:
http://forum.xda-developers.com/showthread.php?t=1317707
Everything you need is in that thread.
try this rsd lite and if that doesnt work ill send my sbf i use too. http://d-h.st/n6d
Thread Closed, only post a question once, i will keep your other thread opene HERE.
Thanks
The-Hulk
Related
Hi everybody... Today i tried to flash my german atrix, using sbf_flash and the OLYEM_U4_2.1.1 ROM...
The problem started in Ubuntu (11.04):
I can start the flash process, but after phone-reboot sbf_flash tells me that it can not access the usb-port. (does not matter if as user, sudo or as real root!)
OSX starts flashing until it breaks at the 6th or 7th upload...
Vista (the only Windows we have here) does not even recognize the phone, so RSD Lite cannot flash it...
At the moment i have a totally unusable phone with "Failed to boot 4. Starting RSD mode"...
Tryed nearly every howto that is given, but i cant even start fastboot-mode so thos howtos are completely unusable for me...
were you trying to downgrade when you first flashed the sbf in linux? because then you are hard bricked. :'( check stickies in atrix development
So before you comment saying "should have searched first" I have tried every way suggested by XDA, Cyanogenmod devs, motorola and various developing websites. It has not worked once yet.
On 2.3.6 Bell Atrix
Rooted with superuser
RSD doesn't recognize my phone, but it did once upon a time (but wouldn't get the image on then either)
Fasboot commands always come up with errors or not implemented unlock notifications.
Using RSD Lite 5.7
newest moto drivers (as far as I know)
Have all my SDK tools
Have fastboot and the adb...dll files
The two computers I have tried on are a brand new HP running Windows 8 64bit and an older HP running Windows 7 64bit
I have been linked to so many threads that never worked.
Any steps, advice, link to new drivers/programs files ANYTHING would be greatly appreciated.
And yes I have the typical Wifi/BT issues as well as a messed up digitizer, but it isn't bad enough to replace yet.
there's a lot of things which can be done... I found this old link which may help? http://www.droidforums.net/forum/droid-hacks/85578-win-7-rsdlite-detecting-probelms-resolved.html
there's also this http://www.droidforums.net/forum/te...33-rsd-lite-does-not-recognize-my-moto-3.html . One of the main points seems to be making sure that you are running RSD as administrator by right clicking on RSD logo and selecting 'run as admin'
Actually great! Thanks!
Will try then post results.
Hoping one of you can give me an idea of what to try next . . . here's the chronology in order with some background:
-US Cellular Motorola Electrify (yep I know that it's not quite a photon, but I wanted to post of XDA . . .)
-Factory original. Wet about a year ago, worked flawless after dryout for the full year.
-Was a little slow one day on operations, rebooted, and got the Moto Screen and the "Starting RSD Protocol Support" message. UP/DOWN volume keys when restarting, etc were all nada, no response.
-Read for a couple days, dowloaded RSD Lite 5.6, updated Motorola drivers. RSD Lite recognized the phone, etc Tried flashing the phone to 2.3.4. I now get the "Failed to Boot 1" - "Starting Fastboot Protocol Support" error message.
-When connected to the computer RSD Lite knows the phone is there, but lists device properties as:
ESN:
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: N / A
DRM Version: N / A
It shows the model as FASTBOOT, and when trying to flash to 2.3.5 gives the fail message - "Failed Flashing Process. Unable to retrieve interface handle."
What do I try next?
Random
PS - I'm a noob. A semi-intelligent one, but a noob just the same! Thanks in advance.
randsom2708 said:
Hoping one of you can give me an idea of what to try next . . . here's the chronology in order with some background:
-US Cellular Motorola Electrify (yep I know that it's not quite a photon, but I wanted to post of XDA . . .)
-Factory original. Wet about a year ago, worked flawless after dryout for the full year.
-Was a little slow one day on operations, rebooted, and got the Moto Screen and the "Starting RSD Protocol Support" message. UP/DOWN volume keys when restarting, etc were all nada, no response.
-Read for a couple days, dowloaded RSD Lite 5.6, updated Motorola drivers. RSD Lite recognized the phone, etc Tried flashing the phone to 2.3.4. I now get the "Failed to Boot 1" - "Starting Fastboot Protocol Support" error message.
-When connected to the computer RSD Lite knows the phone is there, but lists device properties as:
ESN:
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: N / A
DRM Version: N / A
It shows the model as FASTBOOT, and when trying to flash to 2.3.5 gives the fail message - "Failed Flashing Process. Unable to retrieve interface handle."
What do I try next?
Random
PS - I'm a noob. A semi-intelligent one, but a noob just the same! Thanks in advance.
Click to expand...
Click to collapse
bro now im on that stage.still your photon 4g didnt working? or if it ok now? please help me also
uchithisanka said:
bro now im on that stage.still your photon 4g didnt working? or if it ok now? please help me also
Click to expand...
Click to collapse
ok now my phone worked perfectly and unlocked bootloader.heyaaa im happy now
How did you pull it off? i am stuck in a similar issue with my Sprint Photon 4g
Hi, I have bricked my xoom whilst trying to upgrade (stuck on M logo) I can get to RSD protocol support 3 also Fastboot protocol support, also Android recovery. After hours of reading it seems that I may be able to fix it if I use an SBF file, I've found 1 or 2 but they won't download. Does anyone know where I can get a working one or any other way of fixing it? Thanks in desperation!
Hey bros! sorry for posting it in wrong area but I the vbulletin message denied me to post in razr section*, well ima discuss my prob here ... I rooted my xt910 by batch method , everything went fine reboot was working etc, after that I tried to install CWM recovery from a apk file and it resulted in brick (encryption unsuccessful) due to that reason I tried to wipe cache from recovery and tried to flash boot files from cmd (through pc) this resulted in flash failure boot Loop! i got exhausted and mad! The thing was Rsd wasn't recognizing my razr even the drivers were fine (as cmd was working fine too) but after that I got a new data cable and hola! The rsd worked on windows 8 x64 but fsd gave a error while flashing firmware 6/19"cmt.bin"phone result fail ( or something like that ! Can anyone please help me fix this ****! tried droid razr utility (obviously it was for droid razr but I had no chance unbrinking so I just went ahead and tried my luck out, this resulted in flash failure again and the recovery + bp tools fail! The thing is I need razr utility! or rsd cmt.bin error fix or another software to stock back my Motorola! razr..any help will greatly be appriciate ( nvm 90% of YouTube/XDA/ droid were broken and I couldn't use the exact files to flash which may have resulted in brick, I can charge battery for your info tho