Related
ok so i have a rooted n10 along with flashing a kernel on it.....the boot loader is unlocked......i have stock recovery...but i still cant update to 4.2.2 successfully....so what i want to do at this point is just go completely stock so can update successfuly....what do i do??? im ustu just flashing via odin for my galaxy s3
GabrielOspina said:
ok so i have a rooted n10 along with flashing a kernel on it.....the boot loader is unlocked......i have stock recovery...but i still cant update to 4.2.2 successfully....so what i want to do at this point is just go completely stock so can update successfuly....what do i do??? im ustu just flashing via odin for my galaxy s3
Click to expand...
Click to collapse
You can use a rootkit Like WUGFRESH or NEXUS 10 Rootkit in the Nexus 10 forums here to return to stock or do it manually with ADB, there are also guides for that here at XDA. If you have only flashed a kernel you can also go to the stock recovery and just revert to factory, same thing you did when you unlocked the bootloader.
brees75 said:
You can use a rootkit Like WUGFRESH or NEXUS 10 Rootkit in the Nexus 10 forums here to return to stock or do it manually with ADB, there are also guides for that here at XDA. If you have only flashed a kernel you can also go to the stock recovery and just revert to factory, same thing you did when you unlocked the bootloader.
Click to expand...
Click to collapse
yea so now its in no command for recovery and for boot also....im using wugfresh...at this point i dont know what to do.....its incredible how easy it is for galaxy s3 but for the nexus 10 its much different...
https://developers.google.com/android/nexus/images#mantaray
Is the best way to return to complete stock. You'll need to download Android SDK and add the platform-tools directory to PATH though (not too difficult, there's a few guides around), and then just run the flash-all.bat while your N10 is in bootloader.
Do not use toolkits unless you want to break your N10 without knowing what's wrong with it.
espionage724 said:
https://developers.google.com/android/nexus/images#mantaray
Is the best way to return to complete stock. You'll need to download Android SDK and add the platform-tools directory to PATH though (not too difficult, there's a few guides around), and then just run the flash-all.bat while your N10 is in bootloader.
Do not use toolkits unless you want to break your N10 without knowing what's wrong with it.
Click to expand...
Click to collapse
can you link me to some guides or tell me step by step....sorry to be a nuisance man
First you'd want to download: http://dl.google.com/android/installer_r21.1-windows.exe and install it
- You'll need Java SDK installed, preferably Java 7 Update 13
You'll then want to run the SDK Manager (a start menu shortcut should exist for it)
You want to make sure that these things are checked:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Specifically, the Tools folder (both Tools and Platform-tools), and the Google USB Driver
- One of the packages may already be installed
Install packages, and wait till it's done, then close out of it.
You'll then want to add the platform-tools folder to PATH. Something like:
Control Panel > System > Advanced system settings > Environment Variables... > System variables > Path > Edit
- Go to the very end of the text already there, add a ; and then paste the location of the Android SDK platform-tools folder
- My folder location is C:\Program Files\adt-bundle-windows-x86_64\sdk\platform-tools
- Your will either be in appdata somewhere, or Program Files (x86)
Press ok 3 times
Now put the N10 into Bootloader mode, and then plug it in
And then run the flash-all.bat file included in the mantaray factory image (you'll have to extract it)
These instructions are kinda quick, sorry if something doesn't work, but if you get stuck, just ask here
espionage724 said:
First you'd want to download: http://dl.google.com/android/installer_r21.1-windows.exe and install it
- You'll need Java SDK installed, preferably Java 7 Update 13
You'll then want to run the SDK Manager (a start menu shortcut should exist for it)
You want to make sure that these things are checked:
Specifically, the Tools folder (both Tools and Platform-tools), and the Google USB Driver
- One of the packages may already be installed
Install packages, and wait till it's done, then close out of it.
You'll then want to add the platform-tools folder to PATH. Something like:
Control Panel > System > Advanced system settings > Environment Variables... > System variables > Path > Edit
- Go to the very end of the text already there, add a ; and then paste the location of the Android SDK platform-tools folder
- My folder location is C:\Program Files\adt-bundle-windows-x86_64\sdk\platform-tools
- Your will either be in appdata somewhere, or Program Files (x86)
Press ok 3 times
Now put the N10 into Bootloader mode, and then plug it in
And then run the flash-all.bat file included in the mantaray factory image (you'll have to extract it)
These instructions are kinda quick, sorry if something doesn't work, but if you get stuck, just ask here
Click to expand...
Click to collapse
mantaray-jdq39-factory-d79f489e thats the factory image i got from google....for some reason it doesnt come with the flash-all.bat
GabrielOspina said:
mantaray-jdq39-factory-d79f489e thats the factory image i got from google....for some reason it doesnt come with the flash-all.bat
Click to expand...
Click to collapse
you'll have to go into the archive or extract it twice I think until you see the folder, then inside that folder should be the files:
espionage724 said:
you'll have to go into the archive or extract it twice I think until you see the folder, then inside that folder should be the files:
Click to expand...
Click to collapse
yea i extracted it and all i get is mantaray-jdq39-factory-d79f489e
GabrielOspina said:
yea i extracted it and all i get is mantaray-jdq39-factory-d79f489e
Click to expand...
Click to collapse
Hmm, what archive manager do you use? With 7-Zip, I'm able to go inside the image downloaded from Google, and then go into it again, and then I get the folder.
espionage724 said:
Hmm, what archive manager do you use? With 7-Zip, I'm able to go inside the image downloaded from Google, and then go into it again, and then I get the folder.
Click to expand...
Click to collapse
i had winrar...im using now 7 zip...and when i click on flash all bat it says waiting for device...im in bootloader and i have the drivers already
< waiting for device >
erasing 'boot'...
OKAY [ 0.037s]
finished. total time: 0.038s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.057s]
finished. total time: 0.058s
erasing 'recovery'...
OKAY [ 0.029s]
finished. total time: 0.030s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.048s]
finished. total time: 0.050s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.227s]
finished. total time: 0.230s
error: cannot load 'bootloader-manta-mantalj12.img': Unknown error
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
< waiting for device >
error: failed to load 'image-mantaray-jdq39.zip': No error
Press any key to exit...
look at this error...what am i doing wrong?
hmm, try running fastboot devices from a command prompt, it should return a device name.
how would yo do that???
espionage724 said:
hmm, try running fastboot devices from a command prompt, it should return a device name.
Click to expand...
Click to collapse
ok i actually got it to work.....so this basically returns everything to stock right.....is it still unlocked?
espionage724 said:
hmm, try running fastboot devices from a command prompt, it should return a device name.
Click to expand...
Click to collapse
i forgot to add i still cant seem to go into the stock recovery....when i do it gives me the open android with the red exclamation point.
GabrielOspina said:
i forgot to add i still cant seem to go into the stock recovery....when i do it gives me the open android with the red exclamation point.
Click to expand...
Click to collapse
Hold Power Button for half a second and press vol down. If it says "No command." then you may have a different issue then.
espionage724 said:
Hold Power Button for half a second and press vol down. If it says "No command." then you may have a different issue then.
Click to expand...
Click to collapse
when i do that it actually says downloading....do not turn off target..i cant go anywhere else now...
Edit: nvm i got it to recovery but it says no command ....
Thanks
espionage724 said:
Hold Power Button for half a second and press vol down. If it says "No command." then you may have a different issue then.
Click to expand...
Click to collapse
Thanks espionage. I have been working on getting my Nex10 back to stock for too long. This post worked like a charm (I created an account just to say thanks ). I haven't figured out how to give you a "thanks" yet but I will when I do
espionage724 said:
https://developers.google.com/android/nexus/images#mantaray
Is the best way to return to complete stock. You'll need to download Android SDK and add the platform-tools directory to PATH though (not too difficult, there's a few guides around), and then just run the flash-all.bat while your N10 is in bootloader.
Do not use toolkits unless you want to break your N10 without knowing what's wrong with it.
Click to expand...
Click to collapse
Hi! I am trying to do whatever is necessary to get my n10 able to install directly from ota updates. I unrooted by following instructions that said it would return the device to stock, but ota's still dont work. Someone on xda linked me to this post but I am a bit confused by your post. You have a link to factory images and then you say to download android sdk and add platform tools directory to PATH and then flashall.bat while n10 is in boot loader.
Does this mean that I should first download a factory image? Which one? (i am currently running 4.4.2, so should it be this one?)
Once the factory image is downloaded, if i follow the instructions above, by doing "flashall.bat" does this find the factory image and apply it? Does it need to be in a specific folder on my mac?
when i googled instructions for adding platform tools directory to PATH for mac yosemite, I found these instructions: http://codexpi.com/add-android-adb-p...os-x-yosemite/
Are these the correct instructions?
I really appreciate any guidance you can offer. I have looked all over for clear instructions but no luck so far.
This process is very similar to how its done on Windows but I thought I would go ahead and post it here for those who have never rooted or used terminal before. I know the first time I rooted an Android device I was very happy to have a Mac specific guide to follow . Many of you may think this is simplified too much but, like I said, I created this with first time rooters in mind. If a Mod would like to sticky it thats fine. Also, I've tried to be very careful and thorough with the instructions, but if anyone notices a problem please let me know.
As always, I am not responsible if something goes wrong and your device gets bricked. I will try to be as specific as possible and this process worked for me. Also, I don't claim to have the knowledge to fix any problems you may encounter along the way. There are a lot of very talented people here who have extensive knowledge of Android, but I am not one of them. I can unlock my bootloader and root my device but that's about it. So if you do encounter a problem I will try to help but there is no guarantee I can fix the issue (in fact the odds are that I can't fix the issue). Proceed with caution!
Important: Unlocking your bootloader will wipe your device! Please backup anything that is important (pics, vids, documents, etc)!
This guide only applies to the 2013 Nexus 7
A. Prep
1. Charge the Nexus 7 to at least 80% so it doesn't turn off during the process
2. Unlock developer options by navigating to -- settings > about tablet -- and then click the build number 7 times
3. Enable USB Debugging by navigating to -- settings > developer options -- and select the USB Debugging box
4. Download the Android SDK for Mac here and unzip it once it has downloaded. DO NOT use the link posted below for the sdk. It does not contain fastboot and you will not be able to complete the rooting process. Please use the full sdk from Google that I have linked here. EDIT: Google has changed the download for the SDK. Please see posts 73-75 on page 8 for instructions regarding how to get everything you will need for the SDK.
5. Download the latest TWRP for your device here and place it in the platform-tools folder of the SDK. Make sure the TWRP file you download is for the 2013 Nexus 7...not the 2012 version. To find the platform-tools folder -- open the adt-bundle-mac folder you downloaded and unzipped > sdk > platform-tools -- place the TWRP file here. Other files in the platform-tools folder should include adb, api, fastboot, notice.txt, and a few others.
B. Unlock the Bootloader - Warning--This will wipe your device! Backup anything important!
1. With your device powered on, plug it into your Mac
2. Open up terminal and navigate to the platform-tools folder which has the adb, fastboot, and TWRP files. An easy way to do this is to type "cd" (without the quotes) into terminal, add a single space, and then drag and drop the platform-tools folder onto terminal and then press enter.
3. Type this command into terminal: ./adb reboot bootloader
4. If you correctly navigated to the platform-tools folder, you should get an error message saying the device is unauthorized. Go to the Nexus 7 and there should be a dialogue box asking you to authorize the computer. Authorize the computer.
5. Re-type the command: ./adb reboot bootloader
6. Your device should now boot into fastboot mode. On your N7, the word "start" will be at the top in green and you can also see a lot of your device information on this screen
7. Type into terminal: ./fastboot oem unlock
8. Your Nexus 7 will now display a message about unlocking your device. Use the volume button to select the option to unlock the device and then press the power button to confirm the choice.
9. Your device will return to the fastboot mode screen and you can now see in the device information section near the bottom that the device is unlocked. While on this screen, press the power button to select the green "start", which will reboot your device. You must restart your device here or you will run into a softbrick issue during the root process!
10. Congrats! Your device is now unlocked. If you want to root proceed to the next section.
C. Rooting
1. Once your device has rebooted from the unlocking process, everything will have been wiped and reset. You will have to go back and unlock developer options again and you will also have to enable USB debugging again, which can be found part A. Prep of this guide.
2. Download the current version of SuperSU to your Nexus 7. It will go to the download folder on your N7. It can be found here. (Note: The version of SuperSU I have linked to is 1.93, but it gets updated from time to time. You might want to look around and see if a more current version is available. The thread for SuperSU can be found here.)
3. Turn your N7 off and then boot into fastboot mode by pressing the Volume Down button while also pressing the Power Button to turn the device on. If done correctly you should see the green "start" again at the top and the device information near the bottom.
4. Plug the N7 into the computer and make sure terminal is still directed to your platform-tools folder. For instructions on how to navigate to the platform-tools folder see part B. Unlock the bootloader.
5. Type the following into terminal: ./fastboot flash recovery nameofTWRPrecovery.img
5a. For the nameofTWRPrecovery.img part above, you must type the exact file name of whatever TWRP (or other) recovery you've decided to use. This is the same file that you downloaded and placed in the platform-tools folder in Part A. Step 5. above. For me the file name I had to type was openrecovery-twrp-2.6.0.0-flo.img and the total command looked like this: ./fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
6. In terminal you should see the process taking place and it will tell you when its finished and how long it took (less than a second).
7. Now, while still in fastboot mode, use the volume button to navigate to Recovery and press the power button.
8. The N7 will boot into TWRP which we just installed.
9. Using the touch screen, select install and then navigate to the download folder where you saved the SuperSU file
10. Select the SuperSU file using the touchscreen and then swipe to flash it. You will see the rooting process occur on the screen.
11. Congrats! You are now rooted. Select Reboot System and you are done!
Your instructions couldn't be any simpler. I am unlocked and rooted now. This is my first Android device. Thank you very much.
Glad it was helpful for you!
Is there any step involved to install drivers here which I saw mentioned while using Windows system?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Very nice guide! Well done
Sent from my Nexus 7 2013 using xda app-developers App
redhat_123 said:
Is there any step involved to install drivers here which I saw mentioned while using Windows system?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
No, you don't need any drivers for the Mac (which makes it simpler than the Windows process in my opinion). I've included links in the how-to for everything you will need .
geckocavemen said:
No, you don't need any drivers for the Mac (which makes it simpler than the Windows process in my opinion). I've included links in the how-to for everything you will need .
Click to expand...
Click to collapse
Thanks a lot. This is the first time I used MAC to unlock and root a device and it was very quick. Appreciate your effort in putting up the detailed steps.
I just saw this post so I figured I may as well chime in. I've been rooting devices and using adb for years, so the issues wasn't a lack of experience.
I was having an issues with my device being reported as 'Offline'. Despite downloading the SDK several times I was unable to get the latest version.
I posted a thread last week with the updated version of adb needed for OS X in case anyone runs into this same issues that I did: http://forum.xda-developers.com/showthread.php?t=2390999
wad3g said:
I just saw this post so I figured I may as well chime in. I've been rooting devices and using adb for years, so the issues wasn't a lack of experience.
I was having an issues with my device being reported as 'Offline'. Despite downloading the SDK several times I was unable to get the latest version.
I posted a thread last week with the updated version of adb needed for OS X in case anyone runs into this same issues that I did: http://forum.xda-developers.com/showthread.php?t=2390999
Click to expand...
Click to collapse
Hi wad3g, was the problem you ran into related to the link for the Mac sdk I posted in the guide? If it was with my link I'd like to fix it so others don't have the same issue. Thanks!
EDITED TO ADD: Please only use the link in the how-to for the full sdk from Google. wad3g's link only has adb but not fastboot. To complete the rooting process you will need fastboot also.
geckocavemen said:
Hi wad3g, was the problem you ran into related to the link for the Mac sdk I posted in the guide? If it was with my link I'd like to fix it so others don't have the same issue. Thanks!
Click to expand...
Click to collapse
Yes, it is from the same link as above on Google's developer site. They hadn't updated the SDK yet, so each time I downloaded ADB v1.0.29 - ADB for 4.2. I was finally able to find ADB & Fastboot v1.0.31 for Android 4.3. Also, just so you know, the .zip on my thread is not the full SDK. If you're not a developer you don't need the full SDK, so for most the rooter's here my zip will be all that is needed.
You may just want to mention checking what version of ADB you're running prior to start or if you're having any issues. If you're running an older version than 1.0.31 you need to update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hope this helps! Let me know if you have any other questions.
Thanks wad3g. But just to clarify, Google updated the Mac version of the sdk on the 29th of July so the link in the original how-to will work for any version of Android. It's the same thing I used to download the sdk and I'm running version 1.0.31. Also, as mentioned it does contain more than is strictly necessary for unlocking and rooting. However, the original link in the how-to will provide you with the most up-to-date version of the Mac sdk that Google has released, should they update it in the future.
Please Help!!!
Hi I followed all your instructions and right when i was ready and tried to flash the recovery, I get this list of options after waiting for device:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
I don't understand what I should pick or if I should pick any. Please help as soon as possible.
EDIT: The reason I got this list is because I dragged in the fastboot into the terminal because when I tried to enter ./fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img, it said this: -bash: fastboot: command not found
Don't worry you haven't broken anything. What you saw is basically just a message that says you entered an incorrect command and then it presents a list of acceptable commands. Just start the section C. Rooting over again and don't move the recovery file into the command window...just type the full name of the recovery file instead.
EDIT...I think I didn't understand your edit properly the first time. I think you got the bash message because terminal was no longer pointed at the platform-tools folder. To do the rooting process you must make sure terminal is still directed at platform-tools folder. It should still be if you didn't close terminal or do anything else in terminal after the unlocking process. However, if terminal is not directed to the platform-tools folder you can use the "cd" command found in part B. of the how-to to get terminal pointed to the right place again. Once you've done that you can just start Part C. again and all should be fine. When I rooted I just left terminal open after completing the unlocking process and it was still directed at platform-tools. If you closed terminal it wouldn't be pointed at the right location where fastboot is.
One other thing: Are you sure there is a fastboot file in your platform-tools folder? It should look just like the adb file except it will be named fastboot instead.
LAST EDIT PLEASE READ: I'm assuming you used wad3g's download because I just checked and it does not have a fastboot file in it and that is why you got the -bash message. Please use the link in the how-to to download the full sdk from google. Pull out the fastboot file from Google's sdk and put it wherever you put your adb file that you got from wad3g. At that point you will be able to continue with Part C. Rooting.
Hope that last edit of mine helped out. Just follow the how-to step by step (including my links) and you'll be ok.
Thanks So Much But One Last Question
geckocavemen said:
Don't worry you haven't broken anything. What you saw is basically just a message that says you entered an incorrect command and then it presents a list of acceptable commands. Just start the section C. Rooting over again and don't move the recovery file into the command window...just type the full name of the recovery file instead.
EDIT...I think I didn't understand your edit properly the first time. I think you got the bash message because terminal was no longer pointed at the platform-tools folder. To do the rooting process you must make sure terminal is still directed at platform-tools folder. It should still be if you didn't close terminal or do anything else in terminal after the unlocking process. However, if terminal is not directed to the platform-tools folder you can use the "cd" command found in part B. of the how-to to get terminal pointed to the right place again. Once you've done that you can just start Part C. again and all should be fine. When I rooted I just left terminal open after completing the unlocking process and it was still directed at platform-tools. If you closed terminal it wouldn't be pointed at the right location where fastboot is.
One other thing: Are you sure there is a fastboot file in your platform-tools folder? It should look just like the adb file except it will be named fastboot instead.
LAST EDIT PLEASE READ: I'm assuming you used wad3g's download because I just checked and it does not have a fastboot file in it and that is why you got the -bash message. Please use the link in the how-to to download the full sdk from google. Pull out the fastboot file from Google's sdk and put it wherever you put your adb file that you got from wad3g. At that point you will be able to continue with Part C. Rooting.
Click to expand...
Click to collapse
Again in a bit of a sticky pickle. I got it to work because my problem was that I didn't direct the terminal to the folder. Now I am booted into TWRP but I don't understand what you mean by the SuperSu file. I it just the whole folder titled UPDATE-SUPERSU-v1.51?
EDIT: OMG IT WORKED!!! Thanks so much I got it rooted and it works awesome now!!!
Best tutorial for mac ever
I found this so helpful and easy! My nexus 7 is rooted now!:good:
:good::good::good::good:
thanks a lot
Thanks for the guide.
Want to say thanks for your very detailed explanations.
If I may, I would like to suggest one more step after the final step. Make a Nandroid backup. That really helps a lot for people who screwed stuff up.
Yes, creating a nandroid backup is very important and can definitely save you when flashing Roms and stuff if something goes wrong. Creating a nandroid before rooting could get you back to stock with an unlocked botloader too. But I guess that isn't as important now that Google has released the factory images.
Sent from my Nexus 7 using xda app-developers app
VomerGuides [M8]: Bootldr Unlock, S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
Welcome to VomerGuides: [M8 Edition]
Introduction:
Following this guide will allow you to:
- Unlock Bootloader
- Install Custom Recovery
- Root your device
- Achieve S-OFF
- Change your CID to SuperCID (allowing you to bypass regional ROM restrictions)
- Upgrade to the latest firmware (without loosing any data on your SD card)
This guide is based on the UL model of the M8 - you may follow the same steps for other editions but will need to find your respective firmware elsewhere.
Donations:
I do not believe that I should be charging for information sharing. However, having the physical hardware helps me improve this content and support you better as I do require hardware to test/work on for all my content and it's not always possible for me to find someone to borrow devices from.
If you would like to support my work donate to me via:
Thank you
Disclaimer & Copyrights:
I test everything before I share these guides - thus I know they work as intended. However, please proceed at your own risk as I do not take any liability for your devices.
Please do not copy contents of this guide without explicit permission from me. I like to maintain a set standard and quality of the information I share.
Please refrain from posting mirrors as I like to track downloads - I primarily use AndroidFileHost and they mirror files on multiple servers automatically.
READING & FOLLOWING EACH STEP IS KEY TO SUCCESS.
Let's get started!
SECTION 0: SYSTEM PREP:
Let's setup ADB and fastboot
Windows:
- Automated: http://forum.xda-developers.com/showthread.php?t=2588979 (follow the steps in the software)
- Manual Method:
Download this file and extract the folder called "adb" to your C: drive. Your path should look like this:
Code:
C:\adb\
You will need to open a command prompt window using this method:
Code:
- Go to the C:\adb\ folder
- hold down SHIFT key and RIGHT-CLICK
- select "Open command window here".
Mac & Linux:
Install ADB & fastboot using: this file
1. Extract the downloaded zip to your desktop
2. Open Terminal and type in:
Code:
su
cd Desktop/Android/ (note: Android is the directory extracted from zip file)
3. Now type
Code:
./ADB-Install-Mac.sh
Note: By using the method above, your adb and fastboot files are stored at this location on your Mac: /usr/bin/
Let's setup HTC Drivers:
Install HTC Sync Manager to get the HTC One M8 drivers installed, which you will need for this process
SECTION 1: UNLOCK BOOTLOADER, CUSTOM RECOVERY & ROOT
BOOTLOADER UNLOCK:
Make sure you check off all of the following before moving on to the first step.
- Make sure your phone is at least 60% charged.
- Register for an account at HTCdev.
- Enable USB debugging in your phone's Developer options.
- Un-check "Fast boot" on your phone by going to Settings -> Battery Manager.
- Install ADB and Fastboot on your computer.
- Make sure to back up all of your app data using either ADB or HTC Sync, because you will be wiping your phone.
- Install the HTC One M8 drivers on your computer (if you have HTC Sync installed, then you already have them).
Enter Fastboot (bootloader) Mode
Place your device into fastboot mode by plugging in your HTC One to your computer,
then powering it down by holding both the Power and Volume Down buttons until you see the screen below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Locate Your Identifier Token
Once the screen above appears, open up a terminal (command prompt) on your computer. To get the right Unlock Code for your HTC One, you first need to get your device's specific Identifier Token, so type the following into your terminal window, followed by the Enter key.
Code:
fastboot oem get_identifier_token
Copy the Token
Now copy the code you get, but do not include the first (bootloader) portions.
HTCdev
Go to HTCdev and log in to your account.
- Select Unlock Bootloader and then Get Started.
- From the drop-down menu, select HTC One (M8), then click on Begin Unlock Bootloader.
- Agree to the terms and conditions and click Proceed to Unlock.
- On the next page, scroll all the way down and click on Proceed to Step 5.
- Paste the identifier token you copied earlier into its corresponding box near the bottom (called My Device Identifier Token) and click Submit.
- The Unlock Code will be emailed to you, so once you receive the email, download the attachment and place it on your Desktop.
- Initiate the Unlock Code - in the terminal/command prompt, type the following:
Code:
fastboot flash unlocktoken Desktop/Unlock_code.bin
Note: Change [I]Desktop/Unlock_code.bin[/I] to the location of your code.
- Your phone will now prompt you to unlock your bootloader, using the Volume Up button, select Yes and confirm your unlock with the Power button.
- Your phone will reboot and your bootloader will be unlocked!
- After the reboot, you will need to set up your device again as if it were new.
- After getting set up, make sure to re-enable USB debugging and plug it back into your computer.
CUSTOM RECOVERY
Get latest TWRP: http://techerrata.com/browse/twrp2/m8
With your phone plugged into your PC, type in:
Code:
adb reboot bootloader
Once in bootloader mode, type:
Code:
Mac/Linux: fastboot flash recovery /Users/vomer/Desktop/openrecovery-twrp-2.7.1.0-m8.img
Windows: fastboot flash recovery C:\adb\openrecovery-twrp-2.7.1.0-m8.img
Then:
Code:
fastboot reboot
You are now the the latest version of TWRP.
ROOT
- Download SuperSU to your device
- Reboot into recovery mode:
Code:
via fastboot: With your phone plugged in, type in: adb reboot recovery
or
manually: Switch off the device first and then press the Volume Down + Power buttons - once on the bootloader screen use the volume keys to scroll to "Recovery Mode" and press the power button to make the selection
- In recovery, tap on Install and then select the SuperSU zip file.
- When done, select the Reboot system option to boot the device into Android OS.
You can confirm this by using apps like Root checker on the Play Store
SECTION 2: S-OFF & SUPER CID
There are a few basics you need to get out of the way before you can start this process:
- Uninstall HTC Sync.
- Enable USB debugging on your phone
- Turn off all security settings from Settings -> Security.
- Disable Fast boot mode from Settings -> Power/Battery Manager.
Now for the good part!
- Download firewater (note: firewater no longer works. You may try sunshine - but the results are spotty)
- Save the downloaded file to your ADB folder (C:/adb/ or the Desktop if you are on Mac/Linux)
- Plug in your device to your computer.
- Hold Shift and right-click on any empty space in the adb folder and click on Open command prompt window here
- Enter the following in the command prompt window:
Code:
adb reboot
Code:
adb wait-for-device push firewater /data/local/tmp
Code:
adb shell
Code:
su
Code:
chmod 755 /data/local/tmp/firewater
Code:
/data/local/tmp/firewater
- Type in Yes when prompted and hit enter.
- When it is done and says you have S-Off, type the following:
Code:
exit
Code:
exit
Code:
adb reboot bootloader
- The phone should now be S-OFF
- Stay at this bootloader screen - let's get you SuperCID:
- Copy/Paste the command below or make sure there a eight 1's:
Code:
fastboot oem writecid 11111111
- Reboot phone into bootloader mode (by typing: adb reboot bootloader) and verify CID#. It should look similar to this:
SECTION 3: FIRMWARE UPGRADE
Latest firmware's can be found in the post below.
Download the firmware zip file you would like to flash & rename it to firmware.zip
Plug in phone to PC and type this in terminal/command prompt:
Code:
adb reboot bootloader
Start by checking current system details. Type:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000 [COLOR="red"]< This is your bootloader version[/COLOR]
(bootloader) version-baseband: 1.15.2133156.UA13G [COLOR="red"]< This is your radio version[/COLOR]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5 < This is your firmware version
(bootloader) cidnum: 11111111 [COLOR="Red"]< This is your CID[/COLOR]
Now type:
Code:
fastboot reboot-bootloader
After that, type:
Code:
fastboot oem rebootRUU
Note: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots.
Then, repeat the steps above again.
Next, type:
Code:
fastboot flash zip /Users/vomer/Desktop/firmware.zip
Windows users: your command will look something like this: fastboot flash zip C:\adb\firmware.zip
Next, repeat the step above a second time.
Last Step:
Code:
fastboot reboot
Then I went back to the bootloader mode (after the phone reboots successfully):
Code:
adb reboot bootloader
Checked if the update worked:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G [COLOR="red"]< Looks New![/COLOR]
(bootloader) version-main: 1.54.401.10 [COLOR="red"]< Looks New![/COLOR]
CONCLUSION:
Please note my comments on donations/help at the beginning of this guide - it help's me keep the quality up to par for all of us.
Please feel free to provide any feedback!
Thanks for using VomerGuides
reserved if needed
I am assisting vomer with the Custom Firmware creation and uploads as he does not have an M8 for testing purposes.
All my files have been tested on my device prior to uploading however please proceed at your own risk as I do not take any liability for your devices, also confirm md5's match prior to flashing, enjoy!
As with vomer if you would like to support my work please use the Donation Button in my Signature, thank you.
Firmware Downloads (Device & SD card will not be wiped using these files):
4.x.x Base Without Red Text
- 1.54.401.5 (Rename to firmware.zip after downloading)
- 1.54.401.10 (Rename to firmware.zip after downloading)
- 2.12.401.3 (Rename to firmware.zip after downloading)
- 2.22.401.4 (Rename to firmware.zip after downloading)
- 2.22.401.5 (Rename to firmware.zip after downloading)
- 3.28.1540.5 (Rename to firmware.zip after downloading)
- 3.28.401.6 (Rename to firmware.zip after downloading)
- 3.28.401.7 (Rename to firmware.zip after downloading)
- 3.28.401.9 (Rename to firmware.zip after downloading)
5.x.x Base Without Red Text
- 4.16.1540.8 (Rename to firmware.zip after downloading)
- 4.16.401.9 (Rename to firmware.zip after downloading)
- 4.16.401.10 (Rename to firmware.zip after downloading)
4.x.x Base With Red Text
- 1.54.401.5 (Rename to firmware.zip after downloading)
- 1.54.401.10 (Rename to firmware.zip after downloading)
- 2.12.401.3 (Rename to firmware.zip after downloading)
- 2.22.401.4 (Rename to firmware.zip after downloading)
- 2.22.401.5 (Rename to firmware.zip after downloading)
- 3.28.1540.5 (Rename to firmware.zip after downloading)
- 3.28.401.6 (Rename to firmware.zip after downloading)
- 3.28.401.9 (Rename to firmware.zip after downloading)
5.x.x Base With Red Text
- 4.16.1540.8 (Rename to firmware.zip after downloading)
- 4.16.401.9 (Rename to firmware.zip after downloading)
- 4.16.401.10 (Rename to firmware.zip after downloading)
Fantastic! Great guide just as with the M7. This is much appreciated and more importantly trustworthy. It's best to remove all the guesswork when messing with these partitions and your guide does exactly that!
HTC One M8 | ARHD
TorrentzRock said:
Fantastic! Great guide just as with the M7. This is much appreciated and more importantly trustworthy. It's best to remove all the guesswork when messing with these partitions and your guide does exactly that!
HTC One M8 | ARHD
Click to expand...
Click to collapse
Thanks for your kind words
Sent from my Nexus 7 using Tapatalk
I've already gone through to S-off on my own, but your guide will be what I share with people who ask how.
Nice work!
Sent from my HTC One_M8 using XDA Free mobile app
Have been waiting for this. Thanks, and great work, as usual.??
Sent from my SM-P600 using XDA Premium 4 mobile app
"Latest firmware's can be found in the post below.
Download the firmware zip file you would like to flash & rename it to firmware.zip..."
Where is the latest firmware? I have htc one m8 verizon (bl unlocked, rooted, s-off, supercid).
iweksler said:
"Latest firmware's can be found in the post below.
Download the firmware zip file you would like to flash & rename it to firmware.zip..."
Where is the latest firmware? I have htc one m8 verizon (bl unlocked, rooted, s-off, supercid).
Click to expand...
Click to collapse
It will be posted soon.
Sent from my Nexus 7 using Tapatalk
Fantastic guide!
One recommendation though, when you are running adb and fastboot on Mac or Linux, it should be ./adb and ./fastboot.
Cheers
Stewart
Great guide. I already went through unlock & S-off but I used your guide for M7 last year, I think a lot of M8 users will be glad to find this thread
Good guide. However for a second there, I thought that this was a new way to achieve S-OFF... Too bad.
StuMcBill said:
Fantastic guide!
One recommendation though, when you are running adb and fastboot on Mac or Linux, it should be ./adb and ./fastboot.
Cheers
Stewart
Click to expand...
Click to collapse
works both ways if you use my method of installation
vomer said:
works both ways if you use my method of installation
Click to expand...
Click to collapse
Ah ok, cool. Sorry about that!
StuMcBill said:
Fantastic guide!
One recommendation though, when you are running adb and fastboot on Mac or Linux, it should be ./adb and ./fastboot.
Cheers
Stewart
Click to expand...
Click to collapse
Only if you don't have it installed correctly.
My M8 is a Developer Edition ( 1.54.1540.9 ).
HBOOT - 3.16.0.0000
cid: BS_US001
I'm getting this error when i try to S-OFF
"whelp this sucks, firewater can not work on your device no amount of reflashing, retrying, or ruuing will fix.DO NOT COME TOIRC ASKING FOR UPDATES OR ETAS!!! if we were able tpo fix this issue, it will be announced bye bye... sorry it didnt work out."
vickysud said:
My M8 is a Developer Edition ( 1.54.1540.9 ).
HBOOT - 3.16.0.0000
cid: BS_US001
I'm getting this error when i try to S-OFF
"whelp this sucks, firewater can not work on your device no amount of reflashing, retrying, or ruuing will fix.DO NOT COME TOIRC ASKING FOR UPDATES OR ETAS!!! if we were able tpo fix this issue, it will be announced bye bye... sorry it didnt work out."
Click to expand...
Click to collapse
Use SunShine to gain S-Off on your device, see here for instructions and downloads.
Sent from my HTC One using Tapatalk Pro
Sorry if my question would sound quite awkward to many people, but I am VERY new to rooting and all these.
I got a Verizon HTC m8, and I do not live in the U.S., so since I have to be on the Verizon network to get updates for my phone, for me that's not a choice. Which brings me here, right here! To root my device to be able to update it. But I have a couple of questions, and I like them to be answered. And since I am too new with this, any forum I read, I kind of got confused with all of it. SO, i would just like to get simple answers please.
1: Will this process help me update my phone and using the stock HTC RUU? Without losing HTC sense and all of that?
2: Will I be able to uninstall the annoying apps from Verizon?
3: Will this anyhow affect my phone to perform worse?
I don't care about warranty though, I am not in the U.S anyway. And won't be going there for a long time I guess.
Thanks for caring!
Hey @vomer, nice to have you here in M8 threads. Perfect guide like it was already with m7. Can we expect also your list of customized fws? I always preferred using your fws on my m7!! I know you don't have M8... But maybe you will be able to extend this thread with fws checked by yourself! Thx again for the great guide!!!
Sent from my M8
Toxicology said:
Hey @vomer, nice to have you here in M8 threads. Perfect guide like it was already with m7. Can we expect also your list of customized fws? I always preferred using your fws on my m7!! I know you don't have M8... But maybe you will be able to extend this thread with fws checked by yourself! Thx again for the great guide!!!
Sent from my M8
Click to expand...
Click to collapse
Yup post 3 will have ones tested by me.
Sent from my Nexus 5
Huawei Honor 7
– Complete Guide For Beginners –
Optimized For (PLK-L01)
Updating | Rooting | Tweaking | Fixing
In this guide, you will learn the following:
Part I - How to install the latest full ROM for Huawei Honor (PLK-L01).
Part II - How to root Huawei Honor 7.
Part III - How to fix bootloops if things did not go as expected.
Part IV - The most used adb commands.
Part V - The most used fastboot commands.
Part VI - How to change the default boot animation.
Part VII - How to change the default splash screen.
Appendix A - Honor 7 Key Combinations Summary.
Appendix B - How to update Huawei Honor 7 from (B100) to (B180).
Appendix C - Available Custom ROM(s).
Appendix D - Extra Resources.
Appendix E - All Important Downloads.
Notes & Credits:
This guide is written for the absolute beginners who had hard times reading other tutorials on this forum that explains the same set of topics.
This guide is primary written for Microsoft Windows users. Many sections though can be applied to other operating systems.
There are other great guides on this forum that teaches the same stuff but not in a very detailed beginner-friendly way. Special credits go to @piskr for his guide on this topic.
Additional credits go to @DigiGoon and @sminki for their contribution on fixing and updating this guide.
Special credits go to @Ziolek67 and @Kostyan_nsk for their original posts on the splash screen topics.
Special thanks to the Labinator team for their support throughout this guide.
If you have something to add or improve on this guide, please reply to this post and we will be more than happy to update it.
Warning: No one is responsible for what happens to your device while attempting to follow the below guide. Create backups before every section and know the risks before starting out.
Part I - How To Install The Latest Full ROM For The Model (PLK-L01)
Step 1: Download the latest full ROM for Honor 7 from the below link:
http://www.modaco.com/forums/topic/375942-roms-honor-7-stock-rom-images/
Step 2: Extract the (.zip) file and copy the "UPDATE.app" file to your (dload) folder in your external SD card.
Step 3: Make sure the current recovery that is installed is the default stock one and not a custom recovery like TWRP. If you have TWRP installed, make sure to flash the stock recovery before you attempt the update process.
Step 4: Turn off your phone, then press both the Volume Up + Volume Down + Power Key. Then release the power key as soon as you see the initial splash screen.
Step 5: The Huawei eRecovery will start and will update your device from the "UPDATE.app" file that you had placed in your (dload) folder automatically.
Part II - How To Root Huawei Honor 7
Stage 1 – Unlock The Bootloader
Part 1.1 – Getting The Unlock Password
Step 1: Login by clicking here.
Step 2: Click on “Unlock Bootloader”.
Step 3: Accept the unlocking agreement.
Step 4: Fill up the unlock password form as follows:
Product: Smartphone.
Model: (e.g. PLK-L01)
Product Serial Number: Settings -> Status -> Serial Number - > (e.g. H8WDU15814000010)
Product IMEI/MEID (IMEI 1): Settings -> Status -> IMEI1 -> (e.g. 867898020305536)
Product ID: Open the dial up and type: *#*#1357946#*#* -> (e.g. 88429554)
Verification Code: Type the Captcha.
Step 5: Press submit and obtain the unlocking password in red (e.g. 1078018121593242).
Step 6: Store the code obtained in step 5 somewhere safe.
Part 1.2 – Preparations
Step 6: Download and install the latest version of the "15 Seconds ADB Installer”. You can find the download link at >
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Step 7: Download and install the latest version of “HiSuite – Android Smart Device Manager”.
You can find the download link at >
http://consumer.huawei.com/minisite/HiSuite_en/
Step 8: Enable the “Developer options” by going to:
Settings -> About Phone -> Build Number
Tap on the build number 10 times quickly. A message must appear alerting you that the developer mode has been enabled.
Go to the “Developer options” and enable “USB debugging”.
Part 1.3 – Booting into Fastboot Mode
Step 9: Power the phone off.
Step 10: Boot the phone into “fastboot mode” by pressing the below keys.
[Volume Down] + [Tap on Power Button]. You can release the power button as soon as you see the initial splash screen.
Note 1: You must enter the fastboot mode directly after pressing the above keys.
Note 2: In case (Step 10) did not work, then turn off your phone again then insert the USB cable and connect it with your computer. After that, press the same combination mentioned above for 10 seconds. Note 3: You can also boot into the fastboot mode using the following command >
Code:
adb reboot bootloader
Step 11: Connect your phone with your PC. Use a USB cable to connect your phone with your computer while your phone is in the fastboot mode.
Step 12: Open your “Command Prompt (cmd)” and type >
Code:
fastboot devices
Note: The second command must show that your device is in fastboot mode.
Part 1.4 – Perform The Unlock Command
Step 13: Perform the unlock command > fastboot oem unlock ***, where *** is the 16 characters unlock code.
Code:
fastboot oem unlock 1078018121593242
Note: You need of course to replace "1078018121593242" with your unique 16 characters unlock code.
Step 14: Wait for the phone to get unlocked. It will automatically restart if you have entered the correct code.
Step 15: Test if the phone is successfully unlocked by entering the following command >
Code:
fastboot oem get-bootinfo
Case 1: If you have got the message of “Bootloader Lock State: UNLOCKED”, then your phone has been successfully unlocked.
Case 2: If you have got the message of “Bootloader Lock State: LOCKED”, then your phone is still locked.
Note: if you want to re-lock the phone, please check this thread for more details on that. Thanks to @sminki for posting that up and highlighting this point.
Stage 2 – Install Custom Recovery
Step 16: Open your command prompt, and navigate to the right directory where your recovery image file is located. You can do that using this command:
Navigate to the right directory:
[“Directory Letter”]:
Examples: D:, C:, or E:
Navigate to the right folder:
cd [“Full Path Of Directory”]
Example: cd /Users/User1
Step 17: Test if your device is detected by typing the following command while you are in the bootloader mode:
Code:
fastboot devices
> If you got the right messages that your device is properly connected, then you can proceed to step 18.
Step 18: Type the following command to flash the recovery image (TWRP). The recovery image is in English and you can download it from this link. Make sure to download it and place it in the right directory before typing the below command line.
Code:
fastboot flash recovery recovery.img
After the completion of that, simply reboot your device using the following command >
Code:
fastboot reboot
Note: “recovery.img” is the name of the TWRP recovery image. You need to replace this name with the name of your recovery image (e.g. twrp-3.0.2-0-plank.img).
Stage 3 – Root The Device
Step 19: Download the latest SuperSU version from this link and place it on your hard disk then copy it to your phone. You can copy the file from your computer to your device using this command >
Code:
adb push SuperSU-vX.zip /sdcard/
Note 1: You must be in the right directory of the “SuperSU” file or else the above command will not work.
Note 2: You must replace "SuperSU-vX" with the right name of your SuperSU file (e.g. BETA-SuperSU-v2.71-20160331103524.zip)
Step 20: When the process of flashing the recovery is done, reboot your device into the recovery mode using the following command >
Code:
adb reboot recovery
Step 21: After finishing step 20 successfully, your phone would have been booted into the recovery mode. You will be able to see the TWRP home screen. From there, click on the “Install” option then navigate to your /sdcard/ directory where you have copied or pushed your "SuperSU-vX.zip" file.
Step 22: Find the "SuperSU-vX.zip" file and install it.
Step 23: Navigate back to the home page of TWRP then click on the “Reboot” button in order to boot into the system.
Step 24: Double check if your device has been rooted successfully by testing it using one of those root checker applications. There are many of them around the Google Play store.
Part III - Useful ADB Commands
Code:
adb devices
adb reboot
adb reboot bootloader
adb reboot recovery
adb push [source] [destination]
adb pull [source] [destination]
adb backup
adb shell
Part IV - Useful Fastboot Commands
Code:
fastboot devices
fastboot reboot
fastboot reboot-bootloader
fastboot boot recovery recovery.img
fastboot flash [Partition] [Image]
fastboot oem unlock [Unlock Code]
fastboot oem relock [Relock Code]
Note: Use your favorite search engine to search the above commands and learn more about them.
Part V - How To Fix Bootloops
Breaking out of bootloops depends on your device state and what kind of problem you are having. In this section, we are going to focus on the popular case where you can’t access neither the system nor the recovery partitions.
Step 1: Turn off the phone.
Step 2: Press the following buttons:
[Volume Down] + [Tap on Power Button]. You can release the power button as soon as you see the initial splash screen.
Step 3: Head to your computer and download and install the following tool:
http://forum.xda-developers.com/showthread.php?t=2433454
Step 4: Download the latest complete update file (B121) or (B330b) depending on which system you had installed before the bootloop problem. You can download it from:
http://www.modaco.com/forums/topic/375942-roms-honor-7-stock-rom-images-updates-121115-b140/
Then, extract it and get its UPDATE.app file.
Step 5: Use the Huawei Update Extractor to extract the (BOOT.img), (SYSTEM.img), (RECOVERY.img), (CACHE.img), (CUST.img), and (USERDATA.img) from the UPDATE.app file that you have extracted from Step 4.
Step 6: Open your command prompt, and navigate to the right directory where you have extracted the image files. Use the “cd” and “..” commands to do so.
Step 7: Type the following commands and execute them one by one >
Code:
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
Step 8: You can also erase the user data if you like by typing and executing the following >
Code:
fastboot flash userdata USERDATA.img
Step 9: Reboot your device using the following command >
Code:
fastboot reboot
Step 10: You must be able to boot successfully into the system.
Step 11: After booting successfully, apply again the steps mentioned in Part I.
Important Note 1: If the "fastboot flash" is reporting "FAILED <remote: command not allowed>", you need to unlock your device again even if the bootloader is stating that your device has already been unlocked.
Important Note 2: When breaking out of bootloops or frozen splash screens, you need always to flash the right partitions that match up with the previous partitions that you had installed on your system before the occurrence of the bootloop.
Part VI - How To Change The Boot Animation
Step 1: Root Your Device.
Step 2: Create a full Nandroid backup.
Step 3: Create your own animation or download one online. Note that you need the resolution to be (1080 x 1920 pixels). It should not last more than 10-12 seconds at most.
Step 5: Your animation files must be compressed and renamed as: “bootanimation.zip”.
Step 6: Change the permissions of your .zip file to (rw-r-r).
Step 7' - (In case you are running Android 5.x): Navigate to /Cust/Preinstalled/Public/Media and backup the original “bootanimation.zip” file somewhere safe on your hard drive or sdcard.
Step 7'' - (In case you are running Android 6.x): Navigate to /system/etc/media and backup the original “bootanimation.zip” file somewhere safe on your hard drive or sdcard.
Step 8' - (In case you are running Android 5.x): Copy your newly created bootanimation.zip file to the directory /Cust/Preinstalled/Public/Media and replace the original file.
Step 8'' - (In case you are running Android 6.x): Copy your newly created bootanimation.zip file to the directory /system/etc/media and replace the original file.
Step 9: Reboot and check up your new boot animation.
My original post of this section is available at: http://forum.xda-developers.com/showpost.php?p=63828825&postcount=2
Part VII - How To Change The Splash Screen
Requirements:
Your device must be rooted. Follow the steps in Part II in case you have not rooted your device yet.
You must have downloaded and installed the latest version of the "15 Seconds ADB Installer”.
You can find the download link at: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
You need to make a complete backup or a nandroid backup before starting up. You can create a nandroid backup using the custom recovery of TWRP.
Steps:
Turn on your device and connect it to your computer then open the command prompt or your terminal as an administrator.
Make sure your computer can read the data on your phone and all the drivers are installed properly.
Make sure the following command is returning the name of your device:
Code:
adb devices
Save your "oeminfo" to your SDCard:
Code:
adb shell su -c "dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo"
Download this zip file and extract it to your desktop or any location of your choice.
From your opened command prompt, navigate to the extracted zip folder that you have downloaded in Step 5. Use the "cd" command to do that.
Create your new splash screen logo as follows:
Step 1: Open your Adobe Photoshop and create a new file that has the following parameters
Width: 1080 pixels
Height: 1920 pixels
Resolution: 72 pixels/inch
Color Mode: RGB Color, 8-bit
Step 2: After creating your new image, save it as follows:
Extension: *.bmp
From the "Advanced Options", select R5 G6 B5 from the 16-bit depth options.
Save your newly created image in Step 7, in the same folder that you have extracted in Step 5.
From your command prompt, type the following command:
Code:
OEM_logo.exe oeminfo your_logo.bmp
Replace "your_logo.bmp" with the name of your logo.
The above command will create a new oeminfo for you that has your new logo. It will also replace the old one in the same folder.
Copy your newly created oeminfo to your sdcard by typing the following command:
Code:
adb push oeminfo /sdcard/oeminfo
Copy your oeminfo from your sdcard to the right partition on your device:
Code:
adb shell su -c "dd bs=32768 if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
Reboot your device and check the new splash screen.
Note: The original post of this section can be found at this link.
Credits: Special credits goes to @DigiGoon, @sminki, @Ziolek67, and @Kostyan_nsk for their amazing contribution in writing, testing, and adjusting on the original post of this section of the guide.
Appendix A - Honor 7 Key Combinations Summary
[Without Plugging The Device]:
Volume Down + Tap Power Button -> Normal Boot.
Volume Up + Tap Power Button -> Recovery Mode (e.g. TWRP).
Both Volume Buttons + Tap Power Button -> Flash (dload) Image From External MicroSD Card.
[While Connecting The Device To Your Computer]
Volume Down + Power On -> Fastboot Mode - (Tip: You can exit from this mode with a long power button press).
Volume Up + Power On -> Huawei eRecovery.
Both Volume Buttons + Power On -> Flash Image via HiSuite.
Appendix B - How To Update From B100 to B180
For The Model (PLK-L01)
Important Note: Please update your device before rooting it. You will lose your root access if you attempt to update after rooting your device.
Step 1: Download the latest stock ROM for Honor 7 from the below link:
http://www.modaco.com/forums/topic/375942-roms-honor-7-stock-rom-images/
Step 2: Download the B121 EMUI 3.1 update package.
Step 3: Download the B180 incremental update package (B121 to B180).
Step 4: Extract the B121 update zip file and get the UPDATE.app file from it.
Step 5: Copy the UPDATE.app file from your computer to the /sdcard/dload/ directory.
Step 6: Launch your device and go to: Settings -> Updater -> Menu -> Local Update and choose the UPDATE.app file.
Step 7: Install the update and wait until it reboots again. Check if the update is working successfully.
Step 8: Copy the B180 (B121 to B180) incremental update zip file from your computer to the /sdcard/dload/ directory.
Step 9: Make sure the name of your update zip file is “update.zip”.
Step 10: Apply the update by going to: Settings -> Updater -> Menu -> Local Update and choosing the update.zip file.
Step 11: Install the update and wait until it reboots again. Check if the update is working successfully.
Step 12: Delete the update.zip file from your /sdcard/dload/ directory.
Appendix C - Available Custom ROM(s)
r3 - Custom Rom Starter Template: http://forum.xda-developers.com/honor-7/development/r1-custom-rom-starter-template-honor-7-t3337901
r2 - MoDaCo Custom Kernel: http://forum.xda-developers.com/honor-7/development/kernel-r1-modaco-custom-kernel-t3365909
MoDaCo Custom Rom: http://forum.xda-developers.com/honor-7/development/r1-custom-rom-starter-template-honor-7-t3337901
YodaRom: http://forum.xda-developers.com/honor-7/development/rom-6-0-x-yodarom-v1-0-mm-rooted-ads-t3338179
DigiRom: http://forum.xda-developers.com/honor-7/development/rom-digirom-gpe-v1-t3365391
H7T Rom: http://forum.xda-developers.com/honor-7/development/rom-codename-h7t-t3396002
You can view all available custom ROM(s) at: http://forum.xda-developers.com/honor-7/development
Appendix D - Extra Resources
How to build your own kernel for Honor 7: http://forum.xda-developers.com/honor-7/general/guide-how-to-build-kernel-honor-7-t3363894
Honor 7 Multi-Tool: http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176
Spectrum Pure Theme: http://forum.xda-developers.com/honor-7/themes-apps/theme-spectrum-pure-base-theme-t3321234
Appendix E - All Important Downloads
All Stock ROMs and OTA Updates: http://www.modaco.com/forums/topic/...ck-rom-images-updated-1st-april-2016-plk-l01/
The Latest Version Of "TWRP": https://dl.twrp.me/plank/
The Latest Version Of "SuperSU": https://download.chainfire.eu/supersu
The Latest Version Of "15 Seconds ADB Installer": http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
The Latest Version Of "Huawei Update Extractor": http://forum.xda-developers.com/showthread.php?t=2433454
Access the "Huawei Bootloader Unlocker": https://hwid5.vmall.com/oauth2/portal/cloud_login.jsp
Awesome and very helpful guide @kenshiwara
Thank you for this guide.
If I understand, we can update if twrp is installed?
Envoyé de mon Nexus 5
No offence but this is just @piskr 's thread re-typed with some serious errors added to it.
Did you try "fastboot oem relock"? I started a thread on that, it doesn't work.
Did you try any of the "fastboot erase" commands? As when I tried it wouldn't - "Command not allowed"
The Huawei extract tool doesn't get the names of the images on the current full ROMS (tested on B121 and a few of the Chinese ROMS) it doesn't have the mappings for these. However it has worked with incremental patches..
Extracting the files and only flashing a few like system will leave you with and inconsistent device (if from different versions). Those 20+ files have a reason - modem, sensorhub, trustfirmware, teeos (whatever that is!), etc.. There are actually something like 40 block devices on the H7 (/dev/block/platform/hi_mci.0/by-name/). To run an official update on that system would almost certainly result in failure. (I have tried)
..and flashing a whole system doesn't fix a boot-loop. That's flashing the whole system, it goes away because whatever was causing it has been deleted/wiped. If that's the idea, better off flashing Huawei's recovery and doing a full UPDATE.APP of B100 / B121 and moving up.
Oh and just one more minor thing - holding the power button isn't required, turn the phone on and hold either down (with usb data connected) for boot-loader, or up for recovery
Sorry... I know you mean well, however posting things in good faith is dangerous. Especially in a guide aimed at beginners.
sminki said:
No offence but this is just @piskr 's thread re-typed with some serious errors added to it.
Did you try "fastboot oem relock"? I started a thread on that, it doesn't work.
Did you try any of the "fastboot erase" commands? As when I tried it wouldn't - "Command not allowed"
The Huawei extract tool doesn't get the names of the images on the current full ROMS (tested on B121 and a few of the Chinese ROMS) it doesn't have the mappings for these. However it has worked with incremental patches..
Extracting the files and only flashing a few like system will leave you with and inconsistent device (if from different versions). Those 20+ files have a reason - modem, sensorhub, trustfirmware, teeos (whatever that is!), etc.. There are actually something like 40 block devices on the H7 (/dev/block/platform/hi_mci.0/by-name/). To run an official update on that system would almost certainly result in failure. (I have tried)
..and flashing a whole system doesn't fix a boot-loop. That's flashing the whole system, it goes away because whatever was causing it has been deleted/wiped. If that's the idea, better off flashing Huawei's recovery and doing a full UPDATE.APP of B100 / B121 and moving up.
Oh and just one more minor thing - holding the power button isn't required, turn the phone on and hold either down (with usb data connected) for boot-loader, or up for recovery
Sorry... I know you mean well, however posting things in good faith is dangerous. Especially in a guide aimed at beginners.
Click to expand...
Click to collapse
Thank you for your comments and notes. It is great to see your contribution up there.
This was actually my personal guide that i wrote to help myself around while operating on this device (PLK-L01). Based on your comments, there are several sections that require fixing. Would you mind taking the time to re-write those sections in a step-by-step fashion in order to update the guide?
You disagree with the section of "How to fix the bootloop when you can't access neither the system nor the recovery partitions". My solution - which worked for me - was to erase and flash the main partitions. Still though, if you have a better method, please share it with the whole community in a step-by-step fashion. Everyone will be grateful.
We mainly need the following:
1. How to re-lock the phone if the command of "fastboot oem relock" is not working on some models?
2. How to break out of bootloops if we can't access the system or the recovery partitions? (and flashing the main partitions from fastboot is not a stable solution in your opinion).
If you can provide a detailed step-by-step guides addressing the above two points, i would surely be more than happy to update them in the guide. Please note that the above guide is mostly tested on PLK-L01. Please, always mention your model number when writing your notes.
Thanks again for sharing your results with the community and hope you can send us a better version on the above sections based on your findings.
Freebob94 said:
Thank you for this guide.
If I understand, we can update if twrp is installed?
Click to expand...
Click to collapse
TWRP is not required at all if you are just updating. You should root your device after applying all the updates rather than before.
Thank you for comment!
sminki said:
Did you try "fastboot oem relock"? I started a thread on that, it doesn't work.
Did you try any of the "fastboot erase" commands? As when I tried it wouldn't - "Command not allowed"
Click to expand...
Click to collapse
Well me and @kenshiwara both tried it after stucking in bootloop and those commands worked like a charm
kenshiwara said:
Thank you for your comments and notes. It is great to see your contribution up there.
Thanks again for sharing your results with the community.
Click to expand...
Click to collapse
I'm glad you too my reply as intended and not just an angry rant!
DigiGoon said:
Well me and @kenshiwara both tried it after stucking in bootloop and those commands worked like a charm
Click to expand...
Click to collapse
Guessing by your location, you have the Indian single sim version?
sminki said:
I'm glad you too my reply as intended and not just an angry rant!
Guessing by your location, you have the Indian single sim version?
Click to expand...
Click to collapse
No, I have European model PLK-L01, thanks to @kenshiwara
---------- Post added at 07:48 PM ---------- Previous post was at 07:46 PM ----------
sminki said:
I'm glad you too my reply as intended and not just an angry rant!
Click to expand...
Click to collapse
LOL, yeah, some people or developers would have taken it as angry rant but we all are here to learn and help each other.
OK, well I also have an EU PLK-L01 with unlocked bootloader. I re-tested the following today to confirm my initial findings:
fastboot oem get-bootinfo
Code:
...
[COLOR="Green"][B](bootloader) unlocked[/B][/COLOR]
OKAY [ 0.000s]
finished. total time: 0.000s
fastboot erase system
Code:
erasing 'system'...
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
finished. total time: 0.000s
fastboot erase userdata
Code:
erasing 'userdata'...
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
finished. total time: 0.000s
fastboot -w
Code:
Erase successful, but not automatically formatting.
[B]Can't determine partition type.[/B]
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
Erase successful, but not automatically formatting.
[B]Can't determine partition type.[/B]
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
erasing 'userdata'...
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
finished. total time: 0.000s
This was the same for any of the B1xx firmwares.
DigiGoon said:
Well me and @kenshiwara both tried it after stucking in bootloop and those commands worked like a charm
Click to expand...
Click to collapse
You locked the bootloader to fix boot-loop? That's a bad idea!
sminki said:
You locked the bootloader to fix boot-loop? That's a bad idea!
Click to expand...
Click to collapse
Never locked it, just flashed SYSTEM.img by executing
Code:
fastboot flash system SYSTEM.IMG
and it worked.
DigiGoon said:
Never locked it, just flashed SYSTEM.img by executing
Code:
fastboot flash system SYSTEM.IMG
and it worked.
Click to expand...
Click to collapse
Well, in post #7 you wrote this:
------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
------------------------------------------
However, your answer above says otherwise. Erase and flash are not the same thing
One of my main criticisms on the original post was that fastboot erase doesn't work, I went a long way to back this up in post #10
sminki said:
Well, in post #7 you wrote this:
------------------------------------------
------------------------------------------
However, your answer above says otherwise. Erase and flash are not the same thing
One of my main criticisms on the original post was that fastboot erase doesn't work, I went a long way to back this up in post #10
Click to expand...
Click to collapse
Sorry, that was my mistake but I never erased the partition, directly flashed it
DigiGoon said:
Sorry, that was my mistake but I never erased the partition, directly flashed it
Click to expand...
Click to collapse
Cool thanks. I can sleep easy now :highfive:
sminki said:
Cool thanks. I can sleep easy now :highfive:
Click to expand...
Click to collapse
I have updated the original thread highlighting your comments while fixing it according to our latest tests. Please read it up again and inform us if you have anything else to improve on it.
Out of 500 views, only you decided to take few minutes and help in improving this guide. Thank you for your time and know that your support will be appreciated by all the community of XDA-Developers.
Hi there beautiful people.
I'm getting some error updating after installing tw recovery.
Code:
Checking MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to start
E:Error executing updater binary in zip '/external_sd/dload/update.zip
E:Error installing zip file '/external_sd/dload/update.zip
Now backupping, i'm going to try to flash the zip (i'ts a stupid thing?).
Edit: Did not work either. Cannot update using twrp; the update app reboots directly in the custom recovery.
Currently on B121, it already had it. PLK-L01 europe.
Also, do you really think Haweii will public codes? I'm not so optimistic.
Smokehrbar88 said:
Hi there beautiful people.
I'm getting some error updating after installing tw recovery.
Code:
Checking MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to start
E:Error executing updater binary in zip '/external_sd/dload/update.zip
E:Error installing zip file '/external_sd/dload/update.zip
Now backupping, i'm going to try to flash the zip (i'ts a stupid thing?).
Currently on B121, it already had it. PLK-L01 europe.
Also, do you really think Haweii will public codes? I'm not so optimistic.
Click to expand...
Click to collapse
If that update.zip is from Huawei it won't work in TWRP.
You need Huawei recovery to install Huawei updates.
sminki said:
If that update.zip is from Huawei it won't work in TWRP.
You need Huawei recovery to install Huawei updates.
Click to expand...
Click to collapse
Indeed, it sounds pretty logic. So i should revert the stock recovery, update and then reinstall twrp.
Can I do it simply pushing trough adb? And where should I find the recovery.img?
Thanks for the help.
Smokehrbar88 said:
Indeed, it sounds pretty logic. So i should revert the stock recovery, update and then reinstall twrp.
Can I do it simply pushing trough adb? And where should I find the recovery.img?
Thanks for the help.
Click to expand...
Click to collapse
You have to extract them from the UPDATE.APP file!
I've done the work for you.. B121 recovery attached
Unizp, then
Code:
fastboot flash recovery B121_recovery.img
(like you did with twrp)
Then put TWRP back on.
I forgot to add - if the system partition is altered (su) then the official update may well fail..
sminki said:
I've done the work for you.. B121 recovery attached
Click to expand...
Click to collapse
I was downloading the full rom myself, but my internet speed is so slow. My savior, thank you. I hope to not bother you again with my low-tier noob problems.
EDIT: UPDATED March 6th, 2017 for March Google Security Updates Image
-------------------------------------------------------------------------
-------------------------------------------------------------------------
Stey-by-Step for Newbies Guide for restoring a bootloader-unlocked Pixel XL back to factory stock
This guide is ideal for soft-brick situations where you can't boot to your operating system
***Verizon users should research before doing ANYTHING.
***Europe users should be researching before using North American images, though it's usually okay to do so.
SOFT BRICK vs. HARD BRICK:
-What is a hard brick? Well, if you cannot access your bootloader then you're probably hard-bricked and need to do a warranty repair.
-A soft brick is when you CAN access your boot loader. Because if you can access your boot loader then you can repair your own software issue by following this guide.
If your phone is soft bricked and you send it in for warranty then you're a twat.
BOOTLOADER:
How do I access my bootloader? Power off your phone. Hold down the power button and volume down button at the same time, for 20-40 seconds. If you just now shut down the phone, then it takes longer for the bootloader to come up. If the phone has been powered down at least 30 seconds then the bootloader should come up quicker. If your phone is stubbornly upset then it may take several tries and also holding down the two buttons for 40-60 seconds. Another thing that may prevent you from accessing the bootloader is a low battery of course. Never do any software trickery without at least a half full battery for multiple random reasons.
The directions below are for Windows 7 and may need to be modified for other OS's.
***Anyone who doesn't want to lose their setup/apps/user data, just edit the flash-all.bat to remove the -w from the script. Then it won't wipe anything.
You can use this modified flash-all.bat. It's for the latest March "B" image:
http://www.filedropper.com/flash-all_1
1) Install the Google Android driver if your Pixel XL isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio/run/win-usb.html#download
2) Download the factory system image for Pixel XL (Marlin) to C:/Google
https://developers.google.com/android/images
---Here is the direct link for March "B - NOF27B" for All Other users (what we're using in this guide):
---https://dl.google.com/dl/android/aosp/marlin-nof27b-factory-2259c206.zip
---Here is the direct link for March "C - NOF27C" for Rogers users:
---https://dl.google.com/dl/android/aosp/marlin-nof27c-factory-b49c0e7b.zip
3) This is what the folder should look like after the download:
4) Now extract the file.
Your folder should look like this:
5) Go into the extracted folder:
6) The contents of the extracted folder should look like this:
7) Download Google's ADB/Fastboot files to this same folder:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
8) Now extract the ADB download to this same folder. Edit the path to look like it does below:
9) The folder should now look like this:
10) Go into that new folder and CUT all the contents:
11) Go up one folder and PASTE the files into the factory image folder:
12) The folder should now look like this:
13) Now boot your phone to Fastboot mode.
Power off the phone & disconnect from USB cable.
Wait 30 seconds.
Then press Power + Volume Down until you see this screen on your phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
14) Now connect your phone to your computer via USB-C cable.
15) Wait 30 seconds.
16) Then double-click the ever famous "flash-all.bat" to restore your phone to stock.
17) You'll see a black command prompt window pup up and start restoring your phone to stock image.
It'll take 5-15 minutes and when completed, the output should look just like this, except for the "A" vs. "B" designations may be swapped around, and that's fine.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32976 KB)...
OKAY [ 0.876s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.705s]
finished. total time: 5.583s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.457s]
writing 'radio_a'...
OKAY [ 0.562s]
finished. total time: 2.022s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.048s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1701181700
Baseband Version.....: 8996-012511-1701091826
Serial Number........: HT6920203793
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boot_a' (26173 KB)...
OKAY [ 0.690s]
writing 'boot_a'...
OKAY [ 0.299s]
erasing 'system_a'...
OKAY [ 0.265s]
sending sparse 'system_a' 1/4 (515613 KB)...
OKAY [ 13.636s]
writing 'system_a' 1/4...
OKAY [ 5.355s]
sending sparse 'system_a' 2/4 (514104 KB)...
OKAY [ 13.720s]
writing 'system_a' 2/4...
OKAY [ 6.234s]
sending sparse 'system_a' 3/4 (499613 KB)...
OKAY [ 13.263s]
writing 'system_a' 3/4...
OKAY [ 5.738s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 0.891s]
writing 'system_a' 4/4...
OKAY [ 0.359s]
erasing 'system_b'...
OKAY [ 0.297s]
sending sparse 'system_b' 1/4 (517080 KB)...
OKAY [ 13.672s]
writing 'system_b' 1/4...
OKAY [ 5.247s]
sending sparse 'system_b' 2/4 (514384 KB)...
OKAY [ 13.502s]
writing 'system_b' 2/4...
OKAY [ 10.252s]
sending sparse 'system_b' 3/4 (524287 KB)...
OKAY [ 13.766s]
writing 'system_b' 3/4...
OKAY [ 13.995s]
sending sparse 'system_b' 4/4 (85786 KB)...
OKAY [ 2.280s]
writing 'system_b' 4/4...
OKAY [ 2.969s]
erasing 'vendor_a'...
OKAY [ 0.250s]
sending 'vendor_a' (235322 KB)...
OKAY [ 6.049s]
writing 'vendor_a'...
OKAY [ 5.236s]
Setting current slot to 'a'...
OKAY [ 0.172s]
erasing 'userdata'...
OKAY [ 5.251s]
sending 'userdata' (138957 KB)...
OKAY [ 3.550s]
writing 'userdata'...
OKAY [ 1.298s]
rebooting...
finished. total time: 158.668s
Press any key to exit...
`
You're done.
There is no reason to continue reading this thread unless you want to "go the extra mile".
=================================
=================================
18) The phone automatically reboots at this point.
15) After it finished booting, I let it settle for five minutes.
16) I then reboot the phone (unnecessary step, just something I like to do).
17) I then log in and tell Google to restore my account from the cloud.
18) I set Display to stay on for 30 minutes so the phone doesn't go to sleep and my apps can restore without interruption.
19) After all apps are restored, I reboot and then update any remaining apps that need updates.
***OPTIONAL TIP*** Just prior to doing the flash-all.bat, it may not be a bad idea to make the additional step of flashing stock boot.img to both the A & B partitions.
Why not, right? This step is entirely optional and is only for good measure
Make sure you extracted the Google Image you downloaded, to the point where you find the boot.img and place it into the C:/Google folder.
The fastboot commands to install it are as follows:
Code:
fastboot flash boot_a boot.img
then...
Code:
fastboot flash boot_b boot.img
The output should look like this:
Code:
C:\Google>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (26229 KB)...
OKAY [ 0.718s]
writing 'boot_a'...
OKAY [ 0.296s]
finished. total time: 1.030s
C:\Google>fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (26229 KB)...
OKAY [ 0.718s]
writing 'boot_b'...
OKAY [ 0.265s]
finished. total time: 0.983s
C:\Google>
20) Boom, you're all done.
Either go find something else to do or continue reading this guide to root your phone, install TWRP and custom kernel.
=================================
=================================
*** MAY UPDATE USERS SEE THIS POST BEFORE GOING ANY FURTHER:
https://forum.xda-developers.com/showpost.php?p=72329767&postcount=176
TWRP, ROOT AND CUSTOM KERNEL INSTALL
****The next steps are only if you want to install TWRP, Root your phone and install ElementalX kernel.****
1) I enabled SystemUI Tuner (OPTIONAL).
2) I enabled Developer Options (OPTIONAL).
3) I enabled USB Debugging in Developer Options (OPTIONAL).
4) I enabled "Unknown Sources" in Security (OPTIONAL).
5) Download SuperSU root v2.79 SR3:
https://plus.google.com/+Chainfire/posts/27xToSqi5em
-----------Support thread for SuperSU
6a) Download TWRP RC1 IMG file:
https://dl.twrp.me/marlin/twrp-3.0.2-0-RC1-fastboot-marlin.img.html
6b) Download TWRP RC1 zip file:
https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.0.2-0-RC1.zip.html
-----------Support thread for TWRP
7) Download ElementalX-P-1.07 kernel:
http://elementalx.org/devices/pixel/
-----------Support thread for ElementalX
8) Copy the TWRP, kernel and Root zip files to your Pixel's /sdcard (filenames in pic are outdated, sorry):
9) Copy TWRP's RC1 IMG file to C:/Google
10) Right-click any white spot in C:/Google and select the option to "Open Command Window Here"
11) Copy and paste the command "fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img".
The output should look like this after you press enter.
Code:
C:\Google>fastboot boot twrp-3.0
.2-0-RC1-fastboot-marlin.img
downloading 'boot.img'...
OKAY [ 0.710s]
booting...
OKAY [ 0.858s]
finished. total time: 1.578s
C:\Google>
The Pixel will automatically reboot to TWRP RC1 recovery.
12) Put a checkmark on the box "Never show this screen during boot again" and then swipe to allow modifications.
Click "Install".
Scroll down and click on the file named "twrp-pixel-installer-marlin-3.0.2-0-RC1.zip"
Swipe to confirm flash.
13) Reboot to Recovery.
14) Click the "Install" button.
15) Install the root file "SR3-SuperSU-v2.79-SR3-20170114223742.zip".
16) Reboot phone and verify root works. Do NOT install kernel yet. You need Superuser running first to gain ElementalX's advanced install options.
17) Now reboot to TWRP RC1 Recovery to install Kernel.
18) Install the kernel file "ElementalX-P-1.07.zip".
Go through the prompts to select your kernel options you want.
I recommend choosing the defaults unless you're a kernel expert who knows what to expect.
Now reboot normally.
Wait five minutes after bootup for the kernel to "settle".
Enjoy your modded Pixel XL!
=================================
=================================
TWRP BACKUP AND RESTORE
This section is if you installed TWRP and want to do a full ROM backup.
It's not as "obvious" on how to do this vs. older phones with TWRP.
The initial method is the same.
1) Boot to TWRP
2) Select the "Backup" option
3) Back up the "Boot", "System", "Vendor" and "Data". The Vendor option is important and may be new to some of you (it was to me).
If you want a "bit-for-bit" backup, then also select "System Image" and "Vendor Image". This will make your backup file size much larger than usual.
To restore, just do as normal.
Locate your backup and restore all items listed above.
I love this guide, but when I rebooted, it turns out I took the OTA, unintentionally and lost root. Any idea how I can block the OTA?
dablitzkrieg said:
I love this guide, but when I rebooted, it turns out I took the OTA, unintentionally and lost root. Any idea how I can block the OTA?
Click to expand...
Click to collapse
in developer settings....make sure automatic updates is not turned on
v2.2v said:
in developer settings....make sure automatic updates is not turned on
Click to expand...
Click to collapse
I'll try that and report back. Thanks
---------- Post added at 12:56 PM ---------- Previous post was at 12:21 PM ----------
v2.2v said:
in developer settings....make sure automatic updates is not turned on
Click to expand...
Click to collapse
I had that turned off and it still automatically pushed the update to X. How do I root now?
dablitzkrieg said:
I'll try that and report back. Thanks
---------- Post added at 12:56 PM ---------- Previous post was at 12:21 PM ----------
I had that turned off and it still automatically pushed the update to X. How do I root now?
Click to expand...
Click to collapse
Same method as before
Flash SuperSU in bootloader mode
Sent from my sailfish using XDA Labs
sd_shadow said:
Same method as before
Flash SuperSU in bootloader mode
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I'm on Verizon X. I am now stuck at the bouncing balls screen when I tried this suggestion. Any help would be appreciated.
dablitzkrieg said:
I'm on Verizon X. I am now stuck at the bouncing balls screen when I tried this suggestion. Any help would be appreciated.
Click to expand...
Click to collapse
There is lots of discussion about this in the SuperSU thread.
I'm not VZW so I can't help much, sorry.
maybe very stupid question ( and also very stupid from me to not look for it) but i dont know whitch version i have to select P, L or H. And cant watch it anymore Is there a way to find it out ?
Never mind i got it
---------- Post added at 10:51 PM ---------- Previous post was at 10:02 PM ----------
thanx for the great guide !!!!
dablitzkrieg said:
I'm on Verizon X. I am now stuck at the bouncing balls screen when I tried this suggestion. Any help would be appreciated.
Click to expand...
Click to collapse
WHat GB model do you have? flash-all flashed userdata, which cannot be flashed on 128GB model, I am searching for a manual way like the nexus 6P, flash each partition manually, in this thread, http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478 it shows the output and I think to do it manually must flash everything but userdata and do not format userdata if you want to keep internal memory in tact. I have seen some other guides, but they have not worked for me, because it is fastboot system system.img and I think it is fastboot system_a and fastboot system_b, like I said follow the commands and output
yung40oz84 said:
WHat GB model do you have? flash-all flashed userdata, which cannot be flashed on 128GB model, I am searching for a manual way like the nexus 6P, flash each partition manually, in this thread, http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478 it shows the output and I think to do it manually must flash everything but userdata and do not format userdata if you want to keep internal memory in tact. I have seen some other guides, but they have not worked for me, because it is fastboot system system.img and I think it is fastboot system_a and fastboot system_b, like I said follow the commands and output
Click to expand...
Click to collapse
I am actually all set. Thx for the response though! It was simply an outdated adb/fastboot.
There is a possibility that Minimal ADB & Fastboot has some slightly older code buried in it so I recommend installing it, then updating the files using the link in step 2 just to be on the safe side.
Here's the link again. Thanks, Scott.
http://ul.to/6f5616c3
CZ Eddie said:
There is lots of discussion about this in the SuperSU thread.
I'm not VZW so I can't help much, sorry.
Click to expand...
Click to collapse
WHat GB model is yours? 128 or 32? I ask because previously on nexus 6P or older nexus devices you could not flash userdata on anything higher than 32GB model as it would only allocate 32GB on a 128Gb or 64GB model and mess internal size up. Also, this took you completely back to stock, like fresh out of the box setup, when I followed this manually it only was like an OTA, I still had my apps, data. etc.
yung40oz84 said:
WHat GB model is yours? 128 or 32? I ask because previously on nexus 6P or older nexus devices you could not flash userdata on anything higher than 32GB model as it would only allocate 32GB on a 128Gb or 64GB model and mess internal size up. Also, this took you completely back to stock, like fresh out of the box setup, when I followed this manually it only was like an OTA, I still had my apps, data. etc.
Click to expand...
Click to collapse
I'm 32GB.
But Google only offers one image and script for the 32 and 128.
CZ Eddie said:
I'm 32GB.
But Google only offers one image and script for the 32 and 128.
Click to expand...
Click to collapse
They only offer one image for the 6P and 5X as well regardless of memory size, but you still CANNOT flash userdata on a 64GB or 128GB 6P, it will leave you with only 32GB of space when booting up your phone, I know this for a fact, it is most likely the same for the Pixel and Pixel XL.
Note: You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have. If you wish to wipe your internal storage you'd use the following command instead:
Which I do not wipe internal memory anyway, but still cannot flash userdata for bigger storage models.
Can anyone other than yung40oz84 confirm that the flash-all.bat on a 128GB phone causes partition size issues?
CZ Eddie said:
Can anyone other than yung40oz84 confirm that the flash-all.bat on a 128GB phone causes partition size issues?
Click to expand...
Click to collapse
I used the flash all script on my 128gb version with no issues.
Thank God you fixed my Phone. I wanted to use the only rom out there and it killed my phone. Thank you for a clear instruction on how to restore my phone! Wish every one would be a little more clear.
Ok have a issue. When I run flash-all.bat I get waiting on device. Phone is already in bootloader mode. And device is recognized by adb.
moosc said:
Ok have a issue. When I run flash-all.bat I get waiting on device. Phone is already in bootloader mode. And device is recognized by adb.
Click to expand...
Click to collapse
It's clearly a lack of communication issue.
Wrong driver?
Are you sure you're in Bootloader and not in Recovery?
Recovery uses ADB and Bootloader uses fastboot.
Yeah I'm in bootloader. Also redid USB drivers. Tried using skip soft it rebooted into bootloader then hung up on waiting for any device
CZ Eddie said:
It's clearly a lack of communication issue.
Wrong driver?
Are you sure you're in Bootloader and not in Recovery?
Recovery uses ADB and Bootloader uses fastboot.
Click to expand...
Click to collapse