Related
I purchased a Nook Simple Touch during Black Friday for $40 from Sears. The first step for me is to learn from XDA Nook forum on how to root the device. There are lots of posts and confusion is inevitable for a newbie like me. Finally I figured out what's the best approach and rooted the device quite successfully.
To save time and effort for those newbies like me, I think I shall share what I learned and what I tested here. Therefore, I wrote a post on my personal blog and the link is below:
Step-by-step guide for turning NST to a fully fledged Android e-reader
The tutorial covers:
COmplete backup and restore of your NST
Root
Multi-touch and NoRefresh improvements
The main XDA posts from which I learned a lot are:
http://forum.xda-developers.com/showthread.php?t=1346748
http://forum.xda-developers.com/showpost.php?p=22800284&postcount=10
The authors of these posts are greatly appreciated!
Enjoy your rooted NST!!!
hi, thanks for the easy guide! one correction though, on step #2 of the actual rooting process, you mention "sdcard,XUFullTouch-PART-1-START.zip" twice instead of using the END zip.
thanks for your blog it will help since the information in this forum can be harsh to gather.
But it is necessary to add a step: Check the backup before the step #3
a lot of noobs (included me) fall into the trap of a wrong backup (76Mg instead of ~2G).
The purpose of the backup is to come back to something safe. There is already another blog that details everything to root, but omits to check the backup.
You need to add a section to check if the backup is correct:
- size (must be more than 1,8G,
- must contains 8 partitions
- must have the rom partition with the serial
some people here in this forum gives the procedure for all of this. What we need now is an updated procedure and your blog could be the beginning and then the wiki of xda should be also modified.
I get an acess denied when I try to use the link you give
Rooting, Backing Up TA and unlocking bootloader on a Mac can be a pain in the backside especially if you're a nube. Since there isn't an obvious guide out there for us (the most hated computer users by developers) Mac users i decided to create one.
Before we start make sure you're running the latest Mac OS X Mavericks (which is free thanks to apple generosity ) this is to make things easier for me when it comes to helping you.
PLZZZZ PLZZZZZ Read Instruction first (making sure you have a general under standing of them) THEN FIND A POSSIBLE ESCAPE PLAN (just incase things go south) and obtain the correct files before proceeding to follow them!!!!
WARNING!!!!From this point onwards I AM NOT RESPONSIBLE for any damages to your phone, whether they are as small as a 1/1000 mm scratch or as big as a worldwide Nuclear Holocast caused by Aliens! You decided to follow these instruction so it's YOUR FAULT!
Here's the order of what we'll be covering first to last:
1) Backing Up TA
2) Unlocking Bootloader
3) Installing a custom kernel
4) Rooting
BACKING UP TA
You may have heard rumours saying that "YOU CANNOT BACKUP TA ON MAC OS X, ONE MUST HAVE WINDOWS!".
Well I'm here to tell you that's TRUE, sadly. But FEAR NOT! Because the GODS have given us a work around (which is probably longer), and here it is:
First Downgrade to .534 using latest flashtool for Mac OS X
DOWNLOAD HERE http://www.flashtool.net/download.php (make sure you dave the app in applications folder)
Downgrade instruction here: http://forum.xda-developers.com/showpost.php?p=45464122&postcount=3
You can find firmware folder by right clicking ( if thats enables, surf the interwebs on how to do it if you don't know) then "show package contents" => Contents ==> MacOS ===> firmwares. This is ware you'll place your .ftf fiiles.
Before you ask, yes I know downgrading to .534 from .290 might kills sim detection but flashing .290 again (which we'll do at the end) using flashtool will fix that.
Then download,buy or any other means that are LEGAL "wink wink" (I bought BTW cause I love these guys!), Parallels Desktop 9 or later. Or use Bootcamp if you know what that is and are willing reboot you Mac lots of times just to change something on your phone. To me personally it completely defeat the purpose of having a Mac in the first place although its a nice option.
You can get Parallels Desktop 9 or later legal and get a 14 day trial of it here at their official website here: http://www.parallels.com/downloads/desktop/
Then get yourself a copy of Windows OS (windows 8 recommend cause it comes with inbuilt anti-virus) or try this 90 day free trail of Windows 8/8.1 from Microsoft:
Here is link http://www.microsoft.com/en-gb/business/products/downloads-and-free-trials#/
Then use common sense to install Windows on mac using Parallels or if your new and confused follow instructions from this video http://www.youtube.com/watch?v=UsChUvlTePE
Once windows is installed use this seksy guide to Root: http://forum.xda-developers.com/showthread.php?t=2439328
And this other seksy guide to Back TA: http://forum.xda-developers.com/showthread.php?t=2292598&highlight=ta
NOTE: Connect your device while Parallels Desktop (PD) is running windows and a window will pop up notifying you whether you want to connect device to mac or windows. Make sure you select Windows.
Make sure you save the TA file some where safe like google drive, skydrive, drop box, box or all 4 of them
then use flashtool to flash .290 back (root might disappear depending on what you do.)
You can practically use Windows from PD with other guides on xda z1 forum to do the rest of the step. But step 3 is going to be a Nightmare especially on window because you're dealing with drivers and command prompt. If you're not in good terms with these youre going to suffer with these, trust me I know .
Unlocking Bootloader "THE EASY PART!"
Turn off Parallels Desktop open browser and head to: http://xperiafirmware.com/8-firmware/42-sony-xperia-z1-c6903
Scroll down to how to unlock bootloader and follow the instruction using Mac OS X.
then check if bootloader is unlocked by dialling *#*#7378423#*#* and go to service info / configuration
If the last line says
bootloader unlocked: Yes
Then its unlocked
If it says
bootloader unlocked allowed: Yes
then it is locked but you can unlock it
If it says
bootloader unlock allowed: No
then you cannot unlock it
Installing a Custom Kernal"THE HARD PART!"
For this you need to First set up ADB and Fastboot on MAC. I will post a link to a very very easy to follow guide on how to do that. This guide is pretty easy to follow but I do advise that you follow it carefully down the way words are spelt other wise you're going to run into problems.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=1917237
Take note on of this step "press CTRL+X to exit, then Y to confirm the save then press ENTER" because people forget to press ENTER and the start complaining.
Now download and unzip DoomKernel from: http://forum.xda-developers.com/showthread.php?t=2448613
Save it some where convenient like the "android" folder you created.
Then open terminal and type the Command while your device in in fastboot mode (turn off phone and connect usb while holding volume up Button, a blue light should be shown on Z1):
"adb fastboot flash boot directory of where you placed the kernel/Z1-DooMKernel-v04.img"
here's an example of my code:
"adb fastboot flash boot /Users/RealibleCandy4/Desktop/android/Z1-DooMKernel-v04.img"
Now you have custom kernel on phone after reboot.
Rooting
Download SuperSU (do not unzip) and place on sdcard from: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Flash SuperSU.zip on one of the recoveries which you can access by either holding Volume down/up key after you see the DooMkernel splash screen and phone vibrates.
Well done You are now rooted!
Before you ask, yes I know downgrading to .534 from .290 might kills sim detection but flashing .290 again (which we'll do at the end) using flashtool will fix that.
Click to expand...
Click to collapse
Even on windows if you downgrade from .290 to .534 than flash .290 again, it will fix the sim detection? Also what .290 are you flashing with the mac/windows? Link to the file please?
then use flashtool to flash .290 back (root might disappear depending on what you do.)
Click to expand...
Click to collapse
Again I can't see a link to the file for .290, and root might disappear? What does a user have to do to make sure the root doesn't disappear, obviously they want to avoid this.
Sorry just clarifying questions for other people, and myself. Good work on the guide.
RealiableCandy4 said:
Then use common sense to install Windows on mac using Parallels or if your new and confused follow instructions from this video http://www.youtube.com/watch?v=UsChUvlTePE
Once windows is installed use this seksy guide to Root: http://forum.xda-developers.com/showthread.php?t=2439328
And this other seksy guide to Back TA: http://forum.xda-developers.com/showthread.php?t=2292598&highlight=ta
NOTE: Connect your device while Parallels Desktop (PD) is running windows and a window will pop up notifying you whether you want to connect device to mac or windows. Make sure you select Windows.
Click to expand...
Click to collapse
Or... you know... you could just do it from OS X. Check out my guide, much simpler.
http://forum.xda-developers.com/showthread.php?t=2449244
Seriously?! Backing up TA on Mac or Linux is just a few commands in terminal. Very simple.
Sent from my C6903 using Tapatalk
I know you can use terminal but the problem with that is its pretty easy to make spell miss takes on terminal and it can be frustrating + doing it that way is very dangerous since the TA is a sensitive area also there's no way to check if it worked properly by mock restoring TA. I choose this way cause it's much safer.
Sent from my C6903 using xda app-developers app
RealiableCandy4 said:
I know you can use terminal but the problem with that is its pretty easy to make spell miss takes on terminal and it can be frustrating + doing it that way is very dangerous since the TA is a sensitive area also there's no way to check if it worked properly by mock restoring TA. I choose this way cause it's much safer.
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Depends on how you define "safe", I much prefer doing it myself, then I know it is done properly. And what do you mean by mock restoring? You can easily verify authenticity by MD5:ing the TA partition, and subsequently the image taken of it.
Good advice didn't know that. Like you said it depends on you. I personally prefer this method because I can root and back up TA and check if it's correctly backed up with a push of a couple of buttona and I don't have to deal with the fear of accidentally miss typing commands. I'll (with your permission) put a link to your method in the tutorial sometime tomorrow. I'll have to test it first.
Sent from my C6903 using xda app-developers app
TagEHeuer said:
Even on windows if you downgrade from .290 to .534 than flash .290 again, it will fix the sim detection? Also what .290 are you flashing with the mac/windows? Link to the file please?
Again I can't see a link to the file for .290, and root might disappear? What does a user have to do to make sure the root doesn't disappear, obviously they want to avoid this.
Sorry just clarifying questions for other people, and myself. Good work on the guide.
Click to expand...
Click to collapse
Yes flash .290 will fix it make sure you use the latest Flashtool NOT 0.9.11.0.
for firmware I'm using the 14.2.A.0.290 Generic NCB (Unbranded/Nordic) found at http://forum.xda-developers.com/showthread.php?t=2572195
you can find the .290 files on xda z1 general forum
As for root it will disappear when using Flashtool but on you can get it back once you unlock bootloader, flash custom kernel and flash superSU.zip file. Im not sure if you can root 4.3 with a locked bootloader i havent found anything all ask in Q&A section. This guide is for root with unlocked bootloader.
Are you kidding me ? I like your guide... Like all oft the others which are the same.... The only difference; you are using parallels.
My suggestion for your guide: "Get Parallels on your mac, install windows and follow the known 100 tutorials".
Sorry for flamewars... But its really boring to read the same tutorials with different spellings like about 100 times.
Kind regards
Meet
Gesendet von meinem Nexus 7 mit Tapatalk 4
Edit;
@TagEHeuer
Dont Quote entire OP.............
Not everyone will read the billion guides you've read. The more the helpful. He's not doing any harm to anyone. Yes, quoting OP was a mistake, thank you for pointing it out.
meetdaleet said:
Are you kidding me ? I like your guide... Like all oft the others which are the same.... The only difference; you are using parallels.
My suggestion for your guide: "Get Parallels on your mac, install windows and follow the known 100 tutorials".
Sorry for flamewars... But its really boring to read the same tutorials with different spellings like about 100 times.
Kind regards
Meet
Gesendet von meinem Nexus 7 mit Tapatalk 4
Edit;
@TagEHeuer
Dont Quote entire OP.............
Click to expand...
Click to collapse
RealiableCandy4 said:
Good advice didn't know that. Like you said it depends on you. I personally prefer this method because I can root and back up TA and check if it's correctly backed up with a push of a couple of buttona and I don't have to deal with the fear of accidentally miss typing commands. I'll (with your permission) put a link to your method in the tutorial sometime tomorrow. I'll have to test it first.
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Be my guest, I made it specifically because I wanted people to learn more about their devices and as a result hopefully help increase the average knowledge level on these boards! Let me know if you need any help following it.
meetdaleet said:
Are you kidding me ? I like your guide... Like all oft the others which are the same.... The only difference; you are using parallels.
My suggestion for your guide: "Get Parallels on your mac, install windows and follow the known 100 tutorials".
Sorry for flamewars... But its really boring to read the same tutorials with different spellings like about 100 times.
Kind regards
Meet
Gesendet von meinem Nexus 7 mit Tapatalk 4
Edit;
@TagEHeuer
Dont Quote entire OP.............
Click to expand...
Click to collapse
I understand what you mean I did mention that in the post. But i also mentioned that the problem with that method is adb and drivers (mainly drivers) I tried doing that myself and I found that dealing with drivers is a pain, but luckly for use mac users we don't have to deal with that which is a good thing. It makes the installation of custom kernels via fastboot easy and you dont have to wake up the next morning wondering why drivers don't work anymore (which i went though) and causing you to look through 100s of forums for a solution. Somestimes the long why is the best way.
Hello All,
First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive:
The link to QPST: androidbrick.com/download/latest-qpst-2-7-build-422-425-430-437-qfil-qualcomm-flasher/
(Sorry, I haven't passed 10 posts yet, so you have to manually enter into the address bar)
I came to this forum seeking answers to unbrick my hardbricked Note 4, and after many hours of heartbreak and headache, I have come across a tool called QPST.
This tool is used by Qualcomm, and if you read carefully through the accompanying documentation, you will find some interesting stamps - such as "Confidential" etc.
While I am no expert in the use of QPST, from my own incomplete research I am convinced this tool can be used on any device which sports a Qualcomm chipset (Snapdragon etc.) to unbrick it from certain death.
I have not yet succeeded with my attempts at unbricking, but it is now only a matter of time and kind people pointing me in the right directions. :fingers-crossed:
I am looking for the right files to go in the "phone image" and "boot image" lines in the QPST Software Download program.
I hope we can all see the opportunity this tool represents and spread the word among the greater community, not just developers.
Edit:
Using Software Download:
Phone image files will have a .hex extension and I do not believe they can be found on sammobile. I still haven't found the right one.
Boot image files: I still don't know what they will look like. Likely a .hex file.
Using QFIL:
I suspect all these files can be acquired from a service ROM (whatever a service ROM is - I don't think it is a ROM for android as I know them). I am not completely sure of this however.
Using the flat build option will let you select the programmer. It will have a file name like:
prog_emmc_firehoseXXXX.mbn
(Replace XXXX with the correct numbers for your snapdragon. I don't know what the right ones for the Snapdragon 805 are, but I strongly suspect 8084, with a remote possibility of 8064. Edit: I don't know, don't take my word.
There are posts for other phones on XDA, I don't know if they use the 805 chipset or if the files are compatible.) <--- If anyone wants to research, feel free. Team efforts make a big job seem easy! Please post your results!
Accompanying your firehose file will be a bunch of other files in the same folder.
You will need two .xml files to go with the above (usually in the same folder), which will look like as follows:
rawprogram0XXXX.xml (here XXXX denotes some numbering system which will be determined by the internal memory of the device eg 16GB, 32GB, 64GB. I saw an example for a OnePlus One which had rawprogram0_64G.xml.
I'm NOT 100% SURE on this numbering system, as elsewhere on XDA I have come across different file names!
Here's the truncated link: androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/)
patch0.xml
When I find the above, I will post or hassle an admin to post, as these will likely unbrick any Snapdragon 805. Happy hunting!
Here's a truncated link to XproZayd's thread, where a different avenue is explored (and where I got my idea about the 8084 number for firehose -- Remember, I could be wrong!)
forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
This thread is for discussing QPST and how to use it - if you have a hard bricked phone I am not able to help at this stage. However, should anybody find / 'acquire' the right files to use with QPST, we will all benefit.
What made your device hard brick
Sent from my SM-N910G using Tapatalk
Mistake 1: I bought the phone with the known problem of a USB port not working.
Mistake 2: I bought a replacement USB board and replaced it myself, after which the fun and games began. The one time the screen did light up I got an error message about mmc read fail and could not boot.
Mistake 3: Like a fool, I pulled the battery. Now I have a hard bricked / useless Note 4.
Unless the mmc is physically damaged (which I refuse to believe) the phone should be salvageable from its hard brick state. Provided I can find the right files to go with QPST.
Edit:
I have tried contacting Qualcomm to get the files, who have pointed out that they are proprietary to the licensee, ie Samsung. Here's the e-mail below.
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
However, the following link should help you with the information you're looking for:
http://www.mydragonboard.org
Alternatively, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.
can you explain to me everything that is happening?
i got my note 4 hardbricked from......
i really dont know
i was modifying my phone but then it would not boot
AlexanderDAB said:
can you explain to me everything that is happening?
i got my note 4 hardbricked from......
i really dont know
i was modifying my phone but then it would not boot
Click to expand...
Click to collapse
Is it going in download mode or recovery ?
What were you exactly flashing ?
Is it detected in pc as qhsb loader ?
Is the splash screen GALAXY NOTE 4 showing up ?
Sent from my SM-N910G
Update:
So far I have contacted Qualcomm, Intrinsyc (they sell Snapdragon development boards), and a Samsung retail outlet.
All have come back as a negative - the closest I could get was the Samsung retail outlet where a dude used to work in the repair centre and had access to the files then.
Unfortunately, Samsung revoked his permissions now that he only works in a retail outlet.
He knew what I was talking about, but due to Samsung and their encryption etc, he couldn't provide me with the files.
C_dog_1 said:
Mistake 1: I bought the phone with the known problem of a USB port not working.
Mistake 2: I bought a replacement USB board and replaced it myself, after which the fun and games began. The one time the screen did light up I got an error message about mmc read fail and could not boot.
Mistake 3: Like a fool, I pulled the battery. Now I have a hard bricked / useless Note 4.
Unless the mmc is physically damaged (which I refuse to believe) the phone should be salvageable from its hard brick state. Provided I can find the right files to go with QPST.
Edit:
I have tried contacting Qualcomm to get the files, who have pointed out that they are proprietary to the licensee, ie Samsung. Here's the e-mail below.
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
However, the following link should help you with the information you're looking for:
http://www.mydragonboard.org
Alternatively, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.
Click to expand...
Click to collapse
I have the same problem and also looking for a solution. I will contribute to this post as I find something.
There is a similar post here:
http://forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
---------- Post added at 07:10 PM ---------- Previous post was at 06:30 PM ----------
Try this manual.
http://dl-1.va.us.xda-developers.co....rar?key=yrJPiZgu63c6RxNIbU_xVA&ts=1474829412
I've found it earlier today but haven't had a chance to try it yet.
Says the file is gone
Sent from my SM-N930W8 using XDA Labs
It's just the pdf and .pit that i used here: http://forum.xda-developers.com/note-4/help/hard-brick-phone-off-long-help-fellow-t3468792
yashthemw said:
Is it going in download mode or recovery ?
What were you exactly flashing ?
Is it detected in pc as qhsb loader ?
Is the splash screen GALAXY NOTE 4 showing up ?
Sent from my SM-N910G
Click to expand...
Click to collapse
it won't boot at all
i was messing around with the system on the factory binary firmware
yes, it is
nope, it will not boot
i have same problem does any one sucess with this process ?
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Reporting Via N910G.
yashthemw said:
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Reporting Via N910G.
Click to expand...
Click to collapse
can you get me a dude with an AT&T note 4?
same boat with my N910F
C_dog_1 said:
Hello All,
First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive:
The link to QPST: androidbrick.com/download/latest-qpst-2-7-build-422-425-430-437-qfil-qualcomm-flasher/
(Sorry, I haven't passed 10 posts yet, so you have to manually enter into the address bar)
I came to this forum seeking answers to unbrick my hardbricked Note 4, and after many hours of heartbreak and headache, I have come across a tool called QPST.
This tool is used by Qualcomm, and if you read carefully through the accompanying documentation, you will find some interesting stamps - such as "Confidential" etc.
While I am no expert in the use of QPST, from my own incomplete research I am convinced this tool can be used on any device which sports a Qualcomm chipset (Snapdragon etc.) to unbrick it from certain death.
I have not yet succeeded with my attempts at unbricking, but it is now only a matter of time and kind people pointing me in the right directions. :fingers-crossed:
I am looking for the right files to go in the "phone image" and "boot image" lines in the QPST Software Download program.
I hope we can all see the opportunity this tool represents and spread the word among the greater community, not just developers.
Edit:
Using Software Download:
Phone image files will have a .hex extension and I do not believe they can be found on sammobile. I still haven't found the right one.
Boot image files: I still don't know what they will look like. Likely a .hex file.
Using QFIL:
I suspect all these files can be acquired from a service ROM (whatever a service ROM is - I don't think it is a ROM for android as I know them). I am not completely sure of this however.
Using the flat build option will let you select the programmer. It will have a file name like:
prog_emmc_firehoseXXXX.mbn
(Replace XXXX with the correct numbers for your snapdragon. I don't know what the right ones for the Snapdragon 805 are, but I strongly suspect 8084, with a remote possibility of 8064. Edit: I don't know, don't take my word.
There are posts for other phones on XDA, I don't know if they use the 805 chipset or if the files are compatible.) <--- If anyone wants to research, feel free. Team efforts make a big job seem easy! Please post your results!
Accompanying your firehose file will be a bunch of other files in the same folder.
You will need two .xml files to go with the above (usually in the same folder), which will look like as follows:
rawprogram0XXXX.xml (here XXXX denotes some numbering system which will be determined by the internal memory of the device eg 16GB, 32GB, 64GB. I saw an example for a OnePlus One which had rawprogram0_64G.xml.
I'm NOT 100% SURE on this numbering system, as elsewhere on XDA I have come across different file names!
Here's the truncated link: androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/)
patch0.xml
When I find the above, I will post or hassle an admin to post, as these will likely unbrick any Snapdragon 805. Happy hunting!
Here's a truncated link to XproZayd's thread, where a different avenue is explored (and where I got my idea about the 8084 number for firehose -- Remember, I could be wrong!)
forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
This thread is for discussing QPST and how to use it - if you have a hard bricked phone I am not able to help at this stage. However, should anybody find / 'acquire' the right files to use with QPST, we will all benefit.
Click to expand...
Click to collapse
Im in the same boat with my NOTE 4 N910F. Totally blacked out but still picking it up on the PC with QFIL files have found some files but there not the right phone I think.
so fails to load with SAHARA.
cannot find firehose for 910F. Wish someone could solve this one and then publish it all. someone will eventually but QFIL will unbrick all Qualcomm provided you can make the files.
Let me know if you or anyone does. cheers
Lofhario said:
Im in the same boat with my NOTE 4 N910F. Totally blacked out but still picking it up on the PC with QFIL files have found some files but there not the right phone I think.
so fails to load with SAHARA.
cannot find firehose for 910F. Wish someone could solve this one and then publish it all. someone will eventually but QFIL will unbrick all Qualcomm provided you can make the files.
Let me know if you or anyone does. cheers
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3488114
Tried this?
Reporting Via N910G.
Hi, got a Phicomm Energy M+ (E551). It turned off as the battery was empty, so I charged it overnight.
But:
-Switching it on only shows the phicomm logo
-Trying to enter recovery, shows phicomm logo for a second and then the screen stays lit. Nothing else happens.
-On Windows 7 device manager shows it as "RELINK HS-USB QDLoader 9008 (Com3)" (VOL Up+VOL Down + Power)
-fastboot/adb wont find it
-I tried this http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
I dont have a emmc backup but an unzipped Stock ROM of the E551L which support told me to use. (put on SD card and reboot into recovery, but I cant get into recovery)
Hence I use the unzipped ROM with the Qualcomm FLasher :S (http://na.phicomm.info/release/E551L...TA package.zip)
-It starts the process but then says "Failed to enter EDL" (Emergency) mode
Another thing I stumbled across is :
E551L has Qualcomm MSM8916 and Android 4.4.2
E551M has Qualcomm MSM8915 and Android 4.4.4
Will I have to quire a deepflash cable or am I missing something here ?
yashthemw said:
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Click to expand...
Click to collapse
tried but not working
waiting for other solution
This DevDB project and it's related files are by Aravind V. Nair. I'm stating this because so many people are trying to impersonate me. For example, @Balaji Sriram More info: Balaji Sriram impersonating Aravind V. Nair
Most of you are probably facing battery issues. Please check what I have to say regarding that before proceeding. So many people have reported success after fixing the battery issue. Details are available at the bottom of the post
Click to expand...
Click to collapse
If your eMMC storage controller is corrupted, no method will work. You need to replace the motherboard. I'm sorry, I can't help you with that.
Click to expand...
Click to collapse
Big thanks to @ariel.buszczak for his continuous support in every way he could!
Big thanks to @waulliano for uploading the backup.img for XT1022! Download from here
Please upvote the TWRP time issue on GitHub here: TWRP 3.0.2-0 build to 3.1.1-0 build time miscalculation on so many devices.
Click to expand...
Click to collapse
Introduction?
Yes, of course. Hi there!
I have a bricked Motorola Moto E 1st Generation XT1022 condor. I watched so many threads on various forums to try and unbrick, but unfortunately all threads just got abandoned. Hence, I have come up with a DevDB project to try and unbrick Motorola Moto E 1st Generation XT1022 condor if possible. Please note, this project is only for Motorola Moto E 1st Generation XT1022, XT1021 and XT1025 condor. Between, I also have an unbricked working Motorola Moto E 1st Generation XT1022 condor along with the bricked one for test purposes.
This XDA DevDB project is aimed at developers mainly to gather all possible ways to unbrick a hard-bricked Motorola Moto E 1st Generation XT1022 condor, but not restricted to people who want to try their luck at unbricking their Motorola Moto E. Please don't post 3-line request like "my device is bricked, please help" as you will be ignored. If you can't do the research required to provide the right details plus finding the correct files required then, this DevDB project is not for you. The programs, its associated files & threads, etc are NOT going to be being actively developed very soon (July 10th 2017) as I get busy and involved with other things. But the thread remains open for user to post more information, additional files, updates from the public, etc. It's not here for lazy people to scream fix my device, can those type of users please speak to your retailer, cell phone service shop??
I will reiterate again, THIS IS A DEVELOPMENT THREAD AND NOT A REQUEST PAGE FOR "fix my device"
Click to expand...
Click to collapse
I haven't stopped working on this. I do update this XDA DevDB and my GitHub repository for the as I get time.
Please go through this DevDB post thoroughly.
Click to expand...
Click to collapse
Rules and regulations:
Please click the 'Follow Project' button to get notifications every time I update files or make any other changes instead of asking me manually via PM or in thread replies. I won't reply to unsolicited spam messages. So, DO NOT waste your time crafting them.
Click to expand...
Click to collapse
Obey all XDA rules posted here along with CODE_OF_CONDUCT.md posted by me here.
Click to expand...
Click to collapse
Please read through this post and also go through the README.MD file on my GitHub repository for this project carefully and thoroughly. They are created for a reason. I won't reply to unsolicited spam messages, tags, quotes, replies, etc. So, DO NOT waste your time crafting.
Click to expand...
Click to collapse
Warning: I am in no way responsible for your actions. You are on your own. Please undertake all actions at your own risk.
Click to expand...
Click to collapse
Please compress all files before uploading to the cloud after removing personal data. I'm not going to check otherwise.
Click to expand...
Click to collapse
Please attach error codes and other additional information is separate files to avoid clutter. I'm NOT going to check otherwise.
Click to expand...
Click to collapse
DO NOT share anything from this thread. DO NOT mirror anything without prior permission. I have recently busted so many people who have tried to do so despite my warning and even got them banned.
How can I get in touch with you?
My personal blog (All social media profiles link are available):
About Aravind V. Nair
Click to expand...
Click to collapse
Or
Just Search Google for 'Aravind V. Nair' and you can find me.
Click to expand...
Click to collapse
Or
My website: Get to know Aravind V. Nair
Click to expand...
Click to collapse
Or
XDA: Aravind V. Nair - XDA Developers
Click to expand...
Click to collapse
Where can I find the files and instructions?
Please check here: Motorola Moto E XT1022 condor files - GitHub (Aravind V. Nair)
How do I support you?
Hit the thanks button below and the 5-star button above to show your support. Also, you can 'star' and 'watch' my GitHub repository Motorola Moto E XT1022 condor files - GitHub (Aravind V. Nair).
Follow me on social media networking sites if you wish.
Donate to me if you wish by clicking here
What is the goal of this project?
The goal of this project is to gather all possible ways to unbrick a hard bricked Motorola Moto E 1st Generation XT1022 condor. Methods 3, 5, 6, 7 and 8 are perfectly working. Your mileage will vary with other methods. Please don't give up on first try. You need to try a lot of times and test your luck.
What is the proof that this has worked?
I have attached photos to this DevDB post. Please have a look at them.
Will this work for everyone?
As long as you haven't corrupted any of your phone's hardware, you do have chances of unbricking. If the NAND adapter or related parts are not functional, don't even expect to unbrick. A lot of you have tried weird files on the internet, so chances will reduce accordingly.
Where can I find the changelog?
I frequently update and patch things in my GitHub repository as I get time. Be sure to check the changelog here.
How do I find out which bootloader I have?
Sorry, I don't think that's possible when the phone is bricked. I'm not sure though. But definitely, your bootloader version would be the version from your last working stock OS (or custom OS, only if you flashed the motoboot.img or any other equivalent bootloader image).
If fastboot works,
Code:
fastboot getvar all
Can I restore factory aka original firmware if my bootloader is locked?
Yes, you can. However attempting to downgrade to an older version of Android may fail and isn't a good idea. Even with an unlocked bootloader, downgrading cannot be guaranteed. It's also important to be aware that flashing the wrong bootloader (motoboot.img) for your model can have serious consequences. Always identify your model of Moto E and verify the files before flashing.
If you downgrade your phone, it is advised to avoid all OTA updates. These updates can result in a hard-brick (phone will not turn on) if you have a newer bootloader than the one expected. For example, most of you had the Lollipop bootloader, but have downgraded to Android KitKat and thus bricking your phones.
How to disable OTA Updates?
Without root access
Settings > Apps > [swipe left to 'All'] > MotorolaOTA (or Motorola Update Services or something similarly named) > Disable
With root access
Google Play Store has many apps that will allow you to 'freeze' the OTA Update service. Titanium Backup is a common example.
Alternatively, with a 'root access' file explorer, you can delete or rename the following files:
/system/etc/security/otacerts.zip
/system/priv-app/3c_ota/3c_ota.apk
These additional files can be removed or renamed: (If you still get an OTA Update notification)
/system/priv-app/3c_checkin/3c_checkin.apk
/system/priv-app/3c_devicemanagement/3c_devicemanagement.apk
/system/priv-app/3c_notification/3c_notification.apk
I'm a developer or programmer or want to help. Could you please give some reference links?
Yes, of course. All contributions are welcome! Code, documentation, graphics or even design suggestions are welcome; use GitHub to its fullest. Submit pull requests, contribute tutorials or other wiki content -- whatever you have to offer, it would be appreciated!
Please feel free to get in touch with me. I'll always be available even after the deadline. Refer CONTRIBUTING.md on my GitHub repository for reference material and other things.
What are the possible methods of unbricking?
Refer Unbrick methods.md on my GitHub repository.
Where can I download the firmware files?
Check my GitHub README.md file for all files for all models or alterantively Moto E Factory Firmware Images by @lost101
Moto E won't power on. Only white light LED comes up when connecting powers source. Can I charge on AC, etc.
This has nothing to do with clearing cache, recovery and other nonsense. It is just a problem of overly discharged battery when the battery voltage drops below the 3.8 V, which is the minimum voltage of LiPo aka Lithium ion Polymer battery. Unlike other phones, all Motorola devices come with LiPo batteries.
When the battery reaches less than 0%, i.e., less than 3.8 V the phone will not allow it to turn on, as it is harmful for the battery and it might burst. So for these physical security reasons, the phone's adapter chipset/regulator stops the battery from charging. I faced the same problem many times while bricking and unbricking. One thing you could try is to jumpstart the battery by providing excessive power at your own risk, or consider replacing the battery. It is advisable, to never let the battery fall below 10 %. Below 0 %, the internal resistance or rather the impedance of the battery increases to a very very high constant, thus rendering the battery in a 'cannot be charged state'. I won't by trying to fix via firmware as it is very dangerous to charge a battery in such a state. We do not want another bomb apart from the already existing Samsung Galaxy Note 7, do we? :laugh:
Please check your battery voltage using a multimeter or voltmeter and contact me with the same. Please be very careful when removing the battery as Moto E has a loose pin and is easy to break. Caution advised!! For checking using multimeter, set to DC 20 Volts and use the correct input pins. For voltmeter, just use any DC voltmeter having a range of 0-5 Volts.
If the voltage is below 3.8 V, you have to replace the battery. If it is between 3.3 - 3.5 V, you have chances of resurrecting the battery. So try using a above 2 A charger (connecting to laptop won't work as that is just 0.5 A) and leave it like that for about 5 days continuous. Below 3.3 V, please replace the battery. It's not advisable to try and jumpstart.
For the prerequisites, you need a T4 Torx screwdriver and a new Moto E battery. Please buy genuine things. You could have a look at Amazon, Flipkart, eBay, IFIXIT, Snapdeal, etc and also offline stores. Search with the model number of the battery. For XT1022, XT1021 and XT1025, it is Motorola EL40 manufactured by SONY Electronics with a typical mAh of 1980 and minimum of 1860 mAh aka 1860/1980 mAh (min/typ) and 7.1/7.5 Wh (min/typ).
PLEASE DO NOT USE AC TO CHARGE DC BATTERIES DIRECTLY.
You have a high risk of causing serious damage. You might end up killing yourself! Please do not try this. To charge in this manner, you need a bridge rectifier. Noobs, please don't even venture here or think of making it. The battery will not get charged because AC supply changes its polarity after each half cycle. In India, it changes 50 times per second, Brazil 60. Therefore, the battery will be charged in one half cycle and discharged in the next half cycle. So basically, you are damaging the battery due to frequent charging and discharging cycles. Please do not try this!! There is high risk of fire damage and explosion. Those of you who already tried this, please discard the battery immediately to a recycling firm or any other relevant organisation for your country or city. It is not advisable to keep a spoilt battery at home. Using a resistor is not a good idea either as a resistor obeys Ohm's Law which states that the current flowing through any conductor, in this case the battery, is directly proportional to the potential difference across the terminals. So you wouldn't have a steady output. A diode would be preferable. Those who have no clue about these, please do not venture here. I reiterate, I won't be held accountable for any damage caused by you to yourself or your belongings or to anything else.
I was using the Moto E and it suddenly died. What do I do?
Step 1: Open up the phone as I have mentioned earlier. (If you read whatever I have written, you should be knowing what I'm talking about.)
Step 2: Detach the battery. Be very careful not to destroy any internal parts such as the connector which is very fragile.
Step 3: Connect the official charger. (Other chargers didn't work for me always during my testing.)
Step 4: Wait for the screen to say 0% or battery not connected or even if the screen turns on, consider yourself lucky.
Step 5: Attach the battery and reassemble the phone without removing the Moto charger.
Step 6: Go to fastboot, unlock the bootloader and use my fastboot unbrick script for your OS (I have made for Linux, Windows and MacOS). Leave it on charger for a day or two after this.
Step 7: Voila!
This is caused due to undercharging, overcharging or excessive battery drain cycles. In case the phone doesn't power on after connecting battery, check that the EMF of the battery is above 2.9 V with a multimeter as mentioned before.
How to power on Moto E without charger and unbrick?
Safest way is to use the original Motorola charger. As far as I have seen, all the original Motorola chargers have the 4th pin available. For the geeks:
Pin 1: VDD (+5V)
Pin 2: D- (Data-)
Pin 3: D+ (Data+)
Pin 4: ID (ID)
Pin 5: GND (Ground)
The additional pin added to the conventional USB port is the ID pin added to the 4th electrical pin which allows to recognize the device. The technical name is micro USB - B for the one on the charger and mini USB - A for the one on the charger. You can bypass power using this concept. This too is strictly not for noobs.
Errors:
Code:
Preflash validation failed
Buy a new phone. I doubt anyone can help you now...
Code:
Not able to flash GPT / Motoboot
You are not using the right firmware. Try another firmware.
Code:
FAILED (blank-flash: sdl-transfer-image: sdl-hello: invalid HDLC frame)
or
Code:
FAILED (blank-flash: sdl-transfer-image: sdl-hello: error sending packet)
Your bootloader files do not match your bootloader version, use another bootloader.
Code:
Stuck on Opening device: . COM ??
or
Code:
Greeting device for command (Or any other) mode
or
Code:
Switch To FireHose (Or any other) mode
Press and hold power button until detection or until flashing begins.
I'm fed up!! Nothing is working for me!!
Calm down!! Replace your motherboard and/or battery and/or screen, whichever is spoilt. That's the easiest option. But it wouldn't be a good choice to buy new parts now. The phone is quite old. I suggest you buy a new phone instead. That would be a wiser idea. Methods 3, 5, 6, 7 and 8 are perfectly working. Your mileage will vary with other methods. Please don't give up on first try. You need to try a lot of times and test your luck. You are the one who brought your device to this condition. Only you can help yourself.
Does this project have a website?
Yes, a very basic one though. Check here.
Please go through this XDA DevDB main post and my GitHub repository for the same before commenting, messaging or posting.
XDA:DevDB Information
Unbrick hard bricked Motorola Moto E, Tool/Utility for the Moto E
Contributors
aravindvnair99, Thanks for all support!
Source Code: https://github.com/aravindvnair99/Motorola-Moto-E-XT1022-condor-unbrick
Version Information
Status: Stable
Current Stable Version: 309
Stable Release Date: 2018-05-29
Current Beta Version: 309
Beta Release Date: 2018-05-29
Created 2017-05-01
Last Updated 2018-05-29
Reserved
By @kyocell
I am currently getting some SAHARA Port errors I'm trying to install and uninstall drivers and trying.
Will keep updating if it works.
Edit- Fixed SAHARA Port errors but now experiencing different ones.
Edit2- Now experiencing some kind of SAHARA Protocol errors.
Fixed errors guide- If you get any kind of SAHARA Port error then follow this easy guide.
1) First off, delete all the preinstalled drivers
2) disable your machine's driver signature enforcement by doing this -
Click the Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.
3) After you enter your machine with driver enforcement disabled, Now go to the folder "Drivers" and extract the Qualcomm drivers and install them.
4) Here comes the tricky part. Now open your "moto e unbrick folder". Provided by @aravindvnair99 at his GitHub page and open the folders patch0.xml , prog_emmc_firehose_8x10 , rawprogram0.xml and copy all the contents into a new folder called "unbrick".
5) Now install the QPST tool. (installer in the unbrick folder provided by @aravindvnair99 at his GitHub.
6) Once you have this installed, go to the location of the installation of Qualcomm--> QPST --> Bin --> and copy this folder we made called "unbrick" into "bin" folder.
7) Now run Qfil.exe file which is located in the "bin" folder as well.
8) Now, plug your moto e with USB to your pc. If any drivers start installing, let them install.
9) Now select the port. Then browse the path for Programmer. For this click browse --> locate to the "unbrick" folder and select on "All files (*.*)" located at the bottom right of the browse window (dropdown).
10) Now select the file "programmer_8x10.mbn" and click ok.
11) Now click on load XML and locate to the "unbrick" folder and select the "rawprogram0.xml" file then another browse box will open and this time select "patch0.xml" and click ok.
12) You are now all set!
13) Finally click the "download" box and watch your phone come alive!
Hope this guide was easy. @aravindvnair99 you can use these instructions for method 1 as they are more elaborated & also it will save up your time so that you wont have to type so much data instructions. Its all up to you! i only wanna help all those people with this 'Dead moto e' problem and show them that there is still hope!
Much love! Hope it helped!
<3
P.S @aravindvnair99 please correct me if i have told anything wrong anywhere.
Edit - The following error still persists for me
20:39:51: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
20:39:51: ERROR: function: sahara_main:854 Sahara protocol error
20:39:51: ERROR: function: main:265 Uploading Image using Sahara protocol failed
EDIT - FIX FOR THE SAHARA ERROR
1) right as you plug in your phone to your pc and hear that sound (when device is plugged in to pc) right away click the download button without any waste of time.
Reserved
Happy to see this thread. I also have a bricked Moto E XT1022. After searching in many websites , i found that only flashing emmc using EasyJtag box has sloved the problem. Can you do anything with that flash file which flash the bootloader.
arputhatonyking said:
Happy to see this thread. I also have a bricked Moto E XT1022. After searching in many websites , i found that only flashing emmc using EasyJtag box has sloved the problem. Can you do anything with that flash file which flash the bootloader.
Click to expand...
Click to collapse
@arputhatonyking Thanks for the positive response. Sorry to hear that you too have a bricked condor. Yes, for hard bricked only JTag seems to work now. I don't see any other methods. For soft bricked, it is easy to recover. I am trying to find a solution (if possible) using blankflash or any such similar flashing procedures.
Stay tuned as you might be of help to us.
aravindvnair99 said:
@arputhatonyking Thanks for the positive response. Sorry to hear that you too have a bricked condor. Yes, for hard bricked only JTag seems to work now. I don't see any other methods. For soft bricked, it is easy to recover. Me and @Balaji Sriram are trying to find a solution (if possible) using blankflash or any such similar flashing procedures.
Stay tuned as you might be of help to us.
Click to expand...
Click to collapse
Hope to get a successful one..
i flash emmc backuped from eazy jtag with old riff box 1 but, not enter to fastboot. need read from worked phone and try flash to dead one. i look it to ebay but not find with low price phone/ if find and buy one, i will try read it and post here. i have hard bricked XT1021. it flashed customer from XT1022 firmware, now it dead.
VIPER_GE said:
i flash emmc backuped from eazy jtag with old riff box 1 but, not enter to fastboot. need read from worked phone and try flash to dead one. i look it to ebay but not find with low price phone/ if find and buy one, i will try read it and post here. i have hard bricked XT1021. it flashed customer from XT1022 firmware, now it dead.
Click to expand...
Click to collapse
I didn't quite understand what you were trying to say. As far as I understood:
You should have never flashed wrong firmware even though the only difference is the modem files between XT1022 and XT1021. Sure, will wait for your reply. Thanks for your time @VIPER_GE :good:
has XT1021 flashed as XT1022, now it dead. flashed with customer. i try restore with emmc isp flashing with riff box but not work. need try with Z3X easy jtag, not have this one
VIPER_GE said:
has XT1021 flashed as XT1022, now it dead. flashed with customer. i try restore with emmc isp flashing with riff box but not work. need try with Z3X easy jtag, not have this one
Click to expand...
Click to collapse
Oh, okay. Now I understand. Thanks a lot for the clarification @VIPER_GE !
Actually, Riff Box is mainly for selected Samsung devices. Apart from those, only for the ancient (first few) Motorola and HTC devices. Z3X I heard works for recent devices. I am not sure though. Give it a try. There was another JTag thing. I don't remember the name now. It works for all devices having Qualcomm chipset. Let me see if I can find or remember it. I'll send you the link. Between, are you a technician or something? Or just another curious one like us?
just another curious one like us
Anyone know how to generate BlankFlash Files
Can anyone just give the method to flash in bootloader
And is the file listed in the thread is enough or need some more things to unbrick
https://www.youtube.com/watch?v=Qf7kG3qnyx0 https://www.youtube.com/watch?v=_KRFxtz4h24
Do you guys have jtag ?
i have only FIFF Box 1,
We need RawPatch And Programmer Files for QFIL Flash.
mannu233 said:
Can anyone just give the method to flash in bootloader
And is the file listed in the thread is enough or need some more things to unbrick
Click to expand...
Click to collapse
@mannu233 Some more things are required. You can try though with whatever is uploaded. I'm constantly updating the files. I'm working on this day and night. Waiting for @Balaji Sriram to join me soon.
If I replace the "prom_emmc" file in the "blankflash" folder, can I test if flashing works? Thank you!
aravindvnair99 said:
@mannu233 Some more things are required. You can try though with whatever is uploaded. I'm constantly updating the files. I'm working on this day and night. Waiting for @Balaji Sriram to join me soon.
Click to expand...
Click to collapse
cAN you please do me a favour that i wanted to know how to use these files i haven't got any clue how to use them
---------- Post added at 05:19 PM ---------- Previous post was at 05:05 PM ----------
Can someone list up all files whatever is founded in the thread it would be easy for those who are looking for the files
I'm creating this thread to aggregate information in to one location and help anyone out who isn't sure what to do next. I'll be adding to this if and when I can and of course anyone who has anything to add, plz do. This may seem late in the game for some folks, but I'm new to this phone and therefor wanted to help anyone else just picking one up to get familiar with the territory. I have gained SO much from this website over the 7 years I've been here that anything I can give back I'm going to do, and I'm off today with a little time to spare. This won't be overly complicated, and I keep things very simple for ease of use. I'm also aware there are other guides/posts and I will add them to the links as well. This is a small list to start, and will not focus on any one thing, other than making our phones more stable, easier to use and battery efficient. I take no responsibility for anything you may do wth this information, and I take no credit for anything I'm posting here. Links and discussion starting in post 2.
Pixel XL Information Collection - started on 6.1.2018
Swapping Home / Recents Button
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
https://forum.xda-developers.com/pixel-xl/help/swap-recent-button-oreo-t3687721
Root Method: Magisk or Supersu. Magisk 16.4 as of writing
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Bootloader Unlocking: Google Play Store model works a treat, and as of writing, Verizon model now as well thanks to exploit found by XDA member Burduli. - His profile link: https://forum.xda-developers.com/member.php?u=5642246 -
Verizon Bootloader Unlock:
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
APN Settings, including alternative for each. All confirmed working as of writing
https://bestmvno.com/apn-settings/straight-talk-wireless-apn-settings/
Battery Life Threads, including which wake locks to block, greenify options, etc.
https://forum.xda-developers.com/showpost.php?p=60429417&postcount=4
Audio & Battery guide
https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124
Information on IO Schedulers for kernels - I am a huge fan of IO Schedulers and they don't get enough love for what they do
https://androidmodguide.blogspot.com/p/io-schedulers.html?m=1
Guide on how to create your own flashable zip files to flash in TWRP. Confirmed working as of writing
https://goo.gl/zfVGTJ
Camera NX, best camera mod out there. If you're not using this, stop right now and download/install
https://chromloop.com/2018/03/apk-c...camera-5-2-features-bring-back-hdr-nexus2015/
SDK Platform-Tools Stand Alone
https://developer.android.com/studio/releases/platform-tools
How to take a log cat. PLZ read this if you don't know, it's dead simple
https://forum.xda-developers.com/showthread.php?t=1726238
Pixel Beta Downloads
https://developer.android.com/preview/download
Pixel Factory and OTA images
https://developers.google.com/android/images
How to add your APN settings to a ROM if you're on Verizon Wireless and can't edit APN's
https://forum.xda-developers.com/showthread.php?t=2387346
A proper flashing guide, explaining slots A & B
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
Do not EVER RELOCK your bootloader. Here's why.
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Guide on unlocking, flashing images and kernels, etc.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
MTP Windows 10 fix if your phone isn't being recognized by your computer:
https://forum.xda-developers.com/pixel-xl/how-to/guide-fix-mtp-driver-windows-10-t3570625