Related
As posted here:
http://forum.xda-developers.com/showthread.php?t=305940&page=17
there are some of us getting issues with Activesync possibly being caused by some sort of incompatibilities with USB handling/drivers with certain motherboards.
In my case, it prevented installation of Dutty's WM6 Rom, amongst others, but Black 2.5 and 3.0 loaders, didn't have the issues (hanging at part one or part two of the tri colour bootloader, only going part way through the flash and then hanging, only then able to get as far as tri colour, etc, etc).
Chipset of this motherboard is VIA 890, drivers are:
Ding ding!! Ahhhhhhhhhhhhhh, even though I put the latest VIA drivers into this thing, they don't seem to have taken - the default Microsoft installation drivers are still there - this could be the problem.
Chasing up new drivers and will report if these take ok.
ETA: Nope, won't take the drivers. Just answered what dad is getting for his birthday anyway, hehe.
if you really think that this is problem of drivers, try manuall installation of drivers. extract via 4 in one, and then choose to manuall update of each necessary compoment in device manager. choose *.inf file according to component, you actually installing.
I did not follow this thread - http://forum.xda-developers.com/showthread.php?t=305940&page=17 - but there is a few know problems with USB, like wrong drivers, wrong connection, using front USB on computer case (which is very often baadly shielded), or cables from usb front panel is too long and without ferrit ring etc...
you can also try to disable all other unnecesary devices in bios, to free some IRQ (it is common, that USB and VGA or SND have the same IRQ at the same time)...
Ribbit said:
As posted here:
http://forum.xda-developers.com/showthread.php?t=305940&page=17
there are some of us getting issues with Activesync possibly being caused by some sort of incompatibilities with USB handling/drivers with certain motherboards.
In my case, it prevented installation of Dutty's WM6 Rom, amongst others, but Black 2.5 and 3.0 loaders, didn't have the issues (hanging at part one or part two of the tri colour bootloader, only going part way through the flash and then hanging, only then able to get as far as tri colour, etc, etc).
Chipset of this motherboard is VIA 890, drivers are:
Ding ding!! Ahhhhhhhhhhhhhh, even though I put the latest VIA drivers into this thing, they don't seem to have taken - the default Microsoft installation drivers are still there - this could be the problem.
Chasing up new drivers and will report if these take ok.
ETA: Nope, won't take the drivers. Just answered what dad is getting for his birthday anyway, hehe.
Click to expand...
Click to collapse
o yeah, one more thing, USB 2.0 is installed automatically from Service Pack 2, so 4-In-One did not install usb, only support for AGP and IDE.
sinmae said:
o yeah, one more thing, USB 2.0 is installed automatically from Service Pack 2, so 4-In-One did not install usb, only support for AGP and IDE.
Click to expand...
Click to collapse
Aye I think that is the root of my particular problem.
But it's sorted dads birthday present out, so no worries.
ETA: strangely enough, it was a front USB port I first tried on its own with the unlocking, the unlocking sailed in, hehe.
Since I had a problem yesterday when trying to backup from ROM Manager, with the ongoing recovery Amon-Ra, I was the Desi who had no access to SD.
Following the tutorial to repair the brick USB, I got to read it again and from there I wanted to connect the PC and gave me a driver error, when it was installed with no problems so far, and I have root and s- off.
The fact is that I get an error installing the blututu driver "? and finally not just install the drivers so I have no access usb from windows.
Now the problem: I can not enable blututu from the configuration of Desi, I say start, I think a few seconds and then disconnect.
I tried to flash the radio, thinking that since it is the same chip that controls the wifi, 3g, blututuh, etc ... be solved and has not worked.
I do not know if you have something to do, but I notice that in settings has lost blututu device name. Do you know how I can fix this?
Moved to Q&A
Please do not post question threads in Development.
Post What Where:
General - general technical discussion items, news, anything else that does not fit into the other fora categories.
Q&A (Questions and Answers) - all questions, irrespective of type, get posted in here whether they be theme related, accessory related, technical, etc.
Accessories - any items to do with components and/or accessories relating to your device.
Rom Development - only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here.
Themes & Apps - anything to do directly with the development of themes and/or applications. Nothing else goes in here.
This is the latest release of my fix (June 14, 2011). This version addresses the Market ID and Moto Blur issue.
This version does not require the use of scripts on the phone. It uses ADB and sqlite3 (both are included in the zip file).
I created a new thread here because the older version was so full of bugs and comments about said bugs I figured it was time to start fresh, seeing how I am using a different method (the method I should have used to begin with) for this hack. Also, this should have been in development to begin with.
I have not had a chance to test the latest version, aside from verifying the awk command works as exptected. The rest is a strong educated guess, mixed with a re-tooling of it to just use Android Debug Bridge to do what I was having scripts do in the past. Should be much more reliable.
IF YOU DECIDE TO USE THESE INSTRUCTIONS: PLEASE, read through this page entirely from top to bottom at least once prior to doing anything. This way, if you are unsure on anything, you can ask the questions you need answers to. I am not liable for anybody messing up their phone because they didn't think to read the F'n manual prior to following these steps.
If you don't read this through completely before starting, and you brick your system, Don't come crying to me. I warned you.
This version makes it close to impossible to brick the system, but I left that bit in to cover my arse.
If you do not have the phone rooted, download the second zip file, and install the drivers found below:
Motorola Driver(install before you run the batch file)
You will need to enable USB Debugging:
On your phone,go to Settings->Applications->Development->Check "USB Debugging"
Latest version installs busybox for you, but if it doesn't, the script will pause for you to check, and tell you how to quit out of my script before proceding. If you have issues with that, let me know. I haven't tested this version, but by all accounts, it should be more reliable than my previous iterations, with the plus side of not having to purchase an app.
I have not tested it, so you may still need to tell it to install, but it should install the apk.
1. Download the attachment located in this post.
Unzip to a folder on your desktop.
PLUG IN YOUR PHONE NOW!!!
Double click on the batch file ("enable_unknown_sources.bat"). You may have to run as administrator, but I don't think so. Built on Windows XP (I'm a linux guy who wrote this at work in a couple minutes)
When it prompts for you to OK the super user for "unknown", look at your phone. It should have a prompt. If not, it may be ok. We will see....
once your phone has rebooted, you phone will have "unknown sources" enabled already. Don't worry about rebooting. The batch file did that for you.
Quite a bit less work than before. Good news: it's done! never to worry about it again...unless you upgrade....
DISCLAIMER:
DO NOT FOLLOW ANY OF MY STEPS IF YOU ARE UNSURE OF WHAT YOU ARE DOING! I have done my best to ensure that the instructions are accurate, but I made mistakes in the first revision, so who's to say that I didn't miss something this go 'round as well? If you decide to follow this walk-through, your actions are an agreement to not hold me liable if your phone becomes a pretty brick. I am not responsible for what you do with this information. If you have no idea how to do any portion of these instructions, you can either walk away (best idea), or ask for help here.
I am also not the 2nd shooter on the grassy knoll, nor am I the cause of all your woes throughout life. I always wanted to say that in a disclaimer.
Thanks to Vahnyyz for reminding me that I forgot to have you enable USB Debugging.
IF YOU HAVE PROBLEMS:
Have you installed the Motorola Drivers?
Do you have Debugging enabled?
If the answer to the 2 questions above are "yes, damnit! Give me a good answer, and stop wasting my time with these stupid questions", then you will need to tell me at what point the scripts fail. I will look into the problem as fast as I can.
so I tried the program you put on and everything because I haven't been able to root my phone as of yet, but the file I downloaded that included rooting did not work, everytime I ran the application it stated that "Device Not Found" and my phone is connected through USB at the moment.
Forgot a part
Thanks for letting me know about your issue. You need to do the following:
Ensure you have installed the drivers on you computer
Ensure USB Debugging is turned on
To enable USB Debugging, (on your phone...duh) go to Settings->Applications->Development->Check "USB Debugging"
as soon as I run the. bat file, command screen tells me to make sure that busybox is installed, which it is, to unplug phone, go to, busybox and install. Wife's phone is already rooted, once I hit next, "unknown" will pop up on the screen for a second and then....nothing.
Need to fix that to state "....after you ensure busybox is installed, plug phone back in"
Just plug the phone back up prior to proceding
Sent from my GT-I9000 using XDA App
How is the no blur version coming along....anxiously waiting for that!
JBallin4life27 said:
How is the no blur version coming along....anxiously waiting for that!
Click to expand...
Click to collapse
I am running into a problem I believe is caused by an older version of clockworkmod. I am trying to see if I can get a newer version running.
The issue:
It appears that the update file I generate is incompatable with the updater built into the version of ClockWorkMod I am running. Anybody have a newer build of the CWM I can use for testing?
jonsjava said:
I am running into a problem I believe is caused by an older version of clockworkmod. I am trying to see if I can get a newer version running.
The issue:
It appears that the update file I generate is incompatable with the updater built into the version of ClockWorkMod I am running. Anybody have a newer build of the CWM I can use for testing?
Click to expand...
Click to collapse
I had CM6 running on my motorola backflip and still have all the files saved on my computer...would it be in there somewhere and would that be useful to you?
JBallin4life27 said:
I had CM6 running on my motorola backflip and still have all the files saved on my computer...would it be in there somewhere and would that be useful to you?
Click to expand...
Click to collapse
I'm needing the second stage recovery file to make ClockWorkMod something newer than 2.x.x Needing to have it somewhere in the neighborhood of 3.x
jonsjava said:
I'm needing the second stage recovery file to make ClockWorkMod something newer than 2.x.x Needing to have it somewhere in the neighborhood of 3.x
Click to expand...
Click to collapse
Yea lol...no idea what that all means...sorry i'm not any help
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Calgary84 said:
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Click to expand...
Click to collapse
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
tnsmani said:
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
Click to expand...
Click to collapse
I was afraid of that..... is there a way to test a given hardware component?
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
acetone802000 said:
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
Click to expand...
Click to collapse
Indeed I have, dozens of times between the full and mini versions. I've even gone as far as running the toolkits featuring MSMDownloadTool v4.0 to see if it achieved different results (it did not). The mini tool would finish doing its thing (turned the text green upon completion),but I would face varying partitions not being flashed correctly. The full version completes and does not have these varying partitions missing, but the device would then be either stuck in a bootloop where it will eventually reboot itself, or would hang indefinitely on the "swirling dots" loading screen. I tried the remedy of deleting cache in recovery, but this did not help.
deleted
***UPDATE*** - As I mentioned in this thread earlier, I noticed a discrepancy between the variant type listed on my actual device and the variant type returned when queried via fastboot. This got me thinking, and to make a long story somewhat shorter, I found that while most stock Oxygen images I attempt to sideload onto the device fail (at precisely 47%, oddly), I was able to sideload two different Hydrogen images without any resistance at all. I'm guessing something to do with the eMMC vs UFS file storage systems and how each OS uses them.
So I got Hydrogen flashed onto my my device. Smooth sailing, right? Afraid not. Despite fastboot's output clearly stating it was a successful transfer, and the stock recovery on the device echoing this, I still cannot get the OS to load. Now i' stuck with the loading screen hanging indefinitely prior to animation occurring, so basically the static ONEPLUS logo. Factory resets and cache wipes have done nothing to help the situation along. Conventional wisdom from the threads here seem to say using the MSMTool is the right answer..... and thus the circle of frustration is complete with me arriving back where I started. Does anybody have another suggestion I can try out? Still can't flash/boot to TWRP, unlock bootloader, or access Android to activate USB Debug/OEM Unlock either btw.
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
voodooline said:
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
Click to expand...
Click to collapse
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
150208 said:
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
Click to expand...
Click to collapse
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
voodooline said:
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
Click to expand...
Click to collapse
Magnificent, bro.
You're a truly genius.
Looking for some help. I have a ZTE MF833V that works great w/my Mint (tmobile) SIM when plugged into a Win10 PC. I'm having trouble getting it recognized on my IB80A4AL (octa core 64GB android 10). I've tried a few things, and where I am at presently is I have tried to root the head unit. SuperSU reports its not rooted, but after following these instructions here:
PX5 MTCD/E Head Unit Discussion Thread [Rockchip PX5 A53 | Android 8.0 | 2/4GB RAM]
This thread is intended on collect the information about Android 8 (Oreo) over the Android units that features: PX5 Platform Core Board MTCD/MTCE MCU Type The information below is a copy of the same thread for Android 6 by aarick Post 2...
forum.xda-developers.com
I was able to get connected via ADB over wifi, copy the files, and change ownership of the directories listed. PPP widget 3 pops up and says it sees the ZTE modem and asks if I want to use it, and no longer says I need root access, but it errors out with "could not determine system device path for modem" in the logs. I'm outdated in regards to rooting procedures, what is/isn't possible/working in the current android arena, so I apologize for the spotty post. Just hoping someone might guide me to a link, or have some suggestions on the right direction to go to get this USB modem to be detected as a 4g connection device. I also tried kingoroot with no luck. I thought if I could get TWRP loaded, maybe I could try SuperSU or Magisk, but figured I better ask for guidance at this point before I brick something.
Thanks for any help.
Been reading some more, appears maybe I have missed a step, and wound up down a rabbit hole:
Working REAL(!) 3g / 4g USB Modem-Sticks on PX5/PX3 Units
UPDATE 17th sep 2019: PROJECT CLOSED, see post #147 . Okay, we´ve got many threads about "3g/4g" USB-sticks für Car Androids powerd by PX3/PX5. BUT: most posts describe WiFi-Sticks and Sticks recognized as ethernet connection or ´WiFi-Hotspot...
forum.xda-developers.com
Going to play around with changing the connection mode in DC unlocker and see what happens.
Making progress. Plugging in the modem now, the head unit is recognized and I get the little "cell connectivity" icon. Only issue now is that it is staying solid blue, indicating its connected to the LTE network, but not transferring any data. Any idea what I might be missing at this point?
Thanks
I have one with WiFi on it, it only takes power through USB.. It worked fine for me, however I had the same issue as you - it wouldn't download anything.
There's a setting in Android somewhere which say that it won't download anything on WiFi or 3/4G etc. I just set it to "Always allow" or similar..
I can go look for the exact setting if you need, but that should keep you busy for a while, looking for it .
This might be what I did: https://helpdeskgeek.com/help-desk/how-to-resolve-the-play-store-download-pending-issue/