Develop Bugs

HTC One M8 Rooting and S-Off Guide for Newbies (US/International)

Welcome to the HTC One M8 S-Off GUIDE FOR NEWBIES!​
Disclaimer:​I am not responsible for any damage to your phone, in part, or in whole; including bad SD cards, broken reception, bad wifi, Windows 8 being installed, or anything else that could go wrong: Bricking, Bootloops, blips, beeps, boops, or sweeps. You chose to follow these instructions on your own accord and if you do so, agree that I am not liable in anyway, shape or form.
What Models/Carries Should this Work for?
USA: ATT, TMobile
European: Tmobile, VodaFone
I'm unsure if all of this works for Verizon/Sprint versions. You'll have to check the Toolkit's thread and the Firewater thread or official site for confirmation. The above models are just what I've read on the forums)
Credits:
Hansoon2000 for the HTC One Toolkit
Shrimp208 for Minimal ADB and Fastoot
Beups and Fuses for Firewater​.
Ok, so, you want to achieve Root/S-Off and its many benefits. I'm going to walk you through what I did to make this process fairly simple.
Requirements:
HTC One M8
Windows 7, 8, 8.1
No Lockscreen on your phone.
Developer Options Enabled with the following:
1. USB Debugging Enabled
2. Allow Mock Locations (this may not be necessary, but I always do it just in case)
Hint: Don't know how to enable developer options? Go to Settings>About>Software Information>More and tap on "Build Number" 7 times. This will open Developer Options in the Settings menu.
Let's Root!​Use the All-In-One toolkit here:
http://forum.xda-developers.com/showthread.php?t=2699065
Process:
When you open the ToolKit, you'll notice lots of little boxes with text inside. We're going to focus on the box at the very top left that says "To root the phone, follow in order." Fairly simple, right?
First, Download and install HTC Sync Manager and make sure it sees your One M8. Do not use the Install Drivers option from the toolkit, they're outdated/don't work for most people. HTC Sync will install the latest driver for the M8. You can then uninstall the HTC Sync Manager program itself. Link: http://www.htc.com/www/software/htc-sync-manager/
Register at HTCDev. This is needed for this process to gain permaroot at the time I write this. If it doesn't allow you to register, either use a different email address, or ask a friend to do this.
Once logged in, go to "Unlock Bootloader" and Select HTC One (M8) from the drop down list. Follow the steps/prompts and directions on the site.
Get Token ID. Plug your phone in to a USB 2.0 port on your PC (not a hub, not USB3.0, USB 2.0). You should be notified that the HTC One M8 has been plugged in. If so, Proceed. If not, you'll have to figure out the issues you're having with the drivers first.
Two windows will Pop Up. Hit close on the First Window.
The second window should pop up with text. Your token ID is a long series of alpha-numeric text. This is an example of everything you should copy:
{
"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"
}
Note: Copy ALL off that text. From the <<<<Identifier Token Start down to Identifier Token End>>>>
Now, Take that copied text and submit it at HTCDev where it asks you to. If it's successful and you've copied what you need to, an Unlock_Code file will be emailed to you. Download and Place this file in the HTC One Toolkit's Data folder.
Unlcok Bootloader: Again, two windows will pop up, close the first. Your Phone should reboot and the token ID Applied. Your phone will ask you if you want to proceed. Hit Volume Up for "Yes" and Power Button to confirm. This might take a minute, don't freak out.
Flash a Recovery. Once your phone is booted back to the Home screen, go to the far right top window and Select TWRP as the recovery. Select Flash Recovery. Your phone will again pop up with two windows, close the first, and let it do it's thing. Reboot back into the Recovery after this is all done.
Flash Supersu. Go into "Install" in TWRP and select "SuperSu" from the list, swype to begin process.
Congratulations, you should now be rooted!
Time to S-Off!​
WARNING: Not all devices are supported by Firewater. There's really no way to tell until you start running the process to S-Off. If Firewater tells you that your device is not compatible, then it's not compatible. You'll have to wait until Firewater does support your device and is updated.
REQUIRMENTS:
ROOTED HTC ONE M8
ADB and HTC Drivers (htc drivers should be installed from Rooting)
Developer Options Enabled with the following:
1. USB Debugging Enabled
2. Allow Mock Locations (this may not be necessary, but I always do it just in case)
Hint: Don't know how to enable developer options? Go to Settings>About>Software Information>More and tap on "Build Number" 7 times. This will open Developer Options in the Settings menu.
Don't have ADB and don't know where to start? Then download and install MINIMAL ADB AND FASTBOOT:
http://forum.xda-developers.com/showthread.php?t=2317790
Once Downloaded and installed, go to your Start window on the PC and search "ADB". Minimal ADB and Fastboot (here on referred to as ADB) will show up, click on it to bring up a Command Prompt. Using Admin Rights isn't a bad idea either when using ADB.
Go to http://firewater-soff.com/instructions/ And make sure you Follow the Prerequisits to the letter! Read the Instructions for "Rooted, Normal Device Method"
Now that you have the Firewater file, go to Start and Search for ADB, RIGHT CLICK and choose SHOW FILE LOCATION. Drop your Firewater file here. Now we can begin!
Process:
Connect your phone to a USB 2.0 Port if you already haven't and make sure your phone is on the Home screen with NO LOCKSCREEN OF ANY SORT
In the Command Terminal, Type:
adb device (this should show you that your phone is connected. If it says that the phone is inactive/offline, then unplug your phone and replug it. Try again. It should now show up).
Type:
adb Reboot (this will reboot your phone)
After your device has rebooted, there's a 99.9999% chance that it will ":go offline" and not connect to adb (we can confirm this with "adb device" command. Unplug, Replug your phone and ensure it's online and ADB can see it).
Type:
adb wait-for-device push firewater /data/local/tmp
Type:
adb shell
Type:
su
Type:
chmod 755 /data/local/tmp/firewater
Type:
/data/local/tmp/firewater
If you're successful up to this point, Firewater will ask you if you're sure. Type:
Yes
At this point, the Command Prompt will start Chugging bottles of Firewater. Some Command Prompts only Chug One, others, 5,6, up to 12. If you reach 13 Bottles, Abort and try the steps again. This may take a while and several resteps, just be patient. The command prompt, when successful, will notify you that you are now S-Off!
To check this, boot in to Bootloader to confirm (it will say S-Off, not S-On).
The Why:
I believe the reason you need an internet connection is that the Firewater file connects to a server and the voodoo is all done by the server. Why would they do this? Probably to ensure that HTC doesn't screw us out of S-Offing our device like they're known to do by downloading and decompiling files used to S-Off or reverse engineering steps taken to S-Off If anything, this slows them down (and possibly makes it impossible for them to stop us from doing so.)
Special Thanks:
Beups, Fuses, Hasoon2000, and all Developers that are supporting our device with lots of goodies. Don't forget to donate to them to encourage them to spend time on our device, or, just buy them a beverage for all of the hard work and time they spend doing this for us.
If I have forgotten anything or forgot to give credit to someone, please let me know and I'll be sure to add it.

You might want to add that if firewater says your device is not compatible then it means exactly that and you just need to wait for firewater to be updated. There's no pattern to what is and isn't compatible its just luck of the draw and likely down to hardware variances.
Sent from my HTC One_M8 using Tapatalk

stuart0001 said:
You might want to add that if firewater says your device is not compatible then it means exactly that and you just need to wait for firewater to be updated. There's no pattern to what is and isn't compatible its just luck of the draw and likely down to hardware variances.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Ah, yes, you're correct. Thank you!

i'm having a nightmare.
having issues all the way through, seems the htc drivers i get from the toolkit don't install correctly. adb just wouldnt play. i got round that by installing htc sync from phone, that installed correct htc drivers. i then un installed htc sync.
now i've got as far as...
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
3082 KB/s (4519496 bytes in 1.431s)
C:\Program Files (x86)\Minimal ADB and Fastboot>shell
'shell' is not recognized as an internal or external command,
operable program or batch file.
any ideas what i've f'ed up?
---------- Post added at 01:47 AM ---------- Previous post was at 01:39 AM ----------
ok i think it should be adb shell yes?

Yes adb shell
Sent from my HTC One_M8 using xda app-developers app

Learoy1 said:
i'm having a nightmare.
having issues all the way through, seems the htc drivers i get from the toolkit don't install correctly. adb just wouldnt play. i got round that by installing htc sync from phone, that installed correct htc drivers. i then un installed htc sync.
now i've got as far as...
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
3082 KB/s (4519496 bytes in 1.431s)
C:\Program Files (x86)\Minimal ADB and Fastboot>shell
'shell' is not recognized as an internal or external command,
operable program or batch file.
any ideas what i've f'ed up?
---------- Post added at 01:47 AM ---------- Previous post was at 01:39 AM ----------
ok i think it should be adb shell yes?
Click to expand...
Click to collapse
Did you get it all worked out?
Also, I updated the OP to use "adb shell," I apologize, I should have remembered that adb need to be there. As well, I've updated the OP to point to the latest HTC Sync with drivers.

Sorry for the question but it's my first HTC device and I'm studying in deep all the aspects of bootloader, s-off and so on.
What about I need to come back the M8 for warranty?
If I am right I can restore stock rom and recovery and relock the bootloader through s-off. At this point, what about s-off? Is there a way to revert it to stock s-on?

This Rooting method works for the International variant as well right?

Just can't seem to get my device online. I've tried just about everything, restarted phone, laptop, server, different port, different cable, etc. I see a notification that says "Media Device [MTP] connected", and I have an inkling that it could be causing issues, but I can't seem to find a way to disable it. Is anyone else having this issue?
(T-Mobile M8, perma-rooted)
*edit* After several attempts, I seem to have gotten the timing right, using the version of ADB that came with the all in one tool. Somehow it just started to work, but only with that version. Other versions of ADB still saw the device offline. Just one of those annoying things. Either way, I'm now S-OFF. That was the last piece I was missing. Thank you.

Not working!
Have htc one m8 (at&t version) and have tried all the steps but always fails at the end. It saids it wil not work with my device? Don't other people use this with at&t and it works for them? Why doesn't it work for me? Is there another method to s-off? Like from twrp recovery?

patstar5 said:
Have htc one m8 (at&t version) and have tried all the steps but always fails at the end. It saids it wil not work with my device? Don't other people use this with at&t and it works for them? Why doesn't it work for me? Is there another method to s-off? Like from twrp recovery?
Click to expand...
Click to collapse
HTC patched the old S-OFF method, it doesn't work anymore unless you're really lucky to get a device that's before the patch and you don't first update it...
You can try Sunshine S-OFF it's $25 but it seems to do the job right. It actually checks your device for compatibility before you even pay for it, at least that way you won't end up paying for something that "might" not work.
[Android][HTC S-OFF] SunShine for modern HTC devices It's from the same developers of firewater. So far those that did it seems quite happy about it.
Your choice though, it's the only alternative method available.

BerndM14 said:
HTC patched the old S-OFF method, it doesn't work anymore unless you're really lucky to get a device that's before the patch and you don't first update it...
You can try Sunshine S-OFF it's $25 but it seems to do the job right. It actually checks your device for compatibility before you even pay for it, at least that way you won't end up paying for something that "might" not work.
[Android][HTC S-OFF] SunShine for modern HTC devices It's from the same developers of firewater. So far those that did it seems quite happy about it.
Your choice though, it's the only alternative method available.
Click to expand...
Click to collapse
I can't believe I paid $25 but it did work. Wanted to change my software buttons to stock android. Well I guess now I can put other roms on it. If I flash a different custom rom on it, it would be like getting a new phone so I would have to transfer all my data again? Took forever to get apps to restore from helium (carbon) backup and some did not work, really don't want to put custom Rom if it does that again. If I make nandroid backup to internal storage, can I transfer it to my pc for use later on?

patstar5 said:
I can't believe I paid $25 but it did work. Wanted to change my software buttons to stock android. Well I guess now I can put other roms on it. If I flash a different custom rom on it, it would be like getting a new phone so I would have to transfer all my data again? Took forever to get apps to restore from helium (carbon) backup and some did not work, really don't want to put custom Rom if it does that again. If I make nandroid backup to internal storage, can I transfer it to my pc for use later on?
Click to expand...
Click to collapse
Yeah unfortunately if you flash any new ROMs it'll be like a "new" phone like you yourself stated. There will be no apps, nothing. You can back it up and restore with something like Titanium. Even through Google Store it's easy enough if you lock in with the same account again, just reinstall, easy as pie.
Yes if you make a nandroid backup of your device you can store it on your computer for use later on. It's actually advisable to do so, you "might not" find a nandroid backup for your device whilst searching online, so at least if something goes wrong you have a backup on your PC and all is good :good: If only more people would make backups before doing anything though...

BerndM14 said:
Yeah unfortunately if you flash any new ROMs it'll be like a "new" phone like you yourself stated. There will be no apps, nothing. You can back it up and restore with something like Titanium. Even through Google Store it's easy enough if you lock in with the same account again, just reinstall, easy as pie.
Yes if you make a nandroid backup of your device you can store it on your computer for use later on. It's actually advisable to do so, you "might not" find a nandroid backup for your device whilst searching online, so at least if something goes wrong you have a backup on your PC and all is good :good: If only more people would make backups before doing anything though...
Click to expand...
Click to collapse
Titanium backup won't let me backup to sd card, I guess I could backup to internal storage and put it on pc like nandroid or move it to sd card afterwards? I could just download custom rom to my phone, goto twrp and flash it without pc? Is there any dual boot method of roms? I know for m7 there was something that let you switch from sense to stock android with press of button.

Lost & Puzzled Newbie
Hi Guys,
I'm hoping someone can help me out here because I've ben sat in front of my pc for 16 hours straight through the night & I now don't appear to be much nearer than when I started!
So, I picked up my new One M8 & having had some success rooting my ASUS TF700T tablet, I decided that I would root my phone before I got started using it properly & wasted time personalising it. Before I get started, I'm currently on Android 4.4.2, Sense 6.0, & software number 1.54.206.10; if you need anything else, let me know.
I did loads of reading first, hence the night sat in front of my pc, & amongst many others, I was following this thread & the instructions here:
http://forum.xda-developers.com/showthread.php?t=2799796
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I was doing really well to begin with & I managed to unlock the bootloader, flash TWRP, & install SuperSU. Then things started to go wrong. I was undecided whether or not to go for S-Off &/or Super CID but I'd read that S-Off might maximise my battery life even more, so I went for it. I only installed the HTC drivers, absolutely no HTC Sync, my USB Debugging was on, Security was off, & Fastboot was disabled. I downloaded Firewater & after discovering that the ADB folder on my pc wasn't just the folder I'd extracted my ADB zip file to, I found the correct ADB folder on my C: drive, dropped Firewater in & plugged my in M8. It's my own fault because normally, when my phone asks, 'do you want me to do this every time?', I say 'no, just once'......but for some unknown reason, once I'd hooked it up & was using the adb command window (Win 8.1), when the message popped up on the M8 about the phone allowing my pc to connect via adb every time, I, apparently stupidly, said yes.
What happened then was that the adb console, would recognise my phone, so when I typed 'adb device' (or whatever the instruction was), it gave me a page of all sorts of details but then every time I typed 'adb reboot', I got a message saying that the device was offline. If I typed 'adb device' again, I'd get the same page of data & I could see the phone in explorer, so I'm sure the drivers are there, but I also got the same message asking for the reboot.
I've spent hours trying to sort this out & if I'm honest, I got a bit lost (I'm normally quite good at problem solving but I don't suppose it helped not having slept for almost 30 hours now). Anyway, I remembered with my tablet that I just went into TWRP & flashed the 'CHROMi X' ROM from there & by this time, I just wanted to try to get things finished, so because I was most familiar with CyanogenMod, I downloaded it on the pc, transferred it to the phone & tried to flash it I thought I'd read that I neded the ClockworkMod bootloader but I was kind've hoping that TWRP would do the job......it didn't & just failed!
Then my problems really started because the phone went into a boot loop, staying on for only about 10-20 seconds after it booted up. Obviously, by this point I was quite worried that I was about to wreck my shiny new phone but I did some more reading & saw that for someone else, SuperSU had caused this, so I booted back to TWRP, wiped the Dalvik cache & re-flashed SuperSU. Thankfully, that stopped the boot loop
However, I now seem unable to access TWRP? When I hold down the volume down & power buttons, the phone just boots straight through to Android? SuperSU is still installed & it opens up fine (albeit with no apps logged) but it seems like now, the phone might not be unlocked, &/or rooted, or both, though that doesn't seem to make sense to me if SuperSU still runs?
EDIT: I've just tried deleting a folder on the external micro SD card using ES File Explorer & the 'operation failed', so it looks SuperSU, although it asked if I wanted to grant/deny the relevant permissions, isn't working. On 2nd attempt, it worked, so I'm still lost!
EDIT: Fastboot had sneaked back on, so I've switched it back off & I'm back into the bootloader, which says 'Tampered' & 'Unlocked' at the top, & I can boot into TWRP to make the backup of what I've got now that I wanted to make earlier
ANOTHER EDIT: I've now backed up the stock ROM with TWRP & downloaded a root checker app, so I now know that I'm still unlocked & rooted Now I could just do with some help deciding what ROM to install & help on how to go about it.....please
EDIT: After all that, I couldn't sleep, so I didn't try & I stayed up & have managed to sort it. I've got Android Revolution HD on for now but I think I'm correct in thinking that I'll be able to change to another ROM at a later date if I don't like this one? I was going to delete all this, so that people didn't think I was an idiot but it might prove useful to someone else, if only to prove that you probably shouldn't miss a night's sleep because you're trying to root your new phone!!!!
I hope all that makes sense to someone else though? All I wanted to do was get rid of all the O2 bloatware, & most of all, actually be able to write to my external micro SD card, without having to take it out of the phone constantly, so I wanted to install a custom ROM that would be as good as CHROMi X is on my tablet!! but as I said at the beginning, I now feel completely lost & unwilling to start trying again until I know what's happening/has happened.........oh, & I need some sleep!!
If anyone can help get me back on track again, I'd really appreciate it because I really have put the effort in & I don't normally give up but I'm worried that if I keep at it now, I'll end up bricking my phone!! I do want to get this sorted out & enjoy this amazing device for the next couple of years, so any advice on where to start next, which ROM I should use (at this point, I'm easy), or whatever, like I said, I'd really appreciate it
p.s. I didn't mention but once I've sorted my phone out, my girlfriend wants me to sort her HTC One Mini 2 out because she wants to be able to use her external micro SD card too!!

delete

Z1C won't start - advice please

I've got myself into quite a muddle with my rooted Z1 Compact. I was prompted to update the firmware to 14.4.A.0.157, which I did over the air. Since the update, the device had been freezing, restarting and generally being unwell. What I didn't realise, based on a piece I read somewhere, was that this was likely or probable if the phone had been rooted. My memory is a bit sketchy on all the steps I took - but briefly - it suggested checking the status of the phone, from which I followed instructions using flashtool to flash a preceding firmware (xxxx.108), which it appeared to do successfully but now the phone does not boot at all. I'm now lost what to do next and I couldn't say if I've soft or hard bricked the phone. Another article (at android.gs / unbrick-sony-xperia-z1 ) says that if it's hard bricked then I need to flash the full firmware (not just kernel only). I've downloaded and installed Emma from Sony's site. I can get the software to recognise the phone but it says it is locked and I am in the process of downloading the Android SDK to [see if I can] continue this process.
I should have stopped and asked for advice before I did any of this. Now finally I am pausing to seek advice. Can anyone point me in the right direction?
The phone will charge when plugged in, at least it is showing a green LED to imply fully charged.

Brief update: I couldn't enable USB debugging on device, as device doesn't start up. I enter fastboot mode when connecting the device (Windows) and I run "fastboot devices" in the platform-tools folder without an error however when I enter the command with my unlock key, I just get "waiting for device" (several minutes). I am assuming that this might be because I couldn't enable USB debugging on the device? Any suggestions on where to go from here?

I might as well log the antics of my adventurous mind. Given that I hit a dead end, I continued on the original path and used FlashTool to flash 14.2.A.1.114_Customized firmware (why this - because it was the only full firmware that I found). Anyway, thankfully, I now have a working device running that firmware with Android 4.3. I'll try and proceed to get back up to date.

devo1d said:
(why this - because it was the only full firmware that I found).
Click to expand...
Click to collapse
Not sure how when this thread is stickied at the top of the General Section. Z1 Compact Resource Thread -|-Rooting-BL Unlocking-Firmware & More..

Oh my goodness......... It is pantomime season after all

Magic. I confess to being another dizzy head when things don't go right and reading from a multiple sources and getting a bit overwhelmed & lost. Anyway, found the way out and thank you for the pointer to the sticky right-in-front-of-the-eyes info. Bookmarked.

Android tablet, how to disable kiosk mode or install new firmware

I am new to the android programming world. I own an iQR70 device from MLS that is using -if I read well- the kiosk mode for its own application called MAIC (something like Amazon's Alexa virtual assistant).
{
"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"
}
The real pain with this device is that the application is buggy does not get any updates and overall does not work properly.
So, my questions are, a) is there any way to disable the kiosk mode and work with it as a normal tablet? or desperately b) Can I install a compatible firmware? I don't care for the data inside.

You can check for update. Look for android version of tablet. You can check their site for any upgrade of software.
You can flash other firmware. Find compatible firmware as per your model.
You can disable apps same as you do on android mobile.

My tablet currently Is dead boot and I am trying to find the test points. Anyway, I have no access to the android os to disable apps. The virtual assistant is the only app I can use, all others are forbidden.

Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?

zeetotheuno said:
Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?
Click to expand...
Click to collapse
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.

sdancer said:
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.
Click to expand...
Click to collapse
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.

zeetotheuno said:
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.
Click to expand...
Click to collapse
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.

sdancer said:
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
Click to expand...
Click to collapse
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
sdancer said:
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
Click to expand...
Click to collapse
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
sdancer said:
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.
Click to expand...
Click to collapse
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.

zeetotheuno said:
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.
Click to expand...
Click to collapse
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.

sdancer said:
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.
Click to expand...
Click to collapse
That's awesome! Thank you in advance.
Yeah, I guess the hardware reset really takes some time and a lot of trial and error.
But if you manage to do it, let me know, I'm just curious in general, if that's possible with this device.

To Flash your device,
1) Install the drivers
2) Press Download from SP Flash Tool
2) Connect USB
3) Connect the power outlet from your device (in this case) or connect the battery
****WARNING: DONT FORMAT THE PRELOAD or you will get a DEAD BOOT device, use ONLY DOWNLOAD and not download+format
AutoInstall
=================
MediaTek_Preloader_USB_VCOM_drivers.exe
File on MEGA
mega.nz
Manual Install
=================
MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed.zip
File on MEGA
mega.nz
MediaTek_Preloader_USB_VCOM_Drivers.zip
File on MEGA
mega.nz

Hey @sdancer, thank you for the drivers. But I must do something wrong, because it's still not detected. It's not showing in my device manager and nothing happens in SP Flashtool.
I tried the automatic install and the manual install, but still nothing :/
Could you maybe explain how exactly you installed them? Maybe I'm making a mistake there.

1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at

sdancer said:
1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at
Click to expand...
Click to collapse
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.

zeetotheuno said:
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.
Click to expand...
Click to collapse
Hi
I suppose that this is a driver's problem, you should try to fix it someway.

Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko

Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
Any idea, Any fix?

paulos2951 said:
Any idea, Any fix?
Click to expand...
Click to collapse
I have no idea bro :/ Hoping that someone will help me

Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
I have the same problem with you
If you find a solution please send me a message !

Jim-Kyritsis said:
I have the same problem with you
If you find a solution please send me a message !
Click to expand...
Click to collapse
Hi friend! Are you Greek? Is there a way to contact MLS in Greece?

Realme UI 2.0 update issue

Hello everyone. Hope you all are doing well.
I had updated my Realme 6 Pro from Android 10, version RMX2061_11.A.49 to the Android 11 update i.e. Realme UI 2.0, version RMX2061_11.C.15. The thing is, after optimizing apps during the first boot, the phone is stuck at the lock screen and the touchscreen is not responding.
Video of the issue is here: Realme 6 pro UI 2.0 issue
Kindly do help on what to do next. Doing a reset is the last step I want to undertake, since I forgot to take a backup.. Will flashing the Realme UI 2.0 update via stock recovery help? Any help and suggestions would be much appreciated.
Thank you.

soham93 said:
Hello everyone. Hope you all are doing well.
I had updated my Realme 6 Pro from Android 10, version RMX2061_11.A.49 to the Android 11 update i.e. Realme UI 2.0, version RMX2061_11.C.15. The thing is, after optimizing apps during the first boot, the phone is stuck at the lock screen and the touchscreen is not responding.
Video of the issue is here: Realme 6 pro UI 2.0 issue
Kindly do help on what to do next. Doing a reset is the last step I want to undertake, since I forgot to take a backup.. Will flashing the Realme UI 2.0 update via stock recovery help? Any help and suggestions would be much appreciated.
Thank you.
Click to expand...
Click to collapse

Hello soham,
I have the exactly same problem since the yesterday update with my Realme X2 Pro.
If you find a solution please let me know
...at the moment i have no idea.

yeah bro same with mine,
but we have another choice,
drain the battery and let the mobile turn off
after that go to the recovery mode and wipe your data.
or else we need to update the software in the recovery mode which is not arrived yet.

Press the power off and volume up button for about 7 sec and it should power off. when u turn it on press the power off and volume down button for 10 sec and you will boot to recovery mode. After that, u will have to format your data which will cause ur data to be removed.

I dont think there is any other way to fix this. Unless you have your data back up in the cloud. Maybe you can also take out the storage card from your phone which is difficult and then back up your data from a pc or something.

I thought of flashing the ROM, but it was not available anywhere. So I ended up performing a factory reset to boot the phone. There seems to be no other solution for this.

I have no backup..so i wait for the next update..
Wipe data doesnt work for me and i do not format the device.

I have the exact same issue. This problem generally applies to all Realme devices upgraded to Realme UI 2.0. The root cause is the disabling of com.coloros.weather.service package, usually done during debloating through adb. Further analysis I have done is explained on my thread.
Quick fixes you have now:
If you have adb enabled and ticked "Always allow from this computer" on the prompt below when your phone is still working, you can connect your phone in the blinking state and issue the following command: adb shell cmd pm enable com.coloros.weather.service. Then, reboot your phone. It will work normally on Realme UI 2.0.
{
"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
[DATA LOSS] Download this ozip and put it on an SD card. A used SD card works fine as long as it isn't encrypted and has enough free space. Make sure the file name matches your device model. Enter realme UI Recovery (on Realme 7, you press VolumeDown + Power, which might differ for each device) and choose 'Install from Storage'. Enter your device password, select 'SD Card', and pick the ozip you have downloaded. The phone will wipe itself, and you end up with a working phone on Realme UI 1.0.
[DATA LOSS] If your phone is still on warranty period, go to any Realme Service Centre, and use the following statement; the service centre will either replace your phone free of charge or if they don't have any replacements in stock, put you on a waitlist and calls you back once the replacement device is available.
I am updating my device to Realme UI 2.0 when suddenly the device turns off and reboot itself. Now, this device won't allow me to unlock it.
Click to expand...
Click to collapse
Other possible, longer-term solutions are:
Wait for Realme to realize this problem and issue an OTA update. The fix is easy on their side; just add a simple one line on the after-flash script of the next OTA/ozip to enable the weather services package:
Code:
pm enable com.coloros.weather.service
The command pm enable would do nothing if a package is already enabled. However, Realme might not realise this problem. Even if they recognise it, Realme might think it is not their own problem (debloating = user's fault?). If they release this fix, we can just boot into recovery and install it. Realme has support for OTA updates on their recovery. Just enter the device password and then the WiFi password.
I have tried exploring the Realme forums, albeit not directly filing a bug report. I found many, many users experiencing a similar issue as ourselves. Most of it was responded to by Realme representatives in this fashion: "enter recovery mode by pressing this and this, and then choose to wipe data. This will reset your phone to its working state." This is not acceptable for me since a functioning phone is lower on my priority than keeping my data (albeit in limbo).
Suppose your device has MediaTek SoC, and you have not set up any password/PIN/pattern on your device. In that case, you could possibly extract the userdata partition, exploiting the Boot ROM (BROM) exploit by Dinolek and k4y0z with the SP Flash Tool. You first need to find a specific scatter file for your device; however, if none is available, you could generate one from a preloader dump using a tool named Wwr MTK.
If you have set up a password, then this would be infeasible, apparently, since not only the device password is needed to decrypt it, but also some salt stored on the SoC itself; hence this thread highly suggests swapping SoC and eMMC to another working exact same phone (cannibalize another phone).
However, even after you swapped the SoC to a new phone and write your userdata partition on it, you faced a new dilemma:
previously on the old phone, you have a non-working software config, but the decryption key to the userdata is the same as the decryption key to the other partitions
now on the new phone, you have a working software config. The decryption key is available on SoC, but the other partitions are unreadable to the bootloader. They are either unencrypted or encrypted with a different key.
I have not been able to solve the above dilemma.
Hence, my current objective is to nag Realme and invite others to also nag them to implement that simple one line on their OTA update.

any updates? today i update realme 6 to realme ui 2.0 it broke my phone... because of this weather crap usb debugging not working for me...

I too ran into this issue just now. Thanks @said1219 for your suggestion. A single change in my case. I haven't disabled the app, I have uninstalled it. So I ran
adb shell cmd package install-existing com.coloros.weather.service
This fixed the issue. This didn't require restart.
I use Realme C3. After this update again there is a new update of 280MB released on Dec 9, 2021, specifies system optimization.
It doesn't make any issue after this.

vigneshrajarr said:
I too ran into this issue just now. Thanks @said1219 for your suggestion. A single change in my case. I haven't disabled the app, I have uninstalled it. So I ran
adb shell cmd package install-existing com.coloros.weather.service
This fixed the issue. This didn't require restart.
I use Realme C3. After this update again there is a new update of 280MB released on Dec 9, 2021, specifies system optimization.
It doesn't make any issue after this.
Click to expand...
Click to collapse
I have a question, how did you reinstall the weathersystem even if your phone is flickering? Did you do it on power on or in recovery mode? That is an adb fastboot right?? Does your phone prompt you and asks to "file transfer" and "charging only"? Because that's the only last thing I have to do, let my pc run adb fastboot to turn it on

Quasar.Illumia said:
I have a question, how did you reinstall the weathersystem even if your phone is flickering? Did you do it on power on or in recovery mode? That is an adb fastboot right?? Does your phone prompt you and asks to "file transfer" and "charging only"? Because that's the only last thing I have to do, let my pc run adb fastboot to turn it on
Click to expand...
Click to collapse
You let the phone complete boot and enter the flicker-state. Then run "adb devices" as per your photo in my thread.
The following step can be done either on normal boot, fastboot, or recovery mode:
If no device is found, it is likely that USB debugging is disabled on your device.
If your device is found, but it says 'unauthorized', it means that you didn't tick "Always allow connections from this device" or a long time has lapsed since you've connected your PC's ADB to your phone.
If your device is found and it says 'device' on the right of the serial number, you're good to go.
Except for the last scenario, you're possibly getting back to square one.
The following step must be done after the phone completed normal boot, recognized your PC, and enter the flicker-state:
If you disabled the weather package, run
Code:
adb shell cmd pm enable com.coloros.weather.service
If you uninstalled the weather package, run
Code:
adb shell cmd package install-existing com.coloros.weather.service
Your phone will immediately stop flickering and you can enter your password normally. And, as per my reply in my thread, "Allow charging only" could prevent you from accessing ADB.

I thought it wasn't working when I entered adb shell yesterday. Thank you UwU it is working now
said1219 said:
You let the phone complete boot and enter the flicker-state. Then run "adb devices" as per your photo in my thread.
The following step can be done either on normal boot, fastboot, or recovery mode:
If no device is found, it is likely that USB debugging is disabled on your device.
If your device is found, but it says 'unauthorized', it means that you didn't tick "Always allow connections from this device" or a long time has lapsed since you've connected your PC's ADB to your phone.
If your device is found and it says 'device' on the right of the serial number, you're good to go.
Except for the last scenario, you're possibly getting back to square one.
The following step must be done after the phone completed normal boot, recognized your PC, and enter the flicker-state:
If you disabled the weather package, run
Code:
adb shell cmd pm enable com.coloros.weather.service
If you uninstalled the weather package, run
Code:
adb shell cmd package install-existing com.coloros.weather.service
Your phone will immediately stop flickering and you can enter your password normally. And, as per my reply in my thread, "Allow charging only" could prevent you from accessing ADB.
Click to expand...
Click to collapse

Well then, another year has gone by
No changes so far? I noticed new Realme UI updates have been launched in the meantime. Has anyone tried them out yet on the blocked phones?
As you've recommended @said1219 , I've kept my battery in good condition and still hope that this problem can get solved in the future...
However, since this issue started, by principle I've refused to buy any new Realme product...

Question Android Beta to Factory Reset mucked up, plus a bunch of troubleshooting I've already tried

Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that the installation failed. If this wasn't already obvious I'm not good at talking tech but I am decent at troubleshooting things, so I tried. Today I learned what fastboot and adb are, what sideloading is, stuff like lineageos and twrp if. If that's what that one was called, today is a blur. Okay let me be more specific.
It seems like what I need to do is sideload the right OTA image, but I can't find the one I need. The last two I tried, one being the very wrong one and one being (copied from official source):
12.1.0 (SQ3A.220705.003, Jul 2022)Linke66e2df393d5a0f885f62d2de086dcd80cdcf8eb28d567f4582ff67756876170
But this one also wasn't new enough? It says: error: recovery: update package is older than the current build, expected a build newer than the timestamp 1657306786 but package has timestamp 1654117437 and downgrade not allowed.
I've tried the flashing tool (my phone shows up but has a connection issue I couldn't fix), the google rescue mode tool (my phone connected but the browser tool just looped til the phone timed out), I've tried sideloading the twrp apk and such which didn't work due to "error: closed" which I also couldn't fix, but I'm pretty sure all these problems are caused by not having developer options and debugging and those things turned...whichever way they need to be.
If this is important, I'm in Canada, using Telus, the phone is still fairly new and was working perfectly I just had to opt in and then out of the android beta. Kicking myself for that now. If I need to be more specific I'll try but for now, can I unbrick my phone without taking it somewhere to be unbricked for me? I also don't have an SD card to use to do it that way. Thank you.

Try This link for help.

lilyhollow said:
Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that the installation failed. If this wasn't already obvious I'm not good at talking tech but I am decent at troubleshooting things, so I tried. Today I learned what fastboot and adb are, what sideloading is, stuff like lineageos and twrp if. If that's what that one was called, today is a blur. Okay let me be more specific.
It seems like what I need to do is sideload the right OTA image, but I can't find the one I need. The last two I tried, one being the very wrong one and one being (copied from official source):
12.1.0 (SQ3A.220705.003, Jul 2022)Linke66e2df393d5a0f885f62d2de086dcd80cdcf8eb28d567f4582ff67756876170
But this one also wasn't new enough? It says: error: recovery: update package is older than the current build, expected a build newer than the timestamp 1657306786 but package has timestamp 1654117437 and downgrade not allowed.
I've tried the flashing tool (my phone shows up but has a connection issue I couldn't fix), the google rescue mode tool (my phone connected but the browser tool just looped til the phone timed out), I've tried sideloading the twrp apk and such which didn't work due to "error: closed" which I also couldn't fix, but I'm pretty sure all these problems are caused by not having developer options and debugging and those things turned...whichever way they need to be.
If this is important, I'm in Canada, using Telus, the phone is still fairly new and was working perfectly I just had to opt in and then out of the android beta. Kicking myself for that now. If I need to be more specific I'll try but for now, can I unbrick my phone without taking it somewhere to be unbricked for me? I also don't have an SD card to use to do it that way. Thank you.
Click to expand...
Click to collapse
what was the error you got in Android Flash Tool?

jcp2 said:
what was the error you got in Android Flash Tool?
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"
}
I checked with all the troubleshooting tips for connection issues but nothing changed the status. Sometimes it would say already in use when I had the cmd open but then I use kill-server to free it up and it changes to this.

Is your bootloader unlocked? If it isn't (and if Telus is like the US phone carriers), then I don't think you would be able to revert back to Android 12. You will have to wait for Android 13 to officially launch and you can then manually flash the full image (as it seems that you cannot sideload the OTA). And you would have to manually flash the latest full Android 13 beta build for the time being.
Regardless, right now you should try looking into "platform-tools" here on XDA. Then, see if you can use adb to view your phone over USB connection with the stock Google USB cable that came with the phone (most random aftermarket cables work fine, however, a few do not seem to work). You would need USB Debugging enabled to do this, however, the phone may still respond since you had it fall into fastboot mode before (and you would essentially be using adb to put your phone into fastboot mode).
Leave a reply if you can put your phone into fastboot mode/if you can use adb. We can go further from there with what I know about this stuff.

NippleSauce said:
Is your bootloader unlocked? If it isn't (and if Telus is like the US phone carriers), then I don't think you would be able to revert back to Android 12. You will have to wait for Android 13 to officially launch and you can then manually flash the full image (as it seems that you cannot sideload the OTA). And you would have to manually flash the latest full Android 13 beta build for the time being.
Regardless, right now you should try looking into "platform-tools" here on XDA. Then, see if you can use adb to view your phone over USB connection with the stock Google USB cable that came with the phone (most random aftermarket cables work fine, however, a few do not seem to work). You would need USB Debugging enabled to do this, however, the phone may still respond since you had it fall into fastboot mode before (and you would essentially be using adb to put your phone into fastboot mode).
Leave a reply if you can put your phone into fastboot mode/if you can use adb. We can go further from there with what I know about this stuff.
Click to expand...
Click to collapse
Bootloader is locked. It's permanently stuck in fastboot mode, except when I switch to recovery or rescue, and then if I reboot the phone it goes into fastboot. When I use adb and use "adb devices" my device shows up as [devicenumber] sideload. Other adb commands won't work due to "error: closed" which I assumed was because debugging was off. Only thing I got to work so far was sideloading OTA, and you see how that went. But I do have platform-tools and adb and fastboot set up. So that's something. My USB cord is aftermarket but does seem to work.

are you using These drivers? for windows. which version of windows are you running? I think @NippleSauce is correct in that if you don't have usb debugging enabled (you don't) you'll have to wait for A13 final. Or, if you're in your 30 day return window.....take it back to Telus.

Sorry, I've been eating and lifting weights at almost the same time LOL. I also just got the Pixel Buds Pro in the mail (a day before the official release) and they are freaking amazing.
Anyway, since the phone keeps going into fastboot, perhaps we can move forward. What does the screen say on it when in fastboot? There are two different fastboot menus: regular "fastboot" and "fastboot d".
Feel free to post a screenshot if you have something to take a picture of the display with. We'll move forward from there once I'm done lifting =).

NippleSauce said:
Sorry, I've been eating and lifting weights at almost the same time LOL. I also just got the Pixel Buds Pro in the mail (a day before the official release) and they are freaking amazing.
Anyway, since the phone keeps going into fastboot, perhaps we can move forward. What does the screen say on it when in fastboot? There are two different fastboot menus: regular "fastboot" and "fastboot d".
Feel free to post a screenshot if you have something to take a picture of the display with. We'll move forward from there once I'm done lifting =).
Click to expand...
Click to collapse
how are those compared to the pixel buds a?

DespairFactor said:
how are those compared to the pixel buds a?
Click to expand...
Click to collapse
Holy shirtless cow with nine udders good. I'm really liking them. The 11mm drivers really amp up the quality and separation in the sound. I think they're quite close in sound quality to my Sennheiser True Wireless 3's - so I think the price makes it a good deal on today's market. But the thing that makes them such a good deal is that the transparency mode is awesome and is clear and audible to the point where you can't even tell via the audio that you're wearing earbuds. And on top of that, the noise cancellation is some scientific voodoo with its strength for specific sounds. Some light (and semi-enjoyable) sounds pass right through; like me typing on my keyboard or clicking my computer mouse. But other sounds that are generally more noticeable such as people speaking or audio from cellphones is completely gone. It's pretty weird but is very good!
And to top it off, I am also pretty poor in hearing after an sTBI a few years ago. Audio was important to me before the incident, and therefore has become more important to me now. But since my left ear hears sound in a way that makes the sound that goes to my brain sound like people speaking in Charlie Brown, I guess take my opinions with a grain of salt lol.

lilyhollow said:
Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that the installation failed. If this wasn't already obvious I'm not good at talking tech but I am decent at troubleshooting things, so I tried. Today I learned what fastboot and adb are, what sideloading is, stuff like lineageos and twrp if. If that's what that one was called, today is a blur. Okay let me be more specific.
It seems like what I need to do is sideload the right OTA image, but I can't find the one I need. The last two I tried, one being the very wrong one and one being (copied from official source):
12.1.0 (SQ3A.220705.003, Jul 2022)Linke66e2df393d5a0f885f62d2de086dcd80cdcf8eb28d567f4582ff67756876170
But this one also wasn't new enough? It says: error: recovery: update package is older than the current build, expected a build newer than the timestamp 1657306786 but package has timestamp 1654117437 and downgrade not allowed.
I've tried the flashing tool (my phone shows up but has a connection issue I couldn't fix), the google rescue mode tool (my phone connected but the browser tool just looped til the phone timed out), I've tried sideloading the twrp apk and such which didn't work due to "error: closed" which I also couldn't fix, but I'm pretty sure all these problems are caused by not having developer options and debugging and those things turned...whichever way they need to be.
If this is important, I'm in Canada, using Telus, the phone is still fairly new and was working perfectly I just had to opt in and then out of the android beta. Kicking myself for that now. If I need to be more specific I'll try but for now, can I unbrick my phone without taking it somewhere to be unbricked for me? I also don't have an SD card to use to do it that way. Thank you.
Click to expand...
Click to collapse
I opted out of the A13 beta and ran into the sane issue as my bootloader is locked. I was able to get back to A12.
I Googled it and found that you need to use the volume buttons to scroll to recovery and select by pressing the power button. You will then see a screen that says no command, hold the power button and tap volume up and you will be in recovery mode. Scroll down and select install from ADB. You will need to place the most recent A13 OTA zip in platform tools which is what I use for all of my ADB stuff or whatever you use for ADB installation. DO NOT CHANGE THE FILE NAME. Once you have selected install from ADB on your device, type adb install (file name.zip), if you don't include.zip behind the file name, it will error out.
Once you hit enter, your device will say verifying file and you will see the percentage on the pc screen in adb. Once it completes the installation, reboot your device and skip through the setup. Once you skio through setup and get to the home screen, go into settings and go to where you check for updates, it should say update available,if not do a manual check. Once you are prompted about an update, select to download and install. It will install A12 with all the warnings about it wiping your device. Once this install completes and you restart, you will be back on A12.

Thank you everyone! Someone helped me out over telegram after I posted this and we worked through it, realized part of the problem was my cord, and then mostly fixed it the way truckerdewd said, except once android 13 was loaded, I used the Android Flash tool to set it back to 12 and it worked. I'm typing this from a working phone and very happy about it. <3
On a side note how are those fancy new ear buds comfort wise? I have a lot of trouble with pain from ear buds and only use really comfy over ear headphones that I like but I'm desperate for ear buds I don't hate.

lilyhollow said:
Thank you everyone! Someone helped me out over telegram after I posted this and we worked through it, realized part of the problem was my cord, and then mostly fixed it the way truckerdewd said, except once android 13 was loaded, I used the Android Flash tool to set it back to 12 and it worked. I'm typing this from a working phone and very happy about it. <3
On a side note how are those fancy new ear buds comfort wise? I have a lot of trouble with pain from ear buds and only use really comfy over ear headphones that I like but I'm desperate for ear buds I don't hate.
Click to expand...
Click to collapse
I got these Razer Chroma Earbads and they are super comfy and sound great. I got the ones that light up.
https://www.amazon.com/Razer-Hammerhead-Wireless-Bluetooth-Earbuds/dp/B099LZ2BGB/ref=mp_s_a_1_3?crid=V3S5O8UC9983&keywords=razer+chroma+earbuds&qid=1658996631&sprefix=Razer+chroma+ear%2Caps%2C152&sr=8-3

NippleSauce said:
Holy shirtless cow with nine udders good. I'm really liking them. The 11mm drivers really amp up the quality and separation in the sound. I think they're quite close in sound quality to my Sennheiser True Wireless 3's - so I think the price makes it a good deal on today's market. But the thing that makes them such a good deal is that the transparency mode is awesome and is clear and audible to the point where you can't even tell via the audio that you're wearing earbuds. And on top of that, the noise cancellation is some scientific voodoo with its strength for specific sounds. Some light (and semi-enjoyable) sounds pass right through; like me typing on my keyboard or clicking my computer mouse. But other sounds that are generally more noticeable such as people speaking or audio from cellphones is completely gone. It's pretty weird but is very good!
And to top it off, I am also pretty poor in hearing after an sTBI a few years ago. Audio was important to me before the incident, and therefore has become more important to me now. But since my left ear hears sound in a way that makes the sound that goes to my brain sound like people speaking in Charlie Brown, I guess take my opinions with a grain of salt lol.
Click to expand...
Click to collapse
I got my pair coming via amazon today