Just got a a used Droid X2 and accidentally updated to 2.3.5/1.3.418 now trying to follow these instructions and root it:
[How To] Root DX2 2.3.5/1.3.418 magic md5 method
I installed MotorolaDeviceManager_2.3.9.exe from here:
MY MOTO CARE
Hooked-up the phone which was factory reset, set 'USB debugging', and ran the batch files trying USB connection in both 'PC Mode' & 'Charge Only' and keep getting these errors:
Code:
error: more than one device and emulator
error: device offline
The batch stops at '---Reboot Bootloader---' and nothing happens. I've tried following the instructions to hold volume up while turning off and on, but the phone just hangs at 'Starting RSD protocol support' and the batch stops at '< waiting for device >'.
I've even tried uninstalling and re-installing the Motorola drivers and going through everything again, but no change. Any help?
Thanks!
I just downgraded to Android version 2.3.4/1.3.380 with RSDLite and tried the VooDoo method, but Pete's Motorola Root Tools failed.
The Root Tools program was able to detect the device initially, but none of the commands seemed to have any effect and when it tried to reboot the device nothing happened; it goes through the rest of the steps and then indicates that it failed.
I'm running Windows 7 and even tried a system restore then re-installing the drivers, but no change. When I check the device manager there are no unknown devices or anything like that.
Got it!
Finally tracked down the solution to the error 'more than one device and emulator'
Had to use adb.exe that came in Pete's Root Tools to run the command 'kill-server' in the command window:
Code:
adb.exe kill-server
When I checked
Code:
adb.exe devices
initially there were multiple devices listed, somehow the phone was not disengaging when I was plugging and unplugging it. Running kill-server reset the list so that running the root application could finally identify the phone correctly.
If anybody knows why this was happening and how to prevent it please let me know.
Now I can finally go on to flashing a ROM!
jhsu888 said:
Got it!
Finally tracked down the solution to the error 'more than one device and emulator'
Had to use adb.exe that came in Pete's Root Tools to run the command 'kill-server' in the command window:
Code:
adb.exe kill-server
When I checked
Code:
adb.exe devices
initially there were multiple devices listed, somehow the phone was not disengaging when I was plugging and unplugging it. Running kill-server reset the list so that running the root application could finally identify the phone correctly.
If anybody knows why this was happening and how to prevent it please let me know.
Now I can finally go on to flashing a ROM!
Click to expand...
Click to collapse
Let me know what rom you stick with, I just ordered one 4 days ago and should be getting it today. I'm torn between eclipse(on gingerbread) and Cyanogenmod 10(jelly bean) (i want to be able to call, text and use data reliably, and I like being on the newest version of stuff)
DQEight said:
Let me know what rom you stick with, I just ordered one 4 days ago and should be getting it today. I'm torn between eclipse(on gingerbread) and Cyanogenmod 10(jelly bean) (i want to be able to call, text and use data reliably, and I like being on the newest version of stuff)
Click to expand...
Click to collapse
I actually haven't bothered trying CM10, after I got everything running smooth with Eclipse I just left it at that. I can say that I haven't run into a single issue with Eclipse and I've been using it pretty heavily installing/uninstalling apps and trying all the components including the camera, wifi, led lights, sms and calling - all working solid.
A little off topic, but I also installed a home launcher app and after trying GO Launcher and Holo, I found ADW to have the easiest way for me to manage all the apps in groups and still be highly customizable. GO launcher I found buggy and Holo looked great out of the box, but felt a little limited.
I would also suggest getting the Widget Locker app, it's paid, but worth it to be able to customize the lock screen and get to things like the camera, flashlight, dialer etc quickly from the lock screen. I tried a few of the free ones for that and they were buggy or gave me a flash of the old lock screen, Widget Locker works pretty seamlessly.
Enjoy it!
I am a first owner DX2 owner running CM7. Most of the original owners have all moved on and upgraded. I am waiting until my contract ends to ditch VZW and go to prepaid to save money. But I digress.
You have to be on 2.3.4 to install CM7. This is by far my favorite rom, second to eclipse. It is faster and smoother than eclipse. Eclipse starts to slow down over time.
CM10 also has to be installed from 2.3.4. It's fun to play around with, but at the end of day it is too glitchy and not functionable enough due to the bootloader being locked. So in my opinion, it's best to stick with the gb roms.
Sent from my MB870 using Tapatalk 2
Juice3250 said:
I am a first owner DX2 owner running CM7. Most of the original owners have all moved on and upgraded. I am waiting until my contract ends to ditch VZW and go to prepaid to save money. But I digress.
You have to be on 2.3.4 to install CM7. This is by far my favorite rom, second to eclipse. It is faster and smoother than eclipse. Eclipse starts to slow down over time.
CM10 also has to be installed from 2.3.4. It's fun to play around with, but at the end of day it is too glitchy and not functionable enough due to the bootloader being locked. So in my opinion, it's best to stick with the gb roms.
Sent from my MB870 using Tapatalk 2
Click to expand...
Click to collapse
Cm9 wasn't too bad. Its quite a bit more stable then cm10 and now that time has past more apps actually work on it. Give it a try and see how you like it. I couldn't stand the delayed text issue that appears on cm7
Sent from my SCH-I535 using xda premium
Related
I installed faux123's kernel for Gingerbread this morning (I'm running kennethpenn's beta #4.5). Since then, wake on volume only works within the first few seconds after turning off the screen. Because I used WidgetLocker's Easy Wake before, I never did the android.policy.jar tweak. Since it was no longer working, I tried the tweak, but it changed nothing.
Also, I had to reboot a few times to get the new Swype working, and about every other time, my widgets would be lost in both LauncherPro and WidgetLocker.
I'm posting this here instead of in the kernel thread (http://forum.xda-developers.com/showthread.php?t=1156040) because I don't have enough posts yet.
Solution to your problem - Intro to mine
I noticed similar issues with my phone and found it to be an issue with pudding (the unlockable bootloader that u flashed to your phone). This problem was pretty much corrected when I used an older version of pudding available here:
briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Sorry, couldn't put the actual address because I am a new member
Click the "Unlock SBF File" link. Flash it with RSD lite to replace the old pudding.
It worked for me pretty much except that ADB started to have issues. Any time that I try to debug an APP i made through ADB, i get a connection refused error.
Sounds like this kernel needs some refinement. Anyways, hope this helps.
Cheers!
BE CAREFUL WHEN USING RSD LITE. YOU HAVE THE POTENTIAL TO REALLY MESS UP YOUR PHONE.
Hello,
What started out as a spontaneous root adventure turned into a nightmare after I messed with one too many options in Titanium Backup. Fortunately I have a full app backup, so if I can get my phone back to working condition it will be good as new.
Phone stats: Droid Razr M (XT907) running 4.1.2 at time of initial crash
MY PROBLEM:
After restoring and wiping (several times) I am stuck with this scenario. I can boot the phone just fine, and I can get through the new phone setup app, but the moment I attempt to exit the setup app I get this message "Sorry: Setup has stopped working". Setup closes and I am left with a blank desktop, only outlying system UI visible and responsive. I am able to get to settings though a conveniently placed notification, but that's the only way. I am able to access all settings and developer options, which is good, but when I go to look at the apps I notice a lot of apps (not all) are coming up as 0.00B of space. When I reboot the phone I get stuck in a "System Update: Loading Apps" cycle that never ends until I hard restart my phone.
WHAT I HAVE TRIED:
* Using RSD Lite to flash the factory default kernel or whatever: FAILED, can't get past the first out of 19 steps
* Using adb and mfastboot to flash the system image manually: FAILED, doesn't seem to want to install the boot or system images
* Using Droid RAZR M Utility v1.20: FAILED, same failure as adb.
* Downloaded many different drivers, programs, roms, zips, whatever. If you want me to try something again, I probably have the files for it.
I have basically given up trying to figure it out myself at this point, stayed up all last night searching for solutions (I'm a computer science student, who can blame me?) to no avail. It's up to you guys to help me save my phone!
SOLVED
The problem was that I was trying to flash an old firmware version. Got the updated version from a handy developer site with all the phones listed.
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
JayWulf said:
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
Click to expand...
Click to collapse
You need to start over from scratch
post your fastboot getvar all (minus you serial.no and IMEI)
Most likely your using AT&T so if you have s-off you can flash these two and get back two stock. take the OTA Update then re flash recovery and root.
flash this first
http://fs1.d-h.st/download/00101/a1w/4.18.502.7 Custom Firmware.zip
fastboot oem rebootRUU
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot reboot bootloader
now stay on the bootloader
and run this RUU from your PC > http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Take the Over the air update and your all set to start rooting again.
clsA said:
post your fastboot getvar all (minus you serial.no and IMEI)
Click to expand...
Click to collapse
What is this, and how do I do it?
JayWulf said:
What is this, and how do I do it?
Click to expand...
Click to collapse
go to the folder where fastboot and adb are
open a command window (right click / command prompt here)
with the phone plugged into the PC
Type fastboot getvar all
it will output all the specs for your phone
remove the serial no and IMEI when posting it
what if your s-on
I'm having all the exact same problems except I'm 4.3 and s-on. Help please!
Gonna kinda bump this thread a bit because I've got another question - what about the "full unroot" option within SuperSU? Will this help the situation at all, or make it worse?
Hi
for last 6 or 7 month whenever i connect my razr to wifi or 3g it either goes unresponsive or it will reboot few times, and then it will work but it is slow.
I have cleared cache from boot menu, and did factory reset too, but still it is doing same
i have disabled auto-synch, auto updates and forecast app too.
gregoresamsa said:
Hi
for last 6 or 7 month whenever i connect my razr to wifi or 3g it either goes unresponsive or it will reboot few times, and then it will work but it is slow.
I have cleared cache from boot menu, and did factory reset too, but still it is doing same
i have disabled auto-synch, auto updates and forecast app too.
Click to expand...
Click to collapse
I would highly suggest starting over and installing CyanogenMod 11. It's a confusing process but eventually you'll get it.
Start with this video. I'm assuming you're on 4.1.2., as that's what caused my RAZR to slow down too. So don't use the tools he has in the video. Use these tools instead, but make sure that you follow the YouTube instructions and get the USB connection added properly. This method successfully preps the phone for later steps.
Then use these instructions to get the phone rooted and prepped for installation.
Razr's Edge is used to root the phone. Make sure to check if the phone is recognized by Windows by using adb devices and seeing if the phone is connected.
Razr's Edge may say it didn't install properly, like it did for me, but in my case it had successfully placed the files on the phone's internal storage.
Finally, follow the instructions to install safestrap recovery and CyanogenMod.
Let me know if I can help. I have been trying for the past couple years to get the XT910 rooted and install CM11 and I finally got it.
stardestroyer001 said:
I would highly suggest starting over and installing CyanogenMod 11. It's a confusing process but eventually you'll get it.
Start with this video. I'm assuming you're on 4.1.2., as that's what caused my RAZR to slow down too. So don't use the tools he has in the video. Use these tools instead, but make sure that you follow the YouTube instructions and get the USB connection added properly. This method successfully preps the phone for later steps.
Then use these instructions to get the phone rooted and prepped for installation.
Razr's Edge is used to root the phone. Make sure to check if the phone is recognized by Windows by using adb devices and seeing if the phone is connected.
Razr's Edge may say it didn't install properly, like it did for me, but in my case it had successfully placed the files on the phone's internal storage.
Finally, follow the instructions to install safestrap recovery and CyanogenMod.
Let me know if I can help. I have been trying for the past couple years to get the XT910 rooted and install CM11 and I finally got it.
Click to expand...
Click to collapse
Hi thank you
mine is actually 4.0.4 rooted version, with eunonefigretail, there was no upgrade possible for me after that version, i tried to put im version 4.1.2 but on that one i was never able to get any wifi or 3g and there was more problems so i got back to 4.0.4
I will definitely try this
[email protected],
just bought myself an Ulefone T1 from aliexpress and I am wondering if there is any lineageos development out there for this phone? Is anybody planning to develop for this?
cheers
JohnnyT
Stay tunned. The phone is new and development will yet. Dont worry is a great phone and Ulefone is better than yesterday.
https://www.needrom.com/category/ulefone/t1-ulefone/
It will hardly receive official updates, let alone custom ROMs (same fate as the 96% of MediaTek devices out there).
any update . i just bought this phone from banggood. my asus zenfone 3 wifi is failing. so needed something to fill the gap
Finally received my t1 after 11 weeks of waiting!!
Everything works fine apart from the battery usage which is a round 10% per hour on standby with no usage!!
FOLLOW-UP
Following lots of research found that Whatsapp was still trying to verify the phone thru SMS and was draining the battery. Uninstalled and re-installed Whatsapp and verified by manually entering SMS pin.
Now appears to running okay at just over 2% per hour battery drain with bluetooth and GPS set on.
i think i got a thud. reboots when connected to 5g wifi and sometimes when doing stuff on the phone. what a POS phone. never again ulefone!
I am very happy with my T1. High performance, loads of RAM and storage in a decent looking dual SIM package for a very reasonable price tag. First official OTA update yesterday. Also there are rumors about 8.0 upgrade till end of the year.
JohnnyT
Alicklee said:
i think i got a thud. reboots when connected to 5g wifi and sometimes when doing stuff on the phone. what a POS phone. never again ulefone!
Click to expand...
Click to collapse
Mine does occasional reboot. I think its when my mail app is in 'recent apps'. When I clear recent apps. The phone seems more stable, but it's early days.
If anyone finds a fix, please post to the group.
I had my first ota update so that was a plus although it didn't solve the rebooting or activate the 'so called' second camera.
Pickles871 said:
Mine does occasional reboot. I think its when my mail app is in 'recent apps'. When I clear recent apps. The phone seems more stable, but it's early days.
If anyone finds a fix, please post to the group.
I had my first ota update so that was a plus although it didn't solve the rebooting or activate the 'so called' second camera.
Click to expand...
Click to collapse
Do you have yours rooted and your bootloader unlocked? I am getting the update prompt but being unlocked and rooted I'm not sure it will take the update. Some phones tend to brick. Also all of a sudden I am having an issue with "android process.media has stopped" Can't figure out what's causing it but since it started the device has become quite laggy
Mine is not rooted. Its still as out of the box. I have rooted previous phones but find that some of the apps I want to use won't run on rooted phones, like certain banking apps. I don't know if the restarts are an Android 7.0 symptom or hardware/software based. There are so many different views on this it's almost impossible to figure out the causes. For me I keep trying different app and phone settings in the hope that something eventually solves the issue. Maybe a future firmware update will sort it. I live in hope (but don't hold your breath). More likely a new phone will be acquired at some point!
by any chance any of you have gps problems in waze or maps????
Pickles871 said:
Mine is not rooted. Its still as out of the box. I have rooted previous phones but find that some of the apps I want to use won't run on rooted phones, like certain banking apps. I don't know if the restarts are an Android 7.0 symptom or hardware/software based. There are so many different views on this it's almost impossible to figure out the causes. For me I keep trying different app and phone settings in the hope that something eventually solves the issue. Maybe a future firmware update will sort it. I live in hope (but don't hold your breath). More likely a new phone will be acquired at some point!
Click to expand...
Click to collapse
you need to proper root with magisk. and only use magisk, not other super user apps.
with magisk hide you can cheat banking apps or any app thinking the phone is not rooted.
nieXas said:
you need to proper root with magisk. and only use magisk, not other super user apps.
with magisk hide you can cheat banking apps or any app thinking the phone is not rooted.
Click to expand...
Click to collapse
Thats useful to know. Many thanks
Made Lineage 14.1 work on my Ulefone T1 (adb shell hacked)
Hi everyone,
i've been digging around for the last few weeks on my T1 and now i've finally made it boot. I dont know exactly what is working and what not but i can tell WLAN is NOT working for now! The kernel repo at my github was not working so i used the stock one. You may download it as well as the TWRP recovery i made alongside the ROM. But you need to wipe /data partition so all user data is lost in the process. Also while TWRP needs a reboot after wiping /data step 2 & 3 may need to be repeated once. For now i was not able to flash and boot the recovery (working on it) but it can be booted into as follows (when booted into the stock system):
UPDATE: Made it work - it's booting without hacking via ADB-Shell. The parts marked --- obsolete --- are not needed any more.
1.) Disable OEM-Lock in Developer-Options (google if necessary how to do that)
2.) Reboot and keep the upper volume button button pressed until it booted into recovery. If the "no command" screen is displayed, press the power and upper volume button together once again and you shuld reside in the stock recovery. Use it to reboot into fastboot (bootloader).
3.) In fastboot mode, while beeing in the same folder as the downloaded files, type the following:
Code:
fastboot boot recovery.img
4.) Wait for TWRP to boot up and enter the following (within the same folder):
Code:
adb push lineage-14.1-*-UNOFFICIAL-t1.zip /sdcard/
5.) Finally you may flash the Lineage zip file in TWRP (if you have wiped your /data partition at least i needed to)
----------------------------------- obsolete -----------------------------------
6.) Let it reboot into system and while displaying the Linage bootanimation (for now) i had to execute a few commands on adb shell. So, with adb installed, you need to enter the following commands in a common linux/windows shell:
adb shell /vendor/bin/nvram_daemon &
adb shell /system/bin/nvram_proximity &
adb shell /vendor/bin/nvram_agent_binder &
adb shell /system/bin/agoldnvram &
adb shell /system/bin/audioserver &
Click to expand...
Click to collapse
I'm not sure if they are all needed but afterwards my T1 bootet up correcty (more or less). Unfortunately a few drivers are missing as it seems while WLAN is not working for now.
http://d0ndroid.janeiskla.de/lineage-14.1-20180928-UNOFFICIAL-t1.zip
and the recovery
http://d0ndroid.janeiskla.de/recovery.img.
----------------------------------- obsolete -----------------------------------
After fixing another few things the only remaining things i found not working are fingerprint & RIL but I'm looking into that right now. The current builds will always be uploaded to:
http://d0ndroid.janeiskla.de/
The sources i used besides the default Lineage ones are on github:
https://github.com/d0n?tab=repositories
Have fun! And let me know if you make progress on your own
Greez,
d0n
Hi d0n22, are you still working with this rom?