Hi XDAer
I've tried to fix my Motorola Razr HD XT925 on Rogers.
The problem I original had was my phone was freezing on the stock 4.1.2 So i tried to downgrade to ICS with DROID Utility 1.10. That's when i really messed up my device. I tried to do every type of restore from 1.20, 2.0, and 4.0 utilities. Rogers stock ICS and Jellybean through RSD Lite.
Some errors that occured.
1. partition (boot) security version Downgraded
2. fastboot reason: boot failure
3. when restoring get partition error, then removed line in xml
4. boot error, then removed line in xml
5. logo error, then removed line in xml
So in a nutshell the phone only boots to fastboot
and this is what it loads to
Invalid Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013 02-14 09:13:08)
Device is LOCKED, Status Code: 0
I've been trying for more that 3-4 weeks, If anyone can help that would be amazing
kay_aku said:
Hi XDAer
I've tried to fix my Motorola Razr HD XT925 on Rogers.
The problem I original had was my phone was freezing on the stock 4.1.2 So i tried to downgrade to ICS with DROID Utility 1.10. That's when i really messed up my device. I tried to do every type of restore from 1.20, 2.0, and 4.0 utilities. Rogers stock ICS and Jellybean through RSD Lite.
Some errors that occured.
1. partition (boot) security version Downgraded
2. fastboot reason: boot failure
3. when restoring get partition error, then removed line in xml
4. boot error, then removed line in xml
5. logo error, then removed line in xml
So in a nutshell the phone only boots to fastboot
and this is what it loads to
Invalid Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013 02-14 09:13:08)
Device is LOCKED, Status Code: 0
I've been trying for more that 3-4 weeks, If anyone can help that would be amazing
Click to expand...
Click to collapse
can you acess to the console in fastboot mode?
you can erase all your partitions from there with this commands.
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase boot
fastboot erase recovery
then you can extract the files from the rom you want to flash the new partitions one by one.
fastboot flash system system.img
fastboot flash userdata userdata.img
..... etc
(you need to have your bootloaded unlocked to do this)
i tried to unlock my bootloader with droid utilities with no luck
Hi
Can u tell how to recover dead alcatel 991X-2AALFR2
Sent from my HTC Panache using xda app-developers app
This isn't the help hotline forum guys. This is for a specific phone.
Sent from my PACMAN MATRIX HD MAXX
Then where can i get solution for this issue....
Sent from my HTC Panache
I'd look for a forum specific to your device or post in the general android section.
Sent from my PACMAN MATRIX HD MAXX
Ok thank you, friend
Sent from my HTC Panache
anybody know any other way to fix it
Related
My Xoom has had an odd problem. When I got it new, I unlocked the bootloader and rooted.
However, any pushed updates from Moto such as HLK55 caused my Xoom to boot and show the unhappy !Android icon. I had to shut down cold, and reboot. In other words, it never updated properly.
Now that ICS is out, I have Kang 1/15 running but have some non-crash issues. I'd like to flash to try to update to the factory ICS push file but fear that my XOOM won't complete as well.
Any ideas?
So long as you flash back to complete stock using the Motorola files you should be able to upgrade your way up to ICS (via 3.1 and 3.2).
Get the files from http://developer.motorola.com/products/software/
And as on that page, get ADB running and make sure it detects your device then run these commands.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Make sure you get the right version for your device.
hello
i have just boght my xoom and updated it to android ics i was trying to flash it back to factory image to root it but it was stuck on M logo and Dual Core screen
can any one help me please ?
also i intalled AndroidSDK
as in this thread http://forum.xda-developers.com/showthread.php?t=1097997
when i type the command
PHP:
fastboot flash boot boot.img
it gives me error message mean boot.img is not found !
ok i flashed my xoom use these steps
PHP:
Instructions to Flash & Re-Lock Your Motorola XOOM:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
when i did
PHP:
fastboot flash system system.img
command
it gives me message
((failed to process command error 0x12003 ))
can any one help me
You have to place the images in the same folder in which fastboot is present. So, just check if all the four images are present
Sent from my MZ601 using XDA App
thanks for your post
i discoverd the problem was the usb attached in front of my pc and it shulold be connected from the back of the pc
so my broplem solved
Hey guys,
I got this Motorola Xoom from a friend that he wanted updated. He got the Xoom from a contact in Motorola. The thing is nothing shows up in software updates, then I checked the version number
trygon-userdebug 3.1 HMJ37 124251 test-keys
I figured test-keys release won't get the ota notification. I want to update it to Jellybean, so what options do I have? Official JB is preferable but if there's no way out of this then I can root.
I'd like to add, I have no clue which Xoom this is. It is 32gb, has some sort of slot on top(not sure simcard or what). And I can't find the model number anywhere on the body or in settings.
I connected to PC and saw MZ604. I'm checking out the images section now.
Ok I assume I can download a stock image and then put them files in the fastboot folder and flash via these commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
death__machine said:
Ok I assume I can download a stock image and then put them files in the fastboot folder and flash via these commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Click to expand...
Click to collapse
That'll do it.
Do I have to unlock before doing any of the above? I got these steps from http://forum.xda-developers.com/showthread.php?t=1081519
Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
My bad! Apologies.
I used a European Image and flashed it successfully. It was a Honeycomb image, I updated it a lot of times till it reached 4.0.4. Hmm, so there's no jellybean yet for people running European Firmware I read. Another issue was play store kept saying server error.
I googled the Server Error and sorted it is. Thanks guys!
I can understand this is very old post. But I see you said you sorted this by using European Image and flashed it successfully. can you tell me which European image you used ?
Hello
I have a Motorola Xoom from Verizon, and this is the issue.
When I turn on, the tablet it's stuck in M logo screen, I already read almost any information about this issue, but still I can't use my xoom.
I already done this: the bootloader is already unlock
a) Files From MZ600 HRI39
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
b) used RSD method
c) used recovery method too
I had used every method on this forum to recover my Xoom, and nothing seems to work, at this time I don't know what else do.
adb commands doesn't work for me, only with fastboot and RSD is visible my device.
At this time I accept any sugestions, Since apply a factory reset, or install a new Android version
Hey Guys,
I rooted my device a while ago and everyday had to dismiss the OTA update for the last few months. The other night I accidentally accepted the OTA and know my phone is stuck in a bootloop when connected to power. I'm occasionally able to get into Fastboot mode for RSD to see the phone, ADB will not see the phone. When I attempt to select Recovery or Factory the phone bootloops. I have also tried House of Moto and that didn't work.I have tried flashing all the files located at sbf with no luck. In Fastboot the Device is listed as UNLOCKED with a Status Code: 1.
Any help will be greatly appreciated.
When I flash using House of Moto I get an error for the following:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img
NON-HLOS.bin
uniqueflips said:
Hey Guys,
I rooted my device a while ago and everyday had to dismiss the OTA update for the last few months. The other night I accidentally accepted the OTA and know my phone is stuck in a bootloop when connected to power. I'm occasionally able to get into Fastboot mode for RSD to see the phone, ADB will not see the phone. When I attempt to select Recovery or Factory the phone bootloops. I have also tried House of Moto and that didn't work.I have tried flashing all the files located at sbf with no luck. In Fastboot the Device is listed as UNLOCKED with a Status Code: 1.
Any help will be greatly appreciated.
When I flash using House of Moto I get an error for the following:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img
NON-HLOS.bin
Click to expand...
Click to collapse
Does it ever actually boot up and then just restarts? Or are you never getting to the homescreen?
no home screen
Hi,
It won't even boot loop unless it's connected to power. When it is it just boot loops, tried everything but can't get past the boot loop. Spent countless hours trying to make any progress.
try flashing TWRP from fastboot
Code:
fastboot erase recovery
fastboot flash recovery name.img
if you get into recovery try restoring a nandroid
if that doesnt work, make sure you are flashing the appropriate SBF from the update you were in teh process of taking. My bet is somehow your device got partially updated (bootloader) so you are now unable to flash the SBF you were prevously on. ie. you were on 4.2.2, and took the 4.4 update, you need to flash the SBF for 4.4, not 4.2.2
Once you get back up and running, make sure you disable the Moto OTA app using titanium or the like. That should prevent the phone from trying to take an update again.
Still no luck
Thanks everyone for the suggestions, I'm not sure which firmware it was trying to install so I installed all the firmwares available via House of Moto and still no luck. Tried performing a Full and Keep Data and still the phone will continue to boot loop. One thing I did notice during the install using House of Moto I see the following error multiple times:
(bootloader) Variable not supported!
I got this error on all 5 firmwares.
Any ideas...
uniqueflips said:
Thanks everyone for the suggestions, I'm not sure which firmware it was trying to install so I installed all the firmwares available via House of Moto and still no luck. Tried performing a Full and Keep Data and still the phone will continue to boot loop. One thing I did notice during the install using House of Moto I see the following error multiple times:
(bootloader) Variable not supported!
I got this error on all 5 firmwares.
Any ideas...
Click to expand...
Click to collapse
what version of android were you on prior to this happening. What version was the OTA attempting to update you to?
I think I was on Android 4.4 Blur_Version.19.5.3.obake_verizon.Verizon.en.US, not 100% sure what it was trying to install 4.4.4 or 4.4 19.6.3.
Tried House of Moto again and on the 4.2.2 12.15.15 and 4.4.4 I don't get the (bootloader) Variable not supported! error. The phone still boot loops.
uniqueflips said:
I think I was on Android 4.4 Blur_Version.19.5.3.obake_verizon.Verizon.en.US, not 100% sure what it was trying to install 4.4.4 or 4.4 19.6.3.
Tried House of Moto again and on the 4.2.2 12.15.15 and 4.4.4 I don't get the (bootloader) Variable not supported! error. The phone still boot loops.
Click to expand...
Click to collapse
have you tried with the latest version of RSD lite?
If so make sure you edit the XML file to remove the part about erasing userdata
lets try this too... go to sbf.droid-developers.org and download this file for the maxx "Android 4.4.4
Blur_Version.21.11.21.obake_verizon.Verizon.en.US"
Install the latest moto device manager and RSD lite, then try flashing (might erase userdata)
If that does not work, you can manually flash each file in fastboot, lmk if any of that works
last Q, do you have a motorola factory cable?
Tried with and without removing the getvar file and no luck, still stuck in an endless boot loop when connected to power. ADB still doesn't see the device even in Fastboot mode. Never flashed each file in fastboot individual doesn't that require ADB?
uniqueflips said:
Tried with and without removing the getvar file and no luck, still stuck in an endless boot loop when connected to power. ADB still doesn't see the device even in Fastboot mode. Never flashed each file in fastboot individual doesn't that require ADB?
Click to expand...
Click to collapse
no you dont use adb from fastboot, you use "fastboot"
Lets see if we can get you booted to a recovery. Download this file, save it as recovery.img in your ADB directory.
boot to fastboot and run this command to determine fastboot sees the device
Code:
fastboot devices
If you see your device, then run the next command
Code:
fastboot flash recovery recovery.img
then try to boot to recovery. post result (make sure when you highlight "recovery" in fastboot you use volume up to select it. I just made the mistake of using power and my phone wouldnt boot to recovery)