[Q] How to remove a recovery corretly - One (M7) Q&A, Help & Troubleshooting

Hi guys! Lately I had some issues with my rooted HTC One. At first a tasty bunch of info for you
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.206.7
eMMC-boot 2048MB
Aug 6 2013, 11:26:00.0
So here is the deal. Some days ago I've flashed TWRP above my prev installed CWMR by accident. Messed up with the files on my PC.
No big deal I tought. But it is for me. After flashing CWMR v6.0.3.1 (touch) again the touch isn't working for me and I can't go bat to TWRP for some reason.
So the main question for me is how can I move back to a state of "fresh rooted" device with working CWMR incl. touch and no kind of messed up recovery.
Bonus question of the day: what is the advantage of S-OFF? Does it make sense to S-OFF as a user who flashes a custom ROM here and there and is not very experienced with things besides how to get root and install a ROM?
So what to do? Any advice?
Thank you for all kindness and helpful response!

fraehngi said:
Hi guys! Lately I had some issues with my rooted HTC One. At first a tasty bunch of info for you
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.206.7
eMMC-boot 2048MB
Aug 6 2013, 11:26:00.0
So here is the deal. Some days ago I've flashed TWRP above my prev installed CWMR by accident. Messed up with the files on my PC.
No big deal I tought. But it is for me. After flashing CWMR v6.0.3.1 (touch) again the touch isn't working for me and I can't go bat to TWRP for some reason.
So the main question for me is how can I move back to a state of "fresh rooted" device with working CWMR incl. touch and no kind of messed up recovery.
Bonus question of the day: what is the advantage of S-OFF? Does it make sense to S-OFF as a user who flashes a custom ROM here and there and is not very experienced with things besides how to get root and install a ROM?
So what to do? Any advice?
Thank you for all kindness and helpful response!
Click to expand...
Click to collapse
6.0.3.1 is way outdated (touchscreen doesnt work), you can get the updated ones here: http://forum.xda-developers.com/showthread.php?t=2173863
but be warned, backups & restore take about 1 hour instead of 5 mins, so either use TWRP
or 6.0.3.2:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc

nkk71 said:
6.0.3.1 is way outdated (touchscreen doesnt work), you can get the updated ones here: http://forum.xda-developers.com/showthread.php?t=2173863
but be warned, backups & restore take about 1 hour instead of 5 mins, so either use TWRP
or 6.0.3.2:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
Click to expand...
Click to collapse
Okay here is the next problem coming around. I've flashed "recovery-clockwork-touch-6.0.4.3-m7ul.img" now and the touch is working again.
Trying to install ElementalX Kernel at the moment and it stucks with 0% for now about 15 minutes
Oh an it's now saying
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log

Can you reboot, and try again? Same error? Can you browse to folders using cwm?

SaHiLzZ said:
Can you reboot, and try again? Same error? Can you browse to folders using cwm?
Click to expand...
Click to collapse
Ok, did a reboot and the error is gone. Will try to flash the Kernel now again...

fraehngi said:
Oh an it's now saying
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
that's perfectly normal after a "fastboot erase cache" nothing to worry about.
fraehngi said:
Trying to install ElementalX Kernel at the moment and it stucks with 0% for now about 15 minutes
Click to expand...
Click to collapse
happened to me just yesterday :silly:, rebooted using:
adb reboot recovery
and installed again, second time it worked it worked for me. took only a few minutes, but rebooting took a bit longer than usual, also remember you have to reboot twice (according to the ElementaX thread).

nkk71 said:
that's perfectly normal after a "fastboot erase cache" nothing to worry about.
happened to me just yesterday :silly:, rebooted using:
adb reboot recovery
and installed again, second time it worked it worked for me. took only a few minutes, but rebooting took a bit longer than usual, also remember you have to reboot twice (according to the ElementaX thread).
Click to expand...
Click to collapse
Well the first problem solved after a regular boot of the system. That solved the 0% problem, too. But now I face the problem, that the aroma installer / flash of the kernel quits at 10% and the phone went to a black screen. I'm running Android Revolution 31.6

I would guess keep trying! I read somewhere about Aroma issue. Just needs to be reflashed.

Related

No OS, no recovery

Hi everyone, as You can tell I'm a novice when it comes to these things and I don't wish to bore you with the details of how I got into this pickle (unless it's needed) but long story short, my phone does not have an OS and it does not have a recovery. Whenever I turn on the phone it displays this screen:
{
***TAMPERED***
***RELOCKED***
***SECURITY WARNING***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 18 2013, 18:47:36:-1
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
}
That's pretty much all I can do on this phone and I need some guidance on what to do. Thanks in advance!
Use fastboot to flash a recovery. Look at the q&a rollup thread in the stickies to learn how. Then flash a rom of choice by doing an adb push in your new recovery. If this all happened because you flashed a non Sprint Rom, you have more issues to deal with. The second option is to RUU back to stock. This is only possible if you didn't get the latest OTA before borking you phone. If you did get the OTA, you will need to s-off. Read the sticky threads, learn how to achieve these things. There are also countless more posts just like yours in this section with answers.
Sent from my HTCONE using xda premium
propjockey said:
Use fastboot to flash a recovery. Look at the q&a rollup thread in the stickies to learn how. Then flash a rom of choice by doing an adb push in your new recovery. If this all happened because you flashed a non Sprint Rom, you have more issues to deal with. The second option is to RUU back to stock. This is only possible if you didn't get the latest OTA before borking you phone. If you did get the OTA, you will need to s-off. Read the sticky threads, learn how to achieve these things. There are also countless more posts just like yours in this section with answers.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I have been using the sticky, it's just that my backup didnt work after wiping my stuff, and I eventually ended up re-locking my phone, but ill continue to try on the matter
Are you on the latest firmware? Can you manually reboot into recovery using the physical buttons?
Sent from my HTCONE using xda premium
propjockey said:
Are you on the latest firmware? Can you manually reboot into recovery using the physical buttons?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Not sure on the firmware, but no I cannot manually boot into recovery.
How did this happen? Was it a incorrect Rom flash? If so, I think your only option is to try to get s-off using revone. If you can get adb to work well enough to push a file to your storage and run some cmd prompt commands, you should be able to s-off. Then you can RUU back to stock with everything back to factory specs. This process of s-off is only needed if you are on the latest firmware (1.31) because we only have the older firmware RUU file. The system won't allow an older one to flash over a newer one unless your s-off.
Edit: I think your on the older firmware. The radio thou have listed is the same as mine, and I'm in 1.29. Does your computer recognize it when in the boot loader?
Sent from my HTCONE using xda premium
no, it wasn't an incorrect flash, I had tried to restore my rom back to stock from a backup I had, but I had wiped everything before and it turns out my backup was somehow corrupt, so I had no rom to flash. I tried to fix it somehow but I just ended up locking my bootloader and now I am here.
would I just use the all in one toolkit to try and redo everything and ADB push?
You probably could. Unlock again, push a recovery again, push a Rom file using adb to new recovery. Flash and profit.
If things got worse than that, ie: corrupt partitions, then you will likely have to RUU to stock.
Also, now may not be the time to do this but, look into learning basic fastboot and adb commands. They can be a real life saver and help out when an all in one toolkit isn't working or doesn't exist. But I bet you don't want to download the sdk, setup, and learn tonight. Especial not with a phone that's hurt already. For the future though, could save your day.
Sent from my HTCONE using xda premium
I tried to ADB push a rom before, but to no avail, and when I tried to restore from a backup, it mentioned something about there not being a partition. Hopefully this I won't run into this problem again
Good luck!
Sent from my HTCONE using xda premium
well i managed to get TWRP back on, but I cant do the ADB push, I'm getting an error that says "unable to mount '/data'"
any thoughts on this error?
Try sideloading.
http://forum.xda-developers.com/showthread.php?t=2317989
Sent from my HTCONE using xda premium
after all my attempts of trying to ADB sideload, I still get an error after I "swipe to side load"
I keep getting
E: unable to mount '/data'
E: unable to recreate /data/media folder.
Updating partition details
E: unable to mount '/data'
E: unable to mount internal storage
unable to mount data/media during GUI startup
E: unable to mount /data/media/TWRP/ .twrp
E: unable to mount '/data'
E: unable to mount '/data'
E: unable to mount '/data'
I'm at a total loss, and Ive been looking through the sticky and other threads
EmSeeMAC said:
after all my attempts of trying to ADB sideload, I still get an error after I "swipe to side load"
I keep getting
E: unable to mount '/data'
E: unable to recreate /data/media folder.
Updating partition details
E: unable to mount '/data'
E: unable to mount internal storage
unable to mount data/media during GUI startup
E: unable to mount /data/media/TWRP/ .twrp
E: unable to mount '/data'
E: unable to mount '/data'
E: unable to mount '/data'
I'm at a total loss, and Ive been looking through the sticky and other threads
Click to expand...
Click to collapse
if your bootloader is relocked how would you be able to sideload a rom, if thats what you're trying to do i would unlock then reflash recovery and go from there.why did you relock?
Aldo101t said:
if your bootloader is relocked how would you be able to sideload a rom, if thats what you're trying to do i would unlock then reflash recovery and go from there.why did you relock?
Click to expand...
Click to collapse
I unlocked it again, I had relocked it by accident, but I am getting this error
EmSeeMAC said:
I unlocked it again, I had relocked it by accident, but I am getting this error
Click to expand...
Click to collapse
what did you flash to your phone before this.
Aldo101t said:
what did you flash to your phone before this.
Click to expand...
Click to collapse
d3rprom and bulletproof kernel
EmSeeMAC said:
d3rprom and bulletproof kernel
Click to expand...
Click to collapse
does adb work/?
if so i would reflash recovery and then try to sideload a rom
Aldo101t said:
does adb work/?
if so i would reflash recovery and then try to sideload a rom
Click to expand...
Click to collapse
Im trying to get adb to work
EmSeeMAC said:
Im trying to get adb to work
Click to expand...
Click to collapse
delete your htc drivers then plug phone in to computer and let the drivers reinstall, try that??

Help with Brick: HTC First ...big trouble!

Hello to all:
I have an HTC First and this is whats happening: i wanted to root it and i unlock the bootloader and i tried to install the CWM recovery and thats where it gave me an error, so when i try to upload it shows the facebook logo and it says '' this is built for development purposes only'', do not distribute outside of HTC without HTC's written permission, failure to comply made lead to legal action and then it goes to recovery, i tried to install the JmzMystJBSense ROM BY SIDELOAD, it installs but when i hit the restart button goes back to the CWM recovery instead of the system, so i decided to change the system to the TWRP TOUCH recovery to verify if the phone will function normal and then it goes to the CWM recovery and when i enter the HBOOT goes back to the TWRP TOUCH recovery and the worse of all is that both got installed in the ROM last mentioned but when i restart the phone it gives me nothing.
this is the info i have about the HBOOT:
*** TAMPERED ***
*** UNLOCKED***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:-1
thanks in advance
cristianq27 said:
Hello to all:
I have an HTC First and this is whats happening: i wanted to root it and i unlock the bootloader and i tried to install the CWM recovery and thats where it gave me an error, so when i try to upload it shows the facebook logo and it says '' this is built for development purposes only'', do not distribute outside of HTC without HTC's written permission, failure to comply made lead to legal action and then it goes to recovery, i tried to install the JmzMystJBSense ROM BY SIDELOAD, it installs but when i hit the restart button goes back to the CWM recovery instead of the system, so i decided to change the system to the TWRP TOUCH recovery to verify if the phone will function normal and then it goes to the CWM recovery and when i enter the HBOOT goes back to the TWRP TOUCH recovery and the worse of all is that both got installed in the ROM last mentioned but when i restart the phone it gives me nothing.
this is the info i have about the HBOOT:
*** TAMPERED ***
*** UNLOCKED***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:-1
thanks in advance
Click to expand...
Click to collapse
If you don't care about losing sense just sideload the stock one and flash the boot.IMG
Oh and make sure that when you side loaded the ROM it was side loaded 100% that's very glitchy on our phone for some reason and stops like at 50% sometimes and tries installing it from there.
Oh that reminds me, did you remember to fish the boot.IMG from jmz's ROM?
Edit: what cwm and twrp recovery did you use? There's a really helpful tool around these threads from wizzra that dudes it all in a few simple clicks
abrahammmmmmm_ said:
If you don't care about losing sense just sideload the stock one and flash the boot.IMG
Oh and make sure that when you side loaded the ROM it was side loaded 100% that's very glitchy on our phone for some reason and stops like at 50% sometimes and tries installing it from there.
Oh that reminds me, did you remember to fish the boot.IMG from jmz's ROM?
Edit: what cwm and twrp recovery did you use? There's a really helpful tool around these threads from wizzra that dudes it all in a few simple clicks
Click to expand...
Click to collapse
He's on s-on. Is that okay?
Sent from my HTC first using XDA Premium 4 mobile app
russian392 said:
He's on s-on. Is that okay?
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is there any form to put it on s-off without having the system??
Doesn't matter if he's s-on this is actually the reason why he needs to flash the boot.img. one of s-off's purpose is to not do things like have to flash a boot.IMG so yes it's safe
And sadly no. To get s-off it's necessary to boot the device to apply certain changes to the perfmissions on the phone

HTC One OS-2.24.61.1 Help!!!

Hello xDaDevelopers I need your help plss
I have HTC one bought 2nd hand couple of days phone was rooted, and i didn't see that when i bought it becouse never had one before or see one!!
Phone was working fine before i done somethink wrong
I try to return it to sotck rom when i get into recovery ''ClockworkMod Recovery v6.0.4.6''
!Ive gone into this and pressed the "wipe" button and "format data" thinking this would do a full factory reset for the phone.....I was wrong!
I now have no OS on the phone and i'm stuck with big problem as i'm a driver and use my phone as nav..
I try 2 days read at google, forums i can't found way to fix it try evrythink.
ClockworkMod Recovery v6.0.4.6
options when i get there i have just
-reboot system now
-install zip
-wipe data/factory reset
-wipe cache partition
-backup and storage
-advanced
When I go into the bootload the following info is there......
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.61.1
eMMC-boot 2048MB
Jun 21 2013, 23:33:16.0
Help please I have adb/fastboot at my c/ install it!
you need to download a rom and put on your phone's sd card and flash it in recovery through "install zip" a toolkiy might help you out too, you can find one there as well
wright0101 said:
you need to download a rom and put on your phone's sd card and flash it in recovery through "install zip" a toolkiy might help you out too, you can find one there as well[/QUOTE
Problem is i can see ''sd card'' as i delete all that and when i connect phone that can be only with fastboot!!! thx i will try to found ,toolkiy'
Click to expand...
Click to collapse
Your boot loader says you have a different version. Sprint is m7wls.so u prbly wanna look in the other HTC one forums...flashing stuff here may just get into even more trouble
Sent from my HTCONE using Xparent Red Tapatalk 2
being s-on should stop you from install the wrong version, you'll have to push or sideload the files to your phone and flash your boot image. don't delete the internal data from your phone

[Q] What is the right RUU file to use ?

Hi there, Im needing to find an RUU file that I can use on my htc one m7. I lost battery power during an upgrade and soft bricked my phone dumbass I know.
Here is the information thanks ?
My HTC details
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.11.401.10
eMMC-boot 2048MB
May 5 2014 23:16:29.0
OS again is OS-5.11.401.10
Cheers
publication1 said:
Hi there, Im needing to find an RUU file that I can use on my htc one m7. I lost battery power during an upgrade and soft bricked my phone dumbass I know.
Here is the information thanks ?
My HTC details
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.11.401.10
eMMC-boot 2048MB
May 5 2014 23:16:29.0
OS again is OS-5.11.401.10
Cheers
Click to expand...
Click to collapse
your s-on their is no RUU for your version
you need custom recovery and you can flash the GURU Reset
here > Guru_Reset_M7_5.11.401.10-TeHashX.zip
http://www.androidfilehost.com/?fid=23501681358543706
If your stuck and can't flash custom recovery
try and flash this firmware first >> http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/5.11.401.10.zip
Reply
clsA said:
your s-on their is no RUU for your version
you need custom recovery and you can flash the GURU Reset
here > Guru_Reset_M7_5.11.401.10-TeHashX.zip
http://www.androidfilehost.com/?fid=23501681358543706
If your stuck and can't flash custom recovery
try and flash this firmware first >> http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/5.11.401.10.zip
Click to expand...
Click to collapse
So far I have tried 2x ROMS via flashing TWRP but both failed for what ever reason. I tried - 2 that matched my OS and still failed so can only seem to think about trying RUU's now Grrr
publication1 said:
So far I have tried 2x ROMS via flashing TWRP but both failed for what ever reason. I tried - 2 that matched my OS and still failed so can only seem to think about trying RUU's now Grrr
Click to expand...
Click to collapse
what version of TWRP ?
use 2.6.3.3 here > http://techerrata.com/browse/twrp2/m7
Wish me luck
clsA said:
what version of TWRP ?
use 2.6.3.3 here > http://techerrata.com/browse/twrp2/m7
Click to expand...
Click to collapse
away to try and flash it now, thanks
no luck reply
clsA said:
what version of TWRP ?
use 2.6.3.3 here > http://techerrata.com/browse/twrp2/m7
Click to expand...
Click to collapse
Have tried pushing ROM to TWRP using 2.6.3.3 and it comes up saying
Wiping data without wiping / data/media
Done
Updating partition details
E:Unable to open zip file
Error flashing zip /sdcard/ROM.zip
Updating partition details ?
Any ideas ? Thanks
publication1 said:
E:Unable to open zip file
Click to expand...
Click to collapse
bad download probably, check md5
reply
nkk71 said:
bad download probably, check md5
Click to expand...
Click to collapse
Yeh bad download, Cant find any other ones that will work though grrrr
Reply
publication1 said:
Yeh bad download, Cant find any other ones that will work though grrrr
Click to expand...
Click to collapse
Not getting a confirmation when pushing rom to sd card using command line, it follows the command but just keeps flashing. I checked TWRP and it is there but still failing like all the rest. Tutorials say its meant to show something like 33445kb changes to 44533553kb meaning thats it moved so maybe im trying to install when its only partly pushed to TWRP but thats been 5 minutes now ?
publication1 said:
Not getting a confirmation when pushing rom to sd card using command line, it follows the command but just keeps flashing. I checked TWRP and it is there but still failing like all the rest. Tutorials say its meant to show something like 33445kb changes to 44533553kb meaning thats it moved so maybe im trying to install when its only partly pushed to TWRP but thats been 5 minutes now ?
Click to expand...
Click to collapse
If you use sideload theirs a progress and the flash starts on it's own when ready
In TWRP / Advanced / ADB Sideload
on the PC > adb sideload name_of_rom.zip
publication1 said:
Not getting a confirmation when pushing rom to sd card using command line, it follows the command but just keeps flashing. I checked TWRP and it is there but still failing like all the rest. Tutorials say its meant to show something like 33445kb changes to 44533553kb meaning thats it moved so maybe im trying to install when its only partly pushed to TWRP but thats been 5 minutes now ?
Click to expand...
Click to collapse
adb push does not show any progress until it's done (5 to 10 mins for a 1GB file), it will only come back once it's finished
for example, point E here: http://forum.xda-developers.com/showthread.php?t=2228274&page=3
publication1 said:
Not getting a confirmation when pushing rom to sd card using command line, it follows the command but just keeps flashing. I checked TWRP and it is there but still failing like all the rest. Tutorials say its meant to show something like 33445kb changes to 44533553kb meaning thats it moved so maybe im trying to install when its only partly pushed to TWRP but thats been 5 minutes now ?[/QUOTE
Try sideloading a ROM
Click to expand...
Click to collapse
Reply
clsA said:
If you use sideload theirs a progress and the flash starts on it's own when ready
In TWRP / Advanced / ADB Sideload
on the PC > adb sideload name_of_rom.zip
Click to expand...
Click to collapse
It worked, perfectly, what an achievment this has been. Think a few tutorials of my way is required to help other newbies that I once was haha. Thanks for your input buddy ill 1up ya

(SOLVED)My one only boots to recovery (TWRP) after installing custom rom

Hi guys I really need your help.
Basically any rom I run ( via adb sideload or adb push and then install zip) will not work. I get into the aroma (usually) installer and after that is finished I usually get "successfull" but with the exception of "Set_metadata_recursive - some changes failed". After that I have tried a) reboot to system b) wipe cache, dalvik - then reboot c) wipe cache, dalvik and factory reset - then reboot. And pretty much all possible variations of this.
I have tried a few roms like Android revolution HD 84 & 90, Maximus HD same story, one google play edition and some others. I can't figure out wich stock rom I should choose because there are so many to choose from, the CID and MID subjects always gets my confused and I have HBOOT 1.57 ( I should tell you I have s-on)
I can't seem to find anyone/any thread/guide that explaines exactly this problem even with hours and hours going into searching.
My bootloader info:
UNLOCKED
m7_UL PVT SHIP S-ON RH
HBOOT-1.57.000
OS-6.09.401.11
Nov 14 2014, 22:08:05.0 (what's this)
I hope to good there is a solution to this even if I'm not that religous. I would very much appriciate some help from you experts.
forgot to mention: I am almost 100% sure I have superSU and root access (after installing it before and later opening the UPDATE-SuperSU-v.2.45.zip in install zip via TWRP but I do often get the "SuperSU does not seem to be installed" message when rebooting after install. note: I have used the "swiped to install" option and I have also not used it.
fhawkes54 said:
Hi guys I really need your help.
Basically any rom I run ( via adb sideload or adb push and then install zip) will not work. I get into the aroma (usually) installer and after that is finished I usually get "successfull" but with the exception of "Set_metadata_recursive - some changes failed". After that I have tried a) reboot to system b) wipe cache, dalvik - then reboot c) wipe cache, dalvik and factory reset - then reboot. And pretty much all possible variations of this.
I have tried a few roms like Android revolution HD 84 & 90, Maximus HD same story, one google play edition and some others. I can't figure out wich stock rom I should choose because there are so many to choose from, the CID and MID subjects always gets my confused and I have HBOOT 1.57 ( I should tell you I have s-on)
I can't seem to find anyone/any thread/guide that explaines exactly this problem even with hours and hours going into searching.
My bootloader info:
UNLOCKED
m7_UL PVT SHIP S-ON RH
HBOOT-1.57.000
OS-6.09.401.11
Nov 14 2014, 22:08:05.0 (what's this)
I hope to good there is a solution to this even if I'm not that religous. I would very much appriciate some help from you experts.
forgot to mention: I am almost 100% sure I have superSU and root access (after installing it before and later opening the UPDATE-SuperSU-v.2.45.zip in install zip via TWRP but I do often get the "SuperSU does not seem to be installed" message when rebooting after install. note: I have used the "swiped to install" option and I have also not used it.
Click to expand...
Click to collapse
Set metadata errors are caused by using the wrong recovery version ( explained in the FAQ sticky thread page 3 post 1 C) ).
Flash twrp 2.6.3.3 and reflash the rom.
alray said:
Set metadata errors are caused by using the wrong recovery version ( explained in the FAQ sticky thread page 3 post 1 C) ).
Flash twrp 2.6.3.3 and reflash the rom.
Click to expand...
Click to collapse
Thank you so much, you're awesome!!!!!
Got everything up and running
fhawkes54 said:
Thank you so much, you're awesome!!!!!
Got everything up and running
Click to expand...
Click to collapse
you're welcome
Can you edit your first post then click "go advanced" and edit your title to "(SOLVED) My one only boots to recovery (TWRP) after installing custom rom"
alray said:
Can you edit your first post then click "go advanced" and edit your title to "(SOLVED) My one only boots to recovery (TWRP) after installing custom rom"
Click to expand...
Click to collapse
s
Yes consider it done
boot into recovery after installing rom
alray said:
Set metadata errors are caused by using the wrong recovery version ( explained in the FAQ sticky thread page 3 post 1 C) ).
Flash twrp 2.6.3.3 and reflash the rom.
Click to expand...
Click to collapse
hey i'm facing the same problem can you please help ?
currently on TWRP v2.6.3.0
morningmilk said:
hey i'm facing the same problem can you please help ?
currently on TWRP v2.6.3.0
Click to expand...
Click to collapse
Well you din't give us much to go on .. what carrier is your phone and whats the problem
Htc one 32gb at&t
Thanks for your reply i think i have to install the different version of TWRP
Cause the problem i'm facing is after booting into system from new rom installation is my device is ending up into bootloader.
clsA said:
Well you din't give us much to go on .. what carrier is your phone and whats the problem
Click to expand...
Click to collapse
---------- Post added at 09:35 PM ---------- Previous post was at 08:54 PM ----------
Thanks but i figured out and everything is working now
morningmilk said:
Thanks for your reply i think i have to install the different version of TWRP
Cause the problem i'm facing is after booting into system from new rom installation is my device is ending up into bootloader.
Click to expand...
Click to collapse

Categories

Resources