Related
HELP!!!!!!!!!!!!!!!!!!!!!!!! Have had several HTC Devices over the years so went about my usual business of Unlocking Bootloader via HTC Dev, Root obtained Supersu (Thanks again Chainfire) and installed the fabulous looking CWM Recovery by Phil.......
This is where the fairytale ends.... I can not install ANY zip rom at all, I backed up my stock rom which has vanished from both internal and external sd and can not find a RUU Rom anywhere.
UPDATE!! SIDELOADED GPE ROM WHICH WORKED A CHARM AND MY DEVICE IS BACK!!
jody04c said:
HELP!!!!!!!!!!!!!!!!!!!!!!!! Have had several HTC Devices over the years so went about my usual business of Unlocking Bootloader via HTC Dev, Root obtained Supersu (Thanks again Chainfire) and installed the fabulous looking CWM Recovery by Phil.......
This is where the fairytale ends.... I can not install ANY zip rom at all, I backed up my stock rom which has vanished from both internal and external sd and can not find a RUU Rom anywhere.
Simply.. MY NEW HTC ONE M8 IS DEAD!!!!!!!!!!!!!
HELP ME PLEASE
Click to expand...
Click to collapse
can you get into recovery
Does ADB still work?
When yes try flashing TWRP for the M8 then and sideload a custom Rom and....don't panic.
In recovery do you see anything on the internal sd card?
There might be an issue seeing the extrnal so all your data might be there safe,
But sounds like you will need to use "adb push <zip> /sdcard/ to get the file to a location recovery can see it.
Lets not toss "bricked" around, if you can get to hboot you are going to be ok
After a 2am sit down I managed to side load a Google edition ROM (nothing else would work) and my soft bricked M8 is back to life.
H>A>P>P>Y!!!
Hello Everyone,
I need help with my HTC Desire 816 Here is my issue :
I rooted my device using this tutoriol : http://forum.xda-developers.com/showthread.php?t=2775801
everything went smooth but when i open SuperSU it says Binary needs to be updated but i'm unable to update it in anyway.
After root the phone restarts randomly.
I even tried to unroot using SuperSU and other ways but nothing seems to work.
I also tried to Disable Write Permission and that's when it all went wrong.
Now my phone keeps rebooting and i can't even use it
N.B: I always had an iphone, it's my first android phone so i'm a Newbie in rooting.
Any help is REALLY appreciated.
Thanks.
the link doesn't work, if you mean v_superuser guide the post was for kitkat
for lollipop you need to flash supersu v 2.46 I guess, atleast that what I did
the write protection post indicated in his guide also was for kitkat
try flashing stock if you took a backup b4 rooting to stop the random restarts, flash supersu and disable write protection for lollipop http://forum.xda-developers.com/des...-disable-writeprotection-sense-stock-t3091456
[/COLOR]
MaE_sTrO said:
Hello Everyone,
I need help with my HTC Desire 816 Here is my issue :
I rooted my device using this tutoriol http://forum.xda-developers.com/show....php?t=2775801
everything went smooth but when i open SuperSU it says Binary needs to be updated but i'm unable to update it in anyway.
After root the phone restarts randomly.
I even tried to unroot using SuperSU and other ways but nothing seems to work.
I also tried to Disable Write Permission and that's when it all went wrong.
Now my phone keeps rebooting and i can't even use it
N.B: I always had an iphone, it's my first android phone so i'm a Newbie in rooting.
Any help is REALLY appreciated.
Thanks.
Click to expand...
Click to collapse
Sorry your having these problems but as long as you can get into your boatloader they should be fixable. Hopefully you did a full nandroid backup of your phone after rooting before attempting any other flashes or mods but if you didn't then that's just friendly advice for any future flashes for everybody , me included. It's an easy step to skip(I've forgotten to do one myself) but it's the most important step to being able to easily restore from any problems.
Try to get into your boatloader by holding power button then volume down and hold. That should reboot into your bootloader and from there you can enter recovery and do a factory reset then wipe cache and dalvik cache then reboot system and see if that stops the bootloops. If not then you might need to find and reflash your stock recovery and relock your bootloader then find a flashable zip or executable RUU (rom utility update) and flash back to completely stock. If your in the U.S. HTC has the RUU executable files on their website in the downloads section(RUU not kernel). These you can either run from a P.C. as an executable program with your phone in fastboot or rename to your model specific firmware image and install to and flash from your phone's external SD card from your bootloader. The only issue would be if your system has been modified by the write permission mod you flashed then that would need to be removed before any signed stock update could work. What's your specific phone model( a5_"what") and are you in the U.S. or overseas?
EDIT: it's volume down not volume up. Volume up reboots the phone. Sorry, I use an app to do all of that now not my keys.
thoctor said:
[/COLOR]
Sorry your having these problems but as long as you can get into your boatloader they should be fixable. Hopefully you did a full nandroid backup of your phone after rooting before attempting any other flashes or mods but if you didn't then that's just friendly advice for any future flashes for everybody , me included. It's an easy step to skip(I've forgotten to do one myself) but it's the most important step to being able to easily restore from any problems.
Try to get into your boatloader by holding power button then volume down and hold. That should reboot into your bootloader and from there you can enter recovery and do a factory reset then wipe cache and dalvik cache then reboot system and see if that stops the bootloops. If not then you might need to find and reflash your stock recovery and relock your bootloader then find a flashable zip or executable RUU (rom utility update) and flash back to completely stock. If your in the U.S. HTC has the RUU executable files on their website in the downloads section(RUU not kernel). These you can either run from a P.C. as an executable program with your phone in fastboot or rename to your model specific firmware image and install to and flash from your phone's external SD card from your bootloader. The only issue would be if your system has been modified by the write permission mod you flashed then that would need to be removed before any signed stock update could work. What's your specific phone model( a5_"what") and are you in the U.S. or overseas?
EDIT: it's volume down not volume up. Volume up reboots the phone. Sorry, I use an app to do all of that now not my keys.
Click to expand...
Click to collapse
Thank you thoctor , as i said i'm a newbie in rooting so i didn't make full nandroid backup but thanks to you and after doing a factory reset the bootloops stopped, i'm able to use the phone now, but i think the write protection is still disabled, as i'm trying to use apps2sd and creating a new partition in the SD is not working, one more thing i'm unable to update SuperSu's binary too, thanks to your help and i would appreciate if you can help me further.
my model number : A5_ul and cidnum: HTC__E11 , and i'm in europe.
Roberto Nigel said:
the link doesn't work, if you mean v_superuser guide the post was for kitkat
for lollipop you need to flash supersu v 2.46 I guess, atleast that what I did
the write protection post indicated in his guide also was for kitkat
try flashing stock if you took a backup b4 rooting to stop the random restarts, flash supersu and disable write protection for lollipop http://forum.xda-developers.com/des...-disable-writeprotection-sense-stock-t3091456
Click to expand...
Click to collapse
Thanks Roberto
that's the exact way i tried to disable write protection, and that's when it all went wrong, but i retried it now it went smooth, but i think it didn't work , is there anyway to make sure if it's enabled or not ?
MaE_sTrO said:
Thank you thoctor , as i said i'm a newbie in rooting so i didn't make full nandroid backup but thanks to you and after doing a factory reset the bootloops stopped, i'm able to use the phone now, but i think the write protection is still disabled, as i'm trying to use apps2sd and creating a new partition in the SD is not working, one more thing i'm unable to update SuperSu's binary too, thanks to your help and i would appreciate if you can help me further.
my model number : A5_ul and cidnum: HTC__E11 , and i'm in europe.
Click to expand...
Click to collapse
No problem buddy. We've all been there trust me on that. You can update the binaries from within the SuperSU apps settings or in custom recovery. Check to verify you have the most current version from the play store and if not download it. Also you might try to wipe your cache and dalvik cache from within your custom recovery then reboot system and see if that fixes it. As for the WP mod there are some that get it to work right off the bat and others who have to add or remove a line in the lib files using a terminal emulator app but I've never personally used this mod as I have true S off on my 816 a5_chl. I use Link2SD not the one your talking about but the partitioning for the app I use is done on a P.C. using EaseUS partition manager. Is yours the same process?
thoctor said:
No problem buddy. We've all been there trust me on that. You can update the binaries from within the SuperSU apps settings or in custom recovery. Check to verify you have the most current version from the play store and if not download it. Also you might try to wipe your cache and dalvik cache from within your custom recovery then reboot system and see if that fixes it. As for the WP mod there are some that get it to work right off the bat and others who have to add or remove a line in the lib files using a terminal emulator app but I've never personally used this mod as I have true S off on my 816 a5_chl. I use Link2SD not the one your talking about but the partitioning for the app I use is done on a P.C. using EaseUS partition manager. Is yours the same process?
Click to expand...
Click to collapse
Yup i have the latest supersu, About the Link2SD i have it also installed, and i've done the partitions on pc , tried EXT2 , EXT4 amd fat32 nothing worked, after so many tries the last error i get is something like that ( bad magic number in superblock ). that's why i thought it has something to do with the WP.
so i should wipe the cache and dalvik cache and it will do no harm right ?(coz i'm really glad now since i got rid of the rebootloop and i can use my phone .
MaE_sTrO said:
Yup i have the latest supersu, About the Link2SD i have it also installed, and i've done the partitions on pc , tried EXT2 , EXT4 amd fat32 nothing worked, after so many tries the last error i get is something like that ( bad magic number in superblock ). that's why i thought it has something to do with the WP.
so i should wipe the cache and dalvik cache and it will do no harm right ?(coz i'm really glad now since i got rid of the rebootloop and i can use my phone .
Click to expand...
Click to collapse
Lol. I know how you feel. You can wipe those two all day long and nothing bad will happen. It's just a cache cleaner that clears out our any leftover files in the firmwares cache folders. System restore wipes the whole phone except for the external SD card and your personal downloads or data files. Custom delete can add those personal data files so be careful there but otherwise your good. Check settings to see in about phone if your SElinux permissions are set to enforcing or permissive. The mod is supposed to change them to permissive for it to work properly.
Also on link2SD set the new data partition to ext2 if your on a stock rom and set as primary then set the remaining partition for your normal storage(not app data) to fat32 (as that's the format the phone will let you view in your SD card) and also as primary. It was the write permissions that wasn't letting it work not the format because I've been down that road many times before I got mine right.
thoctor said:
Lol. I know how you feel. You can wipe those two all day long and nothing bad will happen. It's just a cache cleaner that clears out our any leftover files in the firmwares cache folders. System restore wipes the whole phone except for the external SD card and your personal downloads or data files. Custom delete can add those personal data files so be careful there but otherwise your good. Check settings to see in about phone if your SElinux permissions are set to enforcing or permissive. The mod is supposed to change them to permissive for it to work properly.
Also on link2SD set the new data partition to ext2 if your on a stock rom and set as primary then set the remaining partition for your normal storage(not app data) to fat32 (as that's the format the phone will let you view in your SD card) and also as primary. It was the write permissions that wasn't letting it work not the format because I've been down that road many times before I got mine right.
Click to expand...
Click to collapse
thanks for the fast response , i wiped the cache and i still can't update the binary i get this msg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if i press normal the phone reboots, if i press TWRp/CWM ( since i rooted with cwm recovery) it reboots enters recovery starts loading then reboots and i get the same msg about the update again.
Also about the SElinux i can't find it in about :S.
MaE_sTrO said:
thanks for the fast response , i wiped the cache and i still can't update the binary i get this msg
if i press normal the phone reboots, if i press TWRp/CWM ( since i rooted with cwm recovery) it reboots enters recovery starts loading then reboots and i get the same msg about the update again.
Also about the SElinux i can't find it in about :S.
Click to expand...
Click to collapse
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
EDIT: try to reflash in recovery the most current flashable zip for SuperSU found on chainfires website for SuperSU. I believe it's 2.4.6 but don't quote me on that just make sure it's the most current one which it will be on his site. That may help the binary issue. Even if the one you flashed is the most current flashable zip flash it again.
thoctor said:
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
Click to expand...
Click to collapse
Just flashed TWRP.
tried to update binary same thing happend but now i see in TWRP when it tries to update it says no MD5
thoctor said:
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
EDIT: try to reflash in recovery the most current flashable zip for SuperSU found on chainfires website for SuperSU. I believe it's 2.4.6 but don't quote me on that just make sure it's the most current one which it will be on his site. That may help the binary issue. Even if the one you flashed is the most current flashable zip flash it again.
Click to expand...
Click to collapse
Flashed TWRP reflashed SuperSU from chainfires website , same issue , but now i can see when it tries to update in TWRP it says no MD5!!!
and i assure u i can't find SElinux anywhere in about !!!!
MaE_sTrO said:
Flashed TWRP reflashed SuperSU from chainfires website , same issue , but now i can see when it tries to update in TWRP it says no MD5!!!
and i assure u i can't find SElinux anywhere in about !!!!
Click to expand...
Click to collapse
No problem , Don't worry about the permissions for now. The MD5 is the checksum that verifies the file isn't corrupt but if you got it from the chainfire site your fine. Try to update the binary thru twrp or in the SuperSU app and select your recovery as the way you want to update and see what happens.
Also did you have MD5 check enabled in TWRP? I do in mine for file verification but just wondering what yours was set to when you got that notice. It shouldn't stop SuperSU from flashing either way it's just a file verifier.
---------- Post added at 12:56 AM ---------- Previous post was at 12:18 AM ----------
the binaries are what SuperSU uses to get and maintain root . If they are incomplete or corrupt then they have to be reflashed over with an uncorrupted version. That is usually why people keep getting the notice to update the binaries and when they do they can't because they are not complete or corrupt and need to be totally removed i.e. reflashing, which you did, or unrooting from the SuperSU app itself and redownloading again from the play store. This is what I've read on several help sites for this issue. Just wanted to pass along the why not just the what.
Again thank you for giving me so much information so i can understand the way things work and what i am doing, MD5 check was disabled i tried updating binary thru twrp i also tried enabling the MD5 both gave the same result, but the weird thing that it says done proccessing zip file , but when it reboots the update msg shows again, another thing when updating through twrp i noticed this line " full SElinux is present ".
MaE_sTrO said:
Again thank you for giving me so much information so i can understand the way things work and what i am doing, MD5 check was disabled i tried updating binary thru twrp i also tried enabling the MD5 both gave the same result, but the weird thing that it says done proccessing zip file , but when it reboots the update msg shows again, another thing when updating through twrp i noticed this line " full SElinux is present ".
Click to expand...
Click to collapse
No problem. To me that's the whole point of helping here on XDA is to make these things easier to understand for the person asking for assistance so they don't have to come back for the same thing again.Also because I was here in the same situations just a year or so ago and others helped me understand and I'm not a rocket scientist by any means .
Try to verify root through the root checker app on the play store. Almost positive it will say not rooted but it can't hurt to verify. Then , again, I would try to uninstall SuperSU through the app itself in it's settings as I'm almost positive the binaries are corrupted or incomplete and that's why you keep getting the same "update binaries message". If I sound like a broken record it's because I have learned from multiple Android device issues that sometimes for whatever reason things don't take and some combination of things might happen to alter the reason and trying the same thing again fixed it after coming back to it. I would also download SuperSU again but on a different device(laptop, computer) from chainfires site and reflash it just on the off chance the file is corrupted . Although at this point it's unlikely I know.
Lastly I would do an advanced wipe in TWRP recovery and add system to Data and Dalvik cache and cache from the factory reset. Not internal storage or SD card. Then I would flash the newly downloaded SuperSU and wipe Dalvik and cache then reboot system. Back up your contacts and numbers through Google's own backup in settings and they may already be backed up and use Super Backup app as well to save to external SD card as it can backup the same things.
thoctor said:
No problem. To me that's the whole point of helping here on XDA is to make these things easier to understand for the person asking for assistance so they don't have to come back for the same thing again.Also because I was here in the same situations just a year or so ago and others helped me understand and I'm not a rocket scientist by any means .
Try to verify root through the root checker app on the play store. Almost positive it will say not rooted but it can't hurt to verify. Then , again, I would try to uninstall SuperSU through the app itself in it's settings as I'm almost positive the binaries are corrupted or incomplete and that's why you keep getting the same "update binaries message". If I sound like a broken record it's because I have learned from multiple Android device issues that sometimes for whatever reason things don't take and some combination of things might happen to alter the reason and trying the same thing again fixed it after coming back to it. I would also download SuperSU again but on a different device(laptop, computer) from chainfires site and reflash it just on the off chance the file is corrupted . Although at this point it's unlikely I know.
Lastly I would do an advanced wipe in TWRP recovery and add system to Data and Dalvik cache and cache from the factory reset. Not internal storage or SD card. Then I would flash the newly downloaded SuperSU and wipe Dalvik and cache then reboot system. Back up your contacts and numbers through Google's own backup in settings and they may already be backed up and use Super Backup app as well to save to external SD card as it can backup the same things.
Click to expand...
Click to collapse
i went through your instructions , and after the last steps now i'm stuck on HTC logo
i can't even turn it off or get into recovery!!!!
i managed somehow to get into recovery no it says no OS installed , i guess i F**k it up right ?
MaE_sTrO said:
i went through your instructions , and after the last steps now i'm stuck on HTC logo
i can't even turn it off or get into recovery!!!!
i managed somehow to get into recovery no it says no OS installed , i guess i F**k it up right ?
Click to expand...
Click to collapse
No you didn't f***k it up I f*****d it up. I was thinking of what I do on my custom rom when I can't get something fixed and I brainfarted and forgot for a second your on a stock rom. That's on me not you so be mad at me not yourself. The good thing is it's fixable. I just flash a new custom rom but with stock it's a little bit different. You need to flash back the stock recovery which I will find and link you to and then lock the bootloader and flash back your stock Rom which I will also link you to. I am so sorry. I was in a doctor's office waiting room and my mind was on other things but that's no excuse just an explanation. Below is the link to stock lollipop for the a5_ul European version
Better than what I first linked us this forum page from Nukaru a few posts down in this forum for the stock a5_ul. He had links to both the stock recovery and stock rom file with detailed instructions on how to get the stock rom back on your phone. I know it works because he had a problem and figured all this out himself then wrote a detailed tutorial on how he fixed his. Link below.
http://forum.xda-developers.com/desire-816/help/a5ul-unable-to-flash-ruu-t3294835/page2
thoctor said:
No you didn't f***k it up I f*****d it up. I was thinking of what I do on my custom rom even I can't get something fixed and I brainfarted and forgot for a second your on a stock rom. That's on me not you so be mad at me not yourself. The good thing is it's fixable. I just flash a new custom rom but with stock it's a little bit different. You need to flash back the stock recovery which I will find and link you to and then lock the bootloader and flash back your stock Rom which I will also link you to. I am so sorry. I was in a doctor's office waiting room and my mind was on other things but that's no excuse just an explanation. Below is the link to stock lollipop for the a5_up European version
Link to stock lollipop rom below
https://www.androidfilehost.com/?fid=23991606952595166
Click to expand...
Click to collapse
Never mind i have nothing to loose as long as it's fixable lol, anyway i'll try this rom now
note: when i relock boot loader it says RELOCKED with S-ON does this matters?
MaE_sTrO said:
Never mind i have nothing to loose as long as it's fixable lol, anyway i'll try this rom now
note: when i relock boot loader it says RELOCKED with S-ON does this matters?
Click to expand...
Click to collapse
No, hold off on that first link I have a better one buddy. Just edited it above. No, "relocked S on" is what it's supposed to say so your fine but don't lock it yet or if you already did unlock it using the same unlock token you used on htc developers to unlock it in the first place . Then you flash back your stock recovery. Then relock your bootloader. Then you flash back your stock rom in that order.
thoctor said:
No hold off on that first link I have a better one buddy. Just edited it above. No relocked S on is what it's supposed to say so your fine but don't lock it yet orv I'd your already did unlock it using the same unlock token you used on htc developers to unlock it in the first place .
Click to expand...
Click to collapse
Alright downloading now...
Hi everyone,
Stuck in BootLoop After Installing BETA-SuperSU-v2.68-20160228150503.zip. I installed using TWRP. Install looks it went fine then I rebooted and bootloop.
HTC M9 (t-mobile)
Unlocked
TWRP version - twrp-3.0.0-2-hima
After installing "BETA-SuperSU-v2.68-20160228150503.zip" my phone is stuck in bootloop. It has rebooted at least 5 times. I then was able to get into HTC download mode.
What can I do now? I have a full nandroid backup.
cloves said:
Hi everyone,
Stuck in BootLoop After Installing BETA-SuperSU-v2.68-20160228150503.zip. I installed using TWRP. Install looks it went fine then I rebooted and bootloop.
HTC M9 (t-mobile)
Unlocked
TWRP version - twrp-3.0.0-2-hima
After installing "BETA-SuperSU-v2.68-20160228150503.zip" my phone is stuck in bootloop. It has rebooted at least 5 times. I then was able to get into HTC download mode.
What can I do now? I have a full nandroid backup.
Click to expand...
Click to collapse
Restore your boot partition or dirty flash rom
Fixed
Thanks thicklizard for the quick reply,
Ended up booting back into twrp and installing BETA-SuperSU-v2.65-20151226141550.zip (aka version 2.65). Connected phone the PC while I was in TWRP, copied older zip file then installed. That fixed the issue and now I am rooted.
cloves said:
Thanks thicklizard for the quick reply,
Ended up booting back into twrp and installing BETA-SuperSU-v2.65-20151226141550.zip (aka version 2.65). Connected phone the PC while I was in TWRP, copied older zip file then installed. That fixed the issue and now I am rooted.
Click to expand...
Click to collapse
Im having the same issues i flashed over the supersu 2.65 but still stock... what older zip file did u install?
willardwellls said:
Im having the same issues i flashed over the supersu 2.65 but still stock... what older zip file did u install?
Click to expand...
Click to collapse
Flashed via twrp 3.0.0-2
This is the file:
https://download.chainfire.eu/752/SuperSU
FYI, if you are flashing a ROM, sometimes they have superSU already built in. So no need to flash your own superSU. That is the case with Viper ROM. Also make sure your firmware matches the firmware that the rom is using.
I had the same problem with SuperSU 2.76. I wiped dalvik cache and cache twice, flashed SuperSU 2.64 and no more bootloop. No backup, stock ROM. I almost crapped myself a little. About to give this thing it's first ROM flash.
Just had the same problem. Put on 2.65 and it's now booting into the OS. Thanks!
Thanked God i found this post, tried latest stable also beta seems bootloop never ends. Try v2.6 all become alive. Many thanks Sir
Same problem after installing latest SuperSu version from TWRP recovery: eternal bootloop. I didn't know what was wrong and tried different supersu versions but I became reluctant to keep trying that method after the second time... Gladly, I found your thread before doing anything else (even posting myself a thread) and now I can continue my evil rooting plans :victory: Thank you for asking and thanks for replying you prevented me to re-lock my phone and do everything from scratch. It's my first root
You're welcome guys, rooting this htc has been the best thing i have done. Let's keep the HTC community in here alive and well!
I recommend once you get the root part done backup then install xposed framework. No ads, YouTube play back without screen being on, best software once you are rooted.
Sent from my HTC One M9 using Tapatalk
cloves said:
You're welcome guys, rooting this htc has been the best thing i have done. Let's keep the HTC community in here alive and well!
I recommend once you get the root part done backup then install xposed framework. No ads, YouTube play back without screen being on, best software once you are rooted.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I beg to differ about xposed. One wrong mod and you're phone is bricked.
Beamed in by telepathy.
I have not had any problems with exposed and that's why I said make a backup on your card. I have installed multiple Xposed modules and have not had any issues I have not seen anybody break the phone either. As I mentioned make a trip back up what is the point of rooting your phone if you're not going to use it to its full potential that's just me
Sent from my HTC One M9 using Tapatalk
Me too - Bootloop
I have an AT&T HTC One M9. Bootloader is HtcDev Unlocked, S-On, and TWRP is installed...
I previously messed up my phone bad by trying to install a OS ROM that didn't work right... So, I used my PC to overwrite it with the HTC OTA version, and that worked. I went into the M9 and tried to download and run SunShine, to get S-OFF, but it said it couldn't temproot, I don't know why, it's pissing me off, and SunShine suggested I root the device with another means. I downloaded SuperSU 2.69 and tried that, it installed okay (I guess) and said it might loop a few times. Try 100! Infinite loop. I tried SuperSU 2.65, but it said, "it's already patched!" and the system ROM had not been backed up. (I'm assuming SuperSU patches whatever is in the system partition?)
Anyhow, it's currently stuck in an infinite loop. I'm going to try re-putting the HTC OTA system ROM on it (great, I lose another half-day at this), and then re-try SuperSU 1.65.
Any idea why SunShine won't S-OFF a device? Why won't temproot work? Any other (good) way to root it?
Twrp question?
I have twrp 3.0.0 installed I make a backup of system and boot... when I boot in the first time on twrp displays a message saying something about OTA protection if I want to receive otas and protect the recovery??? What is that... sorry for my bad English is not my mother language...
thanks dude
Skorpyun812 said:
I had the same problem with SuperSU 2.76. I wiped dalvik cache and cache twice, flashed SuperSU 2.64 and no more bootloop. No backup, stock ROM. I almost crapped myself a little. About to give this thing it's first ROM flash.
Click to expand...
Click to collapse
i am stuck and say my phone going to crab but your post save me
cheers
---------- Post added at 10:53 AM ---------- Previous post was at 10:51 AM ----------
White91 said:
I have twrp 3.0.0 installed I make a backup of system and boot... when I boot in the first time on twrp displays a message saying something about OTA protection if I want to receive otas and protect the recovery??? What is that... sorry for my bad English is not my mother language...
Click to expand...
Click to collapse
i think your s-on on bootloader mape it off then install recovery
Hi, I have and HTC One M8 6.0 with twrp 2.8.7.0. When I was going to turn of my phone to flash supersu, it gave me the option to install it there. So I said yes on the twrp menu. It never turned on again(stuck in the logo). I can access the bootloader but I think that usb debugging is off. In bootloader when you go to factory reset, it gives an error in twrp(failed). Is there anyway I cant lock the bootloader because usb debigging is off, when doing the steps to lock the bootloader(the ones in htcdev), it says <waiting for device>. I have nothing in the phone right now. Any way to fix the bootloop?
Thanks.
pasatmalo said:
Is there anyway I cant lock the bootloader because usb debigging is off
Click to expand...
Click to collapse
Relocking bootloader is done by fastboot, not adb. Fastboot and adb are related, but different requirements:
adb: only worksin OS or alternately TWRP. Requires debugging on.
fastboot: Only works in bootloader-fastboot mode, does not require debugging on.
However, I don't immediately suggest relocking the bootloader (presumably to RUU to stock); at least until trying some other things (below). As it may be possible to just do the root properly and make the phone work; rather than RUU and starting over.
pasatmalo said:
Hi, I have and HTC One M8 6.0 with twrp 2.8.7.0. When I was going to turn of my phone to flash supersu, it gave me the option to install it there.
Click to expand...
Click to collapse
The TWRP root option doesn't work. That is the whole reason for flashing SuperSU.
Also, you should use SuperSU current stable version 2.76. Some previous builds will also probably be fine, but you may need to flash an insecure kernel separately on some older versions for the full system root. SuperSU builds before 2.52 or so simply will not work on Marshmallow, and will result in being stuck on the HTC logo screen.
My recommendation, is to install current version TWRP 3.0, then try to flash SuperSU 2.76, and see if it gets the phone working (and with root). If not, we'll go from there.
Also, I also would advise in the future, to always make a TWRP backup before rooting or other mods. That way, if the mod/root fails, you can simply restore the backup in TWRP, and have a working phone. Too many folks skip this step. Maybe since it goes unmentioned in root guides. But its really just basic (and wise) procedure for rooting/modding.
redpoint73 said:
However, I don't immediately suggest relocking the bootloader (presumably to RUU to stock); at least until trying some other things (below). As it may be possible to just do the root properly and make the phone work; rather than RUU and starting over.
The TWRP root option doesn't work. That is the whole reason for flashing SuperSU.
Also, you should use SuperSU current stable version 2.76. Some previous builds will also probably be fine, but you may need to flash an insecure kernel separately on some older versions for the full system root. SuperSU builds before 2.52 or so simply will not work on Marshmallow, and will result in being stuck on the HTC logo screen.
My recommendation, is to install current version TWRP 3.0, then try to flash SuperSU 2.76, and see if it gets the phone working (and with root). If not, we'll go from there.
Also, I also would advise in the future, to always make a TWRP backup before rooting or other mods. That way, if the mod/root fails, you can simply restore the backup in TWRP, and have a working phone. Too many folks skip this step. Maybe since it goes unmentioned in root guides. But its really just basic (and wise) procedure for rooting/modding.
Click to expand...
Click to collapse
Hi thanks very much, I just solved it by flashing a newer version of SuperSu like you said. One question, to update TWRP from 2.8.7.0 to 3.0.2.0. Do I need to reflash it from the computer, and if so, will it wipe my data? Im pretty new so I dont know much. In TWRP I cant flash the new one because I cant see the .img.
Thanks.
pasatmalo said:
I just solved it by flashing a newer version of SuperSu like you said. One question, to update TWRP from 2.8.7.0 to 3.0.2.0. Do I need to reflash it from the computer, and if so, will it wipe my data?
Click to expand...
Click to collapse
Yes, flash from computer with fastboot. No, it won't wipe your data. But always backup anything important to you, just to be safe, even when not flashing things.
Also, if you already flashed proper version SuperSU, and the phone is working; there isn't in immediate need to update TWRP. Unless you intend on flashing other things with recovery, or creating TWRP backups. In which case, its recommended to use an updated version.
Guys, I rooted some time ago but phone has been acting up lately.
I thought I'd factory reset from TWRP but must have selected to wipe the lot
Now hangs on htc logo (with the red text warning about Dev rom only) and when I can get into recovery, I have no rom to flash.
Question is: Will flashing remove root or is there a rom I should use?
I was thinking about downloading rom from htc site...
Yes you can flash the stock firmware to return to normal then if you prefer to do root again use twrp an magisk root
Xeeon2 said:
Yes you can flash the stock firmware to return to normal then if you prefer to do root again use twrp an magisk root
Click to expand...
Click to collapse
Thanks, figured I'd lose root but only wanted it to get rid of some bloat and try some battery saving apps.
Do you know if I will have to unlock the bootloader again?
BTW, isn't magisk only for M8? I have M8s...
if your phone S-Off flash stock without locking bootloader if S-ON you have to lock it
but I wanna ask you something about the battery, how long does it stay in normal use because mine doesn't live much only a few hours and when I play games it heats like hell
Xeeon2 said:
if your phone S-Off flash stock without locking bootloader if S-ON you have to lock it
but I wanna ask you something about the battery, how long does it stay in normal use because mine doesn't live much only a few hours and when I play games it heats like hell
Click to expand...
Click to collapse
Thanks again.
Battery really sucks - four/five hours and that's not playing games.
I wanted root because I wanted to try greenify, exposed, and stop some wakelocks but to be honest, they didn't help a great deal.
OK so, I have a twrp backup on my sd card which will not restore - says 'mounted read only'
I am also unable to install an RUU (from here: ruu.lalleman.net/HTC_M8S) just fails.
Do I need an RUU or can I use a stock ROM and do I need to use HTC_Fastboot?
Download this RUU
and flash it with this fastboot
boot to normal and apply the latest OTA
then flash this TWRP
and boot to TWRP and make a Nandriod backup just in case anything wrong happens
and a the end use the Magisk root from this thread
then you will have a stock rooted stable ROM with Latest Updates
Man, you're a star. Many thanks for your help and advice.
I did find out why I couldn't restore my twrp backup, it seems 2.8.6 is a bit buggy and I had to mount/unmount and mount partition again to make it writable.
Got the handset up and running and was going to flash twrp 2.8.7 but think I'll follow you plan through from start.
Once again many thanks.
beaverHausen said:
Man, you're a star. Many thanks for your help and advice.
I did find out why I couldn't restore my twrp backup, it seems 2.8.6 is a bit buggy and I had to mount/unmount and mount partition again to make it writable.
Got the handset up and running and was going to flash twrp 2.8.7 but think I'll follow you plan through from start.
Once again many thanks.
Click to expand...
Click to collapse
You are always welcome