Related
[Q] Having trouble figuring out rooting & recovery works on Moto X coming from Nexus
I'm no noob, I've been rooting for a while, but I can't figure out how to root this damn thing . On a Nexus, I just unlocked, flashed TWRP, then flashed superuser from TWRP, and I was done. How does it work on this phone? Can I just flash TWRP and then from TWRP flash a root zip? I'd rather not use any toolkits and such (which seem to be all the rage on this forum). Running Pure edition btw. On latest Lollipop OTA.
mateopase said:
I'm no noob, I've been rooting for a while, but I can't figure out how to root this damn thing . On a Nexus, I just unlocked, flashed TWRP, then flashed superuser from TWRP, and I was done. How does it work on this phone? Can I just flash TWRP and then from TWRP flash a root zip? I'd rather not use any toolkits and such (which seem to be all the rage on this forum). Running Pure edition btw. On latest Lollipop OTA.
Click to expand...
Click to collapse
Yes its pretty much the same, the forums are abit immature at the moment there aernt any proper guides, i just did things the Nexus way
unlock your bootloader first through motorola, following the instructions (make sure there are no spaces in the unlock key): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
flash twrp, then install the superSU zip from adb sideload or from your internal storage if it was already downloaded
youre done
also, you could flash the stock logo image to remove the warning boot image, http://forum.xda-developers.com/moto-x-2014/development/warning-message-unlocked-bootloader-t2871478 to make things look nicer
IINexusII said:
Yes its pretty much the same, the forums are abit immature at the moment there aernt any proper guides, i just did things the Nexus way
unlock your bootloader first through motorola, following the instructions (make sure there are no spaces in the unlock key): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
flash twrp, then install the superSU zip from adb sideload or from your internal storage if it was already downloaded
youre done
also, you could flash the stock logo image to remove the warning boot image, http://forum.xda-developers.com/moto-x-2014/development/warning-message-unlocked-bootloader-t2871478 to make things look nicer
Click to expand...
Click to collapse
Awesome, thanks. Looks like that's what I'll end up doing. I really messed up my phone though when trying to get back to stock. Hopefully my stock image request will be approved soon and I'll be able to go through the process again.
One more question, if I kinda messed up restoring everything to 4.4.4, but I can boot the phone properly, will updating to 5.0 via an OTA update fix any mistakes I made along the way?
mateopase said:
One more question, if I kinda messed up restoring everything to 4.4.4, but I can boot the phone properly, will updating to 5.0 via an OTA update fix any mistakes I made along the way?
Click to expand...
Click to collapse
Not necessarily. The ota contains only changed files (not all files) and therefore if something is wrong with a file that wasn't changed (including anything in /data) then it will still be broken after the update.
crpalmer said:
Not necessarily. The ota contains only changed files (not all files) and therefore if something is wrong with a file that wasn't changed (including anything in /data) then it will still be broken after the update.
Click to expand...
Click to collapse
Alright. Do you know of any way to return to stock without going through Motorola's waiting game. It's been a few hours now and I still haven't been approved for the download.
mateopase said:
Alright. Do you know of any way to return to stock without going through Motorola's waiting game. It's been a few hours now and I still haven't been approved for the download.
Click to expand...
Click to collapse
Honestly, I haven't looked at what options are available for images to flash.
When I asked for firmware, I believe that I asked on a Friday evening and received access on the following Monday morning. So maybe you'll get access in another 15-16 hours? That is your safest bet if your phone is working well enough to last you until then.
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
shabydog said:
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
Click to expand...
Click to collapse
AFAIK you will need a pc to 1)unlock your bootloader and 2)flash TWRP. After that the rest can be done locally. I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Droidphilev said:
I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Click to expand...
Click to collapse
Second that.
shabydog said:
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Click to expand...
Click to collapse
So at least once you need to connect your phone to a desktop computer. It can be practically running anything, within reason of course: Wiindows. Mac OSX, Linux (almost any distro).
You need to unlock your bootloader with one command, but a warning here: Unlocking the bootloader will erase everything from your phone..
Then you need to install a custom recovery, preferably TWRP. After that everything can be done from the phone itself. Well at least until you soft brick it somehow, then you'll might have to use the PC again.
Also two things:
1. No OTAs for rooted phones
2. Don't lock your bootloader if you want to mess with it, because with a locked bootloader, and Enable OEM Unlocking set to off, and without TWRP, if you soft brick it accidentally, you are boned.
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use?
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
And i really prefer to do it on the device and not by ADB commands.
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
shabydog said:
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
Click to expand...
Click to collapse
Well, you still will have to unlock it, if you want root, or want to flash a custom recovery.
Sent from my Nexus 6 running cyosp using Tapatalk
shabydog said:
......I really don't like the issue of trying to set the drivers of fastboot/google and so on!
Click to expand...
Click to collapse
Than do not 'root' your phone.
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
simms22 said:
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
Click to expand...
Click to collapse
Ha ha, or I don't want my birthday to be on the day I was born every year ?
I can recommend the NTRT, the Nexus Telepathic Rooting Tools.
OK.
I want to do that with a toolkit, only bcs it install the drivers.
What Is the most recommended and easiest to use?
I do looking for the 1 click do all.
Does NTRT do that?
Thank you all.
we are eventually goung to have a "my n6 is bricked, how do i fix it with one click" thread here. seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Sent from my Nexus 6 using Tapatalk
shabydog said:
Could anybody guide me through the steps, if needed?
Click to expand...
Click to collapse
<prev> step <next>
simms22 said:
seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Click to expand...
Click to collapse
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
wtherrell said:
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Click to expand...
Click to collapse
It is fairly enough to read directions and slowly-slowly.
NLBeev said:
<prev> step <next>
Click to expand...
Click to collapse
Thanks!
==========================================================
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
Click to expand...
Click to collapse
i agree with you. if there is somebody who knows the ins and outs already, a one click root would be great. and there will be. problem is that marshmallow just came out, and a few things have changed, like like yoe also need a custom kernel to have root on marshmallow.
shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
It is fairly enough to read directions and slowly-slowly.
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
Click to expand...
Click to collapse
There is a reason you're pushing this topic, and I'm quite sure it's because you would feel safer, if there was a tool that did the scary things instead of you. Well, there's no such tool. If you were willing to search XDA, you would find out that the first two weeks after Marshmallow came out were about people bricking their Nexus 6s with toolkits. Then the toolkit got updated and suddenly it knew that is has to flash a modified boot.img too for the root not to brick the phone. But for two weeks it didn't know, because it wasn't necessary for Lollipop. And it will only work until the next security update comes out. And that's once a month.
Meanwhile those who were willing to use the search function, and learned the five minute procedure, were able to update their rooted phones to the next security update and were able to root it as soon as the new modified boot image came out.
And this above is not something somebody will put in a help, or instructions for future updates.
Actually, this is my first time and I was able to do it pretty easily.
fastboot devices
fastboot oem unlock
my bootloader was unlocked within 30 seconds of turning it on.
then, you can easily root via CF Auto root. Just put it into fastboot then doubleclick on the windows, then root, etc....
or.............go into fastboot flash recovery twrpxxxx.img, then it always offers to run SuperSU, and you get custom recovery and root at the same time, etc......
actually the biggest pain is unlocking the bootloader. My Galaxy S4 already was unlocked, so all I did was use goomanager, flash TWRP which always offers to run SuperSU if you don't have it.
Pretty easy, I did unlock bootloader, root, and custom recovery in 10 min.
---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------
............................Then I got sick of stock Google's ROM in 15 min and wiped it and put a custom ROM instead.
Thank you all so much...
@mikeprius
Thank you so much for the info'!
But, could you plz write more details? such as:
1. How did you installed the drivers? (from my expirience, many times the pc dosent install this easily).
I just need the Google oem driver and that's it?
2. When drivers was set - did you made anything in your phones settings? Which?
3. What did you had to do before pushing the files? (Like...put all the files in the same folder? *which files?)
4. And then entered to fastboot mode and typed in these commands in pc:
fastboot devices
fastboot oem unlock
Regarding your last sentence ("or...."):
If i just flash the recovery via fastbot mode I can enter to twrp recovery and it offers to flash the SuperSU?
Sounds to me the best option.
Thanks!
1. The drivers were set from a previous device, so I didn't have to set them, but they can be downloaded and set though.
2. You need to enable developer options and select OEM unlock and USB debugging.
3. I didn't push the files, I just had them on my computer and ran fastboot commands.
4. Those commands are to unlock the bootloader.
There are a lot of different ways to do the same thing (Root, custom recovery, unlock bootloader)
1. Run CF Auto Root on a locked bootloader. It will unlock it automatically (Chainfire has it set that way), root, then download Flashify app and flash the latest img of TWRP.
2. Run fastboot commands to manually unlock the bootloader, flash TWRP, then use TWRP's SuperSU which will root it.
3. Run fastboot commands to unlock bootloader, run CF Autoroot which will root and load SuperSU, then flash TWRP via Flashify or fastboot.
There are many different ways to do the same thing. I actually just googled youtube videos and watched them.
TWRP has SuperSU and root built in. TWRP knows if you don't have it and offers to load it for you.
I went the scenic route just because, but presumably you can achieve all (3) using Option #1 without having to deal with fastboot, adb, etc.....Chainfire's script runs automatically.
I realy try to help people but users that run into problems because of the usage of tookits (and innability to solve problems and/or even lack the most basic knowledge needed) should ask the toolkit dev. for support imo, and not boughter users that have invested time and effort to gain that knowledge to clean up their mess. Period
Please excuse me if this is a simple process, but I cannot seem to locate a thread on how to flash to -44, as I am slowly in the process of trying to root my Turbo.
Currently living off of FoxFi USB tethering, but finally would like to obtain root access since it is available as I miss having wifi tethering!
I'd like to add, that the process of rooting this phone is a bit more advanced than what I have done over the years. I'm used to plugging the phone in the PC, installing a software on the PC, then "one click" root and reboot.
Any insight or recommendations is greatly appreciated! Tethering is my main reason for root, but I'd still like the versatility of having root access.
Thanks XDA!
coconutt said:
Please excuse me if this is a simple process, but I cannot seem to locate a thread on how to flash to -44, as I am slowly in the process of trying to root my Turbo.
Currently living off of FoxFi USB tethering, but finally would like to obtain root access since it is available as I miss having wifi tethering!
I'd like to add, that the process of rooting this phone is a bit more advanced than what I have done over the years. I'm used to plugging the phone in the PC, installing a software on the PC, then "one click" root and reboot.
Any insight or recommendations is greatly appreciated! Tethering is my main reason for root, but I'd still like the versatility of having root access.
Thanks XDA!
Click to expand...
Click to collapse
THIS METHOD WILL VOID YOUR WARRANTY. But if you're on xda, chances are you knew that. It's also irreversible.
If you're not unlocked and not rooted, take the OTA that is available to get you to -44. 44 is the most recent version available, so there is no risk of updating too far.
Once you're on 44, download the Kingroot apk and install it. http://www.kingroot.net/
Then download this version of Sunshine and install it. http://forum.xda-developers.com/showpost.php?p=64027688&postcount=4064
Once both are installed, open Kingroot and follow the instructions to try and get temporary root. It doesn't always work, and sometimes you have to try multiple times. If it fails, uninstall Kingroot, reboot the phone and try again. Wiping cache in the recovery menu sometimes helps too.
After Kingroot says it is successful, run Sunshine and follow the prompts. Sunshine costs $25, so if you're not cool with that, don't try this method. If Sunshine succeeds, your phone will reboot and instead of the Motorola M that you usually see at boot, you'll see a bootloader unlocked warning message. If Sunshine fails, uninstall Kingroot, reboot, reinstall and try again.
Once your bootloader is unlocked, you need to get a custom recovery installed (TWRP), which you can get here http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308. The easiest way to flash that in my opinion is with Fastboot. The easiest way to install Fastboot is by installing this: http://forum.xda-developers.com/showthread.php?t=231779. You'll also need to make sure you have the appropriate drivers so that your PC will recognize your phone. This will ensure that: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Put the TWRP .img file that you downloaded into the folder that you installed Minimal ADB and Fastboot to, boot your phone in bootloader mode, plug it in to the computer, start Minimal ADB and Fastboot, and type the following command:
fastboot flash recovery <name of TWRP .img file>
Once you have that, the sky is the limit. If you only want to add permanent root to your phone, download this: http://forum.xda-developers.com/showthread.php?t=1538053, put it somewhere on your phone, boot into recovery mode (which will now be TWRP instead of the stock recovery), select install, navigate to the .zip file and flash it. That's it. If you want to try cyanogenmod or any other custom rom, see their respective xda threads for details.
Oh, and as for enabling tethering for free, which is only necessary if you have an unlimited data plan (if not, it's free already, just use Verizon's app to do it), find any root browser, search for a file called build.prop, open it with the browser's text editor and add this line to the end of it:
net.tethering.noprovisioning=true
Remember to save when you're done.
---------- Post added 7th December 2015 at 12:00 AM ---------- Previous post was 6th December 2015 at 11:45 PM ----------
If you need more help, this guy might explain better than I did: http://forum.xda-developers.com/droid-turbo/general/videos-tutorials-root-restoring-droid-t3076456
http://forum.xda-developers.com/showthread.php?t=2317790
Link for minimal adb and fastboot, I think this is the right one?
TheSt33v said:
THIS METHOD WILL VOID YOUR WARRANTY. But if you're on xda, chances are you knew that. It's also irreversible.
If you're not unlocked and not rooted, take the OTA that is available to get you to -44. 44 is the most recent version available, so there is no risk of updating too far.
Once you're on 44, download the Kingroot apk and install it.
Oh, and as for enabling tethering for free, which is only necessary if you have an unlimited data plan (if not, it's free already, just use Verizon's app to do it), find any root browser, search for a file called build.prop, open it with the browser's text editor and add this line to the end of it:
net.tethering.noprovisioning=true
Remember to save when you're done.
Click to expand...
Click to collapse
Sorry for the late reply as I'm having the free time to fidget with the phone.
To my understanding about taking the OTA that is available to me is not the Marshmallow update? I have a screenshot of the OTA when it pops up each night, but not sure if I'm allowed to img code it on here. But it displays "New version: 23.21.44.en.US"... I'd just like for you to confirm that this is the -44 update before I advance, thanks a bunch!
Also, I tried the buildprop edit on my current -39 version and it won't let me save the file. I take it this can be done after rooting though.
coconutt said:
Sorry for the late reply as I'm having the free time to fidget with the phone.
To my understanding about taking the OTA that is available to me is not the Marshmallow update? I have a screenshot of the OTA when it pops up each night, but not sure if I'm allowed to img code it on here. But it displays "New version: 23.21.44.en.US"... I'd just like for you to confirm that this is the -44 update before I advance, thanks a bunch!
Also, I tried the buildprop edit on my current -39 version and it won't let me save the file. I take it this can be done after rooting though.
Click to expand...
Click to collapse
Yep. That's it. The marshmallow update isn't out yet, so it cannot be the marshmallow update. Build.prop is located on the system partition, which is write-protected on a stock Turbo. Once you unlock with Sunshine (just rooting with Kingroot isn't good enough), you will be able to edit it. Also, Sunshine no longer needs Kingroot. Simply download the latest version here http://theroot.ninja/download.html and use it to unlock once you're on -44.
TheSt33v said:
Yep. That's it. The marshmallow update isn't out yet, so it cannot be the marshmallow update. Build.prop is located on the system partition, which is write-protected on a stock Turbo. Once you unlock with Sunshine (just rooting with Kingroot isn't good enough), you will be able to edit it. Also, Sunshine no longer needs Kingroot. Simply download the latest version here therootdotninja/download and use it to unlock once you're on -44.
Click to expand...
Click to collapse
Well that was easy! Bootloader unlocked!! Thanks.
Now on to the rooting process. Currently getting my Moto drivers updated on the PC, and I've also downloaded the TWRP file onto the PC as well. As for Fastboot, the link you've provided takes me to a 2005 thread! I'm sure I can find a link to Fastboot to download, but I wanna make sure I get the one I need, if that makes any sense? (Don't mind me being paranoid)
TheSt33v said:
Put the TWRP .img file that you downloaded into the folder that you installed Minimal ADB and Fastboot to, boot your phone in bootloader mode, plug it in to the computer, start Minimal ADB and Fastboot, and type the following command:
fastboot flash recovery <name of TWRP .img file>
Click to expand...
Click to collapse
For an update, I got everything I needed downloaded. I am stuck at this point though, as I can't get passed this point when I input the above command!
EDIT:
I skipped the recovery flash, and went ahead with just the build prop edit for tethering after installing King Root. Rebooted it and still have root, and tethering works. Thanks a bunch!!
coconutt said:
For an update, I got everything I needed downloaded. I am stuck at this point though, as I can't get passed this point when I input the above command!
EDIT:
I skipped the recovery flash, and went ahead with just the build prop edit for tethering after installing King Root. Rebooted it and still have root, and tethering works. Thanks a bunch!!
Click to expand...
Click to collapse
If you want twrp flashify works well.
Tip: When you receive your Fire 2015 tablet, don't setup WiFi if you want to install custom ROM (skip WiFi setup)
Why: They are still shipping with FireOS 5.0.1 and it will autoupdate to 5.1.1 as soon as it sees Internet connection (it doesn't ask and takes over tablet)
Why is that bad: Because it's easier to install custom ROM with 5.0 and still a pain/riskier if from 5.1.1 (as of December 2015)
Why is this method easier/safer: No need to root first, no messing with original ROM (can backup first), no need to enable Developer mode, no need to grant ADB permissions
Prerequisites:
- This method will not work if tablet has upgraded to FireOS 5.1.1 or higher, only 5.0.x works
- Need fastboot tools installed on a computer (Windows tools/drivers here if needed) or (Linux/Mac)
- Download TWRP Recovery here to same computer
- Download your new ROM/support files of choice to an external SD Card
- If on Windows, to keep things simple you might place fastboot command, Recovery image in same folder/directory
Install: Fastboot TWRP Recovery from computer, Install Custom ROM from SD Card
- When you receive Fire, don't power it on (or if you do, don't setup WiFi as it will autoupdate to 5.1.1)
- Copy your downloaded ROM image and support files to an SD card, then insert SD into tablet
- Boot tablet directly into fastboot (power button and volume up button)
- USB attach tablet to computer that has fastboot tools and TWRP recovery image
- Unlock and Boot directly into TWRP image from computer terminal or command line
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot boot TWRP_Fire_2.8.7.0_adb.img
- Takes seconds to transfer file then recovery should appear
- Optional but recommended: From TWRP, Backup Stock Amazon ROM to external SD card
- Factory Reset from TWRP Recovery
- Install ROM and support files from TWRP via external SD card
- Reboot, profit
Just bought another tablet and this method worked again. Went straight to doing this before even booting.
xenokc said:
Just bought another tablet and this method worked again. Went straight to doing this before even booting.
Click to expand...
Click to collapse
Did you buy it from Amazon? I just ordered mine yesterday.
stef-nix said:
Did you buy it from Amazon? I just ordered mine yesterday.
Click to expand...
Click to collapse
Yes, am interested if yours came with 5.0 or 5.1.1. If you boot, dont setup Wifi (skip setup) or will autoupdate - it doesn't ask so be careful. Can then check version.
xenokc said:
Yes, am interested if yours came with 5.0 or 5.1.1. If you boot, dont setup Wifi (skip setup) or will autoupdate - it doesn't ask so be careful. Can then check version.
Click to expand...
Click to collapse
It came with 5.0.1, I'm going to pull out the root script as soon as I turn it on.
stef-nix said:
It came with 5.0.1, I'm going to pull out the root script as soon as I turn it on.
Click to expand...
Click to collapse
You don't need to root it with the above method. Just go straight into fastboot and launch recovery via computer as described, backup stock ROM then install your ROM (then flash or enable root in developer mode within tablet). I trashed a tablet trying to root it with current methods, which is why I came up with this method.
xenokc said:
You don't need to root it with the above method. Just go straight into fastboot and launch recovery via computer as described, backup stock ROM then install your ROM (then flash or enable root in developer mode within tablet). I trashed a tablet trying to root it with current methods, which is why I came up with this method.
Click to expand...
Click to collapse
Gotcha. As soon as I opened it, I blocked OTA updates. Rooted/installed SuperSU, and backed up the stock ROM.
I'm currently running CM12.1 and it's working perfectly.
I did not like how it auto signed into my Amazon account once connecting to WiFi (with OTAs blocked)
Many thanks for this. I'm completely new to modding in any way, shape or form, so this is very helpful.
I have seen another thread (http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416) which suggests that running CM should be possible now with OS 5.1.1 (my tablet has unfortunately updated since shipping). I have also currently run the script contained within http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804, and was wondering whether it would still be possible to follow the instructions here to install CM, or is it necessary to first restore the Fire tablet back to factory settings (if this is possible)?
Thank you in advance for any help!
Parhelius said:
Many thanks for this. I'm completely new to modding in any way, shape or form, so this is very helpful.
I have seen another thread (http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416) which suggests that running CM should be possible now with OS 5.1.1 (my tablet has unfortunately updated since shipping). I have also currently run the script contained within http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804, and was wondering whether it would still be possible to follow the instructions here to install CM, or is it necessary to first restore the Fire tablet back to factory settings (if this is possible)?
Thank you in advance for any help!
Click to expand...
Click to collapse
Did your tablet come with 5.1.1 out of the box? Or did you just connect to wifi and the updates came through?
stef-nix said:
Did your tablet come with 5.1.1 out of the box? Or did you just connect to wifi and the updates came through?
Click to expand...
Click to collapse
I connected to wifi and the updates came through automatically. I hadn't read threads like this one beforehand unfortunately, so I didn't realise that would happen.
Sounds like Amazon is still shipping with 5.0.1 so this method can still apply for those who catch this thread before receiving/booting their tablet. What's nice about this method is you can backup original ROM before modding and don't need to root. Sounds like many have thrashed their tablet trying to root.
Just dont connect to wifi and your fine.
Amazon having a $40 sale, if you ordered one might not setup WiFi when first receiving - re-read first post why.
http://www.amazon.com/Fire-Display-Wi-Fi-GB-Includes/dp/B00TSUGXKE
Just ordered 3 today ... Can't wait to tinker with it.
Thanks for the heads up regarding auto-update!
I've gotten 3 in the last week or so. One came from a small town up north (sorry, shipping details have disappeared from my history) with 5.0.1 and the other two came from Ft. Worth, TX with 5.1.1. I too think everyone should enter recovery immediately when the thing arrives, and then fastboot boot twrp.img to see what happens. I was hoping that if I declined the "Link to my Amazon Account" option, they would pull an older one from stock. Looks like I'm 1 for 3. All 3 have some issues (stuck pixels, backlight bleedthrough) so I'm getting a 4th one from Ft. Worth tomorrow.
percussionking said:
I've gotten 3 in the last week or so. One came from a small town up north (sorry, shipping details have disappeared from my history) with 5.0.1 and the other two came from Ft. Worth, TX with 5.1.1. I too think everyone should enter recovery immediately when the thing arrives, and then fastboot boot twrp.img to see what happens. I was hoping that if I declined the "Link to my Amazon Account" option, they would pull an older one from stock. Looks like I'm 1 for 3. All 3 have some issues (stuck pixels, backlight bleedthrough) so I'm getting a 4th one from Ft. Worth tomorrow.
Click to expand...
Click to collapse
Did you try the steps in this thread with the 5.1.1 unit sright out of the box?
Does this still work, or behaved differently with 5.1.1 ?
I'm waiting for my units to make their way to me. Really interested to see what your experience with the 5.1.1 units.
Thnx!
vn33 said:
Did you try the steps in this thread with the 5.1.1 unit sright out of the box?
Does this still work, or behaved differently with 5.1.1 ?
I'm waiting for my units to make their way to me. Really interested to see what your experience with the 5.1.1 units.
Thnx!
Click to expand...
Click to collapse
My 4th one came from Ft. Worth. I immediately booted into recovery mode but could not boot TWRP. Obviously this turned out to be a 5.1.1 system. If this had been a 5.0.1 system, the first full boot would have been to CM rather than to stock. So if 5.1.1 is installed at the factory you can't get your TWRP on this way.
Just got mine today it had 5.0.1 creating a backup now
Hi,
where can you download twrp from their page?
I see their list of devices but none of them says fire 5th generation.
https://twrp.me/Devices/
THANK YOU!
No you get twrp from here http://forum.xda-developers.com/amazon-fire/development/wip-bootable-recovery-kffowi-ford-t3238683
Root instructions on the RP2 forum seem to assume a level of familiarity with rooting, and general instructions on the web seem to want to cover every possible device which means they cover every means of rooting options and device types and Android versions, and it isn't clear reading those where to start with the RP2.
I've found people on XDA tend to be pretty welcoming to dumber questions, so here's my dumb question.
If I have an "unlocked" (non-AT&T) device running 9 Pie, can someone translate this post:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454
Into usable instructions for those of us new to rooting? I have a Windows computer, a USB-A to USB-C cable (since the C-to-C cable that comes with the phone isn't suitable?), and an unrooted Razer Phone 2 on Pie.
I enable developer options in my phone's settings by tapping the version 7 times. I got that part.
Now, what do I download to my device? A boot image and magisk (?)? The boot image from the thread above, right? How do I ensure what I download to my phone goes to my phone and not the SD card? Is that a dumb question? Do I just remove the SD card before downloading anything?
Then what do I download to my computer? The Android SDK, or some smaller thing? Fastboot something something? ADB something something?
Then I plug my phone in to the computer, enable OEM unlocking in Dev settings on my phone, anything else while I'm in there? USB debugging?
Then I open CMD on the computer? Or some program?
Then I have to check slots, or something? Boot_a vs boot_b?
Then I give what instructions in the command line? What does each one do? I'm coming from a web Dev background where commit comments and //comments or <!--comments--> explain anything new or unexpected or whatever. Similar explantions for each instruction would be ideal. What does each one do?
Any common problems and common fixes, or explanations behind any Razer Phone 2-specific quirks to the process we should be aware of?
Help with any or all of these would be appreciated.
Thank you.
AbsoluteContingency said:
Root instructions on the RP2 forum seem to assume a level of familiarity with rooting, and general instructions on the web seem to want to cover every possible device which means they cover every means of rooting options and device types and Android versions, and it isn't clear reading those where to start with the RP2.
I've found people on XDA tend to be pretty welcoming to dumber questions, so here's my dumb question.
If I have an "unlocked" (non-AT&T) device running 9 Pie, can someone translate this post:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454
Into usable instructions for those of us new to rooting? I have a Windows computer, a USB-A to USB-C cable (since the C-to-C cable that comes with the phone isn't suitable?), and an unrooted Razer Phone 2 on Pie.
I enable developer options in my phone's settings by tapping the version 7 times. I got that part.
Now, what do I download to my device? A boot image and magisk (?)? The boot image from the thread above, right? How do I ensure what I download to my phone goes to my phone and not the SD card? Is that a dumb question? Do I just remove the SD card before downloading anything?
Then what do I download to my computer? The Android SDK, or some smaller thing? Fastboot something something? ADB something something?
Then I plug my phone in to the computer, enable OEM unlocking in Dev settings on my phone, anything else while I'm in there? USB debugging?
Then I open CMD on the computer? Or some program?
Then I have to check slots, or something? Boot_a vs boot_b?
Then I give what instructions in the command line? What does each one do? I'm coming from a web Dev background where commit comments and //comments or <!--comments--> explain anything new or unexpected or whatever. Similar explantions for each instruction would be ideal. What does each one do?
Any common problems and common fixes, or explanations behind any Razer Phone 2-specific quirks to the process we should be aware of?
Help with any or all of these would be appreciated.
Thank you.
Click to expand...
Click to collapse
Hi I create a post that might help you, check it out. https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407
BTW the moderator will likely move this to the questions area.
AT&T Version ?
New to the RP2 community..
Thinking of getting the AT&T RP2 and wanted to find out/confirm if the AT&T version can be OEM UNLOCKED so you can unlock the bootloader.
Thanks in advance,
RJR
AbsoluteContingency said:
Root instructions on the RP2 forum seem to assume a level of familiarity with rooting, and general instructions on the web seem to want to cover every possible device which means they cover every means of rooting options and device types and Android versions, and it isn't clear reading those where to start with the RP2.
I've found people on XDA tend to be pretty welcoming to dumber questions, so here's my dumb question.
If I have an "unlocked" (non-AT&T) device running 9 Pie, can someone translate this post:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454
Into usable instructions for those of us new to rooting? I have a Windows computer, a USB-A to USB-C cable (since the C-to-C cable that comes with the phone isn't suitable?), and an unrooted Razer Phone 2 on Pie.
I enable developer options in my phone's settings by tapping the version 7 times. I got that part.
Now, what do I download to my device? A boot image and magisk (?)? The boot image from the thread above, right? How do I ensure what I download to my phone goes to my phone and not the SD card? Is that a dumb question? Do I just remove the SD card before downloading anything?
Then what do I download to my computer? The Android SDK, or some smaller thing? Fastboot something something? ADB something something?
Then I plug my phone in to the computer, enable OEM unlocking in Dev settings on my phone, anything else while I'm in there? USB debugging?
Then I open CMD on the computer? Or some program?
Then I have to check slots, or something? Boot_a vs boot_b?
Then I give what instructions in the command line? What does each one do? I'm coming from a web Dev background where commit comments and //comments or <!--comments--> explain anything new or unexpected or whatever. Similar explantions for each instruction would be ideal. What does each one do?
Any common problems and common fixes, or explanations behind any Razer Phone 2-specific quirks to the process we should be aware of?
Help with any or all of these would be appreciated.
Thank you.
Click to expand...
Click to collapse
rrusek said:
New to the RP2 community..
Thinking of getting the AT&T RP2 and wanted to find out/confirm if the AT&T version can be OEM UNLOCKED so you can unlock the bootloader.
Thanks in advance,
RJR
Click to expand...
Click to collapse
I have a rp2, att, bootloader unlocked, rooted, on global pie firmware. Not Sim unlocked, but don't care to move carriers.
jonchance_84 said:
I have a rp2, att, bootloader unlocked, rooted, on global pie firmware. Not Sim unlocked, but don't care to move carriers.
Click to expand...
Click to collapse
Same phone/firmware but I cannot get it rooted. It boot loops or gets stuck at Powered by Android logo with fast boot so at least I can re flash the stock global firmware and boot that. Seems no rooted boot loader works nicely for me. If you have any advice I would appreciate it.
i did fastboot boot_a nd boot_b with reboot but now im stuck on razer loading screen. does this mean im stuck in a bootloop?
It did turn out pretty easy.
I wiped all data, flashed the global MR1 image, booted system and took OTA update to MR2, rebooted to bootloader and flashed Arter 12 kernel, rebooted to Arter TWRP recovery, wiped Dalvik, flashed Magisk 20.1, wiped Dalvik, rebooted system >>> Profit!
Got Edxposed, Gravitybox and Greenify running and all banking apps load perfectly. It's just like the old days of modding, LOL!
Wifi is noticeably improved compared to my previous experience with the phone as well.
Total noob question
gboybama said:
took OTA update to MR2
Click to expand...
Click to collapse
What do you mean? You rooted, then upgraded "normally" to MR2? (I had to look up what OTA is, and it's "over the air"? As in a "normal" upgrade for people who let all their things just update as they please?) I ask because I thought once you rooted, normal updates weren't available?
All the tutorials I find are to upgrade to the MR1 boot.img (which my phone will boot with), then upgrade to the arter97 .img which leaves my phone in an endless booting state. (This is the exact step-by-step I followed: https://forum.xda-developers.com/ra...er-phone-2-t3914996/post79489415#post79489415 -- should be post #94: Castanoff 8th May 2019, 11:07 PM). I started out at MR2, I guess from when I updated the phone to a September update before attempting root. (Its original date was January 2019.)
I'm confused at the whole Magisk thing, as I was assuming that's after the arter update?
Tincan17 said:
What do you mean? You rooted, then upgraded "normally" to MR2? (I had to look up what OTA is, and it's "over the air"? As in a "normal" upgrade for people who let all their things just update as they please?) I ask because I thought once you rooted, normal updates weren't available?
All the tutorials I find are to upgrade to the MR1 boot.img (which my phone will boot with), then upgrade to the arter97 .img which leaves my phone in an endless booting state. (This is the exact step-by-step I followed: https://forum.xda-developers.com/ra...er-phone-2-t3914996/post79489415#post79489415 -- should be post #94: Castanoff 8th May 2019, 11:07 PM). I started out at MR2, I guess from when I updated the phone to a September update before attempting root. (Its original date was January 2019.)
I'm confused at the whole Magisk thing, as I was assuming that's after the arter update?
Click to expand...
Click to collapse
Not at all. I totally factory reset my phone and wiped everything. Flashed the latest stock factory image from Razer that I could find at the time (March 2019?). That put me on the older stock ROM, non-rooted. From there, I just booted into the system and kicked off the (as you put it) "normal" check for updates in the system options. That got me to the September version. Next, I flashed Arter's root and custom recovery kernel IMG file with the bootloader and installed the Magisk zip from TWRP recovery.
Update: Actually, it looks like the build number I'm currently running is now available on the Razer site, so flashing back to an earlier version and taking the OTA update is no longer required. You could just flash their latest system image, which they're putting out there as December 2019. (has the same exact build number as my September build) Then the Arter boot.img and a compatible Magisk zip will complete the root.
Just remember that flashing a full Razer system image in this way will erase your internal (non-SD card) storage. I lost some photos doing this.
Is there any way someone can or has a video on ho wto do this. Or maybe a similar phone thats the same.. But i can just use the specific files for my phone instead... This compared to regualr jailbreaking is like reading chinese. I switched from apple to androd rp2 and i love android way better. But these act more computer based. As far as files and stuff like that
I've been beating my head against the wall here. I've tried both MR0 and MR1. When I type in the fastboot command, all I get is < waiting for any device > My phone is in fastboot mode. I have the right drivers installed. I can see my phone using the adb devices command, so WTF?
scottysize said:
I've been beating my head against the wall here. I've tried both MR0 and MR1. When I type in the fastboot command, all I get is < waiting for any device > My phone is in fastboot mode. I have the right drivers installed. I can see my phone using the adb devices command, so WTF?
Click to expand...
Click to collapse
Try running this tool and see if it helps with fastboot. Let it run it'll boot your phone into the bootloader automatically and install all drivers.
https://forum.xda-developers.com/an...astboot-installer-tool-windows-t3999445/page1