I have a RAZR M running on T-Mobile. All was good, but I guess I accidentally took the update last night, because I woke up my phone to be greeted with the "your device has been updated" screen. I was trying to avoid it because I was rooted and wanted to keep the possibility of unlocking the bootloader, but oh well...it's not a big deal. However, now my phone keeps rebooting itself. I haven't narrowed it down to whether it's a consistent time between boots or what, but I've had at least 4 or 5 times since last night where I either glance over and see the boot animation playing, or I've been greeted by the "SIM is from an unknown source" screen when I wake the phone.
There's no chance Verizon will just swap it out for me, is there? Since I'm not their customer, I'm assuming I'd have to go through Motorola, which probably takes forever.
Motos turn around rate is rather fast... 10 days total maybe... 2 shipping to get to them they have to have it done in 5 business days... 2-3 days shipping to get it back to you... but with root they may not fix it... either way its worth a shot if you can go without a phone that long...
Sent from my XT907 using xda app-developers app
Oh, cool, that's not too bad. I'll try going into Verizon tomorrow just to see if I get lucky, but otherwise, I'll get in touch with Motorola.
I had root before, but the update removed it, so it shouldn't be an issue. It's too bad we can't RSD back to 4.1.1. The phone was perfect until the update was installed.
Just redo the NV edit and you don't have to return the phone, you can keep using it on GSM carriers.
The same NV edit works fine under the new build and you don't need root to use RadioComm.
There is also a way to revert to the prior rootable version and then protect root and update again keeping root.
cellzealot said:
Just redo the NV edit and you don't have to return the phone, you can keep using it on GSM carriers.
The same NV edit works fine under the new build and you don't need root to use RadioComm.
There is also a way to revert to the prior rootable version and then protect root and update again keeping root.
Click to expand...
Click to collapse
Sorry, I don't think I was clear. I did redo the NV edit, and that works as expected. It's just that the phone keeps freezing and rebooting. It's done it another 2 times (make that 3...it just did it again) since I posted this thread. The only thing that has changed from yesterday to now is that it now has the update (and a factory reset, since I hoped that would solve the issues).
How do I go back to a rootable version? That would be easiest if possible, but I read that RSD doesn't allow you to downgrade unless you have an unlocked bootloader.
Ok I misunderstood then. Check this link for the reversion method. It is for the HD but the same principle applies to the M as well.
I posted an edited XML file for the XT907 in that thread but there has been more work done since then and a fully scripted tool was made up which may not have been released yet.
This was all worked out over the last couple of days, so check that thread for the most recent info.
Basically you flash back in RSD Lite with the previous full XML.zip but using an edited XML file that skips the tz.mbn and gpt_main0.bin along with the getvar lines.
The boot up and root under that version with Motochopper and use Voodoo root keeper and protect and temp unroot and update again to the current build.
http://www.droidrzr.com/index.php/t...18799201-ota-locked-bootload-razr-hd-test-it/
cellzealot said:
Ok I misunderstood then. Check this link for the reversion method. It is for the HD but the same principle applies to the M as well.
I posted an edited XML file for the XT907 in that thread but there has been more work done since then and a fully scripted tool was made up which may not have been released yet.
This was all worked out over the last couple of days, so check that thread for the most recent info.
Basically you flash back in RSD Lite with the previous full XML.zip but using an edited XML file that skips the tz.mbn and gpt_main0.bin along with the getvar lines.
The boot up and root under that version with Motochopper and use Voodoo root keeper and protect and temp unroot and update again to the current build.
http://www.droidrzr.com/index.php/t...18799201-ota-locked-bootload-razr-hd-test-it/
Click to expand...
Click to collapse
Awesome, thanks! It looks like Kaos is working on a tool for the M, so I'll probably just wait for that. I'm way to tired to read and follow instructions tonight anyway. Thanks for the great work you guys do!
freak4dell said:
I had root before, but the update removed it, so it shouldn't be an issue. It's too bad we can't RSD back to 4.1.1. The phone was perfect until the update was installed.
Click to expand...
Click to collapse
I was just thinking about the root checker in the recovery menu... the "qe0/0 ,1/1 if your rooted and 0/1 if you have rooted"...
Sent from my XT907 using xda app-developers app
Is your phone still freezing and rebooting. If your phone stopped doing that, do you know what you did to stop this because I'm now facing the same problem.
Sent from my XT907 using xda app-developers app
ccdsatt said:
Is your phone still freezing and rebooting. If your phone stopped doing that, do you know what you did to stop this because I'm now facing the same problem.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Mine is still doing it. It's either just a random coincidence that it happened the same time that I took the update, or it's caused by a part of the update that was skipped by the roll-back procedure. Either way, I've contacted Motorola and will be sending the phone to them this week. I just don't feel like dealing with trying to fix it myself, and if the X turns out to be decent, I'm going to end up selling the M so I want it to be in good condition for a good resale value.
Now I need to see if the files to RSD to a completely stock version of the newest build are available anywhere.
Related
Just got a system update notification... taking forever to install... anyone know what it entails?
Edit: SO I see that Sprint ID / EW!!!) was installed, and my Firmware is 2.2.1, and baseband is S: P100.08 S: EB28, and Build is SPH-P100.EB28...
Problem is, I can't remember if that's new or not...lol. Damn me for not paying attention, and DAMN ME for thinking that the possibility of a HC release was possible... stupid hopes and dreams....
Edit II: Just found this report... compared to the rest of the updates, the SGT got the short end of the stick YET AGAIN!!!
http://www.wirelessandmobilenews.co...epic-4g-tab-transform-updates-coming-321.html
"The Samsung Galaxy Tab update adds Sprint ID features."
I updated also and 2.2.1 is new, also ot updated the modem as seen by hitting the soft menu key during the update and looking under about phone, baseband. I would like to see if the update package had a whole modem.bin in ot but i installed the update before I got the temp file. The last update only had a modem file of a few kbytes so it just patched the modem. It would be great to get hold of a whole modem.bin as there are none for the sprint tab currently.
Sent from my SPH-P100 using XDA App
I was just going to as if anyone was able to grab the modem.bin. Hopefully we get luck and someone is able to do so.
What about root status? I'm hesitant to update if it breaks root because of the issues I've had with the stock gallery app (removed it via a root file explorer).
I updated my rooted Gtab and the root seems unaffected. I use mine without a data pack - wifi only. I used the root to get rid of the activation nagger in the notification bar - and it's still gone and SuperUser is still operating.
However: Sprint ID only works through a Sprint Subscriber Data Pack - not over WiFi, unless you have a company "Keyword". Alas - I don't like Sprint ID anyway.
sprint tv
i installed the "sprint" id, and it says in the description about sprint tv. i had this on the evo, but i feel like i'd make better use of it on a 7 inch screen. any ideas how to get it on the tab? i searched the market under the sprint tab and had no luck finding it.. any suggestion would be great
I got the OTA shortly after trying to install clockwork and patching an overclocked kernel. I wasn't expecting the OTA until Monday, but I went ahead and try to install it (it failed, of course).
I managed to pull the downloaded zip file out of my cache and check if there was a modem.bin. Unfortunately, once again, there's only a modem_delta.bin, so no luck there.
I tried running the update again manually after rolling back my kernel, and apparently I still had a modified boot.img, so after doing a full wipe, rolling back to DJ30, and then manually updating to EA24, I was able to get the EB28 update installed, with all of its Sprint ID goodness. It's very late now so I don't have time to actually play with it much, but I'm actually happy to be back to an official build. I'm hoping they fixed a few of the bigger issues I had with EA24, but I somehow doubt it.
Previously I was rooted and had the Bauxite kernel. I flashed the original kernel back and then installed the EB28 update. I lost root, so I tried superoneclick again. It said it rooted but superoneclick locked up while "Remounting system with read-only access..." My tab is unresponsive but the buttons are still lit up.
Update: I finally got it to reboot and I am rooted again.
matt6x7 said:
Previously I was rooted and had the Bauxite kernel. I flashed the original kernel back and then installed the EB28 update. I lost root, so I tried superoneclick again. It said it rooted but superoneclick locked up while "Remounting system with read-only access..." My tab is unresponsive but the buttons are still lit up.
Update: I finally got it to reboot and I am rooted again.
Click to expand...
Click to collapse
Would you mind attaching your file for the original kernel? I forgot to make a backup when flashing Bauxite.
powermatt said:
What about root status? I'm hesitant to update if it breaks root because of the issues I've had with the stock gallery app (removed it via a root file explorer).
Click to expand...
Click to collapse
I applied the update last night and can confirm that root is still intact, so the super one click method should still work if you haven't rooted your tab prior to this update.
Unfortunately, what is also intact is my long standing issue with the stock Gallery app (rogue sensor usage causing massive battery drain). Ah well, removed with Titanium backup, replaced with Just Pictures, problem fixed. Again.
Other than the addition of Sprint ID, this seems to be a pretty minor update. Could be my imagination, but it seems a tad snappier than the EA24 update. Could be the incremental increase to Android 2.2.1. But other than Sprint ID, there are no major new features.
powermatt said:
I applied the update last night and can confirm that root is still intact, so the super one click method should still work if you haven't rooted your tab prior to this update.
Click to expand...
Click to collapse
Thanks for the useful info. I was hesitant to run the update after the previous hassles. I've just updated mine without any noticeable detrimental effect.
regards,
Tony C.
Root was not intact for me after upgrade. I tested with root explorer, and font changer. Both failed after trying to get root permission. I just used SOC after upgrade. All was good...
@lloydcabraham
Here is my backup kernel prior to the new EB28 update. Sorry for the delay, I've been engrossed in basketball.
matt6x7 said:
@lloydcabraham
Here is my backup kernel prior to the new EB28 update. Sorry for the delay, I've been engrossed in basketball.
Click to expand...
Click to collapse
Thanks I really appreciate it!
I was previously rooted with SuperOneCLick (rageagainstthecage method). I did not unroot prior to the upgrade. The upgade said it failed but a look at About Phone proved otherwise. I would suggest that people unroot before the upgrade but it did not matter for me.
After the update I no longer had root access. But I was able to root with SuperOneClick again. I have had no problems since the upgrade/reroot. There are no interface differences that I have spotted so far.
Can someone please post the application name for the Sprint ID so I can remove it. I had gotten rid of all the Bloatware and now after this update I get this which I will not use.
By the way I was rooted with Super One Click and using the Once Click lag Fix and after update I did lose Root. Just re-rooted and am fine now. Got scared because the orientation was not working and I thought it broke it. Sohow the update set the orientation lock.
Also I deleted a couple files hoping these were the new Sprint ID update.
Does anyone know what they are and if I need them can somone please post them? I will take the best guess of what I remember them being called.
Perhaps someone can post there Sprint file names.
SprintAndroid
SprintUpdate
Thanks,
Mark
Can someone post the update.zip for the update? I got the OTA notification but when it attempted to install (using Stock recovery), it failed, somehow.
Thanks in advance.
I need the update.zip as well.
Hell, mine still tries to update my tab to EA24 which always failed. Can't even get the notification for 28. Time to go to Sprint and raise some hell....
Sent from my SPH-P100 using XDA Premium App
My sprint galaxy tab was updated the EB28 the day I got it (two days ago), today I was trying to get CWM on the tab, got stuck at Samsung screen, so I used odin and flashed back to DJ30 (without baseband, which is already at EB28) and have been trying to get back to EB28 since.
Can any of you kind gentlemen who updated to EB28 do a roto backup and upload the file? I think this is the only way I can get back into EB28 at the moment.
Many thanks!
I have a Motorola droid razr m model XT907. It's rooted and GSM unlocked. I'm using it on Straight Talk currently. Verizon is pushing this 98.18.78 update which I hear unroots the phone. I want to know which of the verizon apps I need to freeze or remove to prevent this update.
Thanks in advance
Blufx1 said:
I have a Motorola droid razr m model XT907. It's rooted and GSM unlocked. I'm using it on Straight Talk currently. Verizon is pushing this 98.18.78 update which I hear unroots the phone. I want to know which of the verizon apps I need to freeze or remove to prevent this update.
Thanks in advance
Click to expand...
Click to collapse
Just a heads up, you posted in the Razr HD forum, but no big deal the procedure will be the same for both. When I was running stock ROMs, I would freeze the updater.apk in TiBU to prevent OTAs. However, the new update is rootable with Motochopper 1.3, but you can't unlock the bootloader. If I was in your situation, I would unlock the bootloader now, take the update (for the improvements it offers), re-root it, and unlock it for GSM again. Once your BL is unlocked and you have a custom recovery installed, all you have to do is flash SU in recovery to regain root.
I thank you for the answer. You make it sound so easy,. However, I needed step by step instructions to get where I am now. Can you point me to some to do this? I've unlocked the GSM a couple of times using CellZealot's post. That's no problem. I have titanium backup to freeze the updater.apk, but what is TiBU? I'll get Motochopper in the meantime.
Duhhhh, I just figured out what TiBU is.
Blufx1 said:
Duhhhh, I just figured out what TiBU is.
Click to expand...
Click to collapse
If you don't want to unlock the bootloader and want to take the OTA, then root afterwards, you can find Motochopper 1.3 here:
http://www.droidrzr.com/index.php/t...oot-razr-m-xt907-for-locked-devices-on-91878/
If you want to unlock the bootloader, look for Motopocalypse here (you'll need root access for this, so unlock prior to updating. The OTA does block the ability to unlock the BL, but does not block the ability to root):
http://wiki.cyanogenmod.org/w/Template:Motopocalypse
Once you unlock the bootloader, look for the TWRP thread in the Development section, there should be instructions, along with the file you need to install the recovery. Once TWRP is installed, get the updater SuperSU .zip and flash it in recovery and you will re-gain root. If you want to update after unlocking, you can take one of the several stock ROMs running around here and flash in recovery.
SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Long story short:
- You can stay as is, by just freezing the updater.apk
- You can OTA and re-root with Motochopper 1.3
- You can unlock bootloader and re-root afterwards.
Thanks again. I'll work on this tomorrow and post back.
Blufx1 said:
Thanks again. I'll work on this tomorrow and post back.
Click to expand...
Click to collapse
No probem, let us know how it turns out.
RikRong said:
If you don't want to unlock the bootloader and want to take the OTA, then root afterwards, you can find Motochopper 1.3 here:
http://www.droidrzr.com/index.php/t...oot-razr-m-xt907-for-locked-devices-on-91878/
If you want to unlock the bootloader, look for Motopocalypse here (you'll need root access for this, so unlock prior to updating. The OTA does block the ability to unlock the BL, but does not block the ability to root):
http://wiki.cyanogenmod.org/w/Template:Motopocalypse
Once you unlock the bootloader, look for the TWRP thread in the Development section, there should be instructions, along with the file you need to install the recovery. Once TWRP is installed, get the updater SuperSU .zip and flash it in recovery and you will re-gain root. If you want to update after unlocking, you can take one of the several stock ROMs running around here and flash in recovery.
SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Long story short:
- You can stay as is, by just freezing the updater.apk
- You can OTA and re-root with Motochopper 1.3
- You can unlock bootloader and re-root afterwards.
Click to expand...
Click to collapse
To add to this, if you unlock, you will permanently be able to root...
Sent from my Nexus 7 using Tapatalk 4
Ok. I have the bootloader unlocked. I downloaded a rom from here. It's been cleaned up of bloatware and stuff. I have SuperSU and updater SuperSU, but I dont know what to do with it. I also installed TWRP manager. I need just a little more guidance.
Blufx1 said:
Ok. I have the bootloader unlocked. I downloaded a rom from here. It's been cleaned up of bloatware and stuff. I have SuperSU and updater SuperSU, but I dont know what to do with it. I also installed TWRP manager. I need just a little more guidance.
Click to expand...
Click to collapse
Ok, so first, you need to disable the install-recovery script. I built an app to do this (YOU GET TO BE THE FIRST TESTER YAY!)
Install this app: ftp://kd8rho.net/RecoveryFlasherDisabler-public-test.apk
Choose "disable install-recovery"
That will (theoretically - can't test cause my phone's rooted and ROMMed) allow you to install a custom recovery without any hassle.
Once that's done, follow the installation instructions in this thread http://forum.xda-developers.com/showthread.php?t=2226729, starting with this line:
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
Click to expand...
Click to collapse
You won't have to boot directly into recovery because that app *should* fix that for you. You can boot the phone normally after installing and run something like "adb reboot recovery"
I downloaded and installed your app. When I ran it, it said the installer was found, but disabled. moving on to step two now. Thanks
Hello. This is way off base but does the update fix the screen glitch? Are there any roms that will fix the glitch?
Thanks in advance!
Xt907 JESUS IS THE WAY, THE TRUTH, AND THE LIGHT! *BE BLESSED*
The screen glitch isn't fixed from the update. It might be better. I have a hunch the new radio isn't good for customers with unlimited data in areas with 4G coverage. My phone seems more eager to switch to 3g after the update. Besides that, I can't tell this update foes anything positive. It would be nice to use fastcharge while powered off but for some reason my device will not turn off while it's plugged in. It used to turn off and charge, then one day it quit working. If my battery is low enough and I turn the phone off the green light glows solid for s few minutes then the xt907 turns itself on. Can I downgrade to the previous radio or am I stuck with the new 3g friendly radio that presumably serves Verizon's purposes and not mine?
Sent from my XT907 using xda app-developers app
zombolt said:
The screen glitch isn't fixed from the update. It might be better. I have a hunch the new radio isn't good for customers with unlimited data in areas with 4G coverage. My phone seems more eager to switch to 3g after the update. Besides that, I can't tell this update foes anything positive. It would be nice to use fastcharge while powered off but for some reason my device will not turn off while it's plugged in. It used to turn off and charge, then one day it quit working. If my battery is low enough and I turn the phone off the green light glows solid for s few minutes then the xt907 turns itself on. Can I downgrade to the previous radio or am I stuck with the new 3g friendly radio that presumably serves Verizon's purposes and not mine?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Yea...all I did was flash the radio and it feels like I'm being throttled now that I have the new radio...still on the.3/.78 just with the new radio... I'll try and flash the old radio here in a min ... Are you on an unlocked bootloader?
Sent from my XT907 using xda app-developers app
zombolt said:
The screen glitch isn't fixed from the update. It might be better. I have a hunch the new radio isn't good for customers with unlimited data in areas with 4G coverage. My phone seems more eager to switch to 3g after the update. Besides that, I can't tell this update foes anything positive. It would be nice to use fastcharge while powered off but for some reason my device will not turn off while it's plugged in. It used to turn off and charge, then one day it quit working. If my battery is low enough and I turn the phone off the green light glows solid for s few minutes then the xt907 turns itself on. Can I downgrade to the previous radio or am I stuck with the new 3g friendly radio that presumably serves Verizon's purposes and not mine?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately I am locked. Bought the phone *right* after the may update. I migrated from the droid incredible, which has an open bootloader I believe. So it's been pretty rough after having that phone!
Sent from my XT907 using xda app-developers app
What "screen glitch" are you talking about?
Oh, I forgot to post back. I managed to screw it up royally. But I have it straightened out now after a flash.
The screen will occasionally glitch on the left side, pushing the screen right and changing the color for about 1-2 seconds
Sent from my HTC6435LVW using XDA Premium 4 mobile app
I promise that I have been reading threads for 2 weeks trying to figure out how to solve my problem without posting any questions, because I know no one likes to repeat themselves! I made a little bit of progress, but now I don't know what to do.
I bought my RAZR M in February. I took it out of the box and activated it. I never rooted it - had no intention of rooting it. Everything was great until the April update (98.15.66). All sorts of apps started crashing, background, Chrome, text messaging... phone kept deleting Contacts...it was a mess. I posted in the Moto Support forum and was advised to reset, which I did. It helped a little, sometimes apps still crashed, but I was dealing with it. I know the phone took at least one more update after that, but I don't know which. Then November 8, I did the OTA to 98.30.1. Phone got stuck on the red eye during boot. Tried clearing cache, reset, no luck. Called Moto support and they said they couldn't do anything unless I paid them $120 to flash the phone, because according to their info, my phone was rooted!! I never rooted it, I didn't know anything about rooting (still don't, really). I wonder if something failed during one of these updates and triggered their root checker. After reading threads here on XDA, I was able to use RDS lite to 98.16.3. So at least the phone boots, but now it keeps wanting to do the OTA to 98-30.1.
I assume I should avoid taking the OTA, but I don't know how to do that without hitting "Later" every 12 hours. If I'm understanding correctly, since I have 98.16.3 my bootloader is locked and there is nothing I can do about that. I thought maybe Titanium Backup would help so I could at least freeze the updater, but I don't have SU/root access to be able to do that. Where do I go from here? Thank you very much for any help!
So you've never been rooted and moto said it had been... Did you buy it from Verizon? Lets check and see if that device has ever been rooted... Power of the device... Power on while holding volume up + volume down... Select recovery...when you see Android Andy hold volume down tap volume up... Now you should see QE process does it say 0/0 or 0/1... If it says 0/0 your phone has never been rooted... If it said that I would either call them back.. After taking pix of that... And inform them of that.. Or take it to a Verizon store and request a new device... Post the pic in your topic on Motorola's forum and say how they refused service because your device was rooted when it wasn't... Matt the forums manager should reply and assist then
Sent from my XT907 using xda app-developers app
@sasperson
Where did you "clear cache" during your bootloop? I dont believe stock recovery has that option. Also how did you use RSDLite if you have a locked bootloader, wouldn't it just fail. Not trying to be a ****, i'm just pointing out the inconsistencies.
ATTACK said:
@sasperson
Where did you "clear cache" during your bootloop? I dont believe stock recovery has that option. Also how did you use RSDLite if you have a locked bootloader, wouldn't it just fail. Not trying to be a ****, i'm just pointing out the inconsistencies.
Click to expand...
Click to collapse
Stock recovery does have the option to clear the cache partition...you can RSD I up or to the current version...
Sent from my XT907 using xda app-developers app
ezknives said:
Stock recovery does have the option to clear the cache partition...you can RSD I up or to the current version...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Ok. I didnt know stock recovery had any options, never used it. Didn't he RSD Lite from 98.30.1 to 98.16.3. I thought you couldn't downgrade with a locked bootloader.
I apologize my brain saw .16 the first time I read it from where I'm not used to seeing .30
Sent from my XT907 using xda app-developers app
It does say 1/1. I don't believe it said that when I did the FDR back in April/May when I first starting having issues after the update to 98.15, but I can't say 100% for sure since I didn't even know what it meant up until a couple of weeks ago when I started reading up.
How it got like that, I don't know. I bought the phone from Amazon. Sold by Amazon, marked as Brand New. I didn't buy it from a Joe Schmo marketplace seller.
I have no idea for sure if my bootloader is unlocked or not. From what I've read, it seems that if you have 98.16.3, then it has to be. When I go into the AP fastboot screen, it says Device Status: Locked.
I did post on the Motorola forum and someone there told me how to check in the recovery menu for the root status, but since it says 1/1, someone recommended that I come over here to XDA, which is how I ended up doing the RSD lite thing to at least get my phone functional again.
All of this stuff is so far over my head...I'm not really interested in customization or removing the bloatware - I just disable or ignore it. I am only looking to get my phone back running like normal without telling it "Later" every 12 hours to avoid the update. And if I'm understanding correctly regarding the bootloader, there aren't many customization options anyway. Do I just wait to see if the 98.30 update gets added on the droid-developers.org site?
I
sasperson said:
It does say 1/1. I don't believe it said that when I did the FDR back in April/May when I first starting having issues after the update to 98.15, but I can't say 100% for sure since I didn't even know what it meant up until a couple of weeks ago when I started reading up.
How it got like that, I don't know. I bought the phone from Amazon. Sold by Amazon, marked as Brand New. I didn't buy it from a Joe Schmo marketplace seller.
I have no idea for sure if my bootloader is unlocked or not. From what I've read, it seems that if you have 98.16.3, then it has to be. When I go into the AP fastboot screen, it says Device Status: Locked.
I did post on the Motorola forum and someone there told me how to check in the recovery menu for the root status, but since it says 1/1, someone recommended that I come over here to XDA, which is how I ended up doing the RSD lite thing to at least get my phone functional again.
All of this stuff is so far over my head...I'm not really interested in customization or removing the bloatware - I just disable or ignore it. I am only looking to get my phone back running like normal without telling it "Later" every 12 hours to avoid the update. And if I'm understanding correctly regarding the bootloader, there aren't many customization options anyway. Do I just wait to see if the 98.30 update gets added on the droid-developers.org site?
Click to expand...
Click to collapse
If it says 1/1 that means your currently rooted (0/1 it has at some point been rooted) download a root checker from google play... If it is rooted I'm sure you could install a super user then freeze the updater...
Sent from my XT907 using xda app-developers app
ATTACK said:
Ok. I didnt know stock recovery had any options, never used it. Didn't he RSD Lite from 98.30.1 to 98.16.3. I thought you couldn't downgrade with a locked bootloader.
Click to expand...
Click to collapse
No, the phone tried to install 98.30.1 through OTA, but failed and got stuck on the red eye during boot. Moto said the update failed because I was rooted, which I never rooted the phone. How the phone came to say 1/1 on the recovery screen root check, I'll never know, but it's water under the bridge now.
Once I came here and read how to use RSD lite, I flashed it to 98.16. I don't know what version I was running before the 98.30.1 OTA attempt on Nov. 8.
I downloaded Root Checker. For SU it says, "Not found."
Root Access: "no access"
Is this because I only flashed the VRZ_XT907_9.8.1Q-78-1_1FF.xml, which from what I understand is straight stock? Is the phone technically not really "rooted" then? Is it possible to get the Super Access at this point, or am I stuck?
Again, thank you for your help and patience!
sasperson said:
No, the phone tried to install 98.30.1 through OTA, but failed and got stuck on the red eye during boot. Moto said the update failed because I was rooted, which I never rooted the phone. How the phone came to say 1/1 on the recovery screen root check, I'll never know, but it's water under the bridge now.
Once I came here and read how to use RSD lite, I flashed it to 98.16. I don't know what version I was running before the 98.30.1 OTA attempt on Nov. 8.
I downloaded Root Checker. For SU it says, "Not found."
Root Access: "no access"
Is this because I only flashed the VRZ_XT907_9.8.1Q-78-1_1FF.xml, which from what I understand is straight stock? Is the phone technically not really "rooted" then? Is it possible to get the Super Access at this point, or am I stuck?
Again, thank you for your help and patience!
Click to expand...
Click to collapse
if your on version listed in screenshot yes you can root it ... Use motochopper 1.3
Sent from my XT907 using xda app-developers app
ezknives said:
if your on version listed in screenshot yes you can root it ... Use motochopper 1.3
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Ok, I will give that a try. I have read about motochopper, but was confused as to whether it was the right thing for the version I'm running, I think I was reading "Build version," mixing that with "System version," and getting scared when it said it will brick the phone if not used on the right version. Since my Build Number is 9.8.1Q.78-1, the directions and links on droidrazr.com posted by livinginkaos and SamuriHL should work for me, right? (assuming I can follow the directions, that is)
I wonder if this will fix the strange random app crashes I've been getting ever since the April update. It's very inconvenient to have my text message history wiped.
Thank you for the advice, ezknives!
*Update*
I used motochopper! I used Titanium backup and froze the updater.apk! \o/
I have one more question - now that I have this super user access, is it still best to just disable/freeze the bloatware instead of removing it altogether? I read that some people have used Titanium backup to delete it, I also recall reading that some people had issues with updates if they deleted them and ended up having to reinstall them...?
sasperson said:
*Update*
I used motochopper! I used Titanium backup and froze the updater.apk! \o/
I have one more question - now that I have this super user access, is it still best to just disable/freeze the bloatware instead of removing it altogether? I read that some people have used Titanium backup to delete it, I also recall reading that some people had issues with updates if they deleted them and ended up having to reinstall them...?
Click to expand...
Click to collapse
Yes it's best to freeze it all rather then delete it.... So you don't have to do as much when the next OTA comes out...
Sent from my XT907 using xda app-developers app
ezknives said:
Yes it's best to freeze it all rather then delete it.... So you don't have to do as much when the next OTA comes out...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Everything seems to be back to normal - at least back to how it was a few weeks ago. It still has the random background app crash, but whatever. I've been living with that since the April update. I'm just happy my phone is functional again.
Thanks again for the help!
:victory:
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Piaband said:
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
if i could unlock it when i had gotten it in august, sure. but it's too much effort to start over at this point. i have everything set up perfectly. never had to start over. also didn't want to pay for it and send my info to some stranger on the internet. anyway, moot point. good for you, but that option's not available for most people.
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
No nothing roots 4.4 at this point.
vegasdgk said:
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No he basically just rewrote the instructions of how to root the original firmware.
akellar said:
No he basically just rewrote the instructions of how to root the original firmware.
Click to expand...
Click to collapse
I didn't rewrite it. No where are there instructions for getting root AND write protection off on the 4.2.2 camera update without 1 using command line commands AND 2 that network based program (called Cydia compactor I think). There's none of those complications here. Most people don't even realize 1 click root survives the camera update.
But you are right as to kit kat. I thought my title was clear that this is for jellybean though.
mistermojorizin said:
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
Click to expand...
Click to collapse
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
-Zeta- said:
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
Click to expand...
Click to collapse
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
mistermojorizin said:
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
Click to expand...
Click to collapse
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
-Zeta- said:
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
Click to expand...
Click to collapse
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
mistermojorizin said:
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
Click to expand...
Click to collapse
Not sure about the battery life on kitkat of the MAXX right now, so i will stick with 4.2.2 first and do a little research.
Anyway, thanks for the reply and I've gained root on 4.2.2 (12.15.15) using RockMyMoto:laugh:
I was sitting in my car and looked at the screen and I noticed that the phone was downloading MotorolaOTA 4.0 Does anyone know what it is? I am currently running KitKat 4.4.4 and never did the Lollipop update.
I also stopped the download in process but it appears that the phone would love to continue the download.
Thanks
gman
The phone has an app called MotorolaOTA, which is responsible for downloading system updates. If it was a software update it'd say it's 23.11.39.
Sent from my Droid Turbo using Tapatalk
Just caught my Turbo
I am running KitKat 4.4.4. version 21.44.12 the file it's trying to download is 770 megabytes. Could it be trying to sneak in Lollipop?
gman781 said:
I am running KitKat 4.4.4. version 21.44.12 the file it's trying to download is 770 megabytes. Could it be trying to sneak in Lollipop?
Click to expand...
Click to collapse
Yes, it will download the update but, afaik you MUST confirm installation of it... It's not going to install on it's own...
smokie75 said:
Yes, it will download the update but, afaik you MUST confirm installation of it... It's not going to install on it's own...
Click to expand...
Click to collapse
For over a month I have been getting the update screen and I would just put it off. Now it seems like it is pushing it's way into my phone.
Motorola confirmed recently that they would be patching the Stagefright exploit for the Turbo via OTA. I wonder if they can somehow force the update since it's such an important security issue this time around. I seem to remember Samsung doing something similar with the S6 shortly after release. I would recommend disabling Motorola OTA until more is known.
Not rooted, cannot disable.
Caught my phone doing the same thing. Is Lollipop larger than 770MB? I thought so, but haven't checked into it.
That's what I have been trying to figure out.
TheHolyCobra said:
Caught my phone doing the same thing. Is Lollipop larger than 770MB? I thought so, but haven't checked into it.
Click to expand...
Click to collapse
CM 12.1 ROM (Lollipop 5.1.1) for our Quarks is only 390 MB.
So, yeah, Lollipop 5.1 with Verizon bloatware is probably 770MB.
But the 5.1 OTA for Droid Turbo XT1254 posted here is 1.1GB:
http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
Still 770MB is huge.
Just freeze it
Sent from my XT1254 using XDA Free mobile app
Not rooted and will not allow disable.
My phone downloaded it. Been telling it no thanks for a few days now. Some home after telling it to remind me later it then decided to reboot and start installing. I haven't rooted yet but I have bought moforoot and don't want my 20 bucks to go to waste! Of course I can boot up without it wanting to install. Went into bootloader and powered it off. Almost though i couldn't get into that.
Any way I can stop this thing? Trying to get someone at home to turn on my PC since that is where my moforoot is at and stupid me didn't put it on my server which is on 24/7. Any ideas?
drtweak said:
My phone downloaded it. Been telling it no thanks for a few days now. Some home after telling it to remind me later it then decided to reboot and start installing. I haven't rooted yet but I have bought moforoot and don't want my 20 bucks to go to waste! Of course I can boot up without it wanting to install. Went into bootloader and powered it off. Almost though i couldn't get into that.
Any way I can stop this thing? Trying to get someone at home to turn on my PC since that is where my moforoot is at and stupid me didn't put it on my server which is on 24/7. Any ideas?
Click to expand...
Click to collapse
Before my turbo was rooted, I was able to block the OTA's by installing the motorola drivers on my windows pc and installing Minimal ADB / Fastboot. Go here for instructions http://forum.xda-developers.com/showpost.php?p=57436867&postcount=26
However, I never did download any of the OTA's to my phone but I hope this helps. I believe this is by Rootjunky as far as credits are concerned.
Also by Misterxtc
gman781 said:
Not rooted and will not allow disable.
Click to expand...
Click to collapse
RL_Wells said:
Before my turbo was rooted, I was able to block the OTA's by installing the motorola drivers on my windows pc and installing Minimal ADB / Fastboot. Go here for instructions http://forum.xda-developers.com/showpost.php?p=57436867&postcount=26
However, I never did download any of the OTA's to my phone but I hope this helps. I believe this is by Rootjunky as far as credits are concerned.
Also by Misterxtc
Click to expand...
Click to collapse
The debloat tool is a much easier way to disable any app on your phone. On kitkat it disables and on lollipop it hides the apps. The hide command on lollipop has the same effect as the disable command on kitkat.
---------- Post added at 02:12 PM ---------- Previous post was at 02:10 PM ----------
drtweak said:
My phone downloaded it. Been telling it no thanks for a few days now. Some home after telling it to remind me later it then decided to reboot and start installing. I haven't rooted yet but I have bought moforoot and don't want my 20 bucks to go to waste! Of course I can boot up without it wanting to install. Went into bootloader and powered it off. Almost though i couldn't get into that.
Any way I can stop this thing? Trying to get someone at home to turn on my PC since that is where my moforoot is at and stupid me didn't put it on my server which is on 24/7. Any ideas?
Click to expand...
Click to collapse
Enter recovery mode, clear cache and use the debloat tool to disable the OTA.
[/COLOR]
Enter recovery mode, clear cache and use the debloat tool to disable the OTA.[/QUOTE]
Yea no go on Recovery. It just goes straight to "Installing System update" Got my PC on, downloaded my mofo to my work PC, and not installing drivers and also downloading a stock but rooted version of 4.4.4. not quite ready to move on to 5.1 yet.
Thanks for the help though and tryin to help out! Now to finally jump into my Turbo after 8 months of having it. I miss the days of TWRP on my Razr HD. Funny because i had to reload an old backed up image so i could get some old wifi passwords.
UGH this damn phone. Won't power off when in Fastboot, so i just have to let it sit in fastboot and watch it and just restart everytime it starts up. got 20 minutes left of downloading an image. About ready to say F'it and just factory reset it for now and see if that fixes it or not.
Well flashing a stock rooted rom didn't work. Uses the rooted Quark 21.44.12 image that I download and I know i was on 21.44.12 when i checked last time. So don't know if it was because of the starting up the update or what.
Soft bricked my turbo, time to use RSD Lite again. Haven't had to use this in a LOOOOOONG time (Like Droid X Days)
drtweak said:
Well flashing a stock rooted rom didn't work. Uses the rooted Quark 21.44.12 image that I download and I know i was on 21.44.12 when i checked last time. So don't know if it was because of the starting up the update or what.
Soft bricked my turbo, time to use RSD Lite again. Haven't had to use this in a LOOOOOONG time (Like Droid X Days)
Click to expand...
Click to collapse
I'm probably too late but have you tried this to get back to KitKat? I used it earlier today and it worked great.
Misterxtc said:
I'm probably too late but have you tried this to get back to KitKat? I used it earlier today and it worked great.
Click to expand...
Click to collapse
No I had to get my phone backup asap. using the RSD Lite method actually didn't work. the program would keep freezing right after it read the zip file and then crash. Had to use Root Junky's method. I was able to restore back to stock 21.44.12 and everything was there as if nothing happened so I'm all good.