Develop Bugs

[Q] Help Rooting Motorola Defy in Thailand

I just purchased a Motorola Defy in Thailand (there are not many of these here…Moto’s seem to be very rare here) and I have not been able to root this thing no matter what I have tried. None of the one-click solutions seem to work. I have been able to push the required files via adb to the phone, get into the shell and run the exploit.bin. I get back to the original directory but I the phone disconnects and when I run the adb devices command I get no devices attached. If I reboot the phone I can get it to show up on the adb devices list, but when I run the adb shell I only get a $ and not #. I have tried this many, many times with the same result. I have also re-installed the Moto usb drivers many times and does not seem to make a difference. I must be doing something wrong. This is a brand new phone in Thailand, and probably has only been available here very recently.
I really do not have any experience at any of this but I am trying to learn. I also really need this phone rooted because I cannot access any paid apps in the marketplace In Thailand, and getting some of these apps would make my life easier. I am confident I can get them if I could get root access (using MarketAccess). The reason I bought the Defy in Thailand and not another phone is it is compatible with my home country. Maybe I blew it…..
Any help or advice would be very much appreciated.

I am brand new to all of this, and have no idea what I'm talking about.
A search turns up two guides on how to do this. One at a site called dkszone and one here. Simply by searching "root motorola defy". Dkszone credits xda with the guide. Their guide is a little different, though, in that they reference an ADB gui for Windows, which is what I would have to use. Both guides are worth reading. I can't link to them because I have not posted here enough.
One thing that does strike me is that you make a reference to getting back to the original directory and your phone disconnects. Both guides make a reference to having to reconnect. XDA in step 5 and dkszone in step 7.
Someone here knows the answer.
Haven't been to Thailand in a while. Lived on Soi Lang Suan in Bangkok for two years. '95 and '96 maybe. Is Shinawatra still in exile? I'm sure you must know that he essentially brought cellphone service to Thailand. In a big way, that's for sure. This long before he became the PM, or whatever they call it now.
.

more specific info
I will try to get a little more specific…
I’ve used the guide posted on xda forums and I can push via adb the following files like this:
adb push Superuser.apk /sdcard/Superuser.apk
abd push su /sdcard/su
adb push busybox /sdcard/busybox
adb push exploit.bin /data/local/tmp/exploit.bin
Seems to work no problem…..
I then type the following commands
adb shell
cd data/local.tmp
chmod 0755 exploit.bin
./exploit.bin
The system chews on it a bit, shows a bunch of remarks, then $, then forked a bunch of childs (scary) and then displays the starting directory (C:\documents and settings\userblahblah).
At this point things go nowhere. There is a remark about restarting the adb server on the desktop and re-login. I guess I am not exactly sure what that means or how to do it. If it means unplugging the phone and plugging it back in I have done that. If it means rebooting the phone and/or rebooting my pc I have done that as well. If I type adb devices at the command prompt after running the exploit.bin) I get “list of devices attached” with nothing listed below. I can use kill-server and then again enter the adb devices command (adb starts) but the phone is still not recognized. I can check for hardware devices attached through device manager and the ADB interface does not show up (although it was there when I started this procedure) If I type adb shell at this point I get a device not found error. The only way I can get the phone to be recognized again is if I reboot the phone. When I do this the adb interface is listed in system hardware, I can run the adb devices command and the device shows up. When I run the adb shell command now I get a $....so no permissions, right? This has been a long, frustrating experience.
Does anyone have any idea that I am doing wrong or know of any way to fix this?
Any help or other ideas would be very much appreciated…..
BTW,
I’m pretty sure Shinawatra is still in exile…I think he has like 20 passports or something. Who knows where he is...

I really don't know what to tell you. I really don't.
I would not be able to use that program you are talking about. I would have to use a one-click method. I know you said you have tried the one-click methods before.
I don't need this for my phone and it wouldn't work anyway, I suppose, but I put the one-click .apk on mine just for illustration purposes.
This on a phone with ASTRO file manager pro.
Downloaded one-click .apk from here onto my hard drive. That first post reads that the app is available on the Market. I couldn't find it.
Pic 1 - moved file onto my phone then removed phone from laptop
Hit the ASTRO icon on my phone and I get what you see in pic 2.
Hit sdcard and got pic 3.
Scrolled to bottom and hit the .apk and got pic 4.
Hit Open App Manager and got pic 5.
I can't continue from there because it's not made for my phone.
My intent is not to insult you. If you have done this and it doesn't work, then I am just at a loss. If the info is of no use to you, maybe someone will find it useful in the future. I suppose it's possible that this is all in the thread that I linked to. I can't take the time to read it.
{
"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"
}

Thanks for the input and the concise instructions. I have actually tried running the z4root.apk file from the phone. It installs just fine. When I run the program (for those familiar with it) I choose permanent root (or temporary root, I have done both). There is a notification at the bottom of the program that is telling you what the program is doing at the time. It displays ‘Running exploit in order to gain root access’ (or something similar) and then ‘acquiring root shell’. The z4root program stays on the ‘acquiring root shell’ screen for about 10 seconds or so then the screen reverts back to the all applications screen. No confirmations or error messages…nothing. And the phone is definitely not rooted.
Going to Hong Kong for a day…wish I could use the app store for my wanted apps there….I think I'm going to have the same issue as Thailand (no paid app appstore access).
Still hoping for an answer….and I'm not talking about throwing my phone out the window….yet…

Rooting Motorola Defy
Z4Root does the same thing on my Defy. I also can’t pass through ./exploit.bin either. After executing exploit.bin I get dropped to c:\...\... as expected but then I can’t even go back in adb shell as it gives the error: device offline…I can only get to adb shell after rebooting the phone, however it takes me back $ prompt instead of # prompt. So it seems like this exploit.bin is not capable of giving me # (Root) prompt and so I am unable to mount system partition with read and write access and so unable to execute the rest of the commands on the phone as well. Am I doing it wrong or missing something here? Thanks for the help.

The z4root worked fine till version 2.34.1. From 2.51 version on there is another utility superoneclick. You can find it in the defy section of the forum. Worked for me and a lot of others.
Sent from my MB525 using XDA App

Success!
I do not know why I did not find this tread before but I did get my Thailand Defy rooted using the info and file on this tread:
http://forum.xda-developers.com/showthread.php?t=913709
I need to improve my thread searching skills....
The superonclick version that I had tried previously was different than the one posted on that thread and I did not need to use 'turn on turn off stuff' noted there........one click...done......as advertised.
Thanks for everyone's help.....you have saved a Thailand Defy from a 30 story dive out of the window..... (and saved my sanity).

Success!
Ditto from an apartment on the 13th floor in Ottawa, Canada.

Rooting a Defy
I have one too. While I was on 2.1, I had to use an old version of Super One Click. The update finally came out for my phone, and moved it up to 2.2.2. The update killed my rooting, but the current Super One Click worked like a charm after the update. Mine was from the UAE, and I live in the USA, so some of the pre-installed apps did not apply to me, and were really annoying, trying to localize applications into languages I can't read or speak. Rooting let me kill off some pre-installs. The new version also seems to be a lot more battery gentle, although it really hit the battery hard the first day (I think it was just getting all of the cache and settings caught up using a lot of data connection.)

So I bricked my GNEX...Then brought it back to life!

So, this morning at 5am (yes, stupid time to be playing) I flashed a zip. I have stored on my phone zips for both this and my tablet, and guess what genius did? flashed the wrong friggin one! Very surprised it went through without fault, but hey, **** happens.
So, basically what happened, is my phone became a brick. Black screen, could not boot it up, couldn't et to bootloader or download mode or recovery, tried several things like pulling battery for 30 secs then putting back in, plugging into PC without battery and putting battery in, leaving without battery or SIM for 30 minutes and putting back in, NA friggin DA. Still a brick. Not even the vibration when it first kicks in. Nothing
Starting to think time to call tech support, but as I was trying to plug into PC, I noticed something trying to install, then disappearing real fast. That was my first clue. I opened device manager, plugged phone in, and watched what was happening. A device called OMAP4460 was trying to install for half a second before disappearing, failing, but still, it was something. Even though screen was still blank, and not even bootloader would come up, this was happening. So I googled.
I found this site/thread: http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/. Legija, is a friggin genius Downloaded and unzipped the package, ran the bat, and plugged in the phone. But alas, still no joy
Reread his post - install drivers first...So, putting on my tech hat, how to install drivers if device is not listed, I went into the Actions menu in Task Manager (Win 7), and selected to add legacy hardware. I then chose to install manually, then selected have disk, and browsed to the drivers in the zip package from Legija (all this without device plugged in BTW). I installed the OMAP flash driver successfully, and now showing in task manager with the nice yellow triangle/exclamation mark.
Ran the bat file again, plugged phone in **WITHOUT** battery in phone, and off it went scrolling through it's processes, ninja'n away my f'up. When it completed, put battery back in, held down power, and up she came! Woot! Got back into OS no issues, and I'm one very happy camper.
So I thought i'd share, not thinking anyone else may do the same bloody stupid thing, but maybe a variance, or just have the same symptom (black screen, attempt to install OMAP when plugged into USB), this may just help you! AS for me...deleted all files not for GNEX, i'll continue to stuff around before work, so this is safe
EDIT:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process. Once you see "Press any key to continue..." close the CMD window and proceed to step 9
9. Unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)

Thanks for sharing this find, I'm sure others will find this to be useful

No problem, true believer in sharing my stupid mistakes so other may not follow, or if they do, know how to fix
Oh, in my write up - one change now edited - run the bat with the phone connected to USB **WITHOUT** battery in, once it's finished insert and boot up

Next time I'll be more safe while flashing roms to my phone.
Great find.

wow, this is possible? i thought cwm will prevent you from flashing wrong zips and even if not, why would it kill the bootloader? i was under the impression gnex is close to unbrickable but this topic you linked opened a whole can of worms for me, whats with all these hundreds of people who hard(!)bricked their nexus ... did i miss something?

This was a custom zip I had created myself to do some things on my tab, it ran from install script an install.sh that then went and installed a recovery img. Pretty sure i've never seen this before from any install zip, it was the behaviour I put in mine that allowed it to go through, and I hadn't put into the script to stop if not correct device - lesson learned
BUT - that said, you can do things like this to your phone running scripts, very easy to actually if it's running from su... So never run scripts unless you trust he person whose created it (or have written it yourself and certain of it), know it's definitely for your device, and, most importantly - never miss this step - have had 3 cups of coffee first :good:

Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^

Theshawty said:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Click to expand...
Click to collapse
LOL - easy thing to do if you're screwing with stuff before you're awake, especially scripts. Anything running under superuser can do this effectively, especially scripts working in /dev/block/... All it takes is one FAIL and you're bricked - the question then becomes is it permanent or not! And I always google before I ask questions, otherwise i'd lose my right to abuse others who don't!!! :angel:

rekrapg said:
LOL - easy thing to do if you're screwing with stuff before you're awake, especially scripts. Anything running under superuser can do this effectively, especially scripts working in /dev/block/... All it takes is one FAIL and you're bricked - the question then becomes is it permanent or not! And I always google before I ask questions, otherwise i'd lose my right to abuse others who don't!!! :angel:
Click to expand...
Click to collapse
If it's not permanent, it's not, and never was, a brick.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
If it's not permanent, it's not, and never was, a brick.
Click to expand...
Click to collapse
True - but in how many cases would the above be considered a brick?
If I wasn't such a stubborn son of a *****, I would have just called it a brick after the standard revive tricks failed

Theshawty said:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Click to expand...
Click to collapse
Well it happens my dude.....at least he took the time out to give a guide and explained how he fixed it just in case someone else does something similar
---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------
efrant said:
If it's not permanent, it's not, and never was, a brick.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
True....but most people would not know what to do in this situation and call it a day....at least he searched Google and fixed his problem. Wish more people were like him ya know
---------- Post added at 09:00 AM ---------- Previous post was at 08:56 AM ----------
rekrapg said:
True - but in how many cases would the above be considered a brick?
If I wasn't such a stubborn son of a *****, I would have just called it a brick after the standard revive tricks failed
Click to expand...
Click to collapse
Exactly I said most people would have called it a day.....ZOMGZ MA FONEZ NO LITE UPZ IT HARDSOFT BRICKED!! .....lol all joking aside man your like me I wouldn't have stopped until I was absolutely sure I needed them JTAG boys
Persistence pays off...remember that

Yup. In most cases, there's a way around a problem, you just have to dig until you find it

Congratulations
Saludos desde Ecuador

Though I don't want to have chance to perform your provided method, it's really good to know, in case....
Congratulation and thanks!

rekrapg said:
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
In step 6 you say choose omap, but which one? omap flash drive? omap p4460? also i cant install any of those it says it is not signed and it wont install, i tried booting in safe mode and no luck, i tried using the 'bcdedit /set nointegritychecks ON" , rebooted, no luck either
My galaxy nexus is not exactly bricked but i cant get into bootloader, recovery or fastboot , do you think this method could be useful to me?

Chad_Petree said:
In step 6 you say choose omap, but which one? omap flash drive? omap p4460? also i cant install any of those it says it is not signed and it wont install, i tried booting in safe mode and no luck, i tried using the 'bcdedit /set nointegritychecks ON" , rebooted, no luck either
My galaxy nexus is not exactly bricked but i cant get into bootloader, recovery or fastboot , do you think this method could be useful to me?
Click to expand...
Click to collapse
Choose the one closest to what displays on the device manager. I started with the OMAP Flash Drive one and it worked for me, but you can always choose the 'update driver' option and install another if required. Turn off User Account Control in Control Panel/Users and make sure you're on an admin account, as it may by default block the ability to install unsigned drivers, to be honest not sure on that one as it's always been first port of call for me on Win 7 (and Vista).
I also found this that might help: http://www.techspot.com/community/t...signed-drivers-in-windows-vista-7-x64.127187/

Wish I would have found this a week ago! The exact same thing happened to me, except I had been running a working JB ROM for a day or so.
Went jogging, was listening to music, came home, music stopped, screen wouldn't turn on with power button or USB cable with a charger or a computer, but there was a notification LED flashing. No amount of pressing and holding the power button would bring it back to life, so I pulled the battery. After that it was in the exact state your GNEX was in. Not even the vibrate when trying to power it up. After a few hours of charging and trying all sorts of things to breathe life into it (including a battery swap) I ended up returning it to the brick and mortar VZW store and they replaced it because I was under 2 weeks with the phone.
Thanks for posting!

I ran the OMAPFLASH_tuna on my GNex and now, I seem to be stuck at "Sending Data"(SEE last line in the image attached)
The values of 131072 has been like that for over 20 minutes and have not changed. What data is it sending and to who or where?
to those who've used this too, What should happen after this?
thanks...
{
"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 would be lying if I said I knew exactly what this wonderful tool is doing mate With mine, it ran through in like 30 seconds to completion. I ran it 3 times to be sure! I have 2 suggestions,
1. Sign up to those forums and ask the expert
2. If your device is already 'bricked', it may be worth just disconnecting, closing the CMD window, reconnect and re-run it.
I'm no expert on this application though, I simply found it, it worked for me, so I shared. So option 1 may be your best shot. It's quite likely the bloke who created the tool will be able to let you know the proper path to go down.
EDIT: I am at work atm, so I can't 're-run' it on my device to show you the screen - but I recall it comes up with a 'press any key to continue' prompt after completion (pressing any key just re-runs it).

Funny because another person on GSMHosting is experiencing the same problem and says that his just stops downloading... Just like mines and at the same stop too... hummm...

Updating AT&T OTA issues; need help sideloading

Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
{
"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"
}

If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.

This is exactly what I needed; not necessarily a hand-holding or step by step, but a path forward to investigate. Thanks!

So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
41rw4lk said:
If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.
Click to expand...
Click to collapse

westec2 said:
So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
Click to expand...
Click to collapse
With a locked bootloader you can flash an official firmware that is the same revision or newer. So in short, yes.

Hello! I ended up using the smart tool; it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool; it was the easiest way without root to get updated. Once I had the right drivers installed and it recognized bootloader mode, LMSA was really easy to use.

despree said:
it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool.
Click to expand...
Click to collapse
How did you get the "right drivers" and how did you install them? Does the PC download them automatically when you attach the phone or did you need to find them and manually install them?

Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.

New to updating here
despree said:
Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.
Click to expand...
Click to collapse
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot

omiCar said:
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot
Click to expand...
Click to collapse
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.

despree said:
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.
Click to expand...
Click to collapse
Hi, thank you for your quick response, I will be attempting to do this tonight or tomorrow, I will circle back with an update, again thank you !

Backup phone first with LMSA
That's what I had to do so it would stop hanging at 51%. Use LMSA backup feature first then upgrade

I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.

Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...

bdizzle1686 said:
Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...
Click to expand...
Click to collapse
You can take any flashing all, use a tool to merge the sparsed system images and mount the system img and pull it that way if you really need it

wrenhal said:
I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.
Click to expand...
Click to collapse
Answered my own question. The flash worked fine. I switched over to the log at 51% and watched it copying files and eventually it finished up and the phone rebooted to Oreo. All in all, if say it took only fifteen to twenty minutes.
Sent from my KIW-L24 using Tapatalk

despree said:
Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/help/how-to-manually-update-att-motorola-z2-t3879143

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?

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