Notice: Rooting your device will break OTAs because they require an unmodified system, so you might want to check for updates before rooting your X. However, there is a workaround:
Boot into TWRP via step 5E below, but DO NOT flash it (step 5D)!!
Do a backup of your completely stock, unrooted ROM
Root the device by flashing SuperSU...zip
When an OTA hits, you can get it by doing this:
Boot into TWRP again without flashing it (same as step 1 above)
Restore your stock, unrooted ROM (from step 2 above)
Apply the update from stock recovery
Backup the unmodified ROM with the update if you want, then re-root as above.
Note: You will lose any changes, mods or app data since you did the backup, but hey, at least the OTA is applied.
If you get stuck with an update that won't flash and you haven't backed-up your unrooted ROM as above, look here:
[Guide] How to Install OTA's with TWRP, and please hit thanks for @SpiritBreak3r :good:
_____________________
Disclaimer: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try. If you get confused with terminology, try looking here for answers or Google it. If you get stuck, post a question in the thread—we're here to help you.
Preliminary steps
1. Make sure that your phone is always charged above 50%!!!
Running out of battery in the middle of flashing something could brick your phone.
2. Make sure that your computer can properly communicate with the device:
We will be issuing commands to the phone from your PC via the USB cable using Android’s SDK tools, in particular ADB and fastboot. If you have not done so already, you must install the following on your Windows computer for this to work:
Java runtime
The Universal Android ADB Driver for Windows.
SDK tools for Android (alternately just ADB & fastboot). Remember where this is installed on your harddrive for later!
You can verify the connection between your PC and phone by running the following procedure:
A. With the phone booted normally, connect it to your computer with the USB cable.
B. Enable Android debugging by going to Settings > About phone and tapping on “Build number” 7 times.
C. Go to Settings > Developer options and check “Android debugging”. A dialogue box will appear asking you to authorize your computer’s RSA fingerprint. Click “Always allow...”
{
"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"
}
D. Open a command prompt in Windows and navigate to the folder where you put SDK tools for Android (ADB & fastboot) above.
E. Type the following command:
Code:
adb devices
You should get a return like this:
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
3. Know how to enter “fastboot mode” on the OnePlus X
To root the device, you must be competent at booting it into fastboot mode. There are two ways to accomplish this:
Power off the phone. Then simultaneously hold down the volume up & power buttons until it vibrates. When done correctly, you will see the words “Fastboot Mode” on a black screen. If not, you dumb-thumbed it, and the device will boot normally into Android. Power off the device and try again.
With the phone running Android normally and Android debugging enabled (see above), open a command prompt in Windows, navigate to the folder where you installed SDK tools (ADB & fastboot) and type:
Code:
adb reboot bootloader
Rooting the OnePlus X
There are three essential steps to rooting the device:
Unlock the bootloader
Flash or boot into TWRP custom recovery [For OxygenOS 3.1.3 use TWRP blu_sp★rk r175]
Flash SuperSU...zip from recovery [For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta]
However, we're going to add a few more to protect your data and device in case something gets borked.
1. Backup your phone’s data
Unlocking the bootloader will involve doing a factory reset resulting in the loss of all accounts, emails, texts, apps and app data, pictures, music, etc. on the device. Move anything you need to keep onto your PC or a cloud service like DropBox.
2. Unlock the bootloader
2A.Go into Developer Options and enable bootloader unlocking
2B. Boot the device into fastboot mode. (Simultaneously hold down the volume up & power buttons until it vibrates.) You should see a black screen with the words “Fastboot Mode”.
2C. Plug in the USB cable.
2D. Verify that your device is connected with this command:
Code:
fastboot devices
You should get a return like the image above under Preliminary Steps
2E. Unlock the bootloader using the following commands:
Code:
fastboot oem unlock
The device will unlock the bootloader, erase all user data and reboot itself into Android. You will have to set up everything from scratch.
3. Re-enable Android debugging
3A. Re-enable Developer options by going to Settings > About phone and tapping on “Build number” 7 times.
3B. Go to Settings > Developer options. Check “Android debugging” and re-authorize your computer’s RSA fingerprint.
4. Download SuperSU zip
4A. Head over to Chainfire’s CF-Root thread and download the SuperSU access management tool from the “CWM / TWRP / MobileODIN installable ZIP” link. It will probably called something like UPDATE-SuperSU-v2.XX.zip. This zip file will root your device and install the SuperSU access management app in one smooth motion. Hit the thanks button for Chainfire or donate to his Paypal account and buy him a Coke.
NOTE: For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta
4B. Copy UPDATE-SuperSU-v2.XX.zip to your phone’s SD card.
5. Flash TWRP custom recovery
5A. Download TWRP recovery.
NOTE: For OxygenOS 3.1.3 use TWRP blu_sp★rk r175
5B. Place file you downloaded above to the location where you installed SDK tools (ADB & fastboot).
5C. Boot the device into fastboot mode and connect it to your computer with the USB cable.
5D. In this step, we will replace your stock recovery with TWRP recovery.
Note: This step is optional. If you want to root but preserve stock recovery, skip straight ahead to step 5E below. Thanks @rockuppl for the reminder. :good:
Open a command prompt in Windows and navigate to the folder where you installed SDK tools (ADB & fastboot). Type the following commands:
Code:
fastboot flash recovery twrp-3.0.0-0-onyx.img
5E. Reboot into TWRP recovery with the following command.
Code:
fastboot boot twrp-3.0.0-0-onyx.img
You should now see the custom recovery you just flashed, not the stock recovery.
6. Backup your stock ROM before making any changes
In TWRP press “Backup.” <--- See how simple this is???
Don’t be a noob—backup your device!!! Right now we don't have stock boot debuggable image files for the OnePlus X, so borking your device could leave you with a nice paperweight until we do. :crying: Restoring from a backup in recovery is easy, and only works if you've backed-up first
7. Root the device
7A. The device should still be in recovery from step 6 above. Go back to the main menu and press “Install,” find UPDATE-SuperSU-v2.XX.zip on the SD card, then flash it.
7B. Reboot the phone. It is now rooted!
7C. Go to the app drawer and open SuperSU. Update the binary if prompted. Its icon looks like this:
7D. Download and install Root Checker from the Play Store to verify that you have root access.
Yes I already own the phone and I see the bootloader unlock switch in dev options. I also checked the stock recovery which gives options to flash files from phone memory or otg. So it must be fairly easy. But I still don't want to risk it without it being tried and tested. If there were a custom recovery I could have also backed up the factory image. Only choice is to wait and see I guess
I could try today evening... will update here.
@CafeKampuchia
Is it ok to flash supersu.zip with stock recovery.
Before flashing supersu.zip, will unlock bootloader . Will follow the guide from oneplue two procedure to unlock..
Flashing supersu is safe on hundreds of devices, but I don't have the X so I can't say one way or the other.
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
CafeKampuchia said:
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
Click to expand...
Click to collapse
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Knockys said:
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Click to expand...
Click to collapse
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
CafeKampuchia said:
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
Click to expand...
Click to collapse
My bad then ahah
mjose said:
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Click to expand...
Click to collapse
Yes it fails on stock recovery, we'll have to wait for a custom one indeed...
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Savya said:
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Click to expand...
Click to collapse
Hey i need your help, i installed the custom recovery in Mandarin but i don't understand anything! Could you please tell me where i should go in this recovery to wipe dalvik cache and flash super su? Step by step? Thanks!
Works for me too ! I'll try to install Xposed now ahah !
Hope they'll release TWRP in English soon !
EDIT : Xposed installed and working ! For those who don't know how to do, see here
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
CafeKampuchia said:
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
Click to expand...
Click to collapse
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Savya said:
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Click to expand...
Click to collapse
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
ukanth said:
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
Click to expand...
Click to collapse
Just flashed it now!
Confirmed that its working and its in English!
Thanks a ton mate!
Also do i have your permission to post your link in the oneplus forums? As there are many users there too waiting for an english version.
@ukanth : shared the recovery on my post on the OP forums
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Related
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
{
"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"
}
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
subodhverma21 said:
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
Click to expand...
Click to collapse
TWRP termnal is just so that your phone will connect as adb to your pc.
eg0097 said:
TWRP termnal is just so that your phone will connect as adb to your pc.
Click to expand...
Click to collapse
my problem got resolved.........
actually driver was the only problem which was not allowing ADB to detect device in RECOVERY mode, though device was detected in FASTBOOT mode
So I reinstall the driver to get ADB Interface installed in system> device manager
and then followed your remaining steps i.e. 6 onwards
Thanks a lot.....
Not really sure about the following, but I hard-bricked my phone while rooting it a few days ago. Black screen, phone wasn't visible in ADB / fastboot, LED didn't change after plugging in the charger etc.
The only thing that helped: holding the power button for at least 2 minutes. The device restarted afterwards w/o any issues.
Can't find the source of it anymore ...
Very useful guide, I revived my soft - bricked Moto G
still not working
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
sascha-1102 said:
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
Click to expand...
Click to collapse
|Could someone help please? I am in the same boat and when try to run the above command, I also get this error and no file appears in the sdcard hence cant flash it.
Thanks
My Moto G is working again since one week with stock 4.4.2. I had to do it ain a bit different way...
First, I could get into bootloader and recovery. after several hours my pc recognizes my phone again, but till now I don't know why and how.
Wanted to reflash stock 4.4.2 kitkat again, but this won#t work. so I figured out that after unpacking, I had to replace the gpt.bin with the one from the 4.4.4 stock update. (see down as zip file)
Then I flashed the 4.4.2 stock again to my phone and all went well. It started again. (now I'm on stock recovery)
If you want to do the OTA 4.4.4 Update, there have to be a few things on your phone, otherwise update always fails.
1. if you have x-posed frameworks installed - uninstall it completely
2. if rooted, go into super su preferences and activate unroot all
3. do not activate developper options, or if done before, just uncheck the mark
4. you must be on stock recovery!
5. restart your phone
6. now search after update in about phone.
if bootloader is unlocked - doesn't matter - can stay unlocked
with me it first installed the 176.* OTA because my flashed stock was still 175.*
this went well, then again searched for update and 210.* (4.4.4 kitkat) could be downloaded ota. after it was done, click to install and it should work well - took a bit time.
now you are on stock 4.4.4, but without root atm.
if you want root back - now flash the newest twpr recovery 2.7.7.1 to phone, because here an OTG USB stick will be also recognized - OTG cable needed before. (don't need to push files first to phone)
copied before the su.zip to usb stick and sticked it to phone, then go into recovery. here you can install super user or better su.zip. restart phone and you got your root back on 4.4.4 stock kitkat rom
I solved this issue with twrp sideload.It worked great.
Thanks it worked for me..BUT !!!
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Ysharief said:
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Click to expand...
Click to collapse
I get this error
When im typing adb push AOSP ( i renamed to that name ) /sdcard/ attacks me this: not found. Any help?:crying: Plez :c
eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
I haven't actually bricked my phone but looks like my ROM.
So, I am trying to make a ROM previously in First Built the ROM didn't even wrote System [That was my fault as I wrote the the 'system' folder in Zip as 'System' and in update scripts 'system' to be extracted in '/system']
But , now the ROM has written /system but remains on Warning Boot loader Locked screen and starts to warm up I have tried Installing Kernels to fix it but no luck please help.
Device->Moto G Falcon XT1033
ROM Details->Custom ROM based on stock 5.1
Priority of problem->5 ,as I use MultiRom and have this Custom ROM as Secondary and CM 13 as primary ,but suggest a fix ASAP .
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Sid_Sun said:
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Click to expand...
Click to collapse
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
lost101 said:
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
Click to expand...
Click to collapse
This isn't MiltiRom's Fault probably but nvm I will flash The Custom ROM as primary and see how it goes .
Friend in step 3 you say "Run the adb setup file and press (Y) all 3 times." But what is the file?
In the list there are only 2 to download files
adb-setup-1.3.zip
twrp.zip
Where do i put the command in the 4th step?
Please help
{
"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"
}
Welcome to the Nexus 6 All-In-One Guide. If you are a new user that is looking for the opportunity to take advantage of your device and do it right the first time, this guide is here to point the way. This thread exists to keep all the necessary methods and material in one common place just for you. As always: Do your homework first.
If followed correctly, this guide can be a useful tool. These steps are listed in the order in which they should be completed. The intent is to seamlessly unlock, root, backup and/or flash, leaving as little room for error as possible. This process will erase and/or reset everything on your device. All steps are assuming you have backed up your contacts, texts, pictures, videos, etc. I do not take credit for any of this material or information.
This guide is a compilation of work from across XDA, most specifically users like @Chainfire and @Chromium, that I have simply brought together.
Step 1: Read. Read. Succeed.
Your journey down the Android path of rooting and modifying can be smooth, fun and educational, based on your attempt at learning everything you can before you begin. This is entirely up to you, the user. There is some excellent material here on XDA that I highly recommend reading over as part of step 1. Even though these 2 informational links were written for the Nexus 5, the knowledge still applies so don't skip this information!
A message from the moderators - All users please read
Yep, read it. It's for your own good. Included with some very useful general forum information, it also contains the forum rules which should also be read and understood.
[FAQ][REF]★All you need to know about Android | Read this before you post/root★
This awesome thread by @abaaaabbbb63 is a *noob friendly* collection of information every user that wants to root their phone should know. Many people blindly follow guides without even knowing what "Rooting" means. Hopefully, this will help new users (and old ones, why not?) understand what is happening with their phone, and what they will put up with. Get on over there and read it.
Be sure to checkout Post #2 below for additional information regarding your Nexus 6
Step 2: Installing The Necessary Desktop Tools
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only).
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
Step 3: Unlock, Root & Custom Recovery
For those of you who want to get most out of your Nexus 6, you will certainly want to root it. Rooting your device provides you as the user many, many benefits. That's why you're here right now reading this. You want it all. Please note that there is always the chance of error during these processes. Bad or faulty USB cables, USB ports, bad/old device drivers on the computer, an active virus scanner. These are a few of the issues that can cause your device to fail to connect or prohibit a successful root/flash. Use good and original OEM USB cables. Uninstall any drivers you may have installed for previous mobile devices and disable your virus scanner.
>>>>>>Before you begin, make sure your N6 has USB Debugging Mode switched on<<<<<<
Before continuing, users must enable Developer Options in the devices settings and select the OEM Unlock option. To do so:
- Go into Settings
- Under About Phone, you'll be able to locate your Build Number
- Tap Build Number until you are notified that you have activated Developer options
- Go into Developer Options, ensure it is enabled and check the Enable OEM Unlock box
- While in Developer Options, ensure the USB Debugging box is checked
Unlock The Bootloader
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Plug the phone into your PC, then open a command prompt window window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
On the phone a screen should pop up asking whether or not you would like to unlock the bootloader. Use the volume rockers to highlight "Yes" then press power to confirm the action.
After the above command has finished executing, run the following (DO NOT skip this step, it is more important than you think):
Code:
fastboot reboot
The phone will reboot. Next you will be presented with a screen containing an android logo and a progress bar (this may take up to ten minutes to complete). Wait until the phone has fully booted up into android, then proceed onto the next section of the guide.
Close the command prompt window.
Obtain Root
The instructions below and the zip file are the work of our beloved @Chainfire. CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmware and be the quickest and easiest way for your first root.
- Download the ZIP file
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
Follow the on-screen instructions - watch both the computer and the device!
**If you want to have root access only you can stop here.**
A word on custom recoveries: A recovery image is the system level software for your Android that lets you perform several maintenance and recovery tasks. The stock recovery image is quite limited in what it allows you to do and therefore, flashing a custom recovery image is required to gain full control of your device’s administration. A custom recovery image allows you to perform the following tasks:
- Wipe your phone’s data (Factory reset) and cache
- Make, restore and manage backups of your phone’s operating system and software
- Mount, unmount and format your phone’s internal as well as external storage partitions
- Install a custom ROM or application from a zip file to your phone
- Wipe Dalvik cache and battery statistics
- Make logs for error reporting and debugging
Additionally, you can download the Goo Manager app to install TWRP updates.
*NOTE: I do not recommend Rom Manager as a tool to do anything but just install and/or update your recovery Do not flash ROMs from this application.
Installing A Custom Recovery
Go HERE to download the latest TWRP recovery for the Nexus 6.
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that you should place the file in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it. After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Close the command prompt window.
STEP 4: Making A Backup
Making a Nandroid will allow you to try out new ROMs while still keeping a safe backup in the event you experience issues during or after a custom OS or kernel installation. Be sure your device is fully charged before proceeding to the backup and flashing procedures.
If you are not already booted into recovery then do so now.
1. Boot into fastboot mode (Volume Down + Power)
2. Browse with the volume keys to Recovery Mode and press the power button
3. You are now in custom recovery.
4. In CWM go to Backup and Restore and select Backup. In TWRP select Backup. Name and select the options you want. Swipe to backup.
5. In TWRP, go to Backup and proceed to the next step(s).
6. After backup is finished, select reboot system now or stay in recovery to continue with this guide.
*NOTE: Be sure to save a copy of these backups to your computer and/or micro sd card. Having a recent backup saved to your computer and micro SD card can be useful if something happens to your phones internal memory.
Step 5A: Wiping Your Device
When flashing any ROM, it is always important to follow the proper wipe procedures in order for everything to function properly. There are various levels of wiping based on what sort of transition you may be making. In this guide, I will list the procedures for a full wipe, presuming that you are coming from the stock firmware and changing your OS completely. This is all assuming you have made the appropriate backups. ALWAYS perform the appropriate wipe before flashing a new ROM or update!
1. If you are not already in recovery, boot in now.
In CWM:
2. Select Wipe data/factory reset
3. Select Wipe Cache
4. Select Advanced and Wipe Dalvik Cache
5. Select Mounts and Storage and format /system
6. If you are transitioning from Android versions (4.4 to 4.x, etc) you must also format /data. You will lose all personal data so back it up first.
In TWRP:
2. Select Wipe
3. Select Factory Reset and wipe
4. Select System and wipe
5. If you are transitioning from Android versions (5.0 to 5.x, etc) you must also select Wipe Data and wipe. You will lose all personal data so back it up first.
Step 5B: Flashing a Custom ROM
Once you have selected a ROM for your Nexus 6:
1. Download the ROM. Be sure to download the appropriate Gapps as well.
2. From your PC, place the ROM/Gapps on your internal storage. Remember where they are.
3. Boot into custom recovery.
4. Perform the wipe listed above if you have not already.
5. From the main recovery screen:
>>CWM - Choose the "install .zip from SD Card" and confirm.
>>TWRP - Choose Install and locate the desired ROM on your internal storage.
6. Repeat step 5 and select the Gapps package.
7. Reboot system. It will take several minutes to load so be patient and don't worry. Once the phone is booted, let it sit for 5 minutes, reboot and enjoy!
>>Additional Information
Want the performance boost available with disabling forced encryption? Check out @bbedward's guide linked below for more information and instructions.
[How-To] Disable Forced Encryption
Running Windows 8.x and having device detection issues? Be sure to grab the Google USB drivers and follow the instructions from the link below.
Nexus 6 Driver (ADB, Fastboot and MTP) for Windows and MAC
Need to return your Nexus 6 to stock for resale, OTA or warranty purposes?
Checkout @Mr hOaX's excellent guide. The procedures require the use of the fastboot tool from the Android SDK. See post #1 above for information on installing this if you have not done so already. In his guide, you have the option of returning completely to stock or select specific portions to flash (radio, recovery, etc).
[Guide][How To] Flash Factory Images For Nexus 6
Looking for stock recovery? If you need to revert to stock to receive an OTA, here's the LRX22C Android recovery:
Unzip the image and flash per the norm in fastboot.
View attachment recovery.zip
Maybe I missed it while skimming the guide, but shouldn't there be instructions for people to get Developer Options? Allowing the PC access to your phone on first plug in (ADB won't discover the device without this)? And, most importantly for Nexus 6 (and 9), checking the "OEM Unlock" option in Developer Options?
Added. Thanks for catching that, @Kusanagi Fire :good:
I was just wondering but where are there custom ROMs? Im assuming there are none, but I cant get many things to work
Thanks for all the great info! Would it be possible to add information about removing encryption to this guide?
welp,I got the phone in the mail yesterday and had plans to stay completely stock for a couple weeks,but just couldn't help myself,grabbed the chainfire and twrp files with this guide unlocked bootloader/rooted/ installed custom recovery so here we go ...made my first nandroid already[emoji4]
bogus83 said:
Thanks for all the great info! Would it be possible to add information about removing encryption to this guide?
Click to expand...
Click to collapse
i'll think about it.
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
So if all I do is unlock the bootloader and root, I can still receive OTAs directly?
Sent from my Moto X using Tapatalk
Are the steps the same for a mac?
gotsoot said:
So if all I do is unlock the bootloader and root, I can still receive OTAs directly?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
yup, but you may lose root and your bootloader may be re-locked if they push a bootloader update with it. just fyi.
the likely (hopefully) worst case is likely that you you have to unlock it again (thus wiping your data) and you have to re-setup the phone and re-root.
i cant guarantee success or failure so you assume all risk when you begin ANY modifications on your device.
Are bootloader updates common for Nexus phones? I can't recall hearing about one (though this will be my first Nexus).
Sent from my Moto X using Tapatalk
There were one or two for the nexus 5
Fastboot
Can somebody confirm that fastboot is working on Windows 8.1 because last time I tried it didn't work and I had to use Ubuntu to fastboot my htc.
I'm running Windows 8.1 but my computer would detect my Nexus 6 after installing the drivers via SDK manager. I followed these additional steps and installed the google USB drivers, and that worked for me:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac/
Great stuff, thanks so much for putting this together!
No need for toolkit or drivers on Mac/Linux
Here's Mac/Linux way.
First create a file on your home folder named something like nexus 6. (This is where your going to save your files.)
Download su(I'll let op point to zip)
Download recovery (same as above from op)
Put them both in that file you created. (Make sure it is in home or you'll have to cd to wherever you put it)
OK make sure you back up your data(this will wipe everything.)
Boot into fastboot.
(Hold power and up/down button)
(Ensure you have adb and fastboot installed on your comp)
cd RootNexus (or whatever you named that folder you created)
*First things first...
./fastboot devices
Should see your device.(if not double check adb and fastboot are installed properly. Follow link. http://forum.xda-developers.com/showthread.php?t=1917237(make sure to click thanks button over there for easy setup.)
.
./fastboot oem unlock
(Follow on screen instructions, this will wipe data. )
./Fastboot restart bootloader.
(Linux users remove ./ in front of fastboot.)
Start up phone and sign in and let it completely boot. Then put SuperSU on device.
On your Mac/Linux
(Ensure you are still in root nexus folder)
./fastboot flash recovery recovery.img where recovery.img is the name of your recovery image file
Once that is done on your phone press the volume up (twice) until you see "Recovery". Then press the power button.*
Once inside recovery go to back up and back up your device.
Flash SuperSU after. Then restart and applaud yourself. Your now rooted. I've been doing it this way since forever
Because decrypting makes such a big change in performance, that would be good to have in this thread as well.
gamewarden234 said:
Because decrypting makes such a big change in performance, that would be good to have in this thread as well.
Click to expand...
Click to collapse
I'm putting together some additional information for post #2 of this thread. It will include decryption. :good:
gotsoot said:
So if all I do is unlock the bootloader and root, I can still receive OTAs directly?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
I would like to know this also.
*nevermind*
[SIZE=+3]How-To Guide For Beginners[/SIZE]
[SIZE=+2]Pixel XL (Marlin)[/SIZE]
{
"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"
}
[SIZE=+3]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Pixel XL (Marlin). I'm going to start off with a couple of the more obvious ones and go from there.
[size=+3]Prerequisites[/size]:
If you are on Verizon, please follow dePixel8 guidelines prior to using this thread
Always update your phone to the latest build available before starting the unlocking/rooting process.
You'll need a working adb/fastboot environment on your PC to get through some of these guides.
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:SDKandroid-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.
[SIZE=+3]Quick Tips[/SIZE]
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
[SIZE=+3]Index[/SIZE]
Post #1
1. How To Unlock Your Bootloader
2. How To Install A Custom Recovery On Your Device
3. How To Root with TWRP Recovery
4. How To Root with via Fastboot (No Recovery)
Post #2
5. How To Install A ROM with TWRP Recovery
6. How To Install A Custom Kernel With TWRP Recovery
7. How To Install A Custom Kernel Using Fasboot
8. How To Flash The Factory Images (Return To Stock)
9. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
[SIZE=+3]1. How To Unlock Your Bootloader[/SIZE]
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.
[SIZE=+3]2. How To Install TWRP On Your Device[/SIZE]
Prerequisites: unlocked bootloader (section 1).
Warning: TWRP is currently in RC1 phase and is not fully stable, flash at your own risk.
This guide assumes you have just unlocked your bootloader and are otherwise stock, NO root yet.
Download the necessary files (IMG and Zip) from the TWRP website and add the TWRP zip to your internal storage: https://dl.twrp.me/marlin/
Place the IMG 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 boot path/to/twrp.img
(The TWRP filename in the command will change depending on which recovery you're flashing)
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your password, reboot to the bootloader and try again. Go to install and browse to the zip and install the TWRP zip
[SIZE=+3]3. How To Root[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Download the latest SuperSU of your choosing to your phone:
https://download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip
Boot into TWRP recovery and enter the install menu.
Navigate to where you have SuperSU stored on your internal storage and select it.
Swipe to install.
Thats it, reboot and you should have TWRP and SuperSU installed
[SIZE=+3]4. How To Root via Fastboot[/SIZE]
Prerequisites: unlocked bootloader (section 1)
Special Note: This is for users who do not have or want TWRP installed and want to run stock root
Download Chainfire's root-marlin-pixelxl.zip located here: https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
Extract Chainfire's zip and follow the instructions in the read me
Code:
***** The short guide *****
*BOOT* (do not flash!) the supplied image, and wait a few minutes:
fastboot boot boot-to-root.img
***** The long guide *****
Before you root your device, you need to unlock your bootloader, if you haven't done so yet.
If you are using a Verizon device, you need a special tool for that. Go find that first.
- Boot into Android
- Enable developer options
--- Settings -> About phone -> Build number: tap 7 times
- Enable OEM unlocking
--- Settings -> Developer Options -> OEM unlocking
- Go into bootloader mode
--- Turn off device
--- Hold volume down and power
- Run "fastboot flashing unlock" and follow the on-screen instructions
--- This will wipe your device
To root your device:
- Go into bootloader mode, if not there already
--- Turn off device
--- Hold volume down and power
- Run "fastboot boot boot-to-root.img"
--- Wait for a few minutes. The device will reboot at least twice
- You should be rooted once Android is fully booted up
*****
Enjoy!
- Chainfire
XDA:DevDB Information
Guide: How To Unlock/Root/Flash for Pixel XL (Marlin), Tool/Utility for the Google Pixel XL
Contributors
bajasur, The Flash, beanstown106, @micmars
Version Information
Status: Testing
Created 2016-11-27
Last Updated 2016-11-26
[SIZE=+3]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Pending......
[SIZE=+3]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
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.
[SIZE=+3]7. How To Install A Custom Kernel via Fastboot[/SIZE]
Prerequisites: unlocked bootloader (section 1)
This guide is for users who DO NOT have TWRP installed, and want to Fastboot flash custom kernels.
Check the md5 to verify its integrity.
Download the kernel file you want to flash from whichever kernel developer you'd like
Place the file in your fastboot folder
Open a command prompt within that folder and run
Code:
fastboot flash kernel kernel_binary
kernel_binary will be replaced with whatever the file name (ie fk-r5.gz for Franco's Kernel)
Reboot your device.
Special Note: You may lose root if you had SuperSU pre-installed, you will need to re root following Section 4 (How to Root via Fastboot)
[SIZE=+1]8. How To Flash The Factory Images (And Return To Stock)[/SIZE]
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.
Download the appropriate factory images for your model https://developers.google.com/android/images
Unzip the marlin-xxxxxx-factory-xxxxxxxx (marlin-nmf26o-factory-4f68765c) into a directory on your PC (for this guide we'll use C:\marlin\).
Once unzipped you should have a folder named marlin-xxxxxx (marlin-nmf26o).
Move the contents of this folder into your Fastboot/ADB environment so that you can run fastboot and adb commands. (Note: I do the opposite and move the most current fastboot and ADB from the Android SDK into this folder)
Look for the windows batch file named "flash-all.bat" and double click on it. This should begin the proper full clean flash of all images back to stock. This should take a few minutes, but eventually your phone should reboot on its own and take you to the Android set up screen.
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 commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
[size=+4]Frequently Asked Questions[/size]
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:
adb reboot bootloader
2. 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.
3. 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.
4. 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.
5. Does taking an OTA update wipe my user data?
No, it doesn't.
6. 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:
fastboot format userdata
More to come, special thanks to @Heisenberg for his excellent guide format
Reservation
Don't forget to pin this
Dude, awesome
Looking good @bajasur!
Nice! Great job...should definitely be pinned
Thanks so much @bajasur! I always used the one by the famous @Heisenberg for the 6P and its great to have one for the Pixel XL.
Any plans to also include the step-by-step for restoring back to stock?
MinimalistChris said:
Thanks so much @bajasur! I always used the one by the famous @Heisenberg for the 6P and its great to have one for the Pixel XL.
Any plans to also include the step-by-step for restoring back to stock?
Click to expand...
Click to collapse
Yes, there is a lot more to come. For now to restore to stock I recommend running the flash-all.bat file that comes within the factory image folder.
A detailed step by step image flashing guide will be linked in the next few days.
Sent from my Pixel XL using XDA-Developers mobile app
Thanks @bajasur! We can still use this to unlock and root from NDE63X correct?
oneandroidnut said:
Thanks @bajasur! We can still use this to unlock and root from NDE63X correct?
Click to expand...
Click to collapse
Negative
For Verizon you need to follow the unlock method provided by DePixel Devs. Once you have unlocked the rooting and twrp methods should work.
Sent from my Pixel XL using XDA-Developers mobile app
bajasur said:
Negative
For Verizon you need to follow the unlock method provided by DePixel Devs. Once you have unlocked the rooting and twrp methods should work.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry I should have clarified it is a Google Store edition just with verizon sim and X software. I can just unlock it like normal correct?
oneandroidnut said:
Sorry I should have clarified it is a Google Store edition just with verizon sim and X software. I can just unlock it like normal correct?
Click to expand...
Click to collapse
Yep! That should work fine ☺
Sent from my Pixel XL using XDA-Developers mobile app
bajasur said:
Yep! That should work fine
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Awesome I am trying to wait until TWRP is stable but im inpatient lol
So this is not the correct guide for a Verizon Pixel is it? Besides the sunshine website has anyone made a guide like this yet for the Verizon model
aholeinthewor1d said:
So this is not the correct guide for a Verizon Pixel is it? Besides the sunshine website has anyone made a guide like this yet for the Verizon model
Click to expand...
Click to collapse
Other than flashing dePixel8 to allow bootloader unlocking, all other steps are identical.
aholeinthewor1d said:
So this is not the correct guide for a Verizon Pixel is it? Besides the sunshine website has anyone made a guide like this yet for the Verizon model
Click to expand...
Click to collapse
I'll clarify in the OP regarding Verizon devices but yes that should be the case
Sent from my Pixel XL using XDA-Developers mobile app
Does rooting without TWRP cause bootloops on NDE63V? I tried it with the all-in-one tool and couldn't get my Pixel to boot past the 4 dots when I was on NDE63V.
I have since flashed the Npf26j update. Would it be safe to root via chainfire's method? Wanted to avoid TWRP for now incase I get the data drain bug.
Thanks!
Please help me I am stuck. My international version of one plus 6t after Rooting using the oneclick root tool here on XDA my device is rebooting and going into recovery mode - the TWRP isn't installed by itself. Please advise me on what to do. I have important data that i missed to backup so I dont want to do something stupid. Shall I install TWRP with the tool? Is there a way to run the device in safe mode? please advice
Here is a video of me trying to get into the system: https://youtu.be/WZKhjJhivmg
Here is a fastboot info:
{
"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"
}
No need to panic yet. I don't know about this tool, never used them. What I would do at this point personally is try and boot (BOOT) the TWRP IMG file. That is the first step in TWRP installation. This will get you into TWRP, with a USB cable hooked to the PC you should be able to transfer any data you need.
Then you can try and fix the issue, likely an easy fix. Might be as easy as flashing TWRP, rebooting to recovery and then Magisk. Or you might need to reflash the ROM, but if you do it as is, reflash TWRP, reboot to recovery, flash Magisk, boot, you shouldn't lose anything.
If you aren't sure at this point, ask, as you will lose data if you do the wrong thing. Also the MSM Tool (since I'm sure this will come up) should always be your last resort as that will lock your bootloader. So I always recommend the Fastboot ROM first before that, especially since you have Fastboot working, but try the other stuff first.
a4abbas said:
Please help me I am stuck. My international version of one plus 6t after Rooting using the oneclick root tool here on XDA my device is rebooting and going into recovery mode - the TWRP isn't installed by itself. Please advise me on what to do. I have important data that i missed to backup so I dont want to do something stupid. Shall I install TWRP with the tool? Is there a way to run the device in safe mode? please advice
Here is a video of me trying to get into the system:
Here is a fastboot info:
Click to expand...
Click to collapse
Just fastboot twrp on your phone. Install the installer again. Reboot and, you will be good to go.
OhioYJ said:
No need to panic yet. I don't know about this tool, never used them. What I would do at this point personally is try and boot (BOOT) the TWRP IMG file. That is the first step in TWRP installation. This will get you into TWRP, with a USB cable hooked to the PC you should be able to transfer any data you need.
Then you can try and fix the issue, likely an easy fix. Might be as easy as flashing TWRP, rebooting to recovery and then Magisk. Or you might need to reflash the ROM, but if you do it as is, reflash TWRP, reboot to recovery, flash Magisk, boot, you shouldn't lose anything.
If you aren't sure at this point, ask, as you will lose data if you do the wrong thing. Also the MSM Tool (since I'm sure this will come up) should always be your last resort as that will lock your bootloader. So I always recommend the Fastboot ROM first before that, especially since you have Fastboot working, but try the other stuff first.
Click to expand...
Click to collapse
scorpio76r said:
Just fastboot twrp on your phone. Install the installer again. Reboot and, you will be good to go.
Click to expand...
Click to collapse
Thanks for your reply.
Shall I use this tool here: https://forum.xda-developers.com/on...t-oneplus-6t-using-oneplus-6t-rooter-t3864238 to flash TWRP using this tool:
or you recommend using something else? and what point should I flash it? after going into stock recovery or fastboot screen? One more thing I almost forgot adding that my phone was already rooted but after doing OTA update and then I use the tool to root again which caused me to stuck in this loop of auto power off.
BTW I have set a password on my phone will that cause any issue accessing TWRP if I do manage to flash it? Please advice
a4abbas said:
Please help me I am stuck. My international version of one plus 6t after Rooting using the oneclick root tool here on XDA my device is rebooting and going into recovery mode - the TWRP isn't installed by itself. Please advise me on what to do. I have important data that i missed to backup so I dont want to do something stupid. Shall I install TWRP with the tool? Is there a way to run the device in safe mode? please advice
Here is a video of me trying to get into the system:
Here is a fastboot info:
Click to expand...
Click to collapse
Hello
Try this, it may help you out and you should have twrp back on your phone:
Download "minimal and adb fastboot" to your pc
Find this folder and open it and you should see twrp image in it, rename it "twrp. img"
In a blank space hold shift button and right click to bring up command window.
Once in this window, you should see fastboot. Type "fastboot boot twrp.img" and hit enter.
you should then have twrp on your phone.
Do this and let me know what happens :
Using 'tools' is a bad habit 'cause you don't know what they do.
Read in twrp thread how to install it manually.
The idea is to temporary boot twrp using the .img file in fastboot (fastboot boot twrp.img) then when you're in twrp flash the installer (file name ending with .zip)
Libraplum76 said:
Hello
Try this, it may help you out and you should have twrp back on your phone:
Download "minimal and adb fastboot" to your pc
Find this folder and open it and you should see twrp image in it, rename it "twrp. img"
In a blank space hold shift button and right click to bring up command window.
Once in this window, you should see fastboot. Type "fastboot boot twrp.img" and hit enter.
you should then have twrp on your phone.
Do this and let me know what happens :
Click to expand...
Click to collapse
Exactly, hopefully the member has the twrp installer on his pc so that it can be moved to the device and, installed to maintain twrp after a reboot.
---------- Post added at 11:36 AM ---------- Previous post was at 11:24 AM ----------
Striatum_bdr said:
Using 'tools' is a bad habit 'cause you don't know what they do.
Read in twrp thread how to install it manually.
The idea is to temporary boot twrp using the .img file in fastboot (fastboot boot twrp.img) then when you're in twrp flash the installer (file name ending with .zip)
Click to expand...
Click to collapse
The msm tool is a definite must have if you own a oneplus device. It has saved many lives here, lol
a4abbas said:
BTW I have set a password on my phone will that cause any issue accessing TWRP if I do manage to flash it? Please advice
Click to expand...
Click to collapse
As stated the tool is probably a bad idea. You should install ADB and Fastboot and use these yourself. The password is not an issue at all, TWRP will just ask you for a password and decrypt your data. You just need the correct version of TWRP for your ROM. Most likely you need:
TWRP 3.3.1-6, from here. As mentioned boot the img, using fastboot. Get your data, then try installing TWRP. Do not install the IMG, you install the zip.
Do not use OTA, with a modified device. Use the instructions for TWRP located here. Download the Zip, install in TWRP. Install TWRP again, reboot to recovery again, flash magisk again. The instructions say to uninstall Magisk, and it's probably a good idea to follow the instructions, but personally I never uninstall Magisk. However I don't have a bunch of a mods installed or anything like that.
I've experienced the same and it sounds like you rebooted to a slot without an operational OS
This is what I did. You can also use MSM recovery tool, very handy when you brick
install google SDK platform on your PC if you don't already have it
Download the latest TWRP zip installer and TWRP img boot image, rename them to TWRP.zip and TWRP.img respectively
I create a folder on my C: Drive as ADB and install the contents of the SDK there and the TWRP zip and TWRP img
you can also place your OOS version there, i name mine OOS_90XX.zip
while fastboot screen is open, connect your phone to your PC
Open Command Prompt window
type "cd \ADB"
"adb devices" to ensure that your phone is connected
"fastboot boot TWRP.img"
TWRP should boot
when in TWRP, go to advanced, then ADB sideload
swipe right to intiate sideload
Type "adb sideload TWRP.zip"
after sideload completes, reinitiate sideload
Type "adb sideload OOS9015.zip"
reboot to recovery
you can then reboot to the other slot, repeat steps above and reboot to system
Frozilla said:
You can also use MSM recovery tool, very handy when you brick
Click to expand...
Click to collapse
He's already said he wants to get data off of it. The MSM Tool will wipe the device, and lock the bootloader. The MSM Tool is a handy tool but it should always be a last resort. This device has a working Fastboot, it can very likely be fixed by many other options that don't include locking the bootloader.
OhioYJ said:
He's already said he wants to get data off of it. The MSM Tool will wipe the device, and lock the bootloader. The MSM Tool is a handy tool but it should always be a last resort. This device has a working Fastboot, it can very likely be fixed by many other options that don't include locking the bootloader.
Click to expand...
Click to collapse
Agreed, it's more of a last resort when the device is unresponsive. That's why i said handy when bricked. The steps that I laid out were intended for him to forego that and retrieve his info.
OhioYJ said:
He's already said he wants to get data off of it. The MSM Tool will wipe the device, and lock the bootloader. The MSM Tool is a handy tool but it should always be a last resort. This device has a working Fastboot, it can very likely be fixed by many other options that don't include locking the bootloader.
Click to expand...
Click to collapse
Agreed
Frozilla said:
Agreed, it's more of a last resort when the device is unresponsive. That's why i said handy when bricked. The steps that I laid out were intended for him to forego that and retrieve his info.
Click to expand...
Click to collapse
Yep, and those where great. I just wanted to make sure it was very clear to the OP that the MSM Tool would wipe his data as it would appear the OP is still learning this device, and the MSM Tool has become lots of people's go to, and while it's handy, it needs to be conveyed it should be used only after all other options have been exhausted.
OhioYJ said:
As stated the tool is probably a bad idea. You should install ADB and Fastboot and use these yourself. The password is not an issue at all, TWRP will just ask you for a password and decrypt your data. You just need the correct version of TWRP for your ROM. Most likely you need:
TWRP 3.3.1-6, from here. As mentioned boot the img, using fastboot. Get your data, then try installing TWRP. Do not install the IMG, you install the zip.
Do not use OTA, with a modified device. Use the instructions for TWRP located here. Download the Zip, install in TWRP. Install TWRP again, reboot to recovery again, flash magisk again. The instructions say to uninstall Magisk, and it's probably a good idea to follow the instructions, but personally I never uninstall Magisk. However I don't have a bunch of a mods installed or anything like that.
Click to expand...
Click to collapse
Yo
Thanks for the detailed instructions however the link you have given me only has IMG (twrp-3.3.1-6-fajita.img) Where do I get the TWRP ZIP file and when I follow the link the instructions are different:
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
8. Choose the recoveryimgfilename.img
9. Swipe to install
So I wonder where is the TWRP ZIP part?
I still couldn't find it
a4abbas said:
Yo
Thanks for the detailed instructions however the link you have given me only has IMG (twrp-3.3.1-6-fajita.img) Where do I get the TWRP ZIP file and when I follow the link the instructions are different:
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
So I wonder where is the TWRP ZIP part?
I still couldn't find it
Click to expand...
Click to collapse
There is a thread about twrp in ROM section everything is in there
a4abbas said:
So I wonder where is the TWRP ZIP part?
Click to expand...
Click to collapse
There are two links there, the top one is the IMG file the one marked "installer" is the ZIP file.
I honestly haven't looked at the instructions in quite some time. It appears the new instructions are to avoid the step rebooting to recovery and reflashing Magisk. As if you just flash the recovery ZIP it will wipe out Magisk. I always do the way I listed, I haven't tried it the "new" way. mauronofrio, the developer of TWRP for our device won't steer you wrong. You can do that if you want.
Striatum_bdr said:
There is a thread about twrp in ROM section everything is in there
Click to expand...
Click to collapse
Yes I am trying to follow the TWRP thread here, no where there is mention or link for TWRP.ZIP file the only instruct to flash the IMG file even at the last part. https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
8. Choose the recoveryimgfilename.img
9. Swipe to install
OhioYJ said:
There are two links there, the top one is the IMG file the one marked "installer" is the ZIP file.
I honestly haven't looked at the instructions in quite some time. It appears the new instructions are to avoid the step rebooting to recovery and reflashing Magisk. As if you just flash the recovery ZIP it will wipe out Magisk. I always do the way I listed, I haven't tried it the "new" way. mauronofrio, the developer of TWRP for our device won't steer you wrong. You can do that if you want.
Click to expand...
Click to collapse
Bummer! Sorry about that , just found it
OhioYJ said:
There are two links there, the top one is the IMG file the one marked "installer" is the ZIP file.
I honestly haven't looked at the instructions in quite some time. It appears the new instructions are to avoid the step rebooting to recovery and reflashing Magisk. As if you just flash the recovery ZIP it will wipe out Magisk. I always do the way I listed, I haven't tried it the "new" way. mauronofrio, the developer of TWRP for our device won't steer you wrong. You can do that if you want.
Click to expand...
Click to collapse
By the way, there is a button under the advanced section of TWRP that say "Fix Recovery Bootloop" I wonder if it can help in my case?
UPDATE: Finally I JUST TAP "Fix Recovery Bootloop" AND IT FIXED my **** bootloop and now i can access system without issues :good:
@OhioYJ Thanks so much for directions, Do you have Paypal/LTC/ETH address? I am gonna gift you some $ as appreciation
BTW I am trying to backup with TWRP however I am having "255" error during the backup of Data partition, any ideas how to fix that one?
a4abbas said:
@OhioYJ Thanks so much for directions, Do you have Paypal/LTC/ETH address? I am gonna gift you some $ as appreciation
Click to expand...
Click to collapse
No gift necessary, we're all here to learn and enjoy our devices.
a4abbas said:
BTW I am trying to backup with TWRP however I am having "255" error during the backup of Data partition, any ideas how to fix that one?
Click to expand...
Click to collapse
It most likely has to do with parallel apps / multiple users.
This post here, is from the TWRP thread. (It's at the top of the TWRP main thread, the DEV posted the link)
This post maybe helpful (The first method is what mauronofrio the DEV of our devices TWRP posted a link to, so that would most likely be the route to take)
Hello,
I am new to phone rooting/modding, this is my first time trying to install a custom ROM (lineageOS) to my OnePlus 8 Pro.
First, I followed this guide for rooting, installing TWRP and then Magisk. The only different thing that I did was, when flashing TWRP, not usingfastboot flash recovery twrp-image-filename.img, but fastboot flash recovery_a/b twrp-image-filename.img, because I read that the former may lead to a boot loop.
Everything worked. Then I proceeded to Install LineageOS on instantnoodlep, where it said I needed to upgrade my stock OS to Oxygen 11/Android 11 first (it came with O10/A10). I did that successfully.
However, it turned out that O11/A11 had overwritten TWRP with the stock recovery. So I flashed TWRP again. This too was successful.
I decided not to install the LineageOS with the LineageOS recovery, as in the official guide, but through TWRP. I copied the LineageOS image to phone memory, booted to TWRP, selected Wipe and did a Factory Reset - Wipes Data, Cache and Dalvik (DID NOT choose Advanced Wipe, probably this was the problem?)
After the reset, I selected the LineageOS ZIP file and installed it.
After booting to system, LineageOS starts loading, but after 4-5 mins I see
QUALCOMM CrashDump Mode
--------------------------------------------------
Panic requested on external modem boot failure
mdm_force_reset
Any help for getting out of this?
It will be MUCH appreciated.
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
MaybeDontAsk said:
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
Click to expand...
Click to collapse
The unlock command would be:
Code:
fastboot flashing unlock
Thanks for the suggestions, I will try them when I get to my home PC, I'm at work now.
In the meantime: can someone explain to me what is the exact procedure for installing LineageOS with the latest TWRP image? More specifically, which options in "Advanced Wipe" should be checked, because in all the tutorials I found they were using old versions of TWRP which did not include the "system" option. Mine had it, so I decided not to use Advanced Wipe at all and use the default wipe options (this is also what they did in one of the tutorials). Could this be the cause for the crash dump error?
Also, I am kind of reluctant to re-lock the bootloader and go back to stock OxygenOS. I still have access to the (LineageOS) recovery mode (it overwrote TWRP). Can I try doing something from there, like maybe overwriting it with TWRP again, then wiping everything (the right way) and installing LineageOS again?
Well when ever I get a Qualcomm crash dump error I always like to go back to stock and re do everything fresh just in case something else goes wrong but if you just don't wanna go back to stock you can do this:
If you wanna overwrite lineage os recovery you can reboot into the bootloader, and just do fastboot flash recovery (drag and drop twrp image here)
So it will be something like:
Code:
fastboot flash recovery C:\Users\YourUsername\Desktop\(recovery name).img
Or if you have the twrp image in the same place at platform-tools you can do:
Code:
fastboot flash recovery (recovery.img)
Or a one time twrp boot:
Code:
fastboot boot C:\Users\YourUsername\Desktop\(recovery name).img
Or:
Code:
fastboot boot (recovery name).img
But like I said it's probably better to re-lock the bootloader to start fresh then you can unlock it again and do anything else. Good Luck.
Anyways in TWRP Navigate To:
Wipe>Advanced Wipe> Dalvik/Cache>Data>swipe to wipe
Go back to TWRP home
Advanced>Adb Sideload
Now in PC cmd do:
Code:
adb sideload (drag and drop lineage os zip here)
Hit Enter And Wait Until It Finishes Flashing
Now For The Google Apps (GAPPS):
Download Nik GAPP From:
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
Select "Download"
Then look through all packages and read what each one contains, I would go with either core or basic. But you may need another apps so just read and choose.
Once you choose, click "download now"
Navigate To Folder
Releases>NikGAPPS R if lineage is 18.1(Android 11)>Latest Version>then choose from here and download.
Back to TWRP
If the download for gapps Finished:
Navigate to:
Advanced>adb sideload
Back On CMD:
Flash Gapps:
Code:
adb sideload (drag and drop NikGAPPS zip)
once it finishes:
On TWRP go back to home menu and navigate to:
Wipe>Format Data>Type "yes">Hit Enter>Go Back To TWRP Menu>Reboot>System if it says "no rom is installed" just swipe to confirm reboot, Lineage OS Is Actually Already Flashed. Good Luck!
I know this is long but it's really not lol.
@MaybeDontAsk
Thanks a lot! I will try again via TWRP first. I don't want to re-lock the bootloader just yet, because I fear something may go wrong in the process and I may end up with a bricked phone AND a locked bootloader, and that will really be the worst scenario, from what I've read in forums.
As for the GAPPS part - I don't plan to install them. Just a LineageOS image will be fine.
Alright well hope everything goes well and yeah I also feared I may end up bricking my device with the msm download tool but I've already done it multiple times.
It has fixed a lot of issues for me wether it is that the device is booting straight into recovery or fastboot or that it's not even booting up!
Just something about TWRP: when I tried just booting to it, the phone froze on the "Fastboot Mode" splash screen and stopped there. So I had to use the flash option.
Also, about flashing: I should use
Code:
fastboot flash recovery (recovery.img)
and not
Code:
fastboot flash recovery_a (recovery.img)
fastboot flash recovery_b (recovery.img)
right?
Just double checking to make sure.
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
{
"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"
}
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
freeride01 said:
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
View attachment 5543241
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
Click to expand...
Click to collapse
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
MaybeDontAsk said:
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
Click to expand...
Click to collapse
Alright.
I gotta find a Windows PC though, I am on Linux/Fedora.
My OxygenOS before the wipe was 11.0.10.10.IN11BA, I guess from the list I should download "OOS 11.0.4.4", because its the latest.
I'll post again when there is some progress.
MaybeDontAsk said:
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Click to expand...
Click to collapse
OK, I got my hands on a Windows 10 PC. I downloaded and extracted the MSM tool and watched the video you linked.
There is no Win7 version of the .exe file, so I guess I'll use the "normal" one anyway.
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
freeride01 said:
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
Click to expand...
Click to collapse
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
MaybeDontAsk said:
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
Click to expand...
Click to collapse
Hi again,
I did the whole process again and when I did adb sideload I got this:
Code:
[[email protected] phone root]$ adb sideload lineage-18.1-20220214-nightly-instantnoodlep-signed.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Now what? There's a slide in TWRP that says "Swipe to start sideload", should I swipe it?
EDIT: Maybe Ishould use adb install as described here?
No, you need to reinstall the adb interface drivers, search up on how to do it on Linux.
Tht link you put is for installing apk directly from adb and not roms.
But adb seems to work, adb devices returns my phone ID.
It says something like "(Device ID) | Sideload?
If yes then reboot both the laptop/pc and phone.
Code:
[[email protected] phone_root]$ adb devices
List of devices attached
19356f32 recovery
(changed some digits in serial no. for privacy)