Develop Bugs

Need help, Error flashing HTC one m8 stock rom

Hello friends,
I have tried downloading following ROMS RUU and each rom gives same error, whats wrong? what should I do to fix this?
roms i have tried so far
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ERROR i get every time with these roms
Current ROM Version is 2.23.502, ( RUU reads 2.23.502.3 as current IMAGE version)
Hardware: m8_ul_ca
MID: 0P6B12000
Thank you for reading.

Did u chnge it to international version
Sent from my HTC One_M8 using Tapatalk

manish dubey said:
Did u chnge it to international version
Click to expand...
Click to collapse
According to his statements (on the MID and version) it appears that NO, he did not change to international version.
But I agree, we need more info to be sure. OP should do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
Or just try a different PC. RUU freezing while sending is common, and usually nothing to do with the phone. Win7 and USB 2.0 (not USB 3.0) for the best possibility for RUU to succeed.

And error 155 usually referring to bootloader not relocked when device is S-On

ckpv5 said:
And error 155 usually referring to bootloader not relocked when device is S-On
Click to expand...
Click to collapse
Ahh, I missed that. I looked at the screenshot too quickly!

hello guys,
thanks for replies,
below is more info you asked for
-- The phone is going in TWRP because previously, i tried to install a custom ROM [ i forgot which one ]
-- Phone is stuck at htc one boot splash screen
-- if i reset phone by twrp, then after it gets boot up and then i get 'UNFORTUNATE ERROR' and then again it gets restarted and get stuck in htc boot splash screen
-- i am trying to flash ruu in windows 10.1, should I try windows 7 32bit?
Thank you

You don't read what people said above.
1. you need to relock bootloader to run a RUU because you have a S-On device.
command : fastboot oem lock
then reboot bootloader/fastboot
2. run RUU while on bootloader/fastboot
What you need :
A Windows PC with USB2.0 (I never have problem running RUU on Win 10 64 bit)
Latest HTC USB drivers installed - install HTC Sync Manager as it will install the drivers and some needed Microsoft Visual C++ Redistributable files
then uninstall HTC Sync Manager but leave other things.
http://www.htc.com/us/support/software/htc-sync-manager.aspx
You also can directly install the latest RUU - http://www.htc.com/us/support/htc-one-m8-att/news/ instead of the old version

Administr4tor said:
below is more info you asked for
Click to expand...
Click to collapse
This is not what was asked for. This doesn't tell us much we didn't already know. Aside from confirming that your bootloader is unlocked, and you are s-on.
The proper advice was already given in Post #5 above. You need to relock the bootloader with the following command, in order to RUU: fastboot oem lock

alright, sorry I didnt pay attention,
now when I try to run command "adb devices", I dont see any devices though the device is perfectly installed in windows device manager as " my htc"
also this the screen which i get when I try to turn the phone on

Administr4tor said:
now when I try to run command "adb devices", I dont see any devices though the device is perfectly installed in windows device manager as " my htc"
also this the screen which i get when I try to turn the phone on
Click to expand...
Click to collapse
You don't need to run an adb command, you need a fastboot command. Fastboot and adb are related, but very different things:
adb will never run unless in OS or recovery. What you are seeing (adb not connecting) is normal.
Fastboot commands require the phone to be in bootloader-fastboot mode (which you are in during the pic in Post #7 above).

Thank you very much, it worked, problem solv3d

Update 4.4.4 to marshmallow

Hello,
My uncle gave me his htc one M8 and for some days now I've been trying to factory reset it and update from 4.4.4 to latest android version with no success. Everytime I try to factory reset (from settings or fastboot or pc with ruu) it fails everytime. It doesn't delete music and gallery (deletes apps and settings though) and the update notification never shows up. I'm sorry if the solution is on another thread but I haven't found anything during these days. I live in Balkan so the phone isn't linked with any carrier (bought in a regular store).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

specs
specs

you can update by flashing verizon stock mm ruu.
1) at first update hboot. https://www.androidfilehost.com/?fid=24438995911975644
2) then flash ruu. https://www.androidfilehost.com/?fid=24438995911973442
go to this thread for future support. http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845

umesh.lk said:
you can update by flashing verizon stock mm ruu.
1) at first update hboot. https://www.androidfilehost.com/?fid=24438995911975644
2) then flash ruu. https://www.androidfilehost.com/?fid=24438995911973442
go to this thread for future support. http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
Do I need microSD for this? Because I don't have one

ergi2468 said:
Do I need microSD for this? Because I don't have one
Click to expand...
Click to collapse
you don't need micro sd. you can flash by fastboot commands. use the following files for fastboot binaries. copy the files which you downloaded to fastboot folder.
1) go to fastboot usb mode
2) fastboot oem rebootRUU
3) fastboot flash zip hboot file name.zip
4) fastboot reboot-bootloader
5) fastboot oem rebootRUU
6) htc_fastboot flash zip ruu file name.zip

Delete (obscure) IMEI and serial number from the screenshot. These are personal info, and should not be posted online.

umesh.lk said:
you don't need micro sd. you can flash by fastboot commands. use the following files for fastboot binaries. copy the files which you downloaded to fastboot folder.
1) go to fastboot usb mode
2) fastboot oem rebootRUU
3) fastboot flash zip hboot file name.zip
4) fastboot reboot-bootloader
5) fastboot oem rebootRUU
6) htc_fastboot flash zip ruu file name.zip
Click to expand...
Click to collapse
error cannot load hboot.zip
error preprocess file cannot open ruu.zip

umesh.lk said:
you don't need micro sd. you can flash by fastboot commands. use the following files for fastboot binaries. copy the files which you downloaded to fastboot folder.
1) go to fastboot usb mode
2) fastboot oem rebootRUU
3) fastboot flash zip hboot file name.zip
4) fastboot reboot-bootloader
5) fastboot oem rebootRUU
6) htc_fastboot flash zip ruu file name.zip
Click to expand...
Click to collapse
error cannot load hboot.zip
error preprocess file cannot open ruu.zip

ergi2468 said:
error cannot load hboot.zip
error preprocess file cannot open ruu.zip
Click to expand...
Click to collapse
my bad there working on it

umesh.lk said:
you don't need micro sd. you can flash by fastboot commands. use the following files for fastboot binaries. copy the files which you downloaded to fastboot folder.
1) go to fastboot usb mode
2) fastboot oem rebootRUU
3) fastboot flash zip hboot file name.zip
4) fastboot reboot-bootloader
5) fastboot oem rebootRUU
6) htc_fastboot flash zip ruu file name.zip
Click to expand...
Click to collapse
ok Everything working fine except a little sim sign with ? on status bar. I can call though so not a problem. Thank You for your help

ergi2468 said:
ok Everything working fine except a little sim sign with ? on status bar. I can call though so not a problem. Thank You for your help
Click to expand...
Click to collapse
there is a method to remove sim icon. (sku id changing) but it may be a headache for you. try that. I fixed that on LP. but I haven't changed on MM. I think it will work. All the Best!
http://forum.xda-developers.com/showthread.php?t=2594804

umesh.lk said:
you can update by flashing verizon stock mm ruu.
1) at first update hboot. https://www.androidfilehost.com/?fid=24438995911975644
2) then flash ruu. https://www.androidfilehost.com/?fid=24438995911973442
go to this thread for future support. http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
So it was fine until I arrived on campus where I rely on my data plan. Mobile hotspot doesn't work. It just says error but I assume it is because of the verizon rom. Is there a way to fix this? I think a global unlocked rom should work since the cid:111111

ergi2468 said:
So it was fine until I arrived on campus where I rely on my data plan. Mobile hotspot doesn't work. It just says error but I assume it is because of the verizon rom. Is there a way to fix this? I think a global unlocked rom should work since the cid:111111
Click to expand...
Click to collapse
did you fix sim icon?
it's different to say something about hotspot. i haven't used hotspot in verizon. what is the error? is device rooted? it may not work hotspot as a bug came after root.
i belive there may no bugs in verizon stock roms.
you have superCID. but didn't forget that MID is 0P6B20000 (M8_WLV). your device is a limited one. but can be used globally.
*) if your firmware is 6.21.605.3, didn't downgrade or change it.
*) don't change mid. ( there are hardware changes than M8_UL) device may get bricked.
*) try verizon custom rom. but there may be hidden bugs. http://forum.xda-developers.com/verizon-htc-one-m8/development
after few days, as a user you can understand that stock rom is better at all costs.

umesh.lk said:
did you fix sim icon?
it's different to say something about hotspot. i haven't used hotspot in verizon. what is the error? is device rooted? it may not work hotspot as a bug came after root.
i belive there may no bugs in verizon stock roms.
you have superCID. but didn't forget that MID is 0P6B20000 (M8_WLV). your device is a limited one. but can be used globally.
*) if your firmware is 6.21.605.3, didn't downgrade or change it.
*) don't change mid. ( there are hardware changes than M8_UL) device may get bricked.
*) try verizon custom rom. but there may be hidden bugs. http://forum.xda-developers.com/verizon-htc-one-m8/development
after few days, as a user you can understand that stock rom is better at all costs.
Click to expand...
Click to collapse
No I didn't fix sim icon, didn't downgrade, didn't root, nothing. I am pretty sure it's a sim problem. Will allowing root acces bypass the verizon check and create a hotspot?

ergi2468 said:
No I didn't fix sim icon, didn't downgrade, didn't root, nothing. I am pretty sure it's a sim problem. Will allowing root acces bypass the verizon check and create a hotspot?
Click to expand...
Click to collapse
We can't think that root access will allow to create hotspot. use this custom rom. there may be a chance to create a hotspot. http://forum.xda-developers.com/ver...t/rom-nusenseven-marshmallow-sense-7-t3266678.
it is difficult to reply you today again as this is my bed time.

umesh.lk said:
did you fix sim icon?
it's different to say something about hotspot. i haven't used hotspot in verizon. what is the error? is device rooted? it may not work hotspot as a bug came after root.
i belive there may no bugs in verizon stock roms.
you have superCID. but didn't forget that MID is 0P6B20000 (M8_WLV). your device is a limited one. but can be used globally.
*) if your firmware is 6.21.605.3, didn't downgrade or change it.
*) don't change mid. ( there are hardware changes than M8_UL) device may get bricked.
*) try verizon custom rom. but there may be hidden bugs. http://forum.xda-developers.com/verizon-htc-one-m8/development
after few days, as a user you can understand that stock rom is better at all costs.
Click to expand...
Click to collapse
Also I can't even usb tether

ergi2468 said:
I am pretty sure it's a sim problem. Will allowing root acces bypass the verizon check and create a hotspot?
Click to expand...
Click to collapse
Nope. Root is just a permissions change, that allows the users access to modify certain things. It doesn't really modify anything in itself.
Your best bet if you need WiFi hotspot or tethering, is to flash a custom ROM that supports the Verizon version.

wrong hboot flashed!!! (blackrose nexuse one)

hey guys,
i flashed blackrose (nexuse one hboot) and after it, i can't flash another hboot. say "only blackrose can be flashed"
so i run ruu GB 2.3.3 , that's failed
and now stuck in ruu mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what can i do to solve this problem???
help me step by step

LOL I did this too.
If your desire loads an OS
http://forum.xda-developers.com/showthread.php?t=1460035
Connect to your PC with debugging
Run nexus blackrose on your PC
run from command prompt with command 'blackrose skip'
you should get menu
select disable hboot protection
- You should get message about be careful and phone restarts to fastboot
Flash alpharevs bravo_alphaspl.img and you should be good to go
You MAY be able to flash bravo_alphaspl.img over the blackrose hboot without running the PC end of blackrose - but I ended up disabling blackrose hboot protection using the nexus PC blackrose frontend
You MAY find its partly trashed your recovery - so you may need to re-install whatever you have for recovery.
I believe to run ruu you need to have full htc sync installed (and probably goldcard) the opposite of everything else.

no os installed!
Robcr said:
LOL I did this too.
If your desire loads an OS
http://forum.xda-developers.com/showthread.php?t=1460035
Connect to your PC with debugging
Run nexus blackrose on your PC
run from command prompt with command 'blackrose skip'
you should get menu
select disable hboot protection
- You should get message about be careful and phone restarts to fastboot
Flash alpharevs bravo_alphaspl.img and you should be good to go
You MAY be able to flash bravo_alphaspl.img over the blackrose hboot without running the PC end of blackrose - but I ended up disabling blackrose hboot protection using the nexus PC blackrose frontend
You MAY find its partly trashed your recovery - so you may need to re-install whatever you have for recovery.
I believe to run ruu you need to have full htc sync installed (and probably goldcard) the opposite of everything else.
Click to expand...
Click to collapse
no os installed !! just stuck in ruu mode.
"Run nexus blackrose on your PC" where is link download blackrose files???

Then i doubt you can do anything about changing your hboot until you have
Just concentrate on getting a working rom installed, i would suggest cm-7.2.0.1-bravo
To do that you may need to get a working recovery I couldn't get fastboot to install pretty much anything in that state.
See my recent posts on this including an older 'working' but faulty 4ext via PB99IMG.zip (dont clear any sd partitions with this - just use it to load a rom then update via 4ext app)
First step try the 'clear storage' (with no sd-card in) option from bootloader
If after that still nothing, and you have no recovery,
try the following which ended up the omly way I could get a working recovery installed:
http://forum.xda-developers.com/showpost.php?p=29427407&postcount=17
to get a working recoverr installed but DONT clear the ext partitions using this, just use it to load a rom then update the 4ext version using the 4ext updater apk

View attachment 4024581
Robcr said:
Then i doubt you can do anything about changing your hboot until you have
Just concentrate on getting a working rom installed, i would suggest cm-7.2.0.1-bravo
To do that you may need to get a working recovery I couldn't get fastboot to install pretty much anything in that state.
See my recent posts on this including an older 'working' but faulty 4ext via PB99IMG.zip (dont clear any sd partitions with this - just use it to load a rom then update via 4ext app)
First step try the 'clear storage' (with no sd-card in) option from bootloader
If after that still nothing, and you have no recovery,
try the following which ended up the omly way I could get a working recovery installed:
http://forum.xda-developers.com/showpost.php?p=29427407&postcount=17
to get a working recoverr installed but DONT clear the ext partitions using this, just use it to load a rom then update the 4ext version using the 4ext updater apk
Click to expand...
Click to collapse
I couldn't do anything. So i research in xda and learn some fastboot command. I used this command to go to the recovery:
"fastboot boot recovery.img"
And then i flashed cm-7.2.0.1-bravo. After flashed, i rebooted to system but i faced ruu mode stuck again!!!!
So i type this command:
"fastboot boot boot.img"
Device Loads system and now:
When i try to open blackrose.exe, i face with this error: (Attached screenshot)
"Failed to check device model"
What should i do now????

glassofwiskey said:
View attachment 4024581
I couldn't do anything. So i research in xda and learn some fastboot command. I used this command to go to the recovery:
"fastboot boot recovery.img"
And then i flashed cm-7.2.0.1-bravo. After flashed, i rebooted to system but i faced ruu mode stuck again!!!!
So i type this command:
"fastboot boot boot.img"
Device Loads system and now:
When i try to open blackrose.exe, i face with this error: (Attached screenshot)
"Failed to check device model"
What should i do now????
Click to expand...
Click to collapse
Anyone??? Help

Help! HTC One M8 (Rogers Canada) Bricked?

/Users/sekhon/Desktop/Brick Phone.jpg
Hi,
My HTC M8 (which i have not used for a year) seems to have been cricked to what ever extent !
I put it on charge and the following shows up
________________________________________
*** Software status: Modified ***
*** Locked ***
M8_UL PVT Ship S-ON
(few other lines)
FastBOOT AC
<vol up. to previous item>
<vol down> to next item>
<power> to select item
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
no matter what i do it just ends up here and doesn't really startup,
I had aSD Card in the phone and removed it and tried to restart but no luck!
Any help would be highly appreciated !

saint4mbuddapest said:
no matter what i do it just ends up here and doesn't really startup,
Click to expand...
Click to collapse
So what did you try to do? The above doesn't tell us anything you tried or didn't try (aside from removing the SD card).
Don't want to waste the time and effort, to advise you to do things you may have already tried.

Hello,
Thanks for the reply!
I tried to connect it to my mac via usb to flash a rom or twrp etc but my computer doesn't show the phone.
I tried selecting the recovery mode from the menus and nothing happens.
It just restarts and goes back to the same mode.
So honestly i havnt tried much as i do not know where to begin.. Apart from going into all of the menus on the screen and that's it.
I think i the phone is missing the recovery and the rom? Not sure.... Help!

saint4mbuddapest said:
I tried to connect it to my mac via usb to flash a rom or twrp etc but my computer doesn't show the phone.
Click to expand...
Click to collapse
The mac will only be able to connect via fastboot, in the current condition. Do you have fastboot/adb setup on your mac? I'm not a mac user, so I won't be able to advise much on that.
saint4mbuddapest said:
I think i the phone is missing the recovery and the rom? Not sure.... Help!
Click to expand...
Click to collapse
Since the phone will only boot to bootloader, you are correct in that it appears the ROM is damaged or corrupt. Since I don't think the Rogers version has RUU to recover, you are right in the approach of flashing TWRP and ROM to the phone.
However, you will also need to unlock the bootloader, in order to flash TWRP. And you will need working fastboot connection to mac/PC in order to unlock bootloader and flash TWRP. So you really need to troubleshoot the connection issue, first.
You might also read through the following thread for more recovery options or info: https://forum.xda-developers.com/showthread.php?t=2694297

redpoint73 said:
Since I don't think the Rogers version has RUU to recover
Click to expand...
Click to collapse
On post #1 OP wrote (few other lines) which is important to be highlighted. Without OS info no way to help.
Or as usual need fastboot getvar all result. If it is Lollipop RUU 4.20.631.3 is available for free.
Also I remember Marshmallow RUU is available too on AFH but can't confirm it now as I maybe wrong ..need to search for it
Edit : here is Marshmallow RUU - http://gsm-firmware.com/index.php?a=browse&b=file-info&id=14070
Leave it to you to guide OP.
Maybe need to flash 6.13.631.7 firmware first before RUU

Thanks!
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone. So far all posts and videos i have found explain about trouble shooting when the phone OS is still running but none for my situation.
There is a red highlights text which says "FASTBOOT"
and it turns to "FASTBOOT USB" when i plug in with my MAC
Also i have tried 2 different USB cables same result, tried clicking on the "REBOOT FASTBOOT" as well same result.
Anything else i can do to have a working connection ?
redpoint73 said:
The mac will only be able to connect via fastboot, in the current condition. Do you have fastboot/adb setup on your mac? I'm not a mac user, so I won't be able to advise much on that.
Since the phone will only boot to bootloader, you are correct in that it appears the ROM is damaged or corrupt. Since I don't think the Rogers version has RUU to recover, you are right in the approach of flashing TWRP and ROM to the phone.
However, you will also need to unlock the bootloader, in order to flash TWRP. And you will need working fastboot connection to mac/PC in order to unlock bootloader and flash TWRP. So you really need to troubleshoot the connection issue, first.
You might also read through the following thread for more recovery options or info: https://forum.xda-developers.com/showthread.php?t=2694297
Click to expand...
Click to collapse

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
http://i65.tinypic.com/254x8g0.jpg
<img src="http://i65.tinypic.com/254x8g0.jpg" border="0" alt="Image and video hosting by TinyPic">

saint4mbuddapest said:
Thanks!
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone. So far all posts and videos i have found explain about trouble shooting when the phone OS is still running but none for my situation.
There is a red highlights text which says "FASTBOOT"
and it turns to "FASTBOOT USB" when i plug in with my MAC
Also i have tried 2 different USB cables same result, tried clicking on the "REBOOT FASTBOOT" as well same result.
Anything else i can do to have a working connection ?
Click to expand...
Click to collapse
Have you installed the HTC drivers to your computer?
If not, install HTC Sync Manager (you can get the MAC version here). During the installation of Sync Manager the drivers will be installed. After they are, Uninstall Sync Manager (it doesn't play nice with ADB/fastboot) and the drivers will remain

xunholyx said:
Have you installed the HTC drivers to your computer?
If not, install HTC Sync Manager (you can get the MAC version here). During the installation of Sync Manager the drivers will be installed. After they are, Uninstall Sync Manager (it doesn't play nice with ADB/fastboot) and the drivers will remain
Click to expand...
Click to collapse
Just tried that as well, no improvement

saint4mbuddapest said:
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone.
Anything else i can do to have a working connection ?
Click to expand...
Click to collapse
When on fastboot, correct command is fastboot devices or ./fastboot devices
Based on your bootloader screenshot, you can try the above linked RUU to fix your phone

saint4mbuddapest said:
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone. So far all posts and videos i have found explain about trouble shooting when the phone OS is still running but none for my situation.
There is a red highlights text which says "FASTBOOT"
and it turns to "FASTBOOT USB" when i plug in with my MAC
Click to expand...
Click to collapse
This is working normally, and as intended.
adb and fastboot are related, but different conditions, usage and requirements.
adb: Only works in OS, or alternately TWRP. Needs debugging enabled in phone settings. Will not work in fastboot mode.
fastboot: Only works in fastboot mode. Does not require debugging enabled in phone settings.
Stuck in fastboot mode, you should get a response (phone's ID) to: fastboot devices
Otherwise, there may be a driver or USB connectivity issue.
However, since ckpv5 linked an RUU for you to use, the mac won't help you. RUU is probably the easiest way to get the phone back up and running. But you'll need access to a PC for the RUU to work. RUU won't work properly with mac, even emulating a PC.

redpoint73 said:
However, since ckpv5 linked an RUU for you to use, the mac won't help you. RUU is probably the easiest way to get the phone back up and running. But you'll need access to a PC for the RUU to work. RUU won't work properly with mac, even emulating a PC.
Click to expand...
Click to collapse
It's zip format, can use microsd method

ckpv5 said:
It's zip format, can use microsd method
Click to expand...
Click to collapse
Nice. :good: Obviously, I missed that detail. Should have figures, since most M8 versions without "official" released RUUs seem to get them leaked as zip format.

Question Android 13 and unlocked bootloader

Hello,
Fist, I will say it, I am a total newbie in rooting. So, I followed one of the excellent guides here. Little by little, I begin to understand the process. So I have succeeded to root my pixel 6 pro using magisk.
Then, Android 13 has come. I think, pretty sure, that the bootloader need to be locked again to update. At least, I tried, I removed magisk and so the root, but the update fails.
Then I have reset the phone. Now I try to lock again the bootloader. However, withadb reboot bootloader, I cannot see the phone. fastboot devices shows nothing.
fastboot flashing lock stay on <waiting for any device>
Then I tried adb reboot fastboot. Here, the phone is found when I type fastboot devices. However fastboot flashing lock displays:
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
Click to expand...
Click to collapse
So, my questions:
1.) do I really need to lock the bootloader to update to android 13 ?
2.) what did I do as mistake ? I want to understand, especially if one day I need to sell the phone, I want to be able to lock again the bootloader. Is fastboot flashing lock the right command ?

Ralendil said:
Hello,
Fist, I will say it, I am a total newbie in rooting. So, I followed one of the excellent guides here. Little by little, I begin to understand the process. So I have succeeded to root my pixel 6 pro using magisk.
Then, Android 13 has come. I think, pretty sure, that the bootloader need to be locked again to update. At least, I tried, I removed magisk and so the root, but the update fails.
Then I have reset the phone. Now I try to lock again the bootloader. However, withadb reboot bootloader, I cannot see the phone. fastboot devices shows nothing.
fastboot flashing lock stay on <waiting for any device>
Then I tried adb reboot fastboot. Here, the phone is found when I type fastboot devices. However fastboot flashing lock displays:
So, my questions:
1.) do I really need to lock the bootloader to update to android 13 ?
2.) what did I do as mistake ? I want to understand, especially if one day I need to sell the phone, I want to be able to lock again the bootloader. Is fastboot flashing lock the right command ?
Click to expand...
Click to collapse
You don't need to do all of that to upgrade to android 13. You can read how to upgrade to android 13 here: https://forum.xda-developers.com/t/...-6-pro-bootloader-central-repository.4352027/
as well as here: https://forum.xda-developers.com/t/pixel-6-pro-easy-step-by-step-unlock-root-update.4361847/
it is a long thread with a lot of information, so I'll just give you an adlibbed version of how to upgrade
I read that you have removed root. You can re-root after upgrading. Make sure your bootloader is unlocked first.
First make sure you have the latest sdk platform tools version here: https://developer.android.com/studio/releases/platform-tools
Download the android 13 factory image here: https://developers.google.com/android/images
Extract the platform tools and the factory image, and make sure the flash-all.bat file is in the same location as adb.exe and fastboot.exe
If you want to keep your data, do this. If you don't want to lose your data and don't mind wiping your phone, skip this step and just run flash-all.bat in fastboot.
Edit the flash-all.bat file and remove the -w flag from the
Code:
fastboot update -w image-raven-tp1a.220624.021.zip
command. So it'll just be
Code:
fastboot update image-raven-tp1a.220624.021.zip
Save it, edit again just to double check that -w flag is gone. If it is, reboot your phone back into fastboot and run flash-all.bat.
It'll upgrade and do everything for you. You're on Android 13 now and your data is still intact.
Once your phone is booted, you can patch the boot image from the factory image you downloaded with Magisk and flash it in fastboot again by doing fastboot flash boot --slot=all (drag and drop patched boot.img here) OR type in the file name magisk_patched-xxxxxxxxxx.img. Then you will have root.
If you want to go back to complete factory with a locked bootloader, run Android Flash Tool from Google here: https://flash.android.com/welcome?continue=/back-to-public
Make sure "Wipe Device", "Lock Bootloader", and "Force Flash All Partitions" are checked.

You could always try the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). It's possible you could also take advantage of it's new option to flash only the 13 bootloader to both slots, and then will update the current slot to 13 completely.
Lughnasadh said:
FYI: Even though Android Flash Tool does not flash the whole image to both slots, they have added an option to flash the A13 bootloader to the inactive slot. This may be the easiest option to use when updating to A13 from A12.
Just to be clear, when updating to A13 from A12 a prompt will show up asking whether you want to also flash the bootloader to the inactive slot as well. It doesn't show up in the regular tick boxes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
FYI, you most definitely didn't need to re-lock the bootloader. Also, a pro tip for rooters. Once you unlock a device's bootloader, never ever re-lock it except in very rare circumstances. This didn't count as rare before you consult us.

I would have loved that it would be a solution.
It would allow me only to install android 12... and locking the bootloader make me affraid… I think I will never be able to unlock it cause I can’t use bootloader (see under)
For now, I try to make bootloader drivers working.
Every time I reboot to bootloader, the phone is not recognized by the computer and no adb/fastboot command can be used. So, I cannot use the flash-all.bat script.
Also, now when I use adb reboot fastboot the fastboot screen appears, then bootloader is loaded immediately...
I can’t believe I will spend several hours to be able to install that… I am stuck.
I tried to uninstall several drivers and reinstall drivers, but no changes... or yes a change. Now it is worst, Pixel 6 pro isn’t listed in device manager, and adb bootloader driver has disapear replaced by an adb driver line. Anyways, bootloader driver was never activated.
Edit: I should add that the update through the phone doesn’t work.
Don’t know why... the interface for google android flash tool changed... and now I was able to choose the version and I could flash the two slot with a13 bootloader.
Thanks for the idea...
Even if… I would love to understand why I did not succeed to install it...
Final edit: Android 13 has been successfully installed
Now, time to root it