Please help me understand what went wrong and a solution will really be appreciated. I recently flashed using this after being on Resurrection ROM. And i did so because i had a mega battery problem and wanted to see if either will solve the problem. My phone is still semi-usable and i need to keep it connected to a charger if i do intend to use it while preventing it from shutting itself down because of the battery problem.
{
"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"
}
smlamch said:
Please help me understand what went wrong and a solution will really be appreciated. I recently flashed using this after being on Resurrection ROM. And i did so because i had a mega battery problem and wanted to see if either will solve the problem. My phone is still semi-usable and i need to keep it connected to a charger if i do intend to use it while preventing it from shutting itself down because of the battery problem.
Click to expand...
Click to collapse
For the battery: go back to that battery thread @Vcek posted a method to help the battery problem. I thanked him 2 posts above your post.
As for your current issue, I'm not sure. Try a non-blur stock factory image or try RR again would be my guess.
smlamch said:
Please help me understand what went wrong and a solution will really be appreciated. I recently flashed using this after being on Resurrection ROM. And i did so because i had a mega battery problem and wanted to see if either will solve the problem. My phone is still semi-usable and i need to keep it connected to a charger if i do intend to use it while preventing it from shutting itself down because of the battery problem.
Click to expand...
Click to collapse
What phone do you have?
Was the reflash successful? This ota update was automatic or sideloaded?
Tapatalkkal küldve az én XT1650 eszközömről
Benoe said:
What phone do you have?
Was the reflash successful? This ota update was automatic or sideloaded?
Tapatalkkal küldve az én XT1650 eszközömről
Click to expand...
Click to collapse
Moto Z. I updated it directly, not sideloaded.
The re-flash was successful but somehow OTA don't work.
I'm not sure if the phone battery problem is genuine or just a software bug. I really wish someone would up a link of a firmware to be re-lock and flash the phone to stock.
Achi Shukuteki said:
For the battery: go back to that battery thread @Vcek posted a method to help the battery problem. I thanked him 2 posts above your post.
As for your current issue, I'm not sure. Try a non-blur stock factory image or try RR again would be my guess.
Click to expand...
Click to collapse
I couldn't locate the post you were referring to. Can you please link it here? Please.
smlamch said:
really wish someone would up a link of a firmware to be re-lock and flash the phone to stock.
Click to expand...
Click to collapse
The method you linked (and presumably did) contains exactly this. A firmware you can relock your phone with.
Are you sure that you downloaded the full ~2,3GB? Wasn't any error during the reflash?
It was working on a reteu XT1650-03 without issues.
Benoe said:
The method you linked (and presumably did) contains exactly this. A firmware you can relock your phone with.
Are you sure that you downloaded the full ~232GB? Wasn't any error during the reflash?
It was working on a reteu XT1650-03 without issues.
Click to expand...
Click to collapse
I downloaded it twice for it failed the first time. I believe it's the correct version.
Whenever i tried re-locking using fastboot oem lock command i get the message that i need to Allow OEM Unlocking under Developer Option. But weirdly that option is greyed out on the phone.
Benoe said:
The method you linked (and presumably did) contains exactly this. A firmware you can relock your phone with.
Are you sure that you downloaded the full ~232GB? Wasn't any error during the reflash?
It was working on a reteu XT1650-03 without issues.
Click to expand...
Click to collapse
Can you please help me out with the steps that you're familiar with. I mean relocking and flashing the phone to stock. Please.
smlamch said:
Can you please help me out with the steps that you're familiar with. I mean relocking and flashing the phone to stock. Please.
Click to expand...
Click to collapse
You should ask in the other thread, my phone is unrooted, locked, reflashed only to get better battery life.
Benoe said:
You should ask in the other thread, my phone is unrooted, locked, reflashed only to get better battery life.
Click to expand...
Click to collapse
Okay. I'm gonna give flashing the phone another go.
smlamch said:
I couldn't locate the post you were referring to. Can you please link it here? Please.
Click to expand...
Click to collapse
From: @Vcek
I read somewhere here on the forums the instructions for resetting battery stats for Moto Z :
Hold power button until screen turns off
Enter bootloader by holding vol down
Turn off phone and keep it in the charger for 1-2 hours AFTER it reach 100%
Can anyone with a horrible battery life try this and tell us if there's any difference, because I couldn't tell if I was getting better battery
Related
So, last night I decided to update to one of the CM 10.1 nightlies. I haven't updated in a while and thought why the heck not? So I used the option built in the Settings app to update. I pressed download and waited for it to finish, then hit install and went to sleep while it installed. When I woke up I had no signal. Not even 2g. No calls, texts, data, you name it. Gone.
So I have spent at least 6 hours re installing old versions and scouring the internet and no one has an issue exactly like mine.
Here's a screenshot of what the settings look like:
{
"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"
}
This might be an obvious question but have you tried reflashing one of the available modems?
JBeXX said:
This might be an obvious question but have you tried reflashing one of the available modems?
Click to expand...
Click to collapse
Thanks for the quick reply. No I haven't tried that yet actually. I can't find anything on google. Could you point me in the direction to flashing a modem?
Lepryy said:
Thanks for the quick reply. No I haven't tried that yet actually. I can't find anything on google. Could you point me in the direction to flashing a modem?
Click to expand...
Click to collapse
Just flash in recovery. Probably best to use the newer which is the VRALL4. If this doesn't fix it you may want to try a clean flash with a full wipe.
http://forum.xda-developers.com/showthread.php?t=2108510
JBeXX said:
Just flash in recovery. Probably best to use the newer which is the VRALL4. If this doesn't fix it you may want to try a clean flash with a full wipe.
http://forum.xda-developers.com/showthread.php?t=2108510
Click to expand...
Click to collapse
Wait why would I use the VRALL4 and not the VRALLJB?
Lepryy said:
Wait why would I use the VRALL4 and not the VRALLJB?
Click to expand...
Click to collapse
It's the newer of the 2. It was part of the first vzw ota after release.
JBeXX said:
It's the newer of the 2. It was part of the first vzw ota after release.
Click to expand...
Click to collapse
Alright, here goes nothing. I'll post back the results.
JBeXX said:
It's the newer of the 2. It was part of the first vzw ota after release.
Click to expand...
Click to collapse
Umm. So it seems this update did a lot more than mess up my data. It completely wiped my Recovery and removed my Play Store completely. I have no way to even flash this modem.
Lepryy said:
Umm. So it seems this update did a lot more than mess up my data. It completely wiped my Recovery and removed my Play Store completely. I have no way to even flash this modem.
Click to expand...
Click to collapse
Very odd. What recovery were you using? I'm not on cm 10.1 so I'm not familiar with the updater but did it give you options to wipe any data or caches? And did you reflash gapps after updating?
If you can get a wifi connection you could always try and flash TWRP through the goo manager app. Just a thought.
JBeXX said:
Very odd. What recovery were you using? I'm not on cm 10.1 so I'm not familiar with the updater but did it give you options to wipe any data or caches? And did you reflash gapps after updating?
If you can get a wifi connection you could always try and flash TWRP through the goo manager app. Just a thought.
Click to expand...
Click to collapse
I get an error when using the goo manager app. It says no current recovery installed. I am seriously ****ing stuck. Just one harmless update has demolished all the stuff on my phone.
Lepryy said:
I get an error when using the goo manager app. It says no current recovery installed. I am seriously ****ing stuck. Just one harmless update has demolished all the stuff on my phone.
Click to expand...
Click to collapse
You should be able to install recovery from the goo app. Open the all, then hit menu, then install openrecoveryscript. Confirm and see if will flash it.
Had this problem many of times on a gs3.
Calm down, I may be able to help you.
In the settings picture you posted. The my phone number was out of sight.
If the spot said Unknown.
You may be in luck.
But anyways do this either way.
Make sure you back up any thing you don't want to lose.
Boot into download mode.
Flash a stock unrooted official version. I believe this will also flash the modems and radio as well.
Check your signal and phone settings now.
I would expect nothing has changed signal wise.
But if you still have problems you open up dialer and call this phone number
*2767*3855#
Now your phone will cook up some magic and everything will be like the day you opened the box
However if this does not work, I would consider a new sim card (free at Verizon), try and do some more research
Or accept the fact you may have a hardware problem.
Feel free to pm me to let me know how it goes.
God bless the American people.
MAC address's wifi and bluetooth, imei are here but I have reflashed stock rom but still no luck, any solutions?
kennguy said:
MAC address's wifi and bluetooth, imei are here but I have reflashed stock rom but still no luck, any solutions?
Click to expand...
Click to collapse
Have you tried flashing the att JB radio? (look for it in the general section there is thread with different radios(modems) you can try.
luisoman2000 said:
Have you tried flashing the att JB radio? (look for it in the general section there is thread with different radios(modems) you can try.
Click to expand...
Click to collapse
Hi mate, no luck, any solutions?
Are you 100% sure airplane mode is not activated? I know it sounds dumb but might be the reason if everything else seems working fine.
kennguy said:
Hi mate, no luck, any solutions?
Click to expand...
Click to collapse
If you have an EFS backup, you might want to restore it.
jimbo77 said:
Are you 100% sure airplane mode is not activated? I know it sounds dumb but might be the reason if everything else seems working fine.
Click to expand...
Click to collapse
Yes,,, airplane mode is off... wifi is strange. When I turn it on to scan wifi but wifi automatically switch off.
kennguy said:
Yes,,, airplane mode is off... wifi is strange. When I turn it on to scan wifi but wifi automatically switch off.
Click to expand...
Click to collapse
When you flashed back to stock, did you do it by CWM/TWRP or LGNPST?
I'd recommend LGNPST (made a backup of your internal sd, it will be wiped out) and see if the problem persist.
jimbo77 said:
When you flashed back to stock, did you do it by CWM/TWRP or LGNPST?
I'd recommend LGNPST (made a backup of your internal sd, it will be wiped out) and see if the problem persist.
Click to expand...
Click to collapse
I revert back to stock by this guide: http://forum.xda-developers.com/showthread.php?t=2668412
... but the problem persist... I think may be is a hardware problem...
kennguy said:
I revert back to stock by this guide: http://forum.xda-developers.com/showthread.php?t=2668412
... but the problem persist... I think may be is a hardware problem...
Click to expand...
Click to collapse
I'd say that only option should be to restore the EFS backup. You should have that when first unlocked bootloader with FreeGee
jimbo77 said:
I'd say that only option should be to restore the EFS backup. You should have that when first unlocked bootloader with FreeGee
Click to expand...
Click to collapse
But I did not backup EFS, any solutions except restoring EFS mate?
kennguy said:
But I did not backup EFS, any solutions except restoring EFS mate?
Click to expand...
Click to collapse
Well my only idea right now if for you to get a radio log from the phone and then share it to see if we can spot anything out of usual that might be affecting your phone's connectivity settings.
You can use this app to get the desired logs
http://forum.xda-developers.com/showthread.php?t=1123129
I'll recommend you to try to reproduce the steps so the app can capture the appropriate log, after that share what you get
jimbo77 said:
Well my only idea right now if for you to get a radio log from the phone and then share it to see if we can spot anything out of usual that might be affecting your phone's connectivity settings.
You can use this app to get the desired logs
http://forum.xda-developers.com/showthread.php?t=1123129
I'll recommend you to try to reproduce the steps so the app can capture the appropriate log, after that share what you get
Click to expand...
Click to collapse
OK, I'll send you the log later...but before that I got issue "HW was reset detected".
{
"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"
}
And I tried to back to stock rom then I got no wifi, bluetooth, signal but IMEI is not null. After that, I unlocked bootloader, flash recovery, tried to wipe data and got this issue:
kennguy said:
OK, I'll send you the log later...but before that I got issue "HW was reset detected".
View attachment 2689212
And I tried to back to stock rom then I got no wifi, bluetooth, signal but IMEI is not null. After that, I unlocked bootloader, flash recovery, tried to wipe data and got this issue:
View attachment 2689210
Click to expand...
Click to collapse
The first screen is due to a Kernel Crash, are you running a custom kernel on your phone? I've got that with a few custom Kernels and if that's the case then probably the kernel modules are not compatible with the phone software. Can you flash for example a custom KK Rom without a modified kernel to see if you get any connection?
Now for the second screenshot, my take is that you are using a MicroSD that is formatted as exFAT (Usually that's the format of 64GB cards) and the recovery does not have support for that kind of file system.
[SIZE=+3]Welcome to Questions Answers & Troubleshooting[/SIZE]
{
"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"
}
This thread has been created to assist owners of:
The SONY Xperia X
There are no questions that are deemed insignificant
Helpful information for your device:
Overview of the Sony Xperia X
See also the Index project thread for the Xperia X
ᴥ Please feel free to Ask Away anything about your device ᴥ
Purpose Ask Away Thread
To know what the Ask Away thread is all about, see: http://forum.xda-developers.com/xperia-x/help/help-thread-xperia-x-t3474690
kindest regards, kuzibri
I have a problem with my X, there is an inusual battery use by the "Android OS" app listed
on the battery use screen, about the 30% of the total.
Using "CPU Spy" I see that there is no deep sleep.
I tried to flash the last original firmware with "Xperia Companion" and then did a factory reset
to start really clean, but nothing appears to change.
Any ideas?
Fito2019 said:
I have a problem with my X, there is an inusual battery use by the "Android OS" app listed
on the battery use screen, about the 30% of the total.
Using "CPU Spy" I see that there is no deep sleep.
I tried to flash the last original firmware with "Xperia Companion" and then did a factory reset
to start really clean, but nothing appears to change.
Any ideas?
Click to expand...
Click to collapse
Hi,
forget all about Xperia Companion, it's of no use at all for several reasons:
1. It does not synchronize your contacts, calendar, etc. Use MyPhoneExplorer for that, available from the app store
2. I have had the nasty experience after a crash of my X, that restoring backups won't work and always give an error sooner or later in the restore process. Use Backup Your Mobile Device instead, also available from the app store. Both apps are free. You can backup your device to Google Drive, Dropbox, One Drive or Orange Cloud.
Regarding your problem: When everything is OK, you will receive on your mobile device a message that a system update is availble and that you can install it. Before doing that, connect your device via USB with your PC/Laptop and start the system update. This takes about 30-45 minutes depending on the content on your device. If you do not get the system update message on your device, go to settings -info about the device - software update and click that.
kindest regards, kuzibri
BTW, just updated my own X just two days ago in this way.
The flashing was not a problem,was perfect and I have the latest version of firmware installed perfectly.
My problem is excessive consumption of battery by the Android OS and that the device never comes into deep sleep.
Fito2019 said:
The flashing was not a problem,was perfect and I have the latest version of firmware installed perfectly.
My problem is excessive consumption of battery by the Android OS and that the device never comes into deep sleep.
Click to expand...
Click to collapse
There are a lot of battery saving apps in the store, but I would advice you to use the Stamina mode for your device. To activate that, go to setings -battery - Stamina modus - click it and activate it. After activating this, you will receive a message that background apps or other processes will run slower. Ignore that, cause it's not true. This warning comes only with Marsmallow, other Android systems before that never gave that message and encouraged you to use the Stamina modus. You can also dowload Powerclean from the app store, this app does clean junk files from your device but has also the possibilty to download a seperate battery saving app. Both apps will be displayed in your notification bar.
kindest regards, kuzibri
nice thread,i have a question,i hope someone help me with this one,how do i know if i flashed a firm correctly?,what i mean is,how do i know if i have the Qnovo files installed??? my phone came with the .277 firm and the battery lasted more,now im using .292 and battery is wearing out faster. Thanks. Oh,btw i never let the battery fully discharge,(i just did a full discharge 4 times in 4 months),i always keep the charge between 30 and 90%.
Hello! I bought my device from Germany, I'm in Romania.Device came with Vodafone's apps pre installed. Is there any way i can flash a non carrier firmware? Thanks
Nicolae-Daniel said:
Hello! I bought my device from Germany, I'm in Romania.Device came with Vodafone's apps pre installed. Is there any way i can flash a non carrier firmware? Thanks
Click to expand...
Click to collapse
Yes you can with flashtool http://www.flashtool.net/index.php
Verstuurd vanaf mijn F5121 met Tapatalk
kistigun said:
Yes you can with flashtool http://www.flashtool.net/index.php
Verstuurd vanaf mijn F5121 met Tapatalk
Click to expand...
Click to collapse
Before unlocking the bootloader, is there any drawbacks that i should be aware of? Thanks
Nicolae-Daniel said:
Before unlocking the bootloader, is there any drawbacks that i should be aware of? Thanks
Click to expand...
Click to collapse
You wont need to unlock your bootloader. Using flashtools has no drawbacks, it's works almost the same as the repair option in xperia companion but flash tool has a lot of extra options
kistigun said:
You wont need to unlock your bootloader. Using flashtools has no drawbacks, it's works almost the same as the repair option in xperia companion but flash tool has a lot of extra options
Click to expand...
Click to collapse
Is it ok to flash 301 over 292 ?
Nicolae-Daniel said:
Is it ok to flash 301 over 292 ?
Click to expand...
Click to collapse
yeay no problem
How to root sony Xperia x without using pc
kanna3Aun said:
How to root sony Xperia x without using pc
Click to expand...
Click to collapse
You can try it on a mac . Jokes aside, I don't think you can.
Is there any way to root the 38.1.A.0.367 firmware?
ghuertasw said:
Is there any way to root the 38.1.A.0.367 firmware?
Click to expand...
Click to collapse
Yes, unlock bootloader, flash twrp and flash latest supersu
kistigun said:
Yes, unlock bootloader, flash twrp and flash latest supersu
Click to expand...
Click to collapse
Great! Thanks for your answer!
When you unlock bootloader, the device cleans everything? Is there an alternative to titanium backup that doesn't need root?
Anyone else with extremely picky fingerprint? Only when I wash my hands with soap thoroughly, wipe them, clean the sensor with a tissue, only then it SOMETIMES recognizes fingerprints...
"your finger may be damp" and if this message appears 5 times consecutively fingerprint recognition stops....awful experience
ghuertasw said:
Great! Thanks for your answer!
When you unlock bootloader, the device cleans everything? Is there an alternative to titanium backup that doesn't need root?
Click to expand...
Click to collapse
Yes it will whipe your data(dont forget to backup your TA). I'm not aware of a backup tool that completly backs up your data without root.
There is some talk in the P6 race to brick Telegram group, it seems that the december update is causing root to fail.
So until this is fixed/solved, DO NOT UPDATE IF YOU WANT TO RETAIN ROOT.
{
"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"
}
Oh no topjohnwu you didnt
ne0ns4l4m4nder said:
Oh no topjohnwu you didnt
Click to expand...
Click to collapse
He is working for the enemy now, was only a matter of time for problems to arise since he already stopped supporting MagiskHide at the behest of Google^^
Maybe Magisk just needs an update, maybe we have a bigger problem, we'll see
Nah, he'll find root or another Magisk developer will.
Cant we flash a patched stock boot image after the problem is solved?
As OP stated, do not update to December if you want to keep root. I did before I checked forums and lost root. Rolling back to November to hopefully regain access to root.
bb709394 said:
As OP stated, do not update to December if you want to keep root. I did before I checked forums and lost root. Rolling back to November to hopefully regain access to root.
Click to expand...
Click to collapse
Please report back if its possible to roll back
I don't see any update when I check for update on my Pixel 6.
Do I need to something to get the update? I ma not rooted and hence do not worry about rooting.
bb709394 said:
As OP stated, do not update to December if you want to keep root. I did before I checked forums and lost root. Rolling back to November to hopefully regain access to root.
Click to expand...
Click to collapse
Tread carefully, someone tried dirty flashing which then required a clean flash.
cd993 said:
Tread carefully, someone tried dirty flashing which then required a clean flash.
Click to expand...
Click to collapse
Yup, dirty flashed failed and requiring a clean flash. Good learning experience and lesson for me, don't jump the gun with the newest updates.
Assumptions made when I flashed December update on 4A 5G without any problems... c'est la vie.
bb709394 said:
Yup, dirty flashed failed and requiring a clean flash. Good learning experience and lesson for me, don't jump the gun with the newest updates.
Assumptions made when I flashed December update on 4A 5G without any problems... c'est la vie.
Click to expand...
Click to collapse
Yeah I would have held off rooting, as whilst sideloading the OTA I read that root wasn't working... oh well, a fix will come soon I'm sure
i didnt read this forum before flashing, now im stuck on a screen with the google logo and a loading bar. is my phone ****ed?
does anyone get corrupted data and stuck on google logo? any help?
Lainey52900 said:
i didnt read this forum before flashing, now im stuck on a screen with the google logo and a loading bar. is my phone ****ed?
Click to expand...
Click to collapse
You'll likely have to use the Google reset to factory process to ever use the phone again. I haven't rooted my Pixel 6 yet, though, so I can't confirm. But that's how I fixed a bad Pixel 5 update.
XNine said:
You'll likely have to use the Google reset to factory process to ever use the phone again. I haven't rooted my Pixel 6 yet, though, so I can't confirm. But that's how I fixed a bad Pixel 5 update.
Click to expand...
Click to collapse
what google reset?
Vio281 said:
what google reset?
Click to expand...
Click to collapse
Google Pixel - Update and Software Repair
Need a USB cable and Chrome (I think, never used a different browser for it).
Again, I can't confirm this works but it's just an educated guess
XNine said:
Google Pixel - Update and Software Repair
Need a USB cable and Chrome (I think, never used a different browser for it).
Again, I can't confirm this works but it's just an educated guess
Click to expand...
Click to collapse
just try it, only work up to google 5
Okay, so for anyone else here who tries to root using the December patch and gets stuck on the Google logo screen, here are the steps I took to fix it:
1. Hold down the power button until the phone turns off
2. Enter fastboot via holding down the power button and volume down
3. Attach a usb cable to a computer, download the factory image zip, then extract it
4. Once extracted, double click on "flash-all.bat," this will reflash every single component of the image to your phone and once it's done, will reboot and should boot as if nothing ever happened.
Lainey52900 said:
Okay, so for anyone else here who tries to root using the December patch and gets stuck on the Google logo screen, here are the steps I took to fix it:
1. Hold down the power button until the phone turns off
2. Enter fastboot via holding down the power button and volume down
3. Attach a usb cable to a computer, download the factory image zip, then extract it
4. Once extracted, double click on "flash-all.bat," this will reflash every single component of the image to your phone and once it's done, will reboot and should boot as if nothing ever happened.
Click to expand...
Click to collapse
i got a corrupted image and still stuck on google logo.
Vio281 said:
i got a corrupted image and still stuck on google logo.
Click to expand...
Click to collapse
for anyone running into the same situation i did, I have to use the flash option on the google firmware page to get my phone working again, Thank god...
Hi Team, I Need help with unbricking my device. I'm in a panic state. I had already unblocked my bootloader and downgraded to Oxygen OS 11.3 via MtkClient.
For some weird reason it stuck to bootloader animation and I flashed ROM files again via MTKClient, but it was still on the bootloader screen. Then I thought of flashing preloader files from the backup preloader files I saved before via MTKclient. Now it seems like I have bricked my device. Nothing is showing up.
This is my first post on this forum, Please help me out.
Thanks and apologies for breaking any forum rules.
It seems to be not charging ( I can't tell if it's charging when I'm using my regular charge adapter) and now it's not even showing up on MTKClient.
Hi, First question do you have a warranty?
Kabbutino said:
Hi, First question do you have a warranty?
Click to expand...
Click to collapse
No, this device issues issued for official work :-(
thecreat0rnew said:
Hi Team, I Need help with unbricking my device. I'm in a panic state. I had already unblocked my bootloader and downgraded to Oxygen OS 11.3 via MtkClient.
For some weird reason it stuck to bootloader animation and I flashed ROM files again via MTKClient, but it was still on the bootloader screen. Then I thought of flashing preloader files from the backup preloader files I saved before via MTKclient. Now it seems like I have bricked my device. Nothing is showing up.
This is my first post on this forum, Please help me out.
Thanks and apologies for breaking any forum rules.
Click to expand...
Click to collapse
PS: I also have backups of all partitions including the bootloader in a separate folder created via MTKClient. I hope the device is recoverable given its bootloader is unlocked but I'm worried that It's now not detected in MTKclient not sure if the charge is depleted and charming a device is not possible without valid bootloader???
thecreat0rnew said:
No, this device issues issued for official work :-(
Click to expand...
Click to collapse
Yeah, obviously
When you buy your phone?
thecreat0rnew said:
PS: I also have backups of all partitions including the bootloader in a separate folder created via MTKClient. I hope the device is recoverable given its bootloader is unlocked but I'm worried that It's now not detected in MTKclient not sure if the charge is depleted and charming a device is not possible without valid bootloader???
Click to expand...
Click to collapse
If you have a backup with mtkclient you can restore that
Kabbutino said:
If you have a backup with mtkclient you can restore that
Click to expand...
Click to collapse
But for some weird reason, MTKclient is unable to detect my device after the bootloader flash operation. Is there any further troubleshoot option to see battery percentage etc or some other operation?
thecreat0rnew said:
PS: I also have backups of all partitions including the bootloader in a separate folder created via MTKClient. I hope the device is recoverable given its bootloader is unlocked but I'm worried that It's now not detected in MTKclient not sure if the charge is depleted and charming a device is not possible without valid bootloader???
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"
}
Above are the files from Preloader backup operation from MTKclient. What file I should flash to fix preloader?
thecreat0rnew said:
But for some weird reason, MTKclient is unable to detect my device after the bootloader flash operation. Is there any further troubleshoot option to see battery percentage etc or some other operation?
Click to expand...
Click to collapse
Can you flash other backup of oos 11.3 and unlock the bootloader?
Kabbutino said:
Can you flash other backup of oos 11.3 and unlock the bootloader?
Click to expand...
Click to collapse
Again, I can but MTKclient doesn't detect my device anymore after pressing Volume +- Plus I don't thin flashing other partition backup would solve the issue cause all of this started to occur as I flashed preloader from the backup files
Can you send the log of mtkclient?
Kabbutino said:
Can you send the log of mtkclient?
Click to expand...
Click to collapse
There is nothing showing up on logs as well. Is it possible due to empty battery it's unable to go into bootrom mode? Below is the logs I was getting after flashing preloader and trying to launch MTKclient.
F
thecreat0rnew said:
There is nothing showing up on logs as well. Is it possible due to empty battery it's unable to go into bootrom mode? Below is the logs I was getting after flashing preloader and trying to launch MTKclient. View attachment 5878273
Click to expand...
Click to collapse
Why do you flash preloader?
And which os do you use?
Kabbutino said:
And which os do you use?
Click to expand...
Click to collapse
Oxygen OS 11.3, I thought the preloader is the issue where I was stuck in boot animation. I think the mobile was not charged enough and hence it got corrupted.
Is there any way to charge the device now?
Do you see the bootanimation of oneplus and the unlock bootloader message
Kabbutino said:
Do you see the bootanimation of oneplus and the unlock bootloader message
Click to expand...
Click to collapse
As of now, nothing is showing up. It's just a black screen.
I was able to get MTKClient to work after the one-plus animation screen.