XT910/GSM bricked? Tried RSD Lite - Motorola Droid RAZR

I decided to flash a factory image since the GPS was not working anymore with whatever ROM I tried, plus random problems. The phone was previously set up with CM10.1 and BMM.
Installed RSD Lite, Moto drivers, downloaded several stock ROMs.
From the factory recovery mode I cannot flash any of those zip files so I proceed with RSD lite. I flashed "9.8.2O-124_SPUEM-14_S7_USASPDRICS01O2UKE1007.0R_USASPDRJBO2GB_P013_A012_p2b_S1FF_fb.xml.zip" which is a retail UK JB image. The phone shows the very first boot screen (red logo) and then the screen goes blank. The computer still sees an MTP device, though only in device manager.
I've tried installing other images but they are an older type (ICS I guess, 01.6.7.2-180&01.6.5.1-167) and RSD shows an error while trying to flash the first file from the archive.
Oh, I still have the "Customer error: contact dealer" on the first boot screen, I think this was from a ICS to JB upgrade with CID deletion(?).
I've already flashed twice using RSD, deleted cache+data, rebooted and left the phone to start up for ten of minutes, don't know what to do. RSD lite reports that flashing was ok.

been there
brainwash123 said:
I decided to flash a factory image since the GPS was not working anymore with whatever ROM I tried, plus random problems. The phone was previously set up with CM10.1 and BMM.
Installed RSD Lite, Moto drivers, downloaded several stock ROMs.
From the factory recovery mode I cannot flash any of those zip files so I proceed with RSD lite. I flashed "9.8.2O-124_SPUEM-14_S7_USASPDRICS01O2UKE1007.0R_USASPDRJBO2GB_P013_A012_p2b_S1FF_fb.xml.zip" which is a retail UK JB image. The phone shows the very first boot screen (red logo) and then the screen goes blank. The computer still sees an MTP device, though only in device manager.
I've tried installing other images but they are an older type (ICS I guess, 01.6.7.2-180&01.6.5.1-167) and RSD shows an error while trying to flash the first file from the archive.
Oh, I still have the "Customer error: contact dealer" on the first boot screen, I think this was from a ICS to JB upgrade with CID deletion(?).
I've already flashed twice using RSD, deleted cache+data, rebooted and left the phone to start up for ten of minutes, don't know what to do. RSD lite reports that flashing was ok.
Click to expand...
Click to collapse
Did you erase CID?
if you did yo need to boot in a different way

U did a factory reset in stock recovery? U cannot flash a ics image after flashing jb via rsd. Try again jb EU image than go to stock recovery and perform the wipes
Tapped from my RazR

Got it "fixed", finally. I had to go back into the stock boot/recovery menu and choose "BP Tools", last option from the menu and then it booted normally.
I still have to do this after each reboot because it boots to the black screen: hold the three buttons together until it flashes (which means a hard reboot), let go of the power button, press power button again while the other two are still pressed.
On the plus side the GPS started working again after factory reflash which it was kind of expected since the same chip is providing also WiFi and bluetooth which were running fine.
I have a root question: the device was rooted with the virtual machine procedure but after a factory reset the root was lost. I had saved it using Voodoo RootKeeper and the app shows: superuser installed, device rooted, /system supports root protection, protected su available. The "root permission granted" checkbox is disabled though and no application is able to retrieve the root. The su binary is in both /bin and /xbin so I don't understand how it can not function.
Edit: ok, got it, the su binary has -rwsr-sr-x and the owner is root so random users cannot execute it. I also cannot change the permissions so I probably have to root again and figure out a way to keep the root after a factory reset. It makes sense to install BMM since it can take care of permissions.

Related

[Q] Memory and Android Recovery issues.

Hello!
I own an Atrix which is rooted on stock froyo 2.2.2 from Brazilian carrier Claro.
I tried to install CWM with Rom Manager but after my device rebooted I got the Failed to Boot 2 error message, so I flashed to bootloader with IHOP_bell.sbf (didn't unlock it) and it booted again but now the phone only recognizes 373mb of ram and I cant enter Android Recovery, it shows the Failed to Boot 2 error message again.
Any help would be greatly appreciated!
Thanks for your time!
Fixed.
If you have a similar issue after trying to install CWM with Rom Manager:
(YOU WILL LOSE ALL YOUR DATA)
1. Acquire a full sbf of the rom you have installed.
2. Download RSDLite 5.5.
4. Open RSDLite 5.5, click "..." and select your sbf.
5. With a full charge, plug your phone in and reboot your phone holding volume up.
6. Wait for RSDLite to recognize it.
7. Click start and wait.
Everything should be fine now
At this point is good to mention CWM is not to blame for this AFAIK since I can install it from the APK just fine. Rom Manager was the one who screwed up big time.

bootloop, fastboot file thru RSD returns error "cdt.bin"

I have a moto razr xt910 on rogers, unlocked, originally booted with the fido logo.. I've been using bootmenu manager to dual boot and try roms (mainly cm10) on 2nd system. I tried unsuccessfully to flash Wizzed bean rom in 1st sytem cause I didnt wanna lose my setup in 2nd system whcih was pretty good. I rebooted after it failed instead of staying in the bootmenu manager bootmenu and havent been able to get it back, just bootlooped for a while and tried to flash from recovery. Failing that, I got RSD lite and the rogers fastboot ICS file, but it returned an error in 6/21 "cdt.bin" phone returned "fail" or "failed". Online it seems that that using the motorola factory cable can often solve this problem, but unsurprisingly the one I tried to make didn't work. Do you think you could help me?
Thanks,
Me

[Q] Razr Stuck at Second System Unrooted - HELP NEEDED

Hi everyone,
First Post, checked and no similar problem is found so far, please direct me if there are any
Here is the situation :
I rooted my Razr at 4.0.4 OTA, installed Bootmenu and installed Eclipse 1.5 as my second system.
Then I set that boot will automatically reboot into my second system.
Couple of days ago, my phone automatically updated my SuperSU app, and since then, I lost root and cannot use boot menu manager anymore.
I tried to reboot and entered stock recovery, which is the only recovery I am able to enter now, then wiped the phone, hoping to factory reset it, and nothing happened, my phone still boot into Eclipse instead of Stock.
Then I tried to unroot (using the option provided in SuperSU), then nothing happened.
Then I tried to re-rooting eclipse using the root tool from the Eternity Project (the one key root tool), and despite it does install SuperSU on Eclipse, I don't have root (saying that I do not have root binary) and cannot use Boot Menu Manager.
In short, I am trapped in my second system and I do not know how to gain root and access to my stock system again
I have a GSM Razr that is upgraded to ICS OTA, should be the AsiaRetaileng.03, I can't remember it exactly since I cannot boot into the stock system now.
Please help!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Solved, downloaded a fastboot zip that is compatible with RSD Lite in the website of Eternity Project, flashed it under stock Fastboot mode, now it's good as new again.
Just one thing, I can only find a European Version image, whereas my phone is a Hong Kong Version (Asia Retail), now my phone says it's EuroRetail, but everything else worked just fine.
Does anyone have the 4.0.4 Asia Retail image?
Much thanks.

Bootloops into clockworkmod recovery over and over

I rolled back from MMROM to NOTTACHTRIX Today and now my phone is stuck in CWM. (Cold Boot Android by selecting Boot Anroid NO BP option doesnt work either).
I have flashed MROM, Neutrino, NOTTACHTRIX, CM10.120120720 and all ended up into clockwork mod recovery. Kindly tell me an alternative -.- I am stuck with this from past 12 hours and no luck.
Update
I have managed to boot into android using Cold Boot without BP (i-e GSM radio will be disabled). I am recharging my phone battery and experimenting.
Before flashing NOTTACHTRIX, my phone had SKT version of 2.3.5 v167. I directly went for unlocking bootloader blabla recovery to get the NOTTACHTRIX working (thats like 4 months ago when I bought this phone)
So I tried going back to a version near 2.3.5 or higher. So going for 141 AT&T version didnt seem a problem for me except the .91 version bricks the device if u downgrade from 2.3.5 or above.
RSD Lite gave me 0x703e error and I couldn't flash the stop sbf.
Second resort I did was flashing 2.3.5 and 2.3.6 fruitcakes and still ended up in recovery.
I can only coldboot into android with Neutrino ROM other roms give me rebootloop when I choose coldboot.
I am suspecting a corrupted system or some kind of corrupt script in boot which keeps me in a loop into recovery. I did try adb script for ASUS TF101 to exit recovery bootloop but to no luck.
Also, I tried exitrecovery.zip flashable and still couldnt get into regular android OS.
This device is a headache for me now -.- and seemingly no one bothers to reply or to help me solve this issue >_>
Thanks for reading atleast
Update 3
Fixed it myself.
I downloaded fastboot, 2.3.6 fruitcake (system and boot), the older clockwork mod recovery, the one comes with Bootloader unlocking not some 5.0 version.
All I did was erased RECOVERY from fastboot, then boot and system. Frasled boot and system. Rooted with the bootloader unlocker package. Installed the old recovery and flashed NOTTACHTRIX.
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
mynonama said:
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
Click to expand...
Click to collapse
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Please help...recovery bootloop
dark_prince said:
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Click to expand...
Click to collapse
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
noobButStudying said:
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
Click to expand...
Click to collapse
did you try the updated and usually standardly used CWM, 5.0.2.6?
palmbeach05 said:
did you try the updated and usually standardly used CWM, 5.0.2.6?
Click to expand...
Click to collapse
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
noobButStudying said:
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
Click to expand...
Click to collapse
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Resolved!
palmbeach05 said:
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Click to expand...
Click to collapse
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
noobButStudying said:
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
Click to expand...
Click to collapse
The RSD issue and not being able to do anything. you are the 4rd person that i've dealt with to have that issue. we had a guy on here a few wks ago that me and andresrivas were trying to help. he wasn't getting the bootloop you were getting, but he had a very similar issue and had the RSD issue. like a wk later, i ended up having the RSD issue as well. Andresrivas also has experienced this issue. All i know is flashing that pudding is what saved us as well.
Idk what ROM you're going to put on there, but i would definitely keep that spare around. if your digitizer dies, you have a backup digitizer

[Q] 2.3.5 boot loop and hosed recovery

Current status: BOOT LOOP, NO WORKING RECOVERY
I'm working on a friend's Photon, trying to get it back to stock. It got the 2.3.5 OTA update ages ago and therefore has a locked bootloader.
I have tried many things. Do not tell me to search the forum; I have spent many hours doing exactly that.
The phone starts booting, shows the U.S. Cellular animation from the Electrify due to the performing the first of the six tasks outlined in several places, including here: http://forum.xda-developers.com/showpost.php?p=30654255&postcount=5
It then reboots before getting to a home screen. The next logical step would be to boot to recovery and do a factory reset. However, starting recovery (hold volume down, down until recovery, up) results in the yellow exclamation point sign and android icon and then it freezes. I suspect, but am not sure, that the phone had CWM on it at some point. I'm not sure if the Electrify sbf also re-installs stock recovery?
I can get into fastboot, but the two recovery images I attempt to flash result in "failed to process command flash:recovery error(0x180002)". I have also flashed 2.3.5_45.4.13ota_unbrick.sbf in an attempted to get a working recovery, but that just goes back to the boot loop at the end of flashing.
I can't continue with the 6-step unbrick process because the phone won't boot up all of the way to allow me to root it and install the bootstrap apk. I can't wipe the phone because recovery doesn't work.
What I need:
a fastboot-able stock recovery image file, to ensure that I have the correct recovery. There were links to this at one time, but they are all either rotted or the OP flounced and nuked his posts containing them.
Apparently the yellow exclamation point sign means that stock recovery is installed. However, it never presents a menu or any text, just the image, so something else is wrong. Of course, there are no useful error messages, either, just the image.
No amount of RSDLite appears to be helping. Is there a way to force a factory reset from fastboot or RSDlite instead?
To answer my own question:
fastboot erase userdata does a factory reset.
If anybody else sees this while trying to do the 6-step 2.3.5 stock reinstall, if you get hosed after step 1, that's how you fix it.

Categories

Resources