Related
I am trying to flash my bionic because I deleted a system file by accident. However when my phone is in Fastboot, RSD Lite won't recognize it. I have the option to uncompress and flash while my phone is turned on normally but when it gets to the Fastboot mode, RSD Lite says that its a FAIL because it was unable to boot in to Fastboot. Does anyone have any idea what I can do to fix this?
Hi people, I have a big problem with my friend's Razr i, I was trying to root it, but i didn't want to unlock my bootloader so tried several methods but not a single one worked, So i tried the one for unlocked bootloaders and ended up bricking my device, Now It's stuck on fastboot mode.
I've tried to flash some brazilian firmwares via RSD lite, but it get stuck on "6/9 flashing radio_signed" SO PLEASE SOMEONE GUIDE ME TO THE SOLUTION WHAT AM I DOING WRONG?
PS: Also tried to flash an argentinian Firmware but it didn't even let me start flashing bringing the error "Faled flashing process. Unknown fastboot command. (getvar)"
PS2: Also tried the eternityprj Alternate method without RSD, and it gets stuck on flashing recovery... and it also prompts some errors you can see in the attached file.
HELP ME PLEASE AS I SAID THE RAZR IS A FRIEND'S PHONE NOT MINE, I NEED TO SAVE IT.
Vaizen said:
Hi people, I have a big problem with my friend's Razr i, I was trying to root it, but i didn't want to unlock my bootloader so tried several methods but not a single one worked, So i tried the one for unlocked bootloaders and ended up bricking my device, Now It's stuck on fastboot mode.
I've tried to flash some brazilian firmwares via RSD lite, but it get stuck on "6/9 flashing radio_signed" SO PLEASE SOMEONE GUIDE ME TO THE SOLUTION WHAT AM I DOING WRONG?
PS: Also tried to flash an argentinian Firmware but it didn't even let me start flashing bringing the error "Faled flashing process. Unknown fastboot command. (getvar)"
PS2: Also tried the eternityprj Alternate method without RSD, and it gets stuck on flashing recovery... and it also prompts some errors you can see in the attached file.
HELP ME PLEASE AS I SAID THE RAZR IS A FRIEND'S PHONE NOT MINE, I NEED TO SAVE IT.
Click to expand...
Click to collapse
your secure level was to high for a non bootloader method and if you done a method with a unlocked bootloader and your bootloader was locked thats bad.
unlock your bootloader >>WARRANTY VOID<< install cwm and use any backup. or flash the 39 gb fw but i think you have yet to unlokc the bootloader to safe it.. and be patient dont try to much stuff if your battery goes low you need a factory adapter or something like this to charge ur razr i if the battery is down.
regards hope you get it waorking again
I solved my problem this way
Vaizen said:
Hi people, I have a big problem with my friend's Razr i, I was trying to root it, but i didn't want to unlock my bootloader so tried several methods but not a single one worked, So i tried the one for unlocked bootloaders and ended up bricking my device, Now It's stuck on fastboot mode.
I've tried to flash some brazilian firmwares via RSD lite, but it get stuck on "6/9 flashing radio_signed" SO PLEASE SOMEONE GUIDE ME TO THE SOLUTION WHAT AM I DOING WRONG?
PS: Also tried to flash an argentinian Firmware but it didn't even let me start flashing bringing the error "Faled flashing process. Unknown fastboot command. (getvar)"
PS2: Also tried the eternityprj Alternate method without RSD, and it gets stuck on flashing recovery... and it also prompts some errors you can see in the attached file.
HELP ME PLEASE AS I SAID THE RAZR IS A FRIEND'S PHONE NOT MINE, I NEED TO SAVE IT.
Click to expand...
Click to collapse
Hello good morning
I brick 2 phones trying to get one of them and in the process did fail at 2, how the recovery?
1. - Use RSD Lite version 6.1.4
2. - Use 1 extra phone (htc wildfire root and backup CWMR in case of failure)
3. - Use a GB retail rom (CFC_8.7.1I-110_IFW-39_S7_UCASMI01E1017.0R_USASMIICSRTGB_P042_A005_S1FF_fb.xml)
4. - The phone to unbrick, put fastboot mode, switching on via the power button and vol (-) until the fastboot mode screen read "fastboot reason:" if it does not, re-try until there is
5. should not say "fastboot reason: flash failure, or anything else xxxxxx xxxx xxxxx ............"
6. - Boot rsd lite 6.1.4, select retail rom, and indicate that only "unzip" connects your motorola razr I, and it connects back to the other phone (in my case htc wildfire), which has a debug mode enabled.
7. - Note, that in the window of the Rsd Lite in row 1, the Razr I phone is detected, then you start flashing in RSD Lite 6.1.4, see screenshot of your razr I to see that data is being sent, (the other phone should not be affected and only serves as a decoy to usb drivers, Rsd lite at least do not damage to my phone)
8. - Remember flashing erase the card was in your internal Razr I therefore will lose programs, photos or music you had or downloaded to the SD or internal virtual
9. - Flashing can stop and have to do everything again, but remember that no fastboot mode screen should read:
"fastboot reason: flash failure or otherwise else xxxxxx xxxxxxx ......." must be clean that is just:
"fastboot reason: "
luck : Good:
Warning, do not take responsibility for any damage to your cell involved in the process, ......... the lure of the phone can be found on youtube and just suits the way because of my need to get my phone ........ in no way am programmer or software developer, for which only comment what turned out ok to me
excuse my bad English
jacbarahona72 said:
Hello good morning
I brick 2 phones trying to get one of them and in the process did fail at 2, how the recovery?
1. - Use RSD Lite version 6.1.4
2. - Use 1 extra phone (htc wildfire root and backup CWMR in case of failure)
3. - Use a GB retail rom (CFC_8.7.1I-110_IFW-39_S7_UCASMI01E1017.0R_USASMIICSRTGB_P042_A005_S1FF_fb.xml)
4. - The phone to unbrick, put fastboot mode, switching on via the power button and vol (-) until the fastboot mode screen read "fastboot reason:" if it does not, re-try until there is
5. should not say "fastboot reason: flash failure, or anything else xxxxxx xxxx xxxxx ............"
6. - Boot rsd lite 6.1.4, select retail rom, and indicate that only "unzip" connects your motorola razr I, and it connects back to the other phone (in my case htc wildfire), which has a debug mode enabled.
7. - Note, that in the window of the Rsd Lite in row 1, the Razr I phone is detected, then you start flashing in RSD Lite 6.1.4, see screenshot of your razr I to see that data is being sent, (the other phone should not be affected and only serves as a decoy to usb drivers, Rsd lite at least do not damage to my phone)
8. - Remember flashing erase the card was in your internal Razr I therefore will lose programs, photos or music you had or downloaded to the SD or internal virtual
9. - Flashing can stop and have to do everything again, but remember that no fastboot mode screen should read:
"fastboot reason: flash failure or otherwise cuarquier xxxxxx xxxxxxx ......." must be clean that is just:
"fastboot reason: "
luck : Good:
Warning, do not take responsibility for any damage to your cell involved in the process, ......... the lure of the phone can be found on youtube and just suits the way because of my need to get my phone ........ in no way am programmer or software developer, for which only comment what turned out ok to me
excuse my bad English
Click to expand...
Click to collapse
Could PM Me with the instructions in spanish, there are some things that i do not understand in your english
Tried to use your method but RSD lite got stuck on "4/11 erase userdata" and the phone says "program dummy sp block for userdata" I don't thin I understood well the part of the second phone, does it have to be on, i mean normal on, or does it have to be in flashmode aswell?
I have a stock Verizon Moto X (XT1060) that was running 4.4.4. I was on a flight Friday using the phone in airplane mode to run Spotify and Podkicker - noticed the phone was running a little hot so I shut the apps down for a while. Anyway, upon landing I take the phone off airplane mode and the usual minor flood of emails/texts/updates comes in. About 30 seconds after this the phone begins alternately flashing "Process android.process.acore has stopped" and "Process android.process.media has stopped." These cycled for about 5 displays of each, then would disappear for about 45 seconds, then start again. Tried resetting the phone, letting the battery die, no success.
Saturday I tried to navigate into settings to do a factory reset, but the screen froze whenever I tapped on the "backup and reset" menu. Could access all the other menus from settings (until the error cascade started again....). I was able to boot the phone into recovery mode and wiped the cache - nothing. Went back into recovery mode to do a factory reset and now I appear to be stuck in a boot loop - the Moto logo pops up, buzzes, and then does nothing for about a minute or two before trying again. I can get it into recovery mode and tried to wipe the cache and factory reset again, but still nothing.
Any thoughts? Tried looking at other threads but didn't seem to find anything like this. Thanks!
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
hbenz2008 said:
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
Click to expand...
Click to collapse
No luck, unfortunately. Still stuck on the Moto screen. I can force the phone to reset by holding down the power button and then get it into fastboot, my computer recognizes the fastboot device, and the code seems to have run fine. Thanks for the idea - any other thoughts?
If you can still get into fastboot mode you can try flashing only the stock 4.4.4 system.img via mfastboot. That will not wipe your data. If that does not work I would do a full return to stock via mfastboot or you can use rsd.
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
cmcgowan said:
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
Click to expand...
Click to collapse
No, don't need to unlock boot loader to flash the system.img just enable USB debugging in developer options. Tap build number 5 times to enable developer options. If you have never flashed anything before via fastboot rsd might be easier for you.
Thanks - I've used fastboot before on an older phone but never enabled USB debugging on this phone and now can't get to enable it since I'm stuck with this boot loop. Downloading the files from Moto now so will give it a shot tonight anyway. Can't really break it more than it's already broken since all I've got now is a shiny light up paperweight.
You will still need to download the stock images for 4.4.4 for Verizon and extract them. You can flash via rsd or simply flash just the system by running the command "mfastboot flash system system.img"
You will have to have the image file in the same folder as your mfastboot.exe I usually keep all mine in platform tools.
Sigh. Got everything downloaded but when I tried to flash either the boot image, recovery image, or system image, I ran into errors
Here's what displayed (sub boot/recovery for system - same basic error):
c:\{Path}\mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [16.793s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.756s
I was following option 5 from mark @ cdma forum's guide to return motox to stock (can't link b/c I don't have enough posts...) . No issues until I got to the flash boot boot.img step.
I'm assuming this is due to not having USB debugging enabled prior to my phone eating itself, though I'm not sure. Willing to try other things since I love my Moto X but my cheap replacement phone arrives tomorrow (hopefully) so at least its not the end of the world...
You are sure you got the 4.4.4 images? You did not try to downgrade right?
Yup. Definitely got the 4.4.4 images (went back to the Moto site and it will let me download the 4.4.4 immediately but made me request authorization for 4.4.2) and I know I was running the most recent version since I checked for an upgrade on my phone last week in the hope that Moto had released 5.0.
You are following this guide? http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
If USB debugging is not on you can manually boot you device to boot loader mode. Then fastboot or rsd should work fine.
---------- Post added at 11:36 PM ---------- Previous post was at 11:32 PM ----------
Moto X Restore and unbrick for any major US carrier: https://youtu.be/jhhktIkwi7Q
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
cmcgowan said:
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
Click to expand...
Click to collapse
You are opening the cmd screen from the same folder as your images and fastboot and mfastboot.exe correct? From your error it looks like your cmd screen is directed to your "C" drive.
Sorry, just didn't type out the whole thing - the cmd path is to the platform-tools folder where all of the files are also located...
Damn was hoping it was something simply like that. Have you tried rsd?
I haven't - didn't enable USB debugging and for whatever reason the package I downloaded from Moto doesn't include the XML file of instructions. Most of the links from the youtube video and some of the links from the XDA guide earlier are also dead so seems like I'm pretty much out of options. Thanks for all of your help - guess I'm going with the $80 replacement till I'm up for an upgrade!
I was hoping I could get some help with this, I don't have an unlocked bootloader and everything is unfortunately stock, so here's hoping.
I was upgrading with verizon's upgrade tool while plugged into my computer and it got about halfway through updating before just stopping. Now the phone just automatically boots into fastboot flash mode. When I try to select any option aside from power off, restart bootloader, or barcodes it just flashes the motorola logo and goes back to the menu and the log says it failed to validate the system image. I looked at the unbrick thread and got nowhere and when I try to use the fastboot upgrade option with what I believe is the right image it gives me an not found error.
Is there anything I can do or is this just a paperweight now?
EnormousAxe said:
I was hoping I could get some help with this, I don't have an unlocked bootloader and everything is unfortunately stock, so here's hoping.
I was upgrading with verizon's upgrade tool while plugged into my computer and it got about halfway through updating before just stopping. Now the phone just automatically boots into fastboot flash mode. When I try to select any option aside from power off, restart bootloader, or barcodes it just flashes the motorola logo and goes back to the menu and the log says it failed to validate the system image. I looked at the unbrick thread and got nowhere and when I try to use the fastboot upgrade option with what I believe is the right image it gives me an not found error.
Is there anything I can do or is this just a paperweight now?
Click to expand...
Click to collapse
Was anything non-stock on your phone when you tried the update?
I have a bricked device. I think I accidentally flashed boot into abl_a using QFIL.
My device is stuck on the bootloader. I can only access the phone using fastboot command and with EDL mode controlled with QFIL. I tried going to recovery mode and it shows "Your device cannon be checked for corruption" with a yellow warning then reboots into bootloader again. Then I tried accessing download mode using "Power off-Hold vol up-Connect USB" technique and it shows "Your device has failed a routine safety check and will not boot" and reboots back to bootloader. I have my .kdz stock firmware but LGUP won't detect my device since I can't go to download mode.
I have tried these steps:
Booting TWRP using "fastboot boot twrp.img" Output: Failed to load/authenticate error.
Booting TWRP using "fastboot flash boot twrp.img" Output: OK but nothing happened.
Flashing TWRP using "fastboot flash recovery twrp.img" Output: recovery_a no such partitions error.
Flashing ABL V35 Bootloader using "fastboot flash abl abl_35.img" Output: OK but nothing happened.
Booting .kdz file using LGUP but LGUP doesn't detect any device in COM ports though it works using fastboot and adb before.
Downloading the full backup stock ROM and flashing the XML into the phone using QFIL. Output: Fail Firehose and Fail Sahara Error.
Any kind of help would be appreciated.
Many thanks.
Maple06 said:
I have a bricked device. I think I accidentally flashed boot into abl_a using QFIL.
My device is stuck on the bootloader. I can only access the phone using fastboot command and with EDL mode controlled with QFIL. I tried going to recovery mode and it shows "Your device cannon be checked for corruption" with a yellow warning then reboots into bootloader again. Then I tried accessing download mode using "Power off-Hold vol up-Connect USB" technique and it shows "Your device has failed a routine safety check and will not boot" and reboots back to bootloader. I have my .kdz stock firmware but LGUP won't detect my device since I can't go to download mode.
I have tried these steps:
Booting TWRP using "fastboot boot twrp.img" Output: Failed to load/authenticate error.
Booting TWRP using "fastboot flash boot twrp.img" Output: OK but nothing happened.
Flashing TWRP using "fastboot flash recovery twrp.img" Output: recovery_a no such partitions error.
Flashing ABL V35 Bootloader using "fastboot flash abl abl_35.img" Output: OK but nothing happened.
Booting .kdz file using LGUP but LGUP doesn't detect any device in COM ports though it works using fastboot and adb before.
Downloading the full backup stock ROM and flashing the XML into the phone using QFIL. Output: Fail Firehose and Fail Sahara Error.
Any kind of help would be appreciated.
Many thanks.
Click to expand...
Click to collapse
you need to get lgup working again with the device, for that I believe you need abl, laf, boot and dtbo. so get those from the kdz and flash using qfil, then you should be able to go directly to download (lgup) mode and flash kdz.
AsItLies said:
you need to get lgup working again with the device, for that I believe you need abl, laf, boot and dtbo. so get those from the kdz and flash using qfil, then you should be able to go directly to download (lgup) mode and flash kdz.
Click to expand...
Click to collapse
Hi, thanks for the reply,
I just extracted my .kdz file using LG Firmware Extract but I don't seem to find any abl, laf, boot, nor dtbo img files. I only got LGUPc.dll, LGUPc.dylib, and V409N30f00user-signed-ARB0OPE with no file extension. I tried extracting only the file with no file extension but I'm not sure what to do with the file.
Many thanks.
Maple06 said:
Hi, thanks for the reply,
I just extracted my .kdz file using LG Firmware Extract but I don't seem to find any abl, laf, boot, nor dtbo img files. I only got LGUPc.dll, LGUPc.dylib, and V409N30f00user-signed-ARB0OPE with no file extension. I tried extracting only the file with no file extension but I'm not sure what to do with the file.
Many thanks.
Click to expand...
Click to collapse
Follow this link. They are for kor 20n, so be sure once you flash with qfil, go directly to DL mode, don't try to boot the device. Follow directions in Notes.
Also, it would be wise to save off whats in those partitions first, even though it won't boot. At least that way, if you absolutely had to, you could get back to where you are now.
cheers
AsItLies said:
Follow this link. They are for kor 20n, so be sure once you flash with qfil, go directly to DL mode, don't try to boot the device. Follow directions in Notes.
Also, it would be wise to save off whats in those partitions first, even though it won't boot. At least that way, if you absolutely had to, you could get back to where you are now.
cheers
Click to expand...
Click to collapse
I just finished flashing those files, then I tried going to download mode, it gave me the yellow warning and boots back to the bootloader. I don't see many changes except when I start there is no yellow warning appearing, only when I try to go to recovery mode it still shows the yellow warning. Maybe there is something I did wrong?
Edit: I tried going to DL mode again and it actually goes to DL mode for 1 second and goes back to bootloader.
Thanks in advance.
Maple06 said:
I just finished flashing those files, then I tried going to download mode, it gave me the yellow warning and boots back to the bootloader. I don't see many changes except when I start there is no yellow warning appearing, only when I try to go to recovery mode it still shows the yellow warning. Maybe there is something I did wrong?
Edit: I tried going to DL mode again and it actually goes to DL mode for 1 second and goes back to bootloader.
Thanks in advance.
Click to expand...
Click to collapse
did you flash all four files to both slots? as notes indicate?
remember, after flashing in qfil, we need to hold both pwr and vol down to get out of edl mode. Once you hear the windows chime, indicating the device is disconnected, immediately let go of pwr and vol dwn and just hold vol up. Keep device connected with usb cable. Also be sure to use a usb 2 port, not usb 3. A usb 3 port can result in corrupted files as it's too fast for old qfil sftwre.
AsItLies said:
did you flash all four files to both slots? as notes indicate?
remember, after flashing in qfil, we need to hold both pwr and vol down to get out of edl mode. Once you hear the windows chime, indicating the device is disconnected, immediately let go of pwr and vol dwn and just hold vol up. Keep device connected with usb cable. Also be sure to use a usb 2 port, not usb 3. A usb 3 port can result in corrupted files as it's too fast for old qfil sftwre.
Click to expand...
Click to collapse
I just reflashed all of them and enter the download mode and it works! Now I can access LGUP and when I try to start flashing my .kdz file it failed but I'm now trying redownloading the .kdz file with KDZ downloader. Just in case that .kdz really need a special download. I'll update when my .kdz is finished downloaded and if the flash is successful or not. In the meantime, do you have any sources for the LG V40 LM-V409N .kdz file version? It'll be very useful in case this file failed.
Thank you very much
Hi, I am here with the update.
So I managed to download the .kdz file for the LM-V409N it rebooted and booted for a minute and it restarted then looped from "erasing" rainbow circle then goes to back stuck on LG with a light animation until I hold the power button and it rebooted back to the rainbow erasing circle. So I just put and redo everything and now I got it back on download mode.
I think that I just have a bad/corrupted .kdz file. Do you have a suggestion on where should I find the files? I tried from lg-roms but it's bad firmware. I'll try more firmware for KOR, LGT, and SKT.
Edit: Hmm, I seem to be stuck on either the LG or LGU+ symbol, I'm not sure what to do.
Edit: Apparently, my phone still got the issue that it restarts randomly. I have no idea how to fix it now since the issue still persists after several different phone stock ROM.
Many thanks.
Maple06 said:
Hi, I am here with the update.
So I managed to download the .kdz file for the LM-V409N it rebooted and booted for a minute and it restarted then looped from "erasing" rainbow circle then goes to back stuck on LG with a light animation until I hold the power button and it rebooted back to the rainbow erasing circle. So I just put and redo everything and now I got it back on download mode.
I think that I just have a bad/corrupted .kdz file. Do you have a suggestion on where should I find the files? I tried from lg-roms but it's bad firmware. I'll try more firmware for KOR, LGT, and SKT.
Edit: Hmm, I seem to be stuck on either the LG or LGU+ symbol, I'm not sure what to do,
Many thanks.
Click to expand...
Click to collapse
I'd suggest to get them here: https://lg-firmwares.com/lg-lmv409n-firmwares/
It's important to the md5 checksum to match against the hash they give you when you select a specific kdz. Then you know it's not corrupt.
after unbrick how to get IMEI? I have no backup. using V409N korean model.
AsItLies said:
I'd suggest to get them here: https://lg-firmwares.com/lg-lmv409n-firmwares/
It's important to the md5 checksum to match against the hash they give you when you select a specific kdz. Then you know it's not corrupt.
Click to expand...
Click to collapse
Thank you for your answer. It would've been working now if I didn't get unlucky on the device. You're really helpful to help from my hard-bricked phone into firmware booted.
Again, thank you very much
irfan64672 said:
after unbrick how to get IMEI? I have no backup. using V409N korean model.
Click to expand...
Click to collapse
If you unbricked your device with the stock firmware, just go to telephone and call *#06# and you got your imei. Best to backup your firmware with QFIL.