So i have a twrp-3.2.0-m8.img flashed as the custom recovery which works fine. I tried to install SuperSU and got the binaries error of which i downloaded a much newer version and flashed it through twrp. From flashing it, this has screwed up my phone and i can only boot into hboot and recovery. When i try to boot it normally, it just stays on the HTC boot screen with the green and black text. How can i fix it back to normal or root it correctly?
Just restore your backup ... you should already make one before you tried to root it.
Post here fastboot getvar all result without serial & imei no then we'll see what you need.
ChiefMustardo said:
So i have a twrp-3.2.0-m8.img flashed as the custom recovery which works fine. I tried to install SuperSU and got the binaries error of which i downloaded a much newer version and flashed it through twrp. From flashing it, this has screwed up my phone and i can only boot into hboot and recovery. When i try to boot it normally, it just stays on the HTC boot screen with the green and black text. How can i fix it back to normal or root it correctly?
Click to expand...
Click to collapse
When I helped you previously, I had to advise you to provide the proper details. So why are you repeating the same mistakes here? You need to help us help you, by posting the proper details.
In addition to the getvar output requested by ckpv5, what versions of SuperSU did you use? "Much newer version" doesn't really tell us anything (at least not specific enough for us to help you).
Your current firmware version greatly affects what version TWRP and SuperSU you need to use to avoid problems that you mentioned (no boot). So we can't begin to properly help, until you provide the proper info.
Additionally, you started another thread asking same/related questions. I won't respond to that thread, as making multiple threads (for related issues) is confusing and will only cause more problems (such as hopping back and forth between the threads). Bump your existing thread, if you have to (and asking subsequent questions in that existing thread is an acceptable way of doing that). But please don't make more threads. I have some input on the specific questions you asked in the other thread:
ChiefMustardo said:
Can someone please explain to me why when i use twrp or cwm no ROM installs and the md5 check fails as does the signature verification and it says that the zip file is corrupt. It isn't because i got it from the skydragon website.
Click to expand...
Click to collapse
Can't say for sure why TWRP is failing, until you provide the getvar info. It can be a mismatch between your current firmware and the TWRP version. But we have no way of telling, unless you provide the requested details.
And are you trying to use multiple TWRP versions, or just the one mentioned? And BTW, there is no TWRP 3.2.0, so I assume you mean 3.0.2, but please confirm.
Also, I would avoid CWM, as it hasn't been updated in a very long time, which can create a lot of issue in itself.
What is the exact file name, or Skydragon version of the ROM you are trying to install (also very important)?
Just because you downloaded from Skydragon website, does not exclude the possibility the file is corrupt. A perfectly working file can get corrupted during download to your phone/computer. Try downloading twice, to eliminate that as a possibility.
You should also turn off MD5 verification in TWRP; which is probably causing the MD5 error (as mentioned by dottat here). MD5 check typically not used for ROMs (particularly if there was no MD5 hash code supplied with the ROM).
Here is my fastboot getvar all
http://prntscr.com/bd24cj
ChiefMustardo said:
Here is my fastboot getvar all
http://prntscr.com/bd24cj
Click to expand...
Click to collapse
It was also the SuperSU 2.46
ChiefMustardo said:
It was also the SuperSU 2.46
Click to expand...
Click to collapse
Skydragon: SkyDragon+M8+v4.0.0+Sense+8+MM
TWRP: twrp-3.0.2-0-m8
Philz touch: philz_touch_6.26.6-m8
1. You used wrong TWRP recovery 2.7.x.x that make your version-main now empty.
2. You installed wrong SuperSU - 2.46 is NOT for Marshmallow.
3. When you install a custom ROM, it is pre-rooted, no need to root before or after the ROM installation.
I suggest you revert to stock first then redo the whole thing ... rooting or installing a custom ROM, these you can do later after you fix your phone.
Read this for the drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
And this for installing RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Once it is back to stock, unlock the bootloader again with the unlock_code.bin that you received from htc. If it is not working, apply for a new one.
Once unlocked and after first boot and run setup & everything - install TWRP 3.0.2-0
then install custom ROM (no need to install SuperSU)
ChiefMustardo said:
It was also the SuperSU 2.46
Click to expand...
Click to collapse
That version is really old, released about Feb 2015!
SuperSU 2.65 is recommended. Anything older than 2.52 or so does not include the ability to root MM, and will fail with no boot/boot loop.
---------- Post added at 12:26 PM ---------- Previous post was at 12:24 PM ----------
ckpv5 said:
3. When you install a custom ROM, it is pre-rooted, no need to root before or after the ROM installation.
Click to expand...
Click to collapse
That is true, its not clear what the OP is currently trying to accomplish. This thread started out asking about root (stock ROM?) than started another thread asking about custom ROMs.
Its one or the other, not both (root vs. custom ROM) since as you mention, custom ROMs are already rooted.
I have tried using RUU to get it back to stock but it gets stuck in the updating 0/7 screen
ChiefMustardo said:
I have tried using RUU to get it back to stock but it gets stuck in the updating 0/7 screen
Click to expand...
Click to collapse
Just kill the process, and start it again. This is a reported issue for some folks.
If the issue reoccurs, we may have to look at USB connection issues.
Are you using the RUU zip method that ckpv5 directed in Post #7 above?
The RUU method you have suggested seems like it isworking.
The RUU worked thank you so much. Now to install SkyDragon ROM.
I tried the RUU.exe multiple times but that didn't work but yeah, ckpv5's method has worked. It is on Optimizing 44 of 153
ChiefMustardo said:
I tried the RUU.exe multiple times but that didn't work but yeah, ckpv5's method has worked.
Click to expand...
Click to collapse
The .exe is finicky. Anything but Windows 7 and USB 2.0 can cause problems with its USB connectivity. The zip method is more reliable (as you've seen).
It worked. How do i install a custom ROM? Do i get twrp 3.0.2 then install the zip from that? Also, do i keep my bootloader locked or unlock it?
ChiefMustardo said:
It worked. How do i install a custom ROM? Do i get twrp 3.0.2 then install the zip from that? Also, do i keep my bootloader locked or unlock it?
Click to expand...
Click to collapse
Read again : http://forum.xda-developers.com/showpost.php?p=67197327&postcount=7
Clearly stated :
ckpv5 said:
Once it is back to stock, unlock the bootloader again with the unlock_code.bin that you received from htc. If it is not working, apply for a new one.
Once unlocked and after first boot and run setup & everything - install TWRP 3.0.2-0
then install custom ROM (no need to install SuperSU)
Click to expand...
Click to collapse
OK thanks. Do I not require s-off then?
Also, i just tried to install the ROM with twrp (slide right to flash) and it said zip file is corrupt.
ChiefMustardo said:
OK thanks. Do I not require s-off then?
Click to expand...
Click to collapse
For the huge majority of mods (flashing custom ROMs, root, and much more) s-off is not needed. S-off is only needed for a few very specific things, such as manually flashing hboot, radio, changing CID or MID, and a few others.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
ChiefMustardo said:
Also, i just tried to install the ROM with twrp (slide right to flash) and it said zip file is corrupt.
Click to expand...
Click to collapse
What ROM specifically? Did you deselect the MD5 check in TWRP, as previously advised?
redpoint73 said:
For the huge majority of mods (flashing custom ROMs, root, and much more) s-off is not needed. S-off is only needed for a few very specific things, such as manually flashing hboot, radio, changing CID or MID, and a few others.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
What ROM specifically? Did you deselect the MD5 check in TWRP, as previously advised?
Click to expand...
Click to collapse
I am using the skydragon ROM (latest for Marshmallow) but in the zip the only file there is system. It also skips the MD5 check and has a progress bar for a bit and then comes up with the corrupt zip message.
Related
hello, i need to verify something with you guys.
Currently i'm using an HTC One M8 rooted and running on a stock rom, and TWRP as a recovery, can i still have OTA updates in my phone even if I'm on root and TWRP as a recovery. also one thing how can go remove TWRP recovery or revert to HTC recovery
many thanks
I also am curious about this topic
snap213 said:
hello, i need to verify something with you guys.
Currently i'm using an HTC One M8 rooted and running on a stock rom, and TWRP as a recovery, can i still have OTA updates in my phone even if I'm on root and TWRP as a recovery. also one thing how can go remove TWRP recovery or revert to HTC recovery
many thanks
Click to expand...
Click to collapse
1. Download the stock recovery for your device from the recovery thread
2. Flash it through fastboot (as you did TWRP)
3. Apply the OTA
4. Reflash TWRP
5. Re-root the phone
guess i'm stuck with my rooted phone then, i rooted my phone using Hansoon2000 All-In-One-Kit
and i can't find my stock rom, my software number is 1.54.707.7
snap213 said:
guess i'm stuck with my rooted phone then, i rooted my phone using Hansoon2000 All-In-One-Kit
and i can't find my stock rom, my software number is 1.54.707.7
Click to expand...
Click to collapse
Not stock rom...stock recovery
Look at the bottom of the first post of mr_hofs thread in the general section here: http://forum.xda-developers.com/showthread.php?t=2701376
You'll find your stock recovery there ?
Hope that helps.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
spikeydoo2006 said:
Look at the bottom of the first post of mr_hofs thread in the general section here: http://forum.xda-developers.com/showthread.php?t=2701376 (under the nandroid backups section)
You'll find your stock recovery there ?
Hope that helps.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Remember (as said a million times already in multiple threads) - to flash an OTA you CANNOT have changed anything in the original system (fonts, Xposed mods, removing system apps, ANYTHING) otherwise the OTA WILL FAIL
i've browse mr.hofs thread and i've seen lots of stock recoveries. I don't know which stock recovery will I use.
I tried to match it using my software number 1.54.707.7 but there is none. or should i just try the closer to that version?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
thanks.
snap213 said:
i've browse mr.hofs thread and i've seen lots of stock recoveries. I don't know which stock recovery will I use.
I tried to match it using my software number 1.54.707.7 but there is none. or should i just try the closer to that version?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
thanks.
Click to expand...
Click to collapse
here is my recovery backup from 1.54.707.7. https://www.dropbox.com/s/p2ht9dxns3ggcyk/recovery.img
Can you backup your radio.img for me? I forgot to backup when i convert my phone to GPE.
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
snap213 said:
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
Click to expand...
Click to collapse
Yes, you can! I did it exactly that way - and after OTA update reflashed TWRP and rerouted that way. Its a 4 minute job.
snap213 said:
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
Click to expand...
Click to collapse
Learn to do it yourself, relying on toolkits is a false economy as if anything goes wrong you'll have no idea how to fix it...
EddyOS said:
Remember (as said a million times already in multiple threads) - to flash an OTA you CANNOT have changed anything in the original system (fonts, Xposed mods, removing system apps, ANYTHING) otherwise the OTA WILL FAIL
Click to expand...
Click to collapse
Yes, that has been mentioned quite a few times in various threads..However one question that pops up now is:
Lets says I did make changes to the system files by removing a system app or using xposed mods (but not flashing any custom roms). But these changes were made AFTER taking a backup of (unchanged) stock recovery. Will OTA still fail if i now flash stock recovery and then ota update? I am guessing it should work as i am bringing the phone back to stock status.
Also what if i do not flash any custom recovery, I just boot into it to take a backup and remain in stock rom. In that case, for an OTA update, do i still need to first flash stock recovery if I have not made changes to sys files?
Finally when you say OTA fail, does that mean there is a chance I will brick/soft brick my phone?or is it just an error message. I ask because in case i make changes to sys and then forget about it or do not realise its consequence for an OTA update, its better I know now what I am getting into.
anjaan said:
Yes, that has been mentioned quite a few times in various threads..However one question that pops up now is:
Lets says I did make changes to the system files by removing a system app or using xposed mods (but not flashing any custom roms). But these changes were made AFTER taking a backup of (unchanged) stock recovery. Will OTA still fail if i now flash stock recovery and then ota update? I am guessing it should work as i am bringing the phone back to stock status.
Also what if i do not flash any custom recovery, I just boot into it to take a backup and remain in stock rom. In that case, for an OTA update, do i still need to first flash stock recovery if I have not made changes to sys files?
Finally when you say OTA fail, does that mean there is a chance I will brick/soft brick my phone?or is it just an error message. I ask because in case i make changes to sys and then forget about it or do not realise its consequence for an OTA update, its better I know now what I am getting into.
Click to expand...
Click to collapse
The OTA requires a 100% stock running Android build, so if you have removed any system apps it will just fail and reboot to the ROM you're running at the moment (so you should be safe). Basically, if the /system partition on the phone is ANY way different from how it was when you first bought it the OTA will fail
For example, other than S-OFF my phone is exactly how I received it, therefore the new OTA update installed successfully. If I had removed one system app (e.g. Hangouts), it would fail as it's looking for it and if it can't find it it'll just reboot
i still have my S-OFF here in my HTC, and i haven't removed any system apps. i'll try this later this week.
i just needed my root because of setCPU nothing else.
--- anyway, since we're all learning here.
we'll for example, OTA has been updated and all goes well. now that i have to reflash my recovery to TWRP.
big question again, how do i save my stock recovery using TWRP?
snap213 said:
i still have my S-OFF here in my HTC, and i haven't removed any system apps. i'll try this later this week.
i just needed my root because of setCPU nothing else.
--- anyway, since we're all learning here.
we'll for example, OTA has been updated and all goes well. now that i have to reflash my recovery to TWRP.
big question again, how do i save my stock recovery using TWRP?
Click to expand...
Click to collapse
If you're now on 1.54.401.10, you can manually extract it from the firmware package I uploaded HERE
I installed the OTA yesterday and had a different experience. I am with the stock rooted ROM, but I installed Xposed with some modules and the swipe to sleep and no write protection kernel modules. Also, unlocking the bootloader also ate my calculator and torch apps, and I reinstalled them as user apps instead of system apps.
Well, after flashing the stock recovery, the OTA worked like a charm. I applied it manually from the stock recovery, but I don't think this makes a difference. I had to re-root afterwards, but all the rest was preserved.
I am S-OFF though. Is that the reason why it bypassed some security checks?
Black Antitoon said:
I installed the OTA yesterday and had a different experience. I am with the stock rooted ROM, but I installed Xposed with some modules and the swipe to sleep and no write protection kernel modules. Also, unlocking the bootloader also ate my calculator and torch apps, and I reinstalled them as user apps instead of system apps.
Well, after flashing the stock recovery, the OTA worked like a charm. I applied it manually from the stock recovery, but I don't think this makes a difference. I had to re-root afterwards, but all the rest was preserved.
I am S-OFF though. Is that the reason why it bypassed some security checks?
Click to expand...
Click to collapse
I can see the apps that were removed during unlocking still working if installed as user apps as they're still on the /data partition. If they weren't there at all then it'd probably fail. Surprised that it worked with Xposed installed, but that's also a user app so it could very well work - logically it makes sense.
As a rule of thumb I'd only apply an OTA on a 100% stock system, that way you know it'll all be fine
Hello friends, I just got a new refurbished rogers(canada) HTC M8 GSM phone.Its totally stock at this moment and would like to do sim unlock,s-off and boot loader unlock. But before i would like to get full back up of my stock.Few questions:
1.How can i do full complete backup of my stock phone in case in future i need to revert back?
2. what are the steps to do s-off,sim unlock and bootloader unlock?
Right now phone says:
Android version 4.4.3
HTC sence version 6.0
software number 2.23.631.2
HTC SDK API level 6.25
kernel version
3.4.0--g523xxxxxx
baseband version
1.19.2133xxxxxxxx
build number
2.23.631.xxxxxxxrelease-keys
Thanks in advance...
Go to HTCDev.com to unlock the bootloader. The process is self-explanatory (just follow the website instructions). There is a writeup on the following guide, if you need help. But honestly, if you can follow instruction, the process is self-explanatory as I mentioned: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Then, to backup the stock ROM and recovery, follow the instructions listed on the following thread under "How do i backup the stock HTC recovery?" : http://forum.xda-developers.com/showthread.php?t=2701376
This process will boot custom recovery without actually flashing recovery it to the phone, allowing you to backup stock recovery as well as the stock ROM (if you flash custom recovery before doing this, stock recovery is over-written and therefore can't be backed up). Note that your version's stock ROM and recovery may already be uploaded to the above thread by another XDA user.
Then achieve root by your preferred method (flash custom recovery and flash SU/SuperSU, or use weaksauce, towelroot, etc.). Then use sunshine to achieve s-off (firewater s-off will likely not work, as it was patched some time ago): http://theroot.ninja/
Then after s-off, you can unlock SIM: http://forum.xda-developers.com/showthread.php?t=2708572
Thanks a lot redpont73 for your directions!!!Will follow your steps and let you know how things went..Thanks
Ok i unlocked my bootloader with htcdev.com and it says unlocked now.
Now how to backup my stock at this point? I tried this thread you showed me: http://forum.xda-developers.com/show....php?t=2701376 but didn't understand fully. but it says :fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)"
I am little confused at this point.How can i back up at this point without installing any recovery software like twrp?please guide me.thanks
ninja_zx11 said:
Now how to backup my stock at this point? I tried this thread you showed me: http://forum.xda-developers.com/show....php?t=2701376 but didn't understand fully. but it says :fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)"
I am little confused at this point.How can i back up at this point without installing any recovery software like twrp?
Click to expand...
Click to collapse
By placing the custom recovery image in your fastboot folder, you can then boot recovery without actually flashing it to the phone, using the command you quoted. Think of it as remotely running the TWRP software that is still located on your PC (at least I think that is how it works).
Once you are booted into TWRP, you can backup system (stock ROM) and recovery(stock recovery).
redpoint73 said:
By placing the custom recovery image in your fastboot folder, you can then boot recovery without actually flashing it to the phone, using the command you quoted. Think of it as remotely running the TWRP software that is still located on your PC (at least I think that is how it works).
Once you are booted into TWRP, you can backup system (stock ROM) and recovery(stock recovery).
Click to expand...
Click to collapse
Could you please help me to find the custom recovery image that i can put in my fast boot folder and please step by step if you don't mind please.Just trying to learn and don't want to brick my phone with any wrong move.thanks
i found this thread.
http://forum.xda-developers.com/showpost.php?p=53770286&postcount=4
Will that help?thanks
ninja_zx11 said:
i found this thread.
http://forum.xda-developers.com/showpost.php?p=53770286&postcount=4
Will that help?thanks
Click to expand...
Click to collapse
Yes, that is another method.
---------- Post added at 11:11 AM ---------- Previous post was at 11:05 AM ----------
ninja_zx11 said:
Could you please help me to find the custom recovery image that i can put in my fast boot folder and please step by step if you don't mind please.
Click to expand...
Click to collapse
Go to the General forum section for the M8, and look at the Index thread (sticky at the top of that forum) to find link to recoveries and other resources, including guides and how-tos. Read up and learn.
Taking the time to familiarize yourself with the basic concepts and processes is much more valuable than someone walking your though step-by-step. I won't walk you through step-by-step, as you will learn very little that way.
The process is not that difficult, anyway. You already used fastboot to unlock the bootloader. Other fastboot commands are not any different in execution. If you can't handle taking it from here, modding the phone probably isn't for you.
With S-on, you aren't going to brick the phone by backing up or flashing recovery. Even with s-off, as long as you only flash things intended for the M8 (and only for the GSM version - not CDMA - to be safe), you will not brick. You can only brick the phone if you damage hboot, radio, or partition tables.
redpoint73 said:
Yes, that is another method.
---------- Post added at 11:11 AM ---------- Previous post was at 11:05 AM ----------
Go to the General forum section for the M8, and look at the Index thread (sticky at the top of that forum) to find link to recoveries and other resources, including guides and how-tos. Read up and learn.
Taking the time to familiarize yourself with the basic concepts and processes is much more valuable than someone walking your though step-by-step. I won't walk you through step-by-step, as you will learn very little that way.
The process is not that difficult, anyway. You already used fastboot to unlock the bootloader. Other fastboot commands are not any different in execution. If you can't handle taking it from here, modding the phone probably isn't for you.
With S-on, you aren't going to brick the phone by backing up or flashing recovery. Even with s-off, as long as you only flash things intended for the M8 (and only for the GSM version - not CDMA - to be safe), you will not brick. You can only brick the phone if you damage hboot, radio, or partition tables.
Click to expand...
Click to collapse
Yes you are right...I will read more and i want to learn and will try to do it myself.If i will have some confusion, i will ask here.Looks like i need more reading.
Now what i am planning to do is:
1. Install twrp
2.Take a full nandroid backup.(will it be enough to save me in future if i would like to go back to stock after S-OFF?)
3.root and s-off.
Does it make sense?
ninja_zx11 said:
Now what i am planning to do is:
1. Install twrp
2.Take a full nandroid backup.(will it be enough to save me in future if i would like to go back to stock after S-OFF?)
3.root and s-off.
Does it make sense?
Click to expand...
Click to collapse
The process to backup stock recovery is easy, by either method we already discussed. If you want to be thorough, backup stock recovery.
Backing up stock recovery and stock ROM is sufficient to return (mostly) to stock. There isn't much else you can do
redpoint73 said:
The process to backup stock recovery is easy, by either method we already discussed. If you want to be thorough, backup stock recovery.
Backing up stock recovery and stock ROM is sufficient to return (mostly) to stock. There isn't much else you can do
Click to expand...
Click to collapse
UPDATE:
I downloaded latest twrp and i booted into twrp .then took full backup. i also took back up using philz touch same way by just booting into philztouch.
Then i tried to root using supersu by same booting into twrp and tried to root.it created a supersu icon on the spring board and then i tried to install it from play store but it errored out and phone rebooted.After that i tried to remove the supersu icon from the phone but just couldnt. Then i thought of restoring stock backup using twrp and it restored it to stock stage.Atleast now i know that my stock backup worked.!!!
Now my question is why did supersu not root my phone?Should i try another method?please advice.thanks
ninja_zx11 said:
UPDATE:
I downloaded latest twrp and i booted into twrp .then took full backup. i also took back up using philz touch same way by just booting into philztouch.
Then i tried to root using supersu by same booting into twrp and tried to root.it created a supersu icon on the spring board and then i tried to install it from play store but it errored out and phone rebooted.After that i tried to remove the supersu icon from the phone but just couldnt. Then i thought of restoring stock backup using twrp and it restored it to stock stage.Atleast now i know that my stock backup worked.!!!
Now my question is why did supersu not root my phone?Should i try another method?please advice.thanks
Click to expand...
Click to collapse
huh? Did you flash it and then tried to install it from the play store after it was already "installed" by being flashed in custom recovery? If not, what exactly are you talking about here?
I've never bothered with the play store, just boot the custom recovery and flash the latest SuperSU. That's it... :silly:
BerndM14 said:
huh? Did you flash it and then tried to install it from the play store after it was already "installed" by being flashed in custom recovery? If not, what exactly are you talking about here?
I've never bothered with the play store, just boot the custom recovery and flash the latest SuperSU. That's it... :silly:
Click to expand...
Click to collapse
thanks BerndM14, i just copied supersu zip to internal storage as you said and installed it by booting into twrp from pc. and its done... thanks..
ninja_zx11 said:
UPDATE:
I downloaded latest twrp and i booted into twrp .then took full backup. i also took back up using philz touch same way by just booting into philztouch.
Then i tried to root using supersu by same booting into twrp and tried to root.it created a supersu icon on the spring board and then i tried to install it from play store but it errored out and phone rebooted.After that i tried to remove the supersu icon from the phone but just couldnt. Then i thought of restoring stock backup using twrp and it restored it to stock stage.Atleast now i know that my stock backup worked.!!!
Now my question is why did supersu not root my phone?Should i try another method?please advice.thanks
Click to expand...
Click to collapse
Sounds like a brick in the making.
Make sure that you read and understand what you are about to do before you do it.
A nandroid won't always help you.
If I may make a suggestion, don't go S-Off.
I am abandoning the idea of doing S-off after the suggestion from xunholyx above and after reading this http://android-revolution-hd.blogspot.ca/2013/06/do-we-really-need-s-off.html.
ninja_zx11 said:
I am abandoning the idea of doing S-off after the suggestion from xunholyx above and after reading this http://android-revolution-hd.blogspot.ca/2013/06/do-we-really-need-s-off.html.
Click to expand...
Click to collapse
I see you are learning. I will never understand why folks seek to get s-off, without even understanding what it means. You should not be attempting any mods, unless you fully understand what the purpose is (such as s-off).
redpoint73 said:
I see you are learning. I will never understand why folks seek to get s-off, without even understanding what it means. You should not be attempting any mods, unless you fully understand what the purpose is (such as s-off).
Click to expand...
Click to collapse
thanks redpoint73 for giving me helping hand!! without your help i wouldn't have done it.....
Root/Bootloader unlocking failed? "No SU binary"
A few months ago I got a M8 (international model i believe, it says 'M8x' on the back) and tried to root and unlock the bootloader but failed so I just stored it away .
I followed these videos. Can't paste links...new xda account:
youtube:
HTC One M8 : How to Unlock Bootloader & Root - Easiest Method
HTC One M8 : How to Root & Install TWRP Recovery - Easiest Method
I believe the first video, unlocking the bootloader, was successful(says "Software status: Modified""**Unlocked**" in bootloader mode).
In the second I believe TWRP was installed successfully (It opens up via Recovery) but the SuperSU app was not successful . I don't remember exactly what happened (it was months ago) but when I hit the SuperSU app I think it failed to update as seen in the second video at 2;29. As of today, when I try to open SuperSU, I'm presented with a message that says: "There is no SU binary installed, and superSU cannot install it. This is a problem! If you just upgraded to Android 5.0, you need to manually re-root" hit ok and SuperSU closes.
I found various fixes and such but I'm not sure which is the safest.
Sorry I'm new to android and I just don't want to ruin my device.
SOLVED
I grew some balls and just went for it. Flashed a supersu.zip in TWRP and it worked.
Delete this thread I guess.
If you used the toolkit as shown in the Youtube video, that was your main problem.
The toolkit uses obsolete (and by obsolete, I mean over a year) versions of both:
SuperSU (current version is 2.46)
TWRP (current version is 2.8.7)
Using outdated versions of either/both of these with a stock Lollipop M8 will cause some major issues. Before doing any mods, its best to read and research to make sure you are using the most up-to-date procedures and files. Youtube should not be your only modding resource. Also, keep in mind that the "easiest" way, is not necessarily the "best" way.
huura said:
I grew some balls and just went for it. Flashed a supersu.zip in TWRP and it worked.
Click to expand...
Click to collapse
Making a TWRP backup before flashing anything would have minimized any risk.
---------- Post added at 01:20 PM ---------- Previous post was at 01:20 PM ----------
huura said:
A few months ago I got a M8 (international model i believe, it says 'M8x' on the back)
Click to expand...
Click to collapse
M8x is the Taiwanese, higher CPU clocked variant.
That makes sense. Thanks for all the info. woo slightly higher clock speed variant!
Just successfully updated TWRP with Flashify, TWRP Manager didn't want to work. All good.
Also should I use the superSU 2.52 beta or is it too troublesome? Any benefits?
huura said:
T woo slightly higher clock speed variant!
Click to expand...
Click to collapse
On a side note. Only thing to be aware of, the M8x can't have other versions' radios flashed to it, even with s-off; as confirmed by a few users here (including one very knowledgeable one).
By extension, this probably also means that you can't "convert" to another version by running that version's RUU.
Probably not a major issue, as all other common mods (TWRP, root, flashing custom ROMs) should work fine on the M8x. Just something to keep in mind.
huura said:
Just successfully updated TWRP with Flashify, TWRP Manager didn't want to work. All good.
Click to expand...
Click to collapse
My advice would be to learn how to use fastboot to install TWRP, and skip the pointless middle man apps. Doing it by fastboot is easy, and much more reliable.
huura said:
Also should I use the superSU 2.52 beta or is it too troublesome? Any benefits?
Click to expand...
Click to collapse
No benefits that I know of. 2.46 roots the phone (on Lollipop) just fine, no need to have any "benefits" beyond that.
Marshmallow is a different story.
Ah ok. I'll keep note of that quirk, thanks.
The fastboot method doesn't look too complicated. I'll definitely look into it if it's more reliable/less of a hassle.
One more thing, I wanted to install Xposed for ARHD's sense toolbox. How do I install it? Just install the .apk file on my device and I'm good to go or is there more to it?
huura said:
The fastboot method doesn't look too complicated. I'll definitely look into it if it's more reliable/less of a hassle.
Click to expand...
Click to collapse
Its a good trick to know (as well as other fastboot commands) as it allows you to flash recovery without a working OS (not an unheard of situation, if you mess with flashing ROMs and other things enough times).
The process is pretty simple, as you most likely already have fastboot setup on your computer if you unlocked the bootloader. So flashing a recovery is simply a matter of:
1) Download the desired recovery .img to your fastboot folder (where fastboot.exe is located)
2) Connect your phone to the computer, and boot into bootloader-fastboot mode
3) Open a command prompt on the computer
4) Issue the proper fastboot command
5) Drink beer
huura said:
One more thing, I wanted to install Xposed for ARHD's sense toolbox. How do I install it? Just install the .apk file on my device and I'm good to go or is there more to it?
Click to expand...
Click to collapse
I haven't messed with Xposed for a while, but I think you just need to:
1) Make a nandroid of your current working setup
2) Install the Xposed apk
3) Open the Xposed app and install the desired frameworks
Figured it out, was straight forward
I figured out how to unlock my boot loader with SUNSHINE. BootLoader UNLOCKED and S-OFF'd...... Installed when I went into recovery mode, installed SUPERSU and rebooted phone it only booted to the VERIZON boot screen and wouldn't do anything. I tried FACTORY RESET in DOWNLOAD MODE - still will not boot past the verizon screen
Are you in MM? What version of super su did you install? If yes, try flashing 2.65 if you haven't tried... (by the way, you can easily get out of the bootloop by restoring the boot.img)
Sent from my HTC One M9 using Tapatalk
Not sure whatMM is? SuperSU 2.46
Marshmallow/android6
Sent from my HTC One M9 using Tapatalk
---------- Post added at 04:10 PM ---------- Previous post was at 04:09 PM ----------
2.46 is too old...
Sent from my HTC One M9 using Tapatalk
Yes it's Marshmallow. I went back into recovery. Uploaded the SuperSU 2.65 into my phone, installed it. This time i notices an error message when it finished...
Could Not Find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing zip file '/sdcard/UPDATE-SuperSU-v2.zip
Still does the same thing, just boots to the Verizon Screen
Got it working. I got the Stock RUU from http://forum.xda-developers.com/ver...t/6-0-verizon-htc-one-m9-marshmallow-t3316279. Transferred it onto a SD CARD (That is formatted to FAT32) and booted the phone into download mode where it asks you to FLASH THE RUU. afterwards the phone is back to stock... Now I will try to root it with the correct SuperSU
The phone it rooted ad running. But I am having issues installing a custom ROM... I tried MAXIMUS HD, ANDROID REVOLUTION HD and ViperOne.... None of them will take, get the same error message as before............
******Could Not Find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing zip file '/sdcard/UPDATE-SuperSU-v2.zip8********
Anyone know what could be wrong?
dksob81 said:
The phone it rooted ad running. But I am having issues installing a custom ROM... I tried MAXIMUS HD, ANDROID REVOLUTION HD and ViperOne.... None of them will take, get the same error message as before............
******Could Not Find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing zip file '/sdcard/UPDATE-SuperSU-v2.zip8********
Anyone know what could be wrong?
Click to expand...
Click to collapse
I did get Viper One (ROM) to finally work, I downloaded the incorrect version (v3.5.0 - ALL CARRIERS), so I tried the latest version (v4.3.0) and it worked....
i recently rooted my sprint version phone and on the last step where i have to swipe right inside twrp to flash supersu, my phone gets stuck at the htc one bootup screen. I'm not sure which ruu file to download as i have 3.41.651.4 already on my phone. what do i do now? thanks in advance.
where do i go from here?
freighter2298 said:
where do i go from here?
Click to expand...
Click to collapse
Which version of supersu and twrp?
Beamed in by telepathy.
i think twrp 2.8.6 and supersu 2.46? i cant recall what version of supersu but its some where in the 2.4 range its an older version which could be the cause for the bootup issue according to another user.
If your phone is on Marshmallow firmware, you need to be sure you have the latest versions of everything as stuff from Lollipop is not compatible. Most likely that's your problem. Make sure you have a Marshmallow rom and the latest twrp (3.0) and SuperSU 2.65.
right, but my issue right now is that my pc won't detect my phone so i can't put the later version of supersu.
Was it detecting it before? Can you get into recovery at all?
it was detecting it before and i cant get into recovery also i relocked my bootloader for the ruu and it says ***relocked***
freighter2298 said:
it was detecting it before and i cant get into recovery also i relocked my bootloader for the ruu and it says ***relocked***
Click to expand...
Click to collapse
Sounds like you need to reflash the RUU and start over. Then copy over the correct twrp and supersu.
how do i do that when I have the most updated ruu? the thread said to only upgrade from the current version
The rom will take as a reflash. Also, use a card reader to copy supersu to a microsd, put it into the phone, boot to twrp and flash from there.
**I must stress that YOU MUST CHECK THE MD5 HASH "AND" FILESIZE MATCH THE ORIGINAL.
YOU MUST CHECK THE MD5 HASH "AND" FILESIZE MATCH THE ORIGINAL.
Here is a link to my stuff that i used on my xp machine for my international phone. Do not use any of the phone based stuff unless you are ABSOLUTELY 100% sure it is compatible with your phone: https://drive.google.com/folderview?id=0B4vTiHTBB629QmxGTkpyZWlCR28
Beamed in by telepathy.
Hey, been a while I visited here though but this site has always been my first call when I have issues with my Android.
Kindly help me. I have this m8 intl ver. running marshmallow and I have been trying to use kingroot to root the phone but all the versions I have used so far couldn't get the job done. I am inaccessible to a computer. Although I once used kingroot long time ago when the phone was running lollipop and it worked. After I upgraded the OS to 6.0, the kingroot didn't work.
If kingroot doesn't work, I don't think you have any choice but to use a PC to unlock the bootloader, etc.
Even if you don't personally have a PC, surely a friend or family member has one, they will let you use for an hour or so? Buy them a 6 pack or something, for the privilege.
Well, thank you. I already unlocked the bootloader. And I thought about that options you gave me but the 1hr on a PC is what I don't have. So I have no choice now but to create that 1hr. Thank you.
tunnex190 said:
Well, thank you. I already unlocked the bootloader. And I thought about that options you gave me but the 1hr on a PC is what I don't have. So I have no choice now but to create that 1hr. Thank you.
Click to expand...
Click to collapse
If your bootloader is unlocked, then you don't need a PC. Do you have TWRP installed? There are ways to flash it without a PC (from SD in hboot) if you don't. If you already have TWRP then flash SuperSU with it or a rooted ROM (most M8 ROMs are rooted).
I used to have a TWRP.zip that was flashable from extSD, but I've deleted it from my DropBox. If you need one I could make another
xunholyx said:
If your bootloader is unlocked, then you don't need a PC
Click to expand...
Click to collapse
To install an unsigned zip, needs S-Off.
ckpv5 said:
To install an unsigned zip, it needs S-Off.
Click to expand...
Click to collapse
I never even thought of it being unsigned, but of course you can't. With my HTC devices I have went S-Off soon after getting them, so I was thinking to myself "yeah, I've done that after an RUU"
Thanks for clearing that up.
Thanks guys but the phone is s-off already and unlocked bootloader. And how can I install this twrp? I remembered I did flash twrp-2.8.7.0-m8.img during a time when I was upgrading to Marshmallow; if that's kind of twrp you were talking about? Kindly tell me the way to go about it
tunnex190 said:
Thanks guys but the phone is s-off already and unlocked bootloader. And how can I install this twrp? I remembered I did flash twrp-2.8.7.0-m8.img during a time when I was upgrading to Marshmallow; if that's kind of twrp you were talking about? Kindly tell me the way to go about it
Click to expand...
Click to collapse
It's something like this - http://forum.xda-developers.com/showpost.php?p=67526388&postcount=387
You put the 0P6BIMG.zip on root of your microsd, then reboot to hboot. System will scan and ask you to update, volume up to update. Once finish, reboot .. you have TWRP 3.0.2-0 already installed.
Then download SuperSU.zip.
Boot to recovery (TWRP) - select install SuperSU.zip - done, now your device is rooted.
If you want me to edit the OS no. to fit your current software version, let me know what it is then I make a new one for you and upload here.
tunnex190 said:
Thanks guys but the phone is s-off already and unlocked bootloader.
Click to expand...
Click to collapse
That is a lot of info that should have been supplied in the top post.
First its an unlocked bootloader, you didn't tell us about. Now its s-off, that you didn't tell us about.
I already thought of the method to flash TWRP by zip with SD card method; but realized that you need s-off to do so.
When someone asks how to root, and doesn't give any details; the assumption I would make is that the phone is not previously modified.
I assume the phone was modified by a previous owner? Again, a detail that should have been supplied from the beginning.
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
xunholyx said:
I never even thought of it being unsigned, but of course you can't. With my HTC devices I have went S-Off soon after getting them
Click to expand...
Click to collapse
I was about to post about the SD card flashable TWRP zips that have been posted around here. But then, I realized that you need to be s-off.
I'm normally of the opposite mindset, especially since the introduction of sunshine; I assume that users are s-on unless they indicate otherwise.
redpoint73 said:
That is a lot of info that should have been supplied in the top post.
First its an unlocked bootloader, you didn't tell us about. Now its s-off, that you didn't tell us about.
I already thought of the method to flash TWRP by zip with SD card method; but realized that you need s-off to do so.
When someone asks how to root, and doesn't give any details; the assumption I would make is that the phone is not previously modified.
I assume the phone was modified by a previous owner? Again, a detail that should have been supplied from the beginning.
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
I was about to post about the SD card flashable TWRP zips that have been posted around here. But then, I realized that you need to be s-off.
I'm normally of the opposite mindset, especially since the introduction of sunshine; I assume that users are s-on unless they indicate otherwise.
Click to expand...
Click to collapse
I'm sorry It escaped my mind to tell all of this. I actually modified the phone myself. It was a brand new then, I'm the first owner.
Do I just need to flash superuser through hboot recovery now?
ckpv5 said:
It's something like this - http://forum.xda-developers.com/showpost.php?p=67526388&postcount=387
You put the 0P6BIMG.zip on root of your microsd, then reboot to hboot. System will scan and ask you to update, volume up to update. Once finish, reboot .. you have TWRP 3.0.2-0 already installed.
Then download SuperSU.zip.
Boot to recovery (TWRP) - select install SuperSU.zip - done, now your device is rooted.
If you want me to edit the OS no. to fit your current software version, let me know what it is then I make a new one for you and upload here.
Click to expand...
Click to collapse
Thanks I assume I have installed the twrp version twrp-2.8.7.0. Hope it can get the work done by flashing SuperUser through twrp recovery?
tunnex190 said:
Thanks I assume I have installed the twrp version twrp-2.8.7.0. Hope it can get the work done by flashing SuperUser through twrp recovery?
Click to expand...
Click to collapse
If you already have TWRP 2.8.7.0 - don't accept root offer by that TWRP version (won't work on Marshmallow) but download the latest SuperSU zip and install it in recovery.
http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you wish to update the TWRP to version 3.0.2-0 or later, just download the TWRP.img then in current TWRP you can select Install and select image then select the TWRP.img and select recovery then install.
Thanks. I downloaded the flashable Zipped Superuser from the link you gave. And since you said the older version of TWRP I'm running won't accept root offer, I bet upgrade it then and use it to flash the SuperUser. Do you have a link to download the latest twrp.img?
tunnex190 said:
Thanks. I downloaded the flashable Zipped Superuser from the link you gave. And since you said the older version of TWRP I'm running won't accept root offer, I bet upgrade it then and use it to flash the SuperUser. Do you have a link to download the latest twrp.img?
Click to expand...
Click to collapse
I didn't say the TWRP won't accept root offer .. I said you don't accept root offered by TWRP because that SuperSU offered by TWRP is old version and won't work on Marshmallow.
No problem to use that version TWRP to install latest SuperSU.zip
https://dl.twrp.me/m8/
ckpv5 said:
I didn't say the TWRP won't accept root offer .. I said you don't accept root offered by TWRP because that SuperSU offered by TWRP is old version and won't work on Marshmallow.
No problem to use that version TWRP to install latest SuperSU.zip
https://dl.twrp.me/m8/
Click to expand...
Click to collapse
can you help me with latest flashable TWRP zip? I downloaded the .img but then I realize I would need PC to flash it.
ckpv5 said:
I didn't say the TWRP won't accept root offer .. I said you don't accept root offered by TWRP because that SuperSU offered by TWRP is old version and won't work on Marshmallow.
No problem to use that version TWRP to install latest SuperSU.zip
https://dl.twrp.me/m8/
Click to expand...
Click to collapse
can you help me with latest flashable TWRP zip? I downloaded the .img but then I realize I would need PC to flash it. Or is there other way to install the .img because I couldn't locate it when I entered twrp recovery
tunnex190 said:
can you help me with latest flashable TWRP zip? I downloaded the .img but then I realize I would need PC to flash it.
Click to expand...
Click to collapse
You don't really read what I already posted before. I gave you two options earlier.
1. If you need the flashable zip - you need to give me your OS no.
or
2. Put the downloaded TWRP.img on root of your sdcard. In TWRP select install, below you'll see menu install images, select that, then browse to your downloaded TWRP.img then install. It will ask that image is for recovery or boot, select recovery .. install, done.
ckpv5 said:
You don't really read what I already posted before. I gave you two options earlier.
1. If you need the flashable zip - you need to give me your OS no.
or
2. Put the downloaded TWRP.img on root of your sdcard. In TWRP select install, below you'll see menu install images, select that, then browse to your downloaded TWRP.img then install. It will ask that image is for recovery or boot, select recovery .. install, done.
Click to expand...
Click to collapse
Really I am sorry to bother you. I would prefer option 1. Here's the OS no: 6.12.401.4.
tunnex190 said:
Really I am sorry to bother you. I would prefer option 1. Here's the OS no: 6.12.401.4.
Click to expand...
Click to collapse
Attached .. how-to, read back my earlier post.
Thank you all. Everything went well. I'm grateful