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
Related
Hi All,
I'm lost, so hope you chaps can help.
Have just purchased a Verizon Moto X developer phone X1060 - its from the USA, I'm in Hong Kong and obviously not using a Verizone sim card - further, I'm a iMac user, so Android is new to say the least to me.
My MX is already "rooted" so want to upgrade to latest 4.4.2, obviously I have to do this via boot loader - big difficulties encountered having download all necessary files and cannot "hard" reboot as getting Andy with Red Triangle - I take it some issue with fast boot or whatever, but after 12 hours effort, absolutely stuck and getting annoyed.
So, time to hit boards and get expert advice me thinks?
I always used OTA updates, but I think that you have to unlock your bootloader, and/or, use RSD LITE like this:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Many thanks, but
djlucask said:
I always used OTA updates, but I think that you have to unlock your bootloader, and/or, use RSD LITE like this:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Thanks for your input, but as I have a developer Moto X from Verizone and am using it with a mobile provider in Hong Kong, I cannot do OTA update, hence struggling, and struggling because I'm on OSX 10.8 and an iMac, most guides being for PC - have managed to crack half the issue, but flashing ROM's is a big pain presently, particularly when using Terminal!
editor1 said:
Thanks for your input, but as I have a developer Moto X from Verizone and am using it with a mobile provider in Hong Kong, I cannot do OTA update, hence struggling, and struggling because I'm on OSX 10.8 and an iMac, most guides being for PC - have managed to crack half the issue, but flashing ROM's is a big pain presently, particularly when using Terminal!
Click to expand...
Click to collapse
Oh i forgot the iMac issue, I never saw tutorials for OSX, maybe the best choice here is to make an Windows VM, or an Linux, that way would be always easy to mod your phone.
Sorry I don't have any other possible solutions for this
Might be easier to read up on how to change the recovery to TWRP (make sure get version 2.7); sounds like you are on the stock recovery still since you get Andy w/ Red Triangle) then use TWRP to flash a rooted, updated rom from the development section. If you are already rooted (not just unlocked) then you can use an app like Recovery manager (?) to flash TWRP while booted into the regular android system.
Or, you can also flash all the update files from the Bootloader using Fastboot. I don't have a MAC, so I don't know if the Motorola Fastboot file is available for Mac though. If you can't use the Motorola fastboot, you will need to use fastboot to flash the TWRP recovery, and then flash the new ROM system image using a ROM zip file in TWRP recovery instead of Bootloader.
Just make sure you are in the Bootloader when you try and use fastboot, not in the Factory Recovery. I believe the Andy icon indicates you are in the Factory Recovery.
One other tip: when in bootloader, the "volume up" key is the "enter" key to select the option that is highlighted (not the power key like other Android devices I have used).
When you flash TWRP, DON"T reboot, instead, use the bootloader option to boot to recovery directly (without rebooting).
Once you have a custom recovery, and have root, you won't ever need to worry about working on a Mac instead of PC.
jasoraso said:
Might be easier to read up on how to change the recovery to TWRP (make sure get version 2.7); sounds like you are on the stock recovery still since you get Andy w/ Red Triangle) then use TWRP to flash a rooted, updated rom from the development section. If you are already rooted (not just unlocked) then you can use an app like Recovery manager (?) to flash TWRP while booted into the regular android system.
Or, you can also flash all the update files from the Bootloader using Fastboot. I don't have a MAC, so I don't know if the Motorola Fastboot file is available for Mac though. If you can't use the Motorola fastboot, you will need to use fastboot to flash the TWRP recovery, and then flash the new ROM system image using a ROM zip file in TWRP recovery instead of Bootloader.
Just make sure you are in the Bootloader when you try and use fastboot, not in the Factory Recovery. I believe the Andy icon indicates you are in the Factory Recovery.
One other tip: when in bootloader, the "volume up" key is the "enter" key to select the option that is highlighted (not the power key like other Android devices I have used).
When you flash TWRP, DON"T reboot, instead, use the bootloader option to boot to recovery directly (without rebooting).
Once you have a custom recovery, and have root, you won't ever need to worry about working on a Mac instead of PC.
Click to expand...
Click to collapse
Thanks for info, I've managed to setup fast boot, its the actual flashing of the ROM via Terminal that's confusing to say the least - basically, in Mac terminal necessary to change inputting details associated with rooting instructions found on PC - side of the equation, hence why I'm stuck. Would be easier to get someone with a PC laptop to lend a hand, most don't do custom jobs on Android though, so, will have to figure it out myself and then hopefully render help to others.
Republic Wireless Moto X Moto G Discount Code Link URL
$25 Republic Wireless credit at checkout with purchase of your phone using this discount link
editor1 said:
Thanks for info, I've managed to setup fast boot, its the actual flashing of the ROM via Terminal that's confusing to say the least - basically, in Mac terminal necessary to change inputting details associated with rooting instructions found on PC - side of the equation, hence why I'm stuck. Would be easier to get someone with a PC laptop to lend a hand, most don't do custom jobs on Android though, so, will have to figure it out myself and then hopefully render help to others.
Click to expand...
Click to collapse
Have you tried this?
Toolkit for Mac OS under development...
Sent from my XT1060 using Tapatalk 2
imparables said:
Have you tried this?
Toolkit for Mac OS under development...
Sent from my XT1060 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for info, I've not tried Toolkit, or heard of it - any links to assist with this?
Basically, you are going to see more Mac users adopt Android over the coming months, and many like me suffer in an all OSX environment when playing about with PC-structured advice - shame I never adopted a duel boot system on my mac, but its always been for DTP, hence always happy with Adobe in Mac.
Now upgraded to 4.4.2
editor1 said:
Thanks for info, I've not tried Toolkit, or heard of it - any links to assist with this?
Basically, you are going to see more Mac users adopt Android over the coming months, and many like me suffer in an all OSX environment when playing about with PC-structured advice - shame I never adopted a duel boot system on my mac, but its always been for DTP, hence always happy with Adobe in Mac.
Click to expand...
Click to collapse
Thanks for the input, after two days of hell, I'm now fully upgraded to KitKat 4.4.2, my Moto X1060 Dev phone is working as it should be, I've unlocked it, am able to do side-loading, have TWRP installed - a bigger pain as caused a continually boot loop, erased, re-installed all from Moto and re-cracked it.
So it works, and I did all this on a iMac and in terminal, which I don't often use!
Not bad for someone fast approaching 50 - and yes, this is a kids game I'm afraid to say.
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Seriously?
There aren't enough threads and guides for you to read already? Everything you need is already out there on this forum so why start another thread just because you are too lazy to search and read for yourself?
I have read around and have tried a number of guides a number of times. They haven't worked for me and I'm just wondering what i'm doing wrong. Even though all the information is out there, I don't have the experience to understand it apparently. I've spent hours trying to figure things out but i keep reading conflicting info and half-explained steps and now I'm just confused and would like a clear point in the right direction.
So, do i need to reflash the latest firmware, wait a few hours, then try again on a full charge? Or do i need a euro firmware? Which guide should i follow?
I've downloaded a few applications and driver packages and whatnot but if those could possibly conflict with each other and cause problems i could work with a fresh OS. I'm running OS X but i have linux VMs and friends with clean windows installs (mine is all sorts of messed up)
eatfoodnow said:
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Click to expand...
Click to collapse
It isn't a question of firmware, the phone needs to have an unlockable bootloader to be able to be, well, unlocked. Here is a list http://forum.xda-developers.com/showthread.php?t=2181581 of P880 bootloader versions. Follow the guide to check which BL your phone has.
Thats obsolete, all versions can be unlocked afaik, either with official method or by fuse editing. No need to keep sim card in,you just need proper drivers
Oh, OK, I didn't know that. But, even better, OP should not have any trouble, provided he follows the BL unlock guide here http://forum.xda-developers.com/showthread.php?t=2224020
Maybe his BL is already unlocked OR is relocked (meaning can't be unlocked anymore).
Its more likely that his drivers are messed up imo.
The fuse editing method should work for everyone, i recommend you give it a try
So the fuse method would be the "BL-unlock.bat" method on that bootloader unlock forum post? I've tried it before, but I'll try it again. The directions only say to run it, is there anything else I need? Now, since it's a .bat file I absolutely have to run it on Windows, right? Because if so I'll use a friend's computer instead of my windows installation.
What are the necessary installations before I run the file? How should I configure settings on my phone? (like what type of usb connection should it be)
There are a lot of things that people expect readers to know but I'm really not very knowledgeable about standard practices for phone stuff so I really need every step. Thanks for helping!
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Flying_Bear said:
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Click to expand...
Click to collapse
Also, correct me if i'm wrong I only had stock for 2hours, but also stock needs usb debugging to be enabled or adb won't work?
Yep, afaik usb debugging needs to be enabled
When you are fast enough, it is possible in charging mode wihle the carger animation is shown. But you have install adb driver very fast...
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
eatfoodnow said:
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
Click to expand...
Click to collapse
you can check your bl status by entering sw mode (phone off, hold vol+ and insert charger) or reeboting into bl (adb reboot oem-unlock)
to install cm steps are:
-install recovery (you can choose either cwm or twrp, it's more about looks than functions)
-download rom zip onto sd card
-install said zip from said recovery, there's no adb involved
Now my personal opinion, I really don't see the point in flashing 10.1, i would go staright for cm11 if i were you
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
eatfoodnow said:
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
Click to expand...
Click to collapse
Factory reset then get nandroid manager app and see if you can restore your stuff with that
CM11 is bugless atm and performance (imo) is way superior
So after a factory reset/data wipe, my phone just booted into CM10.1 and now that's working. And it looks like all of my stuff on the phone is still there (though of course apps aren't installed and whatnot, that wouldn't make sense). Thanks for all the help!
I tried to find a feature list or something to see what exactly is better about CM11, and found out that "stable" doesn't exactly mean stable for CM, and that it looks like a good idea to update, so I think I will try to update to that. Do you know anywhere that has an actual feature list to show me what CM11 does that CM10.1 doesn't?
hey guys, Im a total NOOB to all these things. was using iphone before now shifted to android. Let me start from first. i got a nexus 6 1 mnth bak. So as soon as i got it, i put it for 5.1 update. hours later update got downloaded and i clicked install. then halfway thru the updating it said error and it started to restart. then it kept on bootlooping to the android optmisation screen. I cudnt do anything else. tried doing wipe cache, factory reset- nothing worked. SO i replaced my phone for a new nexus 6.
Now iM Totally scared to update it to 5.1 OTA. iM Ccurrently running android 5.0 build- LRX21O. I Have not rooted my phone. sO Can u please tell me whether i can update to 5.1 directly from 5.0 thru nexus roottoolkit as i dont want to do the hard way by entering commands which i think i will mess it up. or rootkit is just for rooting and unrooting phone? CAN u please give me a guide on how to update it to 5.1. i dont want to root it.
please guys, im a total noob to all this. please excuse if i dont know stuff. i used to jailbreak my iphones and ipad and do all kinds of stuff. but since im knew i dont know many things in android.
thank u so much guys
First thing to do is to unlock your bootloader. That way, if anything goes wrong, at any point, you are almost 100% able to restore your phone again. It's also a good idea to flash TWRP (custom recovery).
You can update through NRT, or as a lot of us recommend fastboot. It's not as scary as it looks, and it's actually easier to mess stuff up with a toolkit if you have no idea what said toolkit does in the background (hint: it's using the commands).
It's a good idea to read, read and then read some more. If you have a basic understanding of things it's easier to get things done correctly. Start off by reading the FAQ-thread, lots of good info there.
http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Didgeridoohan said:
First thing to do is to unlock your bootloader. That way, if anything goes wrong, at any point, you are almost 100% able to restore your phone again. It's also a good idea to flash TWRP (custom recovery).
You can update through NRT, or as a lot of us recommend fastboot. It's not as scary as it looks, and it's actually easier to mess stuff up with a toolkit if you have no idea what said toolkit does in the background (hint: it's using the commands).
It's a good idea to read, read and then read some more. If you have a basic understanding of things it's easier to get things done correctly. Start off by reading the FAQ-thread, lots of good info there.
http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Click to expand...
Click to collapse
thanks for ur reply. Wil do it in fastboot mode only. i will read more about it., One last question. Can i flash to 5.1 directly from 5.0? or to flash to 5.1 i need to update it to 5.0.1( since most of the forums said this). aLSO There are 3 shamu factory images for 5.1 LMY47D, 47E, 47I. Which one should i use?
Unless you're running T-Mobile or Project FI you should use LMY48I. Latest 5.1.1 with almost all the stagefright patches.
Edit: Oh yes... You can flash straight to the latest.
yeshwanter said:
thanks for ur reply. Wil do it in fastboot mode only. i will read more about it., One last question. Can i flash to 5.1 directly from 5.0? or to flash to 5.1 i need to update it to 5.0.1( since most of the forums said this). aLSO There are 3 shamu factory images for 5.1 LMY47D, 47E, 47I. Which one should i use?
Click to expand...
Click to collapse
Didgeridoohan said:
Unless you're running T-Mobile or Project FI you should use LMY48I. Latest 5.1.1 with almost all the stagefright patches.
Edit: Oh yes... You can flash straight to the latest.
Click to expand...
Click to collapse
I concur. Get all you drivers working. Figure out fastboot. There are many different ways to set up adb/fastboot. There is the right way or the fast way. Both work. Can always upgrade so the full SDK is available when you get hooked and have to have all the tools. lol There is a thread for 15 second fastboot. It works. Will at least be what you need to learn fastboot. When got adb/fastboot working we can walk you through the commands.
prdog1 said:
I concur. Get all you drivers working. Figure out fastboot. There are many different ways to set up adb/fastboot. There is the right way or the fast way. Both work. Can always upgrade so the full SDK is available when you get hooked and have to have all the tools. lol There is a thread for 15 second fastboot. It works. Will at least be what you need to learn fastboot. When got adb/fastboot working we can walk you through the commands.
Click to expand...
Click to collapse
ok guys, thanks for ur replies. I downloaded SHAMU lmy48i (5.1.1). im running 5.0, nexus 6 international version. let me just confirm what im going to do after this is right and tell me whether to proceed or not.
1)downloaded sdk tools. installed it. dint create a system wide directory. i opened platform tools and opened command window and typed adb version and it said android debug version 1.0.32 blh blah.
2)next i enabled usb debugging and oem unlock in developer settings of nexus 6.
3)connected my nexus 6.
4)went to platform tools and again typed adb devices. it showed my device serial number
5)then i have to enter bootloader. type fastboot devices and it should show my serial number.
6) then type command fastboot oem unlock
7)then have to run fastboot reboot
8) my bootloader is unlocked. Now i have to load it in bootloader mode.
9) then execute flash-all.
10) android will update to 5.1.1
thats all ryt? did i miss anything in this?
Didgeridoohan said:
Unless you're running T-Mobile or Project FI you should use LMY48I. Latest 5.1.1 with almost all the stagefright patches.
Edit: Oh yes... You can flash straight to the latest.
Click to expand...
Click to collapse
ok guys, thanks for ur replies. I downloaded SHAMU lmy48i (5.1.1). im running 5.0, nexus 6 international version. let me just confirm what im going to do after this is right and tell me whether to proceed or not.
1)downloaded sdk tools. installed it. dint create a system wide directory. i opened platform tools and opened command window and typed adb version and it said android debug version 1.0.32 blh blah.
2)next i enabled usb debugging and oem unlock in developer settings of nexus 6.
3)connected my nexus 6.
4)went to platform tools and again typed adb devices. it showed my device serial number
5)then i have to enter bootloader. type fastboot devices and it should show my serial number.
6) then type command fastboot oem unlock
7)then have to run fastboot reboot
8) my bootloader is unlocked. Now i have to load it in bootloader mode.
9) then execute flash-all.
10) android will update to 5.1.1
thats all ryt? did i miss anything in this?
Looks good. If going to use flash-all.bat make sure SDK platform tools are updated to Version 23+ in SDK Manager. Can also unzip the file a second time and do each image separately. Will find more use for the individual files later.
Looks good.
Quick advice: remember that unlocking the bootloader and flashing the factory image will completely wipe your device. If you've had time to accumulate some data on there that you want to keep, make sure to back it up first.
In the future, if you decide to root or use a custom recovery, you won't be able to take OTA updates (it checks for a tampered system). It's quite easy to update anyway... Just use the same knowledge you've earned doing this and follow prdog1's advice.
Unzip the factory image a second time and flash all images except userdata.img. That way you'll get a nice new updated system without wiping your stuff.
If jumping between roms or doing a major update, it can be good to let the entire factory image flash, though. Just make sure to backup your stuff first...
I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?
entermetallica said:
I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?
Click to expand...
Click to collapse
First of all congrats on the new phone. I'm on AT&T and updates came too slow for me. I chose to flash a system image to get upgraded to marshmallow and now we can download ota's directly from Google to keep up to date. Cutting out the need to wait for our updates to be made available from the carriers. Edit: to be clear you have to flash the ota's as well.
I believe others have removed sim card to try to get ota via wifi. I think. Anyway good luck.
Sent from my SM-T700 using Tapatalk
If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.
Dopamin3 said:
If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.
Click to expand...
Click to collapse
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.
entermetallica said:
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.
Click to expand...
Click to collapse
Assuming you're using Windows, if you look in device manager do you see anything either with a red x or yellow exclamation mark? If so you are missing the driver. This thread has the driver zip and briefly explains how to install it via device manager. Once you get the driver installed it should work fine.
And I can't remember if you need to or not to flash the stock images, but you might need to unlock your bootloader. Tap the build number a bunch of times and you will have access to developer options, and there you might need to check "Allow OEM unlocking" or something like that. Again I'm not 100% sure if that's necessary or not. I've ran my bootloader unlocked since day 1 and haven't looked back.
The bootloader does need to be unlocked to flash anything at all, except for a Google-signed OTA image.
Thanks for the help, ive done it. I had to boot into fastboot, and then install drivers from device manager
Sent from my Nexus 6 using XDA-Developers mobile app
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting. I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging.
jwils1236 said:
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting and wouldn't have bought it if I would have known (or at least not updated to Pie). I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging/impossible. Any help would be appreciated and if a solution is brought to light, I am gladly offering $. This could easily be considered a device with best hardware and when rooted, access to best software -- I didn't see significant enough improvements in Note 9 and figured by now the support from XDA community would be abundant for the exynos processor. Turning out ridiculous waste of money if I can't root it (already purchased silver carbon fiber skin, 256 GB Samsung Evo Select SD card, attachable portable wireless charging pack, etc.). Please help!
Click to expand...
Click to collapse
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Its just easy step
Things u needed before proceed
* SD card
*Magisk latest version
*Odin
* Twrp zip file
1. Reflash ur device with proper firmware
2. After done go download mode and flash Twrp zip on odin. After done reboot ur device to Twrp again
3. After boot up to Twrp go to Wipe and do a factory restore . After this done u must install Magisk or u will get official binary only after reboot to system
4. After all the step are followed u are good to go. Cheers
stonedpsycho said:
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Click to expand...
Click to collapse
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
Also, for anyone reading this with the same issue, extracting the boot image from stock firmware (can be done through command prompt/terminal dump or by extracting from stock firmware -- AP Odin file) and patching with Magisk will not flash or work/give root access either unless this device is fully unlocked -- OEM unlock doesn't matter, if RMM still says "Prenormal" in download mode.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I am quite sure it is still rootable on bootloader 6, so updating would be fine.
The trick to get the OEM toggle is a bit hit and miss, the guide below is the method that has had a higher success rate for me, if followed exacty as written.
https://www.google.com/amp/s/www.xd...-samsung-galaxy-s8-samsung-galaxy-note-8/amp/
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I ended up using Chimera Tool to bypass RMM state. Worked instantly. This seems to be a common issue for many Samsung devices, at least on Pie. Not sure there is an alternative solution, currently. Only one I could find for my device.