i would like to know what everything means in htc's bootloader, whats fastboot? and whats does hboot mean, and what does everything thing in the bootloader mean and do? and why do we rename roms to PG05IMG... is that htc's way, like we like to use update.zip in custom recoverys.. thanks
anyone?????????
marcogiudice said:
anyone?????????
Click to expand...
Click to collapse
You're probably not getting a reply because these types of questions have been answered numerous times over the years - and people would probably rather ignore it than be a jerk by saying "ever heard of the search button??". Anyway... jsut Google "ADB for noobs", or "beginners guide to ADB" and you will probably find what you are looking for.
Lipmonger said:
You're probably not getting a reply because these types of questions have been answered numerous times over the years - and people would probably rather ignore it than be a jerk by saying "ever heard of the search button??". Anyway... jsut Google "ADB for noobs", or "beginners guide to ADB" and you will probably find what you are looking for.
Click to expand...
Click to collapse
i see what your saying i did google it before i posted and didnt find what i was looking for, i got adb setup correctly and have been using for it for 16 months but coming across htc bootloader it way different then motos or samsung's with some things in there that would help all the new tb users and should be posted and stickied or in the wiki thread
ok i found half my answer... this for other acquiring minds like me
Here's some (hopefully useful) information about the bootloader:
What's HBOOT?
It's immediately loaded when the phone is switched on. It's mostly responsible for checking and initialising the hardware and starting the phone's software, for flashing official software releases (RUUs via Fastboot), as well as a few other things. In some ways it's comparable to the BIOS on a PC.
How do I root HBOOT?
You can't, it makes no sense. It's a bootloader, not Android. It's like trying to play a DVD on your kettle.
What does upgrading HBOOT do?
It may add extra hardware support for new phones (e.g. SLCD displays) and may fix a few bugs. HTC doesn't release information about it.
What does downgrading HBOOT do?
The opposite. So, if you flash an SLCD phone with an old version of HBOOT that doesn't have the support, the screen won't work.
But rooting depends on HBOOT version?
It doesn't.
Why does upgrading HBOOT remove root?
It doesn't. When you flash an official update your ROM is replaced with an official one, which is why root is lost.
How do I change HBOOT version?
By installing an official RUU/update. There's no other way - the bootloader is protected by the phone's hardware security because a corrupt bootloader means a bricked phone with no way to recover. RUUs contain a version of the bootloader, which is automatically flashed.
Why do I need to downgrade HBOOT to root 0.92?
You don't. You had to downgrade Android because unrevoked3 couldn't root froyo. The new release can, so it works.
Why all the talk about HBOOT then?
Because it is confused with software release, which is the important part. An RUU won't work if the installed software is a higher version (e.g. 1.20.x won't work if you have 1.21.x), and people have mistaken that check for HBOOT version.
What about the xda 0.92 to 0.80 downgrade? It runs on froyo.
It's an engineering/test release from HTC that was leaked. It fakes its software version to 2.09.405.8 so it will run on froyo and downgrade the ROM, so long as you're not on a higher release than that. The process has nothing to do with HBOOT, but it does downgrade the bootloader to 0.80 as a side effect - and results in a dead screen on SLCD phones. It's generally a bad idea to use this hack.
Why would any of this matter?
Because instructions based only on HBOOT version are not reliable. They may not work, or may cause your phone to stop working.
OK NOW FOR FASTBOOT........
Fastboot
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images. It is disabled in the production G1 devices since USB support is disabled in the bootloader[1]. This can be changed if you get root on the device. See also [2]
Fastboot prerequisites
To be able to use fastboot, you need to be running either an ADP1 or the Engineering Bootloader on your G1.
If you are developing on a linux host, you may need to tweak UDEV to recognize the phone in fastboot mode. You may already have done this to get the phone recognized in Eclipse, but you need to do it again for fastboot, since fastboot uses a different device ID: 0bb4:0c01. The warning sign is that fastboot says "< waiting for device >" forever, even when you have the "FASTBOOT" message on the phone; if this happens, try adding the device ID 0bb4:0c01 to your UDEV configuration for Android.
For Opensuse 11.1, the following config file, in /etc/udev/rules.d/11-android.rules, seems to work:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c01", MODE="0666", OWNER="mylogname"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c02", MODE="0666", OWNER="mylogname"
NOTE: change "mylogname" to your Linux login ID. Also note that the product ID bit is optional (probably easier to leave it out), and you need to change "0bb4" to the vendor ID for your phone if it isn't made by HTC (whose vendor ID is 0bb4). You can find the vendor id using 'lsusb'. An alternative to this is just to run fastboot as root, using sudo.
Starting Fastboot
On the G1: To start fastboot, first get to the bootloader: turn off your phone and hold down the "camera" button while powering it back on. You will see a white screen with skateboarding bugdroids. If you just see the normal multicolored bootloader screen, you need to get the device side of fastboot working as noted above. Plug your phone into the usb and if you see "serial0" hit the "back" key. You should now see "fastboot" on the screen.
On the Samsung Galaxy: power down the phone, then long-press the two Call buttons. Beware that fastboot mode will continue to reboot the phone after ~30 seconds of inactivity.
Fastboot Binary
To make use of fastboot, you also need the fastboot program compiled for your host computer. If you have already built Android, you will have this file already. Its location should be:
<android source location>/out/host/{os}_{arch}/bin/fastboot
If you do not have fastboot built, you can either compile the Android source or try DarkriftX's precompiled fastboot (compiled on kubuntu x86)
Fastboot Commands
Here are the commands you can run on your host after fastboot has been started on a device connected via USB. This is a paste directly from the fastboot binary's "--help" command:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
Forcing fastboot to load on every boot
Developers who are creating new images to try out very often can remove their boot and recovery images which will force the phone to enter bootloader mode every time you boot. To fix this, you would reflash the boot and recovery images back allowing the phone to boot normally.
$ fastboot erase boot
$ fastboot erase recovery
NOW,
SO WHY DO WE CHANGE RUU.'S TO PG05IMG??????????
AND THE COUPLE OF OTHER OPTIONS DO IN BOOTLOADER?
THANK U!
I'm guessing it's because that's what it looks for. Kind of like the apply update.zip on stock android recovery. If you notice when you flash, it goes through PG05IMG.X with various file extensions trying to find it and gives a not found error before it finally gets to .zip
PJnc284 said:
I'm guessing it's because that's what it looks for. Kind of like the apply update.zip on stock android recovery. If you notice when you flash, it goes through PG05IMG.X with various file extensions trying to find it and gives a not found error before it finally gets to .zip
Click to expand...
Click to collapse
right, so ok then i was guessing right its like update.zip for stock recovery
thanks
Somewhat of an explanation of our signature checking bootloader can be found here
http://forum.xda-developers.com/showthread.php?t=1008210
Related
Hi all,
So I spent like the whole afternoon tryin to unlock bootloader on my MB860 (rooted) with no luck. This is international version with 2.3.4 system updated OTA.
I tried to unlock bootloader with fastboot - no luck:
Code:
OEM Unlock is not implemented
So i tried flash unlocked sbf file (intl-fix-try1.sbf), still no luck:
Code:
Failed to boot 1
So, I've flashed whole sbf file: 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.20-release-keys-signed-NonEFIGSRetail-EU.sbf
Phone started and all was same as before this operation,
next - I tried another full sbf's:
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31-release-keys-signed-Retail-GB.sbf
1FF-olympus_latam-user-2.3.6-4.5.2A-51_OLL-17.8-111109-release-keys-signed-BellMobility-CA-GAS_NA_OLYMPUSGBCANADABELL_P019.sbf
On both - failed to boot 1
so in the end only sbf that actually allows me to boot my cell is 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.20-release-keys-signed-NonEFIGSRetail-EU.sbf
And the question is - how to get unlocked bootloader for this one?
You really should have searched and read up ahead of time. "Failed to boot XXX" is a perfectly normal and expected thing to happen when unlocking the BL. You shouldn't have messed with any more SBFs. You can still try running the fixer script as mentioned in that thread, hopefully you didn't mess it up too bad.
Thank you ravilov, but isn't this script only for ATT devices?
I am fairly certain it can be used on an international device as well.
Thanks, will try later on today, so what I'm lookin for is this thread:
http://forum.xda-developers.com/showthread.php?t=1182871
and option no.3 is what i should use from this script to have it fixed?
just for the records - the phone is working after i installed only sbf working, all setings and data were not affected, only will need to root it again
stingu said:
so what I'm lookin for is this thread:
http://forum.xda-developers.com/showthread.php?t=1182871
and option no.3 is what i should use from this script to have it fixed?
Click to expand...
Click to collapse
Yes.
stingu said:
just for the records - the phone is working after i installed only sbf working, all setings and data were not affected, only will need to root it again
Click to expand...
Click to collapse
Yeah, that's to be expected.
I think the worst case scenario would be that you won't be able to unlock, in which case you might be one of the unlucky people with the non-unlockable bootloader. If not, this script should help in unlocking your BL.
so, with the script and option number 3 i got the same thing:
Code:
(bootloader) OEM unlock is not implemented
OKAY [ -0.000s]
finished. total time: -0.000s
Or should i first flash small sbf and then use the script?
any other suggestions or am I stuck with soft 2.3.4?
You did flash the pudding/ihop SBF, right? If not, try doing that before you attempt to run oem unlock. If you did already... Well, I'm out of ideas then. I guess while waiting for someone else to chime in, you might as well start mentally preparing that you might indeed stay stuck with the stock firmware.
Well, made it unlocked, it was little bit tricky, so what I did:
-flashed IHOP
-got failed to boot 1 error message again - here, where i was not aware of - I pressed vol up and it switched to fastboot protocol support with boot error present
-did the script, fail to boot error was still there after reboot
-did those 2 points with flashboot application (whole instruction available here http://forum.xda-developers.com/showthread.php?t=1302423):
Code:
13.back in your command prompt window type "fastboot oem unlock" no quotes
14.You will now receive a warning along with a unique device ID
15.Type the following commands using your unique device ID (the numbers in the command prompt) in place of the ####•
fastboot oem unlock ####
fastboot reboot
Now its time to install CWM somehow...
I created a detailed set of step by step instructions for unlocking and rooting the HTC One (M8). This process will work for other HTC models as well, however, obviously I have not tested every phone, and as I have just upgraded to the M8, this process will apply directly to it. I apologize in advance if this steps on anyone's toes, as I will be including download links for specific tools needed. These steps can be found in different threads and guides, but I had not seen one that detailed the entire process from start to finish. Basically, I wrote it in layman's terms so that I was easily able to understand the process. Hopefully this will help anyone having any sort of issues. If anyone feels that this guide is inappropriate, please feel free to delete it, as this is my first "how to"
- Unlocking your AT&T HTC One (M8)
The first thing you will need to do is create a folder labeled "Android". Different guides recommend that you place it on your desktop for easy reference, however, it can actually be placed wherever you wish, as long as you feel confident in navigating to the folder via a command prompt or terminal. For my purposes, I host the folder on my D:\ drive. If you are unable to navigate folders using a command prompt or terminal, Windows 7 and Windows 8 will allow you to right click on a folder and open a command prompt that way.
Downloading the necessary drivers - Drivers can be found by following the link found here:
http://forum.xda-developers.com/showthread.php?t=2019615
CNexus was nice enough to point out that HTC Sync is a lot of bloatware and not required, but can be downloaded if you wish. I opted to download the drivers only. This is a matter of personal preference for me. If you wish to install HTC Sync, then by all means do so.
You will also need to download the ADB/Fastboot files for Windows which can be found here:
ADB/Fastboot files for Windows: https://dl.dropboxusercontent.com/u/1360819/adb-windows.zip
01. Determine if your system is 32-bit or 64-bit and follow the installation instructions for the appropriate software/drivers.
(If drivers have already been installed, then skip this installation step and start with the next).
02. Extract the contents of adb-windows.zip to your "Android" folder.
03. Open a command prompt in, or use a command prompt to browse to the "Android" folder you previously created.
04. On your HTC One (M8) go to Settings > Power, and then uncheck the "Fast Boot" option.
05. Once step 4 is completed, switch your device OFF.
06. Now that the device is powered down, Press the Volume Down and the Power buttons simultaneously to boot the HTC One (M8) into "HBOOT" mode.
07. Using the Volume buttons, navigate to the "Fastboot" option and select it using the Power button.
08. Connect your HTC One (M8) to your PC.
09. On the command prompt you previously opened in step 2, type in the following command "fastboot devices" (do not include the quotation marks).
**At this point, if all steps have been followed properly, you should receive a message in the command window similar to the following:
C:\Users\XXX\Desktop\Android>fastboot devices 011aa0a1a01aaaa1 fastboot
10. Now we will need to go to the HTC Developer website to get an "Identifier Token" before the bootloader can be unlocked. The URL to the HTC Developer website is www.htcdev.com. If you do not already have an account, you will need to register and sign in before you're able to proceed.
11. Once your account has been created and you are logged in, click on the "Development Center" link at the top of the screen.
12. Under the "Unlock Bootloader" option in the center of the page, click on "Get Started".
13. Next, under "Supported Devices" click on "Select your Device" and find the HTC One (M8) and then select "Begin Unlock Bootloader". (This process works for several other HTC devices as well).
14. Accept all warnings and agreements and keep proceeding forward by clicking the "Next" button. When you reach step 8 on the site, enter the following command in the command prompt:
"fastboot oem get_identifier_token" (without the quotation marks).
15. Copy the message seen in the command prompt to notepad or your clipboard.
16. ONLY KEEP THE RANDOM SERIES OF ALPHANUMERICS FROM THE OUTPUT YOU JUST COPIED. Remove everything else such as <<<, (bootloader), Info, or any other piece of text. DO NOT EDIT THE IDENTIFIER TOKEN START OR END LINE!!!
Example:
<<<< Identifier Token Start >>>>
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
<<<<< Identifier Token End >>>>>
17. Paste the edited output inside the "My Device Identifier Token" box on the HTC Developer website and press "Submit". Once you have submitted the identifier token, you will receive your unlock code binary file via email.
18. Upon receiving the "unlock_code.bin" file from HTC (this file is specific to your phone), transfer the file to your "Android" folder that was previously created at the start of this document.
19. With your command prompt still open, enter the following command:
"fastboot flash unlocktoken Unlock_code.bin" (without the quotation marks).
20. After entering this command, a message should appear on your HTC One (M8) screen asking if you really want to unlock the bootloader. Use the Volume key to highlight the YES option and press the Power button to select it.
21. At this point your phone's bootloader will be unlocked and it will restart automatically. The first boot could potentially take some time. If this happens, it is normal. Be patient and wait for the reboot.
22. After your device reboots, any previous settings that you may have saved will be lost with the unlocking of the bootloader. Be prepared for this, as you will need to redo them all. If it is your intention to unlock your bootloader, I highly suggest doing it on a fresh ROM install, so you only have to deal with it once. This means that "fastboot" will be re-enabled in the power settings. If you wish to continue to rooting your device, you will need to go to Settings > Power and un-check the "fastboot" option before proceeding.
- ROOTING YOUR DEVICE
The first thing you will need to do to root your device is to download the following files
TWRP Recovery for the AT&T (M8): http://androidfiles.org/getdownload.php?file=M8/Recoveries/openrecovery-twrp-2.7.0.4-m8_ul_ca.img
SuperSU: download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
1. Once downloaded it is advised to rename the TWRP Recovery file to either "twrp.img" or "m8recovery.img". (I renamed mine to m8recovery).
2. Once renamed, copy TWRP image file into your previously created "Android" folder.
3. Open a command prompt and browse to the same "Android" folder where you placed the adb/fastboot and TWRP Recovery files.
4. Make sure your HTC One (M8) is powered off. Boot the phone into fastboot mode by pressing the Volume down and Power buttons at the same time. Once booted, select "fastboot" by pressing the Power button.
5. Connect the HTC One (M8) to your PC.
6. Enter "fastboot devices" (without the quotation marks) in the command prompt to verify that the device has been detected by your PC. If the device is connected you should receive a message similar to the following:
C:\Users\XXX\Desktop\Android>fastbootdevices
010AA1A0A10AAAA1 fastboot
7. Once verified, type "fastboot flash recovery m8recovery.img" (or whatever you renamed your .img file to and without the quotation marks) in the command prompt and wait for fastboot to flash the TWRP Recovery on your HTC One (M8).
8. After TWRP Recovery has been successfully flashed, the device needs to be restarted manually. To do so, enter the command "fastboot reboot" (without the quotation marks).
9. Upon reboot, transfer the SuperSU zip file to the root directory of your HTC One (M8) via your PC.
10. Turn off your HTC One (M8) and reboot into Bootloader mode by holding the Volume Down and the Power button at the same time.
11. Navigate to the "Recovery" option and select it by pressing the power button. (After following this step, TWRP will load on the device rather than the stock HTC Recovery).
12. Now that TWRP Recovery has loaded, tap the "Install" button and select the UPDATE-SuperSU-v1.94.zip file you previously downloaded.
13. One the SuperSU zip file has been flashed, select the "Reboot System" option to reboot your device.
14. After the device restarts, you have successfully rooted your HTC One (M8). From here, you are now free to install custom Kernels, ROMs, and other mods as you see fit.
I hope this helps everyone out. I am not a developer, nor do I pretend to be. Please give thanks to the people that made all rooting and modding our phones possible
Special thanks to gdnewsevry1 for recognizing a missed step and command.
Very nicely written and well put together. Thank you for taking the time to share this.
Scott
Sent from my HTC One_M8 using XDA Free mobile app
This guide is very well made!
I did figure out that you can root the phone without unlocking the boot loader (with Towelroot modstrings), SOff that way, then just follow your instructions to get TWRP on. You might want to add that in to, for people who don't want to use HTCDev.
suggestion
Thanks for your guide. I just used it and it helped a ton. I would suggest the change and addition below based on my experience.
liquidaluminum said:
TWRP Recovery for the AT&T (M8)
[...]
7. Once verified, type "fastboot flash m8recovery.img" (or whatever you renamed your .img file to and without the quotation marks) in the command prompt and wait for fastboot to flash the TWRP Recovery on your HTC One (M8).
Click to expand...
Click to collapse
7. Once verified, type "fastboot flash recovery m8recovery.img" (or whatever you renamed your .img file to and without the quotation marks) in the command prompt and wait for fastboot to flash the TWRP Recovery on your HTC One (M8).
liquidaluminum said:
9. Upon reboot, transfer the SuperSU zip file to the root directory of your HTC One (M8) via your PC.
10. Turn off your HTC One (M8) and reboot into Bootloader mode by holding the Volume Down and the Power button at the same time.
Click to expand...
Click to collapse
Insert: 9a. Turn off fastboot in settings.
gdnewsevry1 said:
Thanks for your guide. I just used it and it helped a ton. I would suggest the change and addition below based on my experience.
7. Once verified, type "fastboot flash recovery m8recovery.img" (or whatever you renamed your .img file to and without the quotation marks) in the command prompt and wait for fastboot to flash the TWRP Recovery on your HTC One (M8).
Insert: 9a. Turn off fastboot in settings.
Click to expand...
Click to collapse
Good observation. Thank you. I added a line item numbered 22 under the unlocking portion in substitution of 9a. I did it this way, because all settings are reset unlocking the bootloader. For those that are going to proceed to the rooting instructions, I thought it might be smart to go on and take care of disabling the fastboot options right off the bat, so it's no longer a concern.
You were 100% correct about adding the recovery line. I must have missed it while typing this up. Good looking out!
This is almost certainly the best guide I have seen on XDA to unlock/root a device.
I've added it to my Index thread under "Unlock Bootloader, ROOT, S-Off": http://forum.xda-developers.com/showthread.php?p=52653939
Also, one suggestion is to add an alternate section/branch to flash straight to a custom ROM (rather than stay stock and root).
redpoint73 said:
This is almost certainly the best guide I have seen on XDA to unlock/root a device.
I've added it to my Index thread under "Unlock Bootloader, ROOT, S-Off": http://forum.xda-developers.com/showthread.php?p=52653939
Also, one suggestion is to add an alternate section/branch to flash straight to a custom ROM (rather than stay stock and root).
Click to expand...
Click to collapse
I'm definitely thinking about doing that very thing. The only thing that prevented me originally is because of the way I have to use my phone. I've never owned an HTC device before, so I'm not sure if the same issue would exist, but in regards to ROM swapping, when I was running Samsung devices, I found a proprietary problem with the devices themselves that prevented me from running custom ROMs.
I have an Appradio 2 in my car that relies on the MHL output to mirror my device to my dash. When using custom ROMs of any kind (that I tried), I MHL never worked. I addressed the issue with a couple of developers, I was told that because MHL isn't used by many people, support for it isn't focused on. Since that has seemed to hold true for any of the ROMs that I've tried, I've always been limited to rooted stock ROMs. Hence my not including the suggested addition.
I see, it makes sense to write a guide for only what you know about.
I wouldn't necessarily avoid custom ROMs just for the MHL issue. There are a good number of great custom ROMs that are built on the "stock" Sense base, but with varying degrees of optimizations and cool customization options. Its just a gut feel, but with many of these ROMs I would think the MHL function would work fine. In any case, just make a nandroid backup of your current setup (which I highly recommend when flashing just about anything) and if you don't like the current ROM, its easy to revert.
Missing file
Nice writeup, thanks.
FYI, the M8 TWRP link is dead.
I'll see if I can find another. If not, I'll host it somewhere.
About to do this when I get home...
just wanted to know if anything has changed since the last time this was updated. Appreciate the time put into this guide!
Thank you so much. Directions and attatchments worked like a charm. I found another image to use as a recovery since your link was dead. :good:
Great write-up. I'm going to run through this with my new M8. Just one question - can Philz recovery be used with the HTC?
CanuckinPA said:
Just one question - can Philz recovery be used with the HTC?
Click to expand...
Click to collapse
Yes.
If you ever have time..perhaps you should write up a detailed thread about RUUs. There are a few good ones, but most of them written are from guys either stuck on HTC devices or have used android for years. It might knock out the traffic from unnecessary comments on Dev threads. Perhaps letting others know that you can flash RUUs without a computer simply by renaming to 0P6BIMG. AFAIK you can not change CID without access to a computer. I've tried finding out how I can, but I haven't found out anything. I wanted to do a straight GPE conversion considering I never use SENSE based Roms. A few weeks ago my computer crashed, and I figured that idea was out the window til wonder_never_cease told me to rename the file to 0P6BIMG, but to receive OTA updates I'd have to change the CID from SUPERcid to the google gpe CID
---------- Post added at 05:21 AM ---------- Previous post was at 05:20 AM ----------
Isn't philz recovery discontinued ?
hey, thanks for the detailed guide!
do your steps include s-off?
moreover, what is s-off (I am very new to m8) and is it necessary after rooting? what does it provide?
question #2, will I be able to get OTA updates (if I replace TWRP with stock recovery) ?
thanks in advance!
ksoze11 said:
do your steps include s-off?
moreover, what is s-off (I am very new to m8) and is it necessary after rooting? what does it provide?
question #2, will I be able to get OTA updates (if I replace TWRP with stock recovery) ?
Click to expand...
Click to collapse
1) Guide doesn't include s-off. Look for threads/guides on firewater or (more likely) sunshine s-off methods.
S-off is a HTC-specific security flag that means "all security off". S-off isn't required for most root functions, flashing ROMs, etc. Its only needed to flash some protected partitions (hboot, radio), SIM unlock, and a few other things.
S-off also means that things like device check and version check are bypassed. This can sometimes give you more recovery options (for instance "downgrade" by RUU which is not possible with S-on). But it also makes it possible for your to flash mods meant for other devices and possibly brick the phone. So care needs to be taken when s-off, and it shouldn't be taken lightly.
2) You need to be on the stock ROM (with no system files modified) and stock recovery to receive and install OTA. If you have that, it will OTA fine. But you will need to root again afterwards.
Help -- Phone Keeps Rebooting
I went through the entire procedure to unlock and root and all was fine for a week or so until earlier this week.
I'm not sure what I did prior to the problem, but suddenly the phone started rebooting every minute or so. I shut the phone down for a couple of hours, but when I restarted it the rebooting continued.
I booted into Philz recovery and did a restore to stock, reinstalled all of my apps and all was well until this morning. I have Link2SD and after installing Handcent I opened the Link2SD app. Then the reboot returned.
Is there a fix for this issue, or do I have to go back to stock again?
BTW - I haven't flashed a custom ROM yet, still running the stock ATT HTC ROM
CanuckinPA said:
I went through the entire procedure to unlock and root and all was fine for a week or so until earlier this week.
I'm not sure what I did prior to the problem, but suddenly the phone started rebooting every minute or so. I shut the phone down for a couple of hours, but when I restarted it the rebooting continued.
I booted into Philz recovery and did a restore to stock, reinstalled all of my apps and all was well until this morning. I have Link2SD and after installing Handcent I opened the Link2SD app. Then the reboot returned.
Is there a fix for this issue, or do I have to go back to stock again?
BTW - I haven't flashed a custom ROM yet, still running the stock ATT HTC ROM
Click to expand...
Click to collapse
If the phone was working fine for a week, then it must be due to some more recent change made to the phone or app your installed. Did you try to uninstall Link2SD?
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
Problem:
This is the ultimate warning, and you likely don’t want to see this message show up on your screen. Shall this appear, it would mean your device is not safe to use, not trusted and/r corrupted. The OS could still work, but there’s high chances you will encounter performance and security issues.
Consequence:
Before your device begins to start it will be shown:
Android system
There’s an internal problem with your device. Contact your manufacturer for details nexus 6p
Also:
The camera may be no longer properly work
Fixxed:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
mfastboot flash system system.img
reboot bootloader
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastboot reboot-bootloader
fastboot flash vendor vendor.img
Important:
fastboot flashing lock_critical
Enjoy!
@tlip
A couple of notes. You should never advise anyone to flash the userdata.img, it'll result in the minimum commercially available storage size (32gb) being allocated to the device regardless of the actual storage size. So flashing userdata is only compatible with 32gb devices. The correct way to wipe/format the userdata is with this command:
Code:
fastboot format userdata
Also, bootloader reboots are only required after flashing the bootloader and the radio, so the sequence should be like this:
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot
And one more thing, you need to take more care when typing these instructions, you made a few errors, I'll highlight them:
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
[Color=red]m[/color]fastboot flash system system.img [Color=blue](extra m at beginning of command)[/color]
[Color=red]reboot bootloader[/color] [Color=blue](missing "fastboot" prefix, and hyphen between reboot and bootloader (fastboot reboot-bootloader))[/color]
fastboot flash cache cache.img
[Color=red]fastboot flash userdata userdata.img[/color] [color=blue](incorrect command as outlined above)[/color]
[Color=red]fastboot reboot-bootloader[/color] [Color=blue](unnecessary)[/color]
[Color=red]fastboot reboot-bootloader[/color] [Color=blue](another one?)[/color]
fastboot flash vendor vendor.img
I have that message when rebooting. Is this something I should be concerned about? My ignorance had me believing this was a standard screen for all unlocked bootloaders.
sandfreak said:
I have that message when rebooting. Is this something I should be concerned about? My ignorance had me believing this was a standard screen for all unlocked bootloaders.
Click to expand...
Click to collapse
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
EDIT: This info only applies for "Bootloader MAY BE Corrupt" and not "IS Corrupt". Different situation from the OP
Thanked @Heisenberg
Please OP, you give instructions that you expect people to follow and if they type in the wrong info could be fatal...
Seriously, this thread needs closed asap. All the above info( besides Heisenberg) is careless in itself, let alone posting it for others. Stop....just stop. Smh
Heisenberg said:
@tlip
A couple of notes. You should never advise anyone to flash the userdata.img, it'll result in the minimum commercially available storage size (32gb) being allocated to the device regardless of the actual storage size. So flashing userdata is only compatible with 32gb devices. The correct way to wipe/format the userdata is with this command:
Click to expand...
Click to collapse
I have for sure made this mistake before... One lesson learned the hard way
Dissmeister said:
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
Click to expand...
Click to collapse
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
CNLiberal said:
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
Click to expand...
Click to collapse
That's exactly right, locking the bootloader means you can't flash anything to the device.
CNLiberal said:
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
Click to expand...
Click to collapse
Your post made me google this and I did find some people who did have issues like that, though they mention they cant unlock again. If this is what you're talking about, I'd say its a device specific issue; technically as far as Nexus (or correct flashing protocol) is concerned, you should be able to unlock and re-lock as you see fit. As Heisenberg mentioned, you cant flash anything on a locked b/l in the first place.
Personally I've never seen a reason to relock b/l after unlock but it depends on your circumstances.
Dissmeister said:
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
Click to expand...
Click to collapse
Actually if it says your bootloader may be corrupt which is normal. If it says your bootloader is corrupt that's bad. It can say Two different things. He said the second one
dontbeweakvato said:
Actually if it says your bootloader may be corrupt which is normal. If it says your bootloader is corrupt that's bad. It can say Two different things. He said the second one
Click to expand...
Click to collapse
That is one hell of a silly mistake. You're right, I apologize for not seeing that earlier. Will fix my previous reply so others dont get the wrong info from it. Thanks for that :good:
Dissmeister said:
Your post made me google this and I did find some people who did have issues like that, though they mention they cant unlock again. If this is what you're talking about, I'd say its a device specific issue; technically as far as Nexus (or correct flashing protocol) is concerned, you should be able to unlock and re-lock as you see fit. As Heisenberg mentioned, you cant flash anything on a locked b/l in the first place.
Personally I've never seen a reason to relock b/l after unlock but it depends on your circumstances.
Click to expand...
Click to collapse
The way I understood it, after I re-lock then need to unlock again, the phone will force a wipe. The old app Unlock Bootloder would lock and unlock in Android. You wouldn't have to reboot. I guess the developer believes that the new 6P can't perform this same function due to the nature of new locking/unlocking.
Hi Heisenberg,
as being rather new to the topic of unlocking and stuff that means, that I have to follow this (your) sequence for not running into that issue?
Does this hold true also for already having this problem, though?
Cheers, Rovaine
Rovaine said:
Hi Heisenberg,
as being rather new to the topic of unlocking and stuff that means, that I have to follow this (your) sequence for not running into that issue?
Does this hold true also for already having this problem, though?
Cheers, Rovaine
Click to expand...
Click to collapse
This "guide" is very poorly written, don't follow the instructions here. If you need instructions you can visit my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
As long as you're careful and follow my instructions properly you shouldn't haven't this problem.
Heisenberg said:
This "guide" is very poorly written, don't follow the instructions here. If you need instructions you can visit my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
As long as you're careful and follow my instructions properly you shouldn't haven't this problem.
Click to expand...
Click to collapse
Actually, I've tried to follow your guide to the point, but did -obviously- something wrong, hence this issue.
You've got any advice for starting all over -propperly- for getting rid of this issue?
I had this issue too after having "dirty flashed" Android 6.0.1 over Android 6.0.
I flashed system.img and boot.img, as usual through fastboot and never had any problems on "older" devices.
On my Nexus 6P I got this error too and the camera did not work. Having checked the logs I found the error.
You need to flash vendor.img too in order to fix it. You don´t have to relock your bootloader.
Gorgtech said:
I had this issue too after having "dirty flashed" Android 6.0.1 over Android 6.0.
I flashed system.img and boot.img, as usual through fastboot and never had any problems on "older" devices.
On my Nexus 6P I got this error too and the camera did not work. Having checked the logs I found the error.
You need to flash vendor.img too in order to fix it. You don´t have to relock your bootloader.
Click to expand...
Click to collapse
Just for getting it straight...
Initial situation:
Rooted device, latest Cyanoge installed, showing the described issue
How to solve:
Get angler-xxxxxx-factory-xxxxxxxx, unzip ...
"fastboot flash vendor C:\angler\images\vendor.img"
Gratulation issue solved?
Or do I have to get back to a certain state, like factory image fully restored or alike, of my device?
Exactly, you need the latest Factory Image for the Nexus 6P. Extract all content and only flash the vendor.img through fastboot.
Rovaine said:
Just for getting it straight...
Initial situation:
Rooted device, latest Cyanoge installed, showing the described issue
How to solve:
Get angler-xxxxxx-factory-xxxxxxxx, unzip ...
"fastboot flash vendor C:\angler\images\vendor.img"
Gratulation issue solved?
Or do I have to get back to a certain state, like factory image fully restored or alike, of my device?
Click to expand...
Click to collapse
Rovaine said:
Actually, I've tried to follow your guide to the point, but did -obviously- something wrong, hence this issue.
You've got any advice for starting all over -propperly- for getting rid of this issue?
Click to expand...
Click to collapse
Flash the factory images, instructions are in my guide.
I had did a wrong boot.img flash and now fastboot is gone. I just want to verify that fastboot was actually located somewhere inside the boot.img.
Side notes..... I have a phone now that doesnt power on cuz the preloader is cooked by flashing that boot.img. If you try to charge the phone ,the battery charging icon does not show so that means I hard bricked phone.
lextacy said:
I had did a wrong boot.img flash and now fastboot is gone. I just want to verify that fastboot was actually located somewhere inside the boot.img.
Side notes..... I have a phone now that doesnt power on cuz the preloader is cooked by flashing that boot.img. If you try to charge the phone ,the battery charging icon does not show so that means I hard bricked phone.
Click to expand...
Click to collapse
Fastboot doesn't actually reside on the phone it is a communication protocol used to flash the specific partitions of the phones layout. Specifically fastboot itself is just a binary (.bin on OS X and Linux and .exe on windows) used to communicate with the fastboot protocol. Correct me if I'm wrong but what I'm guessing what you did is you meant to flash a boot.img to the boot partition and instead you flashed that to the bootloader/preloader partition erasing the bootloader. There is a flag when the bootloader is complied that allows the bootloader to have support for fastboot. Your best bet is to to try and find a factory image for your phone to try and re-flash the stock bootloader through fastboot. A second option is find a friend who has the same phone model as you and that is rooted, then dump there bootloader using terminal emulator or a similar app, transfer it to your computer and then flash it using fastboot. If you have any more questions or just want some more clarification on what I said feel free to ask more then happy to help !
shimp208 said:
Fastboot doesn't actually reside on the phone it is a communication protocol used to flash the specific partitions of the phones layout. Specifically fastboot itself is just a binary (.bin on OS X and Linux and .exe on windows) used to communicate with the fastboot protocol. Correct me if I'm wrong but what I'm guessing what you did is you meant to flash a boot.img to the boot partition and instead you flashed that to the bootloader/preloader partition erasing the bootloader. There is a flag when the bootloader is complied that allows the bootloader to have support for fastboot. Your best bet is to to try and find a factory image for your phone to try and re-flash the stock bootloader through fastboot. A second option is find a friend who has the same phone model as you and that is rooted, then dump there bootloader using terminal emulator or a similar app, transfer it to your computer and then flash it using fastboot. If you have any more questions or just want some more clarification on what I said feel free to ask more then happy to help !
Click to expand...
Click to collapse
Good info here , I did not know that fastboot was outside the android environments. The command I ran was "fastboot flash boot boot.img" if that makes sence. This was on a chinese smartphone that has a chinese only text bootloader. So no other friends will have this phone where I can grab an image from. I ordered a new phone (surprise , surprise right? ) haha , BUT I would still like to get this brick working for learning purposes and root practice.
lextacy said:
Good info here , I did not know that fastboot was outside the android environments. The command I ran was "fastboot flash boot boot.img" if that makes sence. This was on a chinese smartphone that has a chinese only text bootloader. So no other friends will have this phone where I can grab an image from. I ordered a new phone (surprise , surprise right? ) haha , BUT I would still like to get this brick working for learning purposes and root practice.
Click to expand...
Click to collapse
Glad I could help you out ! It must be a bad boot image then that you flashed, but that shouldn't prevent you from accessing the bootloader. When you get your new phone and root it you should be able to pull that stock boot image and then get your old phone working again. As always any questions let me know !
So fastboot doesn't reside in the phone?
I understand that it's a protocol, but how does the phone know to act like a server for the PC fastboot client?
Where does the phone load the protocol rules from?
Can fastboot mode run even without any partition on the phone?
If so the phone would be virtually unbrickable.
I'm just trying to understand.
JackSlaterIV said:
So fastboot doesn't reside in the phone?
I understand that it's a protocol, but how does the phone know to act like a server for the PC fastboot client?
Where does the phone load the protocol rules from?
Can fastboot mode run even without any partition on the phone?
If so the phone would be virtually unbrickable.
I'm just trying to understand.
Click to expand...
Click to collapse
Perhaps the best way to understand how fastboot works is to take a look at it's source code found here https://android.googlesource.com/platform/system/core/+/master/fastboot/fastboot_protocol.txt and the general fastboot code here https://android.googlesource.com/platform/system/core/+/master/fastboot. Let me know if you still have questions.
shimp208 said:
Perhaps the best way to understand how fastboot works is to take a look at it's source code found here https://android.googlesource.com/platform/system/core/+/master/fastboot/fastboot_protocol.txt and the general fastboot code here https://android.googlesource.com/platform/system/core/+/master/fastboot. Let me know if you still have questions.
Click to expand...
Click to collapse
Thanks, I saw but there is no answer there.
I just got the phone and couldn't resist the temptation to start the shenanigans. I actually flashed an image into both slots and wanted to delete the duplicate image in slot b.
My thinking was that since modem_b was empty before I flashed anything to it, then I probably could safely erase everything with the suffix _b right?
No, and now my phone is bricked. I should also mention that I forgot to set the active slot back to "a" so that was probably a contributing cause.
However when I look at how fastboot flashes the bootloader, I notice that it only touches the partitions with _b. So does that mean that my _a bootloader is intact?\
In the future, I'll only erase the partitions that the factory rom actually rewrites. And I am not touching the bootloader anymore, unless we get an msmtool equivalent for the Tensor chip. Speaking of which, I noticed that when the bricked phone is connected to my computer, it shows up as a serial device.
I am in the process of filing a claim with Google so I still have a few days to figure this out.
Is there something wrong with the how to guides in the Pixel 6 threads?
No, it was just me screwing around with the partitions. I did successfully root the phone previously.
How did you manage to wipe the bootloader partition? "dd" command? Pretty hard core if that was the case.
I rooted the phone and rooted the shell. So when I went to adb shell, I was able to cat /dev/block/bootdevice to see all the partition names.
From then on I just used the fastboot erase command.
In the back of my head, I though that fastboot unlock_critical being disabled would save me from doing stupid things but in retrospect it was probably only to prevent overwriting the bootloader.
I see. Amazing to think that Google would allow erasing the bootloader with a simple fastboot command.
And yet the bootloader on the other slot remains intact. With no way to enter fastboot to switch slots, it seems a replacement is the only option.
Be careful what you tell them if you go for a RMA
In the Pixel 6 Pro forum there is an unbricking guide which uses the exynos dead recovery to start flashboot and then using it to reflash the bootloader. If as you said the phone shows up as com port there should be hope.
Kickbub said:
I rooted the phone and rooted the shell. So when I went to adb shell, I was able to cat /dev/block/bootdevice to see all the partition names.
From then on I just used the fastboot erase command.
In the back of my head, I though that fastboot unlock_critical being disabled would save me from doing stupid things but in retrospect it was probably only to prevent overwriting the bootloader.
Click to expand...
Click to collapse
The unlock_critical command is automatically executed when you unlock the bootloader with the standard command. It's been that way since midway through the Pixel 2 XL lifespan.
Google should be able to make you whole.
Which command do you use, i type cat /dev/block/bootdevice in su mode
it only come out cat: /dev/block/bootdevice: Is a directory.
after knew the partition just use fastboot erase (directory) to wipe it?