• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Still No Root?

D

D33PTHAWTE

Newbie
I'm dismayed that there still isn't any documented root procedure for the HAM2.
I've been scouring the web and have tried several different methods. I thought I was on to something with a manual root guide on xda, however I wasn't ever able to get the last few steps to work. I tried towelroot and an impactor tool by saurik that I had high hopes for. Each method seemed like it could work, but neither did.
I'm to the point now that I'm actually considering paying $20 on ***************** for one of their guys to remotely root my device. I had considered offering a bounty on root anyway I suppose. Just thought for sure someone would come up with something for this awesome device.
 
More bad news I'm afraid: coughed up the $20 for online remote rooting by expert. Completely fruitless and really disappointing. I expected an expert in adb command line to remotely access my PC and root my HAM2. Instead this guy just kept downloading and trying different free one-click root tools...needless to say I got a refund.
Even the highest-end devices like the Galaxy S5 are being simply rooted and we can't get root? What gives? I cannot imagine that Huawei has stiffer anti-tamper measures than the largest phone maker in the world. And yet here we are out in the cold.
I'm open to suggestions, I'll also pledge $50 on a root/custom recovery bounty.
 
I think it's because the user base is not that big for this phone at the moment. It should pick up though but not soon enough.

D33PTHAWTE said:
More bad news I'm afraid: coughed up the $20 for online remote rooting by expert. Completely fruitless and really disappointing. I expected an expert in adb command line to remotely access my PC and root my HAM2. Instead this guy just kept downloading and trying different free one-click root tools...needless to say I got a refund.
Even the highest-end devices like the Galaxy S5 are being simply rooted and we can't get root? What gives? I cannot imagine that Huawei has stiffer anti-tamper measures than the largest phone maker in the world. And yet here we are out in the cold.
I'm open to suggestions, I'll also pledge $50 on a root/custom recovery bounty.
Click to expand...
 
This phone with root would literally make me so happy.

Post on the XDA device forum request thread! I can't link to it as I just joined, but I'm sure you can Google it. Hopefully if there are enough requests, they will make the new forums, our phone will get more users and possibly developers, and we would finally see root!
 
Does this device have a custom recovery such as CWM and/or TWRP? I do not have this device but I am willing to assist. Just need someone with a general understanding of requiring some info, I.e., the system partition for starters?
 
ModdingMyMind said:
Does this device have a custom recovery such as CWM and/or TWRP? I do not have this device but I am willing to assist. Just need someone with a general understanding of requiring some info, I.e., the system partition for starters?
Click to expand...

There isn't a custom recovery yet.
I have a basic knowledge of adb and android, and I'll help you anyway I can.
How can I get the info you need about the system partition?
 
D33PTHAWTE said:
There isn't a custom recovery yet.
I have a basic knowledge of adb and android, and I'll help you anyway I can.
How can I get the info you need about the system partition?
Click to expand...
Could you type and enter, cat /proc/emmc. Hopefully that will bring a list up showing what partitions are what on your device.

If I know where your system partition is located I could possibly write up a very simple flashable zip which could be installed through your stock recovery. Just need to know where your system is lol.
 
Type and enter, mount, in the terminal. It should show all the partitions which are currently mounted on your device. Scroll through and look for /system. Give me that information. Or even better to make it simple, copy and paste all of it and send it to me lol. The sooner the better :-)

deb05961b0af8c70dad49a10ebfaa78f.jpg


You should see something very similar to the picture I just shared from my device.
 
ModdingMyMind said:
Type and enter, mount, in the terminal. It should show all the partitions which are currently mounted on your device. Scroll through and look for /system. Give me that information. Or even better to make it simple, copy and paste all of it and send it to me lol. The sooner the better :-)
Click to expand...

I couldn't fit all of it on one screenshot; in the first screenshot, the second screenshot starts at "none dev/frz cgroup rw,relatime, freezer 0 0"

Screenshot_2014-08-23-12-43-22.png

Screenshot_2014-08-23-12-43-27.png
 
ScoobSTi said:
I couldn't fit all of it on one screenshot; in the first screenshot, the second screenshot starts at "none dev/frz cgroup rw,relatime, freezer 0 0"

Screenshot_2014-08-23-12-43-22.png

Screenshot_2014-08-23-12-43-27.png
Click to expand...
My man! Thanks. Gonna make the flashable zip and send it to you as a PM. If you are not willing to test let me know.
 
ScoobSTi said:
I wish I could help, but I really don't know anything about writing, ADB, and all that.

Hopefully you and D33P will be the saviors of us HAM2 users!

We also finally have our own device thread on XDA.
Click to expand...
Quick favor needed. Boot in to your recovery. Please let me know what all options are seen available while in your recovery. Need this info quickly :-)
 
ScoobSTi said:
This phone with root would literally make me so happy.

Post on the XDA device forum request thread! I can't link to it as I just joined, but I'm sure you can Google it. Hopefully if there are enough requests, they will make the new forums, our phone will get more users and possibly developers, and we would finally see root!
Click to expand...
Sent you a PM
 
Sorry for the delay guys. Was working on a project of mine. Trying to embed some binary data into a shell script because the script needs the binary to properly work. Adding the binary data in to the script gives the user the option to install the binary on to their device if the script detects the binary is not found. However, in the midst of my testings I managed to put my phone in a bootloop due to a human error on my part and wasn't able to resolve it until this morning when I got access to my laptop. Back up and running again lol.

ScoobSTi, you sent me a PM with what you saw being displayed from within your recovery. It was asking you to make sure your device was plugged in via usb? Was there no other options for you? I'm curious since it would not make sense for the stock recovery to ask you to plug your device up via usb. The reason I say this is because if your device were to receive an OTA for example, it would apply itself from within the phone and without the use of a pc. So, could you ellaborate on this a bit more for me. Need a better understanding on what your stock recovery can do.

With that said, a lot of stock recoveries will normally have a "secondary recovery" which looks VERY SIMILIAR to CWM. A lot of times when such people with such recoveries boot up in to their stock recovery will normally see a download symbol of some sort and thereby pressing the volume up key then the power button key would load up that CWM look alike screen where you would then be able to install zips manually from within your phone. This is the ultimate goal here. To be able to install the update.zip I sent you manually from within your stock recovery so that it will place the su binary at /system/bin and then chmod that binary appropriately to give it root access whereas you would then reboot the device, install SuperSU from the playstore, and voila - rooted HAM2.

There is one concern I have though and that is how well your device accepts update.zip files with a signature used by testkeys - will find out though. Worst case, it denies the signature and aborts the installation which will cause no harm. If that ends up being the case then it will be a matter of figuring out the proper signing method for your device.
 
ModdingMyMind said:
Sorry for the delay guys. Was working on a project of mine. Trying to embed some binary data into a shell script because the script needs the binary to properly work. Adding the binary data in to the script gives the user the option to install the binary on to their device if the script detects the binary is not found. However, in the midst of my testings I managed to put my phone in a bootloop due to a human error on my part and wasn't able to resolve it until this morning when I got access to my laptop. Back up and running again lol.

ScoobSTi, you sent me a PM with what you saw being displayed from within your recovery. It was asking you to make sure your device was plugged in via usb? Was there no other options for you? I'm curious since it would not make sense for the stock recovery to ask you to plug your device up via usb. The reason I say this is because if your device were to receive an OTA for example, it would apply itself from within the phone and without the use of a pc. So, could you ellaborate on this a bit more for me. Need a better understanding on what your stock recovery can do.

With that said, a lot of stock recoveries will normally have a "secondary recovery" which looks VERY SIMILIAR to CWM. A lot of times when such people with such recoveries boot up in to their stock recovery will normally see a download symbol of some sort and thereby pressing the volume up key then the power button key would load up that CWM look alike screen where you would then be able to install zips manually from within your phone. This is the ultimate goal here. To be able to install the update.zip I sent you manually from within your stock recovery so that it will place the su binary at /system/bin and then chmod that binary appropriately to give it root access whereas you would then reboot the device, install SuperSU from the playstore, and voila - rooted HAM2.

There is one concern I have though and that is how well your device accepts update.zip files with a signature used by testkeys - will find out though. Worst case, it denies the signature and aborts the installation which will cause no harm. If that ends up being the case then it will be a matter of figuring out the proper signing method for your device.
Click to expand...

Maybe I need to press some more buttons to find the actual recovery. The screen I found where it asked me to plug in the USB cable had the same CWM Android robot with its "front panel" open.

I'll try some combos and report back!
 
ScoobSTi said:
Ok, I found the recovery. For our phone, you have to hold the power button and volume +. It will bring you to this CWM lookalike.

wd2VvE7.jpg


If I put the .ZIP on the external SD and use the recovery to flash it, will it brick my phone if it fails?
Click to expand...
No, it will not. And good job finding it. The zip will place the su binary to /system/bin. It will give the su binary proper permissions. That is all it will do. No more. Very simple process. It's impossible for this procedure to cause a soft or hard brick. So, to answer your question, you will be fine :-). Keep in mind. The recovery may abort the update.zip. If that happens then don't freak out lol. Your device is still fine. That basically means it denied installing the update.zip which would most likely mean the signature used to sign the update.zip wasn't accepted by your recovery. It is required to sign an update.zip but some phones won't accept just any kind of signature. Some phones want the signature to be precise. Report back and let me know. If the installation is successful, then reboot your device, go to the playstore, install SuperSU.
 
ModdingMyMind said:
No, it will not. And good job finding it. The zip will place the su binary to /system/bin. It will give the su binary proper permissions. That is all it will do. No more. Very simple process. It's impossible for this procedure to cause a soft or hard brick. So, to answer your question, you will be fine :-). Keep in mind. The recovery may abort the update.zip. If that happens then don't freak out lol. Your device is still fine. That basically means it denied installing the update.zip which would most likely mean the signature used to sign the update.zip wasn't accepted by your recovery. It is required to sign an update.zip but some phones won't accept just any kind of signature. Some phones want the signature to be precise. Report back and let me know. If the installation is successful, then reboot your device, go to the playstore, install SuperSU.
Click to expand...

Unfortunately, the installation was aborted. How would you go about finding out which signature is required? I have no idea how this stuff works! :p
 
You have what all you need. Now, you just need to get your recovery to accept it. Not sure if your bootloader is locked. If it is, then possibly unlocking your bootloader may help in this process. Most devices for unlocking the bootloader is rather simple. Just boot your device in to the bootloader, plug device in to computer, now do the following:
Code: 
fastboot devices

Should display your devices' serial number. This means they are communicating. You are merely confirming this.

Next,

Code: 
fastboot oem unlock

SIMPLE, right lol.

Some other devices out there like to make it a little more tedious (like HTC for example).
 
Unfortunately, typing "fastboot oem unlock" gave me a big "FAILED" error. The "fastboot devices" command gave me some letters and numbers, so I'll assume they are the serial.

The error says:
Code: 
FAILED <remote: Please input key>
finished. total time: 0.005s

I used this tool to try it.
 
You must log in or register to reply here.
Back
Top Bottom