Related
I am putting this together because, after three weeks of study and four days of full-time work I have finally pulled together the information needed to do this. I will also offer a lead on how to make your phone a Development phone. Sorry, no pictures or vids for the kids, just solid useful information.
You will start with an XT910 or XT912 which is locked to a carrier somewhere in the world. To unlock you must buy an unlock code from one of the sellers on eBay. This will cost from 49 cents to 5 dollars, depending on your phone. I assumed that all the sellers could get all the codes, so I bought the cheapest one and sent him my IMEI. He responded that he does not do Motorola and refunded my 49 cents. So I found a seller who does the XT910, and bought his cheapest auction (for an Atria unlock code). He responded that I had bought the wrong auction as I have an XT910. So I ended up having to buy his XT910 unlock auction and got the code. Now the phone will work with any GSM carrier in the world.
Next is the firmware. I knew the phone is running Gingerbread because in Settings|AboutPhone it said the Android version is 2.3.6. I wanted to upgrade to Ice Cream Sandwich (4.0.4) or higher, and to the MIUI ROM which I've used happily for a year. I went through the (scattered) RSD insctructions to flash ICS, but it always failed on the first file. I finally discovered that the RSD method does not work with many phones at v2.3.6, so I went to an alternative method developed by kholk, which I'll describe here. This method will work when others fail.
The first thing to know is that I'm a Linux type, but kholk also offers a Windows method which I have not tested. His Linux script has a few bugs, which I have corrected in the script attached hereto. Also his Linux fastboot binary is an older version which can not handle the larger image sizes we have now, so I have attached hereto a newer one which the source code was recently leaked from Motorola;
The next thing to know is that when posts mention "Fastboot files" they mean the ROM image files which are divided so they can be installed with the fastboot executable. OTA files are not the same, nor are they desirable. I gather that an OTA file is installed -after- the fastboot files, and provide an incremental upgrade.
Stock and ICS fastboot image files for our phone are here:
http://sbf.droid-developers.org/umts_spyder/list.php
I am in Seattle, WA, and I bought my phone on eBay locked to Rogers Canada. So I and my phone are in the North American region. My stock Rogers is 'Rogers Canada' Gingerbread v2.3.6:
Rogers_XT910_SignedLATAM_167-SLC-M33.1_P042_A014_CFC_1FF_fastboot.xml.zip
http://sbf.droid-developers.org/umt...-SLC-M33.1_P042_A014_CFC_1FF_fastboot.xml.zip
My Rogers ICS is 'Unknown Carrier' Ice Cream Sandwich v4.0.4:
6.7.2-180_SLC-35_R02_SIGNLATAM_SPYDERICSROGERS_P012_A012_HWp2b_CFC_fastboot.xml.zip
http://sbf.droid-developers.org/umt...CSROGERS_P012_A012_HWp2b_CFC_fastboot.xml.zip
North American users, use these. If you're in Europe you want the Central Europe image, ninth from the bottom, for ICS.
It's important to understand that the software you have in the phone at the moment, is "signed" for your specific region of the world. So you can not install a European image to a Canadian phone -- it will fail with "Preflash validation failure". The individual files you unzip from the image zip file will be transferred to their specific locations in the phone, -after- signatures are checked, to make sure you have files for the correct region.
So, choose your image file from the above list, unzip the image file, and put the fastboot executable and script in that resulting directory. I have modified the attached script to work for the Rogers images, basically by adding a couple files which were missing in the original script.
Side Bar: In the file list above, you will also find Development images, and if the fastboot executable could be rigged to ignore signatures, you could install the Dev image and voila, have yourself a development phone! The fastboot source code is available, so maybe some talented coder could make that (dangerous) change. This is dangerous because a n00b could flash a Euro image on his Canadian phone and it wouldn't work. (This error is easily reversable by flashing the right image) Comment by Vatazhka: The signature check is implemented in the bootloader. Unauthorized image gives preflash validation error and causes the bootloader to stop booting with an appropriate message. Moreover, the bootloader can't be unlocked as it lacks support for appropriate fastboot commands. The only way to get around these restrictions is to get a Motorola-signed version of a bootloader which doesn't implement checks, which luckily happened to Atrix guys (Clueless Motorola employees put it into a regular SBF, which was subsequently leaked.).
- Make sure your phone is --fully charged-- or else it could run out of battery and leave you with an expensive brick. Comment by Vatazhka: There are $6 cables to repair bricked devices with no juice left on eBay. Been there, done that It's the standard USB data cable with two pins shorted and ideally should also include a resistor to bring voltage from 5 V supplied by USB down to 3.8 V as supplied by the battery.
- Put the phone in fastboot mode by turning off, then holding Vol+- and power on. Select Fastboot and Vol+.
- Connect the -original- USB cable (some USB cables do not have data lines, only power, and you must have data lines for this) and connect to
your computer. On the phone Fastboot screen it should say "Connected" at the bottom.
- On the Linux computer in a Terminal window, cd to the image directory and # ./FlashLNX.sh It should flash away with no errors. The phone will
reboot and you'll get the Android with rotating polyhedral heart; it will reboot a couple more times and you have ICS!
- Root the phone.
- If you have an XT910, for Recovery you want BootMenu Manager, and if an XT912 you want SafeStrap. Install from the Market. You MUST NOT jump the gun and try to install BMM or SS to Gingerbread. It will brick you. Get up to ICS, then lay down your recovery. Comment by Vatazhka: Not true. SS2 and SS3 can be installed to both XT910 and XT912 (just be sure to install the correct SS2 variant). Developer of BMM actually owns an XT909, which is similar to XT912, and uses BMM on it. Simply choose the one which works with a given firmware (Hopefully this will be solved soon, so you could install whichever suits you, not the firmware.). One caveat: If you intend to try or install MIUI, it WILL NOT WORK with SafeStrap. You need BMM (which includes CWM) for MIUI.
- Now flash whatever image you want.
http://forum.xda-developers.com/showthread.php?t=1792955
I like MIUI:
http://forum.xda-developers.com/showthread.php?t=1756659
- If you ever want to go back to stock, just use the above process and flash GB 2.3.6.
Comment by Vatazhka: This is usually not possible. Most ICS updates bump some of the partition version counters which are stored in the "partition table", which doesn't allow you to go back. You can forget about resetting it - there is a digital signature (eFuse as well?) on guard again. You can only flash partition images with version number which is not lower than embedded in the "partition table".
I'm also not sure about this fastboot update stuff, but I may have used different fastboot variants which haven't had implemented this.
- If you install MIUI directly to the first slot by rebooting to Custom Recovery and installing zip, you will lose Custom Recovery when done so it needs to be reinstalled. The newer MIUIs do not come with GApps (this Play) so you have to get them here:
http://www.miuiandroid.com/community/forums/miui-weekly-rom-releases.103/
... and get BMM here:
http://forum.xda-developers.com/showthread.php?t=1720351
Since I don't have phone service yet I downloaded these to my PeeCee, put them on a microSD card and popped them into the phone. Install BMM with File Manager, and use it to reboot to Custom Recovery to install GApps. Then I used Titanium Backup to remove all G**gle apps except for Play, Framework, and one or two others. (I don't trust the Greatest Data Mining Operation In The History Of The World) Speaking of which, I always install DroidWall and only allow the minimum apps to access The Internets.
Then I used BMM to install CM10 JB to the second slot, just for fun. So now I have dual-boot! MIUI and CM10. Either one can be set to default. Caution though, for the zip you will install to the second slot you must convert it, as per the link above. The resulting file will begin with BM, and -that- is the one you will install. At the same time you can add GApps to be installed right after the ROM. You can -name- your two bootable OS' like this: BMM|BootMenuSettings then tap the very name and a cursor will come up. Delete and rename; Mine are MIUI 2.10.19 ICS and CM10 16.56.44 JB.
MIUI is already rooted, always.
One pleasant surprise in all this is that the new ICS MIUI Backup app does recognize old GB MIUI Backup savesets. I had to install Android Terminal and cp -r them over by hand, but it did restore all my old logs, SMS, apps, etc, thankfully.. I notice that the new MIUI Backup offers Encryption! Well, this really means that you are enabling backups to their "Cloud". In Red China. Where they can pore over your contacts, texts, logs, calls, and friends at their leisure. Encryption? Pshaw. ('shared key') Velly ingenirous.
Recommended apps: DroidWall, AdFree, Snowstorm, RadarNOW!
Some additional tips:
To reboot the phone and put it in FASTBOOT mode.
# adb reboot bootloader
To reboot the phone and put it in RECOVERY mode. Still need to push Vol up + Vol down to use the stock recovery.
# adb reboot recovery
For normal reboot
# adb reboot
For OTA updates (normally not needed), try
# fastboot update ota_update.zip
If low battery and not flashed:
1. Connect your phone using ORIGINAL USB cable to to ORIGINAL wall charger
2. Press and hold both Vol+ and Vol- buttons at the same time and then press and hold Power button until bootloader menu appears with Normal boot already highlighted
3. Use Vol- to highlight BP Tools and press Vol+ to select it
4. Screen with red M will appear followed by a screen with the battery and number undeneath showing how much charge your battery has now which means phone is now in the battery charge only mode
5. Wait for a battery to charge which should take over 3 hours
CAUTION: This method will FAIL if you have not completely flashed the system image. When your battery gets down to about 1/3, fastboot will refuse to flash images and you'll be screwed. There is no way to charge it unless it's booted. If you get in this predicament like I was, put your phone on a hot item, like a laptop power brick, and pray it recovers the battery enough to flash at least system and boot images. Flash them manually (copying lines in the script) if you have to.
Much gratitude to kholk, eval-, and to Jack'O who got me through this.
Well done dude.
Sent from my XT910 using xda premium
Thanks for your help and support Jack'O.
This thread already has 248 views in its first hour of life, LOL.
Wow, that's one comprehensive guide. Just a few corrections:
Side Bar: In the file list above, you will also find Development images, and if the fastboot executable could be rigged to ignore signatures, you could install the Dev image and voila, have yourself a development phone! The fastboot source code is available, so maybe some talented coder could make that (dangerous) change. This is dangerous because a n00b could flash a Euro image on his Canadian phone and it wouldn't work. (This error is easily reversable by flashing the right image)
Click to expand...
Click to collapse
The signature check is implemented in the bootloader. Unauthorized image gives preflash validation error and causes the bootloader to stop booting with an appropriate message. Moreover, the bootloader can't be unlocked as it lacks support for appropriate fastboot commands. The only way to get around these restrictions is to get a Motorola-signed version of a bootloader which doesn't implement checks, which luckily happened to Atrix guys (Clueless Motorola employees put it into a regular SBF, which was subsequently leaked.).
- Make sure your phone is --fully charged-- or else it could run out of battery and leave you with an expensive brick.
Click to expand...
Click to collapse
There are $6 cables to repair bricked devices with no juice left on eBay. Been there, done that It's the standard USB data cable with two pins shorted and ideally should also include a resistor to bring voltage from 5 V supplied by USB down to 3.8 V as supplied by the battery.
- If you have an XT910, for Recovery you want BootMenu Manager, and if an XT912 you want SafeStrap. Install from the Market. You MUST NOT jump the gun and try to install BMM or SS to Gingerbread. It will brick you. Get up to ICS, then lay down your recovery.
Click to expand...
Click to collapse
Not true. SS2 and SS3 can be installed to both XT910 and XT912 (just be sure to install the correct SS2 variant). Developer of BMM actually owns an XT909, which is similar to XT912, and uses BMM on it. Simply choose the one which works with a given firmware (Hopefully this will be solved soon, so you could install whichever suits you, not the firmware.).
- If you ever want to go back to stock, just use the above process and flash GB 2.3.6.
Click to expand...
Click to collapse
This is usually not possible. Most ICS updates bump some of the partition version counters which are stored in the "partition table", which doesn't allow you to go back. You can forget about resetting it - there is a digital signature (eFuse as well?) on guard again. You can only flash partition images with version number which is not lower than embedded in the "partition table".
I'm also not sure about this fastboot update stuff, but I may have used different fastboot variants which haven't had implemented this.
Sent from my XT910
Thanks Vatazhka, I've added your remarks.
So what carrier are you going to use it with? Prepaid of some sort?
Sent from my XT912 using xda app-developers app
N, TMobile USA. It was locked to Rogers Canada but I unlocked it. It's working great. Been with TMo for seven years, and this time I asked them for a credit to buy the phone. (Last contract renewal I got $100 for the Nexus One) They wouldn't give me cash, but put me on a new "Value" plan with unlimited everything and $25 less than I've been paying, for $64/mo. Saving $25/mo over two years works out to alot more than the $280 I paid for the phone.
Here in Seattle we have HSPA+ and I've got fast internet. Supposed to have LTE next year, but HSPA+ is fine. TMo is moving everything to 1900MHz as fast as they can for iPhone compatibility, so we benefit.
Voice quality on this phone is far better than any HTC. The screen is so large I'm not used to it. Concerned that when I sit down I'll crack it in my back pocket, or it will slip out.
MIUI only allows 4x5 icons on the screen and I think I could use 5x7 so I've posted a request on miuiandroid.com.
Thanks
i want to upgrade my just bought vzn razr xt912 to ics and want to use as gsm phone here in india
can anyone help
which ICS ota file should choose from the list mentioned at the OP
and how to proceed.
regards
Get the one for Verizon Droid RAZR XT912.
Sent using a touch screen
Napisane na ekranie dotykowym
First of all, ALL THE CREDITS go to CellZealot from TeamBlackHat !
This was only possible with the files that he provided!
I was just a simple "guinea pig" that killed a Razr testing theories about downgrading it back to Gingerbread ! :angel:
So lets, f.... do it.
<Warning> By continuing to read and deciding to start this procedure, YOU ARE ON YOUR OWN! I, CellZealot, TeamBlackHat & XDA-Developers WILL NOT be held responsible for any personal or material damage that might incur from the actions described here! That's your decision to go on, so deal with it! YOU ARE WARNED! <Warning>
Requirements:
- Stock ICS SBF fastboot firmware package. Google is your friend.
- a PC x86 computer with a usb port
- Linux operating system. (Ubuntu, Arch, Gentoo, Slackware, Debian, whatever distro you choose...)
- Linux O.S. knowledge. You must be familiar with the command prompt (Bash Shell) and the commands! That's up to you.
- This software package -> http://www.multiupload.nl/VL33M4I4A3
- The "fastboot" program from the Android SDK (latest version that you can find.)
- a software bricked Razr, that only shows itself as a "OMAP4430" device, under Win. "Device Manager", when plugged. Give it a try under a Windows computer, just to make sure.
- MicroUSB to USB cable. The one that came with your Razr.
- The Razr must be charge to the minimum required the bootloader to enable the flashing process. There are other ways to charge your phone without the stock charger. You can search here on XDA for it.
PS: The factory service cable, allows you to bypass the battery check, by allowing the Razr to receive 5v straight from the usb port. As per CellZealot explanation on third post.
Optional but HIGHLY RECOMMENDED !
- a Motorola Factory/Service Cable. You can build your own or buy one! I recommend buying from "TeamBlackHat" as they make high quality cables and adapters! If you prefer, you can just buy the adapter and use your own MicroUSB cable with it.
About the expected end result: your Razr in FastBoot mode, ready to be flashed with a stock firmware.
<Procedure>
- download the package "spyder_bl.7z" and unpack to a empty directory to avoid any confusion.
- you will end up with 3 files - "omapflash-lnx", "pbrdl.bin" & "brdl.bin"
- make the "omapflash-lnx" file executable
- plug the phone to pc and press the power button for 2 seconds, till it apears as a "Texas Instruments" device under the usb list (lsusb) or in the kernel log.
Now you must be quick and start typing in this order:
sudo ./omapflash-lnx pbrdl.bin
sudo ./fastboot flash brdl brdl.bin
You should get a "Okay" status on both of them.
Check your Razr screen and it shall be on "FastBoot AP Mode". From here, you can keep flashing on Linux or boot up Windows and use RSD, wich is more user friendly besides being GUI-Oriented.
Some facts about the 3 files: they are all "signed files" by Motorola, that's why it is safe to use. The OMAP4430 cpu on the Razr is factory programmed to only execute signed code, that's why we needed to find an exploit to execute unsigned code. Examples are the KExec, Boot Manager & Safestrat. All of them available here on XDA in their respective threads.
Peace.
:good:
PS: Do not thank me or my posts. This guide was only possible due to CellZealot support. You must thank him, if for some reason it helped you recover your phone. Copy that?
PS: Thanks also XDA-Developers for this amazing community!
EDIT: Corrected the part about the Factory Service Cable. It does not allow you to charge the Razr but rather supply the necessary juice for the phone to work without a minimum charge. Thanks again, CellZealot!!!
I've tried & failed to brick my phone~ It's now nearly impossible to brick this phone :good:
Just some notes from my journey,
pbrdl.bin only accept few commands... so no oem unlock
pbrdl.bin is 1st-loader for USB boot (mbmloader.bin is for NAND boot)
brdl.bin is just mbm.bin (motorola boot manager)
Thank you for the excellent writeup and for the recommendations for TBH Factory Cable/Adapters!
You are very welcome and congratulations on fixing your phone and being in a very exclusive club of users who have brought their devices back from the brink of the abyss...the truly bricked phone. Also big kudos for going to great lengths to research and attempt many complex means to fix a device you had broken yourself rather than returning it to your carrier under warranty. Your ultimate success is richly deserved.
A couple of points I wanted to clarify.
The Factory Cable/Adapter does not charge the device at all, but bypasses the battery and smart charging circuit altogether and powers the device directly by supplying +5v on pins 1 and 4. It will always power on the device no matter what state the battery is in or without a battery at all.
The other thing is that depending what the circumstances are that lead to the corrupt boot loader, restoring the device can be even easier and not require flashing the firmware.
In my case, I had specifically overwritten the mbmloader and as soon as I repaired that successfully the phone booted up perfectly fine and fully rooted with everything exactly as I had left it the night I hosed it!
cellzealot said:
Thank you for the excellent writeup and for the recommendations for TBH Factory Cable/Adapters!
You are very welcome and congratulations on fixing your phone and being in a very exclusive club of users who have brought their devices back from the brink of the abyss...the truly bricked phone. Also big kudos for going to great lengths to research and attempt many complex means to fix a device you had broken yourself rather than returning it to your carrier under warranty. Your ultimate success is richly deserved.
A couple of points I wanted to clarify.
The Factory Cable/Adapter does not charge the device at all, but bypasses the battery and smart charging circuit altogether and powers the device directly by supplying +5v on pins 1 and 4. It will always power on the device no matter what state the battery is in or without a battery at all.
The other thing is that depending what the circumstances are that lead to the corrupt boot loader, restoring the device can be even easier and not require flashing the firmware.
In my case, I had specifically overwritten the mbmloader and as soon as I repaired that successfully the phone booted up perfectly fine and fully rooted with everything exactly as I had left it the night I hosed it!
Click to expand...
Click to collapse
Thanks once again, my friend. Corrected as per your definition, the section about the FS Cable.
Peace.
:good:
Thank you for this valuable guide, it is a true unbricking solution for the RAZR. Some mirrors of the spyder_bl.7z file. Just in case
http://www.mediafire.com/?z5gp1ztvwj81qr4
http://www.4shared.com/archive/BtfH6ML8/spyder_bl.html
Sorry my english so bad
My droid razr can't to flash brdl.bin
Just show waiting device
How to fix it?
I'm has do all procedure...
Tq b4...
prue said:
Sorry my english so bad
My droid razr can't to flash brdl.bin
Just show waiting device
How to fix it?
I'm has do all procedure...
Tq b4...
Click to expand...
Click to collapse
Ehm...Why did you try this??? Have you read careful enough what this is about?? I'm pretty sure your problem can be solved much easier than this way. Depending on your problem you have with your device I suggest you to open up a new thread in general section (or Q&A Section) and ask for help. BUT:
Don't flash anything to your phone if you don't know exactly what you're doing!.
dtrail1 said:
Ehm...Why did you try this??? Have you read careful enough what this is about?? I'm pretty sure your problem can be solved much easier than this way. Depending on your problem you have with your device I suggest you to open up a new thread in general section (or Q&A Section) and ask for help. BUT:
Don't flash anything to your phone if you don't know exactly what you're doing!.
Click to expand...
Click to collapse
problem solved master
i'm forget to use latest version of fastboot
now mw droid razr has startup normaly
tq all...
but now get new problem device always on fastboot n show "recipe failed"
maybe you can help me 4 this case...
Have same problem with other omap device Huawei U9500 (OMAP4440), but your advice not working unfortunately.
After the message about sending a file, nothing happens, the phone to mode fastboot not pass.
Any advice?
Hi all! XT926 is here)
Tell me please can I restore bootloader on my xt926 through this method? Right now when i connect common usb cable to moto and type "lsusb" i see:
ID: 05c6:f006 Qualcomm, Inc.
But when I connect the cable on Windows, the device appears and disappears in the system (I can hear the sound) infinite time, until I remove the cable.
[Q&A] [SCRIPT] DROID RAZR Utility XT912 Jellybean -- Windows + Mac + Linux (All In O
Q&A for [SCRIPT] DROID RAZR Utility XT912 Jellybean -- Windows + Mac + Linux (All In One!)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [SCRIPT] DROID RAZR Utility XT912 Jellybean -- Windows + Mac + Linux (All In One!). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
AP Fastboot Flash Mode (S) (Boot Failure) after "successful" use of RAZR Utility
Hello XDA forums,
I have been a lurker here for several years and been quite amazed at the wealth of knowledge that is XDA forums. Unfortunately for me, I have run into an issue that I am unable to solve by searching for posts of similar unfortunate souls and can no longer remain a lurker, but must venture forth into the light to seek assistance.
About a year ago I used Matt's wonderful utility to save me from losing my Verizon XT912T RAZR MAXX to brickdom. After which I rooted and installed safestrap. Sometime after this, I somehow wound up getting an OTA that killed the root and made me unable to use TiBackup or get into safestrap. My phone was still working fine (minus root apps) and I was overly busy with work and being a new dad to take the time to try to correct the issue...until this past evening...
Begin problem:
I attempted to use Matt's Jellybean root utility to correct the issue (first using the #2 option), and all proceeded correctly (i.e. phone and computer connected fine and all upload/install processes finished "OKAY" according to the command window. The command window said the phone would reinstall radios and then fully reboot.
The reboot process began as indicated and the red Motorola symbol came up for a few seconds, but then I was dumped into AP Flashboot mode again with the following message:
AP Fastboot Flash Mode (S) (Boot Failure)
0A.77
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED, Status Code:0
Battery OK
OK to Program
Transfer Mode: USB Connected
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB(CG: system, status: 0X0056)
Invalid CG OTV(CG: system)
Figuring that I would just have to suck it up and go with option 1 (data wipe), I went back into Matt's program and re-tried using option 1. Again, all uploads and writes showed "OKAY." The command window then stated that it was wiping cache, and user data and then told me the programming was complete and the phone would reinstall radios and then fully restart.
Again, I was dumped back into the same AP Fastboot Flash Mode (S) (Boot Failure).
I have tried this process several times and searched on this and other forums to try to find a resolution to this issue, but have been unsuccessful. PLEASE, IF ANYONE CAN HELP, I WOULD BE MOST GRATEFUL FOR ANY ASSISTANCE!
Phone info:
Verizon XT912T RAZR MAXX
Version 4.1.2
System Version 98.72.165.XT912.Verizon.en.US
---------- Post added at 02:53 AM ---------- Previous post was at 02:46 AM ----------
The Utility I was referring to in the post was the DROID RAZR Utility Jellybean for Verizon XT912.
I have checked the checksum and it matches what is listed on Matt's page.
I have unzipped the download to a regular folder on my desktop and am not trying to run it directly from the .zip file.
I am NOT running it as administrator.
The program appears to be working correctly, but once done my phone doesn't take and jumps back into AP Fastboot.
snoopshoag said:
Hello XDA forums,
The reboot process began as indicated and the red Motorola symbol came up for a few seconds, but then I was dumped into AP Flashboot mode again with the following message:
AP Fastboot Flash Mode (S) (Boot Failure)
0A.77
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED, Status Code:0
Battery OK
OK to Program
Transfer Mode: USB Connected
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB(CG: system, status: 0X0056)
Invalid CG OTV(CG: system)..
.
unsuccessful. PLEASE, IF ANYONE CAN HELP, I WOULD BE MOST GRATEFUL FOR ANY ASSISTANCE!
Phone info:
Verizon XT912T RAZR MAXX
Version 4.1.2
System Version 98.72.165.XT912.Verizon.en.US
---------- Post added at 02:53 AM ---------- Previous post was at 02:46 AM ----------
The Utility I was referring to in the post was the DROID RAZR Utility Jellybean for Verizon XT912.
I have checked the checksum and it matches what is listed on Matt's page.
I have unzipped the download to a regular folder on my desktop and am not trying to run it directly from the .zip file.
I am NOT running it as administrator.
The program appears to be working correctly, but once done my phone doesn't take and jumps back into AP Fastboot.
Click to expand...
Click to collapse
I have the same problem and I opened up the back for charging through pin Method. [Stupidest Mistake Ever] I can't even claim the warranty now because I broke the small [SHenZen] store sticker (had bought it online).
The thing is, we need an UNLOCKED BOOTLOADER to flash these files brother. The Device is LOCKED, Status Code:0 message should be Device Unlocked Status code:3. And there is no way of getting that I think, there was one but it was has stopped.
Goodbye sweet phone...
Hey Huzaifa, thanks for the reply!
Yeah, I kind of figured the phone was hosed. Played with it some more and still couldn't get any response. I don't by any means claim to be an expert on android, but I do work as a network admin and I've gotten fairly decent at recognizing the severity of an issue so I can give estimates on how long something might take to remedy. This seemed like one of those, "Go directly to jail, do not pass go, do not collect $200," types of situations. I'm guessing that it could probably be repaired by Motorola with a direct connect programming cable, but I doubt it will be worth the hassle. I was overdue for a new phone anyway, so I went ahead and got a note 4. Best phone I've ever had!!! Seriously, when considering new phones it usually takes me a couple weeks and I wind up having to make tradeoffs such as lower camera quality for better battery life. It took about a day of research and playing with phones and I could honestly not find a single drawback to the note 4 (aside from the price :^p). Insane camera battery life 2+ days w/ moderate use, super HD display, fast as heck, great reception in my area (which can be spotty at times). If you still need a replacement, that would be my recommendation.
Thanks man, the problem is it was my brother's phone. I was thinking of buying note 4 too... It'll probably go in my bucket list now...
Is this a Complete Stock ROM installation option?
Suppose I've just wiped my stock ROM partition of my phone and have installed a custom ROM on it, Will this utility still be able to flash the official JB rom on my phone?
huzaifaaleem said:
Suppose I've just wiped my stock ROM partition of my phone and have installed a custom ROM on it, Will this utility still be able to flash the official JB rom on my phone?
Click to expand...
Click to collapse
Yes.
And here is updated utility
http://forum.xda-developers.com/showthread.php?t=2861798
Sent from my Razr XT910
Finally I can get me space for Custom rom
welder73 said:
Yes.
And here is updated utility
http://forum.xda-developers.com/showthread.php?t=2861798
Sent from my Razr XT910
Click to expand...
Click to collapse
Thanks alot
huzaifaaleem said:
Thanks alot
Click to expand...
Click to collapse
No problem
Sent from my Razr XT910
waiting for device VZ razr xt912 jelly bean
32 bit Linux System
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*]
[*] Razr Blade: Motorola Droid Razr 4.1 Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Thanks to p3droid for assistance in testing.
[*]
[*] Note: this will not work on Razr HD, Razr M, etc.
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Please carefully follow any instructions provided in the exploit.
[*]
[*] Press enter to root your phone...
[*] Waiting for device...
managed to get thru option 1 fine.
http://forum.xda-developers.com/showthread.php?t=2192467&page=1
But trying to root the application appears to hang.
any idea what I'm missing here?
thanks.
fadobee said:
32 bit Linux System
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*]
[*] Razr Blade: Motorola Droid Razr 4.1 Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Thanks to p3droid for assistance in testing.
[*]
[*] Note: this will not work on Razr HD, Razr M, etc.
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Please carefully follow any instructions provided in the exploit.
[*]
[*] Press enter to root your phone...
[*] Waiting for device...
managed to get thru option 1 fine.
http://forum.xda-developers.com/showthread.php?t=2192467&page=1
But trying to root the application appears to hang.
any idea what I'm missing here?
thanks.
Click to expand...
Click to collapse
saferoot is a little easier to root with.
Unfortunately I only have a linux OS to work with, this vid appears to be Win based.
I did try running the application via wine: almost worked.
ok.. i found the sh. and ran, same issue, then the script said to switch back to camera mode and this picked up the phone.
finally! thank you very much for assistance!
The SU application says I can only add a password by purchasing SU pro. Is there another way to add this password?
XT912 Stuck in Red Eye - Seeking Some Hand Holding
I am relatively novice relative to what makes our smart phones work, but I am fairly "coachable" and a quick study. I have an XT912 with Verizon that is stuck in red eye and goes no where. I am sure my phone operating system updated circa Nov 2013, but frankly, I am not clear as to the details of which version. It was running great as recently as 3 weeks ago, then started just rebooting repeatedly. I made some feeble and likely reckless attempts to do some of the reboot actions and other remedies related to the holding vol up & vol down button while holding power button. I was completely reckless in that. Now I am just stuck on the red eye. I can still get to that reboot screen that has the options to do Fastboot et al. So I am grateful / hopeful / lucky that it appears I have not bricked the phone.. I came across this thread and suspect it could help me get my phone back on line. http://forum.xda-developers.com/showthread.php?t=2192467
Is there any guidance to use these utilities for the novice user? Maybe not quite smartphone reboots for dummies, but something dumbed down a bit for the more timid? I sure do appreciate any replies.
pghrob said:
I am relatively novice relative to what makes our smart phones work, but I am fairly "coachable" and a quick study. I have an XT912 with Verizon that is stuck in red eye and goes no where. I am sure my phone operating system updated circa Nov 2013, but frankly, I am not clear as to the details of which version. It was running great as recently as 3 weeks ago, then started just rebooting repeatedly. I made some feeble and likely reckless attempts to do some of the reboot actions and other remedies related to the holding vol up & vol down button while holding power button. I was completely reckless in that. Now I am just stuck on the red eye. I can still get to that reboot screen that has the options to do Fastboot et al. So I am grateful / hopeful / lucky that it appears I have not bricked the phone.. I came across this thread and suspect it could help me get my phone back on line. http://forum.xda-developers.com/showthread.php?t=2192467
Is there any guidance to use these utilities for the novice user? Maybe not quite smartphone reboots for dummies, but something dumbed down a bit for the more timid? I sure do appreciate any replies.
Click to expand...
Click to collapse
In the index there is a link to how to videos http://forum.xda-developers.com/showthread.php?t=3023837
[INDEX] Motorola Droid Razr Development (2015)
Sent from my XT907 using Tapatalk
[Q] DROID4 XT894 cannot enter ap fasboot
HELP i have a motorola DROID4 XT894 i tried to flash back to stock rom 4.1.2 jellybean but the phone doesn't enter the AP FASBOOT, its become blank (only black displayed) and no sign like: battery ok/ usb conected etc..only black screen display..i tried many times and its alaways stuck in the same way. i enter to recovery mode and wipe data and cache many times and i try to enter AP fasboot but its still the same..hope someone of u can give me answer to recover my phone..thx
Pak rebound said:
HELP i have a motorola DROID4 XT894 i tried to flash back to stock rom 4.1.2 jellybean but the phone doesn't enter the AP FASBOOT, its become blank (only black displayed) and no sign like: battery ok/ usb conected etc..only black screen display..i tried many times and its alaways stuck in the same way. i enter to recovery mode and wipe data and cache many times and i try to enter AP fasboot but its still the same..hope someone of u can give me answer to recover my phone..thx
Click to expand...
Click to collapse
The bootloader maybe a bit mucked up, when you get black screen, does it connect to pc? Show up in Device Manager?
RSD Lite?
Sent from my XT912 using Tapatalk
Flashed Droid Xt912 with the updated Utility. didn't fix my problem It still Auto reboots. I did option 2 then 1 and still the same result. any ideas or suggestions would be helpful.
Jud631 said:
Flashed Droid Xt912 with the updated Utility. didn't fix my problem It still Auto reboots. I did option 2 then 1 and still the same result. any ideas or suggestions would be helpful.
Click to expand...
Click to collapse
maybe hardware failure, like a bad battery.
but could try flashing firmware with RSD Lite, links in Index http://forum.xda-developers.com/droid-razr/general/index-motorola-droid-razr-development-t3023837
sd_shadow said:
maybe hardware failure, like a bad battery.
but could try flashing firmware with RSD Lite, links in Index http://forum.xda-developers.com/droid-razr/general/index-motorola-droid-razr-development-t3023837
Click to expand...
Click to collapse
Bummer. Tried flashing again with the RSD Lite. still I get to the start menu select english then say's please wait this may take a few minutes. then after a while the screen goes darker and then it reboots. back to the start mode. If anybody has anyother ideas please post.
Thanks
Jud631 said:
Bummer. Tried flashing again with the RSD Lite. still I get to the start menu select english then say's please wait this may take a few minutes. then after a while the screen goes darker and then it reboots. back to the start mode. If anybody has anyother ideas please post.
Thanks
Click to expand...
Click to collapse
Try factory reset from recovery.
Sent from my Razr XT910
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
so I been trying to install GSI and I erase all the partitioning and forgot to create them again and now my phone is hard brick when I connect my deep flash cord to my Moto g power 2021 and hold the button it's show no ports and I have the driver install when I connect only thing that happen is that the led blink over and over again. What type of brick is this and is there a fix or i have to buy a new phone please help
Are you using LMSA tool to flash? Because that's what I recommend you use. Also make sure you have the Motorola drivers installed on your computer
That is not the correct software to use while restoring this phone use Fastboot and grab the stock firmware here and match the model https://mirrors.lolinet.com/firmware/motorola/borneo/official/ Flashing instructions are literally a Google search away.
iTrySmoke said:
That is not the correct software to use while restoring this phone use Fastboot and grab the stock firmware here and match the model https://mirrors.lolinet.com/firmware/motorola/borneo/official/ Flashing instructions are literally a Google search away.
Click to expand...
Click to collapse
LMSA is the official tool to use for Lenovo and Motorola devices. Although lolinet is unofficial, both are equally good tools to use to unbrick a device
Fazwalrus said:
LMSA is the official tool to use for Lenovo and Motorola devices. Although lolinet is unofficial, both are equally good tools to use to unbrick a device
Click to expand...
Click to collapse
I've been told by the phone it's self to use that software for Verizon devices only but Aye does the same thing I guess
KILLFIREY1389 said:
so I been trying to install GSI and I erase all the partitioning and forgot to create them again and now my phone is hard brick when I connect my deep flash cord to my Moto g power 2021 and hold the button it's show no ports and I have the driver install when I connect only thing that happen is that the led blink over and over again. What type of brick is this and is there a fix or i have to buy a new phone please help
Click to expand...
Click to collapse
Suggest you go onto the Motorola Blankflash channel on Telegram to get some help: https://t.me/motoblankflash
The admin guys there know their stuff and can give you some specific help/recommendations and the correct method and blankflash files to use.