Hi man, i have a problem.... Let's start: i had a eu moto x (xt1052) with fr firmware, moto is stock, so locked bootloader, stock recover and no root, i had received the ota to 4.4.4 but it cause me some connectivity problem, i have done the full wipe but i didnt solve; so i try to flash again the ota file but the installation fail and when i try to restart i had a bootloop (moto remain to the M screen).
i'm able to open recovery, to charge it and pc see it; how can i solve?
i also try to use rsd but there is no 4.4.4 firmware and i cant flash 4.4.2 (downgrade)
Need more details.
Since the OTA ZIp usually erases itself from the phone after successful install, how did you try and re-install it? Where did you get it from? When you say it failed, exactly what do you mean? (did you get an error? of so, what did it say?)
And you are right... DO NOT TRY AND DOWNGRADE!! Once you have 4.4.4. on there, stick with 4.4.4 or you risk bricking or setting yourself up to brick.
Since you can get into stock recovery, try and wipe data and cache from in there. Does the phone still bootloop?
ok, so it was an ota zip that someone in the italian's forum use, when i try to flash it it fail after some passage and show something like impossible rename the file? or similar.
i have try to do wipe data and wipe cache from recovery but it's the same.
how can i solve?
i try to do a fastboot erase cache and a fastboot erase data.
the first said:
(bootloader) variable not supported!
erasing 'cache'...
okay and after the seconds
with the second
(bootloader) variable not supported!
erasing 'data'...
(bootloader) invalid partition name data
FAILED (remote failure)
finished
so?
daniele1992 said:
i try to do a fastboot erase cache and a fastboot erase data.
the first said:
(bootloader) variable not supported!
erasing 'cache'...
okay and after the seconds
with the second
(bootloader) variable not supported!
erasing 'data'...
(bootloader) invalid partition name data
FAILED (remote failure)
finished
so?
Click to expand...
Click to collapse
The partition isn't named "data", it's "userdata"
Try again with the correct command:
fastboot erase userdata
no error here but i have the same bootloop
daniele1992 said:
no error here but i have the same bootloop
Click to expand...
Click to collapse
Hmmm ok. There is only ONE safe way to fix you back up. It won't be the easiest thing in the world to do since you will have to have someone on the EXACT SAME variant help you with this.
Re-flash TWRP. You'll need to find someone on the exact same XT1052 firmware (who also has TWRP) make a backup of JUST system and boot (not userdata).
They will share the backup with you, and you will flash it using TWRP (restore). That should fix you up -- it is the ONLY safe way to get back on track without downgrading and risking a brick..
hard to find but i will try, other question if i flash the new 4.4.4 firmware (when it will be relased) will i solve?
daniele1992 said:
hard to find but i will try, other question if i flash the new 4.4.4 firmware (when it will be relased) will i solve?
Click to expand...
Click to collapse
Almost certainly. Hopefully the full SBF/FXZ (Full XML Zip) for your specific variant is released very soon. Good Luck with it. :good:
samwathegreat said:
Hmmm ok. There is only ONE safe way to fix you back up. It won't be the easiest thing in the world to do since you will have to have someone on the EXACT SAME variant help you with this.
Re-flash TWRP. You'll need to find someone on the exact same XT1052 firmware (who also has TWRP) make a backup of JUST system and boot (not userdata).
They will share the backup with you, and you will flash it using TWRP (restore). That should fix you up -- it is the ONLY safe way to get back on track without downgrading and risking a brick..
Click to expand...
Click to collapse
Can anyone please help me with TWRP "backup of JUST system and boot" for XT1052 with stock 4.4.4 OTA (212.44.26.en.03)?
Related
I have a Google Play Edition (the real deal from Google, not flashed from something else) was on 4.3, was trying to upgrade to 4.4 using the OTA upgrade. I'm now in a boot loop. I'm *think* my issue is related to SuperSU v.1.8: http://forum.xda-developers.com/showthread.php?p=47868582
I was on Rooted 4.3 with SuperSU 1.8 running properly. Got the OTA message to upgrade. Flashed my Recovery Image back to 4.3 stock from this image: http://forum.xda-developers.com/showthread.php?t=2358781 in the 4.3 RUU Zip.
Ran the OTA update, everything seemed to install correctly.
I can still get into the Bootloader, Fastboot, and Recovery.
On regular boot I get to the select your language screen and then the phone reboots. Just guessing that something is happening between S-On and SuperSU that is causing problems. I've tried a couple older versions of SuperSU pushed with adb in CW and have the same problem.
If anyone have a link to a stock system.img I could flash for 4.3 or 4.4 that would solve all my problems. The system.img I thought I had for 4.3 out of the 4.3 RUU Zip is too large, as is the 4.4 RUU Zip.
Thanks in advance for the help - please be gentle if I'm violating an unknown procedure. I've searched an this for a few hours and haven't been able to find anything that might help me.
Thanks,
Matt
I've upgraded 3 phones so far (all converts, not real GPE) that had super SU installed and not had this issue.
if your seeing select language it means either 1. you wiped data before the OTA? or 2. something went wrong when converting your data.
It's doubtful but possible that anything is wrong with /system. The update script checks for specific versions of files and would have error ed rather than patched a mismatch. Lets start by wiping data and cache.
fastboot erase userdata
fastboot erase cache
fastboot reboot
since your S-On you can't use the RUU's and I'm pretty sure those system.img files are not signed; they are just dumps in img format so even if they weren't too big they still wouldn't work.
mthomas1262 said:
I have a Google Play Edition (the real deal from Google, not flashed from something else) was on 4.3, was trying to upgrade to 4.4 using the OTA upgrade. I'm now in a boot loop. I'm *think* my issue is related to SuperSU v.1.8: http://forum.xda-developers.com/showthread.php?p=47868582
I was on Rooted 4.3 with SuperSU 1.8 running properly. Got the OTA message to upgrade. Flashed my Recovery Image back to 4.3 stock from this image: http://forum.xda-developers.com/showthread.php?t=2358781 in the 4.3 RUU Zip.
Ran the OTA update, everything seemed to install correctly.
I can still get into the Bootloader, Fastboot, and Recovery.
On regular boot I get to the select your language screen and then the phone reboots. Just guessing that something is happening between S-On and SuperSU that is causing problems. I've tried a couple older versions of SuperSU pushed with adb in CW and have the same problem.
If anyone have a link to a stock system.img I could flash for 4.3 or 4.4 that would solve all my problems. The system.img I thought I had for 4.3 out of the 4.3 RUU Zip is too large, as is the 4.4 RUU Zip.
Thanks in advance for the help - please be gentle if I'm violating an unknown procedure. I've searched an this for a few hours and haven't been able to find anything that might help me.
Thanks,
Matt
Click to expand...
Click to collapse
ipfreelytech said:
I've upgraded 3 phones so far (all converts, not real GPE) that had super SU installed and not had this issue.
if your seeing select language it means either 1. you wiped data before the OTA? or 2. something went wrong when converting your data.
It's doubtful but possible that anything is wrong with /system. The update script checks for specific versions of files and would have error ed rather than patched a mismatch. Lets start by wiping data and cache.
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Thanks so much for the reply.
I did wiped AFTER installing the OTA as part of my troubleshooting. I did it through CWM recovery and regular recovery to see if it made any difference. I can do it again through fastboot if you think that will have any affect. Thanks again for the reply, appreciate it.
dunno about stock recovery but CWM doesn't actually do a proper wipe. it leaves /data/media intact. fastboot erase will rewrite the file-system.
mthomas1262 said:
Thanks so much for the reply.
I did wiped AFTER installing the OTA as part of my troubleshooting. I did it through CWM recovery and regular recovery to see if it made any difference. I can do it again through fastboot if you think that will have any affect. Thanks again for the reply, appreciate it.
Click to expand...
Click to collapse
ipfreelytech said:
dunno about stock recovery but CWM doesn't actually do a proper wipe. it leaves /data/media intact. fastboot erase will rewrite the file-system.
Click to expand...
Click to collapse
get the error "FAILED (remote: not allowed)" when I attempt to erase and format user data
I think I'm ready to just push a stock backup nandroid on to the device - any recommendations as to which I should use?
sorry. I didn't realize the one blocks that command. I use it all the time on other devices.
I actually made a stock 4.4 nandroid last night that I'll upload soon. I haven't seen any untainted GPE nandroids posted. with a clean nandroid and the firmware.zip from the ota you should be pretty much the same as running an RUU.
mthomas1262 said:
get the error "FAILED (remote: not allowed)" when I attempt to erase and format user data
I think I'm ready to just push a stock backup nandroid on to the device - any recommendations as to which I should use?
Click to expand...
Click to collapse
ipfreelytech said:
sorry. I didn't realize the one blocks that command. I use it all the time on other devices.
I actually made a stock 4.4 nandroid last night that I'll upload soon. I haven't seen any untainted GPE nandroids posted. with a clean nandroid and the firmware.zip from the ota you should be pretty much the same as running an RUU.
Click to expand...
Click to collapse
That would be awesome. If you don't mind sharing the link when you do I'd appreciate it.
Cheers
Here you go:
https://mega.co.nz/#!TMlgWLDJ!ZfFlcxcRkebpb3cciULnlTf4GMJfy4grwOLi-Ied3Tg
extract the zip, then copy the folder to your recovery's backup location. I made it with CWM.
If your using CWM you can use the command adb push 2013-11-28.07.23.56 /data/media/clockworkmod/backup/GPE/
then restore it from the menu
Here's a link to the untouched firmware.zip from the OTA:
https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
flash that zip from fastboot.
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 firmware.zip
fastboot reboot
should be good to go then. You'll have stock /system and stock recovery so future OTA should work.
mthomas1262 said:
That would be awesome. If you don't mind sharing the link when you do I'd appreciate it.
Cheers
Click to expand...
Click to collapse
I'm hoping this will also work for my situation as I am stuck. I purchased a pre-owned GPE HTC One. The previous owner re-loaded JB stock but left clockwork mod on there. Last night I discovered the stock recovery image and loaded that successfully (wanting a stock experience now). This morning the phone successfully upgraded to the most recent jelly bean. Soon after that upgrade kitkat was ready for download.
As soon as the install finished the phone was stuck in a boot loop. I have tried numerous things to get it to stop but i have been unsuccessful. It appears that it is S-On, which I believe is also adding to my issues. Do you think the situation and nandroid you posted above will work in my situation (total stock recovery and no superSU)?
Thank you!
s-on is not the problem unless the previous owner lied and that's a converted phone and not a legit GPE.
I assume you've done a factory reset from recovery or bootloader?
Feel to try flashing CWM then restoring my nandroid and then flashing the firmware.
The_Doctor_Who said:
I'm hoping this will also work for my situation as I am stuck. I purchased a pre-owned GPE HTC One. The previous owner re-loaded JB stock but left clockwork mod on there. I wanted a totally stock experience. Last night I discovered the stock recovery image and loaded that successfully. This morning the phone successfully upgraded to the most recent jelly bean. Soon after that upgrade kitkat was ready for download.
As soon as the install finished the phone was stuck in a boot loop. I have tried numerous things to get it to stop but i have been unsuccessful. It appears that it is S-On, which I believe is also adding to my issues. Do you think the situation and nandroid you posted above will work in my situation (total stock recovery and no superSU)?
Thank you!
Click to expand...
Click to collapse
ipfreelytech said:
s-on is not the problem unless the previous owner lied and that's a converted phone and not a legit GPE.
I assume you've done a factory reset from recovery or bootloader?
Feel to try flashing CWM then restoring my nandroid and then flashing the firmware.
Click to expand...
Click to collapse
It did come in the GPE box, so I hope he didn't go that much out of the way to lie! lol It is the official GPE.
I did do a factory reset with no luck.
I have tried using the RUU files I found on another thread to flash through fastboot but I get a failed 99 error.
When I attempt to find device with adb, it does not list a device ( I assume b/c of debugging), but finds fine the phone fine on fastboot device.
Also, I thought about reflashing to CWM but when I try to bring up the bootloader after flashing the CWM recovery nothing will come up at as far as a recovery and will just begin to boot the phone.
Thank for any help you may offer and I apologize in advance for my noob questions. I've flashed recoveries and ROMs on the past on other devices but this one has me stumped.
there is no legit RUU for GPE! The conversion RUU only works with s-off because it is not properly signed!
flash this CWM: http://flyhalf205.com/recoveries/recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
after flashing fastboot erase cache
select reboot bootloader on your phone. then select recovery.
then continue with restoring my nandroid and then flashing the firmware in RUU mode.
The_Doctor_Who said:
It did come in the GPE box, so I hope he didn't go that much out of the way to lie!
I did do a factory reset with no luck.
I have tried using the RUU files I found on another thread to flash through fastboot but I get a failed 99 error.
When I attempt to find device with adb, it does not list a device ( I assume b/c of debugging), but finds fine the phone fine on fastboot device.
Also, I thought about reflashing to CWM but when I try to bring up the bootloader after flashing the CWM recovery nothing will come up at as far as a recovery and will just begin to boot the phone.
Thank for any help you may offer and I apologize in advance for my noob questions. I've flashed recoveries and ROMs on the past on other devices but this one has me stumped.
Click to expand...
Click to collapse
looking great - enjoying me some kit-kat right now! thanks a ton!
Awesome. So I take it my nandroid plus the firmware zip worked for you?
mthomas1262 said:
looking great - enjoying me some kit-kat right now! thanks a ton!
Click to expand...
Click to collapse
ipfreelytech said:
Awesome. So I take it my nandroid plus the firmware zip worked for you?
Click to expand...
Click to collapse
The nandroid worked great - not sure what you wanted me to do with the firmware.zip, I *think* the link to the firmware.zip was the same as the nandroid link. Let me know if I'm missing something. Just need to install SuperSU and then I can restore everything from Titanium.
Again, thanks a ton!
That's what I get for listening to other NOOBs when it comes to this. I did as suggested below re: CWM
here are my command lines
c:\And>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8746 KB)...
OKAY [ 1.185s]
writing 'recovery'...
OKAY [ 0.674s]
finished. total time: 1.861s
c:\And> fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.056s]
finished. total time: 0.056s
When I reboot the bootloader and select recovery it reboots and starts the loop over again. that's where I was stuck. I figured if I could load another ROM I'd at least be okay, but I can't get the darn recovery to work.
Ok - at least I know what my issue was before. I attempted to install SuperSU.zip 1.8, installs fine, but when I go into regular boot get boot looping again. Looks like I'll need to wait for an update to SuperSU.zip - if someone with authority can post in the SuperSU thread that might be really helpful.
Thanks!
good eye. I have fixed the link. here's the right one: https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
The purpose of the firmware.zip is to get all your firmware on the correct version as well as writing the stock recovery so that future OTA will work without issue [assuming of course you don't screw with /system by deleting apk you don't use or editing files].
you flash it using fastboot after rebooting to ruu mode. re-read my post.
I think you have a bad super su installer. I've installed super su 1.8 on three ones so far all running the 4.4 GPE and not had issue; however those were all converts and are s-off so that may have something to do with it. However it doesn't make a ton of sense.
mthomas1262 said:
The nandroid worked great - not sure what you wanted me to do with the firmware.zip, I *think* the link to the firmware.zip was the same as the nandroid link. Let me know if I'm missing something. Just need to install SuperSU and then I can restore everything from Titanium.
Again, thanks a ton!
Click to expand...
Click to collapse
---------- Post added at 11:28 AM ---------- Previous post was at 11:22 AM ----------
fastboot getvar all
paste the results here with imei and serial redacted.
The_Doctor_Who said:
That's what I get for listening to other NOOBs when it comes to this. I did as suggested below re: CWM
here are my command lines
c:\And>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8746 KB)...
OKAY [ 1.185s]
writing 'recovery'...
OKAY [ 0.674s]
finished. total time: 1.861s
c:\And> fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.056s]
finished. total time: 0.056s
When I reboot the bootloader and select recovery it reboots and starts the loop over again. that's where I was stuck. I figured if I could load another ROM I'd at least be okay, but I can't get the darn recovery to work.
Click to expand...
Click to collapse
I greatly appreciate the help (and apologize for stepping on the toes of the OP).
c:\And>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.056s
ipfreelytech said:
I think you have a bad super su installer. I've installed super su 1.8 on three ones so far all running the 4.4 GPE and not had issue; however those were all converts and are s-off so that may have something to do with it. However it doesn't make a ton of sense.
Click to expand...
Click to collapse
I got the installer from:
download (dot) chainfire (dot) eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
(can't post URLs yet)
I haven't tried to get s-off, on on the 1.54 version so that makes things a little harder, I've seen some posts about it.
Hi XDA guys, so i have this trouble and i don't know what to do, the problem is that my phone get bricked after updating whatsapp and now i can only boot the phone into fastboot an when i try to unlock the bootlader i get this, so help me please!!
Code:
(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.603s
Victor Gtz said:
Hi XDA guys, so i have this trouble and i don't know what to do, the problem is that my phone get bricked after updating whatsapp... [/CODE]
Click to expand...
Click to collapse
Hi, maybe you could give us some more clear infos of what you have done exactly...
Why you want to unlock your bootloader?
Try to reflash an original firmware with RDS and if you want root use "TwerkMyMoto"...
5m00v3 said:
Hi, maybe you could give us some more clear infos of what you have done exactly...
Why you want to unlock your bootloader?
Try to reflash an original firmware with RDS and if you want root use "TwerkMyMoto"...
Click to expand...
Click to collapse
Well mi phone was working fine with stock firmware and locked bootlader, so i recive this whatsapp update and after this installation the phone shut down and get on again but with the boot logo of motorola and get stuck in it, and if i enter in fastboot non of the options work only the phone gets frized, so i was triyin to unlock the bootloader, for a chance to fix the problem with an update via RSD, but when i try to unlock the bootlader it gives me the error as i mention in the first post and i dont know what do
Victor Gtz said:
...so i was triyin to unlock the bootloader, for a chance to fix the problem with an update via RSD...
Click to expand...
Click to collapse
you dont need to unlock the bootloader to reflash your original firmware via RSD-Lite!
Follow this to install stock rom: http://forum.xda-developers.com/showthread.php?t=2643779
I got yesterday also an Update-Information from whatsapp. I will NOT install until it is confirmed as non-bricking. Thx for your info/warning!
5m00v3 said:
you dont need to unlock the bootloader to reflash your original firmware via RSD-Lite!
Follow this to install stock rom: http://forum.xda-developers.com/showthread.php?t=2643779
I got yesterday also an Update-Information from whatsapp. I will NOT install until it is confirmed as non-bricking. Thx for your info/warning!
Click to expand...
Click to collapse
i Just try using RDS Lite but in the step 4 the reboot never boot and the flash fail
Can you enter recovery? Selecting it in the fastboot menu, what happens? In RSD does it flashes and only in the reboot portion it fails? Did you try to turn it on without the external SD card?
As far as i can tell the device is trying to use the linux discard command, it seems like a wipe that gone wrong.
regnotp synagogue
thiagomtl said:
Can you enter recovery? Selecting it in the fastboot menu, what happens? In RSD does it flashes and only in the reboot portion it fails? Did you try to turn it on without the external SD card?
As far as i can tell the device is trying to use the linux discard command, it seems like a wipe that gone wrong.
Click to expand...
Click to collapse
Hi thiagomtl let me answer your questions, when i try to enter in recovery the phone gets stuck again with the motorola boot logo and after a while returns to fastboot mode, and when i try to flash whit RSD in the step 4 that is reboot, on the phone stays a command that says Rebooting Droidboot and nothing happens, and yeah when i do this operaions i always remove the sim card and the sd card , so if you now something ill appreciate a lot it!!
Try those in fastboot:
fastboot erase data
fastboot erase cache
After try RSD again.
5m00v3 said:
you dont need to unlock the bootloader to reflash your original firmware via RSD-Lite!
Follow this to install stock rom: http://forum.xda-developers.com/showthread.php?t=2643779
Click to expand...
Click to collapse
Are you sure about that ?
For original firmware there is no need to unlock
thiagomtl said:
Try those in fastboot:
fastboot erase data
fastboot erase cache
After try RSD again.
Click to expand...
Click to collapse
I already do that but im still getting this error
BLKDISCARD ioctl /dev/block/mmcblk0 fail
I am guessing that is an error in the emmc, the problem is that i don't know how to fix it
Victor, I'm having the exact same problem. Did you find any solution?
I'm having the exact same problem!!
What I did was that when it gets stuck waiting for reboot I did reboot it manually into fastboot mode again and process continues. The problem is that it gets stuck again when flashing the system partition. Bootloader won't let me erase the partition nor flash it.
Tried unlocking the bootloader and:
(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: 9.666s
Is there a way to know the original provider of the phone, to make sure I'm using the correct firmware?
ismael_mj23 said:
I'm having the exact same problem!!
What I did was that when it gets stuck waiting for reboot I did reboot it manually into fastboot mode again and process continues. The problem is that it gets stuck again when flashing the system partition. Bootloader won't let me erase the partition nor flash it.
Tried unlocking the bootloader and:
(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: 9.666s
Is there a way to know the original provider of the phone, to make sure I'm using the correct firmware?
Click to expand...
Click to collapse
You got a serious bug. There is a huge change your device is now broken beyond repair, i hope not. But can u access the recovery partition? Can u flash a custom boot image?
Hazou said:
You got a serious bug. There is a huge change your device is now broken beyond repair, i hope not. But can u access the recovery partition? Can u flash a custom boot image?
Click to expand...
Click to collapse
I also having the same problem after force power on/off when hang during TWRP format. Now the unit in hard brick. If able to force temporary boot into recovery using ram instead of rom, might have some hope. But it looks like no way to boot from ram. :crying:
same prob as victor gtz
fsd lite freezes at step 4, unlock bootloader doesnt work and so on and so forth, so anybody got a clue what to do?
Dudes
Same problem here, rsdlite didnt work for me and the bootloader cant be unlocked with the same error message. Theres any way to solve this? i read once that you can recover the android from the dead even if the boot isnt working, maybe thats not true at all.....
Neyzik said:
Dudes
Same problem here, rsdlite didnt work for me and the bootloader cant be unlocked with the same error message. Theres any way to solve this? i read once that you can recover the android from the dead even if the boot isnt working, maybe thats not true at all.....
Click to expand...
Click to collapse
It's true, but not for all devices. And if u have the above, the nand memory is broken. That can only be repaired by some kind of powercycle on chip level or anything.
Right.
So, I was opening youtube on the last version of CM 12.1. No xposed, stock kernel, XT1068 model, when all of a sudden the phone stopped working.
Youtube wasn't opening. The phone was stuck on the home screen, all I could do was just press the home/back/recent buttons. Even long pressing power button to reboot would just take me to the power menu but Wouldn't allow me to do anything.
So in the end I long pressed the power menu to force reboot the phone aaaand... stuck on the boot logo. Not on the bootanimation, on the Motorola Bootlogo.
Managed to get to fastboot mode, tried to go to recovery, but after the twrp splash screen It would reboot to the splash screen again.
So i decided to mfastboot the original firmware. Who knows? maybe something got corrupted on cm.
Now, mfastboot is giving me weird errors.
flash partition gpt.bin gives (bootloader) Preflash validation failed
flash motoboot motoboot.bin gives FAILED (data transfer failure (Unknown error))
flash boot boot.img freezes everything and i need to reboot it to try and get to fastboot again.
Anybody knows what I should do? I'm kinda desperate here...
Thanks in advance. Peace.
(by the way, latest motorola drivers, just so you know...)
EDIT. Also, on the phone, it says
"hab check failed for primary_gpt
Failed to verify hab image primary_gpt"
Hope I can help
Are you flashing a gpt.bin from a previous android version? You cannot downgrade gpt.bin or motoboot.bin so the error is normal. From what firmware version is the boot.img you are flashing from? Try downloading this twrp recovery img from here https://dl.twrp.me/titan and
Code:
fastboot flash recovery recovery.img
or
Code:
mfastboot flash recovery recovery.img
Then you can try flashing any rom like this AOSP one http://forum.xda-developers.com/moto-g-2014/development/rom-android-source-project-t3123109
Hope this helps. I understand how hard it is to have a phone that won't boot.
Maybe you should try to place the stock rom 4.4.4 and then upgrade to 5.0, with 4.4.4 rom the GPT will have a downgrade and then you update the GPT putting 5.0
LudwigFerdinand18 said:
Maybe you should try to place the stock rom 4.4.4 and then upgrade to 5.0, with 4.4.4 rom the GPT will have a downgrade and then you update the GPT putting 5.0
Click to expand...
Click to collapse
You cannot downgrade gpt
Well I somehow managed to reboot into recovery, but the great problem here is that it won't mount \data.
Now, maybe all I need is to reformat \data cause it got corrupted, but since TWRP won't mount it, I can't do much about it.
I found on another thread this command
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Which apparently formats the data partition of a phone. I suppose I'd have to change "ext4fs" into "f2fs", but I'm too scared to actually try it out.
Also because I don't know whether mmcblk0p8 is the right block for our data partition.
Jeez, I hate this.
Thanks for your help guys, but I don't think flashing recovery again would help. Nor downgrading, but I'll think about it.
EDIT.
Magic, just magic. After hours of tinkering I did EXACTLY THE SAME THINGS and now it's working. Restored the stock Rom and I'm off to install CM again.
Sorry guys and thanks so much!!!
Long story short, woke up with my N6 stuck at the bootloader screen and cannot do anything at it. I can only see my serial number and if I try anything else, it reloads bootloader. I am trying to flash back to a stock 6.0.1 image, however I keep getting this error while trying to do so.
C:\Program Files (x86)\Android\android-sdk\platform-tools> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.332s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 11.542s
I have tried Nexus Root Toolkit, tried flashing all and tried flashing each image one by one but I still get this "(bootloader) Failed to flash partition FAILED (remote failure)" on all attempts. Phone does show up if I try fastboot devices, and I have tried this on two different computers. Device is also unlocked as well, and I even tried flashing older versions of Lolipop but they all give me the same error. Drivers work fine, and I have everything up to date in terms of bootloader and Andriod SDK. I am starting to think that there is physical damage inside the phone, however I do not know how or why this occurred randomly. Any help would be awesome, as I am very new to flashing images onto my phone and frankly I am 99% sure that my warranty is out, and I really don't want to pay $175 cost .
You can try to use minimal adb and fastboot drivers, unpack for example latest npreview 5 factory Image into same folder and flash each .IMG step by step with cmd window, i always flash this way, if everything else fails.
http://forum.xda-developers.com/showthread.php?t=2317790
And here method 2:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
May this helps you
coremania said:
You can try to use minimal adb and fastboot drivers, unpack for example latest npreview 5 factory Image into same folder and flash each .IMG step by step with cmd window, i always flash this way, if everything else fails.
http://forum.xda-developers.com/showthread.php?t=2317790
And here method 2:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
May this helps you
Click to expand...
Click to collapse
I've already tried method 2 before so I tried method 1 with the program, and it gives me the same exact error as before. Thanks for the help though, it was worth a shot!
Are you able to enter twrp ? Try to reflash Bootloader through twrp
coremania said:
Are you able to enter twrp ? Try to reflash Bootloader through twrp
Click to expand...
Click to collapse
I did not have TWRP installed on my phone since I had it completely stock and unrooted, so I tried installing it in the hopes of that some chance it would work and I could access it. Still getting the same error as before (grumble grumble). It is starting to look like more of a physical problem to me, but thanks for the advice. Here is what I got...
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11585 KB)...
OKAY [ 0.468s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 6.380s
Bootloader is unlocked i guess, may your Bootloader is messed up, did you try to flash only one Factory Image ? Corrupt Download possible ?
What happens if you try unlock command
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
blanco2701 said:
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
Click to expand...
Click to collapse
This was going to be my suggestion!!
Sent from my Nexus 6 using XDA-Developers mobile app
coremania said:
Bootloader is unlocked i guess, may your Bootloader is messed up, did you try to flash only one Factory Image ? Corrupt Download possible ?
What happens if you try unlock command
Click to expand...
Click to collapse
Any image I even try to flash I get the error with, no matter what order or which one I pick. I redownloaded the image again and still nothing, so I don't think it's a corrupt download. What is the unlock command? Sorry for being a noob, never heard of it since all my knowledge is from reading tons of flashing guides on the internet lol.
blanco2701 said:
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
Click to expand...
Click to collapse
Alright, I downloaded the OTA file and got the process to about 47% when suddenly I keep running into the error of "E:Can't open /cache/recovery/log" then followed by more things it can't open. I tried the OTA twice and it gets stuck on that same exact spot. I tried the wipe data/factory reset option from the recovery mode and I get a similar error of "Can't mount", "Can't open", "failed to mount" the recovery log. It seems like there is a problem with the recovery log files (or the folder) on my phone, but I have no idea what that means. I will mess around with some more and try Googling the source of error, but thank you for the help.
fastboot oem unlock
With this command you can unlock your Bootloader, better read here
first http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 , if have 47% done, may you can use twrp now. Good luck
Did you try the erase function from bootloader that may or may not help??
Sent from my Nexus 6 using XDA-Developers mobile app
coremania said:
fastboot oem unlock
With this command you can unlock your Bootloader, better read here
first http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 , if have 47% done, may you can use twrp now. Good luck
Click to expand...
Click to collapse
Oh yes, my device has already been unlocked from the start so that wasn't a problem. I still get the same error when I try to flash anything, including TWRP which means I have to install the OTA. The problem is a get a separate error when I try to install the OTA, which the only solution being to flash my device (or at least that is what most people have been saying when I googled the can't open cache recovery error) so this is a giant goose chase which leads me back to the start :/. I will keep trying however, I refuse to give up after going this far!
holeindalip said:
Did you try the erase function from bootloader that may or may not help??
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Should I try fastboot erase cache and then fastboot format cache? Would refresh the cache on there? I only just learned the erase command so I am not exactly sure what I should try.
Should be able to erase any partition if your unlocked
http://androidforums.com/threads/list-of-fastboot-command.714676/
Sent from my Nexus 6 using XDA-Developers mobile app
I don't know the commands to erase everything from the bootloader but I would try this:
Flash latest twrp and boot into recovery.
Assuming you don't care about anything that's on the phone, go to advance wipe and wipe EVERYTHING lol... reboot into bootloader and try to flash everything from scratch. If this doesn't work, I'll guess your phone have problems.
holeindalip said:
Should be able to erase any partition if your unlocked
http://androidforums.com/threads/list-of-fastboot-command.714676/
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I get the same failure error while trying to format and erase, so I am guessing something is really wrong with my phone or the bootloader is messed up beyond repair. I guess it could be the cable I am using as well, that is one thing I did not take into factor so I will try with another cable if I find a spare. Flashing might be beyond my solution at this rate though... Thanks anyways for the help.
blanco2701 said:
I don't know the commands to erase everything from the bootloader but I would try this:
Flash latest twrp and boot into recovery.
Assuming you don't care about anything that's on the phone, go to advance wipe and wipe EVERYTHING lol... reboot into bootloader and try to flash everything from scratch. If this doesn't work, I'll guess your phone have problems.
Click to expand...
Click to collapse
I really should have had TWRP installed before I guess lol, but I still get the same failure error. My phone has more problems than a teenager going through puberty I swear, thanks for the help though.
Yes try another cable, if it stops at 47%, the Bootloader should be replaced. May try everything without simcard, don't ask me why, i read something similiar in a Moto forum
fastboot erase recovery doesn't help ?
---------- Post added at 19:58 ---------- Previous post was at 19:34 ----------
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660 otherwise try this, but read completely first, adb sideload with a npreview ota rom may help you.
coremania said:
Yes try another cable, if it stops at 47%, the Bootloader should be replaced. May try everything without simcard, don't ask me why, i read something similiar in a Moto forum
fastboot erase recovery doesn't help ?
---------- Post added at 19:58 ---------- Previous post was at 19:34 ----------
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660 otherwise try this, but read completely first, adb sideload with a npreview ota rom may help you.
Click to expand...
Click to collapse
I tried it with another wire and nothing changed, and then I tried taking out my sim card and trying it.... and it worked! It flashed everything normally and loaded up just fine. I don't know whether I should be furious or happy but thank you and everyone who helped. Who would have known just taking out the sim card could have saved me 2+ days of stressing and trail and error. Once again thanks, you really saved me lol.
You're welcome, nice your phone works again !
Don't forget to activate oem unlock and debugging in the Developer options, and flash twrp, so maybe more save for upcoming problems
skipsoft android toolkit maybe help you in future
Soft bricked when trying to flash stock 5.1 back from CM13. Somehow managed to wipe the entire phone and now all I have access to are fastboot and TWRP recovery. I have no ROM ZIPs to access in TWRP since internal storage was wiped. I tried ADB sideload but says it can't mount /data/. My computer recognises the phone as a fastboot device but not as an ADB device.
Is there any coming back from this?
I've downloaded the retail GB stock image file for XT1052 but I can't flash the partition as I just get error 'update gpt_main version failed' 'preflash validation failed for GPT'
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I've downloaded the RetGB for 5.1 for XT1052 from here: https://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1052/
But it seems to be missing a number of key files that are described in option 5 of the link you posted. Am I missing something? I'm also still getting errors each time I try to flash the partition except now CMD is just showing:
"target max-download-size: 768MB error: cannot load 'gpt.bin': no error. Any ideas? Thanks.
My only other thought at this point is to try and flash a ROM in recovery using USB-OTG. Could that work? For example, if I download stock ROM or even the CM 14 I had on previously before everything got wiped and put that on an external drive and flashed in TWRP?
varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I just moved cmd.exe into my platform tools folder where everything else is and tried again to flash the partition. Instead this time I get:
C:\Android-SDK\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.335s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.328s
And then on the phone itself in the fastboot screen it shows:
"downgraded security version. update gpt_main version failed. preflash verification failed for GPT'. I thought this would mean the bootloader I'm trying to flash would represent a downgrade but I checked against the info.txt file in the recovery image zip and it says 30.BE which matches the 30.BE in my fastboot screen...
OK I've now got an OS. Managed to reinstall CM14 using usb-otg. Figured that was the safest bet given it was the last OS installed.
Problem I now have is that I can't get any service (I could previously on CM14 before all this happened). Is it possible that when I managed to completely wipe the phone that I would the relevant modem/radio files?
Thanks
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Sent from my XT1060 Dev Ed
varunpilankar said:
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Click to expand...
Click to collapse
That doesn't have my version - xt1052.
Would this be to return my mobile service? I've got back on CM14 but all my IMEI and sim data has wiped so I can't get service. Not sure if I need to use the 5.1 factory image I have and just flash modem files. Seen elsewhere that I could try
Fastboot flash modem NON-hlos.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Would that do the trick do you reckon?
Take a nandroid backup & try doing it!
There is also a 5.1 stock zip Rom & try that too, might be helpful.
Sent from my XT1060 Dev Ed
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
hachamacha said:
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
Click to expand...
Click to collapse
Thanks. Will give that a look as I would like to know how to easily go back to stock in the event of catastrophe - I've been trying to flash back using both fastboot and TWRP but it fails every time due to 'downgrade security' etc. even though I know I'm using the same bootloader as in the stock ROM.
I managed to get my IMEI and service back by flashing
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
I've now got Resurrection Remix on as I thought I'd see if that would fix my service issues (it didn't - so still had to do the steps above). But have managed to learn a lot over the past few days to bring my phone back from death! I'm mainly used to Sony phones so this has been an experience.