[Q] M7 Set_metadata_recursive - One (M7) Q&A, Help & Troubleshooting

Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I try to flash any custom rom (the one I want is viperone 5.8.0) the entire process goes smoothly until the last step of the installation where i get the error "set_metadata_recursive:some changes failed" I have searched around a lot but am unable to find anything
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Thanks in advance for any response!!!!!!
*EDIT*
FIXED problem turned out to be the wrong TWRP for the phone, was using TWRP 2.7.0.0 and 2.7.0.4 the correct version for the verizon phone is here http://crackflasher.com/openrecovery-twrp-2-7-0-1-m7wlv-img-htc-one-verizon-openrecovery/ rom flashes working now!!!!!

PblicEnemy said:
Whenever I try to flash any custom rom (the one I want is viperone 5.8.0) the entire process goes smoothly until the last step of the installation where i get the error "set_metadata_recursive:some changes failed" I have searched around a lot but am unable to find anything
Click to expand...
Click to collapse
First, I would try formatting (not wiping) your /system partition right before the install. If that fails, try following the advice in this thread, which sounds like a dead ringer for your problem:
http://forum.xda-developers.com/showthread.php?t=2532300
Note: Please post whether formatting /system is successful, so others can see the fact in their search results.

fenstre said:
First, I would try formatting (not wiping) your /system partition right before the install. If that fails, try following the advice in this thread, which sounds like a dead ringer for your problem:
http://forum.xda-developers.com/showthread.php?t=2532300
Note: Please post whether formatting /system is successful, so others can see the fact in their search results.
Click to expand...
Click to collapse
Hello, and thanks for the response, do you know of any guides to formatting my /system partition, and will this mean risking the backup i have saved through TWRP? Also I saw that thread that you posted earlier while researching but I don't understand if it is for my phone or compatible with the rom I'm trying to flash.

PblicEnemy said:
Hello, and thanks for the response, do you know of any guides to formatting my /system partition, and will this mean risking the backup i have saved through TWRP? Also I saw that thread that you posted earlier while researching but I don't understand if it is for my phone or compatible with the rom I'm trying to flash.
Click to expand...
Click to collapse
I believe it's an option under the advanced section of "wipe" in TWRP. And this won't risk your backups, because they're stored on another partition. Don't wipe or format anything except /system. And the file recommended in that article isn't likely to cause harm--I believe it's just a helper for how to perform the commands that are needed to install a ROM (for example, delete the files "system/*"). It's more likely to not work than to harm your phone, and there's no way it could install a ROM correctly, then prevent that ROM from running.

fenstre said:
I believe it's an option under the advanced section of "wipe" in TWRP. And this won't risk your backups, because they're stored on another partition. Don't wipe or format anything except /system. And the file recommended in that article isn't likely to cause harm--I believe it's just a helper for how to perform the commands that are needed to install a ROM (for example, delete the files "system/*"). It's more likely to not work than to harm your phone, and there's no way it could install a ROM correctly, then prevent that ROM from running.
Click to expand...
Click to collapse
Okay I believe I am doing something wrong because I downloaded the .zip file for that binary update that was mentioned in that thread. I extracted the file and also extracted the Rom file, I put the new binary into the extracted rom and removed the old one, then i re-zipped the new rom file, however the phone will no longer install, it doesn't even make it to the install screen. Is this because it needs to be recompiled after I change the binary update? If so how do I go about compiling?

PblicEnemy said:
Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I try to flash any custom rom (the one I want is viperone 5.8.0) the entire process goes smoothly until the last step of the installation where i get the error "set_metadata_recursive:some changes failed" I have searched around a lot but am unable to find anything
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Thanks in advance for any response!!!!!!
Click to expand...
Click to collapse
PblicEnemy said:
Okay I believe I am doing something wrong because I downloaded the .zip file for that binary update that was mentioned in that thread. I extracted the file and also extracted the Rom file, I put the new binary into the extracted rom and removed the old one, then i re-zipped the new rom file, however the phone will no longer install, it doesn't even make it to the install screen. Is this because it needs to be recompiled after I change the binary update? If so how do I go about compiling?
Click to expand...
Click to collapse
BRICK ALERT: A word of CAUTION!! are you using m7_u/ul recoveries, from the version numbers sound like m7_u/ul versions... you have m7_wlv so you need to flash a recovery compatible with that phone!

nkk71 said:
BRICK ALERT: A word of CAUTION!! are you using m7_u/ul recoveries, from the version numbers sound like m7_u/ul versions... you have m7_wlv so you need to flash a recovery compatible with that phone!
Click to expand...
Click to collapse
Someone sent me M7vzw-twrp_2.7.0.4b-santod_recovery, and that is the one I am using at the moment, is that wrong?

nkk71 said:
BRICK ALERT: A word of CAUTION!! are you using m7_u/ul recoveries, from the version numbers sound like m7_u/ul versions... you have m7_wlv so you need to flash a recovery compatible with that phone!
Click to expand...
Click to collapse
Sorry for double post, but you pointed out the solution and the phone is working correctly!

PblicEnemy said:
Sorry for double post, but you pointed out the solution and the phone is working correctly!
Click to expand...
Click to collapse
well hope all is well now, and also make sure to flash ROMs which are compatible!
most users (including myself are on m7_u/ul) and this could be easily overlooked...
Good luck and enjoy

Related

O2 ruu 1.206.17.1

Hello,
Anyone can provide me this official rom?
Sent from my Lumia 920 using Board Express
Problem solved :good:
zeka1974 said:
Problem solved :good:
Click to expand...
Click to collapse
You might wanna post the solution to help others that might be searching and an answer...
Of course
The problem was that I only had unlocked bootloader.
Forgot to root the phone in order to install other roms.
Today with more time checked a few forums and see the missing actions.
Installed TWRP 2.5.0.0 and after that installed Superuser.
after all that is done just paste the ROM (European Unbranded) to the phone; entered bootloader mode, recovery, wipe all data and after that install this rom.
All went fine for now.
Sounds like you just installed a rom zip in recovery and not actually flash an RUU.
A RUU, or Rom Update Utility, is a self extracting stock software package, a lot of times including complete images (with radio, etc) that wipe data or patches.

Help, I need somebody! (Serious problems restoring original firmware)

Hey guys,
I'm really sorry to bother everyone but I just spent 10 hours straight trying to get my HTC One back to its original state.
I'm really frustrated as I have tried 15 different tutorials and have about 1 million tabs open right now.
- I tried the whole re-locking thing and tried flashing a RUU (tried so many different ones but always some signature error. And with exe's I should get the right utility because it's the wrong bootloader). I don't even know what's the right one. Here's the getvar version-main I get: 1.29.401.12
- I somehow wiped everything and can't even get my phone as an external flash drive.
- I read I should have S Off whatever that is, but for that I needed to re-flash a rom. I can't even get that to work anymore. I tried to sideload it. It worked...but there's nothing on the phone except an ever turning cyanogenmod wheel.
- I took a pic of my bootloader screen, maybe you guys can decipher what there's to be done.
https://www.dropbox.com/s/p013md5fog7t4vn/2013-11-14%2017.34.07.jpg
Any help is SO appreciated! x/
Please go easy on me and speak english...not code lol
I know my way around googling the hell out of things but this is obviously my limit^^
ycianca said:
Hey guys,
I'm really sorry to bother everyone but I just spent 10 hours straight trying to get my HTC One back to its original state.
I'm really frustrated as I have tried 15 different tutorials and have about 1 million tabs open right now.
- I tried the whole re-locking thing and tried flashing a RUU (tried so many different ones but always some signature error. And with exe's I should get the right utility because it's the wrong bootloader). I don't even know what's the right one. Here's the getvar version-main I get: 1.29.401.12
- I somehow wiped everything and can't even get my phone as an external flash drive.
- I read I should have S Off whatever that is, but for that I needed to re-flash a rom. I can't even get that to work anymore. I tried to sideload it. It worked...but there's nothing on the phone except an ever turning cyanogenmod wheel.
- I took a pic of my bootloader screen, maybe you guys can decipher what there's to be done.
https://www.dropbox.com/s/p013md5fog7t4vn/2013-11-14%2017.34.07.jpg
Any help is SO appreciated! x/
Please go easy on me and speak english...not code lol
I know my way around googling the hell out of things but this is obviously my limit^^
Click to expand...
Click to collapse
Okay, your hboot is 1.44 (April 2013), so you should be able to achieve S-Off using revone.
can you please post a "fastboot getvar all" (remove IMEI and serialno), and confirm your bootloader is unlocked
sure, here you go:
https://dl.dropboxusercontent.com/u/56231439/Untitled-1.jpg
nkk71 said:
Okay, your hboot is 1.44 (April 2013), so you should be able to achieve S-Off using revone.
can you please post a "fastboot getvar all" (remove IMEI and serialno), and confirm your bootloader is unlocked
Click to expand...
Click to collapse
as for the unlocked bootloader, i guess it's unlocked as it says unlocked in pink on the picture
ycianca said:
as for the unlocked bootloader, i guess it's unlocked as it says unlocked in pink on the picture
Click to expand...
Click to collapse
my bad, i'll get back to you in a little while.....
---------- Post added at 08:48 PM ---------- Previous post was at 08:07 PM ----------
ycianca said:
as for the unlocked bootloader, i guess it's unlocked as it says unlocked in pink on the picture
Click to expand...
Click to collapse
Sorry for having to rewind a little, but can you let me know your goal?
1- hboot -> OK
2- getvar -> OK
3- you can achieve S-Off using revone with a Sense 5 / Android 4.1.2 based ROM
I need to go now, and may not be back till Saturday, in the meantime, if you need to get you phone up & running just use: http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/ (unselect "stock recovery" during installer) or any other custom ROM out there.
If you think I've helped, hit the thanks button,
and please explain where you want to end up.
nkk71 said:
my bad, i'll get back to you in a little while.....
---------- Post added at 08:48 PM ---------- Previous post was at 08:07 PM ----------
Sorry for having to rewind a little, but can you let me know your goal?
1- hboot -> OK
2- getvar -> OK
3- you can achieve S-Off using revone with a Sense 5 / Android 4.1.2 based ROM
I need to go now, and may not be back till Saturday, in the meantime, if you need to get you phone up & running just use: http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/ (unselect "stock recovery" during installer) or any other custom ROM out there.
If you think I've helped, hit the thanks button,
and please explain where you want to end up.
Click to expand...
Click to collapse
my goal, as stated in my initial post and title, is to get my original phone back (firmware and stuff). i had cm on it, now there's nothing on it except a "useless" fastboot and recovery. i just wish to get my original phone back so i can re-sell it.
ycianca said:
my goal, as stated in my initial post and title, is to get my original phone back (firmware and stuff). i had cm on it, now there's nothing on it except a "useless" fastboot and recovery. i just wish to get my original phone back so i can re-sell it.
Click to expand...
Click to collapse
i just downloaded that zip and now i have absolutely no clue what to do...
Ah I think I know what your problem is ... 1.29.401.12 doesnt have a full RUU file anywhere ... can u tell me the filename you tried running (RUU exe?) ..
So what you need is ...
1. TWRP/CWM Recovery installed and working
2. TWRP/CWM Backup ROM file for 1.29.401.12
I could only google and find CWM backup for your ROM so you need to flash CWM recovery first (I assume you know how)
Download your ROM backup from here -> http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__102-1-29-401-12-2013-05-16-zip/
adb push this to your sdcard and use restore option from CWM... also best if you wipe data/factory reset first since you had CM on it
v-b-n said:
Ah I think I know what your problem is ... 1.29.401.12 doesnt have a full RUU file anywhere ... can u tell me the filename you tried running (RUU exe?) ..
So what you need is ...
1. TWRP/CWM Recovery installed and working
2. TWRP/CWM Backup ROM file for 1.29.401.12
I could only google and find CWM backup for your ROM so you need to flash CWM recovery first (I assume you know how)
Download your ROM backup from here -> http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__102-1-29-401-12-2013-05-16-zip/
adb push this to your sdcard and use restore option from CWM... also best if you wipe data/factory reset first since you had CM on it
Click to expand...
Click to collapse
thanks i will try that. do i need to re-lock it first?
ycianca said:
thanks i will try that. do i need to re-lock it first?
Click to expand...
Click to collapse
No need to relock
i don't know how adb push works. i tried following a tutorial but it says to mount sdcard which i don't have. i only have system, data and cache.
i then re-locked, then tried to flash via fastboot oem reboot and flash zip.
that didn't work because of "signature verify fail".
i'd love to try adb push, if you could be so nice to tell me how i'd have to proceed.
It would be easier if you download a Custom ROM and then in CWM choose Install -> Sideload
And then from PC , adb sideload yourfile.zip
This should load the Custom ROM ... it will be easier to transfer and manage the nandroid backup files once the OS is loaded
v-b-n said:
It would be easier if you download a Custom ROM and then in CWM choose Install -> Sideload
And then from PC , adb sideload yourfile.zip
This should load the Custom ROM ... it will be easier to transfer and manage the nandroid backup files once the OS is loaded
Click to expand...
Click to collapse
yes i tried that but it does not work. and i don't get why.
1. i sideloaded a cm stable file.
2. the file had been renamed sideload.zip
3. i started the install and it said successful.
4. when i boot the phone, the cm wheel turns and turns infinitely.
5. i tried a different rom (infection), it said succesful install, i re-booted but that darned cm wheel was still there turning and turning thinking "you like that huh?"
If you have nothing to save on sdcard , this is what I would do ...
1. Wipe System
2. Wipe Cache
3. Wipe Data
4. Wipe INternal Storage
And CWM Sideload should start the flashing immediately after transferring the zip file unless u r doing it some wrong way
---------- Post added at 05:03 PM ---------- Previous post was at 04:58 PM ----------
Here's another way ..
Download this -> http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Sideload it and follow on screen steps
to save us some time. would you be open for a quick chat session with screen sharing?
we could resolve this in 5 minutes like that.
tell me what you think, thanks!
ycianca said:
to save us some time. would you be open for a quick chat session with screen sharing?
we could resolve this in 5 minutes like that.
tell me what you think, thanks!
Click to expand...
Click to collapse
nevermind! it seriously finally worked.
- i had some issues on the way with guru reset but it finally worked.
i couldn't sideload it it said something about too many emulators...
i sideloaded it via a toolkit and it worked. guru reset gave me another version number than the getvar thought. strange isn't it?
anyways...thanks a lot for helping me out!
ycianca said:
nevermind! it seriously finally worked.
- i had some issues on the way with guru reset but it finally worked.
i couldn't sideload it it said something about too many emulators...
i sideloaded it via a toolkit and it worked. guru reset gave me another version number than the getvar thought. strange isn't it?
anyways...thanks a lot for helping me out!
Click to expand...
Click to collapse
getvar shows your firmware version, settings -> about shows you the ROM version

[SOLVED] Epic frustration!!! Problems with ROM installation. Everything else seems OK

Tearing my hair out a little with this one.
Out of the box my phone was a UK GSM HTC One, which I gather is the 'm7' when I'm in this company
I've unlocked the handset with the HTC Developer unlock instructions
I've installed ClockworkMod recovery 6.0.4.8 (as per the note on CyanogenMod site, re new partition structure)
I've rooted with SuperSU.zip
I've not got S-OFF (I'm unclear as to the value of going that far; although I have done with previous phones)
I can get to the bootloader fine; I can switch to fastboot; I can issue fastboot commands; I can get to recovery and do all the recovery stuff; I can issue adb sideloads
What I DON'T seem to be able to do, is install any ROM other than cm-11-20140504-SNAPSHOT-M6-m7.zip . Any other ROM I try (later CM snapshots; Android Revolution HD; deodexed Stock ROM (from Android Rev site)), all give me installation errors....
I get the errors if I;
- Try a CM update from within CM in the Settings/Updates menus
- Reboot to recovery and do a zip install from recovery (zip previously downloaded to phone)
- ADB sideload from recovery
Can ANYONE think of anything I'm not doing; or that I'm doing incorrectly, that might be causing this?
It's driving me nuts!
OpusLefteye said:
Tearing my hair out a little with this one.
Out of the box my phone was a UK GSM HTC One, which I gather is the 'm7' when I'm in this company
I've unlocked the handset with the HTC Developer unlock instructions
I've installed ClockworkMod recovery 6.0.4.8 (as per the note on CyanogenMod site, re new partition structure)
I've rooted with SuperSU.zip
I've not got S-OFF (I'm unclear as to the value of going that far; although I have done with previous phones)
I can get to the bootloader fine; I can switch to fastboot; I can issue fastboot commands; I can get to recovery and do all the recovery stuff; I can issue adb sideloads
What I DON'T seem to be able to do, is install any ROM other than cm-11-20140504-SNAPSHOT-M6-m7.zip . Any other ROM I try (later CM snapshots; Android Revolution HD; deodexed Stock ROM (from Android Rev site)), all give me installation errors....
I get the errors if I;
- Try a CM update from within CM in the Settings/Updates menus
- Reboot to recovery and do a zip install from recovery (zip previously downloaded to phone)
- ADB sideload from recovery
Can ANYONE think of anything I'm not doing; or that I'm doing incorrectly, that might be causing this?
It's driving me nuts!
Click to expand...
Click to collapse
Flash TWRP recovery, version 2.6.3.3, not the latest via fastboot and enjoy
Can't think of a good sig
donkeykong1 said:
Flash TWRP recovery, version 2.6.3.3, not the latest via fastboot and enjoy
Can't think of a good sig
Click to expand...
Click to collapse
For my own satisfaction; why not the latest TWRP?
Thanks though. That sounds like a pretty decisive answer!
Also. For future reference, was the way I laid out my question clear and should I include any other details?
OpusLefteye said:
For my own satisfaction; why not the latest TWRP?
Thanks though. That sounds like a pretty decisive answer!
Also. For future reference, was the way I laid out my question clear and should I include any other details?
Click to expand...
Click to collapse
Latest TWRP has some problems with flashing kitkat ROMs.Version 2.6.3.3 is proven to work with every ROM out there. The best thing to do if you have a problem with your phone is to explain your issue as short as possible and post fastboot getvar all. Your post was fine, but for future reference, and let's hope you won't need it, fastboot getvar all is a great help
Can't think of a good sig
donkeykong1 said:
Latest TWRP has some problems with flashing kitkat ROMs.Version 2.6.3.3 is proven to work with every ROM out there. The best thing to do if you have a problem with your phone is to explain your issue as short as possible and post fastboot getvar all. Your post was fine, but for future reference, and let's hope you won't need it, fastboot getvar all is a great help
Can't think of a good sig
Click to expand...
Click to collapse
UPDATE - Latest CM11 snapshot in and running nicely Thanks donkeykong1
OpusLefteye said:
UPDATE - Latest CM11 snapshot in and running nicely Thanks donkeykong1
Click to expand...
Click to collapse
You're welcome [emoji106]
Can't think of a good sig

So... this is what happened when I tried to updrade to 4.4.3

It's already rooted/unlocked bootloader but, I did everything alright and this is what happened.
can someone help me get if fixed ? thanks
obs: it didn't brick or anything.. just fails when I try to upgrade.
This is what's written:
Updating partition details...
Installing '/sdcard/Blur_Version.212.44.22.ghost
checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of motorola/gh
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/Blur_Version.212.44.
Updating partition details...
FAILED.
Home​Wipe cache/dalvik​ Robot System​
Liooh said:
It's already rooted/unlocked bootloader but, I did everything alright and this is what happened.
can someone help me get if fixed ? thanks
obs: it didn't brick or anything.. just fails when I try to upgrade.
This is what's written:
Updating partition details...
Installing '/sdcard/Blur_Version.212.44.22.ghost
checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of motorola/gh
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/Blur_Version.212.44.
Updating partition details...
FAILED.
Home​Wipe cache/dalvik​ Robot System​
Click to expand...
Click to collapse
Sorry, I didn't mark the Q question.
Liooh said:
Sorry, I didn't mark the Q question.
Click to expand...
Click to collapse
Are you sure of the file your attempting to use.? Maybe you have an FXZ zip file, and you would need to flash with RSDLite or adb..not TWRP..double check what you are attempting..
Also..make sure you are using the correct file for your device..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
Are you sure of the file your attempting to use.? Maybe you have an FXZ zip file, and you would need to flash with RSDLite or adb..not TWRP..double check what you are attempting..
Also..make sure you are using the correct file for your device..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
Click to expand...
Click to collapse
I've wondered that too but I'm using the one that was recommended. The one with the Lite I already did and it proceeded well.
Do you know where I can find more files like that then ? (not firmwares)
Liooh said:
I've wondered that too but I'm using the one that was recommended. The one with the Lite I already did and it proceeded well.
Do you know where I can find more files like that then ? (not firmwares)
Click to expand...
Click to collapse
OMGoodness.. I'm not really sure Sir..I have a XT1060 DEV..but I haven't kept up with the Moto X lately (in the past month)..So..I'm not really the one to help you with newer versions..Are you sure 4.4.3 is right for your device.?
I'd suggest do research in here (XDA) and know what is the latest..I'm assuming that you are trying to flash an OTA..but if you have a file someone has "ported" or something of that nature..go back to where you downloaded the file and research..
Even if you have an OTA zip..I'd suggest maybe know the file more, maybe it should be unzipped and run an XML file..I honestly am not familiar with the file you are attempting to use..
Maybe post a link to where you found the file and myself and others can go look at what file and its purpose..then maybe we can assist you more..Sorry I can't help you more at this time..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
OMGoodness.. I'm not really sure Sir..I have a XT1060 DEV..but I haven't kept up with the Moto X lately (in the past month)..So..I'm not really the one to help you with newer versions..Are you sure 4.4.3 is right for your device.?
I'd suggest do research in here (XDA) and know what is the latest..I'm assuming that you are trying to flash an OTA..but if you have a file someone has "ported" or something of that nature..go back to where you downloaded the file and research..
Even if you have an OTA zip..I'd suggest maybe know the file more, maybe it should be unzipped and run an XML file..I honestly am not familiar with the file you are attempting to use..
Maybe post a link to where you found the file and myself and others can go look at what file and its purpose..then maybe we can assist you more..Sorry I can't help you more at this time..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
Click to expand...
Click to collapse
It was an youtube video, his device is the same as mine XT1058, his device went perfectly.
Liooh said:
It was an youtube video, his device is the same as mine XT1058, his device went perfectly.
Click to expand...
Click to collapse
Oh..OK..maybe contact that one to help you..go back to the video and post a comment/question..maybe someone there can help..
Also maybe post a link here..and we can go look ourselves and maybe help you.?
Also..make sure you have a good download..not corrupted..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
Whatever you are trying to flash can't be flashed with twrp so there's problem number one...
Sent from my XT1060
Liooh said:
It's already rooted/unlocked bootloader but, I did everything alright and this is what happened.
can someone help me get if fixed ? thanks
obs: it didn't brick or anything.. just fails when I try to upgrade.
This is what's written:
Updating partition details...
Installing '/sdcard/Blur_Version.212.44.22.ghost
checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of motorola/gh
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/Blur_Version.212.44.
Updating partition details...
FAILED.
Home​Wipe cache/dalvik​ Robot System​
Click to expand...
Click to collapse
Yep, @rocketsaucev2 is right. You appear to be attempting to flash the update.zip from custom recovery. It is well documented that you must have STOCK recovery in order to flash an official update.zip
samwathegreat said:
Yep, @rocketsaucev2 is right. You appear to be attempting to flash the update.zip from custom recovery. It is well documented that you must have STOCK recovery in order to flash an official update.zip
Click to expand...
Click to collapse
It's already STOCK.
Isn't the 4.4.2 you're talking about ?
Liooh said:
It's already STOCK.
Isn't the 4.4.2 you're talking about ?
Click to expand...
Click to collapse
No, it isn't. The screenshots you uploaded CLEARLY show custom recovery. You need to flash stock recovery back before you can take any updates.
If you don't know the difference between stock and custom recovery, you aren't ready to update. You need to Read, Read, Read....
This would be a good start: http://mark.cdmaforums.com/MotoX-OTA.html (Thanks @KidJoe for the well-written documentation)
samwathegreat said:
No, it isn't. The screenshots you uploaded CLEARLY show custom recovery. You need to flash stock recovery back before you can take any updates.
If you don't know the difference between stock and custom recovery, you aren't ready to update. You need to Read, Read, Read....
This would be a good start: http://mark.cdmaforums.com/MotoX-OTA.html (Thanks @KidJoe for the well-written documentation)
Click to expand...
Click to collapse
Hi friend..
Yes I did everything.
Here me explaining everything: http://forum.xda-developers.com/and...ns-problem-t2810890/post54034992#post54034992
Liooh said:
Hi friend..
Yes I did everything.
Here me explaining everything: http://forum.xda-developers.com/and...ns-problem-t2810890/post54034992#post54034992
Click to expand...
Click to collapse
I'm trying really hard to explain it to you but you just aren't getting it....
This is what you wrote in the post you linked:
1- Return to STOCK(Mine is 4.4.2) But I did stock it to 4.4.2. OK!
2- Install the TWRP to install the SuperSU. OK, Everything's fine.
3- After it, my dev is already rooted.
OK, look at step number 2: YOU INSTALLED TWRP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
When you flashed TWRP, you REPLACED stock recovery with custom recovery (TWRP).
As I've been trying to make you understand, OTAs will -----ONLY----- install if you have STOCK RECOVERY.
You will need to flash stock recovery BACK (replacing TWRP), THEN you can accept the update!!!!
Afterwards, you can flash TWRP back.
This is well documented everywhere.....you will have to do this EVERYTIME a new OTA comes out.
You can NOT accept an OTA if you have TWRP installed.
Do you understand now?
samwathegreat said:
I'm trying really hard to explain it to you but you just aren't getting it....
This is what you wrote in the post you linked:
1- Return to STOCK(Mine is 4.4.2) But I did stock it to 4.4.2. OK!
2- Install the TWRP to install the SuperSU. OK, Everything's fine.
3- After it, my dev is already rooted.
OK, look at step number 2: YOU INSTALLED TWRP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
When you flashed TWRP, you REPLACED stock recovery with custom recovery (TWRP).
As I've been trying to make you understand, OTAs will -----ONLY----- install if you have STOCK RECOVERY.
You will need to flash stock recovery BACK (replacing TWRP), THEN you can accept the update!!!!
Afterwards, you can flash TWRP back.
This is well documented everywhere.....you will have to do this EVERYTIME a new OTA comes out.
You can NOT accept an OTA if you have TWRP installed.
Do you understand now?
Click to expand...
Click to collapse
But I did STOCK and no updates came up.
Liooh said:
But I did STOCK and no updates came up.
Click to expand...
Click to collapse
I'm convinced that you aren't even reading what I'm writing......
Let me make this easy for you:
Do this:
1. Return to Stock 4.4.2
2. Accept the OTA (DO NOT FLASH TWRP)
3. After you accept the OTA, and you are running 4.4.3, NOW you can install TWRP
YOU CANNOT ACCEPT THE OTA IF TWRP IS INSTALLED!!!!! I've told you this SO many times now.....
TWRP is your problem. You must NOT install TWRP and root (supersu) until AFTER you accept the OTA.
It has ALWAYS been like this. This is nothing new.
Please read my posts carefully. If you follow those instructions, it WILL work.........
samwathegreat said:
I'm convinced that you aren't even reading what I'm writing......
Let me make this easy for you:
Do this:
1. Return to Stock 4.4.2
2. Accept the OTA (DO NOT FLASH TWRP)
3. After you accept the OTA, and you are running 4.4.3, NOW you can install TWRP
YOU CANNOT ACCEPT THE OTA IF TWRP IS INSTALLED!!!!! I've told you this SO many times now.....
TWRP is your problem. You must NOT install TWRP and root (supersu) until AFTER you accept the OTA.
It has ALWAYS been like this. This is nothing new.
Please read my posts carefully. If you follow those instructions, it WILL work.........
Click to expand...
Click to collapse
When I go back to STOCK doesn't the TWRP break ? Because whenever I go back to stock and try to click on "Recovery" Dev stops working. That's what I did man..
1- Back to STOCK perfectly.
2- No Updates comes up. What's this OTA update you're talking about ? where does it pops up ? I'M SURE I DIDN'T RECEIVE ANY right after I stock it... I even checked it in the System Updates...
Liooh said:
When I go back to STOCK doesn't the TWRP break ? Because whenever I go back to stock and try to click on "Recovery" Dev stops working. That's what I did man..
1- Back to STOCK perfectly.
2- No Updates comes up. What's this OTA update you're talking about ? where does it pops up ? I'M SURE I DIDN'T RECEIVE ANY right after I stock it... I even checked it in the System Updates...
Click to expand...
Click to collapse
YES, you do NOT want TWRP (or you can't accept the update).
OTA = "Over the air update" = update to 4.4.3
What method are you using to return to stock? Tell me you aren't just doing a "factory reset". How exactly are you "returning to stock"?
If you install TWRP = updates DISABLED.
samwathegreat said:
YES, you do NOT want TWRP (or you can't accept the update).
OTA = "Over the air update" = update to 4.4.3
What method are you using to return to stock? Tell me you aren't just doing a "factory reset". How exactly are you "returning to stock"?
If you install TWRP = updates DISABLED.
Click to expand...
Click to collapse
I tried many.. RSDLite, Manual flashing and that one that is recommended for people with problems with "boot loop" and the first I tried two days ago that erased all my data, cache, everything..
The thing is, is that every method seems to work fine but I just don't receive the update '-'
Actually I receive that upgrade that is something that pops up for 3 seconds saying "Upgrading android, installing apps." Then my Dev initializes normal but still dealing with the 4.4.2...
Liooh said:
I tried many.. RSDLite, Manual flashing and that one that is recommended for people with problems with "boot loop" and the first I tried two days ago that erased all my data, cache, everything..
The thing is, is that every method seems to work fine but I just don't receive the update '-'
Click to expand...
Click to collapse
Please just try.
1. Return to Stock (just use RSD Lite) YES, this will erase EVERYTHING.
2. Go to settings > About Device > System Update
3. Update to 4.4.3 will install.
4. After 4.4.3 successfully installs, NOW you can flash TWRP (ONLY after you are on 4.4.3)
Please just try it.....
---------- Post added at 08:21 PM ---------- Previous post was at 07:36 PM ----------
Liooh said:
Actually I receive that upgrade that is something that pops up for 3 seconds saying "Upgrading android, installing apps." Then my Dev initializes normal but still dealing with the 4.4.2...
Click to expand...
Click to collapse
That is because you flashed TWRP, as I've been trying to make you understand.....
Is Spanish your native language?
If so, perhaps this page will explain it better than I can:
http://getmovil.com/motorola/instalar-android-4-4-3-moto-x-root/
samwathegreat said:
Please just try.
1. Return to Stock (just use RSD Lite) YES, this will erase EVERYTHING.
2. Go to settings > About Device > System Update
3. Update to 4.4.3 will install.
4. After 4.4.3 successfully installs, NOW you can flash TWRP (ONLY after you are on 4.4.3)
Please just try it.....
Click to expand...
Click to collapse
See now ?

[Q] Phone will only boot to recovery

HTC One rooted a few days ago, was running stock then decided to place a custom rom on it.
Rom failed to install, and every time I turn on the phone it goes straight to recovery mode.
Backups dont seem to be working and I've tried sideloading a different custom rom but that also failed. Pushing backups to the phone has also not solved the issue.
HTC one M7 is/was running latest 4.4.3, international
Any help would be greatly appreciated, I guess this is what you'd call a soft brick but I just can't fix it.
Thanks
Criminall
Criminallyinsane said:
HTC One rooted a few days ago, was running stock then decided to place a custom rom on it.
Rom failed to install, and every time I turn on the phone it goes straight to recovery mode.
Backups dont seem to be working and I've tried sideloading a different custom rom but that also failed. Pushing backups to the phone has also not solved the issue.
HTC one M7 is/was running latest 4.4.3, international
Any help would be greatly appreciated, I guess this is what you'd call a soft brick but I just can't fix it.
Thanks
Criminall
Click to expand...
Click to collapse
probably a wrong recovery version for the ROM you are trying to install
assuming you have an m7_u or m7_ul, use TWRP 2.6.3.3 or 2.8.0.0 or 2.8.0.1 (the other versions are known to have issues with some roms)
also check the Frequently Asked Question sticky page 3
and don't forget to check MD5 on your downloads!!
nkk71 said:
probably a wrong recovery version for the ROM you are trying to install
assuming you have an m7_u or m7_ul, use TWRP 2.6.3.3 or 2.8.0.0 or 2.8.0.1 (the other versions are known to have issues with some roms)
also check the Frequently Asked Question sticky page 3
and don't forget to check MD5 on your downloads!!
Click to expand...
Click to collapse
Thanks I did the 2.8.0.1, but now I can't even use adb to flash or anything, the device is essentially unrecognised now. Any tips on how to proceed?
Criminallyinsane said:
Thanks I did the 2.8.0.1, but now I can't even use adb to flash or anything, the device is essentially unrecognised now. Any tips on how to proceed?
Click to expand...
Click to collapse
faq #2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
it was also mentioned in the sticky post i linked earlier, reading it helps
nkk71 said:
faq #2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
it was also mentioned in the sticky post i linked earlier, reading it helps
Click to expand...
Click to collapse
Thanks man, very helpful. However, every time I update the drivers and put the phone in sideload it stops recognising it once again.
I was hoping I could just sideload a new rom to the phone and attempt to install it?
Criminallyinsane said:
Thanks man, very helpful. However, every time I update the drivers and put the phone in sideload it stops recognising it once again.
I was hoping I could just sideload a new rom to the phone and attempt to install it?
Click to expand...
Click to collapse
try adb push method instead of sideload
or once in sideload, right-click your PC in Windows device manager, and "scan for hardware changes", that may fix it

Categories

Resources