Database Develop

[Q] Rooting HTC One with hboot 1.55!!!

Hey guys, I've recently received my HTC international. It came with 4.2 but I updated it to 4.3. I've unlocked the bootloader and do have TWRP as recovery. Now I'm trying to root my phone and also s-ff but I run into a problem because my hboot is version 1.55.
I've tried various of different methods to root my One, they all complete successfully, get a shortcut for supersu still not rooted.
Can anyone help rooting One with hboot 1.55?

You only have to flash this...

Just tried. I am getting the same message I did before in SuperSU... "There is no SU binary installed, and SuperSU cannot install it. This is a problem!! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device."
Just to clarify, this device was not rooted before 4.3. It's a new device. I took it out the box, plugged it into my pc, UPDATED to 4.3 (which updated hboot to 1.55) and then I started looking for ways to root. Unlocking the bootloader worked perfectly but cannot root :/

cagkanm said:
Just tried. I am getting the same message I did before in SuperSU... "There is no SU binary installed, and SuperSU cannot install it. This is a problem!! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device."
Just to clarify, this device was not rooted before 4.3. It's a new device. I took it out the box, plugged it into my pc, UPDATED to 4.3 (which updated hboot to 1.55) and then I started looking for ways to root. Unlocking the bootloader worked perfectly but cannot root :/
Click to expand...
Click to collapse
Are you running stock rom?

Yes. I am running the official 4.3 update. Maybe I should have mentioned this before, my aim is to get the Google Play edition, 4.4 on this device. As far as I know, I need to be rooted, s-ff for this.

Ain't there another way of doing this? Eg, flashing Android Revolution 40.0? what would happen if I tried flashing this on non rooted device? is there a way it would root the device?

I was able to root my device using openrecovery-twrp-2.6.3.0-m7 as recovery. SuperSU 1.80

cagkanm said:
Ain't there another way of doing this? Eg, flashing Android Revolution 40.0? what would happen if I tried flashing this on non rooted device? is there a way it would root the device?
Click to expand...
Click to collapse
Install Android Revolution HD 31.6 then use rumrunner to s-off. That's what worked for me.

[Q] S-off versus SU

Hi
I have a new HTC one M8 (Bell Canada carrier), rooted with HTCDev, I also have SuperUser status and I installed TWRP recovery.
The question is: should I bother to get S-Off?
Another question, unrelated to S-Off vs SU:
As I did not flash a new Rom, I beleive that I still could do the OTA sys updates when they become available,
would doing an OTA system update remove my SU privileges and re-lock the bootloader?
Thanks,
Fizou, in Toronto

Fizou said:
Hi
I have a new HTC one M8 (Bell Canada carrier), rooted with HTCDev, I also have SuperUser status and I installed TWRP recovery.
The question is: should I bother to get S-Off?
Another question, unrelated to S-Off vs SU:
As I did not flash a new Rom, I beleive that I still could do the OTA sys updates when they become available,
would doing an OTA system update remove my SU privileges and re-lock the bootloader?
Thanks,
Fizou, in Toronto
Click to expand...
Click to collapse
1) This is the M7 forum, not M8. In the future, pls post there. There's a forum specifically for the M8
2) S-OFF nd SU are TWO ABSOLUTELY DIFFERENT THINGS ALTOGETHER. Pls research more
Coming to your question, you cannot get OTA updates if you have a custom recovery, which im sure you would be having. If you want OTA updates, you need to flash stock recovery. And, OTA updates wont affect ur root privilege(SU) or the bootloader status

[Q] Please help rooting

I have a HTC One (m7) sprint running 4.4.3. I just unlocked the bootloader. i have the tampered sign and it says unlocked. i installed a customer recovery (the latest twrp 2.7.1.1). i went to recovery and flashed SU 1.25 and once the phone reboots i check root checker and it says i am not rooted. when i open SuperSu it mentions binaries not there. Please help me..

blacjac30 said:
I have a HTC One (m7) sprint running 4.4.3. I just unlocked the bootloader. i have the tampered sign and it says unlocked. i installed a customer recovery (the latest twrp 2.7.1.1). i went to recovery and flashed SU 1.25 and once the phone reboots i check root checker and it says i am not rooted. when i open SuperSu it mentions binaries not there. Please help me..
Click to expand...
Click to collapse
Download and install BusyBox and update SuperSU to version 2 or higher from the Play Store .

[Q] Is my warranty still intact?

I had previously rooted my HTC One M7 with Weaksauce .apk+Supersu. I unlocked my boot loader through HTC.dev and obtained s-off via firewater while connected to PC using adb commands. The custom recovery I used was twrp. I am closing in on my upgrade through Verizon so I decided it was time to revert to 100% stock. I locked my device with revone. I failed to make a backup of my stock ruu in the beginning so I had to find one. I may have unintentionally installed a stock rooted ruu but I am unsure. During this time my software build number was 3.11.605.1. Before I installed the new ruu, my hboot was 1.56 and my previous os was kit Kat 4.4.2. After obtaining s-on, I flashed an ruu that professed to be the latest OTA ruu available for the above build number. Once the ruu was finished installing I rebooted my phone and followed the on screen initialization. Now that I was on my "stock ruu" I performed a software update. When that process was complete I rebooted into the bootloader with the intention of verifying that there wasn't a tampered flag and that all appeared in its original state. The bootloader is locked with s-on and no tampered flag. Okay now that I have said all that, I do have one concern. I checked my apps and supersu is still a system app that is installed without any way of uninstalling. I opened supersu and went to settings and full unroot. At first glance supersu had uninstalled itself, however when I rebooted my phone supersu was still there except now I cannot open the app b/c the binaries are not up to date. I downloaded es file explorer and cannot delete or uninstall any part of su through bin or xbin folders and I cannot uninstall the original apk. From what I understand is that I must reroot to remove supersu. My issue with that is unlocking my boot loader since I have updated to 4.4.3. Even though supersu is still on my phone would that void my warranty? I downloaded rootchecker and I do not have root access.

Zacb01 said:
I had previously rooted my HTC One M7 with Weaksauce .apk+Supersu. I unlocked my boot loader through HTC.dev and obtained s-off via firewater while connected to PC using adb commands. The custom recovery I used was twrp. I am closing in on my upgrade through Verizon so I decided it was time to revert to 100% stock. I locked my device with revone. I failed to make a backup of my stock ruu in the beginning so I had to find one. I may have unintentionally installed a stock rooted ruu but I am unsure. During this time my software build number was 3.11.605.1. Before I installed the new ruu, my hboot was 1.56 and my previous os was kit Kat 4.4.2. After obtaining s-on, I flashed an ruu that professed to be the latest OTA ruu available for the above build number. Once the ruu was finished installing I rebooted my phone and followed the on screen initialization. Now that I was on my "stock ruu" I performed a software update. When that process was complete I rebooted into the bootloader with the intention of verifying that there wasn't a tampered flag and that all appeared in its original state. The bootloader is locked with s-on and no tampered flag. Okay now that I have said all that, I do have one concern. I checked my apps and supersu is still a system app that is installed without any way of uninstalling. I opened supersu and went to settings and full unroot. At first glance supersu had uninstalled itself, however when I rebooted my phone supersu was still there except now I cannot open the app b/c the binaries are not up to date. I downloaded es file explorer and cannot delete or uninstall any part of su through bin or xbin folders and I cannot uninstall the original apk. From what I understand is that I must reroot to remove supersu. My issue with that is unlocking my boot loader since I have updated to 4.4.3. Even though supersu is still on my phone would that void my warranty? I downloaded rootchecker and I do not have root access.
Click to expand...
Click to collapse
to remove files from /system you need root + unsecured kernel or simply from custom recovery. I dont know if having supersu will cause an issue with your carrier (bootloader is locked, s-on, no tampered flag). It all depends who will look at the phone imo, if that person is smart enough, he will understand that the phone was tampered before by seeing supersu installed. Some others don't even know what it is... Probably a better idea to remove it just in case...

[Q] HTC Desire 626 Lollipop 5.1 Root?

Hello, I have been searching for a rooting method that will work for At&t's Desire 626. I quite like the stock ROM and would enjoy backup security and debloating the ROM. Sadly, no root method I've tried has been successful. I've attempted iRoot app and program, Kingo Root app and program, King Root app, Towel Root app, and Towel Pie Root app.
Any clue?

If you have the 626s - here is a way to root it:
http://forum.xda-developers.com/showthread.php?p=63128990

EDIT: NM looks like that worked! At&t desire 626 bought today. SuperSU installed.

So that procedure works for a regular 626 (not the "s" version) from AT&T? Good to know...

Correct. Non-s version from At&t.

doesnt' work
I followed everything step by step and Super SU tells me I have to update the binaries but it doesn't work. Anyone know where I can get the updated binaries to manually install it?

Hmm - so if you tap on the notification, it doesn't update the binaries automatically? Never had that issue...
Does Superuser actually work? If so, and the notification only comes up after a reboot, I probably wouldn't even worry about it...

The super Su app works but none other app recognizes that I have root access, like bloatware removers. I followed every step.
Any ideas?

What exact phone (626, 626s, etc), carrier and Android version?

Plain 626, AT&T Android 5.1
In this same thread they said it would work

Did you use the Supersu zip linked to in the detailed step-by-step procedure post? I know that people had issues with the supersu .zip posted in another thread...
Other than that, I'm not sure - maybe try to flash supersu again?
Sent from my SM-T230NU using Tapatalk 2

I have yet to see any warning about SuperSU needing updating. I just confirmed that I can remove any bloatware, edit build.prop, etc.
I can absolutely confirm that I have Cyanogen Recovery booting too, as Im staring at it now.
Maybe I got an older variant of this phone? The store said it was their last one.
Is there anything I can check to verify that this is the same model?

Which version of Android are you running on your 626? 4.x or 5.x?

5.1, hardware info says "desire 626" not 626s or anything else.

I'm wondering if he used the wrong SuperSU .zip file... Someone else had the same issue and after using the correct SuperSU .zip file (the one posted in the detailed step-by-step rooting thread), he was fine...
Let's wait and get confirmation from the user above as to which SuperSU .zip file he used - hopefully, that's the issue.

I also have an HTC Desire 626 (Android 5.1) and can't root it. I know pretty much nothing about this process and didn't even know you could do it until recently. But I need to have it rooted so I can recover deleted SMS messages. Any instructions for a phone dummy?

alfredojp said:
Plain 626, AT&T Android 5.1
In this same thread they said it would work
Click to expand...
Click to collapse
problem is what continunt u are on to what htc 626 you got in america htc626 and htc626s both are a32e_ul android 5.1, in europe htc626 is a a32_ul 64bit 1.2ghz android 5.1, in asia htc626x is a32_ul android 4.4, and asia htc626 is a32_ul 1.7 ghz , htc 626 mediateck chipset only, and then their is htc626v, htc 626phv ,so seems is many flavours of htc626 metro?? not sure an these but they all got same name but all are separate hardware incompatible with each other htc just loves the name htc desire 626 and if they build a phone and dont know what to call it then default seems to be htc desire 626 as they know people will buy it. just putting name desire will make us want to desire it
regards frankgambit

frankgambit said:
problem is what continunt u are on to what htc 626 you got in america htc626 and htc626s both are a32e_ul android 5.1, in europe htc626 is a a32_ul 64bit 1.2ghz android 5.1, in asia htc626x is a32_ul android 4.4, and asia htc626 is a32_ul 1.7 ghz , htc 626 mediateck chipset only, and then their is htc626v, htc 626phv ,so seems is many flavours of htc626 metro?? not sure an these but they all got same name but all are separate hardware incompatible with each other htc just loves the name htc desire 626 and if they build a phone and dont know what to call it then default seems to be htc desire 626 as they know people will buy it. just putting name desire will make us want to desire it
regards frankgambit
Click to expand...
Click to collapse
yes I have htc626x a32_ul android 4.4 model. I tried many ways to root the device. bootloader is already unlocked. king root app gives temporary root that lasts for about 1 minute. there is no any 626x thread at xda developer.

chanakalk said:
yes I have htc626x a32_ul android 4.4 model. I tried many ways to root the device. bootloader is already unlocked. king root app gives temporary root that lasts for about 1 minute. there is no any 626x thread at xda developer.
Click to expand...
Click to collapse
I rooted my device successfully using http://forum.xda-developers.com/desire-626/help/step-step-root-procedure-htc-desire-t3264727 this procedure