Hey guys,
Terribly sorry if this is a common question, but after two days of searching and being unable to use my phone, I decided to post instead.
I have previously succesfully installed Cyanogen on my HTC One, using CWM. After talking to some family and friends, I decided to try out ARHD instead, as it seemed more fitting to my needs.
I download the zip, flash it from CWM, but I constantly get the error "set_metadata_recursive: some changes failed" at end of installation. I am able to continue and install seems succesful, but I can never boot past the inital white screen HTC logo. I searched for info on this, and some reported it might be due to outdated recovery. However, I have tried with CWM 6.0.4.8 and I am currently running 6.0.4.6 Touch, but no luck with either version.
At one point, I also soft-bricked my phone. I were able to flash new recovery, but had to reset my SD card and I also lost all backups. Somehow the phone booted up in Cyanogen after this, and I were able to download a zip for ARHD 81. I tried flashing this, got "set_metadata_recursive: some changes failed" and I am now unable to boot my phone again.
I have tried pushing and sideloading, however neither seems to work. Since there's no progress bar for pushing, I had to be patient, but after two hours without result I have to assume it's not working. Sideloading always gets stuck at either 3% or 8%, I can't seem to find a cause for this.
I really hope you guys might be able to work out a fix for this issue with me, as I've reached a dead end.
Unlock
I have also unlocked the phone with HTCDev unlock tool, so that should be fine.
TalkingWaterfall said:
I have also unlocked the phone with HTCDev unlock tool, so that should be fine.
Click to expand...
Click to collapse
ARHD requires TWRP Recovery
download TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
then flash it
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
now your rom will install without error
Alright. I have tried installing TWRP, but I always came up with errors booting into TWRP. I got it working once, but at that point in time I didn't have the ROM zip on my phone... I'll try it out asap and get back. Thanks.
That did it. Honestly I feel a little silly at this point, but I wish it were mentioned in the main ARHD thread that you needed TWRP, since in the "You Need" section, it simply requires a custom recovery.
I'd never seen the fastboot erase cache command before, so that helped out a lot getting TWRP working
Thank you so much!
TalkingWaterfall said:
That did it. Honestly I feel a little silly at this point, but I wish it were mentioned in the main ARHD thread that you needed TWRP, since in the "You Need" section, it simply requires a custom recovery.
I'd never seen the fastboot erase cache command before, so that helped out a lot getting TWRP working
Thank you so much!
Click to expand...
Click to collapse
Your welcome
Related
hello guys, i really need help with this last few steps of rooting my phone.
from here,http://forum.xda-developers.com/showthread.php?t=1625841
in step 4. flash recovery downloaded aboved by using this command: fastboot flash recovery recovery_for_1.28
i get the error message as per the title
now before i tried to flash the recovery 1.28, i flashed another recovery from o' brian's. would this cause any problems that would lead to the error message above? i assumed that flashing a new recovery would just overwrite the old one.
when i flashed the recovery from o'brian's, it says waiting for device or something similar to that. then i proceeded to go into recovery as instructed. however, my phone simply turns off. when i have to turn it back on manually, nothing changed.
can any kind soul please enlighten me?
niekehecv said:
hello guys, i really need help with this last few steps of rooting my phone.
from here,http://forum.xda-developers.com/showthread.php?t=1625841
in step 4. flash recovery downloaded aboved by using this command: fastboot flash recovery recovery_for_1.28
i get the error message as per the title
now before i tried to flash the recovery 1.28, i flashed another recovery from o' brian's. would this cause any problems that would lead to the error message above? i assumed that flashing a new recovery would just overwrite the old one.
when i flashed the recovery from o'brian's, it says waiting for device or something similar to that. then i proceeded to go into recovery as instructed. however, my phone simply turns off. when i have to turn it back on manually, nothing changed.
can any kind soul please enlighten me?
Click to expand...
Click to collapse
Note what kind of hboot do you have, check your bootloader, if you have Hboot 1.25 then the functional and recommended Recovery for you is by Paul O'Brien, if you are on Hboot 1.28 then the recommended one is bue unlimited.io, if you are lazy to search for them, you have them included in this tool, i really can't understand why people doesn't use this, as it is free and keeps you away from lots of searching, many threads are old, many procedures are old so the guide recommended by me for everything is the guide by stona15, this one
Hope this helps
Hi guys i have a big problem with my phone htc one m7
i was flashing my phone with a 4.4 viperone rom, and performed a nandorid back up prior to the flash.
Installation failed and i was forced to reboot the phone, now when it loads it brings up TWRP for a few seconds and loops.
is there anything I can do to resolve this ? i cant get into recovery itself to flash a custom Rom but can access HBOOT 1.44.
i have S-On.
any help would be greatly appreciated, have i bricked this phone if i cant get into the recovery or it doesn't load ?
thanks so much
nmagriplis said:
Hi guys i have a big problem with my phone htc one m7
i was flashing my phone with a 4.4 viperone rom, and performed a nandorid back up prior to the flash.
Installation failed and i was forced to reboot the phone, now when it loads it brings up TWRP for a few seconds and loops.
is there anything I can do to resolve this ? i can get into the recovery menu i.e. fast boot etc. but i cant get into recovery itself to access my backed up img.
i have S-On.
any help would be greatly appreciated, have i bricked this phone if i cant get into the recovery or it doesn't load ?
thanks so much
Click to expand...
Click to collapse
First if you want help, change your thread title to something more specific like: ''Help - bootlooping after custom rom flash''
Did you wiped cache? What version of twrp are you using?
nmagriplis said:
Hi guys i have a big problem with my phone htc one m7
i was flashing my phone with a 4.4 viperone rom, and performed a nandorid back up prior to the flash.
Installation failed and i was forced to reboot the phone, now when it loads it brings up TWRP for a few seconds and loops.
is there anything I can do to resolve this ? i can get into the recovery menu i.e. fast boot etc. but i cant get into recovery itself to access my backed up img.
i have S-On.
any help would be greatly appreciated, have i bricked this phone if i cant get into the recovery or it doesn't load ?
thanks so much
Click to expand...
Click to collapse
alray said:
First if you want help, change your thread title to something more specific like: ''Help - bootlooping after custom rom flash''
Did you wiped cache? What version of twrp are you using?
Click to expand...
Click to collapse
Thanks very much for getting back to me, after 12 long hours of research and getting my head around it, i finally found a solution!
In a nut shell this is what i did to resolve the issue:
installed ADB and Fastboot drivers
flashed a recovery img using fastboot
in recovery TWRP, used ADB to push a custom rom to my sd card
flashed with custom recovery and installed OS
What wasnt made clear was the fact that you need to be in a custom recovery (TWRP or CWM) in order for the ADB drivers to work. I was stuck for a number of hours troubleshooting why fastboot would detect my device (fastboot devices) and ADB wouldnt! It was only when i had my phone connected to my windows machine and phone was in TWRP, i could talk to my device and run adb shell, and adb push.
thank god that little cookie is over, heart attack and a loss of my Sunday, but all good now
Hi, I have tried being clever and rooting my HTC ONE Mini, which all went perfectly well. Unlocked Bootloader and installed TWRP.
I found a radio update on a website and tried installing it, with S-ON. As you can imagine I am not stuck in Bootloop.
I somehow managed to wipe all the data off my phone and sdcard too.
So I am stuck with a phone in bootloop with recovery from TWRP.
Everytime i try and fastboot flash any file even an Android ROM.zip it doesnt like it. I am novice at this so you are probably reading this and think what is he doing.
Can someone help me or guide me to getting my phone back and running again. Please??
wrighty29 said:
Hi, I have tried being clever and rooting my HTC ONE Mini, which all went perfectly well. Unlocked Bootloader and installed TWRP.
I found a radio update on a website and tried installing it, with S-ON. As you can imagine I am not stuck in Bootloop.
I somehow managed to wipe all the data off my phone and sdcard too.
So I am stuck with a phone in bootloop with recovery from TWRP.
Everytime i try and fastboot flash any file even an Android ROM.zip it doesnt like it. I am novice at this so you are probably reading this and think what is he doing.
Can someone help me or guide me to getting my phone back and running again. Please??
Click to expand...
Click to collapse
You can't use fastboot to flash a rom.zip! It must be pushed to your phone (use either adb push or adb sideload from recovery) and installed from custom recovery.
Btw this is the wrong forum for your device. Htc one mini forum is here
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
mobone32 said:
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
Click to expand...
Click to collapse
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
mobone32 said:
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
Click to expand...
Click to collapse
you should be able to install TWRP by using the command, "mfastboot recovery twrp.img"
regarding CM11, I don't think is needed anymore to go from CM10 to CM12. it was at one time, but I believe CM or TWRP made some updates so that step is no longer necessary.
but before we can help you further, let us know what ROM you are on now and what ROM you want to be on next.
also, this thread is very helpful: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
Ok I got TWRP on there. Now I would like to get to lolipop 5.1 one way or another. I've always liked CyanogenMod (of course) but want to try CyanHacker. http://forum.xda-developers.com/moto-x/development/rom-cyanhacker-lollipop-ghost-t3033367
Right now I'm on a stock sprint rom I got with kitkat 4.4.4
Here's what I was going to do: (copied from forum)
1. mfastboot flash the latest TWRP if you aren't already at that point. I won't help you on fastboot things as you should already know- look around in the forums for info.
2. BACKUP YOUR STUFF- don't want to lose things without being able to get them back, right?
3. Flash the downloaded CM11 snapshot.
(Heres where I'm stuck. This is where I soft bricked it last night. I tried just now to apply the update using twrp and it just fails. It also fails at rooting my phone.)
4. Let CM11 fully boot and go through the setup screen- just skip everything and get to the homescreen.
5. Reboot into Recovery and wipe EVERYTHING- system, data, dalvik cache, cache, etc.
6. Flash your Lollipop ROM.
7. Flash PA-gapps.
8. Flash SuperSU.
9. Wipe cache/dalvik cache.
10. Reboot.
11. ???
12. Profit.
Thanks for any help!
Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!
Blenderite said:
Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!
Click to expand...
Click to collapse
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...
cultofluna said:
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...
Click to expand...
Click to collapse
Ok I tried that and a new problem came up!! When I try to reboot into recovery, I do not get TWRP, but the stock recovery that was there originally! Unless they have completely changed the look of TWRP. I will try to upload a picture of it if that helps.
You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.
Anova's Origin said:
You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.
Click to expand...
Click to collapse
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html
Blenderite said:
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html
Click to expand...
Click to collapse
Right on that page (last paragraph of fastboot install method), you will see:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".
redpoint73 said:
Right on that page (last paragraph of fastboot install method), you will see:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".
Click to expand...
Click to collapse
I tried this once before, but after your suggestion to try it several times, it finally worked! Thanks!!
Flash TWRP, reboot, press the volume down key before the phone boots, go into recovery, you should see TWRP flash screen, that usually works but I'm glad you got it going