ive f$£ked my razr i, i have rooted and all the rest using mattlgroff and then tried to fastboot back to stock and now my phone is stuck in fastboot, when in fast boot i can select from the item then nothing happens, i.e i press normal startup and then it just hangs, please please help me
doug143 said:
ive f$£ked my razr i, i have rooted and all the rest using mattlgroff and then tried to fastboot back to stock and now my phone is stuck in fastboot, when in fast boot i can select from the item then nothing happens, i.e i press normal startup and then it just hangs, please please help me
Click to expand...
Click to collapse
JB or ICS?
Im having the same or a really similar problem. When i select recovery it just says booting into recovery but never does. Im on ICS.
I had a similar issue. RSD Lite (https sites google com [slash] site [slash] motosbf [slash] rsdlite) is your first port of call, using the appropriate image from http sbf droid-developers org [slash] smi [slash] list.php .
However, that only partially worked for me. It failed first on the logo - so I extracted the zip from droid-devlopers, and edited the XML to remove the complete line <step operation="flash" partition="motoboot" filename="motoboot" ...
After that it would flash up to and including the radio, but then fail on the system_signed ( as it's over 100MB).
To get around that I used the enhanced fastboot from mattlgrof's package http forum xda-developers com [slash] showthread.php?t=1936512, and manually compted the final steps in the xml file in the extracted zip folder:
fastboot flash system system_signed
fastboot flash cdrom cdrom_signed
fastboot oem fb_mode_clear
Then a
fastboot reboot
And all was well - back to stock. Upgraded from there, and flashed CWM and then rooted. Hope this helps
AW: [Q] Bricked my razr i/help me!!!
Use RSD 6.1.4 and you won't have trouble with flashing the System...
Gesendet von meinem XT910 mit Tapatalk 2
Lorewin said:
I had a similar issue. RSD Lite (https sites google com [slash] site [slash] motosbf [slash] rsdlite) is your first port of call, using the appropriate image from http sbf droid-developers org [slash] smi [slash] list.php .
However, that only partially worked for me. It failed first on the logo - so I extracted the zip from droid-devlopers, and edited the XML to remove the complete line <step operation="flash" partition="motoboot" filename="motoboot" ...
After that it would flash up to and including the radio, but then fail on the system_signed ( as it's over 100MB).
To get around that I used the enhanced fastboot from mattlgrof's package http forum xda-developers com [slash] showthread.php?t=1936512, and manually compted the final steps in the xml file in the extracted zip folder:
fastboot flash system system_signed
fastboot flash cdrom cdrom_signed
fastboot oem fb_mode_clear
Then a
fastboot reboot
And all was well - back to stock. Upgraded from there, and flashed CWM and then rooted. Hope this helps
Click to expand...
Click to collapse
Thank you so much, you saved me i just did the first part, removed the line in the xml file and it flashed past the system_signed part and worked and my phone is now alive again thank you so so much
doug143 said:
Thank you so much, you saved me i just did the first part, removed the line in the xml file and it flashed past the system_signed part and worked and my phone is now alive again thank you so so much
Click to expand...
Click to collapse
Glad it worked I wish I'd known about the later version of RSD HSD-Pilot mentioned, as that makes it easier. Still, learning is good
Related
[UNLOCKED BOOTLOADER ONLY ]
Okay i have found the solution ! but i take no responsability if you brick your phone !
My device is an XT925 ! from Rogers Canada !
I never lost IMEI during this downgrade ! Your bootlader must be unlocked !
1 : Charge your phone !
2 : Download the DROID RAZR HD Utility 1.10 - http://forum.xda-developers.com/showthread.php?t=1970267
3 : Go to fastboot...
4 : Downgrade ( yes is for XT926 but it work for XT925 )
5 : Go to fastboot don't let android start ( push 10 seconds power on - vol- - vol+ if the verizon logo start ...the phone shutdown go back to fastboot )
( i don't try to start the phone with the xt926 rom... )
6 : Download and flash via rsd the rom you want ( work great with O2 and LATAM retail )
( off topic : latam retail have only 3 language ... English spanish port...)
7: Downgrade security error ? or get var error ? Edit the XML Inside the rom : delete the 2 get var line :
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
and delete :
<step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" />
8 : Enjoy your ics stock rom...
9 : Upgrade to Jelly Bean if available and if you want
ROOT ALL JB ROM ( and ICS rom )
No need to use OTA rootkeeper when bootloader is unlocked !
Flash CWM
http://forum.xda-developers.com/showthread.php?t=1973904
and Flash SuperSU Via CWM
http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
Need LTE on JB rom ?
Flash via fastboot your modem and fsg...
fastboot erase modemst1
fastboot erase modemst2
Fastboot flash modem modem_signed
Fastboot flash fsb fsb_signed
I really love the o2 ROM... no bloatware...Fast... many language ( french ... arabic... etc )
OP you're a genius thank you so much for figuring this out!
Hey do you know if the Rogers software will work for Fido? Well I got all of the Fido custom software?
SickBeast said:
OP you're a genius thank you so much for figuring this out!
Hey do you know if the Rogers software will work for Fido? Well I got all of the Fido custom software?
Click to expand...
Click to collapse
Rogers and Fido have the same firmware ! ( XT925.RCI... )
o2qc418 said:
Rogers and Fido have the same firmware ! ( XT925.RCI... )
Click to expand...
Click to collapse
Thanks for that. I'm going back to the stock software because I cannot do tethering on LTE with the jelly bean ROM.
Well done!! Will try that today, kudos to you!!
Do not delete this line
<step operation="oem" var="fb_mode_set" />
Click to expand...
Click to collapse
Why ... if you do not delete ... there are an error when you flash...
This method is listed in many others topics ...
The only line anothers line i have deleted is
<step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" />
if i don't delete i have the downgrade security error
I really have no error with my XT925 ! from Rogers Canada !
Flashed 4 friend with the O2 rom
matias-c-18 said:
Do not delete this line
Click to expand...
Click to collapse
Why not? I deleted that line and the last line (see below) that was similar. No issues whatsoever, in fact the whole thing worked a treat!
The other line I also deleted was:
<step var="fb_mode_clear" operation="oem"/>
I figured if you're not setting it at the beginning, then there is no need to clear it at the end.
If you have problem with your LTE
Make this before flashing the modem and fsg via fastboot
fastboot erase modemst1
fastboot erase modemst2
Worked perfectly for me now in original Telcel firmware.
Followed steps to the letter.
thank you!!
So, what exactly is the point of the DROID RAZR HD Utility 1.10? I reverted back to stock ICS by deleting that partition line and the getvar line and flashing via RSD Lite.
If you have to delete the <step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" /> line, that just means that there's still something irreversible after going JB.
Update: My SD card is not accessible after doing things my way.
Update 2: I think I'm retarded... I had my USB settings in Mass Storage mode (which blocks me from my SD card from my phone).
Hi,
What is that "partition" line do anyway? Can we delete it without consequences ?
Sent from my XT925 using xda app-developers app
I am on stock ICS Telcel Rom with unlocked bootloader.
Tried to upgrade to Brasilian Retail 4.1.2 FW using RDS lite 6.0.
1. The power in the house went down, resulting a Fail in the flashing process.
2. Booting up the phone brings me straight to Fastboot saying: Fastboot reason: Flash Failure.
3. Selecting "Normal Powerup" the phone boots to my stock ICS.
4. I tried flashing the Stock ROM through RDS Lite, but it gives me a "Partition_signed" error
I believe that my Fastboot is somehow corrupted and i want to try the following method to recover:
1. Download Telcel Stock Rom
2. Edit the .xml file removing the lines:
a. <step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" />
b. Getvar line
3. Install the ROM using RDS lite 6.0
Is this the correct way? Also: what does eliminating the "Step operation.." line means?
---------- Post added at 08:21 PM ---------- Previous post was at 07:47 PM ----------
Scourge1024 said:
So, what exactly is the point of the DROID RAZR HD Utility 1.10? I reverted back to stock ICS by deleting that partition line and the getvar line and flashing via RSD Lite.
If you have to delete the <step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" /> line, that just means that there's still something irreversible after going JB.
Update: My SD card is not accessible after doing things my way.
Update 2: I think I'm retarded... I had my USB settings in Mass Storage mode (which blocks me from my SD card from my phone).
Click to expand...
Click to collapse
What do you mean when you say: "...That just means that there's still something irreversible after going JB".
elcacho said:
I am on stock ICS Telcel Rom with unlocked bootloader.
Tried to upgrade to Brasilian Retail 4.1.2 FW using RDS lite 6.0.
1. The power in the house went down, resulting a Fail in the flashing process.
2. Booting up the phone brings me straight to Fastboot saying: Fastboot reason: Flash Failure.
3. Selecting "Normal Powerup" the phone boots to my stock ICS.
4. I tried flashing the Stock ROM through RDS Lite, but it gives me a "Partition_signed" error
I believe that my Fastboot is somehow corrupted and i want to try the following method to recover:
1. Download Telcel Stock Rom
2. Edit the .xml file removing the lines:
a. <step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" />
b. Getvar line
3. Install the ROM using RDS lite 6.0
Is this the correct way? Also: what does eliminating the "Step operation.." line means?
Click to expand...
Click to collapse
It shouldn't harm your cellphone, it is weird that it boots normally on your stock ics rom though..
Try to do a full revert to stock and see what it gets you.
My understanding is that the "step operation" delete eliminates some verifications that Rsd lite does before flashing, it is useful if your phone is hanging in some part of the process, it it isn't, it doesn't make any difference (but it normally WILL hang in some part of the process )
I have no idea what has happened to my razr i but everytime I boot up it goes straight into AP fastboot mode
and the following 3 lines appear,
"dismatched partition entry array crc32
fastboot reason: flash failure
fastboot:max download size 100mb
I have tried to flash a rom in RSD LITE but every rom I flash just fails.
I have tried to flash via the fastboot roms but my phone isnt recognised
can anyone please help.
vuittion said:
I have no idea what has happened to my razr i but everytime I boot max up it goes straight into AP fastboot mode
and the following 3 lines appear,
"dismatched partition entry array crc32
fastboot reason: flash failure
fastboot:max download size 100mb
I have tried to flash a rom in RSD LITE but every rom I flash just fails.
I have tried to flash via the fastboot roms but my phone isnt recognised
can anyone please help me please.
Click to expand...
Click to collapse
Easy, easy. Just take the .xml file of the rom you're tryng to flash, delete the whole "motoboot" line, and try to flash again with RSD.
You should be fine.
AW: Please help!
What's your Region?
The Motoboot line - Trick only works with an unlocked BL. If he's still locked he needs an actual Fastboot.
Sent from my XT890
The bootloader is unlocked and im from the UK.
Im not sure how and what im supposed to change in the firmware for a successful flash.
Many thanks for all your help.
AW: Please help!
http://sbf.droid-developers.org/smi...17.0R_USASMIICSRTGB_P042_A005_S1FF_fb.xml.zip
Flash this one without any changes.
Sent from my XT890
sorted
Thank you so much for all your help, my Razr i is now alive and kicking once again.
Hey guys, I'm about to cry :crying: - hope somebody knows a fix :highfive:
To keep it short, what I've done:
Unlocked my bootloader and installed CWM Recovery.
Everything worked.
Then... lastly I wanted to remove the "Bootloader Unlocked message/image"... and flashed a different logo using following this guide http://forum.xda-developers.com/showthread.php?t=1980139 (which was not intended for the XT890 and JB - rolleyes)
Code:
fastboot flash logo [path to the logo.bin i downloaded]
and it returned
Code:
[B]"None signed image detected. Fastboot command failed.[/B]
Now my XT890 JB 4.1.2 EU stays at the "Bootloader Unlocked Screen" when i try to boot (choosing Recovery, Factory etc from AP).
I'm - as you probably can tell already - NOT an expert, but my hope is: I can "fix" it by flashing the logo again with the original/or compatible logo.bin. (incase this should be possible please provide me with a link to it)
Thanks in advance for any input.
Everything works again
I downloaded the proper stock firmware from here http://forum.xda-developers.com/showthread.php?t=2239706, extracted the logo_signed and ulogo_signed, and then "reflashed" the logo_signed using (again)
Code:
fastboot flash logo [path to the logo_signed file]
My next try would have been flashing the ulogo_signed file, but since everything worked out, I'll surely skip that.
PS: Unless someone suggests, that I also should flash the ulogo_signed file (which somehow I doubt)
Pinky-swear: From now on I'll read the whole threads before doing "anything" and I try to avoid doing "anything" on top
Cheers.
Yesterday my moto x alerted me that the KitKat update had been downloaded and was ready to install. I selected INSTALL and the installation began. About a minute into it, it kicked me to the bootloader with the message, "Failed to hab check for recovery: 0x56. Boot up failed".
Also see my post at androidcentral.com at forums.androidcentral.com/moto-x/336036-kitkat-crashed-my-moto-x-unrecoverable.html
Note that my moto x has never been rooted.
forums.androidcentral.com/attachments/moto-x/92779d1384906583-kitkat-crashed-my-moto-x-unrecoverable-kitkat_error.jpg
I selected "Recovery" and it rebooted and attempted to re-install, but then I was met with a image very similar to this except it said "ERROR":
forums.androidcentral.com/attachments/moto-x/92780d1384906685-kitkat-crashed-my-moto-x-unrecoverable-android-error.jpg
Then a few seconds later it rebooted again and now it just gets stuck at the Motorola logo:
forums.androidcentral.com/attachments/moto-x/92781d1384906724-kitkat-crashed-my-moto-x-unrecoverable-moto_x_boot_logo_featured_small.jpg
If I try any of the other options in the boot loader, the behavior is the same.. it gets stuck at the Motorola logo. Yesterday it sat that way for 4 hours before the battery died.
Today I tried connecting it to my computer via USB. My Mac doesn't appear to recognize that it's been connected even though the drivers have been installed. In a Windows VM with MDM it recognized the first time I connected it, but the MDM icon promptly disappeared from the status bar.
I spoke with Verizon tier 2 tech support yesterday and they didn't seem very knowledgeable - the person I spoke with didn't even know what KitKat is.
Surprisingly, I thought I had set up the Motorola data backup to the cloud, but verizon tech support said I must not have enabled it. So my biggest worry is that I've lost all my data (pictures/videos/contacts/etc...).
I'm hoping that somebody on this forum might have some advice for me.
Thanks,
Chris
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
cbridgers, that error happened to me while i was trying to flash through RSD Lite the leaked version of Kitkat. Because it was only to AT&T phones, it gave me that error cause i didnt have an unlocked bootloader. So what i did was flash back the 4.2.2 and for my surprise the phone was with all my config and data, nothing was erased.
Few suggestions...
cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
OK, I got past the previous error by increasing the RAM allocated to my Windows VM. Now I get the following error when running "fastboot flash system system.img":
sending 'system' (850189 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.313s
cbridgers said:
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris
Click to expand...
Click to collapse
Make sure you are using the newest fastboot files, the older ones do not chunk the system image and it is too large to flash.
New fastboot for Mac -- > http://www.teamblackhat.net/Downloads/Darwin.zip
New fastboot for Windows --> http://www.teamblackhat.net/Downloads/fastboot.zip
Use the house if moto save data option you can fxz using rsd or fastboot and it will not erase data at all. I have used it many times works great.
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
Click to expand...
Click to collapse
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
"/modem/image/dsps.b00" has unexpected contents.
Installation aborted
Click to expand...
Click to collapse
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak
Try this
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then take all the files from the first OTA sbf and flash them in order
does that work?
waiflih said:
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak
Click to expand...
Click to collapse
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.
jimmydafish said:
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.
Click to expand...
Click to collapse
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052
waiflih said:
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052
Click to expand...
Click to collapse
They are in the FXZ file named NON-HLOS.bin
Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052
waiflih said:
Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052
Click to expand...
Click to collapse
Well what are you trying to do? but if unlocked you can flash anything you want. I would stay far away from flashing any bootloader, tz, gpt, or sbl files though.
Only flash those files I named before.
Yes, i only flash the files i know are safe to flash, i dont like to use rsdlite. Thx again
Enviado desde mi XT1052
I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140
ekraincg said:
I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140
Click to expand...
Click to collapse
I'm having the same problem with my T-Mo moto x I received yesterday. I tried the fastboot erase cache method. It works to the extent that I can boot back into 4.2.2 but I can't update or perform a factory reset from the settings menu.
When I give the command to fastboot erase cache the bootloader says 'get-var partition type' and 'erasing cache' however the bootloader never says 'cache erased' or any other confirmation message. Fastboot on the desktop does say 'cache erased' though.
Finally, I would try to flash the stock images but I can't seem to find them anywhere. Can someone point me to them please?
Hi there
That's my first post, so please be understanding. Bought a Motorola phone as it is (no water damage) which comes to booting logo and after few minutes keep restarting and trying to booting with no results. I've started red some posts, already but i'm stuck. Reset doesn't work (Power button+volume control down), but when i press power button +camera button and plug in with computer, it shows black screen and green led. Already installed MEDFIELD drivers, RSD Lite and xFSTK-DLDR. tried already RSD Lite with no luck (i've downloaded CFC_signed_customer_8.7.1I-110_IFW-DE-31_RTEU.xml and CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml)
Can get to AP Fastboot Flash Mode, but when i tried to do Factory or Recovery gets:
Failed to enter Factory/Recovery mode. error code -18
No more error code, only some kind of "GETVAR" failed
Read here
http://forum.xda-developers.com/showthread.php?t=2166646
CWMR or TWRP install easy 19-Sep-13
Install and try again
Enviado desde mi GT-I8190L
jacbarahona72 said:
Read here
http://forum.xda-developers.com/showthread.php?t=2166646
CWMR or TWRP install easy 19-Sep-13
Install and try again
Enviado desde mi GT-I8190L
Click to expand...
Click to collapse
I'll give it go and let U know.
Thanks
Got such a message:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder and fastboot file(s) created.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
-----------------------------------.
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
How can i connect with Motorola, at the minute is on AP FASTBOOT
This time i paste .img files into Fastboot Commander folder nad gets:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 0x2025.
Radio version: failed.
Main software version: failed.
cid: 7.
cpld: failed.
product: smi.
getvar:mid failed (remote failure).
getvar:security failed (remote failure).
getvar:build-mode failed (remote failure).
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?
On phone i got Getvar build-mode
Fastboot command failed
If you came down those 2 firmware must know that one is ICS (8.7), the other JB (9.8) and if you wanted to install the ICS tending JB you've done a hardbrick, so I recommend you search for the thread "Unbrick for downgrading"
Sorry for my bad English
Enviado desde mi GT-I8190L
---------- Post added at 08:25 AM ---------- Previous post was at 08:20 AM ----------
asgaard76 said:
I'll give it go and let U know.
Thanks
Click to expand...
Click to collapse
You bootloader is locked?
Only make if you have unlocked
Enviado desde mi GT-I8190L
---------- Post added at 08:31 AM ---------- Previous post was at 08:25 AM ----------
Read here for getvar problem
http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company
Enviado desde mi GT-I8190L
jacbarahona72 said:
If you came down those 2 firmware must know that one is ICS (8.7), the other JB (9.8) and if you wanted to install the ICS tending JB you've done a hardbrick, so I recommend you search for the thread "Unbrick for downgrading"
Sorry for my bad English
Enviado desde mi GT-I8190L
---------- Post added at 08:25 AM ---------- Previous post was at 08:20 AM ----------
You bootloader is locked?
Only make if you have unlocked
Enviado desde mi GT-I8190L
---------- Post added at 08:31 AM ---------- Previous post was at 08:25 AM ----------
Read here forma getvar problem
http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company
Enviado desde mi GT-I8190L
Click to expand...
Click to collapse
I don't know if it's unlocked as i bought when it won't pass booting screen
Quick update:
When i tried using Recovery.img through Fastboot commander got such a message (picture)
and on phone mostly gets Fastboot command failed
Invalid image size for partition recovery
asgaard76 said:
I don't know if it's unlocked as i bought when it won't pass booting screen
Quick update:
When i tried using Recovery.img through Fastboot commander got such a message (picture)
and on phone mostly gets Fastboot command failed
Invalid image size for partition recovery
Click to expand...
Click to collapse
SURELY NOT HAVE THE BOOTLOADER UNLOCKED
IMPORTANT
AS YOU AND I flashed HAS MARKED ERROR, YOU MUST CORRECTLY FASTBOOT FLASH FOR SOMETHING AS BOOT IMAGE ( LOGO_SIGNED ) , EXTRACT OF THE SAME FIRMWARE (ZIP )
1 - . DOWNLOAD ONE FASBOOT.EXE OF THE THREADS XDA
2 - . PLACE THE IMAGE FILE ( LOGO_SIGNED ) WITH THE FASTBOOT EXE FILE IN ONE FOLDER IN THE ROOT FOR EXAMPLE C:\ANDROID\ <---- YOU CREATE
3. - OPEN COMMAND WINDOW IN THE FOLDER FILES YOU HAVE MENTIONED IN THE PREVIOUS ITEM
4 - . RAZR I CONNECTED TO PC BY USB CABLE AND BE IN FASTBOOT MODE SCREEN
5 - . INDICATE THE FOLLOWING COMMAND " FASTBOOT FLASH LOGO LOGO_SIGNED "
IF YOU ARE FLASHING OK FOLLOW YOU'VE INDICATED BELOW
CASE 1
1 - . USE A FIRMWARE JB (9.8 )
2 - . DECOMPRESS , EDIT THE FILE WITH EXTENSION XML, and eliminate GETVAR LINES INDICATED IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company)
3 - . USE RSD LITE VERSION 6.14 MINIMUM TO FLASH THE STOCK XML EDITED ( WHICH YOU HAVE CLEARED THE LINES GETVAR )
CASE 2
1 - . UNLOCK YOUR BOOTLOADER
2 - . INSTALLING A CUSTOM RECOVERY VIA FASTBOOT COMMANDER
3. - INSTALL AN " AS CUSTOM ROM OF OMAR AVELAR " IN THE RECOVERY
FOLLOW THE INSTRUCTIONS IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company) IN THIS THREAD AS INDICATED UNLOCK BOOTLOADER ,
ALSO, THE RECOVERY IS TO INSTALL A CUSTOM ROM FOR EXAMPLE OF OMAR AVELAR AND YOU SHOULD HAVE UNLOCKED BOOTLOADER FOR THAT
jacbarahona72 said:
SURELY NOT HAVE THE BOOTLOADER UNLOCKED
IMPORTANT
AS YOU AND I flashed HAS MARKED DEFECTIVE, YOU MUST CORRECTLY FASTBOOT FLASH FOR SOMETHING AS BOOT IMAGE ( LOGO_SIGNED ) , extract SAME FIRMWARE (ZIP )
1 - . DOWNLOAD ONE OF THE THREADS FASBOOT.EXE XDA
2 - . PLACE THE IMAGE FILE ( LOGO_SIGNED ) FASTBOOT WITH THE EXE FILE
3. - OPEN COMMAND WINDOW IN THE FOLDER archvos YOU HAVE MENTIONED IN THE PREVIOUS ITEM
4 - . RAZR I CONNECTED TO PC BY USB CABLE AND BE IN FASTBOOT MODE SCREEN
5 - . INDICATE THE FOLLOWING COMMAND " FASTBOOT FLASH LOGO LOGO_SIGNED "
IF YOU ARE FLASHING OK FOLLOW YOU'VE INDICATED BELOW
CASE 1
1 - . USE A FIRMWARE JB (9.8 )
2 - . DECOMPRESS , EDIT THE FILE WITH EXTENSION XML, and eliminate GETVAR LINES INDICATED IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company)
3 - . USE RSD LITE VERSION 6.14 MINIMUM TO FLASH THE STOCK XML EDITED ( WHICH YOU HAVE CLEARED THE LINES GETVAR )
CASE 2
1 - . UNLOCK YOUR BOOTLOADER
2 - . INSTALLING A CUSTOM RECOVERY VIA FASTBOOT COMMANDER
3. - INSTALL AN " AS CUSTOM ROM OF OMAR AVELAR " FOR RECOVERY
FOLLOW THE INSTRUCTIONS IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company) IN THIS THREAD AS INDICATED UNLOCK BOOTLOADER ,
ALSO, THE RECOVERY IS TO INSTALL A CUSTOM ROM AVELAR AS OF OMAR AND YOU SHOULD HAVE UNLOCKED BOOTLOADER
Click to expand...
Click to collapse
Will give it go and keep U inform. Thanks
Once again:
1. I have to download Fastboot.exe (is it fasboot commander?)
2. Image file (do i have it?? which one is it?)
3. command window?? I'm lost
4.
asgaard76 said:
Will give it go and keep U inform. Thanks
Once again:
1. I have to download Fastboot.exe (is it fasboot commander?)
2. Image file (do i have it?? which one is it?)
3. command window?? I'm lost
4.
Click to expand...
Click to collapse
1. - Fastboot.exe
2. - logo_signed (must be obtained from the firmware, exploring the zip file) NO DOWNLOAD, draw your own "firmware ZIP (CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip <-- for example)"
sorry for my bad English
Donwload files
http://db.tt/tak1LsuU
note: NO DOWNLOAD logo_signed file is of the firmware: Brasil.en.BR (IS "ICS" NO WORK, YOU DAMAGED YOUR PHONE)
Procedure
1. - Put the downloaded files in a folder in the root "C" on your pc, (I call this folder "Android" for example)
2.- Put the phone in fastboot mode (power button and Vol - squeezing them a few seconds until the screen fastboot mode) and connect with USB the phone to pc
3.- Opening a cmd screen, we stand there, I'm in cmd C:\Android\
4. - cheking with command fastboot devices
5. - Performed the command fastboot flash logo logo_signed
6. - Conducted after ending command fastboot reboot and that's it
7.- enjoy
Warning: only share what I see written on a forum and I served, so I do not take responsibility for any damage this may cause to your phone
---------- Post added at 05:14 PM ---------- Previous post was at 04:56 PM ----------
AND YOU CAN NOT COME TO RECOVERY BECAUSE ERASED PARTITION,
AS YOUR PICTURE
WHERE RECEIVED INSTRUCTIONS TO CLEAR YOUR RECOVERY?
NO YOU ACCESS IT, TO RECOVERY BECAUSE YOU HAVE NO
AND YOU MUST FLASH THE STOCK RECOVERY FIRST TO SEE IF YOU ACCESS TO RECOVERY.
ALSO THAT WHAT TO DO WITH FASTBOOT COMMANDER
what was your firmware that you had installed before this happened to you?
As per picture
It looks like image was installed, what next steps should be done?
Yes, that's my fault. I've tried program and thought that it won't make any effects, because i got messages failed, so unfortunately i erase Recovery partition. Is there anything else what we can do?
Thanks
How can i flash stock Recovery and would it help?
jacbarahona72 said:
what was your firmware that you had installed before this happened to you?
Click to expand...
Click to collapse
I don't know as i bought that phone from someone who sell it cheap (already not working) and probably that person have no clue what version/name of Android was it there?
Ok, try this, it has nothing to do with the logo u just flashed
i dunno if u already done this. But we are gonna install the stock recovery again and see what happens. Installing a recovery cant kill your device
If by this methode u cant install the recovery, fastboot gives an error, your bootloader is locked.
1. In this thread, download the 1.6 zip version of the recovery flasher. (the flasher is an automated proces, but we do it manually)
2. Open de zip file and extract the "stock.img" to the folder with the fastboot.exe
3. now, reboot the device in fastboot mode (power and volume down) and linked with usb to your pc obviously
4. use the command "fastboot devices" and u get a list of attached devices. If ur device is one of them we are good.
5. use the command "fastboot flash recovery stock.img" to flash the stock recovery. If it works, your device has an unlocked bootlaoder. If it doesn't its locked.
If it is locked, we go through the next step with rsd lite and install the latest JB 4.1.2 image to your device.
Hazou
Hazou said:
Ok, try this, it has nothing to do with the logo u just flashed
i dunno if u already done this. But we are gonna install the stock recovery again and see what happens. Installing a recovery cant kill your device
If by this methode u cant install the recovery, fastboot gives an error, your bootloader is locked.
1. In this thread, download the 1.6 zip version of the recovery flasher. (the flasher is an automated proces, but we do it manually)
2. Open de zip file and extract the "stock.img" to the folder with the fastboot.exe
3. now, reboot the device in fastboot mode (power and volume down) and linked with usb to your pc obviously
4. use the command "fastboot devices" and u get a list of attached devices. If ur device is one of them we are good.
5. use the command "fastboot flash recovery stock.img" to flash the stock recovery. If it works, your device has an unlocked bootlaoder. If it doesn't its locked.
If it is locked, we go through the next step with rsd lite and install the latest JB 4.1.2 image to your device.
Hazou
Click to expand...
Click to collapse
had to make a correct flash because if you stay with an "incorrect flash", RSD LITE not work, and in many cases say error, reading the context, "directed to make a flash of SOMETHING" and that would be correct, then with RSD LITE flash the firmware and must not indicated error like before.
to the stock recovery you can flash with the same program that he used wrong
I do not have much that I left the Razr I but I've explained what ... . somewhere in all that I have written must match with you Master.
Sorry for my bad English
Enviado desde mi GT-I8190L
jacbarahona72 said:
had to make a correct flash because if you stay with an "incorrect flash", RSD LITE not work, and in many cases say error, reading the context, "directed to make a flash of SOMETHING" and that would be correct, then with RSD LITE flash the firmware and must not indicated error like before.
to the stock recovery you can flash with the same program that he used wrong
I do not have much that I left the Razr I but I've explained what ... . somewhere in all that I have written must match with you Master.
Sorry for my bad English
Enviado desde mi GT-I8190L
Click to expand...
Click to collapse
Don't get me wrong, if I gave you that idea, wasn't my purpose
U did great in presenting a solution for the problem, the only problem is that in my opinion your post wasn't very easy to read for a new guy with a problem. With all the lines/codes that were produces and not set in a container (/code) and with the big red lines that were in the post it wasn't very understandable.
Your English is fine, it is understandable, just the formatting of the post was in my opinion not very good. The solution is good though, maybe with a small sideway, but good.
Just keep it up and help those guys when ever u can. We need those folks like u that help others out!! :thumbsup:
Hazou
Verstuurd van mijn GT-P5110
Hazou said:
Don't get me wrong, if I gave you that idea, wasn't my purpose
U did great in presenting a solution for the problem, the only problem is that in my opinion your post wasn't very easy to read for a new guy with a problem. With all the lines/codes that were produces and not set in a container (/code) and with the big red lines that were in the post it wasn't very understandable.
Your English is fine, it is understandable, just the formatting of the post was in my opinion not very good. The solution is good though, maybe with a small sideway, but good.
Just keep it up and help those guys when ever u can. We need those folks like u that help others out!! :thumbsup:
Hazou
Verstuurd van mijn GT-P5110
Click to expand...
Click to collapse
Will post any update 2night.
OK. Folks short update
Friend of mine who's also on xda forum gave me few tips which i tried, but no luck. Will post them here:
1. CMD: fastboot oem get_unlock_data
fastboot oem get_unlock_data
...
(bootloader) 3A25150915586129#54413233373034
(bootloader) 48354100000000000000000000#1ACF
(bootloader) 4FDA6DCEE30F10CACA1F7FC1CBD39CB
(bootloader) 08BBF#DFF3ABAE76852954D805ED6EF
(bootloader) 3FA0000
OKAY [ 0.290s]
finished. total time: 0.290s
2. fastboot oem unlock PJYERHAJMZMPVYSRKIXN
fastboot oem unlock PJYERHAJMZMPVYSRKIXN
...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 8.390s
In Motorola phone it says
Unlock
Fastboot command failed
He said that partition table is faulty. It can be done only in Linux or JTAG.
Any advice on this?
We tried this as well:
CMD: fastboot format data
(bootloader) Variable not supported!
formatting 'data' partition...
(bootloader) Variable not supported!
FAILED (remote failure)
FAILED (remote failure)
finished. total time: 0.342s
He said that emmc is faulty that's why fastboot won't work.
Had that problem too... it was due to bad Emmc. Sorry for your loss bro.
It could be indeed an emmc problem, in that case a repair at motorola can only fix it, or u will need to replace the motherboard, that will set u back another 150 dollars.
But, u successfully flashed the logo, so a part of the emmc is still working correctly i assume. btw, my knowledge about emmc problems stops here..
The next steps i should take is the following, we will reformat/partition your device, as far as it goes. But I never done this, didn't need to i only know it is possible. Everything that happens now is on your own responsibility!!
1. Download your correct firmware, must be jellybean 4.1.2 from here(firmware)
2. Extract it content in a folder like "STOCKROM"
3. Download new fastboot files from here (mfastboot,xda)
4. Extract the new mfastboot files in the folder "STOCKROM" if u named it like that.
5. Connect your device with your pc, make sure all drivers are correctly installed, and boot in fastboot mode (power + volume down)
6. Flash each of the partitions in sequence using mfastboot (is like fastboot, but can install files larger then 100mb), you need to enter the following commands one-by-one checking that each one returns an [OKAY]. If it doesnt work, i am out of ideas. sry, but report anyway what happend
7.
Code:
mfastboot flash gpt gpt_signed
mfastboot flash motoboot motoboot
mfastboot flash boot boot_signed
mfastboot flash recovery recovery_signed
mfastboot flash motobp motobp
mfastboot flash system system_signed
mfastboot flash cdrom cdrom_signed
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Good luck with it, i will hear from you.
Hazou
btw, erasing 'data' is impossible, fastboot doesn't know 'data', only 'userdata'
Hazou said:
It could be indeed an emmc problem, in that case a repair at motorola can only fix it, or u will need to replace the motherboard, that will set u back another 150 dollars.
But, u successfully flashed the logo, so a part of the emmc is still working correctly i assume. btw, my knowledge about emmc problems stops here..
The next steps i should take is the following, we will reformat/partition your device, as far as it goes. But I never done this, didn't need to i only know it is possible. Everything that happens now is on your own responsibility!!
1. Download your correct firmware, must be jellybean 4.1.2 from here(firmware)
2. Extract it content in a folder like "STOCKROM"
3. Download new fastboot files from here (mfastboot,xda)
4. Extract the new mfastboot files in the folder "STOCKROM" if u named it like that.
5. Connect your device with your pc, make sure all drivers are correctly installed, and boot in fastboot mode (power + volume down)
6. Flash each of the partitions in sequence using mfastboot (is like fastboot, but can install files larger then 100mb), you need to enter the following commands one-by-one checking that each one returns an [OKAY]. If it doesnt work, i am out of ideas. sry, but report anyway what happend
7.
Code:
mfastboot flash gpt gpt_signed
mfastboot flash motoboot motoboot
mfastboot flash boot boot_signed
mfastboot flash recovery recovery_signed
mfastboot flash motobp motobp
mfastboot flash system system_signed
mfastboot flash cdrom cdrom_signed
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Good luck with it, i will hear from you.
Hazou
btw, erasing 'data' is impossible, fastboot doesn't know 'data', only 'userdata'
Click to expand...
Click to collapse
None of them are working. Anyway i was in few repair shops in Dublin and none of them can fixed as they stated Motorola isn't popular in Ireland. Mostly i heard "i have no clue" or "You have to send to manufacturer". One of them tried fixed (it takes roughly 3 hours), but also gave up. He said that it's nearly same story with chip which Samsung S3 had. Don't ask me what does it mean, cuz have no idea. Friend of mine who's also user on that forum will fix it as he stated, but don't know if i gonna send it to Poland. At this stage i have to stop any more tests with Motorola as i don't know what i have to do.
Thanks for all support and will keep You inform if something turn up.
Btw. one of Chinese "call him tech-e" broked back cover of Motorola (beside camera, cracked glass), but i noticed it when i left his repair centre.
Thanks
Okey, best of luck!
Hazou
Verstuurd van mijn XT890