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.
Related
You have undoubtedly seen lot of Rooting guides for the Mytouch 3G Slide, claiming to root the phone:
wiki.cyanogenmod.com/wiki/TMobile_myTouch_Slide:_Full_Update_Guide
http://forum.xda-developers.com/showthread.php?t=1108316 New way to downgrade from 2.2 to 2.1
http://forum.xda-developers.com/showthread.php?t=999121 Ultra Easy Rooter [dbzfanatic][xologist]
http://forum.xda-developers.com/showthread.php?t=1025336 How-To [Root][NewLinks] The myTouch 3GS if you updated to Offical 2.2.1 and lost root
SuperOneClick doesn't work. Nothing works, I've tried them all several times from several different angles. Therer is some sort of NAND lock on the phone, above and beyond typical. Anyways.
None of the aformentioned guides work, so won't waste your time like I did. They are also all written by people who can not communicate well with other human life forms, and they assume you have a CS and/or IS degree, and also assume you have all the software installed on your machine that they have on theirs, and have all the same settings on your phone that you "should" have on yours and they also assume you are doing some "obvious" steps in the middle of their steps that you should know how to do. They won't tell you that, but they do. So here is the REAL definitive step by step guide, with pics, on how to do it. BTW, you don't need a gold card. You don't need to mess with any consol crap. This should take 15-20 minutes max. What we're basically going to be doing is downgrading to 2.1-update1, then rooting, then putting on the Cyanogen Mod, then adding the google apps (which are not included in the cyanogen mod). I've put as many pics as I could and tried to do a step by step that ANYONE can follow.
I was using Windows 7 64-bit SP1 and I think these are the things that you need to have set up, you may not need them but I was trying so many of everything that I don't even know if they are all required, I'm sure I missed some things, but I will keep editing this guide as needed)
*Make sure you have at least 25MB of free space on your phone's internal memory.
*Make sure you've backed everything up you want to (text messages, bookmarks, programs, etc) But the google cloud should keep most your other stuff okay. (email etc) http://tinyurl.com/3b4qp6q
*Turn USB Debugging on your phone. (Settings, applications, development > USB Debugging - check)
*Turn phone to charge mode only when you plug in the USB cable
*PDAnet was running on the PC (This is required it will install the correct driver for step 1, though it's a tethering app and you won't need it for that) - http://junefabrics.com/android/download.php
1. Plug in phone and go to device manager from control panel on your computer.
You open the "Android USB Devices" and see what driver it says.
If it says something like "Mytouch Slide 3G"
{
"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"
}
go to Update driver > Browse my computer for driver software > Let me pick
pick this one: "ADB Device Interface" , say okay, etc.
If it does say "ADB Drvice Interface" you're good. Exit out of that.
2. Download "T-Mobile_myTouch_3G_Slide_Software_Update_2.15.531.3.exe" from here http://www.htc.com/us/support/t-mobile-mytouch-3g-slide/downloads/ (157MB)
3. Go to your temp windows folder. IF you do Start > Search %TEMP% it should pop up. Keep on eye on this folder as you do the next step. (Maybe sort by date modified to help)
4. Double Click the "T-Mobile_myTouch_3G_Slide_Software_Update_2.15.531.3.exe" file and have it extract everything. At the first main screen, just wait there with it open and not installed.
You hopefully should have seen some folders be created in your temp file. There were 2 on mine, like so, check them both out:
When you see the one that looks like this:
and has a folder structure like this:
that's the folder you want to copy. So:
5. Highlight the folder with "ARUWizard.exe" and "rom.zip" in it. Mine had about 74 files in it. Copy it, and copy it to another part of your hard drive, and rename that awful folder, sheesh. (not needed)
6. You can close out of the Rom Update Utility.
7. In that NEW copied folder, delete "rom.zip"
8. Download the ~140 MB "ESPRIMG.zip" from here: http://www.4shared.com/file/OsmF_ZD7/ESPRIMG.html
9. Put it into the folder that we copied out, and rename it from ESPRIMG.zip TO rom.zip
10. Now, while you are in that folder, "ARUWizard.exe" check check, next, etc.
11. This will downgrade your phone from 2.2.1 to 2.1-update1
12. Tada! Good job. Now, go download the lastest Cyanogen firmware ROM here: http://download.cyanogenmod.com/?type=stable&device=espresso
13. Rename the "update-cm-7.X.X-Slide-signed.zip" to "update.zip"
14. While you are doing this, download the lastest Google Apps from here: http://wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps Mine was called "gapps-gb-20110613-signed.zip" and put that on your phone's memory card as well, no renaming needed.
15. Turn off your phone and take out the memory card and put it in your computer (or turn the phone back into a mountable drive) and copy over the update.zip onto the root director of your memory card.
16. Hold "down volume" and "power" which will boot you into a techy looking screen. Ignore any errors, the volume up and down navigates, so go into "Recovery" Mode.
17. Once in the Recovery, you will see a device with a triangle. Press "Volume Up" & the "Power" button.
18. Select the option to Wipe data/factory reset. Then select the option to Wipe cache partition.
19. See the option to "apply sdcard:update.zip" ? Do it, with power as confirm. This will put the Cyanogen mod on your phone!
20. Reboot system now. Now, you should boot into Cyanogen 2.3.x! However, you will notice you don't have any of the google apps.
21. So, Now, go into your programs on the phone, and you will see "Rom Manager" a eye with a tophat. Say "Install Rom from SD Card" and pick the "gapps-gb-20110613-signed.zip" You may have to fiddle with the plugging in USB/etc to get access to this, you don't have to buy the program, it will do it, but you have to have it set up so you can see the MicroSDcard, etc.
It will reboot your phone and you will now and install all the google apps. The most important one is MARKET, so you can download stuff. It will now go through all the TOS for each google program you said you want. The rest the wizard should navigate you through properly.
Holy hell this was a terribly troubleshooting process which probably took me 20 hours to figure out they were ALL wrong. Big thanks to "Da Maestro" who helped me on Cyanogenmod.
Enjoy!
wait wait wait... so will this method revert the hboot from 1. whatever to the older version and allow S-OFF?!
yeah, I don't even know what you're saying, I'm such the nube. I don't think this deals with the S-On/Off problem though. I saw some other posts that fixed that. This method does nothing to do with that, as far as I know
All I'm saying is I have Cyanogen 7 on my phone and this is how I did it from 2.2.1 stock.
txdeathray said:
wait wait wait... so will this method revert the hboot from 1. whatever to the older version and allow S-OFF?!
Click to expand...
Click to collapse
as far as i'm aware of, there's no S-OFF after you upgrade to 2.2.1, so i was thinking if you can check your hboot by powering off your phone and then turn it on by holding down volume down and power button. hboot version should be on the very top of your screen.
Bootloader error
I get 140 bootloader version error from the RUU. So far I have not been able to get any of the root mrthods to work with my slide.
Any ideas?
nikolag said:
I get 140 bootloader version error from the RUU. So far I have not been able to get any of the root mrthods to work with my slide.
Any ideas?
Click to expand...
Click to collapse
Well at least your not alone in that club. Getting the same error, even using a goldcard. I guess back to the drawing board for us at least.
yeah I had that error too,
http://forum.cyanogenmod.com/topic/28205-stuck-on-step-8-rooting/
EDIT: To fix it, make sure PDANet it installed and that will install the driver so you can change it from "t-mobile mytouch 3G" to "ADB Device..." It's step 1.
raziel420 said:
Well at least your not alone in that club. Getting the same error, even using a goldcard. I guess back to the drawing board for us at least.
Click to expand...
Click to collapse
That is one thing I didn't see, although upon checking it,s not there, and I do have the android SDK installed :/
If it helps any I'm on windows 7 ultimate x64 (since the problem seems driver related).
*edit 1* I keep seeing places where it says to check for the ADB interface driver, but nobody seems to know how to actually install said driver, or where it can be found at.
*edit 2* Turns out that PDAnet is what supplies the ADB driver, so as it happens that IS required (and here I thought that was a stupid tethering app)
*Edit 3* So just to make sure I downloaded the software on the posted links just to make sure some of the other versions I had were not incompatable, and still no joy. At this point I've spent a good 6 hours trying to root this phone and growing significantly more annoyed with it. If anyone has any feel free to contact me, I'd really like to get this working.
hey thanks, I'll edit the guide to say it's required.
Same here, went through all of the steps, still keep getting the 140 error.
edit* went all the way through the steps again very thoroughly, still getting the same error 140. Any Ideas?
It was such a complicated process, dealing with all the other guides some part of them may have worked that I missed. Maybe you do indeed need to make a gold card. It didn't work (I think) on one MicroSD card so I changed to another one.
So I guess make a gold card and give it a try. This is the guide I used to make a gold card:
http://wiki.cyanogenmod.com/wiki/Howto:_Create_a_Goldcard
Thanks for helping me get this guide correct.
One thing I did have to do is change USB ports and USB cables, as stupid as that is, I know, I know. The ones in my monitor worked but the front ones on my computer didn't work with the ROM update utility, but I think the error code I was getting was 170 or 171 USB disconnect error.
dgrwe2512 said:
Same here, went through all of the steps, still keep getting the 140 error.
edit* went all the way through the steps again very thoroughly, still getting the same error 140. Any Ideas?
Click to expand...
Click to collapse
What if you were to save that rom.zip file directly on the SD card, as the update.zip file first? Would that load 2.1? Because the installer wont.
I'm going to try it....
Nope, didn't work.
The gold card would be great if I had a second sd card, guess I will have to go buy one if I want to regain root.
the gold card worked for me just fine after getting my replacement phone on 2.2.1 all i did was back up everything on my sd card make and use the gold card get root and put every thing back on my sd card just fine.
dgrwe2512 said:
Same here, went through all of the steps, still keep getting the 140 error.
edit* went all the way through the steps again very thoroughly, still getting the same error 140. Any Ideas?
Click to expand...
Click to collapse
Do you have PDANet Installed?
Yes, its installed and running. Also, I made a gold card out of my SD card and tried again, and still got the same error. I am starting to hate T-Mobile!
katbastard said:
the gold card worked for me just fine after getting my replacement phone on 2.2.1 all i did was back up everything on my sd card make and use the gold card get root and put every thing back on my sd card just fine.
Click to expand...
Click to collapse
Do you have a link to the Gold Card method that worked for you? I keep getting a bootloader error with this method, about ready to give up.
dgrwe2512 said:
Do you have a link to the Gold Card method that worked for you? I keep getting a bootloader error with this method, about ready to give up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1025336
did this as it reads, i am not a super geek, just know how to follow a list of things to do. i rooted one other time before this when it was really hard to do still. i thought this way was easier
I'm kinda confused why there is gold card discussion here. The method outlined in the first post specifically says that you don't need a gold card. Does this method not work and is that why you are trying gold card stuff?
dgrwe2512 said:
Yes, its installed and running. Also, I made a gold card out of my SD card and tried again, and still got the same error. I am starting to hate T-Mobile!
Click to expand...
Click to collapse
I don't think should have it running while you root. (I would assume that would just cause problems.) You just need to install it for the usb drivers and make sure it works.
Firefox OS
Alcatel One Touch Fire
{
"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"
}
How to Flash Succesfully Any verion of Firefox OS
Get the Build(user.img,boot.img,system.img,data.img)
download a build from here http://elsimpicuitico.wordpress.com/firefoxos/
make your own with the mozilla guide (so stop here and follow mozilla guide)https://developer.mozilla.org/en-US/Firefox_OS/Building_and_installing_Firefox_OS
get one from a friend
Plug-in your Alcatel Fire(Hamachi)
Make sure you have the "Remote Debugging" enabled(Settings > Device information > More information > Developer > Remote Debugging)
Look inside the .zip/tar.gz you had downloaded,there some "flash" files.If:
You are on windows:double click on "flash.bat"
You are on linux,open the terminal in the folder you had unzipped the build,and type"./flash"
Done
If you have a consumer phone, not a dev edition, you will not get root access on adb.
So you have to do this in a Linux machine(or with Cygwin):
shutdown phone
power on pressing "volume-"
it will get 'stuck' into the "alcatel" logo. don't worry it probably worked, this is the screen for fastboot mode as well.
plug in your computer and check `fastboot devices`. if any error here, go read one of the thousands guides for fastboot and android usb drivers
get any boot image from that page. ideally one from the same country as it may matter....
flash the boot image on your phone with. test first with `fastboot boot boot.img`. if it works, redo the above steps and make it permanent `fastboot flash boot boot.img`. You need any boot image that has default.prop setting the user for adb as 0 instead of the default 1.
If you want the ClockworkMod recovery i can update this post to explain how to flash it .
If you will have any problem ,I'll help you and I will update this thread with your problem with the fix
Some infos
When you turn On your Alcatel OTF,you have 4sec to hold "volume-" button just after powering it up. It will stop at initial Alcatel’s logo.If you are ona Linux computer you can confirm that it is connected by typing "fastboot devices"-
Th Codenme of this phone is:Hamachi.
Credits
Me and the owner of the Firefox Os Builds for Hamachi
Thanks HawkeyeWPR. This and your site was very helpful for me and my Fire. Keep going!
Your provided version 1.4 is very nice and fast and I could choose beetween two recoverys (CWM or TWRP). Thats awesome.
HawkeyeWPR said:
Plug-in your Alcatel Fire(Hamachi)
Make sure you have the "Remote Debugging" enabled(Settings > Device information > More information > Developer > Remote Debugging)
Look inside the .zip/tar.gz you had downloaded,there some "flash" files.If:
Click to expand...
Click to collapse
If you have a consumer phone, not a dev edition, you will not get root access on adb.
So you have to:
shutdown phone
power on pressing volume down
it will get 'stuck' into the "alcatel" logo. don't worry it probably worked, this is the screen for fastboot mode as well.
plug in your computer and check `fastboot devices`. if any error here, go read one of the thousands guides for fastboot and android usb drivers
get any boot image from that page. ideally one from the same country as it may matter....
flash the boot image on your phone with. test first with `fastboot boot boot.img`. if it works, redo the above steps and make it permanent `fastboot flash boot boot.img`. You need any boot image that has default.prop setting the user for adb as 0 instead of the default 1.
gcbxda said:
If you have a consumer phone, not a dev edition, you will not get root access on adb.
So you have to:
shutdown phone
power on pressing volume down
it will get 'stuck' into the "alcatel" logo. don't worry it probably worked, this is the screen for fastboot mode as well.
plug in your computer and check `fastboot devices`. if any error here, go read one of the thousands guides for fastboot and android usb drivers
get any boot image from that page. ideally one from the same country as it may matter....
flash the boot image on your phone with. test first with `fastboot boot boot.img`. if it works, redo the above steps and make it permanent `fastboot flash boot boot.img`. You need any boot image that has default.prop setting the user for adb as 0 instead of the default 1.
Click to expand...
Click to collapse
The same process i've done,cause the boot.img file contains the kernel with access to grant "root" access,now I'll add this step to my guide ,Thanks
subnet_zero said:
Thanks HawkeyeWPR. This and your site was very helpful for me and my Fire. Keep going!
Your provided version 1.4 is very nice and fast and I could choose beetween two recoverys (CWM or TWRP). Thats awesome.
Click to expand...
Click to collapse
I'm the Only here experiencing some crashes in the Firefox Browser?
HawkeyeWPR said:
I'm the Only here experiencing some crashes in the Firefox Browser?
Click to expand...
Click to collapse
nope. It is inconsistent as hell right now. Try to compile an image or use a latest build and submit bug reports (it's a full weekend effort just to get started, i tell you that)
Sent from my Nexus One using xda app-developers app
Is there any chance to do video for this, since most blogs are on Spanish and i believe most of us have no expirience in this? :S
Facyber said:
Is there any chance to do video for this, since most blogs are on Spanish and i believe most of us have no expirience in this? :S
Click to expand...
Click to collapse
just follow the points. and when it mentions "look for a guid on something" it is because there are already a ton of video-or-not guides on that stuff
any point in particular you are having trouble?
But a warning, it is unstable. the shipped image has pretty much everything you need anyway (a stable browser)
upgrading to 1.4 will give you almost nothing else new. The browser still has no extra options. no add-ons. nothing. just tabs, back foward, clear history. that is all. most of the changes from 1.1 to 1.4 were in the gaia (ffos launcher) and even that, weren't too interesting ones to being with.
my advice is to stick with the shipped image if you are not going to code for ffos. Or at least help submiting bug reports.
gcbxda said:
just follow the points. and when it mentions "look for a guid on something" it is because there are already a ton of video-or-not guides on that stuff
any point in particular you are having trouble?
But a warning, it is unstable. the shipped image has pretty much everything you need anyway (a stable browser)
upgrading to 1.4 will give you almost nothing else new. The browser still has no extra options. no add-ons. nothing. just tabs, back foward, clear history. that is all. most of the changes from 1.1 to 1.4 were in the gaia (ffos launcher) and even that, weren't too interesting ones to being with.
my advice is to stick with the shipped image if you are not going to code for ffos. Or at least help submiting bug reports.
Click to expand...
Click to collapse
Root part. Don't have clue how, but I found friend coder who knows this stuff so hes gonna try first.
I have intention on building apps for Firefox OS only, so I would like to see new versions, since Telenor in my country is retarded, they ain't relased 1.3 yet, even its been almost a month since relase. -.-
Facyber said:
Root part. Don't have clue how, but I found friend coder who knows this stuff so hes gonna try first.
I have intention on building apps for Firefox OS only, so I would like to see new versions, since Telenor in my country is retarded, they ain't relased 1.3 yet, even its been almost a month since relase. -.-
Click to expand...
Click to collapse
Having a device in the older version is good for that... just so you have an idea, i got my phone in a mexican store. it came with 1.1 and no sign of update ...ever. so your users will NOT be on the latest version anyway.
i suggest you simply use the emulator. develop. and ocasionaly test your app on your 1.3 device for performance and multitouch tests
if you really want to flash just to test apps, not to use your phone daily, you don't even need root just to update the image. unless you want a backup...
just use fastboot to overwrite the system partition (the user interface and gecko code). No root needed. just 3 steps:
1. boot with volume down.
2. plug USB in computer when it gets stuck on the white alcatel screen.
3. `fastboot flash system <name_of_the_file_with_system.img>`
that is all you need.
you will still be able to re-do that any time, so, go crazy. there is no way to brick the phone with that. (your system may be unusable if you use a bad image, but you can always flash a good one later on)
Well I want to use it daily, using apps and stuff like that, but also want to develop. I thought to try for this low device until some better phone came, or even tablet, much faster and stronger, than that will be other story.
Actually,will ship:
The ZTE Open C has a 4-inch, 800x480 display, a dual-core 1.2GHz Qualcomm Snapdragon 200 processor, 3G networking; 1,400mAh battery, 512MB RAM, 2GB flash storage, and 3-megapixel camera. The Spanish carrier Telefonica will sell it in Venezuela and Uruguay in the second quarter of 2014, ZTE said.
The ZTE Open II has a 3.5-inch 480x320 display, dual-core 1.2GHz Qualcomm Snapdragon processor, 3G networking; 1,150mAh battery, 256MB RAM, 2GB flash storage, and 2-megapixel camera. Telefonica will sell this model in six countries
The Alcatel One Touch Fire S, the company's highest-end model, has 4G LTE networking, a 4.5-inch 960x540 IPS screen, a quad-core 1.2GHz processor, an 8-megapixel rear-facing camera and 2-megapixel front-facing camera, and support for near-field communications (NFC).
The Alcatel One Touch Fire E is a step down. It's also got a4.5-inch 960x540 screen, but not with in-plane switching, and its 1.2GHz processor is only a dual-core model. Its rear-facing camera has a 5MP resolution but its front-facing camera is only 0.3MP.
The Alcatel One Touch Fire C is the clear successor to 2013's model. Its 3.5-inch 480x320 screen is the same size, but it now is accompanied by a dual-core 1.2GHz processor. Its camera is pretty low-end, just a 0.3-megapixel model.
and DO NOT FORGET the 25$ model:
Allwinner A31 (1.2GHz); Cortex-A7 Quad-core, PowerVR 544MP2
4.5-inch screen (FWVGA 854×480 pixels)
Cameras: Rear: 5MP / Front: 2MP
3G UMTS quad-band (850/900/1900/2100)
8GB memory
256MB -1GB RAM (adjustable by developer)
A-GPS, NFC
Battery capacity: 1,800 mAh
Wi-fi: 802.11 b/g/n, Bluetooth, Micro USB
At the moment,iìm using my Alcatel OTF as main-daily-use phone,for twitter,mails,pictures,web-browsing,call&texting(+ Whatsapp),and i admit ,sometime he get me angry,but at least ,it's good,for a simple and daily use,but i recommend the 1.3 vers,1.4 it's buggy.
I know all about those new phones, It's kinda my job to know that.
Main reason why I'm not using as daily phone casue my main number is not in Telenor network (Thank God to that, they are most expensive here and yet give less free sms and minutes then other two) and in one shop they couldn't unlock it, whatever code they get it won't work, so I will wait little more and find new shop.
We already given up from Telenor relasing new version, believe me, they gonna relase 1.3 when 2.5 comes out. Mark my words.
I have a question about back up. Do I have to back up? Or can I simply root and then instal? I have no Idea hwo to back up image on Windows.
Firefox os
This is the first Time i've discovered this. When Will this be readily available in the U.S.? I can find the devices on amazon, but will they work with our carriers?
Rustydagger said:
This is the first Time i've discovered this. When Will this be readily available in the U.S.? I can find the devices on amazon, but will they work with our carriers?
Click to expand...
Click to collapse
If you want a device that works in US you can always buy one of the ZTE Open or Open C from the ZTE_US ebay store.
The Open is pretty much the same as the Alcatel Touch Fire
Sent from my V3 using Tapatalk
linr76 said:
If you want a device that works in US you can always buy one of the ZTE Open or Open C from the ZTE_US ebay store.
The Open is pretty much the same as the Alcatel Touch Fire
Sent from my V3 using Tapatalk
Click to expand...
Click to collapse
I agree ^^
Sent From My Samsung Galaxy Y s5360
Thank you for your guide-resume
I was trying to build the latest Firefox OS master branch, but unfortunately, due to some issues, I can't do it for now.
Unfortunately, the builds which the blog Simpliculitico gives are modified ones;
I'd like a clean pure one;
can someone send/upload an allready built and unmodified master image for One Touch Fire? I have no friends who can send me one
Thank you so much *
I tried to follow the instructions and got help on irc to create the custom kennel for that dammed phone.
Two weekends later and i failed every single time.
Never got even a half working one.
Also the one from the blog is far from perfect...
I wouldn't keep my hopes up.
Sent from my XT1053 using XDA Free mobile app
I agree with you,that's why now i will make a guide to have Official OTA from mozilla.
we dont have a section for the vk815 yet so im posting here.
i just rooted my g pad with a 1-click root fro the g3 section
{
"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"
}
i followed this guide by avicohh . be sure to give him a thanks for his work
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
if anyone would like to compile TWRP for the X8.3 we would be very appreciative and i now i would be willing to donate some beer money.
i am not a dev and do not pretend to know anything bout building roms an such but am willing to be a tester
Credit goes to Unjustified Dev for the LG Root Method used here:
UPDATE:
This is the method I used.
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
I used these Drivers:
http://sourceforge.net/projects/avicohh/files/Android/LG_VZW_United_WHQL_v2.20.0.exe/download
Follow the guide all the way through ADB pushing the files to the device in step 5. Easy part.
Step 6 has you rebooted into Download mode:
With Tablet OFF, hold Volume UP and plug in PC connection
Once in download mode, UNPLUG the cable (it says not to but its ok) and replug it back in. This will bling on your PC and will start the driver install process. It will take a minute or 2 before the "unknown devices" start to pop up and start installing the drivers.
You should see a LG device under Device Manager > Ports. Mine was COM5. It varies. Now we are ready to continue. Run the "ports.bat" from a CMD prompt. You want to use the "NETDIAG1" port. Mine was COM5. Don't use the modem COM.
use the "Send_Command.exe \\COM5" to get shell access into your tablet. You should see a "#".
I like to type in "ls /data/local/tmp" to verify the files were pushed over properly in the first few steps using ADB.
AND FOR SOME REASON, this doesn't always work on the first try. I have better luck manually typing out the script string.
Code:
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
You should see a bunch of "inflating...." lines. If it gets stuck or just returns a blank "#" just keep retrying. It seems to work after it is sitting for a few minutes. Eventually you will see the script take off and you are done.
Just hold the power button down and reboot.
player911 said:
Credit goes to Unjustified Dev for the LG Root Method used here:
UPDATE:
This is the method I used.
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
I used these Drivers:
http://sourceforge.net/projects/avicohh/files/Android/LG_VZW_United_WHQL_v2.20.0.exe/download
Follow the guide all the way through ADB pushing the files to the device in step 5. Easy part.
Step 6 has you rebooted into Download mode:
With Tablet OFF, hold Volume Down and plug in PC connection
Once in download mode, UNPLUG the cable (it says not to but its ok) and replug it back in. This will bling on your PC and will start the driver install process. It will take a minute or 2 before the "unknown devices" start to pop up and start installing the drivers.
You should see a LG device under Device Manager > Ports. Mine was COM5. It varies. Now we are ready to continue. Run the "ports.bat" from a CMD prompt. You want to use the "NETDIAG1" port. Mine was COM5. Don't use the modem COM.
use the "Send_Command.exe \\COM5" to get shell access into your tablet. You should see a "#".
I like to type in "ls /data/local/tmp" to verify the files were pushed over properly in the first few steps using ADB.
AND FOR SOME REASON, this doesn't always work on the first try. I have better luck manually typing out the script string.
Code:
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
You should see a bunch of "inflating...." lines. If it gets stuck or just returns a blank "#" just keep retrying. It seems to work after it is sitting for a few minutes. Eventually you will see the script take off and you are done.
Just hold the power button down and reboot.
Click to expand...
Click to collapse
glad you got root. have you tried installing twrp from the vk810.?
in the TWRP thread under android development i ask if anyone was willing to compile TRWP for us and a guy i said he would take a look at it.
Nah. Just rooted. Honestly since Lollipop and ART, Xposed has kinda lost its luster. I actually like the stock LG experience.
I successfully rooted this am using the OneClick Root 1.3 method described here:
http://www.smartphoneclinics.com/easy-way-to-root-verizon-lg-g-pad-x-8-3-vk815-one-click/
It took about 5 minutes, and all that I had to do was choose PTP mode. After rooting I installed Busybox, and all is good!
Now, If I could just do the same with my VZW G4...
Requested a forum for VK815.
I'm looking hard at the VK815 since my Nexus 7 2013 died. I requested a forum for the device at http://forum.xda-developers.com/showpost.php?p=61761668&postcount=18535
Thanks for the work you folks have done already.
Give the request a bump. I referred to this thread.
Split screen
player911 said:
Nah. Just rooted. Honestly since Lollipop and ART, Xposed has kinda lost its luster. I actually like the stock LG experience.
Click to expand...
Click to collapse
My reason to root would be for increasing the number of applications Will work with the split screen mod. Anyone give this a try on this tablet?
mhonard said:
My reason to root would be for increasing the number of applications Will work with the split screen mod. Anyone give this a try on this tablet?
Click to expand...
Click to collapse
yes the split screen mod work. that was the first thing i did after rooting. not sure what mod you are looking at. all i did was edit build.prop
Where did you find this mod?
player911 said:
Where did you find this mod?
Click to expand...
Click to collapse
I didn't find the mod anywhere. I just looked though the build. Prop till I found the line bout split window or something and changed it to true. I don't have my tab on hand but will look and let you know the exact line
player911 said:
Where did you find this mod?
Click to expand...
Click to collapse
About 3/4 way down the build.prop you will find a line that says, persist.slitwindow.support_all_false. Change false to true and you will have all your apps in splitwindow
I rooted my X8.3 using this. Thanks!
Sent from my VK815 using XDA Free mobile app
neckbonest said:
glad you got root. have you tried installing twrp from the vk810.?
in the TWRP thread under android development i ask if anyone was willing to compile TRWP for us and a guy i said he would take a look at it.
Click to expand...
Click to collapse
Anyone know if/when we will see TWRP for vk815?
winpooh said:
Anyone know if/when we will see TWRP for vk815?
Click to expand...
Click to collapse
Maybe never hard to say. It has a locked bootloader and may not get much love from the devs
neckbonest said:
Maybe never hard to say. It has a locked bootloader and may not get much love from the devs
Click to expand...
Click to collapse
All of the LGs have a locked bootloader. Never stopped them in the past. Should be as easy as the 7" models.
player911 said:
Credit goes to Unjustified Dev for the LG Root Method used here:
UPDATE:
This is the method I used.
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
I used these Drivers:
http://sourceforge.net/projects/avicohh/files/Android/LG_VZW_United_WHQL_v2.20.0.exe/download
Follow the guide all the way through ADB pushing the files to the device in step 5. Easy part.
Step 6 has you rebooted into Download mode:
With Tablet OFF, hold Volume Down and plug in PC connection
Once in download mode, UNPLUG the cable (it says not to but its ok) and replug it back in. This will bling on your PC and will start the driver install process. It will take a minute or 2 before the "unknown devices" start to pop up and start installing the drivers.
You should see a LG device under Device Manager > Ports. Mine was COM5. It varies. Now we are ready to continue. Run the "ports.bat" from a CMD prompt. You want to use the "NETDIAG1" port. Mine was COM5. Don't use the modem COM.
use the "Send_Command.exe \\COM5" to get shell access into your tablet. You should see a "#".
I like to type in "ls /data/local/tmp" to verify the files were pushed over properly in the first few steps using ADB.
AND FOR SOME REASON, this doesn't always work on the first try. I have better luck manually typing out the script string.
Code:
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
You should see a bunch of "inflating...." lines. If it gets stuck or just returns a blank "#" just keep retrying. It seems to work after it is sitting for a few minutes. Eventually you will see the script take off and you are done.
Just hold the power button down and reboot.
Click to expand...
Click to collapse
Thanks for these instructions! I got root successfully on my Verizon LG G Pad x8.3. Only things that tripped me up were getting the download mode - which is holding volume up on this device, and also rebooting at the end. I had a brief panic when I ran the scripts successfully, but couldn't reboot after it was done. I still had adb connection, so I tried typing "LEAVE" in the Send_Command prompt and that rebooted the device. Thank God!
neckbonest said:
About 3/4 way down the build.prop you will find a line that says, persist.slitwindow.support_all_false. Change false to true and you will have all your apps in splitwindow
Click to expand...
Click to collapse
did not work me, says it cant save
---------- Post added at 03:29 AM ---------- Previous post was at 02:45 AM ----------
did you already have root because i cannot save the build.prop
screenfreak said:
did not work me, says it cant save
---------- Post added at 03:29 AM ---------- Previous post was at 02:45 AM ----------
did you already have root because i cannot save the build.prop
Click to expand...
Click to collapse
You would have to already have root in order to save an edited build prop, and have root r/w enabled in the root browser you're using.
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
bost005 said:
Thanks for these instructions! I got root successfully on my Verizon LG G Pad x8.3. Only things that tripped me up were getting the download mode - which is holding volume up on this device, and also rebooting at the end. I had a brief panic when I ran the scripts successfully, but couldn't reboot after it was done. I still had adb connection, so I tried typing "LEAVE" in the Send_Command prompt and that rebooted the device. Thank God!
Click to expand...
Click to collapse
I made an edit for Volume Up. It typically is up but I swore I had to actually use volume down. Glad it helped. I like to make detailed walkthroughs so I can not only help others but come back to when I need to later.
Once the script was done, I just waited a few minutes to settle and do a hard shut down. I do that on my G2 and G4.
Hi
Almost just a week into my first Moto phone. Paid high for it and rejected a reasonable Huawei that was 25% cheaper because they stopped allowing boot unlocking.
Very impressed so far. Hardware is great although the sleek packaging, whilst feels nice, has me ****scared until the case I've coming in the mail (cannot buy accessories off the shelf in my area, much to my dismay) arrives.
I've seen the impressive 5-post articles by Explorer 4x4. They were a big factor in my choice to pay the extra cash for this phone.
Alas I'm a little nervously unsure of my next step.
Mainly I'd like to freeze / stop / possibly uninstall the bloatware I don't want.
What is the best full backup option, is it still Nandroid?
After that, is a Magisk root the safest / cleanest option to allow me to clean out that bloat I don't want?
Would appreciate any constructive advice.
Thanks
Yes well, you seem to have previous experience in routing and de-bloating, so
1) Backup all apps with titanium backup or similar (I use titanium)
2) remove bloatware with titanium, system app remover or sd maid or the method of your choice. SD maid is good with removing remnants too.
So, nothing special in regards to previous versions. If you're about to remove some system apps, please check XDA forums if something has changed in that aspect. I have removed the ones that I always remove.
Nandroids will not work on pie due to encryption issues(for now) but Google backups will and you can backup and restore apps+data with TiBu too. Migrate is in beta stages but looks promising. Unlike TiBu it also backups app permissions.
Sent from my Moto G6 Plus using XDA Labs
https://forum.xda-developers.com/g6-plus/themes/debloated-os-t3861046
Xplorer4x4 said:
Nandroid will not work on Pie due to encryption issues (for now) but Google backups will and you can backup and restore apps+data with TiBu too. Migrate is in beta stages but looks promising. Unlike TiBu it also backups app permissions.
Click to expand...
Click to collapse
Thanks! Have never heard of TiBu. How do I find that as a search here and a Google search did not return useful results. Google Play?
weazie said:
Yes well, you seem to have previous experience in routing and de-bloating, so
1) Backup all apps with titanium backup or similar (I use titanium)
2) remove bloatware with titanium, system app remover or sd maid or the method of your choice. SD maid is good with removing remnants too.
So, nothing special in regards to previous versions. If you're about to remove some system apps, please check XDA forums if something has changed in that aspect. I have removed the ones that I always remove.
Click to expand...
Click to collapse
Thanks!
Unfortunately I've fallen at the first hurdle / attempt. I'm unable to unlock the bootloader, let alone get root:
Code:
fastboot oem get_unlock_data
... just hangs without returning anything despite having toggled 'OEM Unlock' in Developer options.
jandroidian said:
Thanks!
Unfortunately I've fallen at the first hurdle / attempt. I'm unable to unlock the bootloader, let alone get root:
Code:
fastboot oem get_unlock_data
... just hangs without returning anything despite having toggled 'OEM Unlock' in Developer options.
Click to expand...
Click to collapse
Are you able to boot into bootloader? Does 'fastboot devices' show your device? Hint: Don't paste your IMEI here.
---------- Post added at 17:51 ---------- Previous post was at 17:47 ----------
jandroidian said:
Thanks! Have never heard of TiBu. How do I find that as a search here and a Google search did not return useful results. Google Play?
Click to expand...
Click to collapse
TiBu = Titanium Backup
weazie said:
Are you able to boot into bootloader? Does 'fastboot devices' show your device? Hint: Don't paste your IMEI here.
---------- Post added at 17:51 ---------- Previous post was at 17:47 ----------
TiBu = Titanium Backup
Click to expand...
Click to collapse
Ah, had a suspicion it was a shortening for Titanium but it was too late at night for my brain to decode it
Yes, `fastboot devices` returns the device serial number and then the word fastboot.
I can also see the fastboot oem get_unlock_data command sent to the device via a line in the bootloader logs screen:
cmd: oem get_unlock_data
Click to expand...
Click to collapse
... however after several minutes, it's just hung. Tried the --verbose flag and still nothing :
{
"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"
}
jandroidian said:
I can also see the fastboot oem get_unlock_data command sent to the device via a line in the bootloader logs screen:
... however after several minutes, it's just hung. Tried the --verbose flag and still nothing :
Click to expand...
Click to collapse
- Do You have the Motorola Drivers installed?
- Are You running the cmd in administrator mode? Try also Windows Powershell.
Other than that, I can't think of anything right now. Many people seem to have had this problem in older moto phones, but I didn't find a solution. Some user mentioned in Youtube comments that "this problem can be solved by jtag software, replacing bootloader" altogether. But sounds like a drastic solution.
weazie said:
- Do You have the Motorola Drivers installed?
Click to expand...
Click to collapse
Yes. Installed them. Latest version I believe.
weazie said:
- Are You running the cmd in administrator mode?
Click to expand...
Click to collapse
Yes, originally probably not but I tried this on instinct but no difference, unfortunately.
weazie said:
Try also Windows Powershell.
Click to expand...
Click to collapse
Just tried this, unfortunately no difference.
weazie said:
Other than that, I can't think of anything right now. Many people seem to have had this problem in older moto phones, but I didn't find a solution. Some user mentioned in Youtube comments that "this problem can be solved by jtag software, replacing bootloader" altogether. But sounds like a drastic solution.
Click to expand...
Click to collapse
Thanks for scratching the old noggin for me.
Personally I'm unfamiliar with JTAG other than just seeing the acronym here and there. So would be an even more drastic solution for me ?
I was wondering if it would potentially have anything to do with me disabling some of the Moto apps. Doesn't seem likely given it's fastboot mode I'm writing in, rather than full blown Android.
jandroidian said:
I was wondering if it would potentially have anything to do with me disabling some of the Moto apps.
Click to expand...
Click to collapse
No, that doesn't affect the thing you're trying to do.
Thought I had a handle on a possible solution:
- Remove a universal ADB driver (clockworkmod) I had installed from way back in the day
- Remove a Google generic driver
- Reinstall (repair) Motorola drivers
- Reinstall ADB fastboot
- Reboot laptop
Nothing ??
Settings, System, Developer options, OEM unlocking (Allow the bootloader to be unlocked): On
Hmmmm
Is it possible this is something to do with the phone's regional designation? Maybe Motorola do not allow unlocking in my region.
Or perhaps it's something to do with the latest software. I did update the phone. Silly me, I still feel updates are often good for security and forget how often features get corrupted or removed these days.
jandroidian said:
Thought I had a handle on a possible solution:
- Remove a universal ADB driver (clockworkmod) I had installed from way back in the day
- Remove a Google generic driver
- Reinstall (repair) Motorola drivers
- Reinstall ADB fastboot
- Reboot laptop
Nothing ??
Click to expand...
Click to collapse
You are on the right track here. Clean out everything from device manager that could possibly conflict, begin from a clean slate (including SDK, adb, fastboot installation) and follow @Xplorer4x4's instructions to the letter. I know it's frustrating, but if that doesn't helplet's think of other solutions. By the way, there are two methods to install the Moto Drivers. One seems to install just the driver (v.6.40 for me) and the other the Moto Device Manager (2.5.4). I did install just the driver.
weazie said:
You are on the right track here. Clean out everything from device manager that could possibly conflict, begin from a clean slate (including SDK, adb, fastboot installation) and follow @Xplorer4x4's instructions to the letter. I know it's frustrating, but if that doesn't helplet's think of other solutions. By the way, there are two methods to install the Moto Drivers. One seems to install just the driver (v.6.40 for me) and the other the Moto Device Manager (2.5.4). I did install just the driver.
Click to expand...
Click to collapse
Thanks for your support. Again, thought I might have had a handle on it: USB debugging was off. Enabled it, no difference.
Back to the history a little (not in chronological order):
- Removed Universal ADB driver:
- Drivers came from here:
https://motorolausbdriver.com/wp-content/uploads/Motorola_Mobile_Drivers_v6.4.0.zip
I used the 64 bit version, not the 32.
- ADB and fastboot installer from here:
https://raw.githubusercontent.com/h...ster/versions/adb_fastboot_installer-1.2s.exe
When I installed / ran Motorola Device Manager, I expected some visible GUI software but I guess I must have had the wrong expectations because all it has ever done is run one single dialog that checks for newer software for the phone and fails. I posted that in a different thread.
Aside from not starting from a clean Windows install, I think I did follow Explorer's method. But I'm not perfect though neither is Motorola, seemingly
I guess I'll uninstall the Motorola stuff and try to start from a cleaner Windows install. Hell, maybe even starting in Safe Mode might be easier.
jandroidian said:
I guess I'll uninstall the Motorola stuff and try to start from a cleaner Windows install. Hell, maybe even starting in Safe Mode might be easier.
Click to expand...
Click to collapse
Yes You're doing it exactly like I was. Hmm.
weazie said:
Yes You're doing it exactly like I was. Hmm.
Click to expand...
Click to collapse
Well, the plot sickens, it seems.
Yet again, thought I was possibly on to a solution. Found these:
Previous / temporary phones there. Uninstall those devices and surely I'm right? Nope.
Then, re-installed the 64 bit drivers. Surely that will take care of these:
Nope
Now I'm in this exact situation that the uninstalling of Motorola Device Manager 2.5.4 warned me about:
So it would see that perhaps the Motorola Device Manager, which I have not re-installed, is actually needed for drivers. I'm not even convinced the files in this zip:
https://motorolausbdriver.com/wp-content/uploads/Motorola_Mobile_Drivers_v6.4.0.zip
are actually legit at all. I decompressed the 64 bit MSI file and it doesn't look like any driver files I've seen before. No .inf files for one thing.
jandroidian said:
So it would see that perhaps the Motorola Device Manager, which I have not re-installed, is actually needed for drivers.
Click to expand...
Click to collapse
I think it is not needed as I don't have it installed. What's peculiar is that I probably did the same installation as you, but my device tree looks like this:
And I don't remember ever installing LeEco device drivers? Now I'm just confusing You more.
weazie said:
I think it is not needed as I don't have it installed. What's peculiar is that I probably did the same installation as you, but my device tree looks like this:
And I don't remember ever installing LeEco device drivers? Now I'm just confusing You more.
Click to expand...
Click to collapse
Well, it seemed to take an reboot, and installing the Motorola Device Manager (not the other drivers) but I appear to have gone another 2 steps forward and one back.
Now have that but still fastboot oem get_unlock_data hangs
Need to head to bed now (forgot to post, just previewed, last night!). Maybe I will have better luck tomorrow.
Thanks for your kind assistance!
Not sure if it's lacking drivers (and perhaps a reboot) but I've gone from three "Moto g(6) plus" devices listed in Other devices, with yellow exclamation symbols, to the same with question mark symbols.
In both cases the phone is not accessible during general windows use
Will have to keep researching about 4 to 6 hours from now.
UPDATE: re-installing Motorola Device Manager fixed the lack of files access.
I am a bit confused at what your problem is. Not sure fastboot has a verbose switch. I've never had a reason to try.
If everything works now leave as is. If you ha e issues start off by removing all drivers for Moto, and remove adb and fastboot too. Then reboot computer. Install just moto dtivers(moto manager is for older phones and Usless to us other than the drivers) and adb/fastboot. Reboot computer. Now connect phone. Then do what you need to do.
Sent from my Moto G6 Plus using XDA Labs
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.