Related
I got the s-off files from xda and had no problems with turning it off. i then used the superoneclick method to root my HTC Aria running the OTA 2.2.2 att update. my phone is rooted, i have superuser and all is good..... except that when i try to go into recovery mode to install a custom rom it just gives me a failure screen of a phone and a red triangle with a red exclamation point in it. i have to take the battery out to reset the phone.
why wont it let me into recovery?
if anyone has some insight for me it would be greatly appreciated.
thank u
AlphaRevX doesn't install recovery automatically for you, but once you have S-OFF you can do it yourself. This post tells you what to do:
http://forum.xda-developers.com/showthread.php?t=1122694
thanks for the quick response.
i downloaded all the files (to windows computer) then extracted files. then i went and put my phone into fastboot usb.
i guess im getting confused on the next step. it says to fastboot flash recovery <recovery.img> from a command line <----- (not sure what the command line is)
i know about phones and apps but am just getting into roms and rooting.
sorry for having a blonde moment
Start > Run > Type "cmd"
Then from command prompt do:
Code:
cd C:\path\to\folder
fastboot flash recovery recovery.img
(replace C:\path\to\folder with the place you extracted the files)
I know there are other threads out there that offer exactly what this does, but even with those, I think it can still be a bit tricky to figure out what to do if you're looking to root and modify your phone. I made this thread to collect everything I've done in one place. This should make everything very straightforward and basically n00b-proof.
I take no credit for any of this work. Please thank all the hardworking devs!
**Following all of these steps will WIPE all data from your phone. Backup before beginning. While these should all be safe, there's always the possibility of bricking your phone. I take no responsibility if you do.**
What you'll need:
USB Cable
USB port
HTC Droid DNA (without the OTA update!)
PC running Windows
Glass of Orange Juice (for the Vitamin C!)
**All of this shouldn't take more than 30 minutes but just in case, make sure your phone has at least a 70% charge.**
Preparing (Installing SDK, Setting PATH, testing ADB)
I highly recommend creating a directory on the root of your C: drive on your PC to hold ALL related files. I called mine "android" but you can call yours whatever you'd like. Whenever issuing any ADB command, make sure you navigate to this folder first.
1. Connect your phone to your computer. One of the pop ups will ask to install HTC Sync. Install this to install the drivers onto your computer. Once installed, you can go into your Add/Remove Programs and uninstall the HTC Sync software if you want.
2. Enable USB Debugging in your HTC Droid DNA from the path “Settings > Applications > Development > USB debugging”. The option of USB Debugging should be ticked.
2. Download the latest version of the Android SDK to your PC here.
3. Extract the files to your PC (I recommend something easy like C:\android)
4. Run the SDK Manager and uncheck everything but the Platform Tools and install
5. Add the SDK tools to your system PATH file by doing the following:1. Simultaneously hold down the Windows Key + R
2. type 'sysdm.cpl' into the run dialogue box and click OK
3. On the system properties window that just opened, click on the 'advanced' tab. Then click on 'Environment Variables'
4. Scroll down through the System variables until you find the PATH. Click 'Edit', then add ';C:\android' (or whatever you named your folder) to the end of the line
5. Click OK and close the open windows.6. Test ADB by connecting your phone to your PC then:1. Open a new command prompt window by pressing Windows+R and typing "cmd" into the box
2. Type 'adb devices' and press enter. You should see your phone's UID listed.
If it says adb devices is not a recognizable command then you didn't setup your PATH correctly
If it says <waiting for device> then your missing the drivers or you didn't enable USB debugging. Try rebooting, and if it still doesn't show, reinstall HTC sync.
Other Tips
You can download all the files necessary at the beginning and do everything through ADB.
Always check the MD5-hash after downloading a file. If they don't match, the download is corrupt and you should try again. I use this simply tiny, no-install MD5 checker.
Always Test after each install to ensure it is working properly. Don't just string all of these together without rebooting once. Bad things might happen and you'd have no idea what's causing it.
You can reboot your phone into the bootloader by either issuing the command "adb reboot bootloader" or pressing and holding the PWR and VOL DN buttons simultaneously when you reboot your phone.
From the bootloader you can enter recovery or you can issue the command "adb reboot recovery"
If your command prompt hangs pressing Ctrl+C will break out of the running command.
Some useful command prompt (DOS) commands:
cd - change directory (ie. 'cd C:\android' will change to the 'C:\android' directory)
cd .. - moves up one directory level
dir /p - lists files within the current directory
Unlocking Bootloader
The next step is to unlock the bootloader. The best method right now is provided by jcase. NOTE: Don't install the OTA update or you won't be able to do this!Step 1: Get SuperCID
Full instructions can be found here.
1. Download .apk from link above.
2. Run the app
3. Run the following Commands via ADB
Code:
adb reboot bootloader
(wait for phone to reboot into bootloader)
fastboot oem readcid
If you see 22222222 you're good to proceed. If you see anything else, reboot the phone and try again.
Step 2: Unlock via HTC Dev site
Go to the HTC Developer website and carefully follow the instructions. They're very straight forward.
When completed you'll have unlocked the bootloader. You'll see a new warning on the splash screen and the bootloader will say *tampered* at the top.Install Custom Recovery
You can choose either ClockworkMod (my preference) or TWRP recoveries.
1. Download the latest version of your preferred recovery. rename it "recovery.img"
2. Using ADB issue the following commands
Code:
adb reboot bootloader
(once the phone reboots into the bootloader)
fastboot flash recovery recovery.img
(once installation is complete)
fastboot reboot
Now you'll have a custom recovery, and can make a full nandroid backup (recommended!).
S-OFF
Full instructions can be found here. beaups did an excellent job writing this up so it would be pointless for me to reproduce here.
Root / Custom ROM
Choose any ROM you'd like. I prefer Team Venom's ViperDNA. I'll use that as the basis for the next steps.
1. Download the full ROM found in the second post in the above link to your phone.
2. Reboot into recovery
3. Select "install zip from sdcard" and choose the ROM .zip file mentioned above. Follow the instructions on screen.
Note: If you choose a different ROM make sure it either includes a kernel that supports system write or you have to install one first by doing the following. Also, if you have WiFi issues after flashing the ROM follow these steps to reinstall the kernel.Installing the Kernel
1. Download a Kernel (such as dsb's Cubed Kernel)
2. Unzip the file and copy the modules.zip file to your phone.
3. Via ADB issue the following commands:
Code:
adb reboot bootloader
(once rebooted)
fastboot flash boot boot.img
(once complete)
fastboot reboot recovery
The phone will reboot into recovery, at which point you should flash the modules.zipENG HBOOT
This is *Optional* and allows for additional ADB commands to be used.
1. Download the HBOOT-8064 file found here. (thanks to fnoji111 and Argumentation)
2. Via ADB issue the following commands:
Code:
adb reboot bootloader
(once rebooted)
fastboot oem rebootRUU
(once rebooted to the black HTC screen)
fastboot flash zip PL83IMG.zip
(once complete)
fastboot reboot
Mods
These are some mods I found to be essential.Remove the Splash Screen disclaimer
Full instructions can be found here.
1. Go to the above link and download the RegawMOD tool (first post) AND the Droid DNA ENG Hboot plugin (2nd post).
2. Make sure the plugin is in the same folder as the tool.
3. Customize it how you'd like. I chose to replace the disclaimer with my own, that basically reads
If Found, Please Return to
*Drumz0rz*
*My Home Phone Number*
Click to expand...
Click to collapse
4. When you're finished press "Create ZIP" and save the file.
5. Via ADB issue the following commands:
Code:
adb reboot bootloader
(once rebooted)
fastboot oem rebootRUU
(once rebooted to black HTC screen)
fastboot flash zip <YourZipName>.zip
(once complete)
fastboot reboot
Now you should have a fully unlocked S-OFF custom ROM, custom Kernel, HBOOT Droid DNA! I hope this helps!
Will this method work for new ota ?
Sent from my HTC6435LVW using xda premium
No, it's just a summary of what's out there. When someone releases a new method to unlock the bootloader I'll update it.
Thank you, when I rooted using the guide linked from one of the sticky posts most of the links were dead, so it is nice to have this.
One suggestion - perhaps include the steps to finish up for those that want to stay on stock rom but be rooted.
drumz0rz said:
No, it's just a summary of what's out there. When someone releases a new method to unlock the bootloader I'll update it.
Click to expand...
Click to collapse
Thanks def look forward to that
Sent from my HTC6435LVW using xda premium
Thanks! Having these steps in a simple guide saved me a good bit of time.
Minor confusion on "Installing the Kernal". I extracted Cubed.Stock.System.Write.zip, flashed boot.img, then flashed Modules.zip in recovery. From the guide, does renaming the package to boot.img work as well?
Lastly, I'm not sure if you want to include flashing/loading ViperDNA's OTA updates.
Is there a way to factory reset phone and eliminate OTA update? I'm assuming no but never hurts to ask....
Sent from my HTC6435LVW using xda app-developers app
John58543 said:
Is there a way to factory reset phone and eliminate OTA update? I'm assuming no but never hurts to ask....
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
No
Sent from my HTC6435LVW using xda app-developers app
steventrev said:
Thanks! Having these steps in a simple guide saved me a good bit of time.
Minor confusion on "Installing the Kernal". I extracted Cubed.Stock.System.Write.zip, flashed boot.img, then flashed Modules.zip in recovery. From the guide, does renaming the package to boot.img work as well?
Lastly, I'm not sure if you want to include flashing/loading ViperDNA's OTA updates.
Click to expand...
Click to collapse
As in renaming the zip? No, you need to do what you said, I left out the flashing the modules. I'll fix that, thanks.
Detailed guide, one question what if you don't have orange juice and want to use Gatorade as a substitute?
Sent from my HTC6435LVW
I'm no nutritionist but I think those two serve very different purposes. Now if you want to substitute it for a glass of say whiskey... that I think is more than acceptable.
ok so i have an htc one on att and i had a sysem uid problem, so i wiped everything icluding the internal storage. now there is no OS installed and i have a mac and htc file transfer wont pick up the phone in recovery mode. how do i install the stock sense rom and put it back on my phone? try to answer immediately cuz i need this for tomorrow
You need to get the proper drivers installed to sideload a new rom or push it to internal sd
My best advice would be to drop the mac for linux or even windows, but that's a different story...
Sent from my SGH-T699 using Tapatalk 2
tristannhowes said:
ok so i have an htc one on att and i had a sysem uid problem, so i wiped everything icluding the internal storage. now there is no OS installed and i have a mac and htc file transfer wont pick up the phone in recovery mode. how do i install the stock sense rom and put it back on my phone? try to answer immediately cuz i need this for tomorrow
Click to expand...
Click to collapse
If you don't have access to a windows PC, you'll probably have to do it similar to this way - http://forum.xda-developers.com/showthread.php?p=26435416 (Download the RUU for your device).
Sent from my Nexus 4
except it doesnt have mac on there and it says to turn fastboot off in settings using the os and i cant. anything else?
Can't you copy/paste the stock rom into the device and boot it up to install? In my huawei I think I can do it with the special "pink screen" (turning on my phone while pressing both volume up and down ). If I have a "dload" folder in the root directory with the stock rom inside, when booting to pink screen it will automatically start the installation..
tristannhowes said:
except it doesnt have mac on there and it says to turn fastboot off in settings using the os and i cant. anything else?
Click to expand...
Click to collapse
Just find the right RUU for your device and execute it (Let it extract the files and go to your temp folder / Don't close the application).
For example if you are using Win7/Win8:
Go to C:\Users\{your username}\AppData\Local\Temp\
You will see some folder(s) with a name like this or similar with an other folder inside it with similar name (path example):
C:\Users\{your username}\AppData\Local\Temp\{487C5E56-F40F-49D7-A913-522D1A257374}\{50F2F878-636A-496F-A7CB-544C067E0C4B}
If you find the right one you will be able to find a file with name rom.zip.
just copy that to the root of your sdcard and rename it to {your MID namber / the 4 first characters}IMG.zip
For example for Incredible S should be PG32IMG.zip
The zip name with your MID number could be PL83IMG.zip (Probably for HTC One)
***Important***
If you want to find your MID number to rename the zip you should get your phone into hboot (by pressing Vol- and power button) and to enable fastboot mode (connect the usb cable to your computer).
Then give the command:
fastboot getvar mid ----> To get your Model ID number
fastboot getvar cid ----> To get your CID number (it could help you to find the right RUU for your device / If you have S-OFF and SuperCID you can Install any RUU but you should be carefull - If you choose some wrong RUU and you flash it you could brick your device as well)
***Attention***
Make sure you haven't sdcard into your phone if you have your XXXXIMG.zip inside because you won't be able to use fastboot option.
As long as you have the right zip with the right name in your sdcard reboot your phone into bootloader (while you have sdcard inside).It will start to scan your sdcard.If the zip has the right name your hboot will find the XXXXIMG.zip and it will tell you to update.Press VOL+ button to start the proccess (VOL- to abort).Wait until proccess is done.May it take a while...
(Don't put off your battery until the process is done and make sure it is at least 30% charged to proceed.)
If you need any help further we are here.
The problem with the above is the htc one does not have a removeable sd and the op's computer isn't recogonizing his phone, the first step is to get the phone and pc to communicate, after this, being the recovery is functional, just a full wipe and install of a proper rom via recovery will suffice, no need to flash an ruu or pcxxximg.zip
Just needs to load a rom to internal sd
Sent from my SGH-T699 using Tapatalk 2
Im glad I have an external sdcard.. When I got it was just with the thinking "I can expand storage", but apparently it has this great advantages as well.
In the HTC maybe you can boot into a special mode that makes the computer recognize the internal partitions and mount them as external drives..
Good luck.
You could use fastboot commands to restore official rom to your device without the need of sdcard.You just need to extract the rom.zip from RUU.exe.
Here is a guide how to extract an RUU on linux and mac:
OpenRUU for Linux & Mac - NEW! Extract rom.zip from any RUU!
**You need wine to run windows executable files (.exe) under linux and mac OS.**
If you have the rom.zip you can flash it using fastboot commands:
fastboot oem rebootRUU ---> Get your phone into RUU mode.
fastboot flash zip rom.zip ---> Flash the rom.zip you extracted before.
fastboot reboot ---> Run this command when the flashing is finished.
The proccess should has been done now!
You could see this guide to if you like:
[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!)
Yes using fastboot is helpful, but in this case again, the op needs to get his phone and pc to communicate first before doing anything. And applying an ruu is overkill,
Get phone to connect to pc
Load proper rom on phone internal sd
Wipe clean through recovery
Flash rom (and gapps if needed)
Reboot
Profit
Sent from my SGH-T699 using Tapatalk 2
Hello everyone. I have a T-Mobile HTC One M7. I had Viper One installed on it and then decided to restore it to stock, and ship it to my lill bro in Europe. I accidentally wiped the whole system on the phone. Now it shows:
***Tampered***
***Relocked***
***Security Warning***
and I can only get into the bootloader and recovery modes. I am a noob when it comes to this. PLease help me put a stock system on my phone!!
Thank you much!!!
Shtehla said:
Hello everyone. I have a T-Mobile HTC One M7. I had Viper One installed on it and then decided to restore it to stock, and ship it to my lill bro in Europe. I accidentally wiped the whole system on the phone. Now it shows:
***Tampered***
***Relocked***
***Security Warning***
and I can only get into the bootloader and recovery modes. I am a noob when it comes to this. PLease help me put a stock system on my phone!!
Thank you much!!!
Click to expand...
Click to collapse
This is the latest RUU for your phone. Just follow the instructions on the page. The "Security Warning" may go away but the other two will more than likely remain.
Rom update utility gives me low battery error
I downloaded the RUU from the link u gave me. I made sure there's a usb driver in place, for my htc one. When i start the rom update thing, and i go through the "agree" and check boxes....the rom utility gives me error 120, saying that my main battery power is low (less than %30), though my phone is fully charged and my laptop is fully charged.... Please advice
Got past the battery error message
Shtehla said:
I downloaded the RUU from the link u gave me. I made sure there's a usb driver in place, for my htc one. When i start the rom update thing, and i go through the "agree" and check boxes....the rom utility gives me error 120, saying that my main battery power is low (less than %30), though my phone is fully charged and my laptop is fully charged.... Please advice
Click to expand...
Click to collapse
now I cant go past error 170 within the RUU instalation process... can figure out how to get past that...
Shtehla said:
now I cant go past error 170 within the RUU instalation process... can figure out how to get past that...
Click to expand...
Click to collapse
Try this process for getting past error 170. If this doesn't work then try this procedure:
Start the RUU.EXE, it will creat a temporary directory in %TEMP%, and within that folder you will find a 1GB+ file called ROM.ZIP <- this is the full ruu.zip which you can flash using fastboot.
After starting the RUU.EXE, when it's on the first screen, in Windows Explorer type %TEMP% in the location box that will jump you to the folder, sort by date modified, and find the newest folder within that, it's going to have a weird long alpha numeric name, and within that you'll find plenty of files, but one very large file called ROM.ZIP, that's the one you want.
Copy rom.zip into your fastboot/adb folder.
At this point just Cancel and quit out of the ROM Update Utility.
Open a command window in your fastboot/adb folder and
Go to your bootloader. Type:
Code:
adb reboot bootloader
Type:
Code:
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time.
Code:
fastboot flash zip rom.zip
Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
Now, you can reboot. Type:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
I get an error right when getting to the step to flash ROM unto phone.
Start the RUU.EXE, it will creat a temporary directory in %TEMP%, and within that folder you will find a 1GB+ file called ROM.ZIP <- this is the full ruu.zip which you can flash using fastboot.
After starting the RUU.EXE, when it's on the first screen, in Windows Explorer type %TEMP% in the location box that will jump you to the folder, sort by date modified, and find the newest folder within that, it's going to have a weird long alpha numeric name, and within that you'll find plenty of files, but one very large file called ROM.ZIP, that's the one you want.
Copy rom.zip into your fastboot/adb folder.
At this point just Cancel and quit out of the ROM Update Utility.
Open a command window in your fastboot/adb folder and
Go to your bootloader. Type:
Code:
adb reboot bootloader
Type:
Code:
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time.
Code:
fastboot flash zip rom.zip
Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
Now, you can reboot. Type:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
[/QUOTE]
I follow the steps just fine, and I get to step "fastboot flash zip rom.zip" and it gives me an error. see file attached
Shtehla said:
Start the RUU.EXE, it will creat a temporary directory in %TEMP%, and within that folder you will find a 1GB+ file called ROM.ZIP <- this is the full ruu.zip which you can flash using fastboot.
After starting the RUU.EXE, when it's on the first screen, in Windows Explorer type %TEMP% in the location box that will jump you to the folder, sort by date modified, and find the newest folder within that, it's going to have a weird long alpha numeric name, and within that you'll find plenty of files, but one very large file called ROM.ZIP, that's the one you want.
Copy rom.zip into your fastboot/adb folder.
At this point just Cancel and quit out of the ROM Update Utility.
Open a command window in your fastboot/adb folder and
Go to your bootloader. Type:
Code:
adb reboot bootloader
Type:
Code:
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time.
Code:
fastboot flash zip rom.zip
Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
Now, you can reboot. Type:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
Click to expand...
Click to collapse
I follow the steps just fine, and I get to step "fastboot flash zip rom.zip" and it gives me an error. see file attached[/QUOTE]Could you post a fastboot getvar all (except for imei and serialno)? Also, open up the rom.zip and post the contents of the android-info.txt file. Were there two rom.zip files?
Here's teh getvar all results
majmoz said:
[/HIDE]
there was only one zip file.
Click to expand...
Click to collapse
Here's what I get when trying to open the rom.zip
See attachement
Shtehla said:
See attachement
Click to expand...
Click to collapse
Let try the RUU 5.14.531.1 it is the next one up from your version.
I relocked the bootloader
majmoz said:
If you remember I had my bootloader relocked through oem relock. I did unlock it yesterday, would that make a difference in the whole process?
Not it says ***tempered*** and ***unlocked*** on the top of the screen.
Click to expand...
Click to collapse
Shtehla said:
majmoz said:
If you remember I had my bootloader relocked through oem relock. I did unlock it yesterday, would that make a difference in the whole process?
Not it says ***tempered*** and ***unlocked*** on the top of the screen.
Click to expand...
Click to collapse
Yes, since you are S-ON your bootloader needs to be locked/relocked to run RUU and OTA.
Click to expand...
Click to collapse
Here's what I get
majmoz said:
Let try the RUU 514.531.1 it is the next one up from your version.
Click to expand...
Click to collapse
when I flash the ruu it starts with the same message, but then it continues and has a finish. Not the one I need I gues. See attachement.
after i started RUU to create the ROM file in TEMP, it did create 2 rom files (rom_01, rom_02) the rom_02 was the 1.5gb one, and I renamed it to "rom.zip" and i continued with original instructions....
P.S thank you for helping me
Shtehla said:
when I flash the ruu it starts with the same message, but then it continues and has a finish. Not the one I need I gues. See attachement.
after i started RUU to create the ROM file in TEMP, it did create 2 rom files (rom_01, rom_02) the rom_02 was the 1.5gb one, and I renamed it to "rom.zip" and i continued with original instructions....
P.S thank you for helping me
Click to expand...
Click to collapse
Did you try the 5.14.531.1 RUU.exe?
Yes I did.
majmoz said:
Did you try the 5.14.531.1 RUU.exe?
Click to expand...
Click to collapse
Those are the results with this new ruu
Shtehla said:
Those are the results with this new ruu
Click to expand...
Click to collapse
Did you try it as a windows executable file not as a rom.zip?
Yep
majmoz said:
Did you try it as a windows executable file not as a rom.zip?
Click to expand...
Click to collapse
the exe file creates the rom zip. I didn't touch the zip, except i copied it in the fastboot folder
Shtehla said:
the exe file creates the rom zip. I didn't touch the zip, except i copied it in the fastboot folder
Click to expand...
Click to collapse
Yes, I know you pull the rom zip out of the %TEMP% folder. Did you Cancel the update in Windows or did you select Next to allow it to continue?
I
majmoz said:
Yes, I know you pull the rom zip out of the %TEMP% folder. Did you Cancel the update in Windows or did you select Next to allow it to continue?
Click to expand...
Click to collapse
I canceled it, after I copied the rom.zip from temp into fastboot folder.
Shtehla said:
I canceled it, after I copied the rom.zip from temp into fastboot folder.
Click to expand...
Click to collapse
Try to run it completely through in Windows.
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622
Download: https://dl.twrp.me/blueline/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
GitHub: https://github.com/topjohnwu/Magisk/releases
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
Was my misunderstanding. I thought you were implying people should go back to stock recovery to flash ota. You are talking about flashing ota in twrp. You might clear that up a little bit in that section.
Great post.
Unfortunately, if you are writing a process, then writing everything out is a requirement. Especially with item numbers or using an outline format. Not everyone understands shortcuts taken or abbreviated words, unless they are spelled out in the beginning. IMO, wrote and read too many processes. Including software requirement documentation.
Hi,
thanks for the thread :good:
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
Yes, I think so too.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
The boot.img is into "image.zip"
Then I suggest to flash into a and b (or both)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
or
fastboot flash boot --slot all boot.img
Edit
be careful here: Factory reset via ADB sideload (can also do this without wiping data)
bootloader is bootloader, boot is boot, bootloader.img isn't boot.img
so, maybe better to write:
fastboot flash bootloader nameofbootloader.img or if simply renamed fastboot flash bootloader bootloader.img
deleted, bug.
trouble flashing files
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
wangdaning said:
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
Click to expand...
Click to collapse
Thanks, but still no luck.
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
fyrmd said:
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
Click to expand...
Click to collapse
I always buy Anker cables and chargers. All have been good so far.
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
Are you able to get into recovery? If so, download the full ota to your pc and side load it with adb.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
i same issue
rczrider said:
[*]Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Click to expand...
Click to collapse
why not copy all files?
---------- Post added at 11:58 AM ---------- Previous post was at 11:55 AM ----------
fyrmd said:
Thanks, but still no luck.
Click to expand...
Click to collapse
boot to the twrp.img and flash the twrp.zip, unless you are on android 10 you should have no problem unless you are doing it wrong. not exactly hard to do.
How to enable oem unlock in this case?
pedro5148 said:
How to enable oem unlock in this case?
Click to expand...
Click to collapse
There are a few suggestions at https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
However, if the network carrier has locked the bootloader, you cannot unlock it. In the U.S., Verizon and AT&T phones generally cannot be unlocked due to locked bootloaders.