Any input is welcome. I struggled a bit to get his working so I'm hoping someone else can benefit:
***As always, proceed at your own risk.***
Prerequisites:
This applies only to the XT1980-3 on the Verizon network (prepaid or postpaid). The XT1980-4 (VZW Version) is not bootloader unlockable. For clarification, the XT1980-3 is the "Unlocked", "Carrier Unlocked", or "Retail" version of the phone. I believe there are also Canada specific and US specific firmwares that are also on XT1980-3. This method should also work on the Amazon version of the phone (someone please confirm). You will lose your built in Alexa functions, and your phone will essentially be a Verizon version when completed (except bootloader unlocked, and rooted if you so choose).
Download and install the Motorola Drivers: https://support.motorola.com/us/en/drivers
Download and extract the zip file: https://www.androidfilehost.com/?w=files&flid=301320
It contains the PDF29.105-25-20 firmware, a rooted boot image (patched using Magisk), as well as adb and fastboot programs.
Step 1: Unlock Bootloader
If your phone is brand new, you will have to turn it on, and navigate through the setup process. You can skip everything except for connecting to a WiFi network (even without a SIM card in your phone). You must have some kind of data connection - either mobile data or Wifi to enable "OEM unlocking" (per step 2 below).
Power up your Z4 and enable Developer options: Under settings, go to "System", then "About phone". At the bottom, tap on "Build number" seven times.
Now go back to the "System" menu, and tap "Advanced", then "Developer options".
Scroll down and turn on "USB debugging".
Also scroll down and turn on "OEM unlocking".
Plug your phone into your PC with the factory USB cable. You should see a dialog on your phone prompting you to accept the USB debugging token. Check the box for "always accept", and tap OK.
Follow all steps from the Motorola Website and take note of all warnings. THIS WILL FACTORY RESET YOUR PHONE AND DELETE ALL YOUR DATA:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
You can use the adb and fastboot programs that are in the zip file. Once the zip is extracted, just open the "cmd-here.exe" to start a command window in that folder. Then you can use the "adb" and/or the fastboot" commands from the Motorola instructions.
Once you unlock the bootloader, your phone will restart.
Step 2: Flash the Verizon Firmware
You will need to get back into fastboot mode. If you have enabled "USB debugging" (again), you can type the following into the command prompt (open cmd-here.exe)
Code:
adb reboot-bootloader
otherwise, just hold down the volume-down key and power key until your phone restarts. It should now be in "bootloader" mode (aka fastboot).
Verify that you see "USB Connected" in green on your Z4.
Open up the folder you extracted, and double click "servicefile.bat". The script will run for several minutes. If the script doesn't run, and you only see <waiting for any device>, then you're not in fastboot mode, not connected to your PC, or something is wrong with your drivers. Once the script completes, scroll through the messages and make sure there are no failures or warnings. Then press any key to exit the script.
Step 3: Root (Optional)
If you want to root the phone, go back into the extracted zip folder and open up "root.bat" (while still in fasboot mode). The script will write a patched boot file to your a and b boot partitions.
At the command prompt, press any key to restart your phone.
Enjoy unlocked bootloader, WiFi and Video calling, and Root on Verizon.
If you want to verify that your phone is rooted, download and install the latest Magisk Manager apk. Look for all green check marks when you start the app. https://github.com/topjohnwu/Magisk/releases
Credit:
Batch File Creation: Root Junky - https://youtu.be/njXQYn53SPc
Firmware Download: https://mirrors.lolinet.com/firmware/moto/
Thanks for this guide. Question can the bootloader be Re-locked after flashing and rooted? I can't get screen lock to work when bootloader is unlocked.
Will this work if using a different network? I'm interested in the rooting.
thanks
kewlzter said:
Will this work if using a different network? I'm interested in the rooting.
thanks
Click to expand...
Click to collapse
You don't need VZ ROM if you use it on other phone service.
I use bone stock rooted with T-Mobile and it works 100% including VoLTE and Wi-Fi Calling
kewlzter said:
Will this work if using a different network? I'm interested in the rooting.
thanks
Click to expand...
Click to collapse
I rooted just by patching boot.img with magisk. No issues and fully stock unlocked XT1980-3.
I do have verizon for service, but service provider shouldn't matter. Patching with magisk seems to provide root. I only did it to have magisk hide my unlocked bootloader from safetyNet check and I can continue getting OTAs.
If anyone wants to take November update from VZW, you'll probably need to connect to your PC and use the Software Upgrade Assistant. This went ok, but obviously flashed a new boot image, so I lost root. I looked everywhere and finally found a dump of the boot image. Patched with Magisk and flashed. Seems to be working, and now I have root. https://github.com/AndroidDumps/motorola_foles_dump/tree/9-PDF29.105-74-2789e-release-keys
clevertrevor777 said:
If anyone wants to take November update from VZW, you'll probably need to connect to your PC and use the Software Upgrade Assistant. This went ok, but obviously flashed a new boot image, so I lost root. I looked everywhere and finally found a dump of the boot image. Patched with Magisk and flashed. Seems to be working, and now I have root. https://github.com/AndroidDumps/motorola_foles_dump/tree/9-PDF29.105-74-2789e-release-keys
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-z4/how-to/moto-z4-retail-verizon-firmware-update-t4006197
---------- Post added at 11:16 PM ---------- Previous post was at 11:10 PM ----------
I wrote that thread a week ago and just realized after the post before this one that I should have put it here. With this method you will have the complete zip to reflash if needed.
Is there a way for root without PC? Using magisk and remote adb connect to virtual somehow?
I have just gotten a Z4 to replace my well traveled Moto X, and was happy to see that I could use this procedure to get WiFi calling. Thanks to @clevertrevor777 for the time and effort.
I did run into a couple of problems. For some reason, using the firmware from the zip file gave me a "no valid operating system". However, I was able to use the latest Verizon firmware from lolinet, patch the boot image with Magisk, and have a working, rooted device. It seems that it won't let me set an unlock PIN, password, or pattern, however.
Has anyone else run into this problem with being unable to set a PIN lock after flashing the Verizon firmware, or the patched boot image?
I've read elsewhere that Magisk can sometimes cause problems with PIN lock, so I was going to try running without root and see if I can get it to work.
Other than that, everything else seems to work. It took a while to get WiFi calling working, but that was a firewall issue (over aggressive IPS on PFSense interfering with the IPSec traffic) and not a problem with the phone.
I'm not sure what fixed the problem I was having with setting a lock screen, but I was finally able to fix it by starting over from square one. I did a couple things differently so I'm not sure what exactly solved it, but it was either waiting to set the screen lock and not doing it during the initial setup process, or making sure it was set prior to patching the bootloader and flashing the patched loader.
Anybody found a dump of foles PDFS29.105-74-4? Seems like it's not available here yet: https://github.com/AndroidDumps/motorola_foles_dump. I just need boot.img before taking the update via VZW Software Upgrade Assistant. Or is there a way to grab the full ROM image from the temporary downloads folder of the Upgrade Assistant and extract the boot.img?
Anybody found a dump of foles PDFS29.105-74-4? Seems like it's not available here yet: https://github.com/AndroidDumps/motorola_foles_dump. I just need boot.img before taking the update via VZW Software Upgrade Assistant. Or is there a way to grab the full ROM image from the temporary downloads folder of the Upgrade Assistant and extract the boot.img?
Click to expand...
Click to collapse
There's a post elsewhere about how to grab it from the Upgrade Assistant, but that didn't work for me. I have been unable to find the temporary downloads folder at the path where the poster said it was. I'm not sure if its location changes for different Windows versions or what is going on.
I waited for the full ROM to show up on mirrors.lolinet and then downloaded that to get the boot.img file to patch.
---------- Post added at 03:39 AM ---------- Previous post was at 03:36 AM ----------
This is the post I was referring to, but I don't have any MSU folder on the path described in there.
https://forum.xda-developers.com/moto-z4/how-to/moto-z4-retail-verizon-firmware-update-t4006197
I was able to get it from the upgrade assistant on my computer again from same location as last time.
---------- Post added at 05:54 PM ---------- Previous post was at 05:51 PM ----------
Are you using Lenova assistant or the Verizon once installed onto your computer from your device? I'm using Verizon and maybe it's different for each user. Look through the folders for any changes when it's starts the download.
slab_bulkhead said:
[/COLOR]This is the post I was referring to, but I don't have any MSU folder on the path described in there.
https://forum.xda-developers.com/moto-z4/how-to/moto-z4-retail-verizon-firmware-update-t4006197
Click to expand...
Click to collapse
Worked for me! Found the MSU folder and followed the instructions from that link! I'm using the VZW tool installed from my phone. Just plug your phone into your Windows PC (Windows 10 for me), then on your phone choose Software Installation for the USB connection type. There should now be a Windows installer on a new drive on your PC. Install the Software Upgrade Assistant from there. I waited until after 100% download on the update process, then copied the gz file to another folder and uncompressed it with WinRAR. Easy peezy lemon squeezy!
clevertrevor777 said:
Worked for me! Found the MSU folder and followed the instructions from that link! I'm using the VZW tool installed from my phone. Just plug your phone into your Windows PC (Windows 10 for me), then on your phone choose Software Installation for the USB connection type. There should now be a Windows installer on a new drive on your PC. Install the Software Upgrade Assistant from there. I waited until after 100% download on the update process, then copied the gz file to another folder and uncompressed it with WinRAR. Easy peezy lemon squeezy!
Click to expand...
Click to collapse
I was using Windows 7, I wonder if that's why my file went to another unknown location.
Will this work on the amazon variant?
nooneelsesdroid said:
Will this work on the amazon variant?
Click to expand...
Click to collapse
Does it have a software update utility for computer? Then it might
nooneelsesdroid said:
Will this work on the amazon variant?
Click to expand...
Click to collapse
Maybe. There would be two big question marks.
1.) Is it possible to unlock the bootloader on the Amazon variant to install the initial VZ ROM image?
2.) Would the VZ software update utility accept that model for upgrades?
It all seems to work for my unlocked version, even though the update utility knows it's XT1980-3 and not -4.
OK I found out I could unlock it. I don't need the verizon rom I just want root. Is it possible to skip the vz rom install and just root?
nooneelsesdroid said:
OK I found out I could unlock it. I don't need the verizon rom I just want root. Is it possible to skip the vz rom install and just root?
Click to expand...
Click to collapse
You should be able to by using Magisk to patch the boot.img file for whatever ROM you want to use, and then flashing the patched boot.img file in fastboot.
Related
WELCOME
to the WINDOWS Bell Atrix 0.37.4 update guide on how to go from 2.2.1 to 2.2.2! (without problems )
===================================================================================================================================================
WARNING
Do not attempt any of these steps if you are on an international firmware. You will probably brick your phone. This guide was made to help people who are having trouble updating from 0.37.4 to the new bell 2.2.2.
Bell users:
Please note that flashing files to your phone and modifying system contents can brick your phone. However, the method I am sharing worked flawlessly for myself and others.
Before beginning:
You need root access on your phone. If you are not sure what root access is, you shouldn't be having problems updating, because you wouldn't have modified system files. Regardless, here is a thread on how to root a bell atrix.
Guide:
Step 1:
Download Titanium Backup from android marketplace, and back up all of your apps and games. This is necessary only if you want to have an easy reinstall of most of your apps and games, as we will be wiping data off of the phone. (if you have another backup program, it should work just fine. Make sure it saves the backup to a folder that you can copy onto your computer)
Step 2:
Remove the external microsd card from your phone (if you have one). This is simply for safety purposes, as we don't want any data being wiped off of this (we don't need the microsd any time during the process).
Now, copy (or cut) all of the data from your internal storage to your computer, just in case, and we are about to wipe data off of your phone.
Step 3:
Format your phone. This can be done two different ways.
The first method is the simplest:
Menu -> Settings -> Privacy -> Factory Data Reset.
The second method (if for some reason you can't do the first) is:
Turn off your phone. Turn it back on while holding the volume down key. It will show the word FastBoot. Keep pressing the volume down key until you reach android recovery. Press the volume up key. Wait patiently. Once a little man appears, there should be a menu. If there isn't, press both the bottom left and bottom right corners of the screen simultaneously. That should bring up the menu. (give it a few tries, it takes me 8-10 lol). From this menu, press volume down until you get to wipe data, then press ok on the bottom left corner (give this a few tries too).
Step 4:
Your phone should now be acting like you just bought it. It should, upon reboot, prompt you to enter your country.. etc. Make sure you either use your existing motoblur account, or create a new one. It is just important for you to have a blur account for the update process (my phone gave me hell when I didn't have one). Do what is necessary to get your phone up and running again.
Step 5:
This is where the fun begins. Reroot your phone usinggladroot(or any other root method you know how to use). Download Superuser, install it, then download Root Checker from android marketplace to confirm root access. Whenever a Superuser popup comes up, confirm / say yes (and make sure the remember box is checked).
Once you have confirmed root access, proceed to the next step.
Step 6:
Download Tenfar's CWM recovery, and install the apk on your phone. Follow the instructions inside of the app to install recovery and enable recovery mode.
Step 7:
Download these two files, and put them in the root of your internal storage. (By root, I mean in the very first directory, ie. F:/put file here)
http://dl.dropbox.com/u/23800522/Blur_Version.0.37.4.MB860.BellMobility.en.CA.zip
http://dl.dropbox.com/u/23800522/Blur_Version.0.37.4.MB860.BellMobility.en.CA.crc
Step 8:
We are now ready to start fixing up the phone, and preparing it for the update.
First of all, we need to make sure ADB (the program we will be using on our computer) has root access on our atrix when it is plugged into our computer via usb.
Before plugging in your atrix via usb, enable USB debugging via:
Menu-> Settings-> Applications -> Development -> Check USB Debugging.
Now plug the atrix into your computer, and set the USB connection to: None. Check to make sure USB Debugging is in your notification bar.
Download these files onto your computer if you do not have the adb files yet. Extract the files preferably into the root of your hard drive (ie C:/ ) is just makes things easier this way.
Now open up command prompt.
If it is not in the directory where the adb.exe file is, you will need to type:
cd C:/
into command prompt. This says "change directory to C:/" (or wherever you put the files, could be cd C:/Program Files/ could be anywhere. wherever you extracted them to.)
Once in this new directory, type this into command prompt and press enter:
adb devices
If a device pops up (mine said TY290380 or something like that) that means that it recognizes your atrix. That is great news. We now have to enable ADB root access on the phone.
If nothing pops up, or it says some sort of error, you are not in the directory where adb.exe is located. Navigate to the proper directory.
Now, type the following command:
adb shell
One of two things can happen here. It will either create a new line with a $, or a new like with a #.
blah blah C:/ adb shell
$
or
blah blah C:/ adb shell
#
If a $ came up, you need to prepare a command BUT DONT PRESS ENTER YET. Type in "su", but dont hit enter. Now go to your phone and unlock your screen. After you unlock your screen and can see your homepages, press enter on your keyboard doing the "su" command. Now look at your phone. A superuser request should appear. Hit yes, and make sure that "remember" is checked. If not, it is ok, as long as the su command went through on your screen. it should now show a # on your command line.
For those of you who had a # on your command line, type in shsu and hit enter, then type in su and hit enter (just to play it safe ).
We are now ready to flash the first files to our device. You can close the command window.
Step 9:
Download this file. It is the original unmodified system partitions and files (thank you NFHimself). Extract the file using winrar or 7zip.
Change your USB connection on your phone to: Mass Storage, wait a minute or so, and then put the extracted file "mmcblk0p12.bin" in your internal storage on your phone. (ie. F:/ )
Step 10:
Dismount the phone from your usb devices via windows hardware manager. Unplug your atrix from your usb. Reconnect it, and choose connection type: none. Make sure usb debugging is in your notification bar.
Now, re-open command prompt. Renavigate to the directory where your adb files are located using the "cd C:/" command (or wherever your files are). Once there, perform "adb devices". Make sure a device is there. Next, perform the command "adb shell". You should have a #. Type in shsu, hit enter, now su, hit enter (just to be sure).
Now copy this command and hit enter (you have to right click paste into cmd prompt):
dd if=/sdcard/mmcblk0p12.bin of=/dev/block/mmcblk0p12
This will begin the flashing process, which will restore all stock system partitions allowing us to update properly. However, it's not over yet .
Mine took a few mins, do not panic. Simply wait for it to say "Complete" in x amount of seconds or whatever. Your phone may crash, but it should boot up fine (if not, that is why we have installed Tenfar's CWM )
After it is complete, turn off your phone. Keep it connected to the computer.
Step 11:
Boot up your phone holding volume down. Navigate to android recovery using volume down. Volume up. Open up the menu with the bottom left bottom right press. Go to clear cache. Press OK. Now reboot your phone.
You can now update through settings and it should work properly. If not, respond in here and I will guide you a few more codes, but it should work.
The phone should now boot up, and it should be running android version 2.2.2.
Regard this thread for how to root the new bell update. Just a heads up, it wiped my internal storage and SD card, so remove and backup that stuff. Lol. But it did root.
Now reinstall your backup program, and get your phone going again!
If you have any questions or problems please post them here and I will reply ASAP, personal messages are hard to keep track of. Thanks again to NFHimself for supplying files and code.
Cheers!
PS: I just finished exams, yay!?
Please say if you notice anything misspelled, etc. Gratzi
You are the f***in man for posting this. Thumbs up to NFHimself for his contribution too!
Links
Crud, your links for the files in dropbox aren't working.
Silvercloak5098 said:
Crud, your links for the files in dropbox aren't working.
Click to expand...
Click to collapse
You sure? I clicked them both myself to make sure they work.
How don't they work?
FYI: I'm reuploading them to megaupload as we speak anyways
IrshaadH said:
You are the f***in man for posting this. Thumbs up to NFHimself for his contribution too!
Click to expand...
Click to collapse
When I got my phone to update to 2.2.2 it felt amazing.
I just wanted to spread the love
Thank you so much!! You don't know how frustrated I've been all day! The only problem I had was that my root was gone after I flashed it, but I just updated through settings and it worked flawlessly
tyrkk said:
Thank you so much!! You don't know how frustrated I've been all day! The only problem I had was that my root was gone after I flashed it, but I just updated through settings and it worked flawlessly
Click to expand...
Click to collapse
NP! Just glad you got your update.
I changed the steps so that the last step is simply updating via settings. If that doesn't work for people I will help them out in this thread with the more complicated coding way.
Cheers!
Couldn't step ten be used to revert to stock from an international sbf?
Sent from my MB860 using XDA App
Ok..quick question. You said not to install for those using any international version. I have run the Telstra sbf at one point..as well as had the Greyblur rom on. Before installing the Telstra I had made a backup using CWM, and a few days ago I had to revert to my old backup due to a rogue app. In my About phone, it tells me my System version is Blur_Vision.0.37.4MB860.BellMobility.en.CA with a Build number of OLYA_U4_0.37.4.
Would this be still safe for me to do seeing's how it seems i'm back to my "Bell sbf" or is there still going to be some Telstra files in there that could cause me some problems?
I made it through to the end of step 10 and the phone was looking good. Then when I shut off the phone and tried to go into Android Recovery, it keeps going to the triangle symbol and I have to reboot.
After a couple times of that I decided to check Android Recovery from inside the app list and it said I no longer have root access.
Any ideas what to do now??
Rickroller said:
Ok..quick question. You said not to install for those using any international version. I have run the Telstra sbf at one point..as well as had the Greyblur rom on. Before installing the Telstra I had made a backup using CWM, and a few days ago I had to revert to my old backup due to a rogue app. In my About phone, it tells me my System version is Blur_Vision.0.37.4MB860.BellMobility.en.CA with a Build number of OLYA_U4_0.37.4.
Would this be still safe for me to do seeing's how it seems i'm back to my "Bell sbf" or is there still going to be some Telstra files in there that could cause me some problems?
Click to expand...
Click to collapse
Depends on whether or not you're still on the telestra framework. If you're confident with your ability to recover from a potential brick via early usb enumeration id go for it.
bdking2 said:
I made it through to the end of step 10 and the phone was looking good. Then when I shut off the phone and tried to go into Android Recovery, it keeps going to the triangle symbol and I have to reboot.
After a couple times of that I decided to check Android Recovery from inside the app list and it said I no longer have root access.
Any ideas what to do now??
Click to expand...
Click to collapse
Edit: See my lower post first, then this one
Open up the menu in android recovery by tapping both the bottom left corner and bottom right corner of the screen at the same time.
It should show you an error if there was one.
Does the phone boot fine?
You should lose root access. When you flash the .bin it restores your bell to stock like you got it from the store. That allows you to update.
Most importantly open up the recovery menu when you see the triangle by tapping the bottom left and right corners simultaneously. Itll take a few tries.
IrshaadH said:
Couldn't step ten be used to revert to stock from an international sbf?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
No, since you are on an international framework it will probably brick your phone.
That .bin file contains the system partitions from the stock bell framework.
If you want to try go ahead but I think the odds are against you
bdking2 said:
I made it through to the end of step 10 and the phone was looking good. Then when I shut off the phone and tried to go into Android Recovery, it keeps going to the triangle symbol and I have to reboot.
After a couple times of that I decided to check Android Recovery from inside the app list and it said I no longer have root access.
Any ideas what to do now??
Click to expand...
Click to collapse
Bdking I have another idea. if you can boot up your phone, re-root it using any normal methods, then install CWM. Boot into CWM recovery mode and clear the cache from there. Then do step 11.
Chances are the update file is hanging out in your cache so when the android recovery sees that it immediately tries to install the messed up package.
Thats why you should clear cache on CWm because it wont try to install anything automatically from the cache. Then do step 11.
Hope it helps, Mag.
No my phone boots fine. And now I can get into android recovery to clear cache and have done so. But before I read your response I rooted my phone again.
Should I just restart everything?
bdking2 said:
No my phone boots fine. And now I can get into android recovery to clear cache and have done so. But before I read your response I rooted my phone again.
Should I just restart everything?
Click to expand...
Click to collapse
No you should be good to go try to update via settings.
You flashed the bin right?
If so you're good to go
I flashed the bin for sure. But wasn't sure about the process because I rooted again.
bdking2 said:
I flashed the bin for sure. But wasn't sure about the process because I rooted again.
Click to expand...
Click to collapse
Root shouldnt change anything only deodexing/webtop mod/ theming should mess it up.
If you flashed the bin go for it. Worst thing that can happen is that the update fails.
In that case, redo step 10, then do step 11.
Magnetox said:
No, since you are on an international framework it will probably brick your phone.
That .bin file contains the system partitions from the stock bell framework.
If you want to try go ahead but I think the odds are against you
Click to expand...
Click to collapse
So, there is absolutely NO WAY I can get back to the Bell framework from 2.1.1 without an actual Bell sbf?
IrshaadH said:
So, there is absolutely NO WAY I can get back to the Bell framework from 2.1.1 without an actual Bell sbf?
Click to expand...
Click to collapse
NFHimself knows a way.
But hes a master of code.
Pm him, he might be able to help you.
He was happy he got his bell 2.2.2 thoough. so im assuming it wasnt easy.
Alright.
Let me first give an overview of where it all begins. If this is the state you are currently in then this guide is for you. To make this guide, I have benefitted heavily from various threads all across the web. So I decided to put it all at one place. This guide would not have been possible without a very comprehensive thread started by "kiwiandy" in the same forum and many others. Ok, so here it is. Please read below, if any of the situations resemble yours, this guide is for you.
ALL CREDITS OF BELOW FILES GOES TO THEIR OWNERS. I AM MERELY REPLICATING THE INFORMATION WITH A GUIDE AND TWEAKS FOR 802W. IF ANY VIOLATION OF ANY RIGHTS TAKES PLACE, PLEASE PMA ND FILE WILL BE REMOVED.
You have purchased HTC Dual SIM from China which is the UNICOM version
You have purchased HTC Dual Sim 802w from the web or any other place and have the chinese phone shipped to you. However you are not sure if its China UNICOM version.
When you go into settings and "About" there is an option of "Software Updates"
When you go into settings and "About" there is NO Software Update option in your 802w HTC dual sim
You want to get rid of Chinese bloatware and are looking for a straightforward Cleaning program that DOES NOT require root.
You want to be able to have custom recovery and flash updates.
You want to or DO NOT want to ROOT your device. (If its not already rooted)
You want the "LOCKED" bootloader and do not want the complications of HTCDEV or "UNLOCKED" or "TAMPERED" bootloader. (Although this guide works for both)
You want English Language and Google Services.
Let me first clear a bit of air with respect to the common terms used in HTC world. One may and may not agree to this. However, as you read through the guide there will be substantial evidence to prove this.
S-OFF: This sits at the top. If you are not Root and if you are not having an "UNLOCKED" bootloader you can stil do ANYTHING with your phone including installing custom recovery and installing images and updates. With a S-Off you dont even need custom recovery to install OTA updates via zip files that you have already downloaded. You can update via the android Stock recovery. You dont need to have root access or unlocked bootloader. S-Off is basically security off and allows unsigned zips to be flashed. With a S-OFF you can instal custom recovery like CWM or TWRP even if you are NOT rooted or even if you have a LOCKED bootloader.
Root happens once you have a locked bootloader. You may or may not have S-Off. Most work can be done if you are rooted. So you dont really need S-OFF. However, those who do not wanr "UNLOCKED" or "Tampered" bootloader written on top of their boot screen they should consider s-off rather than root. Root is basically access to system files and not certain partitions of your phone.
UNLOCKED bootloader allows you have root acces. But as we move on, this method will die and the flashign method of Hboot will rise. This guide can eb used by all the people who either have UNLOCKED Bootloader or LOCKED bootloader or Tampered.
Ok, I think that pretty much clears it. I have tried to answer issues that require a lot of searching here. One more basic thing that needs clearing.
There are two ways to flash recovery or updates if you are S-OFF. One way is to use the HTC DEV method to unlock bootloader and instal via "adb" and fastboot commands.
The second easier way is to use a "Locked" bootloader but S-OFF and No root method to instal ROMS and custom recovery bia "HBOOT" method.
For HBOOT method you need flashable ZIPS. To instal via fastboot requires IMG files. Benefit of this method is that you can do factory reset from the phone and phone will revert to its factory position. No need for doing ti from clockwork mod.
Now Over to the GUIDE. I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR PHONE. IF YOU DONT UNDERSTAND ASK. IF YOU AR ENOT SURE AND DO NOT OWN YOUR OWN ACTIONS DONT TRY THIS.
Please read the whole thread. Reading one part wont help. Poeple with already unlocked bootloaders need to Relock bootloader first. I WILL NOT BE RESPONSIBLE.
Download the Stock 802w firmware RUU file from the following link http://d-h.st/aj4.
This will be a zip format. If you are on Windows, Rename the file as "PN07IMG". If you are on MAC rename the file as "PN07IMG". There is no need to add ".zip" since the downloaded file already has the extension of zip. Save this file in a folder on your PC named "Stock"
However, if after applying the procedure below, you get stuck at "verifying image" or "image not found" please remove the ".zip" exptension from the file. Just rename it. Do not UNZIP.
Download the drivers for your phone. You can google it. Its available easily for download. Even if your phone is recognized by your PC as storage device stil you need to download the drivers for effective adb push if required ever.
Link is : https://dl.dropboxusercontent.com/u/3372901/HTC_drivers_Win7_x64.zip
Unzip to a folder
On your PC goto device manager in the control panel or by right clicking on the my computer icon and selecting properties.
In the device manager, please see if your HTC is listed under android devices. If it is then you dont need drivers.
If however there is an item in the list mentioned UNKNOWN then you need to instal the dirvers provided herewith. These work for both Windows 8 and Windows 7.
These drivers have to be added in manually by selecting location of driver and browsing to that folder.
Once the drivers are installed. Proceed to the next step.
Download the 4.2.2 update to any folder of your PC. Link to Official 4.2.2 OTA update is
https://dl.dropboxusercontent.com/u/3372901/update.zip
Save this file and do not rename it.
Next proceed to download the "ZIP" version of CWM clockwork mod recovery for 802w. This is a special file and has to be like that. Special since it is custom to every version of HTC one. This is for HTC 802w.
Usual CWM recovery files are in IMG format. This one is in ZIP since we are bootloader locked. And we want to keep the botloader lcoked and stil flash recovery via HBOOT.
CWM recovery download page has an IMG for HTC ONE. This DOES NOT work with 802w Dual Sim. You have to use my version below.
For 802 t and 802 d, I can upload another version of CWM but for that Please download a small file called "CID" for google play store.
Run CID on your HTC One phone. and a list of values will appear. Carefullt jot down "cidnum" "mainversion" "bootloader" and "firmware" numbers. Please note this is the method you must use. I found out that using adb command to get all variants gives incorrect values.
My Zip version of CWM is:https://dl.dropboxusercontent.com/u/3372901/PN07IMG.zip
Please save this file in a different location form the previous stock RUU file you downloaded in the beginning of this thread. They both have same names. Hence store this file in a folder on your PC called "cwm". If you need recovery for 802t 802d please mention the values stated above and i can tweak the recovery file to work that way.
TWRP recovery for 802w I stil do not have. if any one has it I fill be willing to make a ZIP version.
Alright, Now off to flashing. Follow these steps CAREFULLY. Every word has a consequence. Please follow it as is. This works for all LOCKED AND UNLOCKED bootloaders with or without root. For LOCKED bootloaders you need to be s-off. Now first we got to know if you are S-off or not. To check this,
Restart your phone. Shut down doesnot work sometimes due to fastboot. SO restart your phone.
When your screen goes blank during the restart, immediately press the VOL DOWN KEY and the Power KEY simultaneously and keep them pressed down. Until the phone goes int a white colous Boot screen with text.
ON the top of the screen will be written : LOCKED or UNLOCKED or TAMPERED. and after that in the next line will be either "S-off" or "S-on"
If you are S-on you need to unlock your device via htc dev and there are tons of threads on it. So unlock your phone and then follow this guide below.
However, if you are S-off you dont need to do anything except follow the guide.
Now the flashing part.
Format your sd card from your phone. Thats the best way to avoid file errors. Just format it within the phone. The command should be in settings under storage.
Once the sd card is formatted, connect your phone to PC. Make sure USB debugging is on.
Copy the PN07IMG.zip file (size approx 870MB) that you downloaded in the folder named "stock" and paste it on the sd card. Do not create any folder on the SD card. Just copy the file to the root of the sd card.
Make sure the file you copied is on the root of sd card. Root fo sd card means when you open the card from your PC the file is right there and not inside any folder.
Also make sure that you copy the file and paste it to your sd card and you DO NOT "send the file to" sd card. Sending the file just creates shortcut and not the original file.
Recheck that the file name is "PN07IMG"
if all is good, then unplug your phone from your pc and reboot.
When you see the blank screen during restart press the VOL DOWN key and the power key simultaneously and keep pressing till the whote screen with text shows up.
Your phone will automatically start searchign for file named "PN07IMG" and will find it and start loading it. Stay calm and let it do what it wants.
If however, the screen shows an error like "IMG file not found" or file misisng and takes you back to the white screen with text on it and options like "Fastboot" and "recovery" etc… that means the file name is incorrect. Remember the file we need is PN07IMG in a zipped format.
A simple check for this is that the file should be zipped but there should be no ".zip" in the name. If thats the case you are good. But if you see the file zipped and also with a ".zip" in the name that means its named incorrectly. Correct file is "PN07IMG" and it should be zipped.
Do not zip the file yourself. The file in the link i provided is already zipped. Just rename it.
If however, your phone system detects the file and starts uploading it and later gives an error while verifying that means the file you downloaded is corrupt. Re download the file.
If however, all goes well, the system will autoflash your phone with the STOCK RUU file of 802w from China Unicom.
System will reboot. and then reboot again. and then finally you will see the welcome screen of HTC
You will be greeted in a chinese language. Just click on the sceen at the language and you can choose english US.
You can skip the settings and accounts and simply skip through to the homescreen of the phone.
Go into Apps. There is a app called "File Manager". run it
GOTO your esternal sd card from the phone and delete the PN07IMG file there. We dont need it any more.
Conenct your phoen via wifi or 3g. There is an app called htc marketplace in your appdrawer.
Run it. Swipe on the first two pages and you come to the main screen of the app.
in the search box above type "GMS" and click search
The apps listing will show "GMS" app and some words in chinese. click on that to download.
Let the download finish. Once the download finishes. Do NOT CLICK ON THE APP.
Remove you external sd card from the phone. Just remove it.
Now RUN the downloaded GMS app. Its in your app drawer.
Click ok in the dialogue that appears. OK is the right button option.
A file will start downloading. It will be of 150 MB approx. Let it download. Dont use the phone this time.
Once the file is downloaded click on it and you will be presented with the Dialer in the HTC phone. There is a code writen on the screen somethign like *#42*…… . Type the whole code as is int he phone and VOILA the phone will restart. If it doesnot, you typed the code incorrectly.
Phone will restart and again restart and then the phone boots into the normal mode but this time you have the Google Play store and all google accounts available wiht you.
Now put back the external sd card in your phone.
Connect yoiur phone to PC. Copy the file downloaded above called "update.zip" onto the root of the folder. Remember sd card should have no folder. THe file update has to be on the main root of the sd card.
Reboot your system and again hold the VOL down and Power key. Release the keys when the phone boots into whote screen with text.
The phone will try to search for an image which it will not find. Now it will present you with a menu stating " FastBoot" and "recovery" and few other options.
Select Recovery. Do this by pressing the VOL Down key once. and then to select press "Power key". dont press both keys together.
Your phoen will now boot into somehting with a red or grene triangle with exclamation mark or sync mark.
Carefully, press the VOL UP key and while pressing it press the Power key and release both.
The phone will now show options and one of them is "Instal zip from sd card"
If no options are shown, repeat the VOL UP and power key thing again.
Choose instal zip from sd card and choose the "update" file you copied to root of sd card.
The system will verify the image. If verification fails, the file downloaded was not correct or the name is not correct. If all goes well, the system will reboot twice and then you are back into your homescreen. Only this time you have the 4.2.2 update Stock.
Stil do not setup your phone. Reconnect it to your PC.
Copy the "PN07IMG" file that you downloaded in the folder named "cwm" on your pc to the root of your sd card. Please make sure the file is copied as is to the root of the sd card.
Reboot your phone and as always hold VOL down and POWER key. until you see the white screen.
Your phoen will autodetect the file and start flashing it. This the CWM recovery file.
System will reboot. and you will come back to your homescreen.
Download the "ROMCLEANER" file. Link is at the end of this post. All credits goto the team of ROM CLeaner. However, the 802w text file has been edited by me to make sure that HTC works and only the chinese bloatware is removed. The file is edited so that common problems like Smart dial not working after romcleaner flash do not occur.
Copy the ROMCLeaner zip file to the root of your sd card again. Also delete the PN07IMG file form your sd card. This is important.
Reboot. and again hold down the VOL DOWN and POWER key until you go into the white screen.
Now choose "Recovery" option by pressing VOl down and then selecting wiht power key.
You are now into Clockwork recovery. LOCKED BOOTLOADER NOT ROOTED. and stil in cwm recovery.!!!
choose flash zip from "external sd card" option and select the ROMCleaner zip file.
Just keep pressing next, or if touchscreen not working, use vol up key select and power key to choose NEXT. However, make sure in one of the options you choose "Sense"
In the last dialogue it asks for ROMCLEANER.. its the second option. Choose it.
Finish the task and your job is done. Chinese bloatware removed. Reboot phone.
You are now into your homescreen.
Setup your phone. If need be back it up with nandroid using your CWM recovery partition.
For those who have unlocked bootloaders and rooted. You may need to RELOCK your Bootloader before the flashing of the STOCK RUU ROM. Instructions to relock are easily available via google.
Cheers.
Link of customized ROMCleaner for 802w : https://dl.dropboxusercontent.com/u/3372901/ROM_Cleaner_v1.6_CWM.zip
I am getting PMs on the above guide.
I suggest all to post questions here.
yahya.hamid said:
I am getting PMs on the above guide.
I suggest all to post questions here.
Click to expand...
Click to collapse
Thanks for the guide. It's very informative. Can you give some more guidence on the 802t?
Dear prompt. Would it be possible to revert after installing update 4.2.2 to 4.1.2 again setting again PN07IMG_M7C_DUG_JB_50_HTCCN_CHS_CU_1.12.1402.1_Radio_1237.17.18.0423_release_318980_signed.zip?
The fact that no update setting OTA to 4.2.2 to 4.1.2 clockworkmod backup ROM 4.2.2 problem "black screen", i.e. when charging the phone to 100% of the screen power button does not turn on until the battery is discharged to 90%.
Help required please
HI
I also am having problems upgrading my rooted 4.1.2 to 4.2.2. I have all the files downloaded and ready. First file was okay but when phone restarted, still the same as before, nothing changed. I tried to apply the 4.2.2 update.zip but it brings an error in cwrm.
Also when I switch my phone on it is telling me the phone is for development purposes only and there is no option to update software through Settings> About.
update.zip 4.2.2 downloaded 11 times. Continuing the upgrade through CWM an error bulid.prop
yahya.hamid said:
Let me first give an overview of where it all begins. If this is the state you are currently in then this guide is for you. To make this guide, I have benefitted heavily from various threads all across the web. So I decided to put it all at one place.
Click to expand...
Click to collapse
Thanks for this great job. But as I'm a total noob in terms of flashing smartphones (well, I did it years ago with my Motorola Razr, though), am not too familiar with the entire terminology (rooted, locked/unlocked bootloader, s-off etc.) and all of the implications and consequences of this stuff yet, and therefore did understand max. 75% of your post, I'm afraid I'd brick the phone if I'd try to follow this guide.
OTOH: I desperately need this Dual SIM phone (note that I don't have it yet), as there currently seems to be no alternative to it. For now, I have just two questions:
You're just mentioning the English language ("You want English Language and Google Services"). Will the phone after this procedure offer a multilingual interface, though (incl. German)?
Would you (or anybody else in this forum) be willing to flash this phone for me in the way described in this guide (which would be generously compensated, of course)?
More questions are likely to be raised later on if I'd get a positive answer to 1. (and a negative one to 2.).
Cheers, myfreexp
donraj86 said:
I also am having problems upgrading my rooted 4.1.2 to 4.2.2. [...] Also when I switch my phone on it is telling me the phone is for development purposes only and there is no option to update software through Settings> About.
Click to expand...
Click to collapse
From what I have read in various threads and believe to have understood, this is one of the logical and unavoidable consequences of the fact that your phone is rooted.
I may be wrong, though. As I said in my previous post, I'm a noob, but one who is at least trying to read and understand. So please don't take my statement as the absolute truth, unless it will be confirmed by more competent folks/devs.
truely awsome, but ..
hey man great work this guide is very useful, but the stock 802w ruu file is currupt, i have downloaded serval times and still some of the files are currupt
Upgrade Problem
Hi , followed the guide from the first step , got stuck on step 39 - I don't get install from sd card , i get apply from sd card , it then halt's with an error "invalid command" and reboots - where do i go wrong ??? TKS
drpweb said:
Dear prompt. Would it be possible to revert after installing update 4.2.2 to 4.1.2 again setting again PN07IMG_M7C_DUG_JB_50_HTCCN_CHS_CU_1.12.1402.1_Radio_1237.17.18.0423_release_318980_signed.zip?
The fact that no update setting OTA to 4.2.2 to 4.1.2 clockworkmod backup ROM 4.2.2 problem "black screen", i.e. when charging the phone to 100% of the screen power button does not turn on until the battery is discharged to 90%.
Click to expand...
Click to collapse
Yes it is possible. If you have followed my guide. Since you have a locked bootloader just use the hboot method above, rename the file and you are back to 4.1.1
donraj86 said:
HI
I also am having problems upgrading my rooted 4.1.2 to 4.2.2. I have all the files downloaded and ready. First file was okay but when phone restarted, still the same as before, nothing changed. I tried to apply the 4.2.2 update.zip but it brings an error in cwrm.
Also when I switch my phone on it is telling me the phone is for development purposes only and there is no option to update software through Settings> About.
Click to expand...
Click to collapse
Please state which state you started from and which steps you followed.
galzamir1 said:
hey man great work this guide is very useful, but the stock 802w ruu file is currupt, i have downloaded serval times and still some of the files are currupt
Click to expand...
Click to collapse
ok lemme upload it on my box
rempi965 said:
Hi , followed the guide from the first step , got stuck on step 39 - I don't get install from sd card , i get apply from sd card , it then halt's with an error "invalid command" and reboots - where do i go wrong ??? TKS
Click to expand...
Click to collapse
apply from sd card is ok
is there a way to use any of m7 rom with 802w ?
hi there:
Thanks for the great guide.. i am using this with my HTC One 802w but when i wanted to flash the zip file for CWM recovery file it return with an error of CID incorrect...
can you advice?
I try to extract the required value via using apps "CID Getter" but it generate a lot of information.
post these online to see whether this will help....
CID: HTCCN703
Bootloader: 2.26
Build version codename: REL
Build version incremental: 211355.2
Build version release: 4.2.2
Rom version: 2.17.1402.2
PS: For mainversion & firmware i cannot get these from the apps above but try to source for similar info.. not sure whether it is help
Appreciate your help as i think i am approaching the last part to get a full workable 802w dual sim...
Need your help to clear this last hurdle before i remove all the annoying apps that Unicom install..
---------- Post added at 06:11 PM ---------- Previous post was at 05:31 PM ----------
wolfmastertom said:
hi there:
Thanks for the great guide.. i am using this with my HTC One 802w but when i wanted to flash the zip file for CWM recovery file it return with an error of CID incorrect...
can you advice?
I try to extract the required value via using apps "CID Getter" but it generate a lot of information.
post these online to see whether this will help....
CID: HTCCN703
Bootloader: 2.26
Build version codename: REL
Build version incremental: 211355.2
Build version release: 4.2.2
Rom version: 2.17.1402.2
PS: For mainversion & firmware i cannot get these from the apps above but try to source for similar info.. not sure whether it is help
Appreciate your help as i think i am approaching the last part to get a full workable 802w dual sim...
Need your help to clear this last hurdle before i remove all the annoying apps that Unicom install..
Click to expand...
Click to collapse
thanks...manage to sort out the problem myself via editing the correct CID....
clear everything.. thanks TS for the great help..
cheers..
Stock ROM corrupt?
Thanks for this very useful guide, but the stock rom file seems corrupt - tried downloading it six times.... mentioned previously in an earlier post as well. Please could you help by uploading again? Many thanks!
Cheers!
Can I Just Update to 4.2.2
Hi
i bought my HTC 802W from Duabi, where i have found the software exactly same 1.12.1402.1_Radio_1237.17.18.0423 , so is it Ok to Move forward to the step after flashing the stock rom , or should i start from the scratch , please note i have Google ply Market already .
Thanks in advance
Dear Yahya
I just finished the steps successfully, only one issue is that still there is some apps in chines language and when I boot or shut down there is a WO and unicom logo, is there a way to remove them
Stuck at update.zip
Hi Yahya - I'm stuck at step #41 ... the update.zip verifies OK, goes to install and then gives the error msg:
assert failed: file_getprop("/system/build.prop". "ro.build.fingerprint") == "htccn_chs_cu/m7cdug/m7cdug:4.1.2/JZ054K/186762.2:user/release-keys" || file_getprop("/system/build.prop". "ro.build.fingerprint") == "htccn_chs_cu/m7cdug/m7cdug:4.2.2/JDQ39/211355.2:user/release-keys"
Installation aborted.
I've downloaded the update.zip file 6 times and retried.
Please, please help!!
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 March 8 2017: As you can probably tell, this is very old. I have not worked on the device in several months and I have no idea if these methods are still safe. Please proceed with caution. I will be using one of these on a daily basis in the near future, so I probably will get back into development, and hope to release new content for the phone to help out the community. Please accept this as an official warning that the following is probably out of date and that you should be very careful should you decide to try it. The original post in it's entirety is spoilered below. You have been warned.
Update: A new update was released for the Prime model, V6.6, which replaces the preloader and completely breaks SPFT. If you unlocked your bootloader (so you can use fastboot) in any capacity before taking that update, there may be hope for you yet, but as of right now V6.6 is unsupported. Update: If you used this method to safely* take* the V6.6* update*, this will still work.
Update: I just checked the stats, and this has been downloaded more than 3 thousand times. I never thought my humble little conversion guide would help out so many people. I have also added a new mirror at [REDACTED], so anyone in North America who was having trouble with the Europe mirror, give that one a shot. It should be faster! I have updated all links in the guide to use the new North America mirror, and added a separate Europe mirror link after each link.
Hello! This is a tutorial for converting the Amazon Prime Edition BLU R1 HD to the OEM BLU version. This will overwrite the relevant partitions on your Amazon version of the device with the non-Amazon version. The physical model number on your device will still be a tell (obviously), but besides that, there will be no way to tell your device apart from the regular model! You can also use this method to convert non-Prime to Prime version, and undo OTAs or system modifications. This will restore a 100% out of the box image from either edition on your device.
This will work if you have software version...
V12
V6.1
V6.4
V6.5
SAFE V6.6 FROM THIS THREAD
This will NOT work on software version...
V6.6
The V6.6 update brought a new preloader that breaks our ability to use SPFT. I am currently working on ways to reverse the damage, but as of right now, there is no way to convert (or downgrade) from software V6.6
You can use this on any 16/2 R1 HD with supported software version to...
Convert to the non-Prime OEM version
Convert to the Prime version
Remove ads (via conversion to non-Prime version)
Unroot
Downgrade to V6.1
Downgrade to V12
Undo system alterations/tampers
Restore the system image to the way it was when you first opened the box
Unbrick a device (if bricked because of bad system/recovery/boot image)
There are a handful of reports about this working flawlessly on the 8/1 model as well. I have not personally tested this, so there is still some risk factor.
This only overwrites the system, recovery, and boot partitions. Any other partitions that have been altered will not be restored. In most cases, other partitions should not have been altered, so this is not a concern. I have a full system backup of all partitions, but there is currently evidence to suggest that it is not safe to flash all of the partitions, so I will not release that backup until more is known.
You *should* be able to safely pull this off without wiping your data. This does not require your phone to be rooted or have any other modifications. You can pull it straight out of the box and do this process! If your phone is rooted, you'll lose it. This will make your phone EXACTLY like the non-Prime version comes out of the box! You can also convert a non-Prime device (or a converted Prime device back) to a Prime device using the same method, but I'm not exactly sure why you would want to. I did this all on Linux, but the Windows should work fine too as long as you have drivers dealt with. If you don't have drivers dealt with, I'm not your guy. I'll just tell you to use a better operating system. You'll also need an archive program that can deal with tar.gz files, because that's how my computer zipped them.
And the standard disclaimer: If this bricks your phone or makes it become sentient and plot with other sentient phones to murder your entire family, it's not my fault. That's all on you, buddy.
Ok, without further ado, on to the tutorial!
First, you need these things. Some of the files are quire large, so it might take a while to download:
You'll need the latest version of Smart Phone Flash Tools, or SPFT for short. You can download that from this site, or from [REDACTED]. Please use the latest version for your OS.
You'll need to download the system image. If you're converting to the non-Prime version, [REDACTED]. If you're converting to the Prime version, [REDACTED]
You need the scatter file. This will tell SPFT where the partitions are. This is the same for both variants, so just download [REDACTED]
Once you have those things, you can start actually flashing your phone:
Power your phone completely OFF! This will not work if your phone is powered on. SPFT writes directly to the phone's memory, bypassing all security measures the phone has, so it requires the phone to be completely OFF to get safe and exclusive access to the memory. DO NOT PLUG IN YOUR PHONE YET!
Extract SPFT into a folder on your computer. If you can't figure out how to do that, please stop tinkering with your phone. It's only a matter of time until you break something.
Extract the system image into the same folder you put SPFT in. The three files (boot.img, recovery.img, system.img) should be in the same folder as all the other SPFT files, including the binaries.
Run SPFT. On Windows, simply double clicking the SPFT executable should do the trick. On Linux, you must run the flash_tool.sh script as root. Open a terminal emulator, cd to the SPFT folder, and run `sudo ./flash_tool.sh`. If you recieve an error about permissions, run `chmod +x flash_tool.sh` and try the first command again.
Go to the Download tab in SPFT and click the Scatter-loading button on the far right side. DO NOT click the Download Agent button. When the file picker dialog pops up, find and open the r1hd-spft-scatter.txt file you downloaded earlier.
You should see a list of partitions. Only three of them (boot, recovery, system) should be checked, and the location should point to the files you extracted from the tar.gz file earlier. If this is not the case, double-click the location block of the boot, recovery, and system partitions, and select the boot.img, recovery.img, and system.img files from your filesystem respectively. After selecting the files, the boxes should check themselves.
From the dropdown in the upper left of the partition list, make sure Download Only is selected. Any other option could damage your device.
Click the Download button in the upper left.
While your phone is OFF, plug it into your computer with a data safe USB cable. The cable that came in the box from the factory is ideal, but any good quality cable will work just fine.
SPFT should start overwriting your phone. If you receive an error from SPFT, unplug your phone, close SPFT, and repeat steps 4 through 9. The whole process takes about 10 minutes, after which you should see a window with a large green checkmark. Once you see that window, you can safely unplug your phone and start it up. You're all done!
And as a bonus, I've also included a guide for unlocking the bootloader, getting custom recovery, and rooting the device after you've done this in post #2. That makes this your one stop shop for getting a brand new Prime phone out of the box!!
HUGE THANKS TO @mrmazak FOR THEORIZING THIS METHOD AND GETTING ME THE NON-PRIME SYSTEM IMAGE TO USE!
As always, if you have any questions, just ask in a thread reply or send me a private message on XDA. And by the way, hit the Thanks button in the lower right corner of the post if my guide helps you. It motivates me to keep this up to date and write more helpful guides. If you feel like giving me even more motivation and help fund future development, [REDACTED].
{OUTDATED}[GUIDE][OEM][Stock] Bootloader Unlock, TWRP, and root!
Update March 8 2017: As you can probably tell, this is very old. I have not worked on the device in several months and I have no idea if these methods are still safe. Please proceed with caution. I will be using one of these on a daily basis in the near future, so I probably will get back into development, and hope to release new content for the phone to help out the community. Please accept this as an official warning that the following is probably out of date and that you should be very careful should you decide to try it. The original post in it's entirety is spoilered below. You have been warned.
Ok, now you've converted your brand new Prime phone to the non-Prime version. How do you unlock this sucker? The conversion process actually unlocks the standard unlock method from the factory, so it's VERY simple! No hoops to jump through or anything. You'll need adb and fastboot. You can get those as part of the official Android developer kit, your distro's repos (on Linux) or Homebrew (on Mac). Of course, this guide works for the normal non-converted non-Prime version as well. This WILL wipe your phone, so make sure you back up any important data before doing this.
This guide is for the OEM (non-Prime) version. If you have the Prime version, convert it to OEM using the guide above BEFORE doing this guide.
The standard disclaimer from above still applies.
This guide is broken up into two parts. Unlocking the bootloader, and rooting the phone. If you are preparing to install Magisk, do the bootloader unlock, skip the rooting part and move on to the Magisk guide. You do not need the files above if you are only unlocking the bootloader. If your bootloader is already unlocked, skip the bootloader unlocking part and skip to rooting the phone. If you are preparing to install Magisk and your bootloader is already unlocked, you shouldn't be here. Also please note that the bootloader can sometimes re-lock itself after completing a conversion/restore from the guide above, especially to/from the Prime version, so if you're not sure, play it safe and re-unlock your bootloader.
Part 1 - Unlocking the bootloader:
Boot up your phone. If you haven't already gone through the initial setup process, go through it. The bootloader unlock process will wipe your phone, so skip as many questions as possible so you don't waste your time.
Open the Settings app, go to About device, fine the Build number (it's toward the bottom), and tap on it 8-10 times (until it says you are now a developer. If it says there's no need and you're already a developer, you can skip to the next step)
Go back to the main Settings menu. You should see a new option where About device used to be, Developer options! Click on it.
Toward the top of the long list of developer options, there is an option called "OEM unlocking". If it's switched off, switch it on. If it's switched on, switch it off and back on again. You may get a warning saying that device protection features won't work. Click Enable and proceed. You may also be prompted to enter your password/PIN/pattern lock if you have one.
Scroll down a little bit to reveal USB debugging. Switch it on if it's not already.
Connect your phone to your computer using a data safe cable. Do not disconnect it until the very end.
On your computer, open a terminal emulator (or Command Prompt with ADB access) and run `adb reboot bootloader`. If you get a message complaining about keys or authorization, check your phone. There should be a window asking for permission for your computer to access the device. Allow it and run the command again.
Your phone will reboot into fastboot mode.
On your computer, run `fastboot oem unlock`. On the phone you will get a warning message talking about the implications of unlocking the bootloader. Press Volume Up to accept them. If everything goes smoothly, your bootloader should now be unlocked. You're not ready to flash quite yet! Flashing at this stage WILL brick your phone, so it's important that you continue following the guide carefully.
On your computer, run `fastboot reboot`. Your phone should reboot anywhere from 3 to 5 times. If it reboots more than that, your phone is bricked and you need to start again by following the guide above again.
Once Android starts up again, you should see the setup wizard. Your bootloader is now unlocked!
Part 2 - rooting the phone:
BEFORE YOU PROCEED: If you want your phone to be encrypted AND rooted, it's important that you unlock the bootloader using the steps above first, then use the encryption APK to encrypt your phone BEFORE installing TWRP and rooting your device. This device is an exception to the general rule of flashing TWRP first and then rooting afterwards. Repeat, if you want your phone encrypted and rooted, unlock the bootloader FIRST, then encrypt SECOND, then flash TWRP THIRD, and root your phone LAST.
This is the guide for rooting the actual phone. You must unlock the bootloader using the steps above before doing this part.
First, you'll need these things on your computer.
The TWRP image for the R1 HD. You can download [REDACTED]).
A copy of the latest SuperSU zip from Chainfire. You can get it from the official forum post, or Chainfire's website.
Linux Users: On Linux, you must add `sudo` to the beginning of all fastboot commands, because most Linux distributions will not give you enough access to the hardware without being root.
And finally, the guide:
Hold Volume Up and Power until the phone turns on with the boot menu. Once the boot menu appears, use the volume keys to scroll to [Fastboot Mode] and press the power button to select it. It's the middle option.
On your computer, cd to the folder where you downloaded twrp-3.0.2-1-r1hd-lopestom.img and do `fastboot flash recovery twrp-3.0.2-1-r1hd-lopestom.img`.
On your computer, do `fastboot boot twrp-3.0.2-1-r1hd-lopestom.img`.
Once TWRP boots up, dismiss the prompt about mounting the system, go to Reboot, then choose Recovery. Your device will reboot back into TWRP. I know this step seems odd, but just trust me.
Make a backup if you want. It's not a bad idea, but seeing how you just unlocked your bootloader so your data is gone and we have the images in case you somehow brick the system, I doubt you actually need it.
In TWRP, go to Advanced, then ADB Sideload. Slide the confirmation slider all the way to the right to confirm.
On your computer, cd to the folder where you downloaded SuperSU and run `adb sideload [SuperSU-zip-name.zip]`, replacing the last argument with the name of the SuperSU zip you downloaded, of course. If your computer says "waiting for device" for a long time, cancel with Ctrl+C, run `adb kill-server`, then run the first command again but with `sudo` in front this time.
Reboot the phone. If everything worked correctly, you should now have a rooted phone with SuperSU, bootloader unlocked, and custom recovery! Yay for cheap phones!
As always, if you have any questions, just ask in a thread reply or send me a private message on XDA. And by the way, hit the Thanks button in the lower right corner of the post if my guide helps you. It motivates me to keep this up to date and write more helpful guides. If you feel like giving me even more motivation and help fund future development, [REDACTED].
reserved 3
reserved 4
reserved 5
Can you verify the image you uploaded for the non-Prime version? I'm getting unexpected EOF errors when extracting in Windows using 7Zip and TarTool, and I'm also getting an "operation not permitted" error when extracting using the built in Archive Utility in OS X.
abs0lute said:
Can you verify the image you uploaded for the non-Prime version? I'm getting unexpected EOF errors when extracting in Windows using 7Zip and TarTool, and I'm also getting an "operation not permitted" error when extracting using the built in Archive Utility in OS X.
Click to expand...
Click to collapse
Yeah, that's because the image isn't fully uploaded. My internet is very slow, so it's taking a while to upload. Sorry about that. I was hoping it would be finished by the time I finished writing this, but alas, nope. I will have all files uploaded by tomorrow, along with .md5 files so you can verify the checksums, so come back then. Again, sorry. I guess I should have posted this _after_ I got those uploaded. Oh! And I have North America mirrors coming within the next couple months. It seems a little oxy-moronic to host files for a US only device on an EU server, but unfortunately, servers in the US are significantly more expensive.
ColtonDRG said:
Yeah, that's because the image isn't fully uploaded. My internet is very slow, so it's taking a while to upload. Sorry about that. I was hoping it would be finished by the time I finished writing this, but alas, nope. I will have all files uploaded by tomorrow, along with .md5 files so you can verify the checksums, so come back then. Again, sorry. I guess I should have posted this _after_ I got those uploaded. Oh! And I have North America mirrors coming within the next couple months. It seems a little oxy-moronic to host files for a US only device on an EU server, but unfortunately, servers in the US are significantly more expensive.
Click to expand...
Click to collapse
No problem - thanks for your work on this!
abs0lute said:
No problem - thanks for your work on this!
Click to expand...
Click to collapse
Just finished uploading the non-Prime version. I will start the other upload before sleeping and update the post removing the warning when I awaken, assuming everything has gone well. You're free to attempt a non-Prime conversion now. Just don't do it the other way around yet.
Sent from my LG G4 using XDA Labs
Can't wait to give this a shot. Well, at least after someone else reports success first...
followed post 1 convert to non prime steps on windows, did not do the bootloader unlock steps.
phone booted up ok, followed by android is upgrading x of 37.
phone working and no ad's on lock screen
the amazon apps are still there but appear to be disabled, causing errors at first boot.
disabled or uninstall the apps. - used cleanmaster
everything seems ok now
Hello, I have now finished uploading the files, so you can now safely flash away! Enjoy! @abs0lute
bupkis said:
Can't wait to give this a shot. Well, at least after someone else reports success first...
Click to expand...
Click to collapse
I report success. Of course I did everything in the guide here before posting it. I'm not irresponsible. It's completely safe. I just finished uploading the files, so please go ahead and give it a shot.
ColtonDRG said:
I report success. Of course I did everything in the guide here before posting it. I'm not irresponsible. It's completely safe. I just finished uploading the files, so please go ahead and give it a shot.
Click to expand...
Click to collapse
ok, away we go! :laugh:
When I try to download the scatter file it just opens the file in a new browser window.
>nevermind, figured it out...success!
...on to bootloader unlock, TWRP, root...
bupkis said:
...
When I try to download the scatter file it just opens the file in a new browser window.
...
Click to expand...
Click to collapse
Yeah, that's a problem with my server configuration. I'll fix it later. For now, you can save the file by opening it in a browser window and pressing Ctrl+S
I have completed the process successfully-TWRP, root, no ads but do still have all the Amazon apps so something is screwy but not the end of the world.
bupkis said:
I have completed the process successfully-TWRP, root, no ads but do still have all the Amazon apps so something is screwy but not the end of the world.
Click to expand...
Click to collapse
Nope, it's not screwy. The non-Amazon version does include a lot of the Amazon apps. You can uninstall some of them the normal way (they're pre-installed user apps), and others you can either disable or uninstall using your favourite system app remover.
Anyone else missing Encrypt section in Settings > Security after converting to non-prime?
When I try to load the scatter, SPFT says "Error: Initializing scatter file failed. Please check the name of scatter file which you load is legal." I downloaded it from both the primary link and your mirror, same error. Any ideas? Thanks.
EDIT: Looks like I downloaded the oldest version, not the newest version of SPFT. Whoops! I'll leave my mistake on here to help others who may assume the first link is the right one.
notfix said:
Anyone else missing Encrypt section in Settings > Security after converting to non-prime?
Click to expand...
Click to collapse
It is missing. How peculiar. I will attempt to implement a workaround in a little bit. Sorry about that.
Update: The Encryption activity exists on the phone, we just can't get to it from the settings menu. You can launch it by manually launching com.android.settings.Settings$CryptKeeperSettingsActivity using your preferred method for launching arbitrary activities. I will release an app that will launch this activity for you ASAP!
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.