Database Users

[HOW TO] Install a ROM with TWRP after a SDCard wipe

Today I decided to unleash my kfhd7 and install CyanogenMod.
After installing the 2nd Bootloader and the recovery, I 'accidentally' removed all my data in the hurry (anyway, I forgot to place the ROM on the SDCard folder before :silly. I was quite confident while doing this, based on my experience with other Android devices, I thought it would be easy to mount the SDCard folder to the computer using TWRP... But that wasn't the case. And my device was not recognize by ADB while in Recovery Mod.
After some research on the forum I noticed that the poor people who had this problem before had to reflash the stock image through the recovery. I used another method, mostly by finding a way to reinstall the drivers. So I decided to share my experience. I know that is maybe a bit noob, but I would enjoyed to find this tutorial while I was despaired and stuck on recovery mod.
Last precision : I am using Windows 8 (and I'm French, so pardon my French ).
What you need
ADB version 1.0.29 or higher you can find the version by typing "adb version" at the command terminal
Kindle Fire HD ADB drivers already installed, I guess it was the case if you were able to install the recovery. Other wise try to install it, you should find the the file executable easily on this forum.
The .zip file of whatever you want to flash, dont forget the gapps if you want to flash Cyanogen
That's all, no need of factory cable.
1. Install drivers
The first step is to reinstall the driver, considering the device was recognised before the flash but not anymore.
Open the Device Manager (hint: by typing directly devmgmt.msc)
You should see "Amazon Kindle Fire HD" under the "Other Devices"
Right click "update driver"
"Browse my computer for driver software"
"Let me pick from a list of device drivers on my computer"
"All devices" then next
At the bottom of the window you can choose a custom driver. Go this path:
C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_048d6e54936abbc3
The last number might be different (or may not, in fact I have no idea).
And voilà!!
Now adb should work.
2. Use sideload
You can now push your .zip to the sdcard, but TWRP have a really useful and smart way to do it.
Go into the advanced option of ADB. The click ADB sideload and swipe to start.
Just type
Code:
adb sideload yourfile.zip
and it's done! Don't forget to repeat it for googleapps if you need it.
For some reasons I had an error from TWRP complaining that he didn't find any OS installed. It worked anyway for me.

Just wanted to say merci bc.
Running the stock rom (rooted + 2nd boot-loader) I´ve flashed the "1.4 GHz(try me first)" by Maromi.
I made a backup before of everything but unfortunately moved. the files to my PC.
With the result of stucking at the blue Kindle logo.
A fastboot cable has been ordered but didn´t arrived in time before the week-end.
Just like you I´ve looked around quite a long time, tried several options but then your thread was the only solution!
By your advice I´ve sideloaded the last 7.3.1 (provided by hashcode) flashed and voilà - my kindle´s back!!
thx again!

Mistaz said:
Just wanted to say merci bc.
Running the stock rom (rooted + 2nd boot-loader) I´ve flashed the "1.4 GHz(try me first)" by Maromi.
I made a backup before of everything but unfortunately moved. the files to my PC.
With the result of stucking at the blue Kindle logo.
A fastboot cable has been ordered but didn´t arrived in time before the week-end.
Just like you I´ve looked around quite a long time, tried several options but then your thread was the only solution!
By your advice I´ve sideloaded the last 7.3.1 (provided by hashcode) flashed and voilà - my kindle´s back!!
thx again!
Click to expand...
Click to collapse
I'm glad that it was useful to you
I was affraid that I was the only one "enthusiastic" enough to do the mistake. :laugh:

gornog said:
Today I decided to unleash my kfhd7 and install CyanogenMod.
After installing the 2nd Bootloader and the recovery, I 'accidentally' removed all my data in the hurry (anyway, I forgot to place the ROM on the SDCard folder before :silly. I was quite confident while doing this, based on my experience with other Android devices, I thought it would be easy to mount the SDCard folder to the computer using TWRP... But that wasn't the case. And my device was not recognize by ADB while in Recovery Mod.
After some research on the forum I noticed that the poor people who had this problem before had to reflash the stock image through the recovery. I used another method, mostly by finding a way to reinstall the drivers. So I decided to share my experience. I know that is maybe a bit noob, but I would enjoyed to find this tutorial while I was despaired and stuck on recovery mod.
Last precision : I am using Windows 8 (and I'm French, so pardon my French ).
What you need
ADB version 1.0.29 or higher you can find the version by typing "adb version" at the command terminal
Kindle Fire HD ADB drivers already installed, I guess it was the case if you were able to install the recovery
The .zip file of whatever you want to flash, dont forget the gapps if you want to flash Cyanogen
That's all, no need of factory cable.
1. Install drivers
The first step is to reinstall the driver, either the device was recognised before the flash.
Open the Device Manager (by typing directly devmgmt.msc)
You should see "Amazon Kindle Fire HD" under the "Other Devices"
Right click "update driver"
"Let me pick driver on my computer"
"choose in a list..."
"All devices" then next
At the bottom of the window you can choose a custom driver. Go this path:
C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_048d6e54936abbc3
The last number might be different (or may not, in fact I have no idea).
And voilà!!
Now adb should work.
2. Use sideload
You can now push your .zip to the sdcard, but TWRP have a really useful and smart way to do it.
Go into the advanced option of ADB. The click ADB sideload and swipe to start.
Just type
Code:
adb sideload yourfile.zip
and it's done! Don't forget to repeat it for googleapps.
For some reason I had an error from TWRP complaining that he didn't find any OS installed. It worked anyway for me.
Click to expand...
Click to collapse
After following your steps I will get to the part where i have to click the last file for the drivers and after I do my computer will say that Windows was unable to find the drivers for the KFHD7, if you have any suggestions on what to do that would be greatly appreciated.

th3lawmak3r76 said:
After following your steps I will get to the part where i have to click the last file for the drivers and after I do my computer will say that Windows was unable to find the drivers for the KFHD7, if you have any suggestions on what to do that would be greatly appreciated.
Click to expand...
Click to collapse
Did ADB worked properly before, with drivers installed? If so you can try something else to reinstall it.
The first step are the same,
Right click "update driver"
"Browse my computer for driver software"
"Let me pick driver on my computer"
And try to find in the list if there is a "Kindle Fire" in the list of devices. You might be able to install it from here.
Otherwise try to reinstall the amazon adb driver (you can find it easily in this forum), and then eventually perform again the operation above.

Update software driver of Windows7 32 bit path :
C:\Windows\system32\driver\ android_winusb.inf

I've tried all your steps and plenty more all over this forum.. I can't figure out why my Kindle HD 8.9 wont connect properly so I could push the rom via ADB.. I basically fell through the same issue as you.. except I'm stuck at trying to get Windows to recognize the Kindle properly... This is what I get regardless of what driver, or .inf I push at it.
{
"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"
}
/10postprereq
EDIT: I got it working, thank you very much for your post.. Helped a lot

gornog said:
2. Use sideload
You can now push your .zip to the sdcard, but TWRP have a really useful and smart way to do it.
Go into the advanced option of ADB. The click ADB sideload and swipe to start.
Just type
Code:
adb sideload yourfile.zip
and it's done! Don't forget to repeat it for googleapps if you need it.
For some reasons I had an error from TWRP complaining that he didn't find any OS installed. It worked anyway for me.
Click to expand...
Click to collapse
For some reason I cannot get this to work. I must not be typing the command language properly.
adb sideload cm-10.1xxxx
I get the following message:cannot read "sideload"
Any thoughts here? Thanks!!

krakora said:
For some reason I cannot get this to work. I must not be typing the command language properly.
adb sideload cm-10.1xxxx
I get the following message:cannot read "sideload"
Any thoughts here? Thanks!!
Click to expand...
Click to collapse
Make sure the ROM or file you're sideloading is in the same directory from which you are sending the command, or replace the filename with the exact full path to the file.

Success
soupmagnet said:
Make sure the ROM or file you're sideloading is in the same directory from which you are sending the command, or replace the filename with the exact full path to the file.
Click to expand...
Click to collapse
Thanks soupmagnet. Yes and Yes.
First: I did not have the Android SDK tools set up properly. I watched the interwebs and took some time to learn the very basic ADB commands. Once I changed directories to the desktop (where my zips were sitting) the simple sideload was a snap. I did get "error closed" message a couple times and used "adb usb" seemed to restart the process. At the end of day, success, my Kindle is flipping awesome now, I know a bit more about pushing files using ADB, and all is good in the world.
Thanks again XDA Developers!
PS: As a side note... I was on 7.4.3 version of the Amazon software and when I installed TWRP and the bootloader. Flash fire makes you switch to 7.2.3 version of the bootloader. I think that is what hosed me in the process... I could only get to recovery and it was like the OS was gone afterwards. Anyways, if you get trapped in recovery, get ready to learn something. :good:

I'm having trouble getting ADB to recognize the sideload command. I have found 2 different places that it is installed on my computer.
Do I use the ADB in the Android SDK, or the one in the Kindle Fire First Aide folder? When I try to open the one in the Android SDK folder the CMD Prompt pops up and flashes loads of text before auto closing, I get the same thing from the KF First Aide folder.
I just need to get my rom.zip onto my Kindle Fire HD, but I am totally lost on where to go from here since I am stuck on either the Boot screen or the TWRP bootloader.
Any help you can offer would be greatly appreciated.

ButchTheKitty said:
I'm having trouble getting ADB to recognize the sideload command. I have found 2 different places that it is installed on my computer.
Do I use the ADB in the Android SDK, or the one in the Kindle Fire First Aide folder? When I try to open the one in the Android SDK folder the CMD Prompt pops up and flashes loads of text before auto closing, I get the same thing from the KF First Aide folder.
I just need to get my rom.zip onto my Kindle Fire HD, but I am totally lost on where to go from here since I am stuck on either the Boot screen or the TWRP bootloader.
Any help you can offer would be greatly appreciated.
Click to expand...
Click to collapse
You don't run ADB like a standalone program. It's just a series of commands to be used from the command line. In order for this to work, the adb executable/binary/whatever must be in the same directory from which you are entering the commands (research the 'cd' command for more details).
Also, for the "sideload" command to work, your device must be booted into TWRP and you have to execute the sideload function from the "Advanced" menu.

soupmagnet said:
You don't run ADB like a standalone program. It's just a series of commands to be used from the command line. In order for this to work, the adb executable/binary/whatever must be in the same directory from which you are entering the commands (research the 'cd' command for more details).
Also, for the "sideload" command to work, your device must be booted into TWRP and you have to execute the sideload function from the "Advanced" menu.
Click to expand...
Click to collapse
Thanks for the quick reply, I decided to just re-flash to the stock 8.1.4 and restart the process, only this time I made sure to put the .zip folder for the new Rom on the systems storage first. Seems to be working so far, CyanogenMod is installing as I type this.
Thanks so much for working on this though, you guys do amazing work.

Dam thank you man
man with out this tread i would be F in a major way i have suceded in bricking two kindle fires hd 7 in the last week
one is compleatly dead dead dead waiting on factory cable. the other i was able to rescue today because of your post
(op) post,
i am not new to ADB, but the kffa, twrp,and other programs used to do these projects never seem to work, for me always stop at a bad time
. The thread installing twrp-2nd bootloader on this site has major flaws i am new to this so i chose 1st timer treads
(thing for dummies) things like step by step instructions, like i was able to follow your instructions easily (although you should have used an address like C;/desktop/xxxx.zip insted of (your zipfile) in the sideload code example. after i figerd out that deal it was easly done 5 min later loaded the code into adb ADB sideload C;/desktop/kfhd7-amizon-os-7.4.3.zip and 5 min after that my kindle rebooted and was back to normal all files intact even my apps. like i never touch a thing. it upgraded back to 7.4.6 and reloaded my apps.
I followed the instructions to a tee 2 times on the "root and recovery w/TWRP" tread and both times wound up having the programs kffa, and twrp, flashfile. stop at some point during the process, and result in me bricking.
i could have missed something or maybe the step by step missed a step or maybe my jdk was f but both time
i was screwed.
I think maybe they don't see the reader as a novice, although most if not all readers here are a novice's of some kind and so leave out info needed to complete with success, the tread i mention earlier he steered away from the topic so many times it made it almost impossible to follow and only refereed to successful outcomes, like put this into the cmd line next do this. but not stopping to think what if the person reading didnt get that response from the command line what do i do then?
And thats just what happen to me both times everything was going great and he said put this adb code in and i couldn't get it to respond like he said or it stoped cant find device or just sit there and do nothing, screwed... im into it now cant back up cant go forward your screwed. anyway my rant over now. THANKS FOR MAKING THIS TREAD you saved my ass.

thelz said:
man with out this tread i would be F in a major way i have suceded in bricking two kindle fires hd 7 in the last week
one is compleatly dead dead dead waiting on factory cable. the other i was able to rescue today because of your post
(op) post,
i am not new to ADB, but the kffa, twrp,and other programs used to do these projects never seem to work, for me always stop at a bad time
. The thread installing twrp-2nd bootloader on this site has major flaws i am new to this so i chose 1st timer treads
(thing for dummies) things like step by step instructions, like i was able to follow your instructions easily (although you should have used an address like C;/desktop/xxxx.zip insted of (your zipfile) in the sideload code example. after i figerd out that deal it was easly done 5 min later loaded the code into adb ADB sideload C;/desktop/kfhd7-amizon-os-7.4.3.zip and 5 min after that my kindle rebooted and was back to normal all files intact even my apps. like i never touch a thing. it upgraded back to 7.4.6 and reloaded my apps.
I followed the instructions to a tee 2 times on the "root and recovery w/TWRP" tread and both times wound up having the programs kffa, and twrp, flashfile. stop at some point during the process, and result in me bricking.
i could have missed something or maybe the step by step missed a step or maybe my jdk was f but both time
i was screwed.
I think maybe they don't see the reader as a novice, although most if not all readers here are a novice's of some kind and so leave out info needed to complete with success, the tread i mention earlier he steered away from the topic so many times it made it almost impossible to follow and only refereed to successful outcomes, like put this into the cmd line next do this. but not stopping to think what if the person reading didnt get that response from the command line what do i do then?
And thats just what happen to me both times everything was going great and he said put this adb code in and i couldn't get it to respond like he said or it stoped cant find device or just sit there and do nothing, screwed... im into it now cant back up cant go forward your screwed. anyway my rant over now. THANKS FOR MAKING THIS TREAD you saved my ass.
Click to expand...
Click to collapse
Which thread did you use to install TWRP?
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS<<

Adb sideload not working
Hi guys, i need your help please! I am at the twrp menu trying to open adb sideload and it says"starting adb sideload feature..." but it stays like that for ages. Any idea??

guidomagaldi said:
Hi guys, i need your help please! I am at the twrp menu trying to open adb sideload and it says"starting adb sideload feature..." but it stays like that for ages. Any idea??
Click to expand...
Click to collapse
Stunts has a nice write up on this exact thing here http://forum.xda-developers.com/showthread.php?t=2459498

LinearEquation said:
Stunts has a nice write up on this exact thing here http://forum.xda-developers.com/showthread.php?t=2459498
Click to expand...
Click to collapse
thanks! its working!

guidomagaldi said:
thanks! its working!
Click to expand...
Click to collapse
You're welcome. Stunts did the write up, I just laid it out for you to play out.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers

Help please
gornog said:
Today I decided to unleash my kfhd7 and install CyanogenMod.
After installing the 2nd Bootloader and the recovery, I 'accidentally' removed all my data in the hurry (anyway, I forgot to place the ROM on the SDCard folder before :silly. I was quite confident while doing this, based on my experience with other Android devices, I thought it would be easy to mount the SDCard folder to the computer using TWRP... But that wasn't the case. And my device was not recognize by ADB while in Recovery Mod.
After some research on the forum I noticed that the poor people who had this problem before had to reflash the stock image through the recovery. I used another method, mostly by finding a way to reinstall the drivers. So I decided to share my experience. I know that is maybe a bit noob, but I would enjoyed to find this tutorial while I was despaired and stuck on recovery mod.
Last precision : I am using Windows 8 (and I'm French, so pardon my French ).
What you need
ADB version 1.0.29 or higher you can find the version by typing "adb version" at the command terminal
Kindle Fire HD ADB drivers already installed, I guess it was the case if you were able to install the recovery. Other wise try to install it, you should find the the file executable easily on this forum.
The .zip file of whatever you want to flash, dont forget the gapps if you want to flash Cyanogen
That's all, no need of factory cable.
1. Install drivers
The first step is to reinstall the driver, considering the device was recognised before the flash but not anymore.
Open the Device Manager (hint: by typing directly devmgmt.msc)
You should see "Amazon Kindle Fire HD" under the "Other Devices"
Right click "update driver"
"Browse my computer for driver software"
"Let me pick from a list of device drivers on my computer"
"All devices" then next
At the bottom of the window you can choose a custom driver. Go this path:
C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_048d6e54936abbc3
The last number might be different (or may not, in fact I have no idea).
And voilà!!
Now adb should work.
2. Use sideload
You can now push your .zip to the sdcard, but TWRP have a really useful and smart way to do it.
Go into the advanced option of ADB. The click ADB sideload and swipe to start.
Just type
Code:
adb sideload yourfile.zip
and it's done! Don't forget to repeat it for googleapps if you need it.
For some reasons I had an error from TWRP complaining that he didn't find any OS installed. It worked anyway for me.
Click to expand...
Click to collapse
Hey please help me I have donwloaded amazon kindle fire but it doesn't displays in my device manager furthermore in my computer I cant find driver software but yes in program files i do have amazon kindle folder, what should I do please help

(Guided) LeTV LeEco Le 1 Pro (US Version) X800 TWRP Recovery, Root

The LeTV LeEco Le 1 Pro is an excellent phone that comes at a very low price. Some retailers are selling the phone for approx. £150. However, the phone does come with a few problems.
The phone comes bundled with an old YouTube app which refuses to update to the latest version. The phone has malware where apps are installed in the background and ads are served in the Chrome browser.
At the time of writing there was no official ROM available. Now a official ROM has been released. It can be found in this post. Installing the official ROM is the easiest way to fix the malware and app problems with the phone.
The TrustGo App from the Google Play store pointed out that the Ant Keyboard bundled app contained the malware. The YouTube problem can be fixed by uninstalling the bundled YouTube and installing the latest YouTube from the Google Play Store.
The phone had to be rooted to remove the YouTube and the malware app Ant Keyboard.
The following instructions will root the LeTV Le 1 Pro USA version only. However, rooting can brick your phone, so if you do go ahead it will be your responsiblity. Rooting also invalidates the warranty of the phone. You will also be able to unroot your phone at a later date and reinstate your warranty.
The following assumes that you are using Windows 10.
Rooting the LeTV Le 1 Pro USA Version
Install TWRP
TWRP will allow to root the phone. First it needs to be installed.
In order to install TWRP, you need to connect the phone to the PC
Lets prepare the PC before we connect it
Install Java JDK 8 using Chocolatey
Open an administrator command prompt
Type cmd in the search, right click Command Prompt and choose Run as administrator.
Copy and paste the following code into the administrative command prompt window to install chocolately
@powershell -NoProfile -ExecutionPolicy Bypass -Command "iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))" && SET PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin
Install and configure JDK 8 by pasting the following code into the administrative command prompt window.choco install jdk8
Download, install and configure android studio using the defaults in the setup
Download Android Studio
Launch setup and accept the defaults
In the final screen select lanuch Android Studio and then finish
Choose the configure dropdown and then choose SDK manager
{
"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"
}
In the SDK manager, check the Google USB Driver from the SDK Tools tab and choose OK
android sdk manager google usb driver
Close the administrative command prompt and then open a new administrative command prompt and type adb. You should see the adb command returning help. This means that adb driver is installed and ready to go.
Download the latest version of TWRP onto the PC using this link
Rename the downloaded file to recovery.img
Now it is time to prepare the phone before we connect it to our already prepared PC. If your phone does not boot into android then you can skip the whole of this #4 section and move on to #5 (TWRP) section below.
Go to settings and then about on your phone. Unlock developer options by touching the build number several times.
Android : Settings -> About
Go to settings, developer options and enable USB debugging
http://i0.wp.com/showtop.info/wp-content/uploads/2016/07/Screenshot_2016-07-11-14-22-04.jpg?resize=900%2C1600[IMG/]
Android enable USB debugging
In the notification bar click on touch for USB options and ensure that MTP is selected
[IMG]http://i1.wp.com/showtop.info/wp-content/uploads/2016/07/Screenshot_2016-07-11-15-16-45.jpg?resize=900%2C1600
Android USB Options
Connect the phone to the PC
In an administrative prompt check the phone is connected correctly by typing
adb devices
You should see a device under adb devices
Download SuperSU and use the file manager to put in the root directory of the phone
Lets flash TWRP into the phone. You should not lose any data, but if you have data on the phone you should make a backup just in case.
We need to boot into fastboot. On the PC, open an administrative command prompt and type
adb reboot bootloader
If your device does not boot into android, you can go into fastboot by switching off your phone, hold the down volume key and then press the power button.
Once in fastboot you should see a small picture of a penguin in the middle of the screen. To check that the phone is connected, in the administrative command prompt type
fastboot devices
You should see your device listed
In the administrative command prompt make sure you are in the directory of the recovery.img file and type the following
fastboot flash recovery recovery.img
Once the recovery is flashed type the following and hold the up volume key to restart in recovery
fastboot reboot
You should now be in TWRP. In TWRP there may be an option advanced or settings to install SuperSU. If the option is not there use install to install SuperSU (downloaded earlier) from the root of the phone storage.
Once installed you can reboot into android and following the instructions in the SuperSU app.
Once the installation is complete download the RootChecker app from the Google Play store and check if the device has been rooted.
Fixing the problems with YouTube and removing the malware
Install Easy Uninstaller, Stubborn Trojan Killer and Malwarebytes Anti-Virus from the Google Play Store.
Uninstall YouTube and Ant Keyboard. I uninstalled Cantonese Keyboard Language and Mii Browser as well as I was not using these. If you start getting errors, simply reboot your device.
Download and install the YouTube app from the Google Play Store.
Run the Stubborn Trojan Killer and remove any found trojans.
Run the Malwarebytes Anti-Virus and remove any found viruses. Run the privacy scanner and follow the recommendations.
Once you have successfully completed the above steps then your device should be malware free and completely usable.

Very nice job. Newbies friendly rooting guide. I think you must add another option in the poll : CM12.1 cooked by Betahydri. It's a fully functional ROM (only IR remote and DT2W don't work yet) for everyday use.

ctragas said:
Very nice job. Newbies friendly rooting guide. I think you must add another option in the poll : CM12.1 cooked by Betahydri. It's a fully functional ROM (only IR remote and DT2W don't work yet) for everyday use.
Click to expand...
Click to collapse
Thanks , for the feedback , you had a good idea but the system doesn't let me edit the post yet

Hello, can you please explain how I can confirm my phone is the international version. I bought it from AliExpress on China.
Please also provide the links to the TWRP and the Super SU. Thanks

Steveyknoxville said:
Hello, can you please explain how I can confirm my phone is the international version. I bought it from AliExpress on China.
Please also provide the links to the TWRP and the Super SU. Thanks
Click to expand...
Click to collapse
If you see CE0560 In the back of the phone, that means you have the international version.
For the TWRP, download Le1Pro_US_TWRP_3.0.2-0_CUOCO92.7z
For Root, download SuperSu-V2.76

Thank you very much. Mine does have that on the rear. This is my second le1 pro the first I hate bricked trying to root it and install recovery. So I have been scared to try this one without knowing which model it is. Do you know if there is a custom ROM or even better asop or CM room available for the international version.
Thanks for your help.
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
Thank you very much. Mine does have that on the rear. This is my second le1 pro the first I hate bricked trying to root it and install recovery. So I have been scared to try this one without knowing which model it is. Do you know if there is a custom ROM or even better asop or CM room available for the international version.
Thanks for your help.

Steveyknoxville said:
Thank you very much. Mine does have that on the rear. This is my second le1 pro the first I hate bricked trying to root it and install recovery. So I have been scared to try this one without knowing which model it is. Do you know if there is a custom ROM or even better asop or CM room available for the international version.
Thanks for your help.
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
Thank you very much. Mine does have that on the rear. This is my second le1 pro the first I hate bricked trying to root it and install recovery. So I have been scared to try this one without knowing which model it is. Do you know if there is a custom ROM or even better asop or CM room available for the international version.
Thanks for your help.
Click to expand...
Click to collapse
You can fix your first bricked phone from HERE.
To be honest, I have tried only two Roms
1- Clean Stock Rom, it's clean of all malwares and virus that came with the Chinese resellers Rom, its very stable, good battery life. only the double tape to wake up & color mod doesn't work, but easy to fix HERE, (IMPORTANT you need to have Stock recovery to flash the Clean Rom or to modify a file in the Zip archive of the Rom to work with TWRP).
2- CM12.1 ROM by BetaHydri, a great Rom very stable only Ir Blaster doesn't work for now. The best choice so far.
3- Other Roms CUOCO92 5.5.014S but I have never used it.

Thank you so much, worked a treat.
Now I have TWRP, CM and super su.
Thanks for all your efforts.

You should also try betahydri CM 12.1 I have it on my phone for about 3 months and runs great , no bugs , and the battery performance is the same.

Hi.
After brick I've rescued my letv le1 x800 Pro US and I flash Cuoco92 rom. I used this rom and it works very fine. XD XD

Maybe I am not looking well enough, but I did not see the TWRP link in your post.
Next to that I installed the Android Studio. But the SDK tabs in the SDK section are disabled with me. It also says that "Android SDK location should not contain whitespace, as this can cause problems with the NDK tool" as a warning. Could this be related to the fact that the tabs are disabled?

the only way to root this phone is by cuocco92 method, there is no other way

[ROOT][TOOL]AutoRoot

AutoRoot
MAJOR UPDATE AUTOROOT 1.1 WITH UI.!!
CHANGELOG
V 1.1 30/1/2017
1. Made an UI
2 .Now Download automatically TWRP and SuperSU
Instructions :
1.You MUST to have adb installed on your PC.
2.Connect your phone to your PC via USB cable.(type C to microUSB adapter costs~9.99).
3.Run AutoRoot
4.Click Download button. (This will download TWRP and SuperSU app)
5.Click Root button
Enjoy
PLEASE ASK ME IF YOU HAVE ANY TROUBLE.
DOWNLOAD
SCREENSHOTS
{
"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"
}

dimkyr said:
AutoRoot
I have developed this exe to help you to root your Nexus 5X.
Instructions :
1.You MUST to have adb installed on your PC.
2.Connect your phone to your PC via USB cable.(type C to microUSB adapter costs~9.99).
3.Run AutoRoot.exe.
4.Follow Instructions.
Enjoy
PLEASE ASK ME IF YOU HAVE ANY TROUBLE.
USEFULL LINKS
Twrp
SuperSU
ΤΗΕ VIRUS ALERT IS FAKE ! VIRUS TOTAL SCAN : https://www.virustotal.com/en/file/...9c40c8e11ca931c2cd1fa289/analysis/1484572253/
DOWNLOAD
Click to expand...
Click to collapse
Hi! Could you explain a little bit more about this tool. What does it do? Does it unlock bootloader? Does it flash TWRP? Does it root? How? Thanks!

CLPose said:
Hi! Could you explain a little bit more about this tool. What does it do? Does it unlock bootloader? Does it flash TWRP? Does it root? How? Thanks!
Click to expand...
Click to collapse
Hello, this tool unlock bootloader, install twrp and root your phone but you have to manually download twrp img and superSU zip.Now i am working to do this automatically.. I write it in batch and just using adb commands. Soon i will upload the code in github, it's a very easy code at all.
I am here to help everytime you want .

dimkyr said:
Hello, this tool unlock bootloader, install twrp and root your phone but you have to manually download twrp img and superSU zip.Now i am working to do this automatically.. I write it in batch and just using adb commands. Soon i will upload the code in github, it's a very easy code at all.
I am here to help everytime you want .
Click to expand...
Click to collapse
Why is this a thing? Why not just stick to the tried and true method of unlocking or use Nexus ToolKit?

v.0.0.0.1 ? What?

bradhoschar said:
Why is this a thing? Why not just stick to the tried and true method of unlocking or use Nexus ToolKit?
Click to expand...
Click to collapse
is it bad make your own tool?

dimkyr said:
is it bad make your own tool?
Click to expand...
Click to collapse
No, it isn't bad. But usually when someone makes a tool it has a high level of flexibility and the program is usually very dynamic. Yours is like 100% static. It's like written in stone what the program is going to execute so that makes this program not user-friendly at all. To be honest with you, it's a nice try. I mean it proves you know and know how to use various batch functionalities. But it's nothing to write home about. I'd suggest diving into something like Java or Python and let the user decide more options so eventually you have a dynamic, but very robust tool for people to use.
2¢

sprremix said:
No, it isn't bad. But usually when someone makes a tool it has a high level of flexibility and the program is usually very dynamic. Yours is like 100% static. It's like written in stone what the program is going to execute so that makes this program not user-friendly at all. To be honest with you, it's a nice try. I mean it proves you know and know how to use various batch functionalities. But it's nothing to write home about. I'd suggest diving into something like Java or Python and let the user decide more options so eventually you have a dynamic, but very robust tool for people to use.
2¢
Click to expand...
Click to collapse
Thank you for your advices! I am begginer with all this thing and i am looking to learn more and make more dynamic tools. I am searching but it's hard to find information about programming for smartphones. So i am looking for help but i don't know where to search.
[Sorry for my bad english]

very cool
thanks for your contribution, everybody started somewhere and there are tons of folks who want a quick no frills method of rooting phones of all makes, Ive done rooting for $ for folks who dont want to learn how for whatever reason and woulduse a tool like this to just get the job done quick & easy.
keep plugging away at it add as much functionality as you want, people just like to troll and down anybody on the 'net but would never have the balls to do it IRL.
Ive been around this forum since before android and have seen it grow, I wish people would be more appreciative and troll less, maybe this tool isnt for you, but it may be just what somebody else is looking for....
I know how to root and have done it many times, Im about to root a bullhead and im glad this tool is here, why do it by hand if somebody else automated it?
work smarter not harder.
bhang

bhang said:
thanks for your contribution, everybody started somewhere and there are tons of folks who want a quick no frills method of rooting phones of all makes, Ive done rooting for $ for folks who dont want to learn how for whatever reason and woulduse a tool like this to just get the job done quick & easy.
keep plugging away at it add as much functionality as you want, people just like to troll and down anybody on the 'net but would never have the balls to do it IRL.
Ive been around this forum since before android and have seen it grow, I wish people would be more appreciative and troll less, maybe this tool isnt for you, but it may be just what somebody else is looking for....
I know how to root and have done it many times, Im about to root a bullhead and im glad this tool is here, why do it by hand if somebody else automated it?
work smarter not harder.
bhang
Click to expand...
Click to collapse
Hi! Thanks for encouriging @dimkyr developing a easy-to-use and useful tool like this one. I think you're 100% right! :highfive: Did you try it yourself? OP, on how many devices did you test your tool? What about drivers for Windows? Could you add some screenshots? I'm trying to root my N5X (MM-MDA89E) and I just can't. I've successfully unlocked its bootloader with NRT, but NRT keeps failling when rooting (tried in my PC with Windows 10, in two other PC with W7, and other PC with Xubuntu) :crying:. I'd be glad to test this tool if it's 100% sure! I WANT ROOT! In case you don't notice, I'm a noob! But I can't afford bricking my new N5X. Thanks!

CLPose said:
Hi! Thanks for encouriging @dimkyr developing a easy-to-use and useful tool like this one. I think you're 100% right! :highfive: Did you try it yourself? OP, on how many devices did you test your tool? What about drivers for Windows? Could you add some screenshots? I'm trying to root my N5X (MM-MDA89E) and I just can't. I've successfully unlocked its bootloader with NRT, but NRT keeps failling when rooting (tried in my PC with Windows 10, in two other PC with W7, and other PC with Xubuntu) :crying:. I'd be glad to test this tool if it's 100% sure! I WANT ROOT! In case you don't notice, I'm a noob! But I can't afford bricking my new N5X. Thanks!
Click to expand...
Click to collapse
Thank you everybody !!
I tested this tool to my N5X and work perfectly. But it's weird that NRT failed..
It's always a chance to fail or brick.
I will post screenshot later in this day!
With regards

CLPose said:
Hi! Thanks for encouriging @dimkyr developing a easy-to-use and useful tool like this one. I think you're 100% right! :highfive: Did you try it yourself? OP, on how many devices did you test your tool? What about drivers for Windows? Could you add some screenshots? I'm trying to root my N5X (MM-MDA89E) and I just can't. I've successfully unlocked its bootloader with NRT, but NRT keeps failling when rooting (tried in my PC with Windows 10, in two other PC with W7, and other PC with Xubuntu) :crying:. I'd be glad to test this tool if it's 100% sure! I WANT ROOT! In case you don't notice, I'm a noob! But I can't afford bricking my new N5X. Thanks!
Click to expand...
Click to collapse
im on linux atm so no i havent tried it, if the toolkit isnt working just do it manually, follow a walk thru to the letter take your time, as long as u follow instructions for your build you will be fine(settings>about phone>build number.... mine is NBD90W which is 7.0 security patch level 0ct. 5,2016)
doing a root tutorial that matches your build will prevent most if not all of the hiccups that can come from incompatibilities in roms that are more complex than a noobie rooter needs to know.
bhang

Does it work on 7.1.1 (N4F26I)?
Thanks!

x987z said:
Does it work on 7.1.1 (N4F26I)?
Thanks!
Click to expand...
Click to collapse
Works on every edition of android

ZTE Maven 3

What's the likelihood of anything happening with the ZTE Maven 3? I understand it's pretty new but I literally can't even find any discussion on it.

I just picked the Maven 3 up today myself and I must admit I'm pleasantly surprised... It performs great considering it was only $30 brand new, and I love the fit & finish of it... Now just gotta try to be patient and hope for Lineage/ResRemix,TWRP,Root,Magisk,etc.... =)

It's apparently going to be $8 shipped from best buy on black friday. I think a lot of people will pick one up even if it were to be just an emergency phone.
{
"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"
}

Any news?
tge101 said:
What's the likelihood of anything happening with the ZTE Maven 3? I understand it's pretty new but I literally can't even find any discussion on it.
Click to expand...
Click to collapse
Have you found anyone thats rooted it?

Logos Ascetic said:
Have you found anyone thats rooted it?
Click to expand...
Click to collapse
No, I haven't found anything about it still. Hoping for at least roof, LOS would be a nice surprise.

I've found that QDLoader is activated in EDL mode (adb reboot edl; you will know you are in when the screen is off and nothing is happening) but I'm not sure how that's useful for us. fastboot and adb do not work in this mode. Volume down + Power button = FTM (field test mode) but I'm not sure what to do in that mode - you can use adb commands but you can't do anything special like mount system as r/w - no fastboot in this mode either. I also tried the ZTE Axon 7 tuliptool but that didn't detect anything (worth a try I guess). iRoot, srsroot, kingroot (pc & apk) don't root it in the FTM mode or regular OS. I've tried adb reboot disemmcwc thing to disable write protection but that didn't seem to do anything different. adb reboot bootloader only brings you to the regular OS. There is also a recovery, but that really only allows you to wipe data/cache and view logs, etc. (volume up + power).
There is an OEM Unlock option in the developer settings, but I still haven't found a way to get to use fastboot. Looking in the system, there are some debug scripts in the /system/bin folder, as well as busybox (toolbox & toybox included) which is interesting. The device is on 7.1.1 & security update "July 1, 2017" (any later exploits?). In "About", there is also a section called "Additional system updates" which seems to allow installing update packages from root directory on storage card?
I'm stuck there, as I'm not super knowledgeable in the art of rooting. Hopefully someone can figure this out!

Thanks for the information, Nick. I'm sure a lot of people got these for 8 bucks like I did just to play around with. I have no intention of putting a sim in it. I just want to use it as a music player with Google music. The main things I want to do are get rid of the preinstalled "locked" apps and unlock it to get rid of the activation nags. How did you get the developer options? When I tap on the Android build, I get this big N. For just over $20, I got a music player with 32 gigs for music. Not bad. I would love to get Aptx HD if we are able to get LineageOS or root it and install the codec but it's not a really big deal since I have it on my main phone. I just want to use this at work plugged in.

Tim Elliott said:
Thanks for the information, Nick. I'm sure a lot of people got these for 8 bucks like I did just to play around with. I have no intention of putting a sim in it. I just want to use it as a music player with Google music. The main things I want to do are get rid of the preinstalled "locked" apps and unlock it to get rid of the activation nags. How did you get the developer options? When I tap on the Android build, I get this big N. For just over $20, I got a music player with 32 gigs for music. Not bad. I would love to get Aptx HD if we are able to get LineageOS or root it and install the codec but it's not a really big deal since I have it on my main phone. I just want to use this at work plugged in.
Click to expand...
Click to collapse
Tap the build number 7 times. It worked for me.

Maven query
First, am I permitted to ask a technical question about this model here? I couldn't find a thread for any sort of Q&A, and starting my own would likely take a week to get a response. If not, kindly point me in the right direction please?
Note: My question is about how to retrieve the encryption key as I adopted my SD card to internal, and now it won't read it suddenly. I believe a file named (expand%s.key) is what contained the key, and I'm not sure how it was deleted. This happened after using Zarchiver and compressing about 700 images into a .zip with ultra compression, 256-bit encryption with password. After it finished the phone rebooted and didn't read the SD card upon boot.

I'm working on a terminal-only approach to rooting using the linux shell. I've got 4 books on linux checked out from the library including a command reference that's about 800 pages thick. If there's a way to root using the command line, I'll find it. Success could take a week or two depending on how many hours a day I put into this. It's also possible that there simply isn't a way to root from the command line only. Wouldn't it be nice though?

Maven root
denny777 said:
I'm working on a terminal-only approach to rooting using the linux shell. I've got 4 books on linux checked out from the library including a command reference that's about 800 pages thick. If there's a way to root using the command line, I'll find it. Success could take a week or two depending on how many hours a day I put into this. It's also possible that there simply isn't a way to root from the command line only. Wouldn't it be nice though?
Click to expand...
Click to collapse
It'd be nice if there were ANY way to root the Maven 2 or 3, I've tried pretty much every well know apk , without PC, & no root. Almost got it 1 time & started to try to remove some crapware & bam reboot.
I'm confused on the custom recovery / root thing. Seems like a chicken / egg ? Need root to install recovery but the root methods on Youtube all seem to start with them all having a recovery installed. You need to get a job but you have no experience, but you need experience to get a job...

Tim Elliott said:
Thanks for the information, Nick. I'm sure a lot of people got these for 8 bucks like I did just to play around with. I have no intention of putting a sim in it.
Click to expand...
Click to collapse
If you want to have some basic data, the Freedompop LTE SIM shows up as an ATT SIM in this device, so it works, even w/o unlocking. can get up to 400 MB of data free per month, along w/free VoIP minutes. While that data isn't going to get you streaming, it's more than enough for some IoT stuff.

Heres a little video i made of the Maven 3 running antutu benchmark.

ZTE Maven 3 ( SIM Mobile Network) Not Working
I am trying to use a ZTE Maven 3 from AT&T(US) in Africa (gift from a friend), but the mobile network (SIM card) is not active after inserting SIM. I've tried to search available mobile networks but I get the error message "error while searching for networks" after it tries searching for about 10 seconds.
My first thought was that the phone is locked to the AT&T network, but it did not prompt for an unlock code. I have had to reset the phone several times just to ensure that it gets to read the network. NB. (I have the network unlock code and have tried using it on the phone through alternate means to no avail) Is there anything I'm missing? I'll be glad to get your ideas. Thanks.

I am working on one also, looks like it might be a while, device is pretty locked up. Spent most the day today with my kali box trying to find any weakness. so far all I have found is that can be hacked with reverse_tcp in metasploit, not much else yet. Played with some Dirty CoW but didnt get to far with that, phone just hard reboots when the scripts are executed. If anyone else working on this wants to collaborate send me a pm.
I dont log on often but I get the notifications when I get a pm in my email
---------- Post added at 04:12 AM ---------- Previous post was at 04:01 AM ----------
000Nick said:
I've found that QDLoader is activated in EDL mode (adb reboot edl; you will know you are in when the screen is off and nothing is happening) but I'm not sure how that's useful for us. fastboot and adb do not work in this mode. Volume down + Power button = FTM (field test mode) but I'm not sure what to do in that mode - you can use adb commands but you can't do anything special like mount system as r/w - no fastboot in this mode either. I also tried the ZTE Axon 7 tuliptool but that didn't detect anything (worth a try I guess). iRoot, srsroot, kingroot (pc & apk) don't root it in the FTM mode or regular OS. I've tried adb reboot disemmcwc thing to disable write protection but that didn't seem to do anything different. adb reboot bootloader only brings you to the regular OS. There is also a recovery, but that really only allows you to wipe data/cache and view logs, etc. (volume up + power).
There is an OEM Unlock option in the developer settings, but I still haven't found a way to get to use fastboot. Looking in the system, there are some debug scripts in the /system/bin folder, as well as busybox (toolbox & toybox included) which is interesting. The device is on 7.1.1 & security update "July 1, 2017" (any later exploits?). In "About", there is also a section called "Additional system updates" which seems to allow installing update packages from root directory on storage card?
I'm stuck there, as I'm not super knowledgeable in the art of rooting. Hopefully someone can figure this out!
Click to expand...
Click to collapse
ZTE phone bootloaders are very secure, unless its part of the ZTE Open project, best we can hope for is a root solution, anything else is a pipe dream or is far far away.
Also not to crush your hopes, a majority of phones now show that OEM Unlock button even though there is not much you can do. Busybox is just toolbox. However that said, If you like I can get you a list of all busybox commands on the phone.

GidgetTheGnome said:
I am working on one also, looks like it might be a while, device is pretty locked up. Spent most the day today with my kali box trying to find any weakness. so far all I have found is that can be hacked with reverse_tcp in metasploit, not much else yet. Played with some Dirty CoW but didnt get to far with that, phone just hard reboots when the scripts are executed. If anyone else working on this wants to collaborate send me a pm.
I dont log on often but I get the notifications when I get a pm in my email
---------- Post added at 04:12 AM ---------- Previous post was at 04:01 AM ----------
ZTE phone bootloaders are very secure, unless its part of the ZTE Open project, best we can hope for is a root solution, anything else is a pipe dream or is far far away.
Also not to crush your hopes, a majority of phones now show that OEM Unlock button even though there is not much you can do. Busybox is just toolbox. However that said, If you like I can get you a list of all busybox commands on the phone.
Click to expand...
Click to collapse
I was also able to gain reverse_tcp meterpeter shell and attempted Dirty CoW with no results (not even a reboot ). Im no expert on Android but perhaps someone could use DRAMMER to bit flip the selinux policy to permissive and or gain temporal root?

FreakofN said:
It'd be nice if there were ANY way to root the Maven 2 or 3, I've tried pretty much every well know apk , without PC, & no root. Almost got it 1 time & started to try to remove some crapware & bam reboot.
I'm confused on the custom recovery / root thing. Seems like a chicken / egg ? Need root to install recovery but the root methods on Youtube all seem to start with them all having a recovery installed. You need to get a job but you have no experience, but you need experience to get a job...
Click to expand...
Click to collapse
LOL. Sorry FreakofN, not laughing at you but if your laughing I'm with ya. I too am playing with a Z835 maven 3 and though my knowledge isn't as advanced to rooting I am learning a thing or two here and there by reading, what I'm finding to be limited, discussion's on the topic related to this particular phone. Now I'm about to boldly reach out to the good people of XDA sporting this particular phone and show my smarts off by asking can someone please tell me where I can find the clipboard on this particular phone. LOL! ?? ROCK N ROLL!
---------- Post added at 09:10 AM ---------- Previous post was at 08:43 AM ----------
Eric1084 said:
It's apparently going to be $8 shipped from best buy on black friday. I think a lot of people will pick one up even if it were to be just an emergency phone.
Click to expand...
Click to collapse
WOW! good deal.

ATOTO S8 - System Contents

I spent the better part of 4 hours today setting up the connection between my new ATOTO S8 Pro and my laptop. After getting USB debugging working, and a functional adb shell, I pulled off everything that I could copy with the limited permissions I had.
To be clear, I have NOT rooted the headunit. I'm a little leery about doing it, as I don't want to break anything, and as of right now, there is no way to restore the headunit back to factory like you would with, say, a Pixel phone.
BUT, for those of you who are curious here is my compressed system dump (or rather, adb pull) of everything I could get my hands on while in a factory state.
https://drive.google.com/file/d/13llpDmcNc5pyKbOIePn1hdDYxXd5iPeP/view?usp=sharing
INTERESTING TIDBITS:
* There is a "fastboot mode". Accessed by the usual "adb reboot fastboot" (still seeing what I can do with it)
* After around 6m 30s, fastboot mode will automatically reboot the unit back into the OS. Fastboot activity MAY reset the idle timer, not sure yet.
* There is NO "recovery mode". "adb reboot recovery" simply reboots the unit. May or may not be a recovery like most phones. Still digging.
* Seems the bootloader is unlockable. I have not done it though. You can activate the "bootloader unlock" option in developer options.
* To access Developer Options, you do the usual button mashing on "About", but to access the actual menu, you need a play store program that will take you directly to it.
* The ONLY USB connection that USB debugging works on is USB1 --> Phone Link. For it to work, you need to change the "computer connection" to whatever the SECOND option is (I'm not translating it)
* File down the very end, outer part of the wire harness clip, and it will go in all the way and latch like it's supposed it. Just needs to clear the casing by 1/16" or less. EASY FIX!
If I find any more interesting things while I have this, I'll update the information here. If YOU decide to root yours, let me know how it goes. I don't have another $340 to spare to buy another one. I'm poor. lol

Subscribed. Thanks for reporting that adb can be done via the second usb connection menu option. I had given up not long ago but changed that last night and it did the trick.

kramttocs said:
Subscribed. Thanks for reporting that adb can be done via the second usb connection menu option. I had given up not long ago but changed that last night and it did the trick.
Click to expand...
Click to collapse
It was like the second thing I tried.
Doing some more probing in a few minutes. Going to see if there is a recovery mode that can be accessed.
So it looks like, if I'm reading things right, there is no root for Oreo using a "One-Click" method. I would have to have access to TWRP, CWM recovery, or something to flash SuperSU. Unless I'm forgetting a method....

When it comes to rooting, I am a consumer so excuse my ignorance. In the file dump does it have the boot.img? If so, is this anything helpful: https://forum.xda-developers.com/android/software-hacking/root-recovery-root-device-magisk-t3779454 ?

Silly/stupid question. I just connected my S8 Ultra up to my car this weekend. Do you use a double-ended USB-A to USB-A cable to connect to use ADB? Or is there another connection that I missed?

JMeister234 said:
Silly/stupid question. I just connected my S8 Ultra up to my car this weekend. Do you use a double-ended USB-A to USB-A cable to connect to use ADB? Or is there another connection that I missed?
Click to expand...
Click to collapse
I used a usb A to usb C as my laptop had the C port. I tried a usb A male to male adapter and that didn't work but it may have been the adapter. A true A to A male cable may work. Just make sure you change the usb setting in the menu of Developer tools.

If you don't know this already, you can access OEM settings on the ATOTO unit this way:
Settings>System, click this option four times continually>input 3368, you will enter into the OEM Settings
It did work for me. I eliminated the split screen view on the back up camera through this hidden menu.
BTW, I was able to get to developer's options without a separate app and interestingly my unit came with developer's options already turned on.
It is also not a guarantee that you can unlock the bootloader just because the option appears in developer's mode. These units use a very customized version of Android & it seems some things are still in the settings, but only cosmetically, they don't actually do anything.

We you or anyone able to root this device?
buffaloquinn said:
If you don't know this already, you can access OEM settings on the ATOTO unit this way:
Settings>System, click this option four times continually>input 3368, you will enter into the OEM Settings
It did work for me. I eliminated the split screen view on the back up camera through this hidden menu.
BTW, I was able to get to developer's options without a separate app and interestingly my unit came with developer's options already turned on.
It is also not a guarantee that you can unlock the bootloader just because the option appears in developer's mode. These units use a very customized version of Android & it seems some things are still in the settings, but only cosmetically, they don't actually do anything.
Click to expand...
Click to collapse

afoarun said:
We you or anyone able to root this device?
Click to expand...
Click to collapse
As far as I know, no one has rooted this device. Having bricked a much cheaper unit attempting root, I'm reluctant to be the first one to try on this one.

buffaloquinn said:
As far as I know, no one has rooted this device. Having bricked a much cheaper unit attempting root, I'm reluctant to be the first one to try on this one.
Click to expand...
Click to collapse
This might help.
System-Update-only-Applicable-to-S8-Ultra-Model-CA.zip
Shared with Dropbox
www.dropbox.com
Someone else has a firmware for S8 pro. So if you run I to problems you can at least reset back to an unbricked state, maybe. Haven't tried it yet. But I hope to use Magisck so I can get Kali Hunter to be installed.

JMeister234 said:
This might help.
System-Update-only-Applicable-to-S8-Ultra-Model-CA.zip
Shared with Dropbox
www.dropbox.com
Someone else has a firmware for S8 pro. So if you run I to problems you can at least reset back to an unbricked state, maybe. Haven't tried it yet. But I hope to use Magisck so I can get Kali Hunter to be installed.
Click to expand...
Click to collapse
I have an S8 Premium with the floating 10 inch screen. I'd have to be damn sure the firmware was an exact match before I'd attempt it.

buffaloquinn said:
I have an S8 Premium with the floating 10 inch screen. I'd have to be damn sure the firmware was an exact match before I'd attempt it.
Click to expand...
Click to collapse
This guy has the Atoto S8 Pro zip file.
PasadenaTX
forum.xda-developers.com
I can't get adb to work yet so that's all that's stopping me
Atoto just gave it to me when I told them my touchscreen didn't work and I only had a Bluetooth mouse at home...

kramttocs said:
Subscribed. Thanks for reporting that adb can be done via the second usb connection menu option. I had given up not long ago but changed that last night and it did the trick.
Click to expand...
Click to collapse
I actually don't see the USB debugging options in the developer options. I did the 3368 thing but nothing in that menu looks anything close to USB debugging, ie same as my phone.
Without that, I don't know how to adb shell into the unit.

JMeister234 said:
I actually don't see the USB debugging options in the developer options. I did the 3368 thing but nothing in that menu looks anything close to USB debugging, ie same as my phone.
Without that, I don't know how to adb shell into the unit.
Click to expand...
Click to collapse
I'll have to check later but I believe it was from the top right 3 dot menu.

kramttocs said:
I'll have to check later but I believe it was from the top right 3 dot menu.
Click to expand...
Click to collapse
1. I can confirm that I flashed/updated the S8 Ultra using the Dropbox zip file above and after it reset Android, it did nothing but reset my google credentials. My apps were still there.
But it also didn't brick my S8 Ultra .
It has the similar files as the Joying zip file which has the same chipset.
After the flash, my phone asked to authorize the adb debugging, while connected to the head unit. I'll see if I can get the head unit to turn on adb debugging so I can root it.

JMeister234 said:
Without pics it didn't happen...
Click to expand...
Click to collapse

Another?
{
"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"
}

JMeister234 said:
1. I can confirm that I flashed/updated the S8 Ultra using the Dropbox zip file above and after it reset Android, it did nothing but reset my google credentials. My apps were still there.
But it also didn't brick my S8 Ultra .
It has the similar files as the Joying zip file which has the same chipset.
After the flash, my phone asked to authorize the adb debugging, while connected to the head unit. I'll see if I can get the head unit to turn on adb debugging so I can root it.
Click to expand...
Click to collapse
Any new developments?

buffaloquinn said:
Any new developments?
Click to expand...
Click to collapse
Well I brought my Ouya back from the dead with LineageOS, converted a Chromebook to GalliumOS for pen testing, or it can connect to Ouyas using adb, or analyze a Lenovo Smartclock to try and add APK's to it before giving up (as others on XDA have also done).
But for this? I can't get ADB to see the head unit. Because there is no ADB Debugging in any of the menus (yes its has Dev Options enabled). No idea how others have done it. If I reboot into Recovery it might show up in "adb devices" command but if the device is simply on, there's nothing returned.

JMeister234 said:
Well I brought my Ouya back from the dead with LineageOS, converted a Chromebook to GalliumOS for pen testing, or it can connect to Ouyas using adb, or analyze a Lenovo Smartclock to try and add APK's to it before giving up (as others on XDA have also done).
But for this? I can't get ADB to see the head unit. Because there is no ADB Debugging in any of the menus (yes its has Dev Options enabled). No idea how others have done it. If I reboot into Recovery it might show up in "adb devices" command but if the device is simply on, there's nothing returned.
Click to expand...
Click to collapse
I use one of the Play Store apps to get into Developer options and it does show an ADB debugging option and most of the other choices available in a typical Developer's menu. The one I use is the first one that comes up in the search on play store, I think the author is Singlebyte.