Develop Bugs

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...

Jiayu G2S - "unofficial forum"

JIAYU G2S
{
"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 Jiayu G2S was released on January 1, 2013. It was a significant upgrade to the G2 with a lot of hardware changes. For the price, it had an impressive list of specifications:
MTK MT6577T ARMv7 Cortex-A9 Dual-core 1.2GHz processor
GPU: PowerVR SGX531
4 inch QHD IPS screen, 960x540 pixel display, OGS (One Glass Screen)
Dual SIM cards supporting GSM 850/900/1800/1900mhz & WCDMA 3G 2100mhz network (only one 3G slot)
1GB RAM / 4GB ROM
Supports up to 32gb class 12 microSD card (TF card)
8MP rear camera, 2MP front camera
Supports WiFi a/b/g & WiFi hotspot, Bluetooth with EDR & A2DP, GPS & AGPS
Android 4.1 OS (Jelly Bean), multi-language
FM Radio
Gravity Sensor, Proximity Sensor, Light Sensor, Magnetic Sensor, Gyroscopic Sensor
2200mah battery
Size: 125 x 61x 9.9mm
Weight: 145g with battery
Overall, I really like the look and feel of the phone. Except for the ear speaker hole, the front is one solid piece of glass, wrapped around with a very solid metal frame. The metal frame is not just a thin piece of sheet metal, but is cast metal, provides for complete rigidity for the whole phone, and should do a good job of protecting that large piece of screen glass. This also means that the phone has a bit of weight, but that feels good in my hand. Additionally, I like the more rectangular design of the phone and the more square edge down the sides that the flat metal frame provides. It is very easy to hold onto.
Call quality is very good for me. Reception seems on par with other phones I've used. The wifi might be a bit weaker than my Huawei G300, but it is fine. The screen is very nice to look at and very sensitive, but you should read below about the "jump screen" problem. You should also read below about potential problems with GPS connection issues. I've now owned two of these phones. The first had the jump screen problem, and was replaced under warranty. The replacement has terrible GPS pickup, but no jump screen problem.
The large battery means that I have no problem getting through a day of use, and I probably could use it for two days without a charge most of the time. (But I do not use the phone for gaming.) The phone runs most of the time at 1001mhz or 250mhz when on, and will only jump to 1200mhz in extreme conditions. "Deep sleep" mode is for when the screen is off, but the phone will run at 1001mhz when charging no matter if it is on and being used or not. That is an issue for phones based on this MTK chipset and not exclusive to the JY G2S.
Jiayu includes a few apps targeting the Chinese market for this phone, but other than that, the OS is mostly "vanilla" Android Jelly Bean (AOSP). The phone comes already rooted, so freezing or deleting unwanted apps is a simple solution for what you don't want. There are a number of modified roms available already, including the Lewa rom (http://www.needrom.com/phone-roms/jiayu/g2s/). But you should note that later hardware versions of this phone have different components. You should make a note of what the rom version is that came installed on your phone so that you know what hardware version you are using.
"Jump Screen" Problem Solved?:
Many of the first batch of phones were plagued with screen problems. Commonly referred to as the "jump screen" problem, the result is that when scrolling through screens of data, the screen just "jumps" to a different location without any apparent reason. The screen also "quivers" when touching it, even if you aren't moving your finger. Jiayu promptly acknowledged the problem and tried to correct it with a quick ROM update released on January 9, 2013. (The build number of the ROM is: G2S 20130108-104044.) This ROM update did seem to work for some, but for others the problem persisted.
At this point, I personally don't know if the problem has been completely solved in the manufacturing of subsequent batches of the phone. My phone had the problem, and flashing the new ROM did not solve it. I returned the phone for replacement under warranty and did receive a replacement phone that does not have the problem. So whether or not there still is a manufacturing problem, Jiayu can replace the phone with one that works. However, see below for the GPS connection problem that I now have.
GPS Connection Problems:
There are also a number of users here who are reporting difficulty with weak GPS fix. My GPS fix on my first phone was excellent, but my replacement phone is not good at all. It has been suggested to install "Faster GPS" from the Play Store, which will let you set your location. Also, you can look at this post from later in this thread for more information: http://forum.xda-developers.com/showpost.php?p=39975417&postcount=209. (Please post any solutions you discover in this thread.)
ROM Flashing:
One of my initial struggles was getting the official rom flashing tool to work. I finally got things going, and I hope I can help others who "just don't get it". So if you want some detailed instructions in English for how to flashing a new official ROM onto the Jiayu G2S, have a look at the second post. (If you are flashing a third-party rom, follow the rom builder's instructions.)
ClockworkMod Recovery:
"Thingbreaker" has provided us with a working CWM Recovery. Here's his post link: http://forum.xda-developers.com/showpost.php?p=37521066&postcount=28
There are two ways to flash the CWM Recovery image: using the ROM flashing tool (harder) or using Mobileuncle Tools (easier).
To use Mobileuncle Tools, install it from the Play Store (free). Copy the CWM Recovery image file to the root of your SD card, making sure there are no spaces in the filename. Run Mobileuncle Tools and choose Recovery Update. Choose the recovery image file that Thingbreaker provided.
To use the ROM flashing tool, you first you need to understand how to flash a complete rom as explained in the second post of this thread directly below. After you know how to do that, then look at this post to learn what is different about only flashing the recovery image: http://forum.xda-developers.com/showpost.php?p=37499848&postcount=23
Conclusion:
I do not recommend purchasing this phone. Period. Until Jiayu can do a better job of quality control, I don't recommend their products. There are other companies out there who's phones are only slightly more expensive, but who have a much better reputation for quality control.
Jiayu, if you are reading this, you need to do better! And you really need to improve your repair department as well. Sending me a replacement phone with a GPS problem causes me to wonder if you are using the "shuffle" method of passing around bad phones instead of repairing them. I'm NOT a satisfied customer.

“Unofficial” Guide to Flashing the Official Jiayu G2S ROM
Disclaimer: I’m just one guy who got this to work after a lot of trial and error. I’m only telling you how I did it. I don’t claim it will work for you. I don’t guarantee you won’t brick your phone by following these instructions. And you should understand that if you don’t bother to read carefully and do exactly what I say, you really can brick your phone. Also, it seems there has been an upgrade to some of the components in later versions of the phone released in March 2013, and you will want to verify which version of the phone you have before installing any roms. You should be able to check the rom build information for the date on your particular phone. This guide only describes how to flash the official rom from Jiayu for the G2S. If you intend to install some other third-party rom, please follow that rom builder's instructions.​
Pre-requisites:
You need a PC running Microsoft Windows 2000 or higher.
If you haven’t previously installed msxml 6.0 and .net Framework 4.0 or higher on you Windows PC, do so first. Get them directly from Microsoft. (I assume you know how to search.)
Download the following:
Latest Jiayu G2S ROM update; the rom I installed was the G2s_20130109-104044 stock rom: http://pan.baidu.com/share/link?shareid=157669&uk=839171988 (Note: the build number of the ROM after installation is: G2S 20130108-104044; don't be confused by the name of the file.) Use Google Translate if you need to see which button to push to start the download. Also note that there is a newer official rom for newer versions of the phone. The rom date is 20130306. I don't know what happens if you install the newer version on an older phone.
This zip file contains the Android USB driver, VCom drivers, SP Flash Tool, and a document of these instructions (ReadMe.doc): http://www.mediafire.com/?tc4q3wy5eabowhf
Unzip the files you downloaded and move/copy folders and files where they need to go:
Within the rom zip that you downloaded from the Baidu website, you can find the \G2s_20130109-104044 sub-folder. This folder contains the actual rom files (14 files). Move this entire folder onto your desktop. The reason for doing this is that there are folders within the zip file whose names contain characters that your version of Windows might not be able to read, even if you can see them in Windows Explorer (the filemanager). This will cause you trouble when you try to flash the rom.
After unzipping the driver and flash tool zip file, you will find the \USB-VCOM-Drivers folder with \INF and \SYS sub-folders. In the \INF folder there are three other sub-folders: \ 2K_XP_COM, \Vista, and \Win7.
Copy the \INF\cdc-acm.inf file into your C:\Windows\inf folder. (You may have to give permission to do this.)
Based on your version of Windows (2K-XP, Vista, Win7, 32-bit or 64-bit), locate the one correct usb2ser_????.inf file and copy it to your C:\Windows\inf folder. (You may have to give permission to do this.)
Copy both the \SYS\androidusb.sys and \SYS\usbser.sys into your C:\Windows\System32\driver folder. (You may have to give permission to do this.)
Install the drivers:
Plug your phone into your computer with a USB cable. If you had not previously installed the drivers, the system will start trying to install them.
If the system asks you to choose to install the drivers, click on “install the software automatically” and proceed.
If system is unsuccessful in locating and installing the drivers, you can try to go back and locate the drivers yourself by pointing to the individual files, but this should not happen if you properly copied the drivers over to your C:\Windows system folders.
BACKUP YOUR DATA NOW!
Proceeding beyond this point is going to mean that EVERYTHING on you phone is going to be deleted and a new system will replace it.
You have been warned!
Warning!
Attempting to install a rom that does not use the correct “scatter” file (see description below) will brick your phone. Don’t do it. If you aren’t sure a rom is made for your phone, don’t attempt to install it.
Install the updated ROM:
1. Turn off your phone, open the back, and remove the battery.
2. Plug your USB cable into your PC and phone. If your PC attempts to install drivers, let it finish.
3. Unplug your phone from the cable.
4. Start the SP Flash Tool program by clicking on the Flash_tool.exe file. If you get a security warning, allow it to run.
5. Click on the “Scatter-loading” button on the right side.
6. Browse to your \Desktop\G2s_20130109-104044 folder and choose the MT6577_Android_scatter_emmc.txt file. All other files will be chosen automatically.
7. Click on the “Firmware -> Upgrade” button.
8. Plug your USB cable firmly into the phone. The Flash Tool will automatically start flashing your new rom. Wait for it to finish and show you the green circle.
9. Unplug your phone from the cable.
Rebooting the phone:
1. Install your battery.
2. Very carefully, without touching the screen, push the power button.
3. Do not touch the phone as it boots!
4. After it has completed booting, you may again use your phone normally.

Following the advice that it might help if the phone is very cold when updating to the new rom, I tried putting it in the refrigerator. Unfortunately, that did not seem to help in my case. The phone still has the "jump screen" problem.
Of course, any other ideas would be appreciated as well.
Has anyone yet been successful in creating a Recovery mod (i.e. ClockworkMod Recovery)?

Tell Me Some Unofficial Way Of Hacking Based On Geograohical Location
Any Jealousy people Tell Me Some Unofficial Way Of Hacking Based On Geographical Location.

twrock: Make sure you do not have screen protector applied and you do not touch the screen during the first boot after flashing.

Thanks for the advice. But I'm not using a screen protector, and I am being very careful about not touching the phone. Nothing seems to help.
Sent from my G2S using xda app-developers app

Have you identified production date of your phone? Is there a sticker anywhere? We might come to a conclusion later on, of which date onward the factory has solved the problem... It might be a hardware problem after all.
Still waiting for mine to arrive...

hi there, for those who already have in their hands the g2s is it possible to give more reviews about its gps and the camera especially at night? thanks

Hi.
I have just created a ClockWorkMod recovery image for the Jiayu G2S.
I don't have the phone yet, it is still on its way, so I can't guarantee that it will work.
Download: http://db.tt/vFO4S6Mc
When flashing this recovery, use the same scatter file as for the stock rom.
If you don't have the scatter file here it is: http://db.tt/Z4TWPowQ
Please try it at your own risk, and give me feedback.

I received mine today. I am stunned. This thing is amazing. After all the HTC's I have this is a dream.
Mine doesn't seem to have the screen problem, but has the 20130108 firmware. I will wait a couple of days and see how it's running and the flash it.
CWM for this would be amazing and unabridged CyanogenMod would be even greater. Wonderful times!!!

fcsabika said:
Hi.
I have just created a ClockWorkMod recovery image for the Jiayu G2S.
I don't have the phone yet, it is still on its way, so I can't guarantee that it will work.
Download: http://db.tt/vFO4S6Mc
When flashing this recovery, use the same scatter file as for the stock rom.
If you don't have the scatter file here it is: http://db.tt/Z4TWPowQ
Please try it at your own risk, and give me feedback.
Click to expand...
Click to collapse
I'll give it a try.
What method did you use to create it? Did you use Koush's "builder"?
I also tried to make a CWM Recovery using the builder. The builder said it was successful, but the resulting CW recovery would not boot.
I'll let you know when I have the time to try it. Thanks.

Anyone know how to get rid of the Google search bar at the top of the standard Launcher? I'd guess that Google doesn't want us to be able to get rid of it.

sdssss said:
hi there, for those who already have in their hands the g2s is it possible to give more reviews about its gps and the camera especially at night? thanks
Click to expand...
Click to collapse
I don't know if my experience is much help. I live in Taiwan, so I suspect my GPS satellite locks were about the same as they would be in China. So for what it's worth....
My first GPS use locked in less than two minutes. I was outside in a parking lot on a clear day when I started. I got into the car after about 30 seconds and put the phone on the dashboard. It was locked in before the screen shut off (which is set at 2 minutes). I did not have Wifi connected, so no help from that. Subsequent to that first use, locking in took less than 15 seconds.
I haven't taken any pictures at night, so I can't help you there.
I'll mention here that if I decided to order this phone today, I'd find a way to get it straight from Jiayu. I ordered mine from Etotalk.com (and wasted money on their "Etotalk mod rom"), and they aren't being very helpful with aftersales follow up. I finally gave up on them and am now talking straight to Jiayu support. But I have to wait until after Chinese New Year to send it back. They said that they would not be able to replace the phone until after Chinese New Year anyway, so sending it back now would only mean I would be without the phone longer.

hello, i'm G2S first batch too, what do you mean about shaking problem? is it shake hard ? i got the problem while charging the phone, but if it's unplug, it's seems to be normal.
i'll try the new firmware from this thread, thanks for the link :laugh:
by the way, i've ported the CWM recovery for G2S, i'll upload it if you need it

For those who already have the phone, is the signal strong even if you are inside buildings?
I'm asking this because many users report that jiayu g3's signal is very week when you get indoor, and i'd like to know if it was corrected in this version.

sempracurtir said:
For those who already have the phone, is the signal strong even if you are inside buildings?
I'm asking this because many users report that jiayu g3's signal is very week when you get indoor, and i'd like to know if it was corrected in this version.
Click to expand...
Click to collapse
my phone is work normally even inside the buildings it depends on the network carrier, except you're in the basement
by the way, i've flashed the newest firmware from the page1, and the "jumpscreen" error while charging is now fixed. More stable touchscreen, thanks man :laugh:

Gps
fix ok, but not accurate.
The worst gps that I have had.
Solutions?
Hello
verbal

twrock said:
I'll give it a try.
What method did you use to create it? Did you use Koush's "builder"?
I also tried to make a CWM Recovery using the builder. The builder said it was successful, but the resulting CW recovery would not boot.
I'll let you know when I have the time to try it. Thanks.
Click to expand...
Click to collapse
Yes I have used the builder.
So did anyone try my CWM recovery?

fcsabika said:
Yes I have used the builder.
So did anyone try my CWM recovery?
Click to expand...
Click to collapse
Sorry, how can I install it?
I read your post yesterday but I didn't understand.
Can you explain me better?
Thanks.

lelepanz said:
Sorry, how can I install it?
I read your post yesterday but I didn't understand.
Can you explain me better?
Thanks.
Click to expand...
Click to collapse
You can install it the same way as the official rom.
See the second post by twrock.

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

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

Question is it possible to backup my phone with my current issue?

i need help making a backup of my phone, my screen is black so i can't see anything. my pc does recognizes it when connected.
p.s. haven't rooted my phone

testask123 said:
i need help making a backup of my phone, my screen is black so i can't see anything. my pc does recognizes it when connected.
p.s. haven't rooted my phone
Click to expand...
Click to collapse
does the phone still have touch working despite screen is black? Touch is required because you will need to enable Developer Options and then USB debugging. Afterwards, you should be able to control your device via scrcpy using a computer. Or, make file backups by leveraging ADB command "adb pull", though this would already be possible when you connect the device and choose "File transfer" on a window that appears.

TechnoSparks said:
does the phone still have touch working despite screen is black? Touch is required because you will need to enable Developer Options and then USB debugging. Afterwards, you should be able to control your device via scrcpy using a computer. Or, make file backups by leveraging ADB command "adb pull", though this would already be possible when you connect the device and choose "File transfer" on a window that appears.
Click to expand...
Click to collapse
i can't tell, i don't here or feel vibration.
if i can't access debug, can i not backup?
is there no program that can make one?

testask123 said:
i can't tell, i don't here or feel vibration.
if i can't access debug, can i not backup?
is there no program that can make one?
Click to expand...
Click to collapse
I have an idea but i may have to test first.
Is your phone stock or have you unlocked the bootloader?

TechnoSparks said:
I have an idea but i may have to test first.
Is your phone stock or have you unlocked the bootloader?
Click to expand...
Click to collapse
bootloader is not unlocked

testask123 said:
bootloader is not unlocked
Click to expand...
Click to collapse
Is the warranty still valid? If YES, then i cannot help you, because unlocking the bootloader may render the warranty void (but i am not sure, you may confirm with relevant Xiaomi service centres).
ignore everything. this is because there is nothing we can do without the authorization from adb, or choosing "file transfer" during USB connection when in the OS
i am sorry
edit: also because i totally forgot that unlocking the BL will definitely wipe the device, which defeats the purpose of this thread!

TechnoSparks said:
Is the warranty still valid? If YES, then i cannot help you, because unlocking the bootloader may render the warranty void (but i am not sure, you may confirm with relevant Xiaomi service centres).
ignore everything. this is because there is nothing we can do without the authorization from adb, or choosing "file transfer" during USB connection when in the OS
i am sorry
Click to expand...
Click to collapse
is there no trustworthy program that could back it up?

testask123 said:
is there no trustworthy program that could back it up?
Click to expand...
Click to collapse
With what i knew so far with [AOSP] Android, no, because there needs to be a user confirmation on the screen. I suppose maybe Xiaomi have some proper backup tools? (I guess)

Oh yeah, maybe an external display could work. Please wait while I try to gather some limited information

After some quick googling @testask123 , the Poco F3 does not support HDMI-out through the usb-c port. This looks to me like a dead end, and we won't be able to backup the data from the phone. Because as previously mentioned, in order to backup any meaningful data, the user have to interact with the screen for confirmations.
I actually under the assumption that you want to backup the device before sending it for warranty replacement. I also assume that your screen is broken in some way, but the device is functional, for example, you can receive calls. If you are not going to warranty claim the phone, then you may replace the screen at repair shops without needing to format your data at all, thus giving you access to everything on your device once everything is up and running.
Final question, does the touch screen still work despite the screen is black?

Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.

Renate said:
Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.
Click to expand...
Click to collapse
Could you go into details as to how to modify boot.img to enable adb?
I tried searching a bit but nothing came up

It's mostly changing prop.default in the image, maybe add something to start adbd earlier in the boot process.
Or making a rooted recovery.
But this is all based on being able to flash something, either in fastboot or at a lower level with EDL/MSM.

Renate said:
It's mostly changing prop.default in the image, maybe add something to start adbd earlier in the boot process.
Or making a rooted recovery.
But this is all based on being able to flash something, either in fastboot or at a lower level with EDL/MSM.
Click to expand...
Click to collapse
Ahhh I see , but why boot.img? It's rather difficult to modify for you gotta unpack ramdisk and all? ( I tried doing this long time ago but got stuck on how to repack properly x: )
System.img / vendor.img should be better targets for u can unsparse them ( make rw ) on PC and easily edit .prop files
It's a rly good idea

It's easier to pack something if you never unpack it.
imgutil.exe in my sig lets you modify boot images without taking it all apart.
Warning: Android moves on and many busy bees are working to make our lives more difficult.
If you have problem with imgutil.exe contact me about it.
Code:
C:\>imgutil.exe /v /x boot.img prop.default
C:\>my-fave-editor.exe prop.default
C:\>imgutil.exe /v /r boot.img prop.default
Just don't use some ignorant Windows editor like "Notepad" that uses \r\n.
I like Notepad++.
Also, with a boot image you can try booting it without flashing it.

TechnoSparks said:
After some quick googling @testask123 , the Poco F3 does not support HDMI-out through the usb-c port. This looks to me like a dead end, and we won't be able to backup the data from the phone. Because as previously mentioned, in order to backup any meaningful data, the user have to interact with the screen for confirmations.
I actually under the assumption that you want to backup the device before sending it for warranty replacement. I also assume that your screen is broken in some way, but the device is functional, for example, you can receive calls. If you are not going to warranty claim the phone, then you may replace the screen at repair shops without needing to format your data at all, thus giving you access to everything on your device once everything is up and running.
Final question, does the touch screen still work despite the screen is black?
Click to expand...
Click to collapse
it's hard to tell, maybe i should try to see if i can pull it of, but don't know the exact position of the usb setting in the dropmenu.
if someone could provide some screenshot, it might give me an idea where to tap.

Renate said:
Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.
Click to expand...
Click to collapse
i remember turning on wifi debugging, but dont know if that's still the case or even useful

testask123 said:
i remember turning on wifi debugging, but dont know if that's still the case or even useful
Click to expand...
Click to collapse
Well, try to connect. Is WiFi on? Do you know the IP address? Can you get it from the router? Can you ping it?
Code:
C:\>adb connect 192.168.1.?
("?" is not literally a question mark, put a small number in there.)

Renate said:
Well, try to connect. Is WiFi on? Do you know the IP address? Can you get it from the router? Can you ping it?
Code:
C:\>adb connect 192.168.1.?
("?" is not literally a question mark, put a small number in there.)
Click to expand...
Click to collapse
the ip from the phone?
sorry i'm not so knowledgeable about these things and wanted to make sure

{
"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"
}
Yeah, the IP of your phone.
If you're on your own router you can log in and see if your phone is there and what IP.
Now you know that my cheap Walmart tablet is on (local) IP 192.168.1.4