Determine software version of inactive phone? - Droid X General

Ok, so I ultimately want to root this phone and install a custom ROM on it. However, it is not activated, and I cannot bypass the prompt to activate, I can only get to a dialer.
So, after reading the forums, it appears that the latest official FW is .621 and there's a root method for it, but it only works on .621. Obviously, root methods are version dependent. I figure I have to know the software version before continuing then.
Is there a code I can enter into the dialer to pull up software info? Or perhaps an adb command that doesn't require root? Anything at all I can do?
Or, do I even need software info? Can I simply proceed with some alternative root method?
Regards
Smith
EDIT: I ended up solving this through trial and error. I flashed the 2nd most recent sbf file and it produced an error in the bootloader, indicating that the device must've been on .621 so I sbf back to .621 and I'll proceed with that method.
EDIT 2: Ok, so that's fine and dandy and I was able to flash the sbf specified in the thread, but now zerg exploit won't run because I have no way of enabling adb :/ any ideas?

smithisize said:
Ok, so I ultimately want to root this phone and install a custom ROM on it. However, it is not activated, and I cannot bypass the prompt to activate, I can only get to a dialer.
So, after reading the forums, it appears that the latest official FW is .621 and there's a root method for it, but it only works on .621. Obviously, root methods are version dependent. I figure I have to know the software version before continuing then.
Is there a code I can enter into the dialer to pull up software info? Or perhaps an adb command that doesn't require root? Anything at all I can do?
Or, do I even need software info? Can I simply proceed with some alternative root method?
Regards
Smith
EDIT: I ended up solving this through trial and error. I flashed the 2nd most recent sbf file and it produced an error in the bootloader, indicating that the device must've been on .621 so I sbf back to .621 and I'll proceed with that method.
EDIT 2: Ok, so that's fine and dandy and I was able to flash the sbf specified in the thread, but now zerg exploit won't run because I have no way of enabling adb :/ any ideas?
Click to expand...
Click to collapse
http://www.droid-life.com/2010/06/10/tip-how-to-bypass-android-activation-screen-on-motorola-droid/ this shows how to by-pass the "activation", I just did it so it does in fact work for the Droid X M8810

dasfaust said:
http://www.droid-life.com/2010/06/10/tip-how-to-bypass-android-activation-screen-on-motorola-droid/ this shows how to by-pass the "activation", I just did it so it does in fact work for the Droid X M8810
Click to expand...
Click to collapse
You sir are incredible, thank you, I will try this when I get back to work tomorrow !
Sent from my SGH-I747 using xda app-developers app

Also, if you want to root, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1800047
Please post any questions you have in that thread
Sent from my Galaxy Nexus using Tapatalk 2

Going to check that thread now, got ADB working, just need to path it, and get all the other stuff going... Got this Droid X free and it has that pesky .621 on it.

Related

Verizon ota failed

Hello,
Yesterday I rooted my new droid x. I used titanium backup to backup, then remove some of the apps that I didn't need. However, then I received the ota update, and it fails to install. Im assuming it is because I have removed the city id, amazon mp3 store, and backup assistant. I try to restore, but I find I cannot restore them jacques they are non market apps. Where can I find them, then install them?
Sent from my DROIDX using XDA App
quinnteq said:
Hello,
Yesterday I rooted my new droid x. I used titanium backup to backup, then remove some of the apps that I didn't need. However, then I received the ota update, and it fails to install. Im assuming it is because I have removed the city id, amazon mp3 store, and backup assistant. I try to restore, but I find I cannot restore them jacques they are non market apps. Where can I find them, then install them?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Theres An .sbf I Used To Get The Update Easily
Just Make Sure You Back Up Everything
(.sbf Is Used By RSD Lite Just In Case You Didn't Know)
hmm...
Ok, well, im not all that familiar with what your talking about...
I soppose I kinda did the opposite when it comes to removing integral apps on the phone, but from what im reading, im mostly hosed aren't I?
How do i find this .sbf and how would i use this RSD to restore?
I apologize in advance for being such a noob.
Time to start learning about your Droid X. It's all here, in this forum and in the development forum. Check out the Wiki first. There's a link to it on the first post of the android development forum.
Your problem is easily solved btw.
http://www.droidxforums.com/forum/d...oll-your-320-dx-back-2-3-151-now-you-can.html
Download the backup there, boot into CWM and restore from that image. You'll get all the crapware back and will be able to OTA. Alternatively you can go to 928droid.com and download the clean DX image.
I called Verizon about not being able to update with the OTA and they are sending me a new phone lol!
Sent from my DROIDX using XDA App
Erickomen27 said:
Theres An .sbf I Used To Get The Update Easily
Just Make Sure You Back Up Everything
(.sbf Is Used By RSD Lite Just In Case You Didn't Know)
Click to expand...
Click to collapse
I did a little research and found that i have the 30.04 boot loader. My attempts at locating what i guess is referred to as a "system only SBF" have been futile. Is there somewhere i can find this? what is the name of the file i need, i know links cannot be posted.
I attempted at restoring the apks to the phone via adb (applied proper permissions etc). I got the apks back, and the apps running properly (backupassistantclient.apk ... etc) however, to no avail it still will not update.
hmmm 30.04. TMK only the leaked 2.3.320 SBF and the official OTA use that bootloader. Are you sure the update didn't work? Maybe your brand new phone already has the update? Settings->about phone->Android version should tell you. 2.2.1 = the OTA.
Sleuth255 said:
hmmm 30.04. TMK only the leaked 2.3.320 SBF and the official OTA use that bootloader. Are you sure the update didn't work? Maybe your brand new phone already has the update? Settings->about phone->Android version should tell you. 2.2.1 = the OTA.
Click to expand...
Click to collapse
Actually, I've had that bootloader on 2 separate X's; one I bricked on a system only leak of .320 and one I ended up using the leaks to get to .340(wouldn't OTA, possibly because I forgot to fix permissions). I know because at one point I SBFed the phone from .151 to .15 and I saw the bootloader version.
quinnteq said:
I did a little research and found that i have the 30.04 boot loader. My attempts at locating what i guess is referred to as a "system only SBF" have been futile. Is there somewhere i can find this? what is the name of the file i need, i know links cannot be posted.
I attempted at restoring the apks to the phone via adb (applied proper permissions etc). I got the apks back, and the apps running properly (backupassistantclient.apk ... etc) however, to no avail it still will not update.
Click to expand...
Click to collapse
Sleuth is correct--there is a full (as opposed to "system only") 2.3.32 SBF that works with 30.04. As has been previously suggested, all of the info on finding this file and installing it are contained in the wiki (which is located on the xda droid x dev page). It really isn't a big deal to resolve your issue. Learning to unbrick your phone with RSD will be extremely useful to you in the future, as will the time you spent screwing around with ADB.
I give you props for trying to resolve your issue yourself, rather than crying to Verizon the first time you ran into trouble
ok, so i got it to SBF finally! it worked. now i have 2.2.1. But i no longer have root access, gaaha! what gives! anyway... any good tip to restore root access?
I am glad i know how to do the SBF processes, im not so leery about installing custom roms on my DX anymore... which is my end goal now that i can do the SBF for this boot loader.
However, how to do i get root access again?
Reroot your phone however you did the first time.... I used z4root, took some time to get it work... but eventually got it to work
Sent from my DROIDX using XDA App

Don’t try OTA 4.5.141 with a rooted phone

I was getting "Failed to boot 2 starting RSD mode" error and when my Atrix tried to reboot to install the OTA update. The only way I could get to boot again was to remove the battery and put it back, and after that, it boots normally to the home screen, and after the SD card gets mounted it shuts down to try to install the OTA update and you get the same error again.
I got it working again by following the suggestions from Atrixforums.com. What I did was to flash my phone with RDS lite v5.6 using the file 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011 and that fixed my phone and it’s been working normally.
If you can get your phone to the home screen without rebooting or you get a different type of error, you could try the Automated Update (PC Users Only) from Motorola website (I need confirmation if this would work with a unlocked bootloader)
Details:
My phone was using the stock rom version 2.3.4
Rooted (I did not remove the root access before applying OTA 4.5.141 and this is reason why I got in this problem)
Locked bootloader (I am not sure if this would work with unlocked bootloader)
Unlocked sim card
I hope it helps,
Already posted in Dev section:
Warning 1
Warning 2
Search before posting :>
Alaq said:
Already posted in Dev section:
Warning 1
Warning 2
Search before posting :>
Click to expand...
Click to collapse
Those threads reference problems with unlocked phones. The OP has a rooted phone that is not unlocked. So, not a dupe per se.
That said, I upgraded my rooted-only phone with no issues. I rather suspect the OP may have unlocked his bootloader and forgotten about it.
You can OTA 141 with a locked and rooted phone. Just be sure to unroot (you need to do this manually if you ever used the fastboot preinstall method) and make sure everything is back to stock. If you used oneclick or any other root method that has an unroot, manually verify it really removed everything (su, superuser.apk, etc).
gnahc79 said:
You can OTA 141 with a locked and rooted phone. Just be sure to unroot (you need to do this manually if you ever used the fastboot preinstall method) and make sure everything is back to stock. If you used oneclick or any other root method that has an unroot, manually verify it really removed everything (su, superuser.apk, etc).
Click to expand...
Click to collapse
I have used the one click easy method only and nothing else. And I agree with you, it seems that not unrooting your phone before the OTA update creates this problem. I’ll be more careful the next time when the ICS it’s available.
I just want people like me that it’s not been in the android scene for long, do not get in to this kind of problems.
It would probably be a good idea to post a check list every time a new update comes up, reminding us of the precautions that we must have. Because even if you know what you are doing If you forget just one little change you made it could lead to some problems.
Greetings,
btw, here is what I did to unroot prior to the 141 update. I rooted 2.3.4 with the fastboot preinstall method...no idea if this unroot method cleans up the one click method.
link
1. Open Android Terminal Emulator
2. Type in the following commands, hitting ENTER after each line of code: (after typing 'su' below, look for the Superuser request and approve it, you can only continue if you get the # prompt.
Code:
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o rw,remount /dev/block/mmcblk0p17 /preinstall
rm /system/bin/su
rm /preinstall/sqlite3
rm /preinstall/dosu
rm /preinstall/Superuser.apk
rm /preinstall/su
reboot
3. Let the phone reboot fully and then go into Settings > Applications > Manage Applications > find Superuser and uninstall it just like any other app.
Click to expand...
Click to collapse
I am was also facing the same issue with OTA. I finally managed to update my rooted, locked phone via USB method using Motorola Software Updater.
Root is lost after the update.
I did the OTA on my atrix which was locked and rooted. Updated fine without any problems, but I did lose root. Can't figure out which method is safe to use to re-root.
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
k00ey said:
I did the OTA on my atrix which was locked and rooted. Updated fine without any problems, but I did lose root. Can't figure out which method is safe to use to re-root.
Click to expand...
Click to collapse
live4nyy said:
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Click to expand...
Click to collapse
I used this method and it worked fine. It did give an error message that superuser was already installed but it rooted the phone anyway.
Sent from my MB860 using Tapatalk
live4nyy said:
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Click to expand...
Click to collapse
Thank you! Worked great.
charlyee said:
I used this method and it worked fine. It did give an error message that superuser was already installed but it rooted the phone
Click to expand...
Click to collapse
Charlyee, did you unroot your 4G with the preinstall method prior to following these instructions? Please confirm. Thanks!
badnokia said:
Charlyee, did you unroot your 4G with the preinstall method prior to following these instructions? Please confirm. Thanks!
Click to expand...
Click to collapse
I did the root saver method but I had all kinds of problems doing the OTA, so I ended up by downloading the software from the Moto website via USB.
At that point my Atrix was unrooted, but I don't know if it was the root saver method or download of the software.
I tried Motofail to root as well but that didn't work.
Hope that helps.
Sorry, didn't mean to write a thesis in answer to a simple question.
Sent from my MB860 using Tapatalk
Is it safe to use the aRoot unroot method if my Atrix is rooted and unlocked in order to update to 4.5.191?
Confirmed Success: Unroot, OTA Update, Root
Sorry if this info is redundant, but I'm super paranoid about the OTA updates & wanted to confirm what I did worked for my rooted, but locked Atrix 4G:
1) Unrooted with the directions on this page: http://www.atrixforums.com/forum/mo...ons-including-stock-locked-2-3-4-2-3-6-a.html
2) Ran OTA update
3) Rooted again with the following instructions: http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
I just did sucessful update on my unlocked and rooted Motorola Atrix 4G (MB860) from 2.3.4 to 2.3.6 via RSDLite 5.6, and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf SBF file.
Windows 7 64-bit Ultimate. Everything passes O.K.
I had this happen on my atrix rooted no unlocked bootloader I reflashed with the above method nd success. I unrooted my wife's atrix first and installed the ota with no problems. So unroooting first seemed to work.
Sent from my MB860 using XDA App
I did not have a problem at all updating to 4.5.141 with a rooted phone minus the fact I lost root until I saw the link live4nyy posted.
Just an FYI for others like me that have been waiting to pull the trigger on the update.
I was rooted with the /preinstall (briefmobile) method (had never unlocked the bootloader). I read conflicting reports on whether OTA would work, and for some reason I couldn't get the Motoroloa update program to see my phone. Rather than figuring out why it wasn't seeing my phone, I did the "unroot" steps listed by gnahc79 in this thread and then let the phone update OTA and then rooted again using the /preinstall method.
The whole process took about 30 minutes, most of that was the OTA download and install.
Did you guys have to re-hack mobile hotspot after the OTA update?
Sent from my Motorola 2-way pager

[XOOM2/XYBOARD][HOW TO] Motorola Xoom 2/Xyboard Everything Root and more!

XOOM2/Xyboard Everything root and more!
From 26/03/2014, I will no longer be updating this post as I no longer have the device and Motorola won't be upgrading the device further. Please instead of sending me PMs, go to the Q&A board or post your comment on this thread.
Note: This method will not work on Windows 8. Only Windows XP, Vista, 7, Linux and Mac OS X is supported.
Root Method - Honeycomb
1. Download the Windows version here, or the Linux/OSX version here.
2. Your Computer must have Motorola Drivers installed before rooting and connect your device with debugging on to your computer via USB. (Mac Users don't need drivers)
3. Extract the zip file from the download link, and run “run.bat” (on Windows) or “run.sh” from a terminal (on Linux/OSX)
4. Your device should reboot a few times during the process, don't worry.
5. Then you should see a finished message on the Root Method Window. At this point your device is safe to be removed from the computer.
7. As you are running Honeycomb if you are reading this then you should be receiving the ICS OTA soon. So lets backup your root so you can restore everything root after the upgrade (saves time). Download OTA Rootkeeper and backup root.
6. Well Done! You have root. Enjoy root and be safe.
Blog Post: Here
Root Method - Ice Cream Sandwich
1. Connect your Xoom2/Xyboard via USB to your Windows PC. Install Motorola Drivers from here.
2. Under Settings > Developer Options > Hit the "Enable USB Debugging" selection.
3. Download the Root Installer from here. (Says for Droid RAZR but also works on Xyboard and Xoom 2]
4. Unzip the download.
Bootstrap/Safestrap[Custom Recovery]
Waring: DO NOT proceed if you are inexperienced. bootstrap is messy and is only needed once we have ROMs cooking. All questions about the recovery ask in the developer thread.
1. Install the Bootstrap APK file.
2. Allow Superuser Powers.
3. Read the instructions which is displayed on the user interface.
5. You will now see a splashscreen after you reboot (before boot animation), here you can decide if you want to enter recovery or continue with boot.
-Method Under Constuction-
Unroot or temporary unroot
Temp Unroot - If you need to unroot for any reason and come back at any time, then install OTA Rootkeeper and then select the option "temp unroot). This will remove root without restarting and you can restore by a touch of a button.
Full remove of Root - If you want to complety remove root all together, if you need to send in your device for repair or trading your device. Install Ginger Unroot and continue with the onscreen instructions. This application has confirmed to work on the Xoom2/Xyboard.​
Doing it right now
Linux version has a wrong link or not uploaded yet
mdcykkk9 said:
Linux version has a wrong link or not uploaded yet
Click to expand...
Click to collapse
Should be working now.
Thx is working now . i just made a donation to his paypal account. i hope for future support for the tablet .
Thanks, is good news. Now we just need that we have updates to fix bugs, and if it can be ics ...
This is worth a donation to continue the work.
édit : error, sorry, it's ok
Working well ! Thank you.
I rooted my Xoom 2 ME bought in France.
But I cannot update to 3.2.2 ???
My build 1.6.0_218.3-MZ607 ,current version 3.2
Would this work for Xoom 1 wi-fi version ?
ouatitw said:
Would this work for Xoom 1 wi-fi version ?
Click to expand...
Click to collapse
This root method should work on all Motorola Devices running honeycomb or gingerbread. Try it out and see if it does
Sent from my Motorola Xoom 2
I did the US ICS update on My UK Xoom so im on 4.03 at the moment - i believe Motorola added some file which prevents me so far from rooting with the current one click programs ? so would it be safe to try this ?
ouatitw said:
I did the US ICS update on My UK Xoom so im on 4.03 at the moment - i believe Motorola added some file which prevents me so far from rooting with the current one click programs ? so would it be safe to try this ?
Click to expand...
Click to collapse
The method is safe to try but Email Dan if you have any issues when rooting.
Thanks a lot Dan Rosenberg,
Suppose i root my device and if i need to use my warranty at later point of time.
Is there is anyway that i can hide Motorola that i have rooted my device.
luke.arran said:
The method is safe to try but Email Dan if you have any issues when rooting.
Click to expand...
Click to collapse
I wouldn't email Dan, I'd post it here... Dan probably has more than enough things going on than to answer all rooting questions on here...
This root method very well may work on the Xoom with ICS, never hurts to try it. I don't see how you can't root with an existing method though, with the Xoom being fully unlockable and all...
Elysian893 said:
I don't see how you can't root with an existing method though, with the Xoom being fully unlockable and all...
Click to expand...
Click to collapse
the thing is that maybe you can, but you might not want to Unlocking wipes all your data, apps, etc and also permanently sets a variable stating that your warranty is gone.
It might, for example, be desireable to create a backup of all your apps and data using titanium backup, which requires root, before unlocking your xoom.
Does this mean that more knowledgeable folks can create custom ROMs now, or does that still require an unlocked bootloader?
Trackz said:
Does this mean that more knowledgeable folks can create custom ROMs now, or does that still require an unlocked bootloader?
Click to expand...
Click to collapse
No, we need to figure out a bootstrap for custom roms. No custom kernels.
Also, the method to fix adb remount is reset every other boot by the kernel, init.rc rebuilds local.prop on reboot as a failsafe and can't be changed without a custom kernel...
Response to luke.arran
luke.arran said:
This root method should work on all Motorola Devices running honeycomb or gingerbread. Try it out and see if it does
Click to expand...
Click to collapse
Just to let you know this does not work on all Xoom models like you say. Here is my thread with my specs in it. I have tried it three times following the directions to a T and it never gets past;
"[*] Initiating Phase 1...
[*] This may take a few minutes, don't mind the buzzing."
I have now let it run for over an hour each time and it never goes any further and my Xoom is still not rooted. It did not even ever reboot on its own. Does anyone have any suggestions? If not I'll just use some threads 1 & 2, I got from a friend.
Thanks, InfiniteImmortal
llama-power said:
Unlocking wipes all your data, apps, etc
Click to expand...
Click to collapse
Not this method. It is supposed to unlock and root motorola devices in 10 minutes without deleting any files. When I read about this on android police I was very excited as I never rooted because I only needed Superuser for my Xoom (never was interested in ROMs) and could never justify scraping everything just for this.
I tested the files here on a windows 7 machine... if I run from command at step 2. I get su permission denied. If I run the batch file I get "failed backup" loop after the device has been detected
tried the portable one click .exe found in "Motofail: Universal Motorola Android Root Tool (Portable)" works perfect on my bionic
obviously fails to remount as it does not include local.prop from step 5. so it's not working on xoom
This is the most awesome root utility I ever came along. It took something like 6 mins to root my phone without losing any files, if I can get it to run on my Xoom this will be just a dream come true!
Update: This root method does not support the Original Xoom. Confirmed by Dan.

Easy 2 click root: How I got to 4.2.2 Camera Update/Rooted and WP permanently Off

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:

buying a new razr m to root?

I'm entirely new to anything phone/development related so I apologize for my ignorance (I also apologize if this is in the wrong section). I've had a razr M for about 2 years now and I'm entirely content with it except after the last update I can no longer use my foxfi for wifi access. From what I understand I can't root my phone and downgrade from this operating system so my question is this: Can I buy a new one off ebay for ~$100, root it and use foxfi (or some other free wifi tether) while keeping my unlimited data and not "bricking" it? The battery on my current phone has gone to crap anyways and I was considering buying a replacement phone considering they're only ~$100 anyways.
It's a pain in the but trying to figure all of this out with only limited time to browse the internet at work and trying to sort the 100's of pages of info from my phone.
Is this feasible? Are there certain things I need to verify about a phone before I buy it to make sure I can complete this process?
Thanks in advance,
Rory
If you're on the latest firmware, you CAN root with Towel Root and unlock with Motopocalypse. Then you can downgrade back to JB. There's a method posted by @bweN diorD somewhere in this forum.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
If you're on the latest firmware, you CAN root with Towel Root and unlock with Motopocalypse. Then you can downgrade back to JB. There's a method posted by @bweN diorD somewhere in this forum.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Thanks RikRong! How do I know if I'm on the latest firmware (does that just mean the latest operating system? My phone says 4.4.2 so I'm assuming that's a yes)? Sorry, there's a thousand new terms and I'm struggling to take in what this all means.
When it comes to trying to root my phone, since I have no more foxfi I also don't have a way to have internet access on my computer/tablet to walk me through the rooting process/assist me if something goes wrong with the... would you think it's intuitive enough/fullproof that if I print out the thread I can just follow it through and shouldn't have issues? Also, I looked through the first 4 or 5 pages in this forum and didn't find any threads started by "bweN dior" but I'm probably just overlooking what I'm looking for. Do you know what the thread was titled?
Thanks,
Rory
http://forum.xda-developers.com/showthread.php?t=2783157
Install .apk and run
Profit
Don't forget to thank geohot
rypkr937 said:
Thanks RikRong! How do I know if I'm on the latest firmware (does that just mean the latest operating system? My phone says 4.4.2 so I'm assuming that's a yes)? Sorry, there's a thousand new terms and I'm struggling to take in what this all means.
When it comes to trying to root my phone, since I have no more foxfi I also don't have a way to have internet access on my computer/tablet to walk me through the rooting process/assist me if something goes wrong with the... would you think it's intuitive enough/fullproof that if I print out the thread I can just follow it through and shouldn't have issues? Also, I looked through the first 4 or 5 pages in this forum and didn't find any threads started by "bweN dior" but I'm probably just overlooking what I'm looking for. Do you know what the thread was titled?
Thanks,
Rory
Click to expand...
Click to collapse
actually, i didnt make a guide for this model. i made it for the hd/maxx hd. the root and bootloader unlock is the same and you can use those files, but you can NOT use any of the phone specific software in the guide or you will likely brick your phone.
http://forum.xda-developers.com/showthread.php?t=2789743
bweN diorD said:
actually, i didnt make a guide for this model. i made it for the hd/maxx hd. the root and bootloader unlock is the same and you can use those files, but you can NOT use any of the phone specific software in the guide or you will likely brick your phone.
http://forum.xda-developers.com/showthread.php?t=2789743
Click to expand...
Click to collapse
Yeah, I saw that it was someone else that made the guide for the M, but I like how yours is set-up. I was going to point him to your thread in the HD forum for rooting and unlocking, then refer him to guide in the M forum for downgrading. Use Bwen's guide to use Towel Root and Motopocalypse. Get TWRP from here: http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img and flash a SU zip to gain permanent root. Then use this guide to downgrade: http://forum.xda-developers.com/showthread.php?t=2786016 .
RikRong said:
Yeah, I saw that it was someone else that made the guide for the M, but I like how yours is set-up. I was going to point him to your thread in the HD forum for rooting and unlocking, then refer him to guide in the M forum for downgrading. Use Bwen's guide to use Towel Root and Motopocalypse. Get TWRP from here: http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img and flash a SU zip to gain permanent root. Then use this guide to downgrade: http://forum.xda-developers.com/showthread.php?t=2786016 .
Click to expand...
Click to collapse
Okay, I'm trying to start this process. From my droid, I downloaded http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img but immediately I'm encountering problems. My phone says it cannot open this file. I'm already dreading this is going to be difficult/dangerous...
Why can't I open this file? Also, what is flashing a SU zip?
There is far too much about this I don't understand.
I am willing to pay someone to root a razr m for me. Do I have any takers?
Towel Root and Motopocalypse are both apps that you can download to the phone and then run. They're just apps, so they are as easy as opening the app then running. You need to use Towel Root, then Motopocalypse to unlock, and then you can install TWRP. If you don't want to use fastboot to install recovery, then you can flash it with Rashr or Flashify. Just download TWRP and place on your external SD, no need to open or extract it. Flash it with one of those apps. Once you're rooted and unlocked, you should be able to use that guide to downgrade.
Sent from my HTC6525LVW using Tapatalk
rypkr937 said:
Okay, I'm trying to start this process. From my droid, I downloaded http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img but immediately I'm encountering problems. My phone says it cannot open this file. I'm already dreading this is going to be difficult/dangerous...
Why can't I open this file? Also, what is flashing a SU zip?
Click to expand...
Click to collapse
just use the tutorial i posted before as a guide, substituting the files @RikRong gave you for the recoveries.
i just updated the guide to include a complete step by step for flashing the recoveries and su zip.
the only thing you will need is fastboot and adb in the same folder with your recovery file.
the guide instructs to use adb and fastboot from my script, but you wont have my script. thats why you need to grab adb and fastboot from google.
its not difficult, you just dont understand what needs to be done. you dont open the recovery with the phone booted up. just read the guide and subsequent link to the step by step and you will quickly see where you are going wrong.
http://forum.xda-developers.com/showthread.php?t=2789743
just a quick disclaimer for those not following along, ^^^^^ the firmware and recoveries in this guide are for the 926 only!!! use it for reference only!! any other files in the guide and the guide itself, is universal.
rypkr937 said:
There is far too much about this I don't understand.
I am willing to pay someone to root a razr m for me. Do I have any takers?
Click to expand...
Click to collapse
Please refer to this thread > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Now I think I got problems. I thought I had it all figured out with all of the walkthroughs. I have the phone in fastboot mode and I was flashing it with RSD for the previous firmware. It was going through the steps and on 7/20 it said failed flash. I tried again and now it says failed flash after 1/20. I'm afraid to try and boot the phone. What should I do?
rypkr937 said:
Now I think I got problems. I thought I had it all figured out with all of the walkthroughs. I have the phone in fastboot mode and I was flashing it with RSD for the previous firmware. It was going through the steps and on 7/20 it said failed flash. I tried again and now it says failed flash after 1/20. I'm afraid to try and boot the phone. What should I do?
Click to expand...
Click to collapse
If your boot loader isn't unlocked, you can't flash older FW. Did you unlock already?
Sent from my HTC6525LVW using Tapatalk
rypkr937 said:
Now I think I got problems. I thought I had it all figured out with all of the walkthroughs. I have the phone in fastboot mode and I was flashing it with RSD for the previous firmware. It was going through the steps and on 7/20 it said failed flash. I tried again and now it says failed flash after 1/20. I'm afraid to try and boot the phone. What should I do?
Click to expand...
Click to collapse
It says USB error. I unplugged it from the computer and tried it again. It's step 7/20 "flash modem "non-hlos.bin" where it is getting screwed up.
RikRong said:
If your boot loader isn't unlocked, you can't flash older FW. Did you unlock already?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Yes. I think? I did these steps successfully
-----------------------------------------
2. BOOTLOADER UNLOCKING
-----------------------------------------•Download Towel Root [XDA] [WEBSITE] - Disregard if you have previously rooted using Towel Root
•Download Motopocalypse [WEBSITE] [DOWNLOAD]
•Place both on external SDcard
•Install and run Towel Root
•Follow any in-app prompts
•Reboot
•Install and run Motopocalypse
•Follow any in-app prompts
•Reboot
•PROFIT!
My error specifically says this:
Failed flashing process. 7/20 flash modem "non-hlos.bin" -> USB error occurred while reading/writing.
I unplugged it and tried another USB port and it went through all the steps 20/20. Then it rebooted my phone and the phone says "please wait, this may take a few minutes". After several minutes RSD told me to "manually power on the phone". Since the phone was never shut off I couldn't do this so I unplugged the USB and replugged it in thinking maybe there was another USB error. RSD has now finished and says result is "PASS". However my phone still says "please wait, this may take a few minutes". Should I let me phone be or should I restart it?
rypkr937 said:
I unplugged it and tried another USB port and it went through all the steps 20/20. Then it rebooted my phone and the phone says "please wait, this may take a few minutes". After several minutes RSD told me to "manually power on the phone". Since the phone was never shut off I couldn't do this so I unplugged the USB and replugged it in thinking maybe there was another USB error. RSD has now finished and says result is "PASS". However my phone still says "please wait, this may take a few minutes". Should I let me phone be or should I restart it?
Click to expand...
Click to collapse
do the 3 button trick to get into flash mode and tell us what the status code is please.
bweN diorD said:
do the 3 button trick to get into flash mode and tell us what the status code is please.
Click to expand...
Click to collapse
power + volume up + down rebooted me to a screen that asked me to select my language (just as before). After selecting English it goes back to the "please wait this make take a few minutes" screen.
It's working!!!! I just ran RSD again (and this from the start on a usb 2.0 port as I read 3.0 can screw it up). This time it worked like a charm! I'm back on jellybean and posting from my laptop through a foxfi connection from my phone! SO thankful for this and those who did the write ups/walk throughs and posted in here! I got a lot of apps and setting to update ahead of me ugh. I'm going to do some donating here for the help! Thanks to those who posted in this thread and the ones who made those write ups and the app developers!
How do I keep my phone from automatically updating back to KK?? I didn't let it update when KK originally came out (I just kept clicking postpone) until about a month or two later it just updated on it's own. Well my phone just started automatically downloading a system update again. I put it in airplane mode but how do I keep this update from happening again and getting screwed by KK again?

Categories

Resources