hi all i just rooted my phone and installed xposed installer and getting this error even though i updated the farework pls help me
jithumyself said:
hi all i just rooted my phone and installed xposed installer and getting this error even though i updated the farework pls help me
Click to expand...
Click to collapse
Probably a stupid question, but you did do a full reboot right?
yuup i did a full reboot i switched off the phone and turned it on , well rite after we install the new update the xposed installer asked you to reboot i did that but still i am getting the error i even unzipped from recovery too
jithumyself said:
yuup i did a full reboot i switched off the phone and turned it on , well rite after we install the new update the xposed installer asked you to reboot i did that but still i am getting the error i even unzipped from recovery too
Click to expand...
Click to collapse
Switch Phone Off is not a reboot, it goes to sleep mode then.
You should do a real reboot, do you have the apm?
Otherwise use "adb reboot" without the quotes instead.
jithumyself said:
yuup i did a full reboot i switched off the phone and turned it on , well rite after we install the new update the xposed installer asked you to reboot i did that but still i am getting the error i even unzipped from recovery too
Click to expand...
Click to collapse
Maybe this will help: http://forum.xda-developers.com/showpost.php?p=50586287&postcount=70182
nkk71 said:
Maybe this will help: http://forum.xda-developers.com/showpost.php?p=50586287&postcount=70182
Click to expand...
Click to collapse
i dont know how to do that can u pls guide me
jithumyself said:
i dont know how to do that can u pls guide me
Click to expand...
Click to collapse
1- Xposed -> Framework -> Install/Update -> Soft reboot, after reboot go back to Xposed -> Framework, and it should look like this: (other post has the pictures)
2- Xposed -> Downloads -> download whatever module you want
3- Xposed -> Modules -> enable whatever module you want
4- select the options you want in the Module, and then reboot
how to reboot as soldier told me when i swithoff my phone i just putting it to sleep mode
guys it just got fixed the only think i had to do is softboot and it worked uff saved thanks mates .. any new modules i should try out ???
s off on h boot 1.56
i was tired of this xposed giving me problem so i decide to install a custom rom , well here comes a problem again the s off i tried all the methods the firewater the rumrunner renove nothing works i cant even get this android revelouting rom to work also an error regarding metdata permission any one pls help me with this situation
jithumyself said:
error regarding metdata permission any one pls help me with this situation
Click to expand...
Click to collapse
Wrong recovery. Please use the correct recovery.
Sent from my HTC One using Tapatalk
wrong recovery i dont get it mate.. i backed up a recovery with twrp and have the cusotm recovery twrp can u pls quide
jithumyself said:
wrong recovery i dont get it mate.. i backed up a recovery with twrp and have the cusotm recovery twrp can u pls quide
Click to expand...
Click to collapse
older recoveries which dont support selinux cause the "error regarding metadata permission"
if you have an m7_u or m7_ul get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Was done with that then tried to get s off well here goes again tried every method I can :crying: moonshine revone rum runner firewater I think with hoot 1.56 it won't work . Any help on that
jithumyself said:
Was done with that then tried to get s off well here goes again tried every method I can :crying: moonshine revone rum runner firewater I think with hoot 1.56 it won't work . Any help on that
Click to expand...
Click to collapse
if rumrunner and firewater aren't able to S-Off, you'll just have to stay on custom ROM (or a stock ROM, such as http://forum.xda-developers.com/showthread.php?t=2224752) until firewater is (IF) updated.
i really wanted to install the google play store edition for htc the purest form of android
Related
Hi.
Just tried to root my Htc one using this method: HTC One M7 How To ROOT EASIEST METHOD.
Unlocked the boot loader successfully.
Then downloaded newest TWRP Recovery Image openrecovery-twrp-2.6.3.0-m7.img
Followed the instructions
One thing was suspicious when entering fast boot:
*** Tampered *** <- dont't know if it's good or no ?
*** Unlocked ***
On top of the screen It wasn't shown tampered only unlocked ?
But everythinh went well, entered recovery mode using image and install the superuser.
And reboot. The su app was there, but after checking on two apps - phone wasn't rooted.
So download old image from TWRP 2.5.0.0
And after flashing it and enter the screen when u see buttons Install, Wipe,Backup ...
the Screen it's Freezed. Swipe to Unlock is not working.
And after hitting the power button the home button and < Blinking.
Also fastboot is not working. [ waiting for device ] only.
So how to restart it so i can flash a newer image to try root it again ?
Or maybe something different is wrong ?
Thank's
adascezary said:
Hi.
Just tried to root my Htc one using this method: HTC One M7 How To ROOT EASIEST METHOD.
Unlocked the boot loader successfully.
Then downloaded newest TWRP Recovery Image openrecovery-twrp-2.6.3.0-m7.img
Followed the instructions
One thing was suspicious when entering fast boot:
*** Tampered *** <- dont't know if it's good or no ?
*** Unlocked ***
On top of the screen It wasn't shown tampered only unlocked ?
But everythinh went well, entered recovery mode using image and install the superuser.
And reboot. The su app was there, but after checking on two apps - phone wasn't rooted.
So download old image from TWRP 2.5.0.0
And after flashing it and enter the screen when u see buttons Install, Wipe,Backup ...
the Screen it's Freezed. Swipe to Unlock is not working.
And after hitting the power button the home button and < Blinking.
Also fastboot is not working. [ waiting for device ] only.
So how to restart it so i can flash a newer image to try root it again ?
Or maybe something different is wrong ?
Thank's
Click to expand...
Click to collapse
It's not frozen, the old version uses different touchscreen drivers that why you can't press anything.
Use adb to reboot, and flash an up to date version of TWRP or CWM:
"adb reboot bootloader"
that will get you back to FASTBOOT USB.
nkk71 said:
It's not frozen, the old version uses different touchscreen drivers that why you can't press anything.
Use adb to reboot, and flash an up to date version of TWRP or CWM:
"adb reboot bootloader"
that will get you back to FASTBOOT USB.
Click to expand...
Click to collapse
Thank's for quick help.
It worked.
But flashed openrecovery-twrp-2.6.1.0-m7.img so the older one and still not rooted.
Try also with other images from TWRP. still nothing.
app keep saying that my phone is not rooted correctly
Any solution what's wrong ?
adascezary said:
Thank's for quick help.
It worked.
But flashed openrecovery-twrp-2.6.1.0-m7.img so the older one and still not rooted.
Try also with other images from TWRP. still nothing.
app keep saying that my phone is not rooted correctly
Any solution what's wrong ?
Click to expand...
Click to collapse
Try downloading this http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip and flash it in TWRP recovery.
Hit the thanks button if i helped
nkk71 said:
Try downloading this http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip and flash it in TWRP recovery.
Hit the thanks button if i helped
Click to expand...
Click to collapse
Great that solved my problem. Thank U. Can't locate that button. But will try harder.
Now I'm trying to install busybox wchich is failed of course because life would be to easy.
Already dig out that this is probably the read write protection problem and to solve this need to add new kernel module
or change my custom rom.
For me better will be adding the module only to install busybox from this solution:
http://forum.xda-developers.com/showthread.php?t=2230341&page=3
But where find command prompt ? Should go to recovery mode ?
Or maybe install the custom rom to avoid future problems?
But which one ?
adascezary said:
Great that solved my problem. Thank U. Can't locate that button. But will try harder.
Now I'm trying to install busybox wchich is failed of course because life would be to easy.
Already dig out that this is probably the read write protection problem and to solve this need to add new kernel module
or change my custom rom.
For me better will be adding the module only to install busybox from this solution:
http://forum.xda-developers.com/showthread.php?t=2230341&page=3
But where find command prompt ? Should go to recovery mode ?
Or maybe install the custom rom to avoid future problems?
But which one ?
Click to expand...
Click to collapse
Didnt know about the busybox problem oops
Anyway, what's your goal? Custom ROM, Stock ROM, etc??
If you want to stay fully stock, you could use one of the "Guru Reset" ROMs: http://www.htc1guru.com/downloads/stock-rom-downloads/ (I believe those include superuser etc. which you can select during flashing in AROMA)
Otherwise, the custom ROMs out there are all great, it's all personal preference. They each have their own "pros and cons" IF we can say that, but they are all excellent.
You'll have to experiment to see which one works for you
nkk71 said:
Didnt know about the busybox problem oops
Anyway, what's your goal? Custom ROM, Stock ROM, etc??
If you want to stay fully stock, you could use one of the "Guru Reset" ROMs:
link (I believe those include superuser etc. which you can select during flashing in AROMA)
Otherwise, the custom ROMs out there are all great, it's all personal preference. They each have their own "pros and cons" IF we can say that, but they are all excellent.
You'll have to experiment to see which one works for you
Click to expand...
Click to collapse
Well i don't know what I'm looking yet. Change from Ios to android.
By now trying to finish setting up my phone so can start using it.
When was searching forum just found the solution - someone had the same problem installing busybox.
That's way came up with that solution to solve my problem.
If someone have solution how to install busybox.
Was trying two different busy boxes both are crashing after install.
Don't want start another topic
Ok there is solution for that too.
http://forum.xda-developers.com/showthread.php?t=1929852
Thank you for your help.
Now can read more
Has anyone experienced this? I have to force reboot when I load into recovery.
It's a new phone from the factory, it's unlocked and has TWRP 2.6.00
Drakeskakes said:
Has anyone experienced this? I have to force reboot when I load into recovery.
It's a new phone from the factory, it's unlocked and has TWRP 2.6.00
Click to expand...
Click to collapse
please specify the device, or just post a fastboot getvar all (excluding IMEI and s/n)
2.6.0.0 sound kind of outdated
Sounds like a firmware issue, you need be firnware with new touch screen driver
HTC One
Like nkk71 said get TWRP 2.6.3.4
I just went with Clockwork. I only wanted to use TRWP because my old phone had it, and I hate learning new things. Now I'm trying to do the OTA Kitkat update and it's not working. I hate these stupid phones
Drakeskakes said:
I just went with Clockwork. I only wanted to use TRWP because my old phone had it, and I hate learning new things. Now I'm trying to do the OTA Kitkat update and it's not working. I hate these stupid phones
Click to expand...
Click to collapse
you can't get OTA update with any custom recovery
you need stock recovery....
If you want help, post your fastboot getvar all minus serial no and IMEI
clsA said:
you can't get OTA update with any custom recovery
you need stock recovery....
If you want help, post your fastboot getvar all minus serial no and IMEI
Click to expand...
Click to collapse
So, to upgrade to Kit-kat then CM11 ....do I have to do a complete factory reset, then OTA update, then do unlock/root/s-off and install rom?
Why would you install kitkat then Cm 11?
Sent from my HTC One using Tapatalk 4
clsA said:
Why would you install kitkat then Cm 11?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Doesn't CM11 need to piggy back off Kitkat? I always hear "CM for Kitkat" and when I go to Goomanager, it doesn't give me CM11 only 10.1
All I want to CM on my phone, Im rooted, have CMW premium, SUperSU and unlocked...
When I go to CWM, it doesn't work, when I try and DL from Goo, it doesn't work, when I try to download from CM app, doesn't work. I'm going to throw this phone across the room. I hve done custom roms before, but always using a toolkit for PC. I only have access to a mac for the time being
Drakeskakes said:
Doesn't CM11 need to piggy back off Kitkat? I always hear "CM for Kitkat" and when I go to Goomanager, it doesn't give me CM11 only 10.1
Click to expand...
Click to collapse
No and why do you have 2 threads going ?
here's CM 11
http://forum.xda-developers.com/showthread.php?t=2579229
The Device must be unlocked and equipped with a Recovery,
you need a ROM.zip and optional GAPPS,the Download Links will you find here.
At first,make a Nandroid-Backup of your existing system!
When you first time flash the ROM or you changed from another ROM-Base,
do a Full Wipe via Recovery,flash the ROM, and then the GAPPS.
Restart to System,configure and enjoy CM11.
Click to expand...
Click to collapse
Are you still with hboot 1.44? Upgrade to have a newer touch driver pls
Sent from my HTC One using xda app-developers app
clsA said:
No and why do you have 2 threads going ?
here's CM 11
http://forum.xda-developers.com/showthread.php?t=2579229
Click to expand...
Click to collapse
This thread was only about TWRP not working, but someone piggy backed off this conversations after I started the other one.
clsA said:
No and why do you have 2 threads going ?
here's CM 11
http://forum.xda-developers.com/showthread.php?t=2579229
Click to expand...
Click to collapse
is GSM version for Sprint...before I go through with the DL
Drakeskakes said:
is GSM version for Sprint...before I go through with the DL
Click to expand...
Click to collapse
No... Why are you in the GSM forums ??
you most likely have the wrong recovery installed also
does your recovery file say m7wls ?
you need to be here getting your files
http://forum.xda-developers.com/sprint-htc-one
clsA said:
No... Why are you in the GSM forums ??
you most likely have the wrong recovery installed also
does your recovery file say m7wls ?
you need to be here getting your files
http://forum.xda-developers.com/sprint-htc-one
Click to expand...
Click to collapse
I have the proper recovery installed
Recovery-clockwork-touch-6.0.3.2-m7spr.img
I just tried this
Install zip from sdcard->
choose zip from sdcard->
0/ ->
Download ->
cm-11-20140309-NIGHTLY-myspr.zip
The log says
Installing update...
set_metadata_recursive:some changes failed
E:Error in /sdcard/o/Downoad/cm-11-20140309-NIGHTLY-M7spr.zip
(Status 7)
Installion Aborted
Drakeskakes said:
I have the proper recovery installed
Recovery-clockwork-touch-6.0.3.2-m7spr.img
I just tried this
Install zip from sdcard->
choose zip from sdcard->
0/ ->
Download ->
cm-11-20140309-NIGHTLY-myspr.zip
The log says
Installing update...
set_metadata_recursive:some changes failed
E:Error in /sdcard/o/Downoad/cm-11-20140309-NIGHTLY-M7spr.zip
(Status 7)
Installion Aborted
Click to expand...
Click to collapse
During the install, it aborted and now the stock rom won't load. It keep going into recovery and I have nothing to load it to. I can't shut it off, and I would like to just work on it tommorow. If it dies, I'm worried I wont be able to charge it back up to work on it. Now I'm pretty worried
Nevermind CM11 now working, switched from CWM to TWRP andf it works great
I rooted my phone and then unrooted it in order to update on Sense 6. Everything went well with unroot procedure except superuser app stays in app tray. Since then the phone is locked and on stock. Now I need to return the damn thing because of bad camera. I tried to remove superuser app by deleting system/apps/superuser.apk and system/xbin/su in ES File Explorer but it said that those files cannot be deleted. I also tried to uninstall the app through Google Play but that didn't work either.
I realise that there probably won't be any left options except to reroot my phone, deleting superuser app and then unroot again but I have to ask is there any way to remove it without reroot?
I'm scared of reroot because I don't know would I be able to unroot again and put the phone back on stock ready for service or RMA. I'm on Sense 6 (6.09.401.10), Android version 4.4.3. The phone is still under warranty.
Please help with any available info. I'm noob at this so I even don't know where should i start or what questions to ask.
Edit:
Rooted by the help of this tutorial
Unrooted by the help of this thread from user nkk71
Anyone on this?
jhercog said:
Anyone on this?
Click to expand...
Click to collapse
You need root to access those system folders, only thing I can suggest is Factory Reset from the settings menu. If that doesn't work try factory reset from Stock recovery and even the bootloader factory reset is worth a try.
Not sure it will help though I don't think it touches the system partitions.
What method did you use to s-off your device originally?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
You need root to access those system folders, only thing I can suggest is Factory Reset from the settings menu. If that doesn't work try factory reset from Stock recovery and even the bootloader factory reset is worth a try.
Not sure it will help though I don't think it touches the system partitions.
What method did you use to s-off your device originally?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I did factory reset from boot loader menu and tried to delete those files again but that didn't work.
I don't know how to do factory reset from Stock Recovery. Would you care to explain?
To be honest, I don't remember how did I get s-off originally.
jhercog said:
I did factory reset from boot loader menu and tried to delete those files again but that didn't work.
I don't know how to do factory reset from Stock Recovery. Would you care to explain?
To be honest, I don't remember how did I get s-off originally.
Click to expand...
Click to collapse
Boot to the bootloader and Select "Recovery" the screen will go black for a short period then display a picture of a phone with red exclamation. Don't worry it's normal.
Hold volume up and press (don't hold just press) power to reveal the stock recovery menu, you will see some errors about can't mount sd card again this is normal in stock recovery.
The reason I asked about s-off method was if you used Sunshine you can use it again on the same device without paying the fee. But if you have to root again you will need s-off to return to stock. And there's no guarantees the older (free) methods will work now your updated to the latest firmware.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Boot to the bootloader and Select "Recovery" the screen will go black for a short period then display a picture of a phone with red exclamation. Don't worry it's normal.
Hold volume up and press (don't hold just press) power to reveal the stock recovery menu, you will see some errors about can't mount sd card again this is normal in stock recovery.
The reason I asked about s-off method was if you used Sunshine you can use it again on the same device without paying the fee. But if you have to root again you will need s-off to return to stock. And there's no guarantees the older (free) methods will work now your updated to the latest firmware.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Well, that doesn't work. Still stuck with SuperSu in my app drawer.
Sunshine method doesn't ring any bells to me. I didn't use it most probably.
So, I probably have to reroot, unlock, s-off to be able to uninstall SuperSu? Any advices on doing that on my firmware? Would I be able to relock, unroot and s-on again?
Would it be possible to use something like Z4Root app to temporary root the device and then uninstall SuperSu? Or root/unlock/s-off method is necessary?
Does anybody have a safe method for removing SuperSu under these circumstances and is willing to explain it in details so noob like me can understand it and do it by himself?
jhercog said:
Does anybody have a safe method for removing SuperSu under these circumstances and is willing to explain it in details so noob like me can understand it and do it by himself?
Click to expand...
Click to collapse
Outside of what Danny201281 stated there is really not much you can do except go thru root again to remove the files. There is one long shot that might work; go to Google Play Store > My Apps and scroll down to see if SuperSU is present. Click on it and see if the Uninstall option is there. Other than that sorry, I'm out of ideas.
jhercog said:
Does anybody have a safe method for removing SuperSu under these circumstances and is willing to explain it in details so noob like me can understand it and do it by himself?
Click to expand...
Click to collapse
Under Settings for SuperSU, doesn't it have an option for Full Unroot?
majmoz said:
Outside of what Danny201281 stated there is really not much you can do except go thru root again to remove the files. There is one long shot that might work; go to Google Play Store > My Apps and scroll down to see if SuperSU is present. Click on it and see if the Uninstall option is there. Other than that sorry, I'm out of ideas.
Click to expand...
Click to collapse
Yeah I tried that but that doesn't work either.
vaporjet said:
Under Settings for SuperSU, doesn't it have an option for Full Unroot?
Click to expand...
Click to collapse
I can't launch SuperSu because there is no SU binary installed.
jhercog said:
I can't launch SuperSu because there is no SU binary installed.
Click to expand...
Click to collapse
Doesn't sound right that SuperSU can survive a factory reset, unless it is baked in. Are you sure you're running a stock ROM?
vaporjet said:
Doesn't sound right that SuperSU can survive a factory reset, unless it is baked in. Are you sure you're running a stock ROM?
Click to expand...
Click to collapse
Yes, because OTA updates are working as expected. As far as I know, I wouldn't be able to receive and install OTA updates if I would run anything other than stock ROM.
Anybody have some good advice or link (preferably detailed step by step instructions) on how to safely root under these conditions, remove SuperSu and then unroot back to stock?
jhercog said:
Anybody have some good advice or link (preferably detailed step by step instructions) on how to safely root under these conditions, remove SuperSu and then unroot back to stock?
Click to expand...
Click to collapse
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Go into twrp choose Advanced / file manager go to system/app delete su and Superuser.apk
could also be under /superuser/su and Superuser.apk
reboot to the bootloader and flash stock recovery ...done
I'm not sure if you have it but stock recovery's are here >
Stock recovery collection
http://forum.xda-developers.com/showthread.php?t=2545227
I also Googled and found this
Boot your phone to TWRP recovery mode by turn off your phone then presses Vol up + Power to boot into bootloader then choose RECOVERY. There is a more simple way, by using “adb reboot recovery”.
Once came into TWRP main menu, now tap Mount -> Mount system then taps Home.
Tap Advanced -> File Manager, browse to “/system/xbin” folder. From there delete su, daemonsu or busybox if it exists. Also browse to “/system/app” the get rid of Superuser.apk.
Now Supersu doesn't come back when I reboot and root checker tells me my phone isn't rooted
Click to expand...
Click to collapse
clsA said:
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Go into twrp choose Advanced / file manager go to system/app delete su and Superuser.apk
could also be under /superuser/su and Superuser.apk
reboot to the bootloader and flash stock recovery ...done
I'm not sure if you have it but stock recovery's are here >
Stock recovery collection
http://forum.xda-developers.com/showthread.php?t=2545227
Click to expand...
Click to collapse
I'm sorry for asking noob questions (in bad English) but Is it safe to do on Sense 6 Update?
M7_UL PVT SHIP S-ON
HBOOT-1.57.0000
RADIO-4T.29.3218.08
OpenDSP-v32.120.274.0909
OS-6.09.401.10
Do I need S-Off? Would I than be able to claim my warranty with all traces of rooting removed?
Is there anything I should know in order to keep myself out of screwing things up beyond repair?
clsA said:
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Go into twrp choose Advanced / file manager go to system/app delete su and Superuser.apk
could also be under /superuser/su and Superuser.apk
reboot to the bootloader and flash stock recovery ...done
I'm not sure if you have it but stock recovery's are here >
Stock recovery collection
http://forum.xda-developers.com/showthread.php?t=2545227
I also Googled and found this
Click to expand...
Click to collapse
Oh, and my version-main is 6.09.401.10 as fastboot 'getvar version-main' stated. I can't find it on the Stock recovery page you recommended. The nearest is 6.09.401.5. Can I use that version or...?
jhercog said:
Oh, and my version-main is 6.09.401.10 as fastboot 'getvar version-main' stated. I can't find it on the Stock recovery page you recommended. The nearest is 6.09.401.5. Can I use that version or...?
Click to expand...
Click to collapse
You can extract the stock recovery from the OTA the stock recovery is inside the firmware.zip >> https://www.androidfilehost.com/?fid=95784891001603795
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
Hello my friends, i have opened the bootloader in my phone a htc one m7 And I've developed a program SuperSU
In the phone and you Login to recovery mode and I did the following
install zip from sdcard
choose zip from sdcard
UPDATE-SuperSU-v2.40.zip
Yes – Install UPDATE-SuperSU-v1.25.zip
and after that Phone has done re-run and the show has become a black screen.
can anyone help me
and when i click on the factory reset he is going to clockworkmod recovery v.6.0.3.1 screen
what i have to do????
thank you
abede said:
Hello my friends, i have opened the bootloader in my phone a htc one m7 And I've developed a program SuperSU
In the phone and you Login to recovery mode and I did the following
install zip from sdcard
choose zip from sdcard
UPDATE-SuperSU-v2.40.zip
Yes – Install UPDATE-SuperSU-v1.25.zip
and after that Phone has done re-run and the show has become a black screen.
can anyone help me
and when i click on the factory reset he is going to clockworkmod recovery v.6.0.3.1 screen
what i have to do????
thank you
Click to expand...
Click to collapse
First you need to post your "fastboot getvar all" output. Then, you need to change your recovery to TWRP because it's recomended for our phone. Most likely you flashed outdated SU, and that caused bootloop. But, as I said, post your "fastboot getvar all" output, but delete your IMEI and serial no. That way we will be able to help you
^^Definitely caused by an outdated SU bin if your phone is running a lollipop rom. You need at least 2.46 on Lollipop. Reflashing the correct versio might fix your problem, otherwise you'll need to reflash your rom.
abede said:
(...)
UPDATE-SuperSU-v2.40.zip
Yes – Install UPDATE-SuperSU-v1.25.zip
(...)
Click to expand...
Click to collapse
strange the zip name is 2.40 and then its saying 1.25.....
alray said:
^^Definitely caused by an outdated SU bin if your phone is running a lollipop rom. You need at least 2.46 on Lollipop. Reflashing the correct versio might fix your problem, otherwise you'll need to reflash your rom.
strange the zip name is 2.40 and then its saying 1.25.....
Click to expand...
Click to collapse
sorry it's 2.40 version
but can you give me video or article explain reflash rom.