Some Progress in Rooting the HAM2 - Huawei Ascend Mate 2

I personally own a HAM2 with model number MT2L03. I know in China, this phone but of different model number has been rooted. I was trying to re-do the rooting process on my own phone. After several weeks' work, I got some progress.
Thanks to your feedbacks! Now we have fully rooted the beloved phone! Hooray!
Since I am not an expert in Android system, I can not guarantee your success.
PLEASE TAKE YOUR OWN RISK.
Make long story short, the essential step is to unlock the bootlloader.
==WARNING: UNLOCKING BOOTLOADER WILL PERFORM FACTORY RESET. BACKUP YOUR PHONE FIRST!==
To unlock the bootloader, you need the unlock code of your phone. I asked a friend in China who had a software to get the unlock code for Huawei cellphones, or maybe you can email Huawei to get the one for you. I am not able to post links so I repacked the software and upload it here. Let me know if you think this is not appropriate.
Remark: There is an image down there for instructing using this software.
Please input your S/N and IMEI and make the setting like in the imaged packed. Click the lower left button, you should get your unlock code in a text file on your desktop, which is a 16 digits code.
Once you get your unlock code, please reboot into fastboot mode and unlock your phone. THIS STEP WILL DO A FACTORY RESET FOR YOUR PHONE.
For those who are not familiar with adb or fastboot, here is how.
First open the USB debugging mode on your phone and connected it to your computer. Use adb to enter the fastboot mode.
Code:
adb.exe wait-for-device
adb.exe reboot bootloader
Now your phone should have been rebooted into fastboot mode. There will be a note LOCKED on the top of the screen. Then use fastboot and your unlock code to unlock your phone
Code:
fastboot.exe devices
fastboot.exe oem unlock YOUR_UNLOCK_CODE
If everything goes well, your phone will do a factory reset and reboot automatically. Now you have successfully unlock your phone.
Then I use those one-click rooting softwares to get the root access. In my test, root genius and baidu root both did the job. I don't have recommendations for you since both root access management software s**k.
Update: Please use Kingo root on PC end or towelroot on the android end to get root access and install SuperSU
And you are all set. Should be able to gain root access and uninstall apps you don't need. Also Titanium backup acts just perfectly.
Update: Xposed Frameworks are partially functional. Please disable the resources API and it shall work.
Thanks for reading.

To unlock the bootloader is one important first step. Great news.

This great! I'll try on my phone after I get everything backed up. Did you try towelroot, framaroot or eroot?

THIS IS IT!!!!!!!!!!!!!!
Thank you.... After get this phone last week, and read enormous thread, onekey root method, failure, failure, now this come right on time!!!
D:\Android\android-sdk\platform-tools>fastboot oem unlock 118187202XXXXXXXXXXX
...
(bootloader) Unlocking ...
OKAY [ 0.020s]
finished. total time: 0.020s
D:\Android\android-sdk\platform-tools>fastboot oem get-bootinfo
...
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.040s]
finished. total time: 0.040s
===================================
Just to warn everyone again, This will automatically factory reset your phone.

Quickly I have made a translation of the software, please let me know if you have any questions.
I only use the software to retrieve the unlock code, and use command line to do the unlock.
{
"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"
}
The 16 alphanumeric S/N number should come from somewhere back of the battery after remove the back cover, or (more unreliable, but I am lazy) it is also in the sticker of the package.
If you get above error, it mean the gotcha code is wrong, you can click the link right of the gotcha image in step 7 to change the gotcha image to a easier one. Other error dialog box should have "SN" or "IMEI" text etc so I will not post picture.
Below attachment is same as above pic.

aragon257 said:
This great! I'll try on my phone after I get everything backed up. Did you try towelroot, framaroot or eroot?
Click to expand...
Click to collapse
Hello aragon257, I tried eroot but not working. towelroot not working either but didn't try change the mod strings. It might be possible to root the phone using towelroot. Let me know if you succeed.

Can someone help me?
Here is what I am looking at...
I have question marks at the top. Also it doesnt seem to allow me to unlock because of the 3rd field. Something needs to go in it, but what?
EDIT:
Nevermind... @xordos description helped me

xordos said:
Quickly I have made a translation of the software, please let me know if you have any questions.
I only use the software to retrieve the unlock code, and use command line to do the unlock.
Click to expand...
Click to collapse
Thanks for your translation! I was too sleepy to do the job last night.

has anyone tried Kingo?
---------- Post added at 10:48 AM ---------- Previous post was at 10:32 AM ----------
hey @ScoobSTi check this out
YEEEEEEEEEEEEEEEEEESSSSSSSSSSSSSSSSSSSSSSSSSSS
World's first rooted HAM2 US VERSION!!!!!

dbmj said:
I also checked eroot without luck, and towelroot might work but was too sleepy to check all those mod strings. If you are able to do that and install SuperSU, please let me know.
And you are all set. Should be able to gain root access and uninstall apps you don't need. Also Titanium backup acts just perfectly.
Actually the root is not 100% success because of the lack of SuperSU. But still I can do a lot with the *partially* rooted phone. Hope this can help and some one could come up with a method to finish the root.
Thanks for reading.
Click to expand...
Click to collapse
Hi, Have you installed Busybox?
I first attempt of install SuperSU also failed...Following is what I did and all looks worked:
1) update: RootGenius rooting come with KingUser as root management tool, not recommenced.
I use root RootGenius successfully root the phone, actually the english version not work, but the chinese version worked.
09/05/2014 10:34 AM 5,717,592 RootGenius.exe (worked)
09/05/2014 10:31 AM 4,954,744 RootGenius_en.exe (not work)
After root, the su binary is like this:
ls -l /system/xbin/su
-rwsr-sr-x root root 34124 2014-09-05 10:35 su
2) Then I installed busybox from play store, then installed SuperSU from "ChainFire".
ls -l /system/xbin/su
-rwxr-xr-x root root 125420 2014-09-05 10:42 su
-rwsr-sr-x root root 34124 2014-09-05 10:35 ku.sud
It first also show unsuccessful when updating su, but after a few retry, and rebooting, it says SU updated successfully.
EDIT: above su looks like not normal, but anyway, that maybe a different topic.

---------- Post added at 10:53 AM ---------- Previous post was at 10:52 AM ----------
Use Kingo...
WARNING!!! This took several minutes and phone rebooted probably a dozen times. Just do not unplug it and let it run its course.
---------- Post added at 11:02 AM ---------- Previous post was at 10:53 AM ----------

xordos said:
Hi, Have you installed Busybox?
I first attempt of install SuperSU also failed...Following is what I did and all looks worked:
1) I use root RootGenius successfully root the phone, actually the english version not work, but the chinese version worked.
09/05/2014 10:34 AM 5,717,592 RootGenius.exe (worked)
09/05/2014 10:31 AM 4,954,744 RootGenius_en.exe (not work)
After root, the su binary is like this:
ls -l /system/xbin/su
-rwsr-sr-x root root 34124 2014-09-05 10:35 su
2) Then I installed busybox from play store, then installed SuperSU from "ChainFire".
ls -l /system/xbin/su
-rwxr-xr-x root root 125420 2014-09-05 10:42 su
It first also show unsuccessful when updating su, but after a few retry, and rebooting, it says SU updated successfully.
Click to expand...
Click to collapse
Thanks. I'll try when I get home.

EVERYONE PAY UP!!!
ha ha ha ha
Look @Modding.MyMind
I just wanna say we all rallied together to get this done. Good work everyone! This phone just became 100 x better!

zzEvilGeniuszz said:
has anyone tried Kingo?
---------- Post added at 10:48 AM ---------- Previous post was at 10:32 AM ----------
hey @ScoobSTi check this out
YEEEEEEEEEEEEEEEEEESSSSSSSSSSSSSSSSSSSSSSSSSSS
World's first rooted HAM2 US VERSION!!!!!
Click to expand...
Click to collapse
You rooted your HAM2 with Kingo only?

rekamyenom said:
You rooted your HAM2 with Kingo only?
Click to expand...
Click to collapse
Unlock your bootloader using the instructions on page 1 of this topic then install Kingo on your PC. Put your phone in USB DEBUGGING and plug it in. Then root using Kingo.
That's it!
All along it was the locked bootloader that prevented root access, so naturally when the bootloader was unlocked it was much easier.
This took a while and seemed to hang but it did not. It rebooted probably a dozen times until it finally said ROOT SUCCESSFUL!
I unplugged phone and plugged it back in a checked root status on Kingo and it said it wasnt rooted. So then I installed a root checker on my phone from the play store and checked status and it said it was in fact rooted.
Since then, I have verified root so I do not know why Kingo said it wasnt rooted after i plugged it back in. No matter, it is done.

zzEvilGeniuszz said:
Unlock your bootloader using the instructions on page 1 of this topic then install Kingo on your PC. Put your phone in USB DEBUGGING and plug it in. Then root using Kingo.
That's it!
All along it was the locked bootloader that prevented root access, so naturally when the bootloader was unlocked it was much easier.
This took a while and seemed to hang but it did not. It rebooted probably a dozen times until it finally said ROOT SUCCESSFUL!
I unplugged phone and plugged it back in a checked root status on Kingo and it said it wasnt rooted. So then I installed a root checker on my phone from the play store and checked status and it said it was in fact rooted.
Since then, I have verified root so I do not know why Kingo said it wasnt rooted after i plugged it back in. No matter, it is done.
Click to expand...
Click to collapse
Cant get the bootloader unlock code... Got the ????????????? Like you had.

rekamyenom said:
Cant get the bootloader unlock code... Got the ????????????? Like you had.
Click to expand...
Click to collapse

zzEvilGeniuszz said:
Click to expand...
Click to collapse
Yup, tried that like 10 times. I will take a screen shot of what I am getting

rekamyenom said:
Yup, tried that like 10 times. I will take a screen shot of what I am getting
Click to expand...
Click to collapse
This is what I get

rekamyenom said:
Yup, tried that like 10 times. I will take a screen shot of what I am getting
Click to expand...
Click to collapse
Do you have the correct drivers installed? Does ADB detect your device?
Try lowercasing the hx37

Related

[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)

{
"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"
}
Options:
1) Fresh Root - This is to do a clean root on your stock Asus JB rom or any other custom rom. Great for any users that lost root during an upgrade.
2) Fresh Start - This will give you a clean start by wiping your system partitions (backup your data) then flashing a stock JB image. After the package will do a clean root to the TF201 (Make sure you download the JB update for your region from the Asus site then extract and place the "blob" file in the same folder as this package and rename to "system.blob"
!!! This is for users with from any region with unlocked bootloaders only !!!
I made this because a few users have had trouble with root after the JB update from Asus. What I have made is an automated package that includes the root binaries and the the Team Win Recovery. From FASTBOOT this package will flash a custom recovery then root it. If a previous broken root from an update exist it will remove the old broken root and re-root it. Simple as that!
Additionally I have made another option in this package called "Fresh Start" and what this will do is wipe you tablet clean (backup your data) then flash a new image of JB. Once completed it will flash the custom recovery and root it before you even sign-in and set up the tablet. I recommend this as it will make the tablet nice, clean & speedy.
This assumes you have the correct drivers installed for your device, if not I recommend my Universal Naked Drivers Here
Credits:
Root Binaries - (ChainsDD) http://androidsu.com/superuser/
Recovery - (TeamRecovery) http://www.teamw.in/project/twrp2
**************************************************
This thread is not for help with unlocking your device or the naked drivers.
Hashes:
CRC32: 8C62EA76
MD5: 2E946D245F3778A5DEF2D07C00F8EF4B
SHA-1: 343661C655399CBE77E5D2946B59CFCCB77A1A69
Thanks
*ninja reserved*
I was so happy to see this and miss the "for unlocked bootloader only"
Anyway hope someone could come up for Locked Bootloader.
:EDIT_THANKS
Hey there,
after some issues i made the root!
great work!
thank you 1wayjonny!
:EDIT_SOLVED
think i made it. don´t know why, but after the 30 try the bat said finished, okay...
:EDIT_ORIGINAL
Hey everyone,
i got a problem, i flashed my tf201 with the new JB rom from the asus website, my device is unlocked. no root before. now i can´t root it...
everytime i start the "Fresh Root.bat" or the "Fresh Start.bat" i get multiple lines with
"FAILED (command write failed (Unknown error))"
can anybody help me?
greetz andy
howsed said:
Hey there,
after some issues i made the root!
great work!
thank you 1wayjonny!
Click to expand...
Click to collapse
Thanks for the feedback, being its automated you just have to get use the on screen instructions. I wiped and re-flashed, then rooted about 30x in a row with this package so I thought I would release to others to make their life easier.
If anyone has suggestions for any instructions that were not clear enough let me know and I can update for clarity.
howsed said:
:EDIT_THANKS
Hey there,
after some issues i made the root!
great work!
thank you 1wayjonny!
:EDIT_SOLVED
think i made it. don´t know why, but after the 30 try the bat said finished, okay...
:EDIT_ORIGINAL
Hey everyone,
i got a problem, i flashed my tf201 with the new JB rom from the asus website, my device is unlocked. no root before. now i can´t root it...
everytime i start the "Fresh Root.bat" or the "Fresh Start.bat" i get multiple lines with
"FAILED (command write failed (Unknown error))"
can anybody help me?
greetz andy
Click to expand...
Click to collapse
You have missed the step that mounts the /System from recovery. This has to be done manually then ADB can push ROOT. It said write failed so i assume this is where you got stuck.
1) Make sure you run as "Admin" just in case
2) When you boot into the custom recovery, you must select the "Mount" icon then then select system. After then you continue with the batch file and all should be good.
I can confirm that this worked w/ my TF201. Thanks a bunch!
I was unlocked and had root plus a "backup" according to Voodoo OTA RootKeeper. I manually installed the JB update via sdcard and lost root plus all signs of root. Being unlocked, I used your method in Win7 (parallels virtual machine on mac) running a shell as admin and everything worked without any hitches. I have root and have verified by Voodoo OTA, Root Explorer, and Titanium Backup.
A big thanks to you for this. I now have root again!
Robert
Ha ha ha ha! Root Restored!
Sir, You are a God! I lost root when I manually updated to JB using the Micro SD Card method. Followed your guide and am now rooted on JB! Sixaxis gaming Nirvana restored! Thank you!!!
---------- Post added at 08:25 PM ---------- Previous post was at 08:24 PM ----------
I can also confirm that the Asus Unlock tool worked for me.
I just tried this the total fresh start (blob method ). Got to last stage (mount system). Adb no device found . How can I rectify this .
Edit I updated sdk today .. tried naked drivers etc still cant get it to recognize it
Sent from my GT-I9300 using Tapatalk 2
adz63 said:
I just tried this the total fresh start (blob method ). Got to last stage (mount system). Adb no device found . How can I rectify this .
Edit I updated sdk today .. tried naked drivers etc still cant get it to recognize it
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
For anyone having issues with the ADB command I would manually try ADB before this package. This package assumes you have your drivers working in FASTBOOT & ADB. Or when you get the recovery flash and you have booted the recovery open a second prompt and try the "adb devices" command before this package pushes root.
I see that you have quite a few amount of post and would think you have some experience, since you are still having issues I would say that the drivers are dirty or something else weird is going on.
You have mentioned you get the recovery flash then booted, at this stage can you go to your device manager and take a screen shot of the Android device? You may have to repoint the device to the drivers but non the less a screen shot would help.
is there something like this but not for unlocked bootloader? I lost root on OTA but i didn't have it unlocked and don't want it to be fore now, I'm just using stock.
Works beautifully!
Thanks for root back!
I'm running CM10 unofficial right now but it's giving me some issues I'd rather not deal with right now...it already has the JB bootloader...can I still flash this to go back to stock[JB]?
I was wondering how to reinstall a recovery and to root again... Thanks!
Note: i just copy command lines from the bat file because i'm on linux.
Just wanted to say: it worked perfectly and painlessly on my already unlocked but otherwise stock prime!
Hi,
Coming from Completely Stock Prime with JB update. Unlocked BL via Asus Tool then used this method and everything went Perfect!! Thanks for your Effort.
I have to say that I'm glad to see you made this, worked great. Tried many other ways to root jb after I flashed androwook and lost custom recovery and root.
You're awesome!
Sent from my SGH-T999 using xda premium
Q
Do i lose erverthink or will i keep my current stock rom whitout installing erverthink.
Thanks works like a charm, unlocked my prime and installed the naked driver let the batch file do it work. back on rooted system with everything working
So I'm trying to do the Fresh start but can't for the life of me figure out how to move and rename the blob file unfortunately. I've got the extracted JB update file on my desktop but can't rename the blob file, right clicking it won't give me the option...
I'm supernoob with this device so can anyone please walk me through or figure out what I'm missing? Please...
Edit: well, looks like I've just gotten myself an unrecoverable bootloader...
more detailed instructions would be appreciated
I am a noob to this device and just unlocked the bootloader.
Can you post detailed step-by-step instructions for your method in the OP or PM. I am also wondering if TWRP version has been updated to 2.3.
Thank you very much.
EDIT: I am all set. Thanks.

[Q] Rooting Cubot s208

Hi Guys
I'm trying to root this phone so after a bit of looking around I have vroot and all the drivers for the phone.
I have the English version of the software but half way through the root, it ask for something to be done in Chinese which I'm not sure what it needs.
On screen I get the options to hit next and on the phone its enable restore or not.
Anyone have any clues as to what needs to be done to stop the root failing ?
Thanks
Richie
No one else ever root this device?
richie1888 said:
No one else ever root this device?
Click to expand...
Click to collapse
I Did, just install Vroot or RootGenius they should do the trick.
i went for RootGenius
i suggest u to install CWM recovery after rooting and keeping a copy of the original rom
Sorry i cannot post link since i registered only to answer
Thanks, Trabacchin.luigi - most helpful Just got my S208 today and XDA first place to come for helpful info
RootGenius did not work, but then again, I am running it in Paralells desktop on MAC which may be the issue. Awaiting for a Windows machine to be free to try it on that.
Thanks again,
Jeff
---------- Post added at 12:55 PM ---------- Previous post was at 12:40 PM ----------
Update - Vroot worked first time.
Couple of pointers for others:
RootGenius loads LOTS of junk stuff to your PC unless you custom install and be VERY CAREFUL to deny loading of "apps". Lots of double-negative options, looks like you are saying "no" but you are really saying "yes". Be careful.
Vroot worked straight away - BUT loads some Chinese options on your phone and all of a sudden your call logs, contacts, SMS etc are being accessed. All text in Chinese characters so do not know what exactly the apps are. Deleted.
Jeff
Well, I had LOTS of problems subsequently with Vroot (now iRoot). In the end, I unrooted and used KINGO ROOT and it worked first time, with no extra odd apps loaded, doing who-knows-what (iRoot add-ons!).
Anyway, have now rooted the S208 and I hope to be able to update the firmware, resizing the partitions at the same time.
Look here http://www.android-hilfe.de/8390125-post4.html
Install mentioned recovery using flash tool, boot into recovery, leave recovery and answer question to install SU by swiping slider. After reboot into ROM, let SU do update (it will ask you) and voilá phone is rooted
root Cubot S208 using KingRoot (I installed also Purify)
trabacchin.luigi said:
I Did, just install Vroot or RootGenius ...
Click to expand...
Click to collapse
tested RootGenius and Vroot (now iRoot) *installed lot of spam*.
I rooted my firmware CUBOT_4041C_V12 original buil using KingRoot (I installed also Purify) using this xda download link:
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
and next
http://forum.xda-developers.com/devdb/project/dl/?id=13663&task=get

zte z831

How do i root my zte z831/chapel? if there is one will somebody please explain it to me?:crying:
ZTE MAVEN 2 Z831 - Android 6.0.1 - Messaging App .3
I just got this new AT&T phone and need to root it to delete this bloatware!! Also need to fix Messaging App .3 - I just got this phone and the Messaging App is crashing constantly!
I've searching all around, tried everything recommended, Kingo desktop and one-click as well as SRS... tried all recommended fixes for Messaging App and NOTHING ...
Experts please reply?!?
To start off. If the ZTE maven 2 was bought from a carrier your phone is boot loader locked. Until your phone's boot loader is unlocked by some soft ware or a source available rooting the ZTE maven 2 will be impossible. Even I the bootloader was unlocked there is still no custom Roms made for this phone yet. Definitely the first thing needed will be the TWRP program. So far no new methods of rooting or unlocking the boot loader yet.
Ok... So are we saying it's not possible? Or it is possible with a difficult process?
Lookingforinfo said:
To start off. If the ZTE maven 2 was bought from a carrier your phone is boot loader locked. Until your phone's boot loader is unlocked by some soft ware or a source available rooting the ZTE maven 2 will be impossible. Even I the bootloader was unlocked there is still no custom Roms made for this phone yet. Definitely the first thing needed will be the TWRP program. So far no new methods of rooting or unlocking the boot loader yet.
Click to expand...
Click to collapse
Mine has an OEM unlocking option under Developer options ...
Sent from my LG-V410 using XDA-Developers mobile app
Has anyone made progress with the Z831
errata
i have gotten kingroot apk to successfully rooted my maven z831.
Only the apk worked, the windows version did not.
However, its not persistent between reboots.
But, i only need to root the phone and remove bloatware, so that work fine for me.
one more thing to note: the first 2 times after reboot, kingroot was able to smoothly root the phone again.
by the third time, it took a bit longer to root and went thru 2 reboots, between the same rooting process, which is normal.
So, if you want to remove bloatware, i would suggest: install titianium backup root (TI), root the phone, use TI to remove bloat
Tested kingroot 5.0.5, achieved partial root and it doesn't persist. cannot grant SU privilege to some apps. cannot remount partition as R/W, so you are not really "deleting" the bloatware, it will come back after reboot. Also very unstable, will have frequent random power offs which resets root. Tried to replace with Super SU and make changes via terminal but nothing worked yet.
How did you get it to work? I have tried to run it multiple times and it won't root with Kingoroot on my Maven 2 ZTE z831.
smith.ks1028 said:
How did you get it to work? I have tried to run it multiple times and it won't root with Kingoroot on my Maven 2 ZTE z831.
Click to expand...
Click to collapse
Make sure you are running the latest version of kingroot.
is there a forum for this phone?
cfli1688c1 said:
i have gotten kingroot apk to successfully rooted my maven z831.
Only the apk worked, the windows version did not.
However, its not persistent between reboots.
But, i only need to root the phone and remove bloatware, so that work fine for me.
one more thing to note: the first 2 times after reboot, kingroot was able to smoothly root the phone again.
by the third time, it took a bit longer to root and went thru 2 reboots, between the same rooting process, which is normal.
So, if you want to remove bloatware, i would suggest: install titianium backup root (TI), root the phone, use TI to remove bloat
Click to expand...
Click to collapse
I'm starting to get mad. Has anyone made any progress on rooting this damn phone since it is such low memory?
JDeschaine1985 said:
I'm starting to get mad. Has anyone made any progress on rooting this damn phone since it is such low memory?
Click to expand...
Click to collapse
I got perm root did u miss my last post where it shows it? We don't have a forum to my knowledge for the maven 2 for me to post a guide if we get one I will post a guide on how to root it perm with kingroot
Nope,
I didn't see that post. Would you mind sending it to me?
JDeschaine1985 said:
I'm starting to get mad. Has anyone made any progress on rooting this damn phone since it is such low memory?
Click to expand...
Click to collapse
Here's how I got my zte maven 2 (ATT) rooted.
Disclaimer: This method worked for me but may not work for others, I am not responsible if your device is bricked as a result of this. Also, this method does seem to be a bit finicky and inconsistent.
Credit to @madvane20 his post here helped me get root for this phone. He also got his phone rooted before I did, be sure to give him thanks.
Credit to @ZTE Girl for finding a way to remove ads from King root and keeping perm root.
With KingRoot you can get perm root, but personally I hate KingRoot, so at the end there is a method to replace KingRoot with SuperSu. Unfortunately SuperSu root resets on reboot, but a quick, 10 second adb command will reroot your phone with SuperSu
Edit: @ZTE Girl found that using lucky patcher to remove ads from King root worked for her and kept permroot.
Step 1: Enable USB debugging on your phone, and download adb and ZTE drivers to your PC.
2: Download KingRoot from KingRoot.net (download the apk for android)
3: Connect your phone to ADB, and run this command in terminal adb shell make sure you get no errors and accept any USB debugging requests.
4: Now type reboot disemmcwp This will reboot your phone without write protection.
5: When your phone reboots, run adb shell again, and install the kingroot APK. Google will give you a warning about this app being unsafe, install it anyways.
6: Now, here's the finicky part, sometimes KingRoot works, sometimes it doesn't, you just have to keep trying. Make sure your phone is still connected to the computer through adb shell, and then click try root in KingRoot. While KingRoot is attempting to get root: in adb shell keep typing su and pressing enter. Just spam this, It will keep giving errors, but eventually it (should) work. Make sure to accept any prompts on your device while you do this.
7: When you are able to successfully get into su, wait a bit, just to make sure your device doesn't restart
8: Now type getprop ro.product.name, the response should be Z831
9: Now type setprop persist.sys.k Z831, then type getprop persist.sys.k It should say Z831
10: Now type cd /dev/block/platform/soc.0/7824900.sdhci/by-name/
11: Then type dd if=recovery of=/sdcard/recovery.img This will backup your recovery, I highly recommend that you copy the backup to your computer in case something goes wrong.
12: Now type dd if=boot of=recovery, this will write boot to recovery. This part can be risky, it worked for me, but if it bricks your device, you can't say I didn't warn you with that said, don't let that scare you away from finally rooting this device and getting all the advantages that come with it
13: Now type this reboot recovery Your device my blackscreen and not boot after this, personally mine did, and I fixed it by removing the battery, and after puttting it back in, it booted normally.
14: When your phone boots up, type adb shell again, and then type su
15: Type id response should be "uid=0(root) gid=0(root) context=u:r:shell:s0" Note: I don't think my uid showed when I did this, if yours doesn't show, don't worry, it should work fine.
16: Now type setenforce 0
17: After that, type getenforce, it should respond back with "permissive"
18: To test if system is writable, type mount -o remount,rw /system, if you get no errors, everything is working , if you get an error, type reboot disemmcwp, and then try to mount system RW again.
19: I would recommend removing the update service now, so an update doesn't come and screw up your root.
20: Read this: Now you should have permroot with kingroot, however, as you will soon find, kingroot has a ton of ads, and can get very annoying. So, if you want SuperSu and no kingroot, keep reading. If you want to keep KingRoot, then you are done, have fun with your rooted Maven 2
Edit: @ZTE Girl found that you can use lucky patcher to remove ads from Kingroot while still keeping permroot.
21: Download the KingToSuperSu zip in attachments, I have modified it slightly from the original zip so it works better. You will see a folder inside the zip named "mrw" copy this folder to the root of your /sdcard (must be copied to the root of /sdcard)
22: Now go into adb shell again, and then type su
23: Type mount -o remount,rw /system
24: If you get no errors, simply type sh /sdcard/mrw/root.sh, you will see a lot of errors in the script, no need to worry, now you should have SuperSu. Note: sometimes you get a notification saying "com.eu.chainfireSuperSu has stopped" or something like that, run the command again, and it should work.
25: SuperSu will say binary needs to be updated, but the update always fails, however you can click no thanks, and it will work fine.
26: SuperSu root will go away after you reboot, however, to get root back, simply type adb shell (while connected to your computer of course) then su and then sh /sdcard/mrw/root.sh and just like that, you're rooted again. Note: I couldn't get this to work in a terminal emulator, and it would only work in adb shell for me.
Edit: If you want stock recovery back, run this command in adb shell with su dd of=recovery if=/sdcard/recovery.img. I haven't tested this, and it might unroot/brick your device. This is at your own risk.
This guide was long and complicated, sorry for that, if you need any help, just ask me and I will try to help the best I can.
If this guide helped, please clicks thanks, it means a lot to me
Proof: http://imgur.com/a/zecyU
Also: if any mods/admins read this, could you please make a forum for ZTE Maven 2? I would love to get this guide out more so more people can root their phone.
Ur guide is pretty much what I did I asked for a forum but never got one I have a guide for warp 7 very similar just not as much words wrote out however I didn't try to replace king root does it work without risk of brick to replace king oh SuperSU u have to keep enabling I guess. U can disable all the annoying stuff kingroot has
---------- Post added at 02:47 PM ---------- Previous post was at 02:41 PM ----------
Also u didn't list at the end once u have root u can reflash reg recovery back unless I mean the SuperSU part needs it still the same
madvane20 said:
Ur guide is pretty much what I did I asked for a forum but never got one I have a guide for warp 7 very similar just not as much words wrote out however I didn't try to replace king root does it work without risk of brick to replace king
Click to expand...
Click to collapse
Yup, your post for the warp 7 helped me a lot, I gave you credit in my post too.
You can replace KingRoot without any risk of brick, only problem is SuperSu is only temproot. To get root back after reboot you just have to run a quick command in adb shell, it's inconvenient, but I think it's much better than the alternative of having KingRoot.
Edit:
I haven't tried putting recovery back, so i'm not sure if that would work or not. I'll put that in the post though.
Ok I'll give a shot at making SuperSU perm once I get home not home for weekend
---------- Post added at 02:51 PM ---------- Previous post was at 02:50 PM ----------
I have a guide ready for the phone but never posted due to no forum for it lol
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
So since u have one posted already we can use that and if I get SuperSU to be perm then I will add to the guide.
madvane20 said:
Ok I'll give a shot at making SuperSU perm once I get home not home for weekend
---------- Post added at 02:51 PM ---------- Previous post was at 02:50 PM ----------
I have a guide ready for the phone but never posted due to no forum for it lol
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
So since u have one posted already we can use that and if I get SuperSU to be perm then I will add to the guide.
Click to expand...
Click to collapse
Yeah SuperSu perm would be nice, I think we just need to add a startup script or something? Also, I feel bad since I kinda stole your guide, I can delete my post if you want.

Alcatel Ideal 4060a bootloader and custom recovery

rooted alcatel ideal 4060a trying to find out if there is anyway to unlock bootloader and install custom recovery
Developer options
Sent from my Alcatel_4060A using XDA-Developers mobile app
r00t.l3gg3r said:
Developer options
Sent from my Alcatel_4060A using XDA-Developers mobile app
Click to expand...
Click to collapse
i am aware of allow oem unlock, this does not however help me in the process of unlocking and installing custom recovery.
TWRP doesn't appear to be available for the 4060A Ideal yet, if anyone notices they made one in the future please post in this thread.
Did you try the very latest version of KingRoot from Nov 23, 2016: http://forum.xda-developers.com/devdb/project/dl/?id=21707
Please post if you did and if it worked.
EDIT: Yes. KingRoot5 does work but DO NOT USE King-O-Root. King-O-Root will permanently BRICK this phone. But KingRoot5 works.
EDIT2: See this post
I rooted this phone yesterday with the latest KingRoot. I I installed my backup from an LG K7 which I had fully rooted by using an older version of Super su me. Unfortunately I lost that phone. I found this phone on closeout at Kmart and Im trying to get something going on it. It's strange that busybox will install with the new version of KingRoot still installed. Everytime I run super su me (I have tried several different versions) it either crashes or just doesn't do anything. I'm working on it now. Any of you funny guys been able to remove KingRoot and keep root.
Screenshot from this phone. I once rooted an elevate and it came back as a pixi.
The reason why your post is important is people don't want to run KingRoot and find out the hard way it doesn't work, so thanks for posting that.
Yes, removing KingRoot and keeping root would be the golden grail, I'll post here as soon as I come across anyone who's done that. I can't find anyone yet with TWRP or FlashFire-equivalent, let alone root with KingRoot removed...
I read on another thread for this device that they successfully did it with the PC version of KingRoot. I'm leary about putting it on my laptop. I'm hard on phone's and have been messing with them for about a year now so far I haven't bricked a device. I've unlocked a couple of bootloader's. Seems I have the best luck with metro/lg. But I like a challenge and couldn't pass up this phone for the price. First time I got an at&t phone to achieve any kind of root.
I rooted this phone using kingroot then used this post http://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989 to switch out kingroot for SuperSU. But you should read the comments in the thread as well for helpful hints, I used link2sd to fully remove kingroot after the script finished.
Bottom line is root and supersu can be achieved fairly easily.
I will give it a try. Ty
arolust said:
I rooted this phone using kingroot then used this post http://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989 to switch out kingroot for SuperSU. But you should read the comments in the thread as well for helpful hints, I used link2sd to fully remove kingroot after the script finished.
Bottom line is root and supersu can be achieved fairly easily.
Click to expand...
Click to collapse
Did you remove KingRoot 5?
Would you please post how exactly you removed KingRoot on Alcatel Ideal 4060a..
Thank you.
Dingolo said:
I will give it a try. Ty
Click to expand...
Click to collapse
Did it work for you? I don't see Alcatel mentioned in that thread. I'm curious.
He says it worked for him using link2sd. The original method without link2sd used in the linked thread does not work on Alcatel Ideal 4060a, I tried it.
But his method of using link2sd may work - he says it does.
But how do you exactly do that method? What lines of code do you use, what exactly is the process with link2sd?
That's what we are after, how do you use link2sd with Alcatel Ideal 4060a. I hope he comes back and posts. Otherwise one of us will hopefully figure it out eventually on here...
arolust said:
I rooted this phone using kingroot then used this post http://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989 to switch out kingroot for SuperSU. But you should read the comments in the thread as well for helpful hints, I used link2sd to fully remove kingroot after the script finished.
Bottom line is root and supersu can be achieved fairly easily.
Click to expand...
Click to collapse
In the post I linked theres a person who (on the first page) added a code to the script for link2sd.
However, im a bit to lazy to do the research into editing the script, so I think I just ran the script then used link2sd to remove kingroot, then reboot.
Though I had to do this while enduring a constant popup requiring me to press ok over and over.
To be honest though Im a bit fuzzy on the full process because I to had trouble getting the script to work. I might have run the script then rebooted then tried removing kingroot.
I will do this then post full instructions.
I actually know exactly what you are talking about.
But what exactly did you do inside link2sd, can you just post that?
c627627 said:
I will do this then post full instructions.
I actually know exactly what you are talking about.
But what exactly did you do inside link2sd, can you just post that?
Click to expand...
Click to collapse
Thank you for your leadership/initiative :good:
Heyyyyyy, picked up this phone on black friday for $10, well 2 of them. Cant find the device thread tho....im sure its just that im blind...anyone link me up? AND this is the first ATT phone I have read that root can be achieved, I mean by running kingo root, Gonna try it as soon as I find some time...
forgottenhacker said:
Heyyyyyy, picked up this phone on black friday for $10, well 2 of them. Cant find the device thread tho....im sure its just that im blind...anyone link me up? AND this is the first ATT phone I have read that root can be achieved, I mean by running kingo root, Gonna try it as soon as I find some time...
Click to expand...
Click to collapse
Low-end phones don't have their own sections in xda. I doubt there is one for this phone.
goldentequila said:
Low-end phones don't have their own sections in xda. I doubt there is one for this phone.
Click to expand...
Click to collapse
Right, I have attempted to use Kingo root and I was able to remove att crap but I can't grant any other su permissions as I don't get that pop-up box with allow root permissions. I'm not sure how Kingo works but I'm pretty sure there should be some way to grant permissions.
forgottenhacker said:
Right, I have attempted to use Kingo root and I was able to remove att crap but I can't grant any other su permissions as I don't get that pop-up box with allow root permissions. I'm not sure how Kingo works but I'm pretty sure there should be some way to grant permissions.
Click to expand...
Click to collapse
We should wait for c627627 to post an instruction. He was going to try it and report back.

Unlocking bootloader with HDX Nexus ROM

Howdy,
I bought a refurbished HDX 7" (thor) off Amazon, it came with HDX Nexus ROM (v4.0.5 @ ggow), Android 4.4.4 already installed. It has a few hick-ups (like the updated Play Store always stops, and some apps, like Dialer, will startup themselves), anyways I'd like to switch to CM or at least get a fresh install of Nexus. Rooting was easy with KingRoot, the bootloader is locked and all attempts to unlock have failed (Unlock code is not correct).
From what I understand, I can't install TWRP without unlocking the bootloader and I can't install SafeStrap since I don't have FireOS installed.
Any ideas?
Thanks a bunch.
yoyohoho said:
Howdy,
I bought a refurbished HDX 7" (thor) off Amazon, it came with HDX Nexus ROM (v4.0.5 @ ggow), Android 4.4.4 already installed. It has a few hick-ups (like the updated Play Store always stops, and some apps, like Dialer, will startup themselves), anyways I'd like to switch to CM or at least get a fresh install of Nexus. Rooting was easy with KingRoot, the bootloader is locked and all attempts to unlock have failed (Unlock code is not correct).
From what I understand, I can't install TWRP without unlocking the bootloader and I can't install SafeStrap since I don't have FireOS installed.
Any ideas?
Thanks a bunch.
Click to expand...
Click to collapse
HDX Nexus 4.0.5 was likely rooted. Regardless, it's an older/discontinued build that should be updated.
You can install TWRP on any rooted 3rd gen HDX by following step #2 (only) in the OP in this thread; steps #1 and #3 pertain to unlocking the bootloader.
Please note that while the above procedure has been sucessfully executed by dozens of HDX owners there is risk involved that could easily lead to a bricked device. Basically if anything goes wrong the device is toast.
Once TWRP is available you can flash the HDX builds of CM 11 or Fire Nexus HDX (successor to v4.0.5). Be sure to follow the flashing instructions in the relevant ROM thread OP. You will need to unlock the bootloader to install any other custom ROM.
Unlocking bootloader
Thank you, thank you, your simple instructions worked liked a charm. Only took about 10 minutes to complete, yet I spent 4 hours searching forums for an answer....ackkk.
Anyhow, at some point I'd like to upgrade to CM12 since there are a couple apps that require Android 5.1 or later. So I need to get my bootloader unlocked. I followed the posting by ONYXis, but it kept saying that unlock code is incorrect. My question is: Would the procedure work if I installed FireOS (maybe 4.5.2)? Or am I missing some other step?
Thank you, thank you again
yoyohoho said:
Thank you, thank you, your simple instructions worked liked a charm. Only took about 10 minutes to complete, yet I spent 4 hours searching forums for an answer....ackkk.
Anyhow, at some point I'd like to upgrade to CM12 since there are a couple apps that require Android 5.1 or later. So I need to get my bootloader unlocked. I followed the posting by ONYXis, but it kept saying that unlock code is incorrect. My question is: Would the procedure work if I installed FireOS (maybe 4.5.2)? Or am I missing some other step?
Thank you, thank you again
Click to expand...
Click to collapse
Unlock code and application procedure works on any rooted 3rd gen HDX with a vulnerable bootloader regardless of installed ROM, recovery, etc. Most likely you have a typo in one of the input values or the concatenated string fed to the code generator is not in the proper format. Look carefully at required format in the OP along with your manfid and serial to insure everything is to spec.
If still no joy post your manfid and serial in the other thread (referencing this discussion) and request someone generate an unlock code on your behalf. I am travelling this weekend with no access to my Windows box until Monday.
Be aware unlocking poses no risk to your device; it will either work or not. Also try a different USB port and/or cable. I know it sounds far fetched but amazing how many times that "fixes" fastboot weirdness.
Solved
Davey126 said:
Unlock code and application procedure works on any rooted 3rd gen HDX with a vulnerable bootloader regardless of installed ROM, recovery, etc. Most likely you have a typo in one of the input values or the concatenated string fed to the code generator is not in the proper format. Look carefully at required format in the OP along with your manfid and serial to insure everything is to spec.
If still no joy post your manfid and serial in the other thread (referencing this discussion) and request someone generate an unlock code on your behalf. I am travelling this weekend with no access to my Windows box until Monday.
Be aware unlocking poses no risk to your device; it will either work or not. Also try a different USB port and/or cable. I know it sounds far fetched but amazing how many times that "fixes" fastboot weirdness.
Click to expand...
Click to collapse
Many, many thanks to you, Davey126, for your encouragement and patience with my noobness.
I knew my unlock file was OK since I verified with OpenSSL... cable, ports and drivers were OK too.
The solution for ME was to switch over to a WinXP box from a Win10 box, and it worked flawlessly. I admit though that I still use XP as my main system so I'm very familiar with it, however, when I started this endeavor things like Android SDK needed a 64-bit box.
Anyways, thanks again for your support and score one for WinXP
yoyohoho said:
Many, many thanks to you, Davey126, for your encouragement and patience with my noobness.
I knew my unlock file was OK since I verified with OpenSSL... cable, ports and drivers were OK too.
The solution for ME was to switch over to a WinXP box from a Win10 box, and it worked flawlessly. I admit though that I still use XP as my main system so I'm very familiar with it, however, when I started this endeavor things like Android SDK needed a 64-bit box.
Anyways, thanks again for your support and score one for WinXP
Click to expand...
Click to collapse
Glad you got everything working! Sometimes good old XP still shines bright.
I too have got the same device as yours with the same HDX nexus ROM installed which has glitches like you mentioned (automatic startup of apps etc), managed to root it and managed to install twrp but just can't make fastboot execute unlock probably windows fastboot driver issues. I am working on it, may be i will try with win xp on a virtual machine. By the way, i wanted to know which ROM did you try and which one did you find to be working well with this device with buttery smooth experience and no glitches and that all those glitches were settled after bootloader unlock and flashing of a ROM? kindly do suggest some ROM and if possible the drivers that you used to unlock or any other details necessary. thanks
Same here, but i can't to root my device
I tried kingroot and towelroot, but didn't works
ybridos said:
Same here, but i can't to root my device
I tried kingroot and towelroot, but didn't works
Click to expand...
Click to collapse
same here, refubrished device from ebay, Nexus Rom, stock recovery, and unable to root it, kinroot didn't work :crying:
---------- Post added at 10:43 AM ---------- Previous post was at 10:11 AM ----------
Hey, im just rooted it! All what needed were Factory reset and mobile Kingroot. Hope this will work for other preople!
xob0t said:
same here, refubrished device from ebay, Nexus Rom, stock recovery, and unable to root it, kinroot didn't work :crying:
---------- Post added at 10:43 AM ---------- Previous post was at 10:11 AM ----------
Hey, im just rooted it! All what needed were Factory reset and mobile Kingroot. Hope this will work for other preople!
Click to expand...
Click to collapse
I have tried with Kingoroot and it is worked on first try. May be helpful to you, good luck
I have same device with #Davey126
I wanna install TWRP and then root my KF,
so, Is this step below is good for me?
2. Flash old vulnarable aboot and cubed twrp (just in case). Check that all these commands executed without errors. If you'll get one - read second post below. If your firmware <=13(14)3.2.3.2 skip this step.
Download aboot and twrp for Thor (Kindle Fire HDX 7) https://drive.google.com/open?id=0B2...GxXMUZPZTlZTUk or for Apollo (Kindle Fire HDX 8.9) - https://drive.google.com/open?id=0B2...zJDQkczNzRLaHM - and put this two files (twrp_cubed.img and aboot_vuln.mbn) into root of your kindle internal storage.
Run:
Code:
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Now you have working twrp recovery. It already works even without unlocked bootloader. You could boot into it by holding volUP during grey kindle logo. But no need to flash anything until unlock. At this point this is just emergency tool if something goes wrong =)
Click to expand...
Click to collapse
Quoted from https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
yoyohoho said:
Howdy,
I bought a refurbished HDX 7" (thor) off Amazon, it came with HDX Nexus ROM (v4.0.5 @ ggow), Android 4.4.4 already installed. It has a few hick-ups (like the updated Play Store always stops, and some apps, like Dialer, will startup themselves), anyways I'd like to switch to CM or at least get a fresh install of Nexus. Rooting was easy with KingRoot, the bootloader is locked and all attempts to unlock have failed (Unlock code is not correct).
From what I understand, I can't install TWRP without unlocking the bootloader and I can't install SafeStrap since I don't have FireOS installed.
Any ideas?
Thanks a bunch.
Click to expand...
Click to collapse
Can anyone help me unlock bootloader?
my KF HDX 7 ís same #yoyohoho with 4.4.4 installed.
I searched few days, but cant find exactly way, because my english is so bad
Hey yoyohoho, can u help me?
Mark2014 said:
Can anyone help me unlock bootloader?
my KF HDX 7
Click to expand...
Click to collapse
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Davey126 said:
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
I read it before but not sure. tks
Davey126 said:
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
i'm follow your link but stucked after go into [fastboot]
image attached below.
{
"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"
}
KF screen alway show Ready without step:
5. On the Computer go to Device-Manager and change driver in "Other Android" to "Fire Devices - Android Adb Composite Driver" . It should say "Ready" on the Kindle.
it shows "waiting for device" and I wait a half of hour but nothing happen.
Iam using win7 64b, and usb driver already installed.
What should I do next?
hi there, i have similiar situation, yet a little bit different. from Fire OS (don't remember version number) i went to this ROM: https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931 and i have Bootstrap on my device. it means, that my BL is locked. may i use this steps https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006 to unlock BL?
miguelm75 said:
hi there, i have similiar situation, yet a little bit different. from Fire OS (don't remember version number) i went to this ROM: https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931 and i have Bootstrap on my device. it means, that my BL is locked. may i use this steps https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006 to unlock BL?
Click to expand...
Click to collapse
Yes. Linked procedure does not care how the device is currently configured.
Davey126 said:
Yes. Linked procedure does not care how the device is currently configured.
Click to expand...
Click to collapse
thanks. i have one problem - where should I look for drivers to change drivers to "Fire Devices - Android Adb Composite Driver"? because when i try to change to drivers installed to c:\Program Files (x86)\Amazon.com\Fire_Devices\, system says "I cannot install Android device".
my operation system is Windows 10
miguelm75 said:
thanks. i have one problem - where should I look for drivers to change drivers to "Fire Devices - Android Adb Composite Driver"? because when i try to change to drivers installed to c:\Program Files (x86)\Amazon.com\Fire_Devices\, system says "I cannot install Android device".
my operation system is Windows 10
Click to expand...
Click to collapse
Install the Motorola Device Manager (here) which contains compatible drivers for HDX devices that work on a wide variety of platforms. You don't need to run the manager, just install it. One click goodness that actually does something userful.
Davey126 said:
Install the Motorola Device Manager (here) which contains compatible drivers for HDX devices that work on a wide variety of platforms. You don't need to run the manager, just install it. One click goodness that actually does something userful.
Click to expand...
Click to collapse
still no luck
this is strange - when Kindle is powered on, is visible in "Device Manager" as "Android Adb Composite Driver", but when i reboot it to BL, it's "Other devices"/"Android" and it cannot be changed
and i installed Motorola drivers. should i restart system?

Categories

Resources