Related
Hey everyone, I'm brand new to this, and I was told before I start getting into ROMS that I need to run this software:
http://forum.xda-developers.com/showthread.php?t=1182871
So I followed each and every step, and my phone rebooted and it said "Unlocked" like it was supposed to. BUT, when it booted into the OS, it booted into the stock OS as if I had just bought it off the shelf. Additionally, I am seeing a little exclamation point and android character when I go to the Android Recovery option under fastboot (also installed via linked software)
What happened!?
Congratulations, you have just successfully unlocked the bootloader. Obviously you had higher hopes and were expecting bells and whistles, sorry to disappoint but that's it for this step. Next, flash a custom recovery via fastboot (I recommend the RomRacer's version of CWM), and then use that recovery to flash whatever ROM you choose. Instructions for all these steps are available in other threads. Good luck!
ravilov said:
Congratulations, you have just successfully unlocked the bootloader. Obviously you had higher hopes and were expecting bells and whistles, sorry to disappoint but that's it for this step. Next, flash a custom recovery via fastboot (I recommend the RomRacer's version of CWM), and then use that recovery to flash whatever ROM you choose. Instructions for all these steps are available in other threads. Good luck!
Click to expand...
Click to collapse
I thought when the phone rebooted after unlocking bootloader, it would boot back into the system I had before unlocking it? I flashed the "Tenfar recovery" that was in the automated script. However, when I flashboot into "Android Recovery," this is when I get to the exclamation point/ android character. Is this normal?
EDIT: I just reran the script to install recovery, and it seems to have worked the second time. I ran a backup and saved it on my external SD card, but is this backup of MY system, or of whatever its now booting into after being unlocked?
Ok guys, apparently I've somehow managed to screw this up. I swear I am following instructions completely!
I decided to try MIUI first, and so I made the backup, wiped all the data/cache/etc, and flashed the ROM. Upon reboot I discovered I couldnt get past the Dual Core screen. So, I rebooted into recovery and flash my backup, and have now found out that I cant get past the "Rethink Possible" screen.
Since at that point you haven't flashed anything else yet, the backup you made couldn't be anything else but your "normal" system.
No idea what (if anything) might've gone wrong, but here's something that you maybe didn't know - after flashing a new ROM, the following boot will always take MUCH longer than usual. After that the phone should boot at "normal" speed again. So have patience and give it time.
Also, not sure how come you're stuck at "rethink" screen. As far as I know that's the very end of the boot process, it is shown just before the launcher starts. Still, give it more time. If nothing happens after, say, 5 mins, try booting into recovery and wipe data and cache, then try booting normally again.
I think I may have found the problem. When I go to restore, it runs for a while, and then says "Error formatting /data"
What should I do?
Alright, im at a loss here. I've done everything I can think of. I've tried every restore setting possible, I've wiped everything MANY times, I've flashed a few diff ROMS to try to get ANYTHING to work.
I am utterly confused about why none of this is working. I've read so much info on the forums that my head is just swimming. I never thought this would be that hard.
At this point I'd just like to get ANYTHING working so that I have a usable phone tomorrow.
sounds like you're having lots of fun :laugh: try not to worry... we've all been there to varying degrees
If this was me I wouldn't go down the 'fastboot' method but just stick to accessing android recovery by the 'power off/on, hold volume down when powering on, and then selecting android recovery'
After this you should be into the phone's recovery mode with the menu in front of you? scroll down to 'wipe data/factory reset' and select (by pressing the power button) after this select 'wipe cache partition' and repeat the process.
Then go to 'install zip from sd card' and select this... if you have installed the ROM's correctly you should have a list at the bottom of the 'sd card' list? Select the rom you want and install by pressing power button ect.
Once this has been installed you then need to 'go back' to the main recovery page and then select 'reboot system'
Let us know if this helps... and good luck!
i would add wipe all (data & cache) again after installing!
I would try this:
Power down your phone, go to fastboot mode (Power + Vol-, then find Fastboot with Vol- and confirm with Vol+), connect to computer, then on the computer run these commands:
Code:
moto-fastboot erase -w
moto-fastboot reboot-bootloader
Then in the same menu as before, select Android recovery (and confirm with Vol+). When in recovery, try doing restore again.
If that doesn't work either, here's an alternative method to wipe /data from recovery using adb.
When in recovery, connect the phone to the computer and run this:
Code:
adb shell
That should place you in the phone's shell. Now in recovery go to Mounts and storage > Mount /data.
Then in the phone shell (on the computer) run this:
Code:
mount | grep /data
It should print something like:
Code:
[color=red]/dev/block/mmcblk0p[B]XX[/B][/color] on /data type ext3 (rw,nodev,noatime,nodiratime,errors=continue,data=ordered)
Note the first value printed. For me it's /dev/block/mmcblk0p16 but I'm not sure if that goes for all Atrixes out there, so better safe than sorry.
Now go back to recovery and select Mounts and storage > Unmount /data.
Now back to the computer - run this:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p[B]XX[/B]
Where XX is obviously what you got from the previous command.
When it's done (you get your prompt back), type exit and go back to recovery on the phone. Now you can try restoring your backup or flashing a ROM or whatever.
Solved
barry_ said:
sounds like you're having lots of fun :laugh: try not to worry... we've all been there to varying degrees
If this was me I wouldn't go down the 'fastboot' method but just stick to accessing android recovery by the 'power off/on, hold volume down when powering on, and then selecting android recovery'
After this you should be into the phone's recovery mode with the menu in front of you? scroll down to 'wipe data/factory reset' and select (by pressing the power button) after this select 'wipe cache partition' and repeat the process.
Then go to 'install zip from sd card' and select this... if you have installed the ROM's correctly you should have a list at the bottom of the 'sd card' list? Select the rom you want and install by pressing power button ect.
Once this has been installed you then need to 'go back' to the main recovery page and then select 'reboot system'
Let us know if this helps... and good luck!
Click to expand...
Click to collapse
This is EXACTLY the process I had been using. I just tried this again with MIUI, and again I got the screen that said MIUI was successfully installed from the sdcard. I rebooted, and now I've been stuck at the "Dual Core" unlocked screen.
gianluca.tomat said:
i would add wipe all (data & cache) again after installing!
Click to expand...
Click to collapse
No luck im afraid.
ravilov said:
I would try this:
Power down your phone, go to fastboot mode (Power + Vol-, then find Fastboot with Vol- and confirm with Vol+), connect to computer, then on the computer run these commands:
Code:
moto-fastboot erase -w
moto-fastboot reboot-bootloader
Then in the same menu as before, select Android recovery (and confirm with Vol+). When in recovery, try doing restore again.
Click to expand...
Click to collapse
How do I do this on the computer? What do I type it into?
wvcaudill2 said:
This is EXACTLY the process I had been using. I just tried this again with MIUI, and again I got the screen that said MIUI was successfully installed from the sdcard. I rebooted, and now I've been stuck at the "Dual Core" unlocked screen.
Click to expand...
Click to collapse
This is because the recovery you used is an outdated one.Install rom racer recovery, you can install it through fastboot http://forum.xda-developers.com/showthread.php?t=1204500
harishatrix said:
This is because the recovery you used is an outdated one.Install rom racer recovery, you can install it through fastboot http://forum.xda-developers.com/showthread.php?t=1204500
Click to expand...
Click to collapse
How do I enter these flashboot commands into the computer?
wvcaudill2 said:
How do I enter these flashboot commands into the computer?
Click to expand...
Click to collapse
As you don't know about fastboot I would suggest you to download automatic bootloader unlock from here http://forum.xda-developers.com/showthread.php?t=1182871, unzip it, you will find img file named " recovery-clockwork-4.0.1.4" replace it with romracer recovery you downloaded and rename the romracer recovery as " recovery-clockwork-4.0.1.4". Just to be safe even replace the "recovery-en-goapk-0630-1029" with rom racer recovery and rename it as "recovery-en-goapk-0630-1029". Open main and select option 6 and follow the on screen instructions.
harishatrix said:
As you don't know about fastboot I would suggest you to download automatic bootloader unlock from here http://forum.xda-developers.com/showthread.php?t=1182871, unzip it, you will find img file named " recovery-clockwork-4.0.1.4" replace it with romracer recovery you downloaded and rename the romracer recovery as " recovery-clockwork-4.0.1.4". Just to be safe even replace the "recovery-en-goapk-0630-1029" with rom racer recovery and rename it as "recovery-en-goapk-0630-1029". Open main and select option 6 and follow the on screen instructions.
Click to expand...
Click to collapse
Okay, so I did this and then went in and reflashed MIUI and it worked! Of course, now that I think about it, I should've created a new backup or something, but I guess its too late now.
On a side note, where can I find that google apps package?
wvcaudill2 said:
Okay, so I did this and then went in and reflashed MIUI and it worked! Of course, now that I think about it, I should've created a new backup or something, but I guess its too late now.
On a side note, where can I find that google apps package?
Click to expand...
Click to collapse
You will find the link for gapps from thread you downloaded the rom, I would suggest youto flash CWM touch recovery as it will make future flashing easy. Download it from here http://forum.xda-developers.com/showthread.php?t=1475444, and flash it the way you flashed the rom. Try out neutrino Rom if you are looking for fast and battery efficient rom
There are fruitcakes if you want to go back to stock rom.
harishatrix said:
You will find the link for gapps from thread you downloaded the rom, I would suggest youto flash CWM touch recovery as it will make future flashing easy. Download it from here http://forum.xda-developers.com/showthread.php?t=1475444, and flash it the way you flashed the rom. Try out neutrino Rom if you are looking for fast and battery efficient rom
There are fruitcakes if you want to go back to stock rom.
Click to expand...
Click to collapse
Could you link me to these "fruitcakes," and do I flash them like everything else?
wvcaudill2 said:
Could you link me to these "fruitcakes," and do I flash them like everything else?
Click to expand...
Click to collapse
Here you go http://forum.xda-developers.com/showthread.php?t=1163009 and yes you have to flash it like all other roms.
So I am currently on hboot 1.50 and today i attempted to install the new viper rom. It's based off of the new ics release.
I kpet getting bot loops with it so I wiped and then attempted to restore back to my cm9 devil toast.
Now i'm stuck in a boot loop. I was wondering if you guys knew how to get back into a rom.
I'm currenlty not at my home computer so I can't connect it to the computer and boot into recovery via the computer.
derik123derik123 said:
So I am currently on hboot 1.50 and today i attempted to install the new viper rom. It's based off of the new ics release.
I kpet getting bot loops with it so I wiped and then attempted to restore back to my cm9 devil toast.
Now i'm stuck in a boot loop. I was wondering if you guys knew how to get back into a rom.
I'm currenlty not at my home computer so I can't connect it to the computer and boot into recovery via the computer.
Click to expand...
Click to collapse
You are the fourth person today for whom I am writing the same solution but try it from someone else's computer if you want cause without it you will still be stuck..
Try the following steps,
1. go to recovery > wipe & factory reset, wipe cache, wipe dalvik, go to mounts and storage, wipe system, data, cache, sd card... everything u can find there... wipe all..
2. in recovery DO NOT REBOOT, turn off phone
3. go to android development of evo 3d gsm, find a rom, for example mikrunny 1.06, open the archive extract the boot.img from the kernel folder.
4. assuming u have android sdk installed on ur computer, make a new folder and from the android sdk tools copy adb.exe, fastboot.exe, adbwinapi.dll (exact same files u used to unlock bootloader). also in this folder put that boot.img you extracted from the rom
5. put that folder in C:\
6. get back to phone , still DO NOT BOOT UP YET, and power up phone in bootloader mode (vol down & power) and go to fastboot
7. connect phone to pc in fastboot usb mode
8. open command prompt, type cd c:\"folder" ("folder" = folder u created with the sdk tools)
9. type in cmd: fastboot flash boot boot.img
10. after it's completed, go to recovery, still do not boot up phone
11. in recovery go to mounts and storage, usb storage and now copy the whole rom and nothing but the rom on the sd card
12. install zip from sdcard, select rom and let it install, it should boot up automatically
steps were given by SeptimiuB, I am just replying to your query because I've gone through the same mess and recovered as well.
Just unlock your bootloader and install a recovery before trying the above steps.
Cheers.
vishaltejwani said:
You are the fourth person today for whom I am writing the same solution but try it from someone else's computer if you want cause without it you will still be stuck..
Try the following steps,
1. go to recovery > wipe & factory reset, wipe cache, wipe dalvik, go to mounts and storage, wipe system, data, cache, sd card... everything u can find there... wipe all..
2. in recovery DO NOT REBOOT, turn off phone
3. go to android development of evo 3d gsm, find a rom, for example mikrunny 1.06, open the archive extract the boot.img from the kernel folder.
4. assuming u have android sdk installed on ur computer, make a new folder and from the android sdk tools copy adb.exe, fastboot.exe, adbwinapi.dll (exact same files u used to unlock bootloader). also in this folder put that boot.img you extracted from the rom
5. put that folder in C:\
6. get back to phone , still DO NOT BOOT UP YET, and power up phone in bootloader mode (vol down & power) and go to fastboot
7. connect phone to pc in fastboot usb mode
8. open command prompt, type cd c:\"folder" ("folder" = folder u created with the sdk tools)
9. type in cmd: fastboot flash boot boot.img
10. after it's completed, go to recovery, still do not boot up phone
11. in recovery go to mounts and storage, usb storage and now copy the whole rom and nothing but the rom on the sd card
12. install zip from sdcard, select rom and let it install, it should boot up automatically
steps were given by SeptimiuB, I am just replying to your query because I've gone through the same mess and recovered as well.
Just unlock your bootloader and install a recovery before trying the above steps.
Cheers.
Click to expand...
Click to collapse
Man.. Even after that it still keeps kicking me into boot loops...Then whenever I go to recover via recovery, my nandroids freeze on bootscreen...
derik123derik123 said:
Man.. Even after that it still keeps kicking me into boot loops...Then whenever I go to recover via recovery, my nandroids freeze on bootscreen...
Click to expand...
Click to collapse
In that case, I recommend you go s-off. ICS tends to bootloop for many people who are s-on. Try the wire trick. http://forum.xda-developers.com/showthread.php?t=1585846
S-off > Locked with Tapatalk 2
coal686 said:
In that case, I recommend you go s-off. ICS tends to bootloop for many people who are s-on. Try the wire trick. http://forum.xda-developers.com/showthread.php?t=1585846
S-off > Locked with Tapatalk 2
Click to expand...
Click to collapse
Will definitely look into that. Thanks man
Before I get into the gist of my current problem I think it might be relevant to provide some backstory. I decided I wanted to try and root my phone so I could install a new custom ROM. I had done some jailbreaking back when the iPod touches came out, back when jailbreaking was extremely ghetto and unreliable, so I figured I could teach myself this fairly easily. I unlocked bootloader using the htcdev method without an issue, and, following a guide, downloaded something called Rootboot to flash the phone. There was only one step to this portion, so I assumed it would be easy. Running the rootboot started rooting my phone, however after a couple of lines in the command prompt it said something about the adb, failed, and the phone was stuck in a boot loop with no roms on it at all. I stayed up all night with the damn thing attempting to fix it, and at one point, actually got it to load up the stock ROM from the computer using some combination of RUU's and fastboot commands. I have no clue how I did it, all I know is that it was not through adb sideload because the recovery I had at the time wouldn't work with adb sideload for whatever reason. It was the recovery that came with the All-In-One toolkit, for the AT&T / TELUS version. At this point I figured since the phone was working I would just install the VenomROM, and after a few hours of playing around with fastboot and the bootloader trying to get a ROM loaded, I figured I was familiar enough with all of them to load the ROM.
Which is what brings me to my current issue. I KNOW the boot.img is flashed to the device because I used the All-In-One Toolkit to do it, erased the cache, did it again using fastboot commands in the command prompt, erased the cache, and continued to use recovery to install the ROM. I got it to load and install, cleared the darvik cache, data, and cache, but when booting, the phone would get to the lock screen, upon which sliding to unlock, presented me with a white screen that says "htc" on it instead of a launcher. After a couple of seconds of waiting, it says, "setup has quit responding" and gives me the option to close or to wait. Either option results in the phone rebooting wherein I only see a black screen with the notification bar at the top displaying my battery and no internet/network connection. I have gone back and flashed the boot.img again and cleared cache, darvik cache, and data several times and just have no clue what I'm doing wrong to not get this phone to boot with the ROM. I can reflash at any point from my sideload.zip file and the installation process has an option to flash the kernel (boot.img) because it is included in the zip. Any help would be much appreciated. I highly doubt theres anything wrong with the ROM or boot.img, it is probably me just not doing it right.
I am using (or attempting to use) the 1.2.7 version of VenomXL+ on the HTC One X+ along with TWRP 2.5 as the recovery.
Hi patarrfwifwi,
This should help you getting your phone back, make sure your SDK/ADB tool is perfectly installed (see in my signature if you need a guide) on your computer, this is the manual procedure to achieved a custom recovery, installing root and transferring a ROM via sideload to your phone to allow an installation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Your phone should reboot in Recovery
(!! The following instruction are with TWRP Recovery installed !!)
Select Advanced -> ADB Sideload -> swipe to activate
Download this file SuperSU and transfer this file again in platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
Type>adb sideload SuperSU.zip (Enter)
(Success)
Once done select Install menu of the Recovery
Locate sideload.zip and select it.
Swipe to confirm.
You are done rooting your phone.
Stay in Recovery and delete the sideload.zip file
Select Advanced -> ADB Sideload -> swipe to activate
Download this file ViperXL+ 1.2.7 JB and transfer this file again in platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
Double click on the ViperXL+-1.2.7.zip file and locate the boot.img and drag it to the platform-tools folder.
Type>adb sideload ViperXL+-1.2.7.zip (Enter)
(Success)
Once done select Wipe menu and wipe (factory reset and format system)
Select Install menu of the Recovery
Locate sideload.zip and select it.
Swipe to confirm.
Aroma installer will start leave everything by default and install the ROM.
Once done select Reboot-> Bootloader
Make sure FASTBOOT USB is highlighted
In bootloader via the command window type>fastboot flash boot boot.img (Enter)
(Success)
At the prompt type>fastboot erase cache (Enter)
(Success)
Finally at the prompt>fastboot reboot (Enter)
Rebooting
Give your phone ~5-10 minutes to complete the installation.
Tell me how that went please.
Thank you very much for the extensive reply. I am going to start on this right away. Quick update: I tried installing a different ROM named elegancia and got the same problem at the lock screen with it saying system process not responding. Might be irrelevant at this point, but I thought I'd throw up the update.
Starting this now, I'll get back to you when I'm done.
Unfortunately, this ended in the same problem. White screen with htc, system process stopped running. boot loop.
The only differences between this and what I was doing is that I never had that SuperSU step before and I was running everything from the data folder of the All-In-One toolkit instead of the sdk.
Try fixing permissions in recovery.
sixcarnage said:
Try fixing permissions in recovery.
Click to expand...
Click to collapse
Ok, did that. It just enters a black screen with the notification bar at top, then goes black. The keys respond to hitting the lock/power button, but the notification bar goes away permanently, then phone goes back and reboots again.
What boot.img are you flashing? Is it the one inside the .zip?
sixcarnage said:
What boot.img are you flashing? Is it the one inside the .zip?
Click to expand...
Click to collapse
Yes
Try the one in the forum under the downloads. I know it's the stock but give it a shot.
Where would I find that?
If that doesn't work try the Beast Mode Kernel.
Download: http://db.tt/aGV3WhR2
Extract the boot.img from .zip and then flash the .zip in recovery.
Does this work?
---------- Post added at 10:39 PM ---------- Previous post was at 10:37 PM ----------
patarrfwifwi said:
Where would I find that?
Click to expand...
Click to collapse
Don't get cocky that was an accidental thanks
Here is the stock boot.img from the Viper thread
Download: http://www.androidfilehost.com/?fid=9390248398092764372
I don't really need a custom ROM, if I could just get the phone back to stock that would be good too. Basically, I don't care what I do to get it to work again, I just want to be able to use my phone. I've been out a cell since Sunday night and if going back to stock is easy and simple I'll just do that. If custom ROMs are the easiest option at this point I'll stick with that too; whatever gets my phone working the fastest.
Any luck with the above?
I flashed the boot.img from the beastmode, adb sideloaded the zip, installed the zip, did a wipe (darvik cache and whatnot) and after the Viper startup screen, it brought me to a screen that said upgrading apps (260 of them) and my hopes were up so much, but then it just started with the black screen. went into recovery and wiped the cache and darvik cache again, restarted, same problem with the htc screen.
I flashed the stock boot onto it and restarted. No luck,
I'm going to bed for the night. I'll be back on around 3 PM EST tomorrow.
patarrfwifwi said:
I'm going to bed for the night. I'll be back on around 3 PM EST tomorrow.
Click to expand...
Click to collapse
I'd go back to stock for now.
What I would do is get the att latest ruu and adb it to the phone to install. This happened to me and all I got was a black screen with the noti bar on top and nothing else. And then i send the latest ruu zip through adb and installed it. And now I have a working phone
Seems like we can't downgrade right now..
Sent from my SoftBank AQUOS PHONE Xx 203SH using XDA Premium
can you give me a link to this? i found the latest ruu, but its an exe file instead of a zip
RUU is always under an *.exe type file. It must be flash in bootloader mode (fastboot) via your computer with your phone plugged in.
Can you tell which HBOOT version you have (you can check this in bootloader mode)?
Heisenberg's How-To Guide For Beginners
Nexus 6P
{
"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"
}
Intro
This thread will serve as a location for basic how-to guides for the Nexus 6P. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
If you're unsure about something please read the FAQ section in post #3 before creating a post to ask a question.
Prerequisites
Always update your phone to the latest build available before starting the unlocking/rooting process. This guide is always current/correct as per the requirements of the most recent build available.
You'll need a working adb/fastboot environment on your PC to get through some of these guides.
Google have finally decided to allow us to install adb & fastboot without needing to install the entire Android SDK. Hurrah! What does this mean for you? Much less mucking around. Grab the appropriate version for your OS:
Platform tools for Windows | Google USB driver for Windows
Platform tools for Linux
Platform tools for Mac
Main Page
Simply download and extract the archive (and follow the linked instructions for the Google USB Driver for Windows). Once you've extracted the download you should have a platform-tools folder, within that folder you should see fastboot and adb. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Please see older method for installing adb/fastboot here:
You must have Java installed and up to date in order to use the SDK Manager, please ensure that this is taken care of before installing the SDK.
Please do not install adb/fastboot via any means other than the Android SDK, using other tools (like Minimal adb & fastboot) can lead to an outdated setup and various problems with flashing. You've been warned, other tools will not be supported in this thread.
Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library, Google USB Driver
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Quick Tips
How to boot into the bootloader:
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
How to boot into recovery:
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
adb reboot recovery
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
Index
Post #1
1. How To Unlock Your Bootloader
2. How To Install A Custom Recovery On Your Device
3. How To Decrypt Your Data Partition
4. How To Make A Nandroid Backup With TWRP Recovery
5. How To Make An EFS Backup With TWRP Recovery
6. How To Root
Post #2
7. How To Install A ROM with TWRP Recovery
8. How To Install A Custom Kernel With TWRP Recovery
9. How To Update To A New Build Of The Stock ROM
10. How To Flash The Factory Images (Return To Stock)
11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
12. How To ADB Sideload an incremental OTA update package.
13. How To ADB Sideload a full OTA update package.
14. How To Update To Android 7.0 Nougat
FAQ can be found in post #3!
1. How To Unlock Your Bootloader
Go into Settings/About Phone, scroll down and click on “build number†continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock†checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Power off your phone then boot into the bootloader (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue the unlock command:
Code:
fastboot flashing unlock
This will erase all user data from the device!
You should now see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to confirm if you're sure you want to go ahead.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
Allow everything to go ahead and once finished you can disconnect your usb cable.
Note: After unlocking your bootloader, each time your phone boots up you'll be greeted with a warning that says "Your device software can't be checked for corruption. Please lock the bootloader". This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is unlocked it will stay there.
Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock.
2. How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader (section 1).
Download the latest TWRP Recovery.
Make sure you check the md5 of the file to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Boot into the bootloader. Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot flash recovery <filename>.img
(The recovery filename in the command will change depending on which recovery you're flashing)
Use the volume keys to scroll and power key to select the Reboot Bootloader option. Once the phone has booted back into the bootloader you can use the volume keys to scroll and the power key to boot into your newly flashed recovery. It's now safe to disconnect your usb cable.
When TWRP boots up you'll be asked whether you want to allow system modifications or to keep it read-only, choose to allow system modifications, there's no benefit to keeping it read-only.
On Nougat you need to flash SuperSU after booting into TWRP otherwise TWRP won't stick (see section 6).
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.
3. How To Decrypt Your Data Partition
This is no longer necessary as long as you use TWRP 2.8.7.1 or newer, unless you are using the Android N developer preview, in which case you must decrypt.
Prerequisites: unlocked bootloader (section 1).
TWRP recovery cannot decrypt your data partition at this stage. In order for TWRP to be able to read/write on your data partition (to root or create a nandroid backup) you will need to format it, a format will remove encryption.
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot format userdata
Please note: this will erase all user data from the device!
Once the process has completed you can either reboot normally:
Code:
fastboot reboot
Or you can reboot back to the bootloader in order to undertake another task:
Code:
fastboot reboot-bootloader
4. How To Make A Nandroid Backup With TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Warning: before you make a backup with TWRP you must remove all lockscreen security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin will result in an "incorrect pin" message), you'll be forced to perform a factory reset to boot into Android. To remove lockscreen security go to Settings>Security>Screen Lock and set it to swipe/none.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
Boot into TWRP and select the backup option from the TWRP home screen, check the system/data/boor boxes, and swipe to backup. The process will take a few minutes.
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Fingerprint) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue. Boot into TWRP and use the built in file manager to delete /data/sytem/locksettings.db. This should be enough to get you into your OS again. If it isn't you can also try deleting /data/system/locksettings.db-shm and /data/system/locksettings.db-wal. If this still doesn't fix your issue you can delete /data/system/gatekeeper.password.key and /data/system/gatekeeper.pattern.key.
5. How To Make An EFS Backup With TWRP Recovery
An EFS backup is very important to have, if your EFS partition becomes corrupt you will have no IMEI, and therefore will not be able to use the phone as a phone. Making an EFS backup is insurance against this catastrophic event. Without a backup, restoring your EFS can be extremely difficult or impossible. The backup you create can be easily restored using the restore tool in TWRP recovery.
Boot into TWRP and select the backup option from the TWRP home screen, make sure only the EFS box is selected, and swipe to backup. The process will take a few seconds. Keep a copy of the backup on your phone and also keep another copy somewhere safe.
6. How To Root
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Download the latest root version (Magisk, SuperSU) of your choosing to your phone:
Magisk Stable
Magisk Beta
SuperSU Stable
SuperSU Beta
Boot into TWRP recovery and enter the install menu.
Navigate to where you have the root zip stored on your internal storage and select it.
Swipe to install.
Once the zip has installed you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this. You do have root, ignore this every time it comes up.
FAQ can be found in post #3!
Donate To Me
FAQ can be found in post #3!
7. How To Install A ROM with TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device. You'll also need to find out what build your ROM is based on and download the vendor image for that build, you'll find the latest in my index here.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your internal storage and select it. You can hit the "add more zips" button now to queue up your gapps package to be flashed after the ROM zip.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
Hit the home button once everything has finished installing.
Install the appropriate vendor image.
Select the install option from the TWRP home screen.
Click the "install image" button in the bottom-right corner.
Navigate to where you have the vendor image stored on your internal storage and select it.
You'll now be asked which partition to flash the image to, select vendor.
Swipe to install.
Once you've installed all necessary zips/images you'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button and you'll boot into your new ROM.
8. How To Install A Custom Kernel With TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
9. How To Update To A New Build Of The Stock ROM
Prerequisites: unlocked bootloader (section 1).
This method does not wipe your data, so you will keep your apps and settings. You should have no problems, however, if you experience problems you may need to perform a factory reset and flash again. Make a backup first and transfer it to your PC.
Download the latest build via the appropriate factory images for your model (Nexus 6P/Angler) here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
Once all operations are complete you can reboot the device.
You'll have to flash SuperSU again now, plus add any mods that you previously had.
10. How To Flash The Factory Images (And Return To Stock)
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box. This will wipe everything from the phone. If you wish to flash the factory images without wiping your personal data from the internal storage please move on to the next section.
Go to Settings/Backup & Reset and perform a factory data reset. This will remove all of your user data from the device (apps, settings, photos, music, etc).
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
If you wish to you can also relock the bootloader with this command:
Code:
fastboot flashing lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all user data from the device.
Once all operations are complete you can reboot the device.
11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box, except it will not wipe any of your personal data (photos, music, etc) from the internak storage.
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into TWRP recovery and enter the wipe menu, select advanced wipe, check only the data box and swipe to wipe.
Go to the TWRP main menu and enter the reboot menu, select bootloader. The phone will now boot into the bootloader, once it has you can connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
12. How To ADB Sideload an incremental OTA update package.
Prerequisites: Completely stock setup (the only modification allowed on the phone is the unlocked bootloader).
Download the appropriate OTA zip from my index. OTA updates must be taken in order so you must select the right zip. For example, if you're currently on the MMB29Q build you must select the MMB29Q --> MHC19I zip. The filename will be quite long so to make things easier you can rename it to something easier. For the purposes of this guide let's say we'll rename it to "ota.zip". Place the file in your fastboot folder on your PC.
Boot into the bootloader, use the volume buttons to scroll the options and use the power button to select recovery mode.
Once the phone has booted into the stock recovery (you should see Andy Android with an exclamation mark) hold power and tap volume up to get into the recovery menu. Use the volume buttons to scroll and use the power button (you might need to hold it) to select "apply update from adb".
On your PC navigate to your fastboot folder, hold shift and right-click your mouse, select "open command prompt here". Issue the following command:
Code:
adb sideload ota.zip
Wait for the operation to complete (it'll tell you once it's finished) and once it's all done you can reboot your phone, the first boot might take a while.
13. How To ADB Sideload a full OTA update package.
Prerequisites: Completely stock setup (the only modification allowed on the phone is the unlocked bootloader).
Download the OTA zip that you want to upgrade to from my index. You don't need to be on any specific build prior to flashing a full OTA package. You can only move to a higher build though. The filename will be quite long so to make things easier you can rename it to something easier. For the purposes of this guide let's say we'll rename it to "fullota.zip". Place the file in your fastboot folder on your PC.
Boot into the bootloader, use the volume buttons to scroll the options and use the power button to select recovery mode.
Once the phone has booted into the stock recovery (you should see Andy Android with an exclamation mark) hold power and tap volume up to get into the recovery menu. Use the volume buttons to scroll and use the power button (you might need to hold it) to select "apply update from adb".
On your PC navigate to your fastboot folder, hold shift and right-click your mouse, select "open command prompt here". Issue the following command:
Code:
adb sideload fullota.zip
Wait for the operation to complete (it'll tell you once it's finished) and once it's all done you can reboot your phone, the first boot might take a while.
14. How To Update To Android 7.0 Nougat
Prerequisites: unlocked bootloader (section 1).
This method does not wipe your data, so you will keep your apps and settings. You should have no problems, however, if you experience problems you may need to perform a factory reset and flash again. Make a backup first and transfer it to your PC.
Download the Nougat factory images for your model (Nexus 6P/Angler) here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
You can skip flashing the recovery if you wish, but even if you do the stock recovery may be patched on the first boot anyway. So you'll need to flash TWRP and SuperSU again if you need/want those, as well as any other system modifications you may have had.
Note: Do not flash the userdata.img
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
You'll have to flash SuperSU again now, plus add any mods that you previously had.
FAQ can be found in post #3!
Donate To Me
Frequently Asked Questions
1. How do I boot into the bootloader?
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
[/INDENT]
[INDENT]adb reboot bootloader[/INDENT]
[INDENT]
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
2. How do I boot into recovery?
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
[/INDENT]
[INDENT]adb reboot recovery[/INDENT]
[INDENT]
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
3. When issuing the fastboot flashing unlock command it doesn't work, I only get a list of possible commands. What's going on?
This is usually due to having an outdated adb/fastboot setup. If you installed adb/fastboot by any means other than via the Android SDK this is probably the cause. Visit the prerequisites section in the beginning of this guide to properly install adb/fastboot and ensure that it's up to date.
4. After unlocking the bootloader I get a message that says "Your device software can't be checked for corruption. Please lock the bootloader". What's going on? Can I get rid of it?
This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is locked it will stay there.
5. How do I take an OTA or update if I have root or other system modifications on the stock ROM?
You can't take an OTA update while you have root or any system modifications. You'd need to use fastboot to flash the system, boot, and recovery images. It's much easier to just flash the newer build with fastboot, see section 9 of this guide for full instructions.
6. Does taking an OTA update wipe my user data?
No, it doesn't.
7. Do I need to make an EFS backup?
Yes. Absolutely yes. An EFS backup is extremely important, if your EFS partition becomes corrupt your IMEI will disappear and you will not be able to use the phone as a phone. Without a backup it can be extremely difficult (or impossible) to restore your EFS.
8. Do I need to flash the userdata.img from the factory images?
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:
Code:
[/INDENT]
[INDENT]fastboot format userdata[/INDENT]
[INDENT]
Reserved
Reserved
Reserved
Reserved
thanks
works great
The_android_Modder said:
works great
Click to expand...
Click to collapse
Lol, how?
Heisenberg said:
Lol, how?
Click to expand...
Click to collapse
Magic
tyvar1 said:
Magic
Click to expand...
Click to collapse
xxtruplayaxx16 said:
lmao
Click to expand...
Click to collapse
He must be from the future...
The_android_Modder said:
works great
Click to expand...
Click to collapse
thank you for the morning lolz
If we wanted, could we just go to step 4, and not do the rest? I.e just root stock and leave it as is?
Is that safe?
If it is, can I flash a rom on later?
Thanks
(I know the device isn't out yet, just getting prepared for it.)
tf2manu994 said:
If we wanted, could we just go to step 4, and not do the rest? I.e just root stock and leave it as is?
Is that safe?
If it is, can I flash a rom on later?
Thanks
(I know the device isn't out yet, just getting prepared for it.)
Click to expand...
Click to collapse
No, because you need a custom recovery in order to flash SuperSU, and you need an unlocked bootloader to flash a custom recovery. Why not just unlock the bootloader?
Heisenberg said:
No, because you need a custom recovery in order to flash SuperSU, and you need an unlocked bootloader to flash a custom recovery. Why not just unlock the bootloader?
Click to expand...
Click to collapse
Ah you misunderstood me, I mean like do all steps upto 4, and then not do the rest?
Sorry for misunderstanding
tf2manu994 said:
Ah you misunderstood me, I mean like do all steps upto 4, and then not do the rest?
Sorry for misunderstanding
Click to expand...
Click to collapse
Ahh ok, now I understand. Yes of course, they're not actually steps that all need to be completed, they're just numbered sections. So if all you want to achieve is to root your stock ROM then you only need to follow steps 1-4.
Hemm sorry but are we talking about a phone that doesn't exist?
Fentadroid said:
Hemm sorry but are we talking about a phone that doesn't exist?
Click to expand...
Click to collapse
It certainly does exist, it just hasn't been released yet. And as it says in the OP these processes remain virtually unchanged from model to model in the Nexus line.
Heisenberg said:
It certainly does exist, it just hasn't been released yet. And as it says in the OP these processes remain virtually unchanged from model to model in the Nexus line.
Click to expand...
Click to collapse
I hope that too!!!
Great Job
Thanks for your Hardwork:good:
Hello,
I noticed that many people want to get recovery working on Marshmallow-Beta. Most people don't want to loose there data, settings ....
So I thought about writing a little Tutorial.
We need:
boot.img with included Recovery
TWRP for unlocked Bootloader
FTF of the .264-firmware (you can download it via XperiaFirm (keep in mind selecting your Phone (e.g. D6503))
[URL="http://www.flashtool.net/downloads.php"]flashtool and it's latest update
A few GB space on your SD-Card
MM-Beta-Zip
Installed Drivers
Time [/URL]
The first thing we need to do is to backup our Data, but How to do this without Recovery, TitaniumBackup isn't a good solution.
So .. one way would be to flash a boot.img, so we can boot a recovery, which is included into that file
Step1: Shutdown your Phone (you should have at least 50% battery for a safe flash)
Step2: Connect your Phone to your Computer, while pressing the Volume UP Button (if you have a blue light you're now in fastboot-mode)
Step3: flash the boot.img (fastboot flash boot stock-17.1.1.A.0.402-sirius-repack.img via cmd) NOW YOUR PHONE CAN NOT BOOT TO MARSHMALLOW ANYMOREStep4: Connect Phone to PC and backup your Data From internalSD
Enter recovery and make a backup
Step1: reboot your phone (fastboot reboot), then press the vol down Button repeatedly, until you enter the recovery.
Step2: make a backup and select everything, but boot IMPORTANT !
Flashing new bootloader
Step1: shutdown your phone completely
Step2: start flashtool and select the thunder symbole + flashmode
Step3: select your downloaded FTF and select wipe Userdata+Apps-Logs
Step4: plug in your phone with vol+ pressed, so that you're in flashmode
Step5: flash firmware
Flashing TWRP
Step1: Shutdown your Phone
Step2: Boot into Fastboot
Step3 Flash TWRP for unlocked bootloader : fastboot flash recovery recovery.imgRestoring MM
Step1: Shutdown your phone
Step2: Boot into Recovery (hold Power and VolDown, release Power when phone vibrates)
Step3: flash MM-Zip
Step4: restore your Backup
Step5: restore Internal-SD-Backup-files to InternalSD---
Done
OK, thanks
So you mean we're going to use TWPR's backup function. But does TWRP Backup restore internal sd's general files(photos, songs....etc)?
Flashing ftf with wipe userdata option will wipe EVERYTHING on my internal-sd, including photos and songs. So It's no use if twrp cannot restore them
Or do you write this guide only for people who only want to keep their appdata and settings(/data/data, /data/app)?
Also, you mentioned about NEW Bootloader of .264 firmware. Many ppl told me that I should update to new BL to install recovery in MM.
Does the NEW BL has seperated partitions for each recovery and boot(kernel)?
hw0603 said:
So you mean we're going to use TWPR's backup function. But does TWRP Backup restore internal sd's general files(photos, songs....etc)?
Flashing ftf with wipe userdata option will wipe EVERYTHING on my internal-sd, including photos and songs. So It's no use if twrp cannot restore them
Or do you write this guide only for people who only want to keep their appdata and settings(/data/data, /data/app)?
Click to expand...
Click to collapse
You're right .. I didn't noticed that internalSD is wiped, too. But you can back up it via PC in Recovery or in Android
@backupfunction ... No Recovery has the option to backup InternalSD (because the developers think its useless)
hw0603 said:
Also, you mentioned about NEW Bootloader of .264 firmware. Many ppl told me that I should update to new BL to install recovery in MM.
Does the NEW BL has seperated partitions for each recovery and boot(kernel)?
Click to expand...
Click to collapse
Yes exactly there is a seperate recovery partition
raolleel said:
You're right .. I didn't noticed that internalSD is wiped, too. But you can back up it via PC in Recovery or in Android
@backupfunction ... No Recovery has the option to backup InternalSD (because the developers think its useless)
Yes exactly there is a seperate recovery partition
Click to expand...
Click to collapse
Thanks for reply I'm going to try installing MM on weekend
I tried it, it worked perfectly, thanks!