[Q] Razr M (XT907) Bricked - M Logo - Droid RAZR M Q&A, Help & Troubleshooting

I have a Motorola Droid Razr M (XT907) that upon last reboot decided to stop at the Motorola Logo and won't continue the boot process. I can get into Fastboot and Recovery, but so far, neither has been helpful. I have read several threads concerning similar issues, but have not found a solution yet. This phone has not been previously rooted or unlocked and to my recollection the latest OTA has been installed.
When in Fastboot, it says Device is locked. Status code 0.
I'm working on a Windows 7 PC. I have installed Motorola Device Manager and the Motorola USB drivers. When the phone is in Fastboot, it is recognized in my device manager as Mot Single ADB Interface. When I run Motorola Device Manager it replies:
There are no updates for your device at this time.
Current Version:
98.12.4.xt907.verizon.en.us
I have also installed RSD Lite version 6.1.5. When I run it, it shows my connected device, however all of the fields look so:
ESN: N/A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: N / A
DRM Version: N / A
I have not been able to find the correct FXZ image to repair the phone and fear it may well be lost. I'm only 12 days away from phone upgrade eligibility and it's cost prohibitive to upgrade early, so I'd like to repair the phone enough to use it for the next 12 days.
Any and all suggestions would be great.
Thanks

Go through this threadhttp://forum.xda-developers.com/showthread.php?t=2869432 thoroughly. It contains everything you need to know. In short, flash your phone to stock KitKat 4.4.2 the .10 build, not the .15 build, unlock your bootloader and then it's up to you whether you continue on stock or flash a custom ROM. Do check (http://forum.xda-developers.com/showthread.php?t=3042687) that you have the latest drivers and the latest version of RSD Lite installed and if you have trouble with flashing check to make sure you're using the correct cable...

Related

New VZW Trophy w/OS version 7.0.7389.0 not updating

Just unboxed a Verizon Trophy today. Activated on the Network successfully.
Phone is running the following Windows Phone Version
OS Version: 7.0.7389.0
Firmware Revision Number: 2305.06.10322.605
Hardware Revision Number: 003
Radio Hardware Version: 1.52.00.03.28_23.15w.05.06U
Bootloader version: 1.3.230506.23
Chip SOC version: 2.3.0.5.6
The phone is saying no updates found.
Zune software did not update on initial connection.
When trying to manually update via Zune Software 4.8 the following error appears.
"Can't check for updates right now. Please try again later.
We couldn't connect to the update service. Disconnect and reconnect your phone, then try installing the update again.
80072EE7"
This error has occurred on three separate computers including a fresh install.
While this device is brand new it's no longer under warranty.
Any Ideas?
Verizon, HTC, and Microsoft have no clue whats going on.
Screw that, you have two options.
SPL hack, custom rom. Read my guide here to find out how!
Benefits:
Full unlock, run stuff like Opera!
Internet sharing enabled!
Download the newest rom and flash it. You won't lose any data since you have non to lose. Go to footballs thread here and get "RUU_Spark_W_S_VERIZON_WWE_2.04.605.02_Radio_NV_0215_NV58008_RELEASE.exe".
Sorry I didn't catch this thread earlier, but I hope this helps. I'd just do a full unlock. :/ Having the shipping rom and the 1.03 bootloader (you should), you should be able to unlock very easily.
Sorry, double post... lost internet during first post. Please delete.

[Q] Motorola RAZR M XT905 HelpPlease!~!~!

o7. Has anyone out there used the Moto RAZR M XT905.. more specifically, has anyone successfully unlocked, rooted & flashed a custom ROM to replace JellyBean 4.1.2
My Question:
With a few different RAZRs and their different android versions out there, I'm lost as to the specific version of TWRP or CWM I must use, and the appropriate ROOT method.
Many Infos:
This is the Telstra/Aussie version (DROID XT907 is Verizon/US)
We're still stuck on JB 4.1.2
My RAZR M is the Developer Edition, so unlocking the bootloader was no problem, as unlock code was provided by Motorola.
I then rooted and installed TWRP recovery.. This was over a year ago and I cannot recall what I used to root, or what version of TWRP I had.
Phone worked great all last year, then I very stupidly used an app requiring ROOT access that was specifically for the XT907 US version.
I lost access to the soft keys & some of the UI (I think this is soft-brick?)
My next mistake was to reset to factory settings in the hope of fixing the issues.. which worked!! but has destroyed my WIFI & Bluetooth
Both WIFI & Bluetooth won't toggle on now and are not displaying MAC addresses.. At least I can still call & txt.
After many hours of reading (which I should have done FIRST!) I found a copy of the Telstra 4.1.2 JB Firmware for RAZR M XT905. Yay.
Flashed that with RSDLite.. but no joy.. both still just as broken.. Boo.
I think that some required files have gone AWOL.. wpa_supplicant could be gone (or I may just need to overwrite it with a working version)
This means I will need to flash a custom recovery & gain root access again.
So...
With a few different RAZRs and their different android versions out there, I'm lost as to the specific version of TWRP or CWM I must use, and the appropriate ROOT method.
Hopefully someone here has the same mobile, or some experience flashing/rooting Moto's ??
Cheers

unbricking hard brick - moto x style

hey guys
i just brick my phone (no idea how, flashed android 7 firmware) after flash my phone was working for like 2 hours, then i let himself update a security options. After update my phone went brick
As far i found :
- installed Qualcoom QDLOADER 9008 driver
- found QFIL programmer
i need to have programmer path (something related to JTAG) and build xmp path
Where i can find them? Or is it a other way to resscue my phone?
I feel your pain. My timeline:
- The phone was unlocked but still in Stock Nougat (7.0?). Got that from OTA in Brazil.
- I tried to update to LineageOS 7 via TWRP. After a full wipe (everything, system, data, card, cache etc) I installed the new ROM. Turned on, bootlooped forever.
- Searching around I found out that there was no modem in the Nougat roms and for some reason I needed to flash a Marshmallow modem for my region to make that work (I think there is no Nougat modems around or something).
- I found a LA_DS modem for 6.0, flashed that using TWRP, still bootloop. Tried other roms using TWRP, still bootloop.
- I then downloaded a full stock old 6.0 firmware to go back to stock but the phone wouldn't accept some files ("preflash validation failed").
- Searched around and found out that you can't downgrade a bootloader from Moto.
- Using fastboot, I flashed the files the phone was willing to accept and it finally booted the 6.0 Marshmallow stock rom, but with no networking (radio/modem/baseband/IMEI missing).
- Flashed the 6.0 modem for my region again and everything worked. Connected on WiFi, dual sim cards detected etc.
- I started to install every update the phone showed to try to update it back to latest MM version.
- The three first updates went ok, the fourth turned off the phone to never turn on again.
Looks like there is no way out of this. My phone is pretty old and MotoCare in Brazil will charge a lung and a half for repair.
dsnunes said:
I feel your pain. My timeline:
- The phone was unlocked but still in Stock Nougat (7.0?). Got that from OTA in Brazil.
- I tried to update to LineageOS 7 via TWRP. After a full wipe (everything, system, data, card, cache etc) I installed the new ROM. Turned on, bootlooped forever.
- Searching around I found out that there was no modem in the Nougat roms and for some reason I needed to flash a Marshmallow modem for my region to make that work (I think there is no Nougat modems around or something).
- I found a LA_DS modem for 6.0, flashed that using TWRP, still bootloop. Tried other roms using TWRP, still bootloop.
- I then downloaded a full stock old 6.0 firmware to go back to stock but the phone wouldn't accept some files ("preflash validation failed").
- Searched around and found out that you can't downgrade a bootloader from Moto.
- Using fastboot, I flashed the files the phone was willing to accept and it finally booted the 6.0 Marshmallow stock rom, but with no networking (radio/modem/baseband/IMEI missing).
- Flashed the 6.0 modem for my region again and everything worked. Connected on WiFi, dual sim cards detected etc.
- I started to install every update the phone showed to try to update it back to latest MM version.
- The three first updates went ok, the fourth turned off the phone to never turn on again.
Looks like there is no way out of this. My phone is pretty old and MotoCare in Brazil will charge a lung and a half for repair.
Click to expand...
Click to collapse
Pretty similar situation on my part. I downgraded back to 6.0 and when it tried to take the December update I ended up with the same thing as you. I ended up getting a replacement from Moto for under 100 dollars which was worth it rather than trying to find a solution that doesn't exist.

ZC550KL Woes - Unable to Root - Z010D - Fastboot Not Working

Hello Everyone,
I am having lots of issues with rooting my ZC550KL. Used both the Asus Utility Unlocking tool (The APK does not install even though the unknown sources option has been enabled) and the Fastboot hangs while looking for a connected device. I have had used the Google USB Driver on Windows and the Phone is recognised, also tried this on Linux and still no luck..
Can someone help me with any other fresh Ideas on how I can get this sorted? I have had used the latest Update from Asus and updated to marshmallow. Also not sure if I can downgrade back to 5.0.2 which was the original Firmware this phone was shipped with.
Really appreciate any feedback.
After a few hours of digging, I've ended up flashing the stock Lollipop Image and now I am finally rooted..

Really Tricky Problem

Hello people!
I've been doing installation of custom ROM and any kind of configuration for a while now. But I have now in my hands a tough problem. My dad bought athene XT1640-DS (Moto G4 Plus), just like the one of mine own, but mine doesn't have the '-DS'.
But the device is stuck at Stock Android 6.0.1 and I can't update it.
The USB seems have some problem because any PC in my house recognize the 6.0.1 phone, but works fine with my up to date 8.1.0 athene, but it's charging only, and the turbo charging isn't working. the fingerprint isn't working neither.
It looks like the bootloader was unlooked, because everytime it's turned on shows the 'bootloarder unlock message'. But I was unable to root it, I tried all the one click root apps, but none of them worked.
It doesn't have any custom recovery, so I tried to update with the stock recovery but every OTA Blur Version rom that I found for athene shows a error telling that my ROM version isn't compatible with the updates (the ROM version code of this phone is MPJ24.139-23.1/ 1 user).
Anyone have any hints of what can I do to update this device?
Device XT-1640-DS
Android: 6.0.1
M8952_7000.04.03.32R
ATHENE_BRAZIL_DSDS_CUST
Kernel: 3.10.84-GCF01273
[email protected] #1
MPJ23.139-23.1
From what I know one click methods doesn't work with this device. You need a proper kernel for android 6.0 like elementalx 1.0. And supersu or magisk zip flashed through a recovery like TWRP.
Is there a way to update de kernel, or do that other things without PC and root?
Or a way to use adb without USB connection?
Have you tried fastboot flash methods like in this thread?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
So.. the big issue is that this device isn't connecting to the PC, it's charges, but neither the PC not the Android show any signs that their are connected. I can't use adb from the PC because I couldn't make the computer recognize the phone.
can you at least transfer files in mtp mode with the usb cable? because looks like the micro usb port is messed up.
If you are on warranty period you should go for it
I can't use the mtp neither. The only thing I can do is charge. And I'm out of warranty :/

Categories

Resources