Updated guide rewritten here: http://forum.xda-developers.com/showpost.php?p=68538891&postcount=1
WARNING: THIS IS FOR THE MOTO MAXX ONLY. I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT MIGHT HAPPEN TO YOUR BELONGINGS.
@respider made a custom recovery for us. It's not even beta, it's alpha. What it means is that it's the first attempt to make a custom recovery. Bugs are expected.
To root, you can use the attached datroot, or SuperSU
Before anything, go to the Motorola website and unlock your bootloader.
1. Download the file attached. Download the recovery
2. Leave the maxxpatched.img in your PC and put datroot.zip in your phone.
3. Open a terminal with adb and fastboot. If you don't know what i'm talking about, Google it.
4. In terminal use:
Code:
adb reboot bootloader
Your phone will reboot and you'll see the fastboot screen.
5. Unzip the recovery and rename the file to recovery.img
Code:
fastboot boot recovery.img
6. Now you'll boot into the recovery. Press simultaneously Power and Vol UP to show the commands.
Some users say the best way is to hold the Vol UP and then press and release the Power.
7. Install > click on the datroot.zip/supersu.zip> let it install > clear cache and dalvik
8. Reboot system.
9. You've got root.
glad to see the recovery is being useful... I hope we manage to get a working TWRP or CWM soon
Do I need to unlock the bootloader first??
ellopr said:
Do I need to unlock the bootloader first??
Click to expand...
Click to collapse
If he says no, he just earned like over 5 grand.
Maxx only were his first words, yes you must unlock your bootloader first.
Did this couple of days back, worked perfectly!! Now waiting for custom recovery and roms
---------- Post added at 10:48 PM ---------- Previous post was at 10:45 PM ----------
Hey since some of us are rooted, any body with knowledge care to look into trying to boost the sound of this baby a little?
tested
NOT WORKING ON DROID TURBO
prking07 said:
Did this couple of days back, worked perfectly!! Now waiting for custom recovery and roms
---------- Post added at 10:48 PM ---------- Previous post was at 10:45 PM ----------
Hey since some of us are rooted, any body with knowledge care to look into trying to boost the sound of this baby a little?
Click to expand...
Click to collapse
Bummed i aint' got root. Anyway. 'mixer_paths.xml' search xda for the proper values to modify. Its super simple and should dramatically increase the volumes. I've used this method on a bunch of phones running stock 4.x.x. Will work on 5.0 also. Tested on my nexus 7 2nd gen.
I'm sure Danger2u was 'reporting' and not 'complaining'.. easy enough to understand. it's way impossible OP would have been trying this on a turbo either,...
There needs to be a Moto Maxx forum. Seeing this in the turbo forum from my turbo just makes me sad.
alexcreto said:
5.
Code:
fastboot boot maxxpatched.img
6. Now you'll boot into the recovery.
Click to expand...
Click to collapse
When I get to step 5 and try to boot into recovery, only a resting android with a red exclamation point is shown.
And a text that says "Ningún comando" which means "No command".
I can't do anything else, after a while the phone reboots itself into my homescreen.
What should I do? What could be wrong?
UPDATE: Ok, after a while I found the solution:
When it shows "no command", press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key. It will display additional menu options.
Click to expand...
Click to collapse
Thanks to sbdc003 in androidforumshttp://androidforums.com/
Thanks @alexcreto, great tutorial!
ImpheOtus said:
When I get to step 5 and try to boot into recovery, only a resting android with a red exclamation point is shown.
And a text that says "Ningún comando" which means "No command".
I can't do anything else, after a while the phone reboots itself into my homescreen.
What should I do? What could be wrong?
Click to expand...
Click to collapse
Oh, my bad...
I'm so used to that I forgot to mention.
Press simultaneously Power and Vol UP
alexcreto said:
Oh, my bad...
I'm so used to that I forgot to mention.
Press simultaneously Power and Vol UP
Click to expand...
Click to collapse
Thank you!
I'm comming from Galaxy SII and S4 and I had never had to do this so it's my first time with fastboot, ADB and custom recoveries.
ImpheOtus said:
Thank you!
I'm comming from Galaxy SII and S4 and I had never had to do this so it's my first time with fastboot, ADB and custom recoveries.
Click to expand...
Click to collapse
Don't worry man, glad you enjoyed.
i understand very well that the guide is for Moto Maxx and NOT for Droid turbo.
but like some cases a method works on other phone that are similar
so i tested and just say that is not working on Droid turbo
in this way other users will not try on their Turbo
and i don t make any flame or other
frankeegee said:
I guess there is a reason for your name, eh? ?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I try, but my xt 1225 is not recognized, no drives installed? I have de MDM 2.4.5, but in Windows 7 not Works. How to download latest version of drives to Motorola xt1225?
adb devices not list my xt1225. I try with minimal adb and fastboot and Android SDK.
How to fix this? I need unlock bootloader.
Thanks
Thanks
muccioli said:
I try, but my xt 1225 is not recognized, no drives installed? I have de MDM 2.4.5, but in Windows 7 not Works. How to download latest version of drives to Motorola xt1225?
adb devices not list my xt1225. I try with minimal adb and fastboot and Android SDK.
How to fix this? I need unlock bootloader.
Thanks
Thanks
Click to expand...
Click to collapse
In the control panel, access the device manager and find your phone among the connected devices.
(Im not running Win right now, so Im gonna try to tell you the steps by memory)
You have to right click and install updates to it.
Instead of letting it find them over the net, you'll choose the option to choose one from the list.
In that list find and pick the Moto Comp ADB
That should make it work.
If I switch to Win later today I'll update this post.
Hope it helps....
alexcreto said:
In the control panel, access the device manager and find your phone among the connected devices.
(Im not running Win right now, so Im gonna try to tell you the steps by memory)
You have to right click and install updates to it.
Instead of letting it find them over the net, you'll choose the option to choose one from the list.
In that list find and pick the Moto Comp ADB
That should make it work.
If I switch to Win later today I'll update this post.
Hope it helps....
Click to expand...
Click to collapse
Many thanks, but,
Do not have Moto Comp ADB in the options.
I try again use SDK, show message Daemon not start. Start daemon in port 5037. Daemon start. But nothing is happening. Don not show my device.
muccioli said:
Many thanks, but,
Do not have Moto Comp ADB in the options.
Click to expand...
Click to collapse
I remember that there was a parent called Motorola and a parent called Android ADB. Did you check both?
help
well im in the same position of the non recognized adb drivers i can't get my unlocked bootloader, and i wanna ask. after achieving root, can i install xposed framwork an then the gravity box, to make some changes??
Related
This is the same as any other Nexus device.
WARNING. As is normally the case, this WILL factory reset your device.
Install the Android SDK (and Google USB driver).
Android SDK
Google USB Driver (Windows)
Enable USB debugging on the Nexus 7.
Unlock Developer Options by going to Settings > About Tablet and clicking on the build number seven times.
Go to Settings > Developer Options and check USB debugging. Click OK on the warning.
Connect the Nexus 7 via USB and reboot the Nexus 7 into the bootloader.
Note: Users have reported failures and "Access is Denied" errors when connected via USB 3.0 ports so use USB 1.1 or 2.0 to be on the safe side.
Open a command line / terminal and navigate to your SDK platform-tools directory.
Enter
Code:
adb reboot bootloader
and hit enter.
Once the Nexus 7 boots to the bootloader, unlock it
At the command line / terminal enter
Code:
fastboot oem unlock
and press enter.
On the Nexus 7, use the volume up button to select 'Yes' on the 'Unlock bootloader?' screen.
Press the power button to save your choice and verify on the next screen that you see 'LOCK STATE - UNLOCKED' at the bottom.
Use your volume keys to select 'Start' and click the power button to factory reset and reboot.
Enjoy your unlocked bootloader!
Do you have the usb drivers installed? That happened to me ("old" n7) when I didn't have the usb drivers installed.
may need to update your drivers for it to be able to see the device.
when you try adb devices while it is on does it kick back the device id number?
i haven't tried yet as i knew the drivers out currently would be an issue.
gksmithlcw said:
Any ideas? I tried I tried the ol' fastboot oem unlock command and it just sits there with the < waiting for device > message.
Click to expand...
Click to collapse
Perhaps it needs new adb/fastboot drivers ? I'm still charging mine, so I haven't tried. Sorry. Maybe the new driver comes with the 4.3 SDK ?
gksmithlcw said:
Any ideas? I tried I tried the ol' fastboot oem unlock command and it just sits there with the < waiting for device > message.
Click to expand...
Click to collapse
First off (don't mean to be a d!ck) but this thread belongs in "General", or "Q&A", because you haven't posted a development thread.
Second, unlocking the boot loader is just as easy as the first Gen Nex7. I had mine unlocked within 5 minutes of getting it home.
As others have said, make sure your drivers are installed, or ADB won't even recognize the device.
mrancier said:
Perhaps it needs new adb/fastboot drivers ? I'm still charging mine, so I haven't tried. Sorry. Maybe the new driver comes with the 4.3 SDK ?
Click to expand...
Click to collapse
I updated my SDK when 4.3 dropped but I did have to go snag the Google USB driver and install it to get the N7 to be recognized.
ATGAdmin said:
First off (don't mean to be a d!ck) but this thread belongs in "General", or "Q&A", because you haven't posted a development thread.
Second, unlocking the boot loader is just as easy as the first Gen Nex7. I had mine unlocked within 5 minutes of getting it home.
As others have said, make sure your drivers are installed, or ADB won't even recognize the device.
Click to expand...
Click to collapse
1. You may be right (as far as my posts go) but how am I to ever make a dev post if I'm not allowed to make a first post in a dev forum?
2. This /is/ a dev-related post.
3. My feelings wouldn't be hurt if the mods felt the need to move the post.
Yeah I had to install the google usb drivers from the SDK in device manager of Windows to get the n7 recognized.
Thanx. Just got home with my new nexus 7....bootloader now unlocked :highfive:
Nevermind it literally is that as the command.
Sent from my Nexus 7 using Tapatalk 4 Beta
keynith said:
Can you update it with the commands? So people don't have to search
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The commands are there...
Also, unlocked mine not 5 minutes after opening on Ubuntu 13.10.
no idea why my device won't be read by adb. but i manually rebooted to bootloader and fastboot oem unlock took care of that. time to wait for root/recovery
Worked great thanks!
---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------
smirkis said:
no idea why my device won't be read by adb. but i manually rebooted to bootloader and fastboot oem unlock took care of that. time to wait for root/recovery
Click to expand...
Click to collapse
Make sure you update your files from the SDK Manager. It had updated USB driver which from there it would install the proper drive and then it worked form me.
The trick, as stated in the Nexus Toolkit after driver install, is that you need to change the tablets usb settings from MTP to PTP. Tablet was immediately seen using "old" nexus toolkit universal usb drivers (old = i did not download the new SDK). I choose toro 4.2.2 (because it doesn't matter for unlocking) and then told it to unlock. worked like a charm.
Now the question is ... how long does it take to reboot cause mine is taking forever!!!
OK it booted. So yeah the Nexus 7 Toolkit ver 5.0 worked just fine to at least unlock. I did not root (4.3 still too buggy) or install a custom recovery yet.
Stock recovery, pretty please?
My dumbass flashed TWRP for Grouper. Wouldn't boot, so I tried erasing the recovery in hopes it would self-restore. No dice. Can't seem to find recovery-from-boot.p either. No boot and still no custom recovery for this puppy. :crying:
Would someone be the kindest person on earth and pull & post the stock recovery...or tell me how to find and flash a back-up copy already stored on my nexus? Google hasn't even posted the img files yet. My new toy is borked and Daddy wants to play tonight!
Thank you!
My body and my 7 are ready for a recovery!
Thank you!
treoo0_1 said:
My dumbass flashed TWRP for Grouper. Wouldn't boot, so I tried erasing the recovery in hopes it would self-restore. No dice. Can't seem to find recovery-from-boot.p either. No boot and still no custom recovery for this puppy. :crying:
Would someone be the kindest person on earth and pull & post the stock recovery...or tell me how to find and flash a back-up copy already stored on my nexus? Google hasn't even posted the img files yet. My new toy is borked and Daddy wants to play tonight!
Thank you!
Click to expand...
Click to collapse
I'd be happy to, but am having a hard time finding the correct ADB command.
isnt the new N7 files called Razor instead of grouper ? or is that just what the device was called prior to launch
adb pull
jc monkeyballs said:
I'd be happy to, but am having a hard time finding the correct ADB command.
Click to expand...
Click to collapse
Can you use
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example:
Code:
adb pull /system/recovery.img C:\Android\Local
Thanks for offering to help!
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
Lpuboy87 said:
isnt the new N7 files called Razor instead of grouper ? or is that just what the device was called prior to launch
Click to expand...
Click to collapse
Yep. Razor.
Branch = Razor
codename = Asus flo
Wifi Model: ME371K
followed the first post and it worked....used this for the commands
ADB Commands
---------- Post added at 11:12 PM ---------- Previous post was at 11:10 PM ----------
treoo0_1 said:
Yep. Razor.
Click to expand...
Click to collapse
yeah thought so. :good::highfive:
Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!
That explains why the OTA for the N preview was the same size as the image, and why after upgrading to March security release I didn't have to download a different OTA to get to N
So is this usable in all situations? If yes then should download it & store it safely
Interesting thing, can this update bypass factory reset protection?
iluvatrix said:
So is this usable in all situations? If yes then should download it & store it safely
Click to expand...
Click to collapse
I would assume this could be used in any situation where you have a paper wait. So say you're on marshmallow build and somehow things go wrong ,bootloader locked USB debugging not check ,with this ota you can still sideload but it will be an N build which is fine at least you'll have a working device that now you can revert back to your original build. So I'm keeping this as well. I really don't need to but its nice to have just in case. I normally keep my bootloader unlocked at all times anyways just in case things go haywire... Someone correct me if I'm not correct please. Have a nice weekend all?
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Good question..
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Most likely not, because normally when receiving an OTA all of that remains intact but, I think it's worth a test.
This will NOT bypass factory reset protection. This is just an update.zip that is a signed "FULL" image rather than a "DIFFERENCE" image. That means that it just doesn't need to perform the verification step before proceeding to install the update.
There is also another "problem" with relying on these as the ultimate unbrick files, which is that if you happen to install some official build that is NEWER than N-pre1, then the recovery will refuse to "downgrade". So while it may be useful for now while nobody is running anything newer than N-pre1, it isn't a permanent solution.
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
doitright said:
This will NOT bypass factory reset protection.
Click to expand...
Click to collapse
The first N preview apparently has a bug that will allow a user to bypass FRP (if they are on the first N preview)
http://www.androidpolice.com/2016/0...ory-reset-protection-workaround-on-android-n/
flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
I'm glad to hear it worked for you
Works for me boss
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:
mowgli762 said:
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:
Click to expand...
Click to collapse
Why didn't you just flash the system.IMG if the bootloader was unlocked?
holeindalip said:
Why didn't you just flash the system.IMG if the bootloader was unlocked?
Click to expand...
Click to collapse
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).
mowgli762 said:
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).
Click to expand...
Click to collapse
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.
holeindalip said:
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.
Click to expand...
Click to collapse
Good - case specific information needs no apology - Diplomacy has never been alluded to as being in my skill set (too much glass in my house to throw stones).
Thanks for your interest and info.
TriguyRN said:
Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!
Click to expand...
Click to collapse
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .
atef79 said:
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .
Click to expand...
Click to collapse
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face
TriguyRN said:
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face
Click to expand...
Click to collapse
I already shared your post in my topic that I made in the Nexus 6p section to help all who bricked there devices with locked bootloader, and thx again .
This is my topic link
http://forum.xda-developers.com/nexus-6p/help/command-t3308390/post66086939#post66086939
just want to ask would this method work if the phone has not been authorized to a specific PC ?
iluvatrix said:
just want to ask would this method work if the phone has not been authorized to a specific PC ?
Click to expand...
Click to collapse
I'm not sure what you mean by "if the phone has not been authorized to a specific PC". As far as I am aware Android phones are not authorized to a PC, that is an Apple thing...
UPDATE -- ISSUE RESOLVED
*** New OTA available ***
See links below
Updated zip confirmed working here:
https://plus.google.com/100708818877715770270/posts/dEyVgqmURw2
Android Beta Program:
https://g.co/androidbeta
OTA Download:
NEW (fixes both OTA and sideload failures)
https://ota.googlezip.net/packages/.../1c0e174d9aeefbb176b4dd38b48270a0fd4082d9.zip
pangolin.rollin said:
For those experiencing issues updating to 8.1 on locked n stock f/w there is now a fix!!!
Source and Credit goes to "AC" : [url]https://issuetracker.google.com/issues/68264793[/URL]
See post #64 and #71
FIX SUMMARY
1. Enroll in beta ota
2. Download ota
3. Enable Developer mode
4. When update screen says "Reboot to update" DON'T click it but rather issue "adb reboot recovery"
5. Once in bootloader go to recovery like normal and ensure it says recovery 8.1
6. You may then enable update from adb for sideload.
7. When pixel is in ready to receive update issue "adb sideload <update.zip>"
8. Profit
Android Beta Program:
https://g.co/androidbeta
OTA Download:
[url]https://ota.googlezip.net/packages/ota-api/google_sailfish_sailfish/42c4425cf03125fe7c535e39cbac7d17c1a2f65a.zip[/URL]
Please post your success stories or issues.
I was on OPR3.170623.008 when this was done.
Click to expand...
Click to collapse
Credit goes to @ACastanza ,
Here is the mentioned fix by him/her : https://forum.xda-developers.com/showpost.php?p=74331289&postcount=51
Although i commend you trying to summarize the steps, they are wrong
adb reboot recovery is not a valid command ; i believe what you meant was
Code:
adb reboot bootloader
And i am not sure about this, but i think turning on developer mode is entirely optional.
NoobInToto said:
Credit goes to @ACastanza ,
Here is the mentioned fix by him/her : https://forum.xda-developers.com/showpost.php?p=74331289&postcount=51
...
And i am not sure about this, but i think turning on developer mode is entirely optional.
Click to expand...
Click to collapse
Oops yeah updated to bootloader, hadn't seen the post before or anything on XDA. Been following the normal circles. Can't hurt to spread the news!
The whole reason for suggesting the "optional" part of developer mode is cause if you try just the regular reboot /key press combo and miss it you have to redo the OTA download which is rather annoying. Rather just remove that possibility.
NoobInToto said:
Credit goes to @ACastanza ,
Here is the mentioned fix by him/her : https://forum.xda-developers.com/showpost.php?p=74331289&postcount=51
Although i commend you trying to summarize the steps, they are wrong
adb reboot recovery is not a valid command ; i believe what you meant was
Code:
adb reboot bootloader
And i am not sure about this, but i think turning on developer mode is entirely optional.
Click to expand...
Click to collapse
adb reboot recovery is definitely a valid command (assuming you're running a current version of ADB).
Enabling developer mode was not part of my original post, I don't think it is required, but then I was running it anyway. Entering recovery through a command rather than having to catch it at exactly the right moment with the key command is definitely easier, but I hadn't tested it that way when I did this originally. Glad this works too, it's much easier.
Also, glad people are finding this useful!
pangolin.rollin said:
Oops yeah updated to bootloader, hadn't seen the post before or anything on XDA. Been following the normal circles. Can't hurt to spread the news!
The whole reason for suggesting the "optional" part of developer mode is cause if you try just the regular reboot /key press combo and miss it you have to redo the OTA download which is rather annoying. Rather just remove that possibility.
Click to expand...
Click to collapse
Ah, now I get it. I forgot you needed usb debugging for adb when booted in system.
Anyways, booting in bootloader mode was easy, it is very hard to miss. One has to press power+volume down immediately after first bootloop, when the screen is back, and i was able to get into bootloader mode within 1 second.
---------- Post added at 05:11 AM ---------- Previous post was at 05:09 AM ----------
ACastanza said:
adb reboot recovery is definitely a valid command (assuming you're running a current version of ADB).
Enabling developer mode was not part of my original post, I don't think it is required, but then I was running it anyway. Entering recovery through a command rather than having to catch it at exactly the right moment with the key command is definitely easier, but I hadn't tested it that way when I did this originally. Glad this works too, it's much easier.
Also, glad people are finding this useful!
Click to expand...
Click to collapse
I had checked adb reboot recovery when booted in system. It did not work in 8.0.0.
Woops, I only read the first part of your post. Nevermind.
NoobInToto said:
I had checked adb reboot recovery when booted in system. It did not work in 8.0.0.
Click to expand...
Click to collapse
Your right it doesn't work in 8.0. That's why I specified to do it when it says "reboot to update" because when the system "pre-loads" the OTA it switches the active boot slot for next reboot. That's why doing it this way works as well.
ACastanza said:
Woops, I only read the first part of your post. Nevermind.
Click to expand...
Click to collapse
Huh? lol..
Anyways man didn't mean to steal your thunder. Just glad we're on 8.1.
You're the best! :good:
pangolin.rollin said:
Huh? lol..
Anyways man didn't mean to steal your thunder. Just glad we're on 8.1.
You're the best! :good:
Click to expand...
Click to collapse
No worries! Just glad people are getting updated without needing to factory reset.
(ADB rebot recovery actually does work on 8.0 but you need to have adb debugging enabled and need a new-ish version of the ADB binary).
ACastanza said:
No worries! Just glad people are getting updated without needing to factory reset.
(ADB rebot recovery actually does work on 8.0 but you need to have adb debugging enabled and need a new-ish version of the ADB binary).
Click to expand...
Click to collapse
Oh, yeah, the latest one not only has reboot recovery, but direct reboot to sideload options too....sweet
Btw there is a second workaround. It involves adb sideloading the same build (8.0.0) and then sideloading the Dev preview.
This worked for me. Looked like it was bootlooping again at first, but eventually booted into 8.1.0. Thanks!
invisibro said:
This worked for me. Looked like it was bootlooping again at first, but eventually booted into 8.1.0. Thanks!
Click to expand...
Click to collapse
Yup, strangely enough, that is the expected behavior for this workaround. @pangolin.rollin should include info about it in the OP post.
What am I missing here? I enrolled in the beta (Verizon locked bl) yesterday and within about an hour I had a notification to update to the beta. I clicked download and install and on the reboot I was running 8.1. What's all this about bootlooping, slots, rebooting bootloader? I did none of that and it worked flawlessly.
NoobInToto said:
Yup, strangely enough, that is the expected behavior for this workaround. @pangolin.rollin should include info about it in the OP post.
Click to expand...
Click to collapse
Updated op thanks
** Fixes "parse error -22" and update not installed, while this works first boot looks like it's looping. **
bobby janow said:
What am I missing here? I enrolled in the beta (Verizon locked bl) yesterday and within about an hour I had a notification to update to the beta. I clicked download and install and on the reboot I was running 8.1. What's all this about bootlooping, slots, rebooting bootloader? I did none of that and it worked flawlessly.
Click to expand...
Click to collapse
Your lucky then! Not sure of the official cause of the errors and why some work and some don't. But seems some devices have issues verifying. That's why Google even pulled ota images.
So I presume that the only problems were with sideloading? I never do that on my Pixel since I just like it updating in the background, reboot and done. With a locked bootloader I can't take a chance of doing something wrong. If they send me an image or OTA that bootloops then it's not my problem and they have to either fix it or replace it. Nonetheless, it's working very well and the reboot wasn't long at all. Might be the better way to go.
I did this fix and although it did work, now when I wake the device back up it takes a long time to do so. Double tapping the screen doesn't work at all, and when I hit the power button it takes about 5 seconds before the screen turns on. I'm going to try to sideload the ota again and see if it fixes it.
EDIT: Nope, still having the same issue
cred05 said:
I did this fix and although it did work, now when I wake the device back up it takes a long time to do so. Double tapping the screen doesn't work at all, and when I hit the power button it takes about 5 seconds before the screen turns on. I'm going to try to sideload the ota again and see if it fixes it.
EDIT: Nope, still having the same issue
Click to expand...
Click to collapse
Haven't heard of this problem yet.. were you on stock OPR3 with locked bootloader?
There is a new OTA (for same build, but new working OTA) for 8.1 rolling out.
https://plus.google.com/100708818877715770270/posts/dEyVgqmURw2
Please can someone grab the OTA URL?
Settings > System > Developer Options > Take Bug Report > Full Bug Report, then email it to yourself (or PM it to me) and search for the URL ending with ".zip".
I don't have a sailfish device on me right now to do it myself. Thanks!
Edit: here it is
https://ota.googlezip.net/packages/.../1c0e174d9aeefbb176b4dd38b48270a0fd4082d9.zip
pangolin.rollin said:
Haven't heard of this problem yet.. were you on stock OPR3 with locked bootloader?
Click to expand...
Click to collapse
I was on stock 8.0 OTA, locked bootloader. The issue seemed to have gone away by itself. Very strange
Since the majority of the hardware between the devices is gonna be almost exactly the same, I'mma give a shot at rooting it. Picking up tomorrow, so hopefully it goes well
I just got this phone. Let me know how what happens please.
tge101 said:
I just got this phone. Let me know how what happens please.
Click to expand...
Click to collapse
Yeah, I'll keep a heads up. I'm sitting in metro now tryna see what's going on, small argument. Their commercials in Philly don't mention that you need to switch carriers for the rebates.
I'll probably be getting one next week. Says it has 7.1.2 an it weighs less? Cool
attempt
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.
tribal1209 said:
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.
Click to expand...
Click to collapse
Are you trying to root the aristo or aristo 2?
Aristo 2. Sorry, kind of diving in head first with this whole process. If im doing something obviously wrong go easy on me lol.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
Aristo 2
Hmm and you flashed the twrp that was for the aristo right?
Well the TWRP files i used were on *How To* forums posts and youtube videos for the original LG Aristo. Everything was going fine but the touch screen while in TWRP does not work. Maybe there os a different version I can try? Do any of you guys have any ideas, my understanding though is that TWRP has to be created for a specific device once released. Is thats whats going wrong?
you unlocked the bootloader and flashed the aristo 1 recovery thats what you did so far right?
The aristo 1 recovery will not work at all.
The screens are of the same build, but different composition.
That's why I wanted to test this myself before posting further on the subject.
I can risk my phone, most of you cant.
I figured as much. Thanks for the info! Just got mine today. Glad the aristo's battery works in the aristo2 as i bought a couple batteries for it. I still do like the aristo though it feels a bit better in my hand.
Well luckily It seems i have not screwed up my phone. Have reset and wiped it multiple times which was annoying, but seems to be ok. It sucks because it looks like the touch screen alone is whats screwing me over. If only i had a way around it. Then again im sure you guys have a better idea of whats going on. Guess ill just be patient until more is posted on subject.
We need a new recovery for this anyway. Since the aristo 2 isn't gonna have multiple versions (besides the Korean base model the 2 is built after), we should be able to build just one recovery using the model number as it's target, we can make it borderline universal if a new version were to pop up.
I decided against going the metro route, buying mine in bulk. So I'll have one to smash when this is all over.
The TWRP method works the same as the Aristo, and the TWRP recovery IS compatible. However the touch screen does not function.. Is there a way to get it to work?
@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
brad2192 said:
@[email protected]@tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Not to sound sceptical but is this the real deal?
spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Please someone let me know! I want this phone rooted (Its an awesome phone) but want some verification before I start flashing and downloading random files.
spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Yes, it is. What I did was use LG firmware extractor and extracted the boot image, then I proceeded to patch the boot image with magisk manager. Enabling OEM unlock allows me to flash the boot image with the newly-created custom one. Remember though, you should create a backup of your device because enabling OEM unlock will completely erase everything.
brad2192 said:
@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Supposedly the img you posted is simply a modified version of Magisk you posted. Someone please explain to me (Who is new to this whole process) why this supposed explanation does not involve any recovery program or requiring of wiping/clearing any cache or what have you?
Hi All,
In the best interest to provide clarity I'm creating this quick and easy tutorial on how to root your Razer Phone 2 after the Pie Upgrade. Please send me any feedback to improve this post, we need to build up a strong community.
*As usual, I'm not responsible of any damage or brick to your phone, do it at your own risk.
Pre-Requirements:
-Be sure to have at least 70% of charges... or plug your phone to power
-Backup anything you consider important
-Already installed Pie Upgrade via OTA or Side Loaded
-Enable Developer Options
• Open Phone "Settings" and scroll down.
• You will see an option "Build Number".
• Simply tap on it 7 times to enable it on your Android Oreo based device.
• Your device immediately display a message on screen that will say "You are now a developer".
• The Developer Option is now available in the Settings>System>Developer Options. Enjoy!
- Install Android Drivers (https://developer.android.com/studio/run/win-usb) and ADB, I personally recommend -[TOOL]Minimal ADB and Fastboot [2-9-18] - https://forum.xda-developers.com/showthread.php?t=2317790
-Unlock Bootloader
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
• Using ADB commands reboot on bootloader
adb reboot bootloader
• After reboot completes follow phone menus and select "UNLOCK BOOTLOADER"; accept all warnings, after restart you have completed the unlock.
Root and Installing Magisk
Since our phone doesn't have a proven customer recovery fully working (Ex TWRP) Magisk needs to be installed by manually patching the device boot image.
Making leverage of Warrior1988 post [Root Magisk Pie Update For Unlocked Devices] all credits to him. Download the image from his post
• Boot in fastboot mode To boot into fastboot, press and hold the Power button + Volume Down Keys for few seconds; Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Install Magisk Download the apk and install it as usual on your RP2, that should be all.
DONE!!!! You now have a unleashed the beast! Please send me any recommendations to improved this guide.
chpimentelpr said:
Install Android Drivers and ADB
Click to expand...
Click to collapse
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
chpimentelpr said:
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
Click to expand...
Click to collapse
I assume this is where we plug our phone into our computer?
chpimentelpr said:
• Using ADB commands reboot on bootloader
Click to expand...
Click to collapse
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
chpimentelpr said:
• Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash*boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
AbsoluteContingency said:
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
I assume this is where we plug our phone into our computer?
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
Click to expand...
Click to collapse
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Warrior1988 said:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
No asterisk. Cool. Got it. Thank you, dude.
The drivers are the regular ones for android nothing specific, they can be downloaded from their SDK https://developer.android.com/studio/run/win-usb
App root detection?
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Bounty33 said:
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Click to expand...
Click to collapse
You can use magisk to hide the root from those apps. In general banking app are not affected by root. Google pay could be affected, but I don't use it so can't be sure. And you can always unroot.
AbsoluteContingency said:
No asterisk. Cool. Got it. Thank you, dude.
Click to expand...
Click to collapse
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
chpimentelpr said:
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
Click to expand...
Click to collapse
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
AbsoluteContingency said:
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
Click to expand...
Click to collapse
Yes, install them as any other driver.
After rooting can you relock the boot loader or will that brick the phone?
ndragon798 said:
After rooting can you relock the boot loader or will that brick the phone?
Click to expand...
Click to collapse
Not sure, but why you want to relock the boot.
chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Mostly to get rid of the startup message
Very nice. I've rooted a ton of phones over the years, but they had more established communities and had well-explained (and tested) methods of rooting. The previous guide posted (that you referenced) was fine enough, but it was very much lacking a couple prerequisites that I was wondering/concerned about. This guide has cleared all of that up for me, and I now feel confident about rooting this phone.
Just as soon as I charge up the phone and install the OTA I've been avoiding until now... lol. Hoping somebody will make a Magisk module to move the clock back to where it belongs (if they haven't already).
EDIT: Just wanted to add my success story to this. Only thing I had to do that wasn't listed in the instructions (but makes sense) is that fastboot didn't work until I enabled USB Debugging (again, after the wipe and reboot), and I had to very manually tell the computer which driver to use (ADB) after that. Didn't have that issue for the bootloader instructions beforehand (that time, the driver worked automatically), so I figured I'd mention it.
chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
ndragon798 said:
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
Click to expand...
Click to collapse
I don't believe encryption is supported at the moment, and I don't encourage you to try it until TWRP is fully supported since you may end up in a boot loop. I'm eagerly waiting for the full encryption capability, so I will let you know as soon as something come up.
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
ChronosTrigger said:
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
Click to expand...
Click to collapse
i'm glad it helps.
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
xttweaponttx said:
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
Click to expand...
Click to collapse
I doubt the issue with the wifi is related with the image, since it doesn't have anything to do with it. If your phone doesn't detect the update you will need to sideload it. Then try the root guide again. Let us know how it goes, it the first time I hear something wrong with WIFI after rooting.