Hello All!
This is my guide to rooting, recovering, and "romming" the Motorola Droid Razr M!
ROM: CyanogenMod 10.1 Official
DISCLAIMER: All software that I will provide links to is AS-IS. I will NOT be responsible for anything that happens to your phone as a result of this guide
Lets Begin!
Pre-Reqs:
- All download links are in the text document below. I am not allowed to post outside links because this is my first post
-Razr M
-OEM Cable
-Software Version must be < 98.18.78.XT907.Verizon.en.US (If software is 98.18.78 and you haven't unlocked your bootloader follow this guide (link in text document below) to only root your device )
-Android Jelly Bean 4.1 (I did mine with 4.1.2. Not sure it will work on ICS)
-Battery % > than 90 %
-Patience
-MAKE SURE TO BACK EVERYTHING UP (CONTACTS, DATA, TXTS, ETC)!!
Part 1 (Rooting):
Step 1: Obtain the "motochopper.zip" file (Credit to Dan Rosenberg)
Step 2: Extract the zip
Step 3: Make sure to have the latest windows drivers for phone (If not on windows skip this step):
Step 4: Connect M to computer and make sure usb debugging is enabled (allows computer to "talk" to phone)
Step 5: Navigate to motochopper folder and click "run.bat"
Step 6: Follow on-screen instructions
Step 7: Jump for joy because you now have root!
Step 8: Proceed to Part 2
Part 2 (Bootloader):
Step 1: Obtain the "motopocalypse.zip" file (Credit to Dan Rosenberg)
Step 2: Extract the zip
Step 3: Connect M to computer
Step 4: MAKE SURE that you have root!!!!!
Step 5: Click "run.bat"
Step 6: Follow on-screen instructions
Step 7: Confirm that the bootloader is unlocked (Status code 3 or "Warning Bootloader Unlocked!" Screen on boot up)
Step 8: Proceed to Part 3 if confirmation is successful
Part 3 (Recovery/ROM):
Before you proceed you must be sure that you actually want to install a ROM on your device. My choice was CyanogenMod 10.1 Official for the Razr M.
If you find some other guide that has a safer way of doing this the use that one.
Step 1: Obtain a recovery image. I chose ClockworkMod 6.0.3.2
Step 2: Put this file inside of the "motopocalypse" folder
Step 2.1: Grab the CyanogenMod 10.1 Official Zip and the gapps package
Step 2.2: Put these files on the root of your Android phone (/sdcard) or on a microSD and put it into your phone
Step 3: From the command window type: "adb reboot-bootloader" and hit enter. You should be greeted with a familiar screen;
Ok, here is where the guides on the internet failed me. On the official cyanogenmod blog for the Razr M, it says to issue: "fastboot flash recovery your-recovery.img" and then "fastboot boot your-recovery.img". This first command worked but the second one didn't and I was unable to ever boot into CWM. That's when I had to turn to this command: "fastboot flash boot recovery.img". What this command does is replace your boot sequence (correct me if i am wrong) with CWM. So when you reboot, it will only boot into CWM. This is why your have to be serious about putting a ROM on your device. Installing a ROM fixes the boot sequence.
Step 4: If you want to continue issue the command: "fastboot flash boot your_recovery_filename.img" If you want to turn back now issue the command: "fastboot continue"
Step 5: If it installed the recovery correctly then issue "fastboot reboot"
Step 6: You will now hopefully boot into CWM.
Step 7: Use volume keys to scoll and power to select
Step 8: Choose wipe_data/factory_reset and confirm the choice
Step 9: Choose "install zip from sd" and select the CyanogenMod package. Confirm and you will see it install
Step 10: Choose "install zip from sd" and select the Gapps package. Confirm and you will see it install
Step 11: On the main menu select "reboot phone now"
Step 12: If everything was successful you will boot into CyanogenMod 10.1 Official!
Step 13: Set everything up.
Step 14: Proceed to Part 4
Part 4 (Recovery again/ Finishing up):
Step 1: Everything may seem ok, but you don't have a recovery partition anymore
Step 2: Connect M to computer if it isn't anymore
Step 3: Hold down vol+, vol-, and power at the same time to get to boot menu. Select bootloader with vol- and select it with vol+
Remember my big spiel earlier about how these commands didnt work. Well now they do! I suspect that the didn't work before because Verizon's OEM Android kept overwriting your custom recovery
Step 4: Go to "motopocalypse" folder and Issue "fastboot flash recovery the-same-file-you-flashed-earlier.img"
Step 5: It will succeed and then issue "fastboot continue"
Step 6: Now you have your recovery partition back! You can now boot into it from the boot menu or from the cyanogenmod menu
Step 7: Not over yet! Boot back into CyanogenMod and go to settings
Step 8: In Android 4.2+ the developer settings are disabled. To fix this tap on the build number in the "about phone" section 10 times
Step 9: From now on to use adb your will need to get the updated adb files for Android 4.2+ :
Step 10: You may notice that the screen has some kind of weird refresh bug when you scoll. To fix this, check the Developer Setting item that says "Disable HW overlays"
Step 11: Enjoy
Thank you guys so much for reading this guide and I hope you found it very helpful!
If you have any questions or problems leave a comment or just PM me. I will do my best to help you out.
Cheers,
Ryan (carb0nrain)
it works
it works on the Razr M 201M softBank.
Will this work with the latest OTA?
I know the latest OTA was supposed to have removed the unlock exploit. If I follow all the intructions will I still be able to root AND unlock?
Root with the latest OTA update
Forveralon said:
I know the latest OTA was supposed to have removed the unlock exploit. If I follow all the intructions will I still be able to root AND unlock?
Click to expand...
Click to collapse
This guide is only meant for people how don't have the latest OTA update. The latest OTA update removed the bootloader unlock exploit which means that you can't install a custom recovery or ROM. However, there is still a way to root your M with the latest OTA update. Look at the first link in the text document above (I can't post links directly in replies because i am a fairly new member). Hope this helps!
Cheers,
Ryan
I am the op of the other method in the dev forum.
Seems we approach it from opposite ends. Do we get the same results?
I need to check yours out....
Different Ends
aviwdoowks said:
I am the op of the other method in the dev forum.
Seems we approach it from opposite ends. Do we get the same results?
I need to check yours out....
Click to expand...
Click to collapse
This is how it worked for me. (See attached pic) Which part did we do differently. If anything is wrong, please feel free to correct me.
Cheers,
Ryan
Do you want to be on the old radio-...81p? The new is in my goodies...78p.
Radio
aviwdoowks said:
Do you want to be on the old radio-...81p? The new is in my goodies...78p.
Click to expand...
Click to collapse
Could you explain to me what the radio file is? And what is the difference between the 81p and the 78p radios. This is one of the subjects that i still dont know much about.
Thanks
Just flash it from recovery. It is from 981878.
Radio
aviwdoowks said:
Just flash it from recovery. It is from 981878.
Click to expand...
Click to collapse
Thanks
Could one of you in the know, please give the system versions that allow root? I just bought a Razr M, that came with 98.16.1.XT907 and the one click root worked fine. There is a nag wanting to do a OTA for version 98.16.3 but I keep telling it "later" as I do not know if that version is rootable. Is it?
Thank you, and I hope this helps someone else.
Rumblur said:
Could one of you in the know, please give the system versions that allow root? I just bought a Razr M, that came with 98.16.1.XT907 and the one click root worked fine. There is a nag wanting to do a OTA for version 98.16.3 but I keep telling it "later" as I do not know if that version is rootable. Is it?
Thank you, and I hope this helps someone else.
Click to expand...
Click to collapse
The new version is rootable but you can't unlock the bootloader. If you are still on the older version, you're lucky. Unlock the bootloader and don't take the update until afterwards. Even if you don't use it, you might regret not unlocking the bootloader because the update blocked the bootloader unlock exploit. Look for the RazrM Utility 1.20. It has the root method, bootloader unlock, recovery flash tool, and recovery tool all in one package.
RikRong said:
The new version is rootable but you can't unlock the bootloader. If you are still on the older version, you're lucky. Unlock the bootloader and don't take the update until afterwards. Even if you don't use it, you might regret not unlocking the bootloader because the update blocked the bootloader unlock exploit. Look for the RazrM Utility 1.20. It has the root method, bootloader unlock, recovery flash tool, and recovery tool all in one package.
Click to expand...
Click to collapse
So if I read you right, you're saying go ahead and unlock the bootloader, root it, take the OTA (just the one I mentioned or all of them? I think there's one even newer than that if not two) and then using the tool you mentioned, root it again?
Rumblur said:
So if I read you right, you're saying go ahead and unlock the bootloader, root it, take the OTA (just the one I mentioned or all of them? I think there's one even newer than that if not two) and then using the tool you mentioned, root it again?
Click to expand...
Click to collapse
Yeah, pretty much, but you'll need to root first, then unlock the bootloader (use utility 1.20 for this). After that, you can take the OTA and reroot by using Motochopper 1.3 or by just flashing a SU zip in recovery. The utility can be used on the previous update only, not the newest one. Another option for you after you unlock the bootloader and install a custom recovery, is using one of the stock based ROMs on this forum or Batakang. There are a couple of stock based, pre-rooted ROMs running around here.
RikRong said:
Yeah, pretty much, but you'll need to root first, then unlock the bootloader (use utility 1.20 for this). After that, you can take the OTA and reroot by using Motochopper 1.3 or by just flashing a SU zip in recovery. The utility can be used on the previous update only, not the newest one. Another option for you after you unlock the bootloader and install a custom recovery, is using one of the stock based ROMs on this forum or Batakang. There are a couple of stock based, pre-rooted ROMs running around here.
Click to expand...
Click to collapse
OK, I took the 3.1.6 update and the bootloader is still unlocked. I tried using the utility 1.20 afterwards and the root (option 5) failed. It said "SU already exists". If I uninstall SU would that help and then it take root? Or, is there another version of motochopper that I need to find and download?
Rumblur said:
OK, I took the 3.1.6 update and the bootloader is still unlocked. I tried using the utility 1.20 afterwards and the root (option 5) failed. It said "SU already exists". If I uninstall SU would that help and then it take root? Or, is there another version of motochopper that I need to find and download?
Click to expand...
Click to collapse
If your bootloader is unlocked and you have an aftermarket recovery installed, all you need to do is flash a SU zip in recovery.
RikRong said:
If your bootloader is unlocked and you have an aftermarket recovery installed, all you need to do is flash a SU zip in recovery.
Click to expand...
Click to collapse
No aftermarket (that I know of, but I'm rusty on this stuff as this is the first thing I've done since the HTC Inc2). I just found a DL for motochopper 1.1.2 and used it. I downloaded a root checker from the store and it says "this device has root access". So I guess I'm good!
While I have your help and attention here, I've looked at the ROMs listed on this site but there is not much information about why one is better than another etc. I'm perfectly fine with the stock phone "IF" it has root (which it does now) and IF the weird shutdown/lockup thing goes away. My other #1 main concern is anything that will increase reception.... I am leaving the Inc2 behind for that very reason... horrible reception.
Rumblur said:
No aftermarket (that I know of, but I'm rusty on this stuff as this is the first thing I've done since the HTC Inc2). I just found a DL for motochopper 1.1.2 and used it. I downloaded a root checker from the store and it says "this device has root access". So I guess I'm good!
While I have your help and attention here, I've looked at the ROMs listed on this site but there is not much information about why one is better than another etc. I'm perfectly fine with the stock phone "IF" it has root (which it does now) and IF the weird shutdown/lockup thing goes away. My other #1 main concern is anything that will increase reception.... I am leaving the Inc2 behind for that very reason... horrible reception.
Click to expand...
Click to collapse
If you want to run a custom ROM, you'll need to install TWRP or CWM. If you want to get the best reception, stick to stock and just tweak it, or find one of the customized/deodexed/tweaked stock ROMs running around here. I've had no issues with aftermarket ROMs and signal, but many people have complained about weaker reception on the aftermarket ROMs.
many thanks. I will check out the deodexed stuff. Is there any preference or reason to pick TWRP over CWM or vice versa? One last question after that.... when I had a Droid X, when I was ready to sell it I used a SBF CD to put it back to bone stock OEM. Is there something like that for the M?
Rumblur said:
many thanks. I will check out the deodexed stuff. Is there any preference or reason to pick TWRP over CWM or vice versa? One last question after that.... when I had a Droid X, when I was ready to sell it I used a SBF CD to put it back to bone stock OEM. Is there something like that for the M?
Click to expand...
Click to collapse
I prefer TWRP because it's easier use. Also, it seems to work better than CWM for the 4.3 ROMs that are out now. Yeah, you can run a XML in RSD and restore to stock. Here's a complete listing of Moto firmware.
http://sbf.droid-developers.org/
Related
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices and has clocked over 9.5 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
- Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Are you having fastboot driver issues? You can find fastboot drivers in many places, but the easiest way is probably just installing the Android SDK.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
Download
2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download: CF-Auto-Root-manta-mantaray-nexus10.zip
--- History ---
2013.05.20: SuperSU v1.30
2013.02.20: SuperSU v1.05
2012.12.02: SuperSU v0.98
Thanks!
Newbie question: Does CF-Auto-root unlock the bootloader as well? (probably not, as I understand from your post and that's what I want, but I want to be sure...)
case-sensitive said:
Thanks!
Newbie question: Does CF-Auto-root unlock the bootloader as well? (probably not, as I understand from your post and that's what I want, but I want to be sure...)
Click to expand...
Click to collapse
From the OP... i marked in bold the important part.
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
case-sensitive said:
Thanks!
Newbie question: Does CF-Auto-root unlock the bootloader as well? (probably not, as I understand from your post and that's what I want, but I want to be sure...)
Click to expand...
Click to collapse
No, this does not unlock the bootloader it only gives you root acess and installs the SuperSu app. To unlock the bootloader you must use fastboot and type the command:
fastboot oem unlock
I would suggest taking a look at mskip and wugfreshs toolkits located in the original development and development section of the nexus 10 forums respectively for a simple way to unlock your bootloader.
Sent from my SCH-I535 using xda premium
Good to see nexus 10 getting all this support from Android gurus here on xda ...but again it's a nexus device ...me glad I bought it ...extremely happy with my purchase thanks chainfire for this easy root method as usual it works
So if this doesn't unlock your device, why does the OP state:
Note that if your device had not been unlocked before, this procedure will wipe all your data !?
Does rooting/installing SU wipe this device?
His previous version didn't wipe the device, so I'm guessing this one doesn't either
Didn't need to unlock boot loader to root
shimp208 said:
No, this does not unlock the bootloader it only gives you root acess and installs the SuperSu app. To unlock the bootloader you must use fastboot and type the command:
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Are you sure? The script in the ZIP in OP has the following command:
Code:
tools\fastboot-windows.exe oem unlock
Does that not issue a unlock? Is it necessary to run this command?
hi there, not sure how to get this to work
its giving error because it can't find adbwinapi.dll
I installed the sdk for 4.2 already, not sure what i am missing
Thanks for help
d0nald01 said:
hi there, not sure how to get this to work
its giving error because it can't find adbwinapi.dll
I installed the sdk for 4.2 already, not sure what i am missing
Thanks for help
Click to expand...
Click to collapse
Please re-download, I've included the missing file in the new package.
now its stuck at waiting for device
when i plug in my n10 on bootloader screen, i hear the bad connection to usb sound, the 3 note sound, not the usual 2 note sound when i the connection is good.
but i am still able to see my n10 when i boot it up normally and can transfer files etc
am i missing something?
Thanks for this tool, works perfectly.
I'm also stuck on "waiting for device" also. any way around this?
Edit: Downloading and installing full drivers fixed it.
Big thanks, I was stuck in a bootloop, but this got me out of it!
Worked perfect (Debian)
Happy new year guys
Does CF Auto Root support JB 4.2.1 on the Nexus 10 yet?
Thanks
idefix_sin said:
Happy new year guys
Does CF Auto Root support JB 4.2.1 on the Nexus 10 yet?
Thanks
Click to expand...
Click to collapse
Sure, I used it again to root the device after taking the 4.2.1 update.
Hi, I've just bought n10. I want be sure if this procedure will wipe my data? I read that unlocking cause wipe everything. But I don't need it, root is enough Thanks for help.
From the first post:
Chainfire said:
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Click to expand...
Click to collapse
mieszk3 said:
Hi, I've just bought n10. I want be sure if this procedure will wipe my data? I read that unlocking cause wipe everything. But I don't need it, root is enough Thanks for help.
Click to expand...
Click to collapse
Seems pretty obvious to me. I didn't put it in bold red letters because it's irrelevant.
hello everyone,
i am very new to rooting and all that
i have the htc m8 international version
i have a problem with the mic as no one can hear me and i need to get it to the agent under warranty.
i cant do that unless i atleast unroot the phone
i cant S off with firewater as i get the error msg from them that i shouldnt try again
any help?
would really appreciate the help
anyone?
I think you do not have to have s-off in order to unroot your phone.
mohammed_usif7 said:
hello everyone,
i am very new to rooting and all that
i have the htc m8 international version
i have a problem with the mic as no one can hear me and i need to get it to the agent under warranty.
i cant do that unless i atleast unroot the phone
i cant S off with firewater as i get the error msg from them that i shouldnt try again
any help?
would really appreciate the help
Click to expand...
Click to collapse
That doesn't help a lot you know, seems people have varied definitions of what it means to be "rooted"
If I should go by what I know happens in order to use the SuperSU app then the reverse would be.
Unroot - Open SuperSU, go to settings, scroll down to "Full unroot".
Stock Recovery - Go to this thread and select your stock recovery version.
Once you found the version, download it, extract the zip file and move it(recovery.img file) to the adb/fastboot folder(You MUST have used this method before in order to flash custom recovery in order to root your device). Once you moved it to said folder, open a command prompt from within that folder >>> hold shift, right click and select "Open command prompt/window here".
Connect device to computer, type in adb devices to make sure your device gets detected. If it shows your serial number all is good, type in adb reboot bootloader to boot into bootloader mode, once your done booting into HBOOT, type in fastboot flash recovery name_of_recovery.img For the love of all that is holy, REMEMBER TO UNZIP/EXTRACT the .zip file you downloaded!!! before doing this.
Once that is done type in fastboot oem lock to lock the bootloader again, this will "relock" the bootloader and will show as such. Once that is done, type in adb reboot to reboot the device back into the OS and you're done.
Though I don't see what the point is really, mic problem is most likely as a result of hardware failure not software and as such they can't try and put the blame in your shoes because you unlocked, flashed custom recovery and rooted your device.
jwsm said:
I think you do not have to have s-off in order to unroot your phone.
Click to expand...
Click to collapse
i deleted the su folder and everything from twrp
i still cant update my phone
when i do that it takes me to recovery mode
So you have rooted your phone and installed a custom recovery(twrp) and are trying to return everything back to stock because you have to send the phone in for repair, correct?
If so, all you have to do is to unroot and flash the stock recovery back. Just follow the directions in BerndM14's post. OTA updates require that you have the stock recovery on your phone. They will not work if you have a custom recovery like twrp installed.
never mind got it
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
What are you talking about? Before unlocking have you checked OEM unlocking from Developer tools? After this you need to flash Twrp, boot into it directly from bootloader and flash SUPERSU. That should be the minimal steps in order to keep the custom recovery in place.
HaiKaiDo said:
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
Click to expand...
Click to collapse
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
You do need some knowledge so take a look at the howto conversation http://forum.xda-developers.com/showthread.php?t=3206930
, this is my go to tool since my Nexus 4 http://forum.xda-developers.com/showthread.php?t=3258492
Darke5tShad0w said:
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
Click to expand...
Click to collapse
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
HaiKaiDo said:
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
Click to expand...
Click to collapse
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
wtoj34 said:
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
HaiKaiDo said:
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
Click to expand...
Click to collapse
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
wtoj34 said:
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
Click to expand...
Click to collapse
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Well i went and redid everything the same way I did the first time and it worked! I must done something stupid the first time. Guess this thread was for nothing! xD Thanks for clarifying some things for me though guys.
HaiKaiDo said:
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Click to expand...
Click to collapse
Disabling encryption does give you a speed increase. It may or may not be noticeable for your use but the majority can see the difference.
So you have to decide between security and a snappier phone.
Just remember to back all your data up as this requires wiping your data and possibly a clean flash and either switching from the stock rom to another rom(Most have the forced encryption disabled) or when on stock rom either flash another kernel or flash supersu in systemless mode.
Hotspot need it Help! Nexus 5x
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Varsismaname said:
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Click to expand...
Click to collapse
You need to go and start your own thread in the q&a section, its not polite to high jack someone else's.
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
I forgot to mention that when I try to use the and side load it says something about the e drive, like if there es no drive on my phone
rectangularspace said:
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
Click to expand...
Click to collapse
Do you know and understand how you use fastboot or the Deuces script to flash factory images to return you to stock OS?
Well not really. But I follow many instrucciones from differents post and nothing
rectangularspace said:
Well not really. But I follow many instrucciones from differents post and nothing
Click to expand...
Click to collapse
Read over this thread. Then let us know if you need help. https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Also, if you have twrp installed, you can flash the OTA zip that corresponds to your current OS version :good:
I do have twrp installed the problem is that I don’t have the zip on the phone to install the ota file.
Try with deceus Script (Just search for it) and select repair bootloop. It will download the factory Image and flash it on a and b partition then your phone will boot again. But your data will be lost :/
Ok., I will let you guys know thank you
Also, I forgot to mention that it looks like that I don’t have a OS installed ( twrp is telling me that every time i try to get out to the get out of the twrp menu. At this point i haven’t don’t anything mention in this post because I’m resetting my computer nd I’m installing right now the android sdk software.
You don't have to install the full Android SDK software for the job you're trying to do. You can download the latest Fastboot commands and ADB through Google, or even XDA(somewhere).
I've installed adb to my Windows commands, so once in recovery, when I need a file, I just "adb push file.zip /sdcard/".
No worries though. You'll be back up and running. ?
Edit: Also, if you still have data on your phone, you can check using the file explorer on TWRP. If you do, you can adb pull anything you want to keep.
@rectangularspace Link to the standalone platform tools HERE. This is all you need.
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Yes, but going down from 9 to 8 will cause/require a data wipe.
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Why did you decide to install Oreo?? There will be no further security or functionality updates for 8.1. The next monthly update to Pie should be the first Monday of next month (October 1st) if you don't get a OTA nag before then.
I have the update available to install on my settings. But what I'm looking for is to start over on rooting my pixel 2 xl. But after last experience I'm a little conservative when it comes to mess with the phone. I'm reading right now the post where it says to do the critical unlock for the phone but I don't know witch bootloader version I have. Can you guys help me out
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
rectangularspace said:
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
Click to expand...
Click to collapse
You only need to do the unlock process one time, BUT there are two separate unlock commands which include unlock_critical. If in doubt you can use fastboot device-info or getvar to check the current status. Make sure you are using the latest version of the platform tools I linked to above. One word of caution... don't EVER re-lock your bootloader or you WILL run into problems. Even if you are returning the phone to Google for RMA you do not need to re-lock it.
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
rectangularspace said:
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
Click to expand...
Click to collapse
I meant the only way to lock the bootloader will be thru a fastboot command.
rectangularspace said:
I meant the only way to lock the bootloader will be thru a fastboot command.
Click to expand...
Click to collapse
Yes, once you have successfully unlocked the phone in fastboot using the two separate commands, you will never have to do it again, AND flashing anything will not re-lock the bootloader. Please read over Nathan's GUIDE HERE to confirm you have done this correctly (and completely). Once this is done you can flash OTA's , full Google images, custom roms, etc. Lastly, if you are properly unlocked you cannot brick your phone. No matter how bad it gets, you will always have a path to restore the phone to it's original state. Don't hesitate to take the OTA being offered on your phone. It will take you to 9.0 without losing data or locking anything. :good:
Hi --
Old Galaxy Tab Pro 10.1 running kitkat. I am using CF Auto Root to root it via Odin and I get the "pass" in Odin but then it just reboots into the existing OS and Supersu is not on the device. The instructions I have been following say that you should try again but switching off the "auto reboot" in odin. I did that, but it just remains in download mode. The instructions said to take out the battery...which, not really an option for the tablet.
I believe I followed all other instructions: I have the correct CF Auto Root file for my build; I have the drivers from Samsung ...
Any advice is appreciated.
tojotojo said:
Hi --
Old Galaxy Tab Pro 10.1
Click to expand...
Click to collapse
Which one?
tojotojo said:
running kitkat......
Click to expand...
Click to collapse
So you want to keep that?
If not why don't you flash TWRP and Lineage?
bmwdroid said:
Which one?
So you want to keep that?
If not why don't you flash TWRP and Lineage?
Click to expand...
Click to collapse
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
tojotojo said:
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
Click to expand...
Click to collapse
And , obviously, terminology may be/probably is "off" here (newbie and all) ... but I believe there's a step before being able to flash TWRP and Lineage - whether that's "rooting" or "unlocking" or whatever. I'm basically still "stock" at this point.
tojotojo said:
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
Click to expand...
Click to collapse
I see.
Imo it's necessary 1st of all to make sure it's on latest stock to have latest bootloader.
Flashing TWRP with Odin is extremly easy.
Here is a post/thread although written for S4 valid for most others as well.
Written a how-to myself as well but the english part is not as up-to-date as the german is.
tojotojo said:
And , obviously, terminology may be/probably is "off" here (newbie and all) ... but I believe there's a step before being able to flash TWRP and Lineage - whether that's "rooting" or "unlocking" or whatever. I'm basically still "stock" at this point.
Click to expand...
Click to collapse
No unlocking necessary with that old device.
Rooting means having SU or Magisk but flashing works without as well.
bmwdroid said:
No unlocking necessary with that old device.
Rooting means having SU or Magisk but flashing works without as well.
Click to expand...
Click to collapse
Great, will give this a shot later today. Appreciate the help!
Well, didn't get very far. My understanding is that you have to unlock the OEM bootloader under developer options...which, ... well, I don't have that option listed once I've accessed the developer options. Tried a bunch of options -- factory reset, changed date/time to long ago .... used Smart Switch to check for updates (which one post said would prompt it to appear. Any options for getting this modded without the OEM bootloader unlock option? One post somewhere said that having the USB debugging option checked would work, but .... questionable.
tojotojo said:
Well, didn't get very far. My understanding is that you have to unlock the OEM bootloader under developer options...which, ... well, I don't have that option listed once I've accessed the developer options.
Click to expand...
Click to collapse
As I said: not on this old device
tojotojo said:
Tried a bunch of options -- factory reset, changed date/time to long ago .... used Smart Switch to check for updates (which one post said would prompt it to appear. Any options for getting this modded without the OEM bootloader unlock option? One post somewhere said that having the USB debugging option checked would work, but .... questionable.
Click to expand...
Click to collapse
Just use Odin to flash latest TWRP,
Reboot to that TWRP,
Wipe everything plus "Format Data"
Flash suiting ROM and test if it works
reboot to TWRP and flash Gapps fitting this ROM version (I prefer Bitgapps ARM)
Be happy
@tojotojo remember that Odin can only flash .tar and .tar.md5 files
TWRP.....img are to flash later in an old TWRP to get a newer one.
you need check off auto-reboot. it still in dload-mode, then press power to reboot and just as you see it starts boot press recovery-mode key combination to enter recovery. if you are slow, tab will load default system without ur root and recovery. i hope this help you.