Related
Okay I have searched and searched through these forums through and through and there is no possible way the root a Droid 2 Global. I have tried all the ways listed here Pete's way the One Click and the Superone Click and I tried Z4root and that didn't work either! Is there a new way to do this???(When I had my HTC Eris that was unrootable too.) I think Im gonna give up and on my next upgrade I'll probably just get an iPhone 4s or something, because any phone I touch will before outdated and unrootable and unable to flash any of the cool custom roms and play emulators and crap. I'll just an iPhone 4s and talk to siri.
Thanks anyway for all the help guys and thanks developer for all your hard work!!!
-Mars
you're doing something wrong
edit: did you enable usb debugging?
how far did you get?
and miui ics is a cool rom
thousands have rooted their global
at least hundreds anyways
Which stock version are you on? Froyo, GB...
War-Rasta said:
Which stock version are you on? Froyo, GB...
Click to expand...
Click to collapse
Pete's root is suppose to work on froyo too
Sent from my DROID2 GLOBAL using xda premium
Z4root will NOT work on stock 2.3.3. I've been using a Droid 3 one click root tool for linux and it's been working without fail. I've noticed this tool also works on the regular D2. Z4root will only work with the original stock.
EDIT: As far as cool roms, I'm using MIUI ICS. You like ICS but don't want to spend 700 bucks for an off contract phone? That's right. Your D2G runs it just fine lol.
MIUI isn't really ICS. It's just bits and pieces of the framework.
Gasai Yuno said:
MIUI isn't really ICS. It's just bits and pieces of the framework.
Click to expand...
Click to collapse
Diced, mixed, or blended, it's still the best rom I've used
I am using Gingerbread.
System Version 4.5.608.A956
Android Version 2.3.3
What does the DROID3 One-Click Root script tell you? Any errors while you run it?
Gasai Yuno said:
What does the DROID3 One-Click Root script tell you? Any errors while you run it?
Click to expand...
Click to collapse
Nothing. Once it finds the phone and the rooting process begins it will say running expoit 1 of 3 (setting up symlink) and it will remain at the reboot screen forever!
my phone says:
Bootloader DO.11
Battery OK
OK to program
Transfer Mode:
USB
then nothing happens!
This time I got the "server not running" error!
Make sure your phone is set to PC mode with USB debugging on. I usually have to run the script twice. The first time it doesn't do anything. End it and start it again and it works for me every time.
Also, as far as MIUI ICS, it's technically android 2.3.7 but it's still ICS to me lol. It's enough like it to make me happy.
xero925 said:
Nothing. Once it finds the phone and the rooting process begins it will say running expoit 1 of 3 (setting up symlink) and it will remain at the reboot screen forever!
my phone says:
Bootloader D0.11
Battery OK
OK to program
Transfer Mode:
USB
then nothing happens!
Click to expand...
Click to collapse
Have you tried pulling the battery without unplugging the phone from the PC and closing the script's window?
So that it boots normally and continues.
Gasai Yuno said:
Have you tried pulling the battery without unplugging the phone from the PC and closing the script's window?
So that it boots normally and continues.
Click to expand...
Click to collapse
I'm gonna try that now! Standby...
Nope that didn't work! I didnt think was going to either!
I just tried the latest version of SuperOneClick and again with this screen on my phone:
my phone says:
Bootloader D0.11
Battery OK
OK to program
Transfer Mode:
USB
I'm starting to think somehow that this screen somehow not allowing me the further root my phone! With the SuperOneClick the program running and then immediately stopped responding!
Any ideas?
what is the latest version?
I thought you just need it in usb charge mode and have usb debugging on
edit: I don't see a SuperOneClick that works with GB
---------- Post added at 03:49 PM ---------- Previous post was at 03:18 PM ----------
xero925 said:
I just tried the latest version of SuperOneClick and again with this screen on my phone:
my phone says:
Bootloader D0.11
Battery OK
OK to program
Transfer Mode:
USB
I'm starting to think somehow that this screen somehow not allowing me the further root my phone! With the SuperOneClick the program running and then immediately stopped responding!
Any ideas?
Click to expand...
Click to collapse
try petes with a different computer
HTML:
http://www.psouza4.com/Droid3/
1. Make sure you have Motorola drivers installed.
2. Download and unzip 'MotorolaOneClickRoot_psouza4'
3. On your phone: Settings > Applications > Development > USB debugging(check box)
4. Plug phone into computer and select "Charge Only" mode
5. Navigate to 'MotorolaOneClickRoot_psouza4' folder and run 'MotorolaOneClickRoot.exe'
6. Now just follow the instructions in the command window and unlock the phone after each reboot.
For Windows XP users having trouble try this -> v7 .bat One Click
edit: are you trying to using a computer with usb 1.0?
if that doesn't work, maybe sbf
Hi,
i am definitely not an expert, in fact everything i know about android i learned from reading other people's threads but i managed to root my droid 2 global yesterday using superoneclick.
the first time i tried to run it the program froze up in the middle of the process and wouldn't do anything, including close. while i was trying to figure out how to fix i came across a post that said to start the program while usb debugging is off and then turn it on when it says waiting for device so i tried that and it actually worked. go figure.
i have no idea if it will work for you or not but i thought i would share in case you wanted to give it a try.
crazydz said:
Hi,
i am definitely not an expert, in fact everything i know about android i learned from reading other people's threads but i managed to root my droid 2 global yesterday using superoneclick.
the first time i tried to run it the program froze up in the middle of the process and wouldn't do anything, including close. while i was trying to figure out how to fix i came across a post that said to start the program while usb debugging is off and then turn it on when it says waiting for device so i tried that and it actually worked. go figure.
i have no idea if it will work for you or not but i thought i would share in case you wanted to give it a try.
Click to expand...
Click to collapse
Thank you!!!! That worked!!! I can confirm SuperOneClick v2.3.3 works on a D2G running 2.3.3!!!!
Im using Barnacle wireless tethering and gonna flash a custom rom later today!!
Thank you guys so much helping and I plan to donate and support you efforts here!!
the instructions are on the SuperOneClick v2.3.3 thread
http://forum.xda-developers.com/showthread.php?t=803682
Turn USB Debugging OFF
Click Root
When it says: Waiting for Device, Turn USB Debugging ON
It'll now run RATC
When it says: Starting ADB Server...
Turn USB Debugging OFF
Turn USB Debugging ON
Turn USB Debugging OFF
All BEFORE it says "Waiting for device..." again
Click to expand...
Click to collapse
I am trying to revert my HTC Evo Shift 4G, which is running android 2.3.4 to android 2.2. I have been able to successfully temp root it, but I've been getting stuck after that. I'm using these instructions. I wasn't sure what to do for step 4, until I found this (second reply, by the user "timlair") but when I attempted to follow his instructions, I received the following error message "adb: not found." Does anyone have any suggestions, or am I doing something wrong?
Thanks in advance
szvenig7 said:
I am trying to revert my HTC Evo Shift 4G, which is running android 2.3.4 to android 2.2. I have been able to successfully temp root it, but I've been getting stuck after that. I'm using these instructions. I wasn't sure what to do for step 4, until I found this (second reply, by the user "timlair") but when I attempted to follow his instructions, I received the following error message "adb: not found." Does anyone have any suggestions, or am I doing something wrong?
Thanks in advance
Click to expand...
Click to collapse
ADB.exe is a file on your local PC. When you do "adb shell" you are now running on the phone's shell. If you need to run linux commands on the phone you do so from within adb shell ($ or su prompt #). Once you're done, type "exit" (maybe twice if you're in the # prompt) and it will return you to your command prompt. You can then execute more adb commands like "adb push" or "adb reboot recovery".
Hope that helps! :good:
Hi I really need help can someone help me?
My Shift 4G is saying this when I try
Code:
./fastboot-mac oem get_identifier_token
it gives me this!
Code:
COMMAND ERROR!
Please help!!!!!!!!!
iLeoable said:
Hi I really need help can someone help me?
My Shift 4G is saying this when I try
Code:
./fastboot-mac oem get_identifier_token
it gives me this!
Code:
COMMAND ERROR!
Please help!!!!!!!!!
Click to expand...
Click to collapse
Try using THIS method to Root.
prboy1969 said:
Try using THIS method to Root.
Click to expand...
Click to collapse
Thanks! But I just figured out that I need to update my HBOOT!
iLeoable said:
Thanks! But I just figured out that I need to update my HBOOT!
Click to expand...
Click to collapse
Glad you got it sorted. I still love my Shift, miss it a lot sometimes.
I miss mine too. I loaned it to a college student while his wm crap phone was broken and he killed the display. Oh well I guess.
Chad The Pathfinder said:
I miss mine too. I loaned it to a college student while his wm crap phone was broken and he killed the display. Oh well I guess.
Click to expand...
Click to collapse
I'm actually trying to put one back together out of parts that I have left over. Almost have it done .
Every time I try to flash the OTA update, it first asks me if I want to install the untrusted zip, which doesn't make much sense, because why would an OTA be untrusted?
Then, during the installation, it aborts for some reason. After that it asks if I want to fix root.
I have no idea why any of this is happening, but I can't install the update because of it. What should I do?
Sent from my Nexus 5 using Tapatalk
There should be a reason in recovery why it failed. We'd need to know it before we can help
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
For me at least (I didn't start this thread), it fails because Roboto-Bold.ttf contains unexpected content.
I don't recall ever changing Roboto-Bold.ttf, so I have no idea what about it is unexpected.
CarpeNivem said:
For me at least (I didn't start this thread), it fails because Roboto-Bold.ttf contains unexpected content.
I don't recall ever changing Roboto-Bold.ttf, so I have no idea what about it is unexpected.
Click to expand...
Click to collapse
It's a non standard font installed by something. If you have anything non standard on your phone the ota will fail
Thank you. I understood that.
What I meant to say is, how do I correct it? Where can I find a copy of Roboto-Bold.ttf that the update will be "expecting"?
And then, if/when it complains about another file being unexpected, where did I find THAT? etc, etc.
CarpeNivem said:
Thank you. I understood that.
What I meant to say is, how do I correct it? Where can I find a copy of Roboto-Bold.ttf that the update will be "expecting"?
And then, if/when it complains about another file being unexpected, where did I find THAT? etc, etc.
Click to expand...
Click to collapse
You need to read this http://forum.xda-developers.com/showthread.php?p=47369234. Basically you need to flash the stock system.img
Those instructions include "attach phone to computer while phone is in fastboot mode".
However, when I do that, when I attach my phone to the computer while in fastboot mode, my Nexus 5 is NOT SHOWN when I type "adb devices" OR "fastboot devices".
When my phone is in recovery mode, and I type "adb devices", then it IS shown. Additionally, if my phone is fully booted up as normal, if I type "adb devices", it IS shown then too.
But if there are things which need to be done from the computer at the command prompt (and it seems that there are) while the phone is in fastboot mode, well, I cannot do those things, as my device doesn't seem to recognized at all while in that mode.
CarpeNivem said:
Those instructions include "attach phone to computer while phone is in fastboot mode".
However, when I do that, when I attach my phone to the computer while in fastboot mode, my Nexus 5 is NOT SHOWN when I type "adb devices" OR "fastboot devices".
When my phone is in recovery mode, and I type "adb devices", then it IS shown. Additionally, if my phone is fully booted up as normal, if I type "adb devices", it IS shown then too.
But if there are things which need to be done from the computer at the command prompt (and it seems that there are) while the phone is in fastboot mode, well, I cannot do those things, as my device doesn't seem to recognized at all while in that mode.
Click to expand...
Click to collapse
Google tool adb fastboot drivers xda. Use that to get the drivers working with fastboot
jd1639 said:
You need to read this http://forum.xda-developers.com/showthread.php?p=47369234. Basically you need to flash the stock system.img
Click to expand...
Click to collapse
Will that do anything to root access?
Sent from my Nexus 5 using Tapatalk
kehlan said:
Will that do anything to root access?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
After taking the ota you'll have to re-root
I think it's finally happening. I think I'm finally done. I'm successfully running 4.4.2 on my rooted Nexus 5. Thank you so much for the help (especially since this isn't even my thread; it just had a title which aligned perfectly to my problem, so hopefully the OP was helped along the way also).
To recap, for future use other visitors to this thread...
1. I tried to apply the 4.4.2 update using an OTA.zip file I found elsewhere on the Internet. This is easy. You've probably already done this.
2. I was told "build.prop" contained unexpected content.
3. I remembered that I had changed the DPI, so I changed that back from my personal 420 to the default 480. This resolved the previous error message.
4. I tried again, but this time was told Roboto-Bold.ttf contained unexpected content. I have no idea why that was.
5. I followed SOME of the instructions on this page: http://forum.xda-developers.com/showthread.php?t=2513701
Specifically, from the "Method 2" section, I did the "fastboot flash system C:/image-hammerhead-krt16m/system.img" and "fastboot flash boot C:/image-hammerhead-krt16m/boot.img" commands. That's ALL I DID from the "type these commands" section of those instructions. Doing that, I did NOT lose data! (well, none that I've yet noticed, at least)
6. I tried AGAIN to flash the OTA.zip file from Clockworkmod Recovery. This time it finally worked!
7. I checked Settings > About Phone, and I'm running 4.4.2 now!
8. I'm having trouble changing the DPI back to 420. I'm probably not rooted anymore. I'll have to go do that again. No big deal. Everything else seems fine.
...along the way, I needed to install drivers, for which I tried so many things, I don't even remember anymore what was the best method. I think using "ADB Manager.exe" from within my ADB folder was best. I also, at one point, had to change my USB device type from MTP to PTP. That was done on the phone, by swiping down the notification area.
Ugh, I wish I remembered everything, so I could spell it out as directly and clearly as I would've appreciated it be this morning, but I've seriously done so much recently that I know I'm missing certain steps, and I feel really bad for anyone having problems. There are so many instructions on the Internet that say, "Do this, and then this will happen," but they never explain what to do if that DOESN'T happen. And now here I am, not being any better than any of them. Sorry. Good luck.
Glad you got it working
I am trying to be able to get root on 4.4. I am currently on 4.2.2 (12.15.15) (camera update). I just rooted using RockMyMoto and ran through the MotoWPNoMo and I still get a "1" status when I type "adb shell getprop ro.boot.write_protect". Why is this happening?
Edit: By the way I have a Verizon carrier (if that matters).
Dreadlord12p said:
I am trying to be able to get root on 4.4. I am currently on 4.2.2 (12.15.15) (camera update). I just rooted using RockMyMoto and ran through the MotoWPNoMo and I still get a "1" status when I type "adb shell getprop ro.boot.write_protect". Why is this happening?
Edit: By the way I have a Verizon carrier (if that matters).
Click to expand...
Click to collapse
Carrier doesn't matter. Can you give a couple more details?
Can you paste the output of the motowpnmoto?
When I ran it initially, the output indicated to me it completed without error but I was still getting a 1. After I got it working properly, it fully ran and was clearly successful and i got a zero. I am thinking perhaps it didn't run properly and complete and it did not tell you that.
Check the main motowpnmoto thread and see if you can find my post. I think I posted a complete successful run for reference.
Sent from my XT1080 using Tapatalk
Dreadlord12p said:
I am trying to be able to get root on 4.4. I am currently on 4.2.2 (12.15.15) (camera update). I just rooted using RockMyMoto and ran through the MotoWPNoMo and I still get a "1" status when I type "adb shell getprop ro.boot.write_protect". Why is this happening?
Edit: By the way I have a Verizon carrier (if that matters).
Click to expand...
Click to collapse
How many times have you run it, and did you keep your phone screen on? I think it requests a Give Root pop up for ADB
Another question.
I was on 4.2.2, get root with RMM. Then i suceed with WPNoMo. I get "0" code.
Then I just got messed with SlapMyMoto - cant get it done. I decide to wipe Maxx with House of Moto. Wiped, install 4.4 ota. Now I'm without root, but adb script from WPNoMo still show me "0" code. Can I get root? Any help? :fingers-crossed:
livinitwarrior said:
How many times have you run it, and did you keep your phone screen on? I think it requests a Give Root pop up for ADB
Click to expand...
Click to collapse
I have run it twice with no errors. I had my screen on the whole time. I granted the SU access popup for ADB. I will give you my log report after this post.
Dreadlord12p said:
I have run it twice with no errors. I had my screen on the whole time. I granted the SU access popup for ADB. I will give you my log report after this post.
Click to expand...
Click to collapse
Never mind, I just tried it on my windows 7 laptop and it worked. It said "removed pesky write protection..."
F***!!
I followed all the steps for slapmymoto but when I try to install the 4.4 update, IT FAILS!! PLEASE HELP.
Dreadlord12p said:
I followed all the steps for slapmymoto but when I try to install the 4.4 update, IT FAILS!! PLEASE HELP.
Click to expand...
Click to collapse
did you try the command to see if write protection is still off?
livinitwarrior said:
did you try the command to see if write protection is still off?
Click to expand...
Click to collapse
Yes and it gave me a blank. Not a 1 or a zero. If I did the last step on slapmymoto with the adb commands before I updated to 4.4, would that mess it up?
[email protected]:/ $ su
[email protected]:/ # getprop boot.write_protect
[email protected]:/ #
Dreadlord12p said:
Yes and it gave me a blank. Not a 1 or a zero. If I did the last step on slapmymoto with the adb commands before I updated to 4.4, would that mess it up?
[email protected]:/ $ su
[email protected]:/ # getprop boot.write_protect
[email protected]:/ #
Click to expand...
Click to collapse
What Failure are you getting?
Sent from my KitKat Ultra
Dreadlord12p said:
Yes and it gave me a blank. Not a 1 or a zero. If I did the last step on slapmymoto with the adb commands before I updated to 4.4, would that mess it up?
[email protected]:/ $ su
[email protected]:/ # getprop boot.write_protect
[email protected]:/ #
Click to expand...
Click to collapse
I'm pretty sure, at least for me, that for the command prompt to work with adb the best, have one in the folder you have the adb stuff in and open it from there, because it sounds like your adb shell isn't running. Did you check processes on ctrl+shift+escape?
Edit: try "adb shell getprop ro.boot.write_protect"
Caseyk621 said:
What Failure are you getting?
Sent from my KitKat Ultra
Click to expand...
Click to collapse
When it is installing the update with the little android icon, it gets about halfway and then it says "error". Then it reboots and tells me that the software update failed.
Dreadlord12p said:
When it is installing the update with the little android icon, it gets about halfway and then it says "error". Then it reboots and tells me that the software update failed.
Click to expand...
Click to collapse
So one, did you do all the steps including getting back a 0 after MotoWPNoMo? And then flashed back to stock 4.2.2 on the 12.15.15 update?
livinitwarrior said:
So one, did you do all the steps including getting back a 0 after MotoWPNoMo? And then flashed back to stock 4.2.2 on the 12.15.15 update?
Click to expand...
Click to collapse
Yes. I got a "0" after running MotoWPNoMo and I flashed the 4.2.2 (12.15.15).
Edit: I actually did not get either a 1 nor a 0. It was just blank. But MotoWPNoMo said was, "removed pesky write protection successfully".
Dreadlord12p said:
Yes. I got a "0" after running MotoWPNoMo and I flashed the 4.2.2 (12.15.15).
Edit: I actually did not get either a 1 nor a 0. It was just blank. But MotoWPNoMo said was, "removed pesky write protection successfully".
Click to expand...
Click to collapse
hmm ok. Until you make sure the files have been sent over. It sounds like there might not have been a full overwrite of the FXZ... you might want to try it again with the 12.15.15 on RSDLite version, and then try from there. If you tried to keep data, that might be the issue and it never reloaded the stock recovery back
livinitwarrior said:
hmm ok. Until you make sure the files have been sent over. It sounds like there might not have been a full overwrite of the FXZ... you might want to try it again with the 12.15.15 on RSDLite version, and then try from there. If you tried to keep data, that might be the issue and it never reloaded the stock recovery back
Click to expand...
Click to collapse
I used houseofmoto. I will try with rsd. And I did a full fxz. I kept no data.
Dreadlord12p said:
I used houseofmoto. I will try with rsd. And I did a full fxz. I kept no data.
Click to expand...
Click to collapse
idk why, but RSD has never given me an issue, even though it takes longer. Keep us updated
Dreadlord12p said:
When it is installing the update with the little android icon, it gets about halfway and then it says "error". Then it reboots and tells me that the software update failed.
Click to expand...
Click to collapse
Here is the MotoWPNoMo log:
==================== Moto-WP-NoMo 0.0.4 ==============================
Moto-WP-NoMo comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running Moto-WP-NoMo lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running Moto-WP-NoMo] -
---
(1) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(2) Understand that you may NOT repack or redistribute Moto-WP-NoMo
Ok?
(Yes/No)
Yes
!! Do NOT for any reason bite, punch, or molest your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (40/120)
must play a little while longer...
it's so cold in here
hmm, hold please
..............................................
[---------------------------------------------]
doing some *stuff*..................
this is getting boring, let's go ahead and get started..
clobbering (1).....
Waiting for ADB (39/120)
must play a little while longer...
lets put some things back in place...
installing root stuff, thanks chainfire
wait for it.........
yep, done. bye bye pesky write protection!
send your money, ALL OF YOUR MONIES to - [email protected]
Press ENTER to exit
write protection log
Here is the log when I check for write protection:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb shell getprop ro.bo
ot.write_protect
0
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Alright, I have done all the steps except installing the 4.4 OTA. I will keep you posted on whether or not the update fails. *crossing my fingers*.
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
carmike692000 said:
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
Click to expand...
Click to collapse
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Caseyk621 said:
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Click to expand...
Click to collapse
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
carmike692000 said:
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
Click to expand...
Click to collapse
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Caseyk621 said:
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Click to expand...
Click to collapse
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
EDIT - I'm sure one problem with the computer not listing the phone as a device is it cannot find the device driver to install for it, and I've not been successful googling for it. So in the Windows Device Manager list, my XT1080 has a yellow exclamation mark by it. Also, just installed TiB and froze "Motorola OTA" since I had to wait five minutes to post this edit anyways.
carmike692000 said:
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
Click to expand...
Click to collapse
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Caseyk621 said:
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Click to expand...
Click to collapse
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
carmike692000 said:
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
Click to expand...
Click to collapse
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Caseyk621 said:
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Click to expand...
Click to collapse
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
carmike692000 said:
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
Click to expand...
Click to collapse
Glad I could help! Don't forget to make a backup in TWRP! You may find yourself wanting to go back to stock sooner than you think! I keep trying ROMs but always end up missing active notifications and touch less as well as some others!
Sent From Droid Ultra
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
nubia11 said:
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
Click to expand...
Click to collapse
Flash the stock recovery with fastboot. I forget if you need to also unroot or not. Also make sure you have any apps that were disabled or frozen enabled/defrosted