I flashed LCA43 with adb sideload eefea3292b364b67db746dc4131713605b8e8f76.signed-platina-LCA43-from-LDZ22D.eefea329.zip and everything wents very well.
Now I am in tests and tomorrow I leave a feed-back of the new version.
Thanks.
I download Bits Watch Face from Play Store and I am testing with the new Android Wear LCA43.
For first impression Bits Watch Face is awsome, I like it, very cool.
What was your flash-process?
Unlocked/locked Bootloader? Stock Firmware?
My adb sideload command always breaks things at 61% with an "Installation Aborted" (Error 7) when it is verifying the Image.
Thanks for your help
My flash process is adb sideload eefea3292b364b67db746dc4131713605b8e8f76.signed-platina-LCA43-from-LDZ22D.eefea329.zip
Previously I am in pure stock with locked bootloader, and I flash the new LCA43 with windows 10.
When I flashed it stops two or three minutes in 61% than I continues to 100% without any breaks.
I think you must wait at 61% until process continues.
Try flashing it with another usb port for example.
FYI
The old technique of forcing an ota update still works for a stock watch: Make sure you have the latest android wear app.
1. Reset the watch from settings
2. On the phone, erase the data from the android wear app.
3. Connect the watch to the app
After the watch syncs, it will ask if you want to update.
I have tried, flashing stock and sideloading, no dice, reflashing stock and locking bootloader then sideloading, again no dice, unlocking flashong stock once more relocking and trying ota, nothing flashes when ota tries to flash the lint gets to 15-25% theb flips to the dead Android for around 30-60 seconds before rebooting.
i tried multiple cables, pcs and operating systems (win7-10 linux Ubuntu and debian) and multiple downloads from seperate sources, nothing seems to want to give me this update..
Any help would be appreciated
freshlysqueezed said:
FYI
The old technique of forcing an ota update still works for a stock watch: Make sure you have the latest android wear app.
1. Reset the watch from settings
2. On the phone, erase the data from the android wear app.
3. Connect the watch to the app
After the watch syncs, it will ask if you want to update.
Click to expand...
Click to collapse
Thank you,it works
I have the new Android Wear 1.3 flashed at 28 hours ago and for now i am loving the new faces, and i like the battery optimization, in my case it consumes only 0.89% battery in one hour.
I have the screen off and micro off with an application.
LG G Watch have a new stable upgrade in my opinion.
Hi. What do you mean by micro off ?
Do you also keep fit off ?
Sent from my LG-D852 using XDA Free mobile app
ruben46_ said:
Thank you,it works
Click to expand...
Click to collapse
Tried this twice, stock with bootloader locked and both times it comes up with the dead android and reboots. Not sure what's wrong.
Sent from my Hitchhikers Guide to the Galaxy
Visegrad said:
Tried this twice, stock with bootloader locked and both times it comes up with the dead android and reboots. Not sure what's wrong.
Sent from my Hitchhikers Guide to the Galaxy
Click to expand...
Click to collapse
Did for me right now too. Maybe try to boot into recovery mode and flash it via ADB sideload.
For the user that ask me I mute the mic with an apk "mute wear mic" that I download, I think that is free.
I upgrade my to 1.3 with adb sideload command and it work at the first shoot.
I have also ended up with the dead android and tried both sideloading and the regular installing from watch. Tried with restoring the watch to stock and locked the bootloader but I am still ending up with a dead Android image then reboot..
steso90 said:
I have also ended up with the dead android and tried both sideloading and the regular installing from watch. Tried with restoring the watch to stock and locked the bootloader but I am still ending up with a dead Android image then reboot..
Click to expand...
Click to collapse
Yeah, it's weird. It's like I've lost recovery. I have flashed back to stock, locked the bootloader and try to go to recovery, dead android. unlocked bootloader, try to go to recovery from bootloader... dead android. I have used the restore tool to push recovery image on, everything says it went fine, try any method to get to recovery...dead android. I was able to flash the Mysterious Magic rom back on via his script with no issues, so not sure where the disconnect is, but for now I will stick with the rom since the battery life is great with that.
I've tried everything with no luck, LCA43 doesn't want to be installed on my watch.
I got the OTA, but when I press install it start installing until more or less the middle of the progress bar and then I get a dead android. I downloaded the OTA to do a sideload but it gets aborted at 61%. I formatted all the partitions and flashed the official images of LDZ22D, then tried both methods, with the same result.
Does anyone have the link to the official img? Because the OTA doesn't seem to work for me.
Sent from my Nexus 4 using XDA Free mobile app
JanusDC said:
I've tried everything with no luck, LCA43 doesn't want to be installed on my watch.
I got the OTA, but when I press install it start installing until more or less the middle of the progress bar and then I get a dead android. I downloaded the OTA to do a sideload but it gets aborted at 61%. I formatted all the partitions and flashed the official images of LDZ22D, then tried both methods, with the same result.
Does anyone have the link to the official img? Because the OTA doesn't seem to work for me.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
It's not "aborted" at 61% (or does it say Aborted?), only takes a long freaking time till it hits 100% from then on. Just wait 5 minutes or so once you see 61% on your CMD window.
Also I posted the update in a separate thread here, I think under General.
EpicLPer said:
It's not "aborted" at 61% (or does it say Aborted?), only takes a long freaking time till it hits 100% from then on. Just wait 5 minutes or so once you see 61% on your CMD window.
Also I posted the update in a separate thread here, I think under General.
Click to expand...
Click to collapse
If I boot into recovery, I get the dead android, and ADB can't see my device when this happens, so I can't sideload your update file, so I tried installing TWRP recovery and installing that file from there, but it fails straight away from TWRP.
How did you get ADB to see you device when you have the dead android showing?
Thank you =)
Is there any way to make the ota flashable through twrp?
hugoprh said:
If I boot into recovery, I get the dead android, and ADB can't see my device when this happens, so I can't sideload your update file, so I tried installing TWRP recovery and installing that file from there, but it fails straight away from TWRP.
How did you get ADB to see you device when you have the dead android showing?
Thank you =)
Click to expand...
Click to collapse
Boot into bootloader, select recovery there, once the screen turns to the LG logo instantly swipe from left upper to right lower corner as fast and often as you can, after a few seconds you should see a menu on the stock recovery screen. Then select the adb sideload option and send it from your PC via "adb sideload zipnamegoeshere.zip"
EpicLPer said:
Boot into bootloader, select recovery there, once the screen turns to the LG logo instantly swipe from left upper to right lower corner as fast and often as you can, after a few seconds you should see a menu on the stock recovery screen. Then select the adb sideload option and send it from your PC via "adb sideload zipnamegoeshere.zip"
Click to expand...
Click to collapse
No luck, tried it, booted into the bootloader, selected recovery and once the screen turned to the LG logo, I swipe from left upper to right lower corner as fast and often as I could, went again into the dead android screen and ADB still unable to see the device.
Isn't the swipe from upper left to lower right, to boot into the bootloader? I can do that, but whilst booting into recovery, from the bootloader, it just goes to the dead android.
Also tried to do a factory reset to the watch, cleared the data of the Android App on the phone, connected the watch and update fails when the progress bar is at about 20%
if any one could get their hands into the full ROM file, that would be awesome.
Any other ideas are welcome =)
And thank you for your help
Related
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
laxsrbija said:
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
Click to expand...
Click to collapse
did you try reflashing your recovery via Odin?
SuperSU
laxsrbija said:
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
Click to expand...
Click to collapse
First of all what are co workers doing messing with your phone I would seriously not be happy!! screen lock comes to mind!
As the above post said flash another recovery in odin I recommend Philz recovery,backup your data in recovery then factory reset if that does not work flash another rom via recovery or return to stock with odin. You can also boot into recovery with adb but I would try above first.
Then charge your co-worker for all the time wasted trying to fix phone
Thank you so much for the idea, I just tried this and it worked! After flashing new recovery via ODIN, I'm now able to access my phone. There was no need to flash the ROM again, as it was fine, the only problem was with the recovery.
And I still have my data!
Thank you very much again, cheers :laugh:
tallman43 said:
First of all what are co workers doing messing with your phone I would seriously not be happy!! screen lock comes to mind!
Click to expand...
Click to collapse
He's actually a good guy and I'm sure he didn't do it on purpose. He told me that he was playing a game and he tried to add more coins using GameCIH. Then the prompt to allow root access to the app came up along with a notification to update the SU binary. He said he pressed that button by mistake. I wasn't mad at the guy, I was only upset that I may lose my data.
laxsrbija said:
Thank you so much for the idea, I just tried this and it worked! After flashing new recovery via ODIN, I'm now able to access my phone. There was no need to flash the ROM again, as it was fine, the only problem was with the recovery.
And I still have my data!
Thank you very much again, cheers :laugh:
Click to expand...
Click to collapse
you are welcome! glad to see that it works again.
How long did everyone's initial update take? Mine has said "Downloading update" for about 1 hour so far...
About 5 minutes
Thanks, I will try restarting it again >_>
draco259 said:
Thanks, I will try restarting it again >_>
Click to expand...
Click to collapse
How fast is your internet?
joshuabg said:
How fast is your internet?
Click to expand...
Click to collapse
Just did a speed test on my phone and get 49.6 mbps download. My router's traffic monitor isn't showing any activity on the N9 for some reason.
EDIT: I am going to reboot my router to see if that does any good.
draco259 said:
Just did a speed test on my phone and get 49.6 mbps download. My router's traffic monitor isn't showing any activity on the N9 for some reason.
EDIT: I am going to reboot my router to see if that does any good.
Click to expand...
Click to collapse
Did you reboot your Nexus 9 yet?
3 times over the last few hours, just rebooted my router as well.
Took mine about 10 minute to download over a 3G connection while I was in WalMart. The install process was about 3 minutes.
Well this is interesting....After disconnecting from my WiFi and tethering from my phone, immediately after it connected, the tablet said it has finished download the update, and it rebooted to install it. Whatever the case the update is about done installing, then I will be running some wifi speed tests on it. Maybe the Google servers were overloaded or something.
My update downloaded fast but it was stuck on checking connection for 3-4 minutes
Sent from my Nexus 7 using XDA Free mobile app
Initial Update Failed in Mine
I just received my Nexus 9, and started the initial setup. Download took like 5 minutes as stated in download, but when it reboots into recovery mode to apply the update, when it is around 30%, it just stops and show the android with the red exclamation mark and the label "Error". After that, tablet reboots and asks again for the update. I was not able to find someone with the same issue, called Google Play support, and they just advice to me, that I have to return it
You guys have any advice before I return it back to Google?:crying:
rabarkar said:
I just received my Nexus 9, and started the initial setup. Download took like 5 minutes as stated in download, but when it reboots into recovery mode to apply the update, when it is around 30%, it just stops and show the android with the red exclamation mark and the label "Error". After that, tablet reboots and asks again for the update. I was not able to find someone with the same issue, called Google Play support, and they just advice to me, that I have to return it
You guys have any advice before I return it back to Google?:crying:
Click to expand...
Click to collapse
Can you boot into recovery and do a factory reset?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Can you boot into recovery and do a factory reset?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes I can, and I have done factory reset several times. It just starts the process again, download the update and fail again. Also downloaded the factory image, and tried to run the update with the zip included in it, but the problem trying to flash system.img (reported in here http://forum.xda-developers.com/nexus-9/help/factory-image-flash-t2929019) does not allow me to proceed. Anyway, the bootloader is locked, and because I can not even get to the home screen in android, I'm not able to fastboot oem unlock, and therefore, can not flash directly the images. Have no idea what else to do...
---------- Post added at 10:37 PM ---------- Previous post was at 10:27 PM ----------
rabarkar said:
Yes I can, and I have done factory reset several times. It just starts the process again, download the update and fail again. Also downloaded the factory image, and tried to run the update with the zip included in it, but the problem trying to flash system.img (reported in here http://forum.xda-developers.com/nexus-9/help/factory-image-flash-t2929019) does not allow me to proceed. Anyway, the bootloader is locked, and because I can not even get to the home screen in android, I'm not able to fastboot oem unlock, and therefore, can not flash directly the images. Have no idea what else to do...
Click to expand...
Click to collapse
The only thing I have not tried, is to install the update directly from fastboot, but I will need to get or find where that 297.9 MB file is located, so I can try that.
Does anybody happens to have the link or the update.zip file, so I can try doing it from fastboot?
I appreciate the help guys!
You can just use the Nexus factory images to reetore it via fastboot
KMyers said:
You can just use the Nexus factory images to reetore it via fastboot
Click to expand...
Click to collapse
I tried, but flashing the update in the factory image throws an error, which has been reported here in XDA. The solution is flash directly all img files contained in the package, but as I has not been able to go into Android, and check this new damned "Allow unlock bootloader" option in Developer section, I'm not able to unlock the bootloader, neither to flash anything using fastboot.
EDIT - Google support was not able also to guide me with futher troubleshooting. They will replace the tablet with a brand new
Pls help me root my zte obsidian running android 5.1 Model NO. Z820
I need help too
I also have ZTE obsidian tmobile and really want to root it i cant do much because it only comes with 4gb of space and i cant move apps to the SD card till i root Please help find a root
yeah same issue here all say that it cant after like 10-15 mins its just like nope sry
have you used this
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Yes, I tried. Its not working.
Is there any other way. I am desperate. It doesnt allow to move the Apps to SD card. There is no way. Locked in 4GB
I have a z820 in need of root as well. I've tried everything, including the link up there, and so far.....nope. Nothing. No apps to SD for me either.
Zte can't root for ****!!!!
I'm so mad because I really tried everything even a computer won't let me tried everything there to like why would the make a zte that can't even move your games or pictures or music to your SD card knowing danm well everybody gone need like we only got 4g that's nothing so what are we so posted to do delete stuff that we like.to trade for the other that we really don't need **** I'm pissed right now I know y'all are to but if anybody finds something please send me the info or con me by [email protected] thank you:good:
Needs update
This Phone really needs an update, it reboots and sucks, we can't even get into fastboot or anything to try to unlock the bootloader someone needs to make this possible because who in the hell uses only 4gb of storage, apps are so big and you can only download like 3 apps then you have to get rid of something if you want another app and its dumb so please someone..HELP US :crying:
Throwing my post up here so I can follow. Need root bad on this thing. I am using lite versions of every app. Lol
Same problem w/ ZTE obsidian..tCan't move to SD card. Anybody figure somethcing out yet?
I've gotten Kingroot to attempt to root it once and the results varied. Usually got 16% but the highest was almost 30% but I can't even get kingroot to even root it anymore.
The phone is not going into fastboot at all. I think the bootloader is locked. The phone will never be rooted.
I might of found a way, but it's untested so, proceed at your own risk, I am not responsible if your phone becomes bricked.
Enable developer mode and tick "OEM Unlocking" in the developer menu
Download SuperSU update zip from Chainfire's site and put it on your sdcard (internal won't work)
Power off your phone and hold power and volume up
Select recovery, wait for the android with the lid open to show up
Hold power and volume up for a couple seconds and let go
A menu should pop up, if not try again until it does
Select "update from sdcard"
Select the SuperSU zip
Let it flash the zip (shouldn't take long)
Choose reboot
See if SuperSU is installed and test that it works
Again, this is untested and would need a couple of people testing it to make sure it works flawlessly, so if this worked, please post that it did.
Nope. Thank you though.
picsles said:
Nope. Thank you though.
Click to expand...
Click to collapse
Any type of error happen or did it not allow it to flash at all?
I can't even get to recovery. Gives me the choice then goes to dead android guy.
Sent from my LGL21G using Tapatalk
Musicmanmike said:
I can't even get to recovery. Gives me the choice then goes to dead android guy.
Sent from my LGL21G using Tapatalk
Click to expand...
Click to collapse
You have to hold down power and vol up for like 2 seconds when you get to the dead android, then you'll get the recovery menu.
When I try to install the update package, I get 'opening update package' followed after less than a second by 'installation aborted'.
I powered down from the Developer Options screen with OEM unlock turned on when trying to update - it appears to turn off during boot as it is off again on restart.
Any suggestions? I looked at the logs that are visible from the recovery screen but they did not seem to have anything useful. Are there logs I can retrieve via ADB to see what the issue is?
My phone has build B18.
Kurrelgyre said:
When I try to install the update package, I get 'opening update package' followed after less than a second by 'installation aborted'.
I powered down from the Developer Options screen with OEM unlock turned on when trying to update - it appears to turn off during boot as it is off again on restart.
Any suggestions? I looked at the logs that are visible from the recovery screen but they did not seem to have anything useful. Are there logs I can retrieve via ADB to see what the issue is?
My phone has build B18.
Click to expand...
Click to collapse
OEM Unlocking is always on for me even after restarts but I haven't tried to flash SuperSU yet. You might wanna get a logcat while doing it and post it here to see if anyone knows what the problem is. I have an older build of the phone (B03) but I dunno if it matters or not.
EDIT: Also every new Kingroot build allows you to attempt to root it for like 2 days and then it just can't for some reason but the thing with 18% still happens.
LUModder said:
You might wanna get a logcat while doing it and post it here to see if anyone knows what the problem is. I have an older build of the phone (B03) but I dunno if it matters or not.
Click to expand...
Click to collapse
The logcat I am familiar with is in ADB. The only way I can find to access the phone from recovery with ADB is to select the flash from ADB option, which puts the phone in sideload mode where you can't pull data off. I was unsure if trying to load the ZIP that way would brick the phone so I haven't tried it.
I also tried using Fastboot and it doesn't recognize the phone at any time.
Is there another way to capture what is happening with the update?
I tried selecting restart in bootloader from the recovery menu with the phone connected to the PC. It stayed at the ZTE splash screen for over 10 minutes but neither fastboot nor ADB was able to communicate with it. I tried various key combinations without effect and finally ended up pulling the battery. Maybe it just froze up during boot for some reason.
I have tried every one-touch root I can find, none of them work. All the manual guides start with unlocking the bootloader - which I can't find any info on for this model. Based on the partition info, it's definitely locked: it has 27 (!) partitions including names like seccfg and oemkeystore. Is this normal for a lollipop device?
So I rooted my phone using king root and everything was working fine up until I tried to switch from kingroot to super su using super sume. After that my phone just reset and at first was endlessly restarting, after shutting it off and back on I was able to get it to stop endlessly booting but ran into a different issue. The phone boots up and reaches the "android is starting... Starting apps." Screen and doesn't go anywhere past that. I went into recovery mode and preformed a data wipe to see if that would work and the problem still persists. I am in fact running on stock no clockwork recovery or anything of that nature. If anyone can help that would be great! ?
123carlos123darkred said:
So I rooted my phone using king root and everything was working fine up until I tried to switch from kingroot to super su using super sume. After that my phone just reset and at first was endlessly restarting, after shutting it off and back on I was able to get it to stop endlessly booting but ran into a different issue. The phone boots up and reaches the "android is starting... Starting apps." Screen and doesn't go anywhere past that. I went into recovery mode and preformed a data wipe to see if that would work and the problem still persists. I am in fact running on stock no clockwork recovery or anything of that nature. If anyone can help that would be great! ?
Click to expand...
Click to collapse
Just let Android start apps. It might take 5 to 10 minutes.
me tooo
123carlos123darkred said:
So I rooted my phone using king root and everything was working fine up until I tried to switch from kingroot to super su using super sume. After that my phone just reset and at first was endlessly restarting, after shutting it off and back on I was able to get it to stop endlessly booting but ran into a different issue. The phone boots up and reaches the "android is starting... Starting apps." Screen and doesn't go anywhere past that. I went into recovery mode and preformed a data wipe to see if that would work and the problem still persists. I am in fact running on stock no clockwork recovery or anything of that nature. If anyone can help that would be great!
Click to expand...
Click to collapse
im in the same boat as you.
Damn....................
Im in the same hole as all of you or at least was....
So the problem with this is that these rooting programs such as kingroot and Kingoroot arent compatible with a lot of devices that aren't popular such as alcatel phones for instance....... although it is available for higher versions fortunately. The glitch that we have all had is due to trying to use 2 rooting programs (NEVER TRY THIS!!!!!!!) on one device and interference when booting up causes this annoying bootloop. Im assuming that no one here has managed to unlock the bootloader, so what you must do is plug your phone into a pc via usb and then try to download this firmware:
drive.
google.
com/open?id=
0BwBw9a_
6fkKUMmpWWno0S2ljTjA
Justt put it all together and download the firmware afterwards.... the pc must detect the phone first so this program can detect and install the drivers. Requires a format tho, so take that in mind. Hope it works for you guys......
Hello xda family
I got poco f1 for less than a month now, recently got notification of 10.3.7 update which was 1.8G in size, followed instructions and after update was completed and phone was restarted, the phone is in unusable condition, apps don't fully work, update app gives white screen then goes unresponsive, screen doesn't go off and drains super quickly.
I did some research and it doesn't seem to be a global issue, so is there a way to restore functionality on the phone?
I did some research and since update app doesn't work post-update, I can't use it to reinstall rom, so for fast boot restore I found out I have to unlock boot loader which takes 72 hours that I can't use the phone. Is there any way to restore to old firmware, uninstall update, reinstall without unlocking bootloader?
I'm desperate for ideas guys
My WiFi is not working properly after the update. It gets connected but I can't browse anything
Does anyone have same issue
aatkco said:
Hello xda family
I got poco f1 for less than a month now, recently got notification of 10.3.7 update which was 1.8G in size, followed instructions and after update was completed and phone was restarted, the phone is in unusable condition, apps don't fully work, update app gives white screen then goes unresponsive, screen doesn't go off and drains super quickly.
I did some research and it doesn't seem to be a global issue, so is there a way to restore functionality on the phone?
I did some research and since update app doesn't work post-update, I can't use it to reinstall rom, so for fast boot restore I found out I have to unlock boot loader which takes 72 hours that I can't use the phone. Is there any way to restore to old firmware, uninstall update, reinstall without unlocking bootloader?
I'm desperate for ideas guys
Click to expand...
Click to collapse
sir what do you mean "unusable condition"
did you buy used Poco ?
anyways! since your BOOT is locked! you cannot use TWRP,
download the recovery rom from https://mirom.ezbox.idv.tw/en/phone/beryllium/ , 1.8gb, rename the file to "update.zip" , put it in internal storage "download" folder, goto DOWNLOADER app, call the update from internal storage (right side top, 3 dots) and select "update.zip" file and apply! the device should boot in to MIUI RECOVERY and apply the update.... REBOOT!
if this doesn't help... then
ASSUMING YOU HAVE ALL THE QUALCOM DRIVER INSTALLED!
downlaod MI FLASHER,
download miui10.3.7 FASTBOOT ROM (2.6BG) FROM https://mirom.ezbox.idv.tw/en/phone/beryllium/
and boot device in to FASTBOOT (green android bot on screen) ,
extract, and then further extract fastboot rom, until u see folder name "images" , open miflasher, click SELECT and POINT it to IMAGES folder,
connect poco to your pc , click button "FLASH ALL" (only) and hit FLASH (or START), you will see slow progress bar (green) and full rom will be flashed!
FIRST REBOOT WILL TAKE TIME
YOU WILL LOOSE ALL YOUR DATA
inshallah it will be okay now!
call for 72 hour unlock time! if you wana root your poco! but IF YOU DON'T KNOW WHY SHOULD YOU ROOT? then probably you should not unlock your device
best of luck!
aatkco said:
Hello xda family
I got poco f1 for less than a month now, recently got notification of 10.3.7 update which was 1.8G in size, followed instructions and after update was completed and phone was restarted, the phone is in unusable condition, apps don't fully work, update app gives white screen then goes unresponsive, screen doesn't go off and drains super quickly.
I did some research and it doesn't seem to be a global issue, so is there a way to restore functionality on the phone?
I did some research and since update app doesn't work post-update, I can't use it to reinstall rom, so for fast boot restore I found out I have to unlock boot loader which takes 72 hours that I can't use the phone. Is there any way to restore to old firmware, uninstall update, reinstall without unlocking bootloader?
I'm desperate for ideas guys
Click to expand...
Click to collapse
try to hard reset your phone. press vol up + power button simultaneously until recovery comes up. then reset