I got an error at the begining of the flash, something like "too many files opened" and stop flashing. I aborted the process and now my f3 is dead, black screen, not recovery or fastboot. Windows desn't detects anything. Some help would be appreciated.
I am afraid you must put your F3 in EDL mode(Google it) basically it involves shorting of two pins in the phone to activate the EDL mode, you need to remove the back panel for that. After you put your phone in edl mode it will be recognised by your pc and you can restore it from there
{
"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"
}
What have you tried to flash? Using what?
Once you put the device in EDL mode you can use a fastboot rom to reflash the device, I have done this to Mi A1 which was in similar situation as described above.
Once you put the device in EDL mode you can use a fastboot rom to reflash the device, I have done this to Mi A1 which was in similar situation as described above
hexisg said:
What have you tried to flash? Using what?
Click to expand...
Click to collapse
I was flashing last xiaomi.eu by fastboot
Skynet75 said:
Once you put the device in EDL mode you can use a fastboot rom to reflash the device, I have done this to Mi A1 which was in similar situation as described above
Click to expand...
Click to collapse
Thx a lot, I've been reading about edl connection but didn't find this info. My doubt now is to do this and lost my waranty or send it to SAT and asume the risk to be charged.
muil said:
Thx a lot, I've been reading about edl connection but didn't find this info. My doubt now is to do this and lost my waranty or send it to SAT and asume the risk to be charged.
Click to expand...
Click to collapse
If it's under warranty give to the store they may repair it for free(possibly change the whole motherboard), if it's not under warranty or if they charge you with some insane amount try to go to a third party repair shop ask them to open the back panel and ask them to put it in edl mode and reflash it(if they don't know how to do it, just get the phone opened and do the other steps yourself). I am asking you to visit a third party store to open up the phone because the back panel is glass (glass is glass and glass breaks if not removed properly)
muil said:
Thx a lot, I've been reading about edl connection but didn't find this info. My doubt now is to do this and lost my waranty or send it to SAT and asume the risk to be charged.
Click to expand...
Click to collapse
In future don't flash xiaomi.eu with fastboot...
I remember reading that it overwrites critical partitions during flashing , there's a high likelihood to fk stuff up with that , use twrp instead
No twrp for android 12 yet, so...
Same thing happened to me last month. But i ended up fixing it. Its a pretty tricky process
mucha.k1994 said:
No twrp for android 12 yet, so...
Click to expand...
Click to collapse
Don't flash ...
TormentedHeart said:
Same thing happened to me last month. But i ended up fixing it. Its a pretty tricky process
Click to expand...
Click to collapse
Did you jumper the EDL test points? Did you need special tools to remove the back cover?
Rstment ^m^ said:
In future don't flash xiaomi.eu with fastboot...
I remember reading that it overwrites critical partitions during flashing , there's a high likelihood to fk stuff up with that , use twrp instead
Click to expand...
Click to collapse
Well...I flashed xiaomi.eu on this phone a cuple of times by fastboot before twrp was ready and everything went ok. The difference this time is my PC was overloaded with other tasks and the error "many files opened" I got, make me think this could be de cause.
Skynet75 said:
If it's under warranty give to the store they may repair it for free(possibly change the whole motherboard), if it's not under warranty or if they charge you with some insane amount try to go to a third party repair shop ask them to open the back panel and ask them to put it in edl mode and reflash it(if they don't know how to do it, just get the phone opened and do the other steps yourself). I am asking you to visit a third party store to open up the phone because the back panel is glass (glass is glass and glass breaks if not removed properly)
Click to expand...
Click to collapse
Finally I will send it to Xiaomi service. It looks easy the EDL method but as you say I would probably break the back cover. I'm crossing fingers to not be charged.
Hello I think I can help them I had the same problem
I had the Android 12 DP 5 Flashed by Munchy's Youtube channel
I had them running well until the day before yesterday but when I got up in the morning it told me that update is installed I should reboot
wtf what for update it sucked the update for the Pixel 5 and installed it I thought
ok reboot via ADB in fastboot boot ......and EDL Mode ....
then I researched and found this nice gentleman ..... I got in touch via whatsapp and the next day he did it.... it cost me 35 Euros but I think it's better than buying a new one
I give his data if someone has a problem I would try it here
https://www.unbrickmi(.)com/
I hope I could help someone else
noobstyle1337 said:
Hello I think I can help them I had the same problem
I had the Android 12 DP 5 Flashed by Munchy's Youtube channel
I had them running well until the day before yesterday but when I got up in the morning it told me that update is installed I should reboot
wtf what for update it sucked the update for the Pixel 5 and installed it I thought
ok reboot via ADB in fastboot boot ......and EDL Mode ....
then I researched and found this nice gentleman ..... I got in touch via whatsapp and the next day he did it.... it cost me 35 Euros but I think it's better than buying a new one
I give his data if someone has a problem I would try it here
https://www.unbrickmi.com/
whatsapp +91 76449 33731
I hope I could help someone else
Click to expand...
Click to collapse
But what did he do or what did you do by his guidance to fix it?
muil said:
But what did he do or what did you do by his guidance to fix it?
Click to expand...
Click to collapse
@ABHIROOP90
Download telegram and message this guy .
He does it for maybe 7-10$ ...
That's what he told me at least , some users say he's legit but you'll have to pay and see for yourself.
Don't know if you can't do edl by yourself as some say you need edl authorised account
That's if you want edl... But if you open the device you'll have troubles getting warranty 100% if the edl fails for whatever reason.
I'd go and give it to warranty myself...
muil said:
But what did he do or what did you do by his guidance to fix it?
Click to expand...
Click to collapse
The gentleman has an Xiaomi auth account and can do the EDL ..... I think not everyone has such an account
Rstment ^m^ said:
@ABHIROOP90
Download telegram and message this guy .
He does it for maybe 7-10$ ...
That's what he told me at least , some users say he's legit but you'll have to pay and see for yourself.
Don't know if you can't do edl by yourself as some say you need edl authorised account
That's if you want edl... But if you open the device you'll have troubles getting warranty 100% if the edl fails for whatever reason.
I'd go and give it to warranty myself...
Click to expand...
Click to collapse
I didn't have to open my Poco If you hang in EDL mode then you can also press 20 sec power then the Edl mode restarts and then you can flash
Related
Hi,my wildfire s was updated from 1.66.401.1 directly to 2.13.401.3 and is now stuck in the white screen (without logo) and continues in a bootloop. Bootloader menu didn`t work. Computer, of course, doesnt see the phone I know it's because I don`t update hboot. But there is any opportunity to fix the phone?
What do you mean by 'bootloader menu didn't work'? Did you try to remove the battery and then use vol down + power ?
vbhtt said:
What do you mean by 'bootloader menu didn't work'? Did you try to remove the battery and then use vol down + power ?
Click to expand...
Click to collapse
Yes, I try. No responce. Thats unusual bootloop, I dont even see the HTC logo, only blinking screen
ru_LapTop said:
Yes, I try. No responce. Thats unusual bootloop, I dont even see the HTC logo, only blinking screen
Click to expand...
Click to collapse
That's not a bootloop
Your phone is probably bricked
{
"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"
}
MrTaco505 said:
That's not a bootloop
Your phone is probably bricked
Click to expand...
Click to collapse
You don't normally get bricked when you update your firmware especially if you are s-on and with b/l locked
You should go to the htc shop and show them your phone. They should replace it or atleast repair it.
vbhtt said:
You don't normally get bricked when you update your firmware especially if you are s-on and with b/l locked
You should go to the htc shop and show them your phone. They should replace it or atleast repair it.
Click to expand...
Click to collapse
Phone is no longer under warranty There is no way to repair the phone at home? XTC Clip?
ru_LapTop said:
Phone is no longer under warranty There is no way to repair the phone at home? XTC Clip?
Click to expand...
Click to collapse
They should still honour the warranty if your not unlocked and an official update caused the problem.
I think he means the time period of the warranty is over.
Silly question but does the orange/green led come on when you connect it to the charger or computer?
Sent from my HTC Wildfire S A510e using XDA App
intel007 said:
They should still honour the warranty if your not unlocked and an official update caused the problem.
Click to expand...
Click to collapse
vbhtt said:
I think he means the time period of the warranty is over
Click to expand...
Click to collapse
Yes, I mean it.
vbhtt said:
I think he means the time period of the warranty is over.
Silly question but does the orange/green led come on when you connect it to the charger or computer?
Click to expand...
Click to collapse
Red led lights up for 10 seconds, after that phone tries to turn on, and starts blinking again.
Is HTC sync installed on your computer? If not, then install it. Because without the drivers, your computer won't recognise the phone.
Do you know how to use adb?
Sent from my HTC Wildfire S A510e using XDA App
ru_LapTop said:
Yes, I mean it.
Red led lights up for 10 seconds, after that phone tries to turn on, and starts blinking again.
Click to expand...
Click to collapse
can you boot into fastboot??
(remove the batery re insert it again after 5 sec and then hold the volume down key and power button for mostly 5 sec)
if you can do so then download ny rom extract it and then use the adb commands..
for that you will need adb files
http://www.mediafire.com/download.php?b6mk4b8p1xm5nok
download this zip .. unzip on desktop/there are three files in it if the three files are in the folder named android then remove the three files from the folder and paste the three files on dektop..
the rom you downloaded .. extract it..
and copy boot.img and system.img to desktop
when in boot loader.. the fastboot option will be highlighted select it
to select press power button..
when done connect the phone to pc. (dont forget to install htc sync, cuz you wud need drivers for the pc so that it can detect your phone..)
and then go to start menu on task bar..
select Run option..
in run option write cmd and click on ok
from now press enter after every command
Code:
cd desktop
fastboot flash boot boot.img
fastboot flash system system.img
now remove the cable from phone..
remove the battery and try rebooting the phone..
vbhtt said:
Is HTC sync installed on your computer? If not, then install it. Because without the drivers, your computer won't recognise the phone.
Do you know how to use adb?
Click to expand...
Click to collapse
I`m not a novice I know how to use HTC Sync and ADB, but they dont see the phone, otherwise I wouldnt ask.
Today I will try to go to the service center without warranty,maybe they will be able to help
ru_LapTop said:
I`m not a novice I know how to use HTC Sync and ADB, but they dont see the phone, otherwise I wouldnt ask.
Today I will try to go to the service center without warranty,maybe they will be able to help
Click to expand...
Click to collapse
ask him if you can pay him and get that thing back to normal
mhrsolanki2020 said:
ask him if you can pay him and get that thing back to normal
Click to expand...
Click to collapse
I did so But they demanded too high price, and obviously they want to change all hardware completely. I hope they are smart enough not to do this. The story goes on
ru_LapTop said:
I did so But they demanded too high price, and obviously they want to change all hardware completely. I hope they are smart enough not to do this. The story goes on
Click to expand...
Click to collapse
try visiting a private mobile repair shop..
mhrsolanki2020 said:
try visiting a private mobile repair shop..
Click to expand...
Click to collapse
If official service will not be able to repair it,that the only thing that I will.
But I still interesting how device can recover Hboot, maybe someone in my city has it.
ru_LapTop said:
If official service will not be able to repair it,that the only thing that I will.
But I still interesting how device can recover Hboot, maybe someone in my city has it.
Click to expand...
Click to collapse
i dont get you
If its a softwer problem i dont see why would they demand such "high prices"(you never said how much exactly) if they have the right eqipment compleatly reviving a dead phone will cost you around 20-30 euro. If thats high for you i guess you are right. But if its a hardware problem i dont see how a dev forum would help you. I'm a noob so i wouldnt know ...
Service Center wanted to change all motherboard, and demanded $195(!!)
I found information about the device, called RiffBox($100-$150),I will use it. And in the future I will never go to such foolish service centers
Hello, today i flashed one of the new nougat stock roms. The first boot was fine, everything worked perfectly . But after rebooting I've got the "your device is corrupt. it cannot be trusted and it may not work properly" message, and it wont boot anymore. I cant go into recovery and i cant go into download mode because i get the same the same message and the phone reboots. i can only access the fastboot mode for bootloader unlock, and apparently that my bootloader is now locked. So I've tried to unlock the bootloader again, but it says "Wrong Bootloader Unlock key". Anyone has any idea?
darkstewie92 said:
Hello, today i flashed one of the new nougat stock roms. The first boot was fine, everything worked perfectly . But after rebooting I've got the "your device is corrupt. it cannot be trusted and it may not work properly" message, and it wont boot anymore. I cant go into recovery and i cant go into download mode because i get the same the same message and the phone reboots. i can only access the fastboot mode for bootloader unlock, and apparently that my bootloader is now locked. So I've tried to unlock the bootloader again, but it says "Wrong Bootloader Unlock key". Anyone has any idea?
Click to expand...
Click to collapse
I have the exact same problem and to be honest I think we are f*****. I haven't found any way to re-unlock the bootloader since it seems that the unlock.bin doesn't match with the Device-ID anymore.
This is an IMEI problem. It goes to 0, so the unlock.bin no longer works. I also had this message but my phone was still booting. So I was able to solve the problem.
But you, you can not start your phone, so I do not know how to fix your problem. Sorry
Pif0u said:
This is an IMEI problem. It goes to 0, so the unlock.bin no longer works. I also had this message but my phone was still booting. So I was able to solve the problem.
But you, you can not start your phone, so I do not know how to fix your problem. Sorry
Click to expand...
Click to collapse
No it isn't an IMEI problem, I can reboot my phone and I can access the download mode to flash a KDZ which I did.
EDIT: Oh but I just see in the settings that my IMEI indeed turned into a zero... I do have a TWRP backup of my IMEI.
I quess it's a better idea to make my own G4 Q&A, Help & Troubleshooting thread for help.
I reply in your topic
Pif0u said:
Tutorial to restore imei
1 -Go to phone dial
2- Type *#546368#*815#
3- Go to SVC Menu
4- Go to Port Check Test
5 - Enable Port check test
6 - Download this :
Code:
https://mega.nz/#!cZ9TxBLT!v9qEfeNTeCKYw8XoAhaMOkN48pp4WtLBCU_8KlYeERs
7 - Run the program
{
"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"
}
8 - Click to Qualcomm NV Tools
9 -
10 - Check the box IMEI, Write your IMEI in IMEI(dec) and click to write.
11 - Reboot phone
Click to expand...
Click to collapse
Oh... I just made my own thread, I didn't notice your reply because you didn't quote me... But thanks for this tutorial! I'll give it a try :good:
Pif0u said:
This is an IMEI problem. It goes to 0, so the unlock.bin no longer works. I also had this message but my phone was still booting. So I was able to solve the problem.
But you, you can not start your phone, so I do not know how to fix your problem. Sorry
Click to expand...
Click to collapse
Well, that's sad. This doesn't make any sense . RIP my loevely G4 I guess. Thank you anyway!
darkstewie92 said:
Well, that's sad. This doesn't make any sense . RIP my loevely G4 I guess. Thank you anyway!
Click to expand...
Click to collapse
Hhmm maybe you aren't totally lost, you can access Fastboot mode right, so how have you tried to access the Download mode? You pressed the Volume up button and connected your device with a USB?
It seems you have the same problem as I had, your IMEI turned into a "0", that's why your unlock.bin fails to flash. Just try to access the Download mode for a couple of times, maybe with a but of luck it wil boot into Download mode eventually.
Is there a way to change imei on nougat? Because i cant go in download mode to downgrade to mm
Having the same issue. Cant enter on download or recovery. Fking sht
---------- Post added at 02:30 PM ---------- Previous post was at 02:18 PM ----------
How r u accessing fastboot for bootloader unlock?
Mr.FREE_Bird said:
Hhmm maybe you aren't totally lost, you can access Fastboot mode right, so how have you tried to access the Download mode? You pressed the Volume up button and connected your device with a USB?
It seems you have the same problem as I had, your IMEI turned into a "0", that's why your unlock.bin fails to flash. Just try to access the Download mode for a couple of times, maybe with a but of luck it wil boot into Download mode eventually.
Click to expand...
Click to collapse
I've tried like 20 times already, unfortunately it reboots almost instantly.
We all have the same problem at this point I know that we either hold the smartphone so or we send it to assistance but considering that it is not covered by warranty do not know how long it is
pedrogcsb said:
Having the same issue. Cant enter on download or recovery. Fking sht
---------- Post added at 02:30 PM ---------- Previous post was at 02:18 PM ----------
How r u accessing fastboot for bootloader unlock?
Click to expand...
Click to collapse
press volume down while your phone is turned off, and then plug your usb cable connect to your pc.
darkstewie92 said:
press volume down while your phone is turned off, and then plug your usb cable connect to your pc.
Click to expand...
Click to collapse
Not working for me aswell
Randy_Orton91 said:
We all have the same problem at this point I know that we either hold the smartphone so or we send it to assistance but considering that it is not covered by warranty do not know how long it is
Click to expand...
Click to collapse
I don't even know if they are gonna repair it, and if they do, we will need to pay I guess, I don't how much.
darkstewie92 said:
I don't even know if they are gonna repair it, and if they do, we will need to pay I guess, I don't how much.
Click to expand...
Click to collapse
Use this guide, i solve the problem: https://forum.xda-developers.com/showpost.php?p=73498317&postcount=140
Randy_Orton91 said:
Use this guide, i solve the problem: https://forum.xda-developers.com/showpost.php?p=73498317&postcount=140
Click to expand...
Click to collapse
thank you, but i cant even boot into the ROM. It worked fine the first time,now it doesn't boot anymore.
darkstewie92 said:
thank you, but i cant even boot into the ROM. It worked fine the first time,now it doesn't boot anymore.
Click to expand...
Click to collapse
Same to me
Try this method to live your download mode - https://forum.xda-developers.com/g4/...lcomm-t3452853
You can try a last attempt before you give up if you can not fix it: write an email to [email protected] explains the problem that you've updated to nougat beta and now your bootloader has re-locked and your imei is set on 0 and so the unlock.bin file does not work, try to see if they send you a working one, yesterday I wrote the email and they also answered me asking for more info but I have now solved the problem. Attach the device id and a photo of the back of the phone where the imei is written. Try it
Hi im having a hard time figuring this out, this is a brand new 5t that bricked itself while ota updating
the device is in a boot loop (wont go any further than the oneplus logo)
if i enter to the recovery it says LOCKED, and the oem unlock option on android is not enabled
im in argentina so i cant send the phone to oneplus rma
{
"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"
}
is there any way to unlock the bootloader? then i would be able to flash it and save the phone
Ps: a level 2 OnePlus tech guy tried a remote fix with the official brand software and it did not work
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Hope that helps. If you can get it to load in that mode, it'll fix about anything.
es0tericcha0s said:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Hope that helps. If you can get it to load in that mode, it'll fix about anything.
Click to expand...
Click to collapse
Thanks a lot! i think that oneplus did use that file and did not work but i will try it again (at least 10 times)
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
This is why I wish we had a fastboot OEM image install option like Google provides.
Maybe we do though and I just haven't found it yet.
Haven't looked very hard.
es0tericcha0s said:
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
Click to expand...
Click to collapse
if i boot to recovery and press the power button to select factory reset or any usefull option, the phone resets, i think that the problem is a corrupt recovery, thats why i want to unlock it, install TWRP and then try to flash android
CZ Eddie said:
This is why I wish we had a fastboot OEM image install option like Google provides.
Maybe we do though and I just haven't found it yet.
Haven't looked very hard.
Click to expand...
Click to collapse
maybe this is an anti thief security measure? (since android 6.0 )
es0tericcha0s said:
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
Click to expand...
Click to collapse
why would i have a problem putting the 5t on qhusb? i did not know that it could be done via testpoint
the phone works, the problem seems to be a faulty file on the bootloader or maybe an internal damage from factory (i hope this is not the case)
in a few hours i will try it all and post the result
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
es0tericcha0s said:
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
Click to expand...
Click to collapse
I did the entire process and the result is the same as before doing it, the phone turns on and gets stuck on the oneplus logo, it does nothing else, the recovery works but doesnt do anything usefull
Do you get any errors when performing a factory reset? As in a partition not mounting? Since your baseband doesn't show in the fastboot mode, I'm thinking maybe an /efs error. If you got it new, I'd talk to 1+ about an RMA since this was caused by an official update and one of their technicians already failed to fix it.
es0tericcha0s said:
Do you get any errors when performing a factory reset? As in a partition not mounting? Since your baseband doesn't show in the fastboot mode, I'm thinking maybe an /efs error. If you got it new, I'd talk to 1+ about an RMA since this was caused by an official update and one of their technicians already failed to fix it.
Click to expand...
Click to collapse
It may well be a partition error, one+ is not being helpfull right now
I did comit an error saying that the recovery works, it doesnt work, the pone only goes into fastboot and qhusb mode, after that it will allways get stuck on the oneplus logo
On adb i get feedback if i try to flash the phone says "not allowed, locked device"
I think that the problem is a corrupt bootloader
The msmdownloader tool works, i dont know what It copies on to the terminal but i want to flash the recovery and bootloader using that tool, i dont know if it is possible
this the md5sum file that i found in a compilation for oneplusone (msmdownloader tool)
so i shoud be able to do the same with the 5t
es0tericcha0s said:
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
Click to expand...
Click to collapse
that is no true, u just have the phone powered off and then hold the volume + and plug the device in, if u saw the video in the unbrick post he was not bricked at all and everything was working good and still did a restore, not sure why it is not working for the OP but it should fix it.
Yes i can enter into qhusb, and i can flash the phone with msm downloader, but i used the origibal file that oneplus technicians use amd it didnt work, now i want to flash hydrogen os or the recovery file only into the terminal but i dont know how to modify the msm downloader (the unbrick tool)
Had the same error message tonight after spontaneous reboot of my (unmodified and locked) device. Fortunately, reimaging with stock ROM from downloads.oneplus.net via adb sideload worked for me, without losing any data. Tried that?
sascha224 said:
Had the same error message tonight after spontaneous reboot of my (unmodified and locked) device. Fortunately, reimaging with stock ROM from downloads.oneplus.net via adb sideload worked for me, without losing any data. Tried that?
Click to expand...
Click to collapse
I remember that the device wouldnt flash anything because it was locked, but I will try the sideload right away
It has been impossible to fix, this is the best i got doing fastboot boot recovery.img
Hi
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
I am not even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
Device State: Locked
Developer Mode : Not Enabled and not possible to do now
PLease help me. As i am from Nepal , there is nothing i can't claim for warranty.
{
"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"
}
senbros said:
Hi
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
I am not even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
Device State: Locked
Click to expand...
Click to collapse
Sorry, but with no working recovery and a locked bootloader you are dead in the water. There is nothing that can be done.
Are you able to unlock your bootloader? Might be able to download the factory image do it that way. Fastboot flashing unlock it something. Then run the flash all.bat from the factory image once you download it and unzipped it.
mammothjojo88 said:
Are you able to unlock your bootloader? Might be able to download the factory image do it that way. Fastboot flashing unlock it something. Then run the flash all.bat from the factory image once you download it and unzipped it.
Click to expand...
Click to collapse
I tried nothing works to unlock bootloader.. Still looking for solution..
Thank you for your time
Can't find valid operating system
senbros said:
Hi
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
I am not even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
Device State: Locked
Developer Mode : Not Enabled and not possible to do now
PLease help me. As i am from Nepal , there is nothing i can't claim for warranty.
Click to expand...
Click to collapse
Hi Mate,
I had the same thing happen Last Friday morning. I was just applying an OTA update, then when phone rebooted I got the same message on my Pixel 3 ( 2 weeks old ). I spent many hours over the weekend trying to figure out how to get a factory image on it. However without unlocking the bootloader ( which is not possible ), also having the recovery also corrupted, there is nothing we can do, except send it to a friend or someone we know and trust to get the phone repaired or if its under warranty still, possibly replaced by google. Sorry to be the giver of bad news. These are now expensive paper weights. It seems it becoming more common.
This is happening for more pixels. Google is must fix it remotely or pixel 4 might fail on landing.
issue resolved by google support
Hi,
i am having same issue with my pixel 3 last week, so i called Indian google service center ( 1800-419-0655 ) they pick up my phone from my place and resolve the issue.
so i will suggest you to visit/call google support team so they will resolve you issue.
---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------
slysurfer said:
Hi Mate,
I had the same thing happen Last Friday morning. I was just applying an OTA update, then when phone rebooted I got the same message on my Pixel 3 ( 2 weeks old ). I spent many hours over the weekend trying to figure out how to get a factory image on it. However without unlocking the bootloader ( which is not possible ), also having the recovery also corrupted, there is nothing we can do, except send it to a friend or someone we know and trust to get the phone repaired or if its under warranty still, possibly replaced by google. Sorry to be the giver of bad news. These are now expensive paper weights. It seems it becoming more common.
Click to expand...
Click to collapse
hi there,
i had same issue last week, so i called google support. they pick up my pixel from my place and resolve the issue.
so please do the same contact google support. they will help you.
Problem in Pixel 3
They gave you a replacement or repaired the original device?? And how many days B2X took from pickup to delivering it back??
tailorhardik94 said:
Hi,
i am having same issue with my pixel 3 last week, so i called Indian google service center ( 1800-419-0655 ) they pick up my phone from my place and resolve the issue.
so i will suggest you to visit/call google support team so they will resolve you issue.
---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------
hi there,
i had same issue last week, so i called google support. they pick up my pixel from my place and resolve the issue.
so please do the same contact google support. they will help you.
Click to expand...
Click to collapse
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
bradwatson said:
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
Click to expand...
Click to collapse
You can't do anything if you come across this problem whilst your bootloader is locked. I had a Pixel 3, applied ota via recovery and I got that error message. Couldn't do anything, flash factory image etc due to locked bootloader and recovery being corrupted.
Quite simply if it's under warranty, contact google.
kartikb said:
You can't do anything if you come across this problem whilst your bootloader is locked. I had a Pixel 3, applied ota via recovery and I got that error message. Couldn't do anything, flash factory image etc due to locked bootloader and recovery being corrupted.
Quite simply if it's under warranty, contact google.
Click to expand...
Click to collapse
Not entirely true. If OEM unlocking was previously enabled, then despite your phone being locked, it will still accept the unlocking command. Just happened to me. I am trading in my phone. I uninstalled Magisk, booted to bootloader, locked the bootloader and got the dreaded "Can't find valid operating system" alert. I thought it was toast since no response to adb at that point. The screen looked like the bootloader screen but with less text. Finally used vol down/pwr to get to bootloader, re-unlocked and re-flashed the OS. Back in business, at least getting my full trade-in price!
flash.android.com really helped, thank you!
device locked (locking the device is what caused this for me) and windows saying it doesnt recognize the device when I plugged it in while in the bootloader. For some reason flash.android.com recognized the device, not sure why
same thing happened with right now
i was trying to lock bootloader on custom rom (nonsense,i know)
so,phone wasnt being recognized by pc,and somehow android flash tool recognized and i clicked flashing and it needed bootloader to be unlocked so it did,and phone booted back on custom rom.
nice
yearn2burn said:
Not entirely true. If OEM unlocking was previously enabled, then despite your phone being locked, it will still accept the unlocking command. Just happened to me. I am trading in my phone. I uninstalled Magisk, booted to bootloader, locked the bootloader and got the dreaded "Can't find valid operating system" alert. I thought it was toast since no response to adb at that point. The screen looked like the bootloader screen but with less text. Finally used vol down/pwr to get to bootloader, re-unlocked and re-flashed the OS. Back in business, at least getting my full trade-in price!
Click to expand...
Click to collapse
Just happened to my Pixel 4a5G trade-in for Pixel 7. Completely uninstalled magisk and then tried to re-lock the bootloader. Bootloader locked and got the no operating system error. Called google and they said send it in as and I will get full amount. The dude did not sound very reassuring. I luckyly stumbled on this thread. tried to unlock the bootloader but it failed. I reset my computer and tried it again and it worked. Phone booted up. I took and OTA and tried to re-lock the bootloader and SUCCESS. This phone never had an OTA so I believe the one slot was empty, maybe that is why this happened. Moral to the story, make sure both slots has an OS on them.
Thanks
BB
bradwatson said:
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
Click to expand...
Click to collapse
Thanks! This was exactly what I needed. I didn't realize you could get into fastboot with hardware controls and I was trying through adb
I'm an idiot and did this same thing.
bradwatson said:
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
Click to expand...
Click to collapse
Just wanted to say thanks - had a panic moment until I read this and realized I could do that. Pixel 4 wiped and ready to go back. Thanks again, years later.
{
"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"
}
steady 100% overnight while playing for 5 hours, thats not good i think
My story before I got into this mess:
I received my phone as a christmas gift to myself on January 2022
I really want to remove those bloatwares so obviously I'll unlock its bootloader and flash custom roms. I tested every roms available on a whole month of february and stayed for xiaomi.eu since I want the feels of miui but not the global one.
So far so good and im happy with eu rom until 22.8.10 update.
August 12, lunchbreak at work I decided to push some updates on my device. After flashing I still have almost 70-60% , I used it until 10%, after charging it my phne constantly loops at fast-charging animation and low power warning. I thought my cables were faulty or the charger plug itself. I didnt do anything and after a while it was okay.
about an hour later it just reboots itself, constantly powering on and off, unable to start itself, and after a while, i think 4-6 unsuccessful reboots and it fixes itself.
I just slept for a day not noticing anything. The morning I woke up, this is where i notice omething strange happen with my battery stuck at 100% even using some battery intensive apps before going to bed, looked up at battery stats and saw it stays constant for 16 hours.
I thought might be a bad update then I factory reset the phone. Still sitting at 100. I flashed previous version. No changes. This is the point I worried. I downloaded that 5 gigabyte fastboot rom of poco f3 global and still no signs of luck, I even choose to lock bootloader , still the same issue.
After collecting some infos, someone on TG said it might be related to PMIC breaking things up, ahardware-related issue.
Anyone having this? Thanks
There can be bugs on the weekly builds. Use the stable builds if you don't want to deal with potential bugs
Zinnz said:
There can be bugs on the weekly builds. Use the stable builds if you don't want to deal with potential bugs
Click to expand...
Click to collapse
i even rollback to global stock rom , same results, maybe ill bring my phone to service center, it may be an isolated case
fireclouu said:
i even rollback to global stock rom , same results, maybe ill bring my phone to service center, it may be an isolated case
Click to expand...
Click to collapse
I wouldn't go to a service center unless it's a hardware issue. You should be able to fix it, it just may take awhile of trial and error. you already have more knowledge than the average service center tech when it comes to flashing roms and whatnot, they're just wanna send it away most likely.
Also, could you summarize the issue you're having? It will increase your chances of someone replying with a potential fix
Zinnz said:
I wouldn't go to a service center unless it's a hardware issue. You should be able to fix it, it just may take awhile of trial and error. you already have more knowledge than the average service center tech when it comes to flashing roms and whatnot, they're just wanna send it away most likely.
Also, could you summarize the issue you're having? It will increase your chances of someone replying with a potential fix
Click to expand...
Click to collapse
i thought so too about flashing and stuff yeah xda rules!
but this one im not sure but it was not the usual software issue. I tried jumping from every roms i know, eu, lineage, arrow and still stuck at 100%
I also tried reverting it back to fastboot global stock roms, even the old ones and still facing the same issue
im now looking at flashing my device on edl mode. I remember my old phone I have redmi 5a, I got broken sensors due to jumping from xiaomi.eu to stock rom, even fastboot roms wont help, and the only thing fixes the sensors back to normal was edl mode flashing.
but edl mode is a pain when it comes to pocof3 , it needs to short some test points and to have authorize mi accounts just to get it done
fireclouu said:
i thought so too about flashing and stuff yeah xda rules!
but this one im not sure but it was not the usual software issue. I tried jumping from every roms i know, eu, lineage, arrow and still stuck at 100%
I also tried reverting it back to fastboot global stock roms, even the old ones and still facing the same issue
im now looking at flashing my device on edl mode. I remember my old phone I have redmi 5a, I got broken sensors due to jumping from xiaomi.eu to stock rom, even fastboot roms wont help, and the only thing fixes the sensors back to normal was edl mode flashing.
but edl mode is a pain when it comes to pocof3 , it needs to short some test points and to have authorize mi accounts just to get it done
Click to expand...
Click to collapse
There are Deep Flash Cables, I don't know if those work on Poco F3..
fireclouu said:
i thought so too about flashing and stuff yeah xda rules!
but this one im not sure but it was not the usual software issue. I tried jumping from every roms i know, eu, lineage, arrow and still stuck at 100%
I also tried reverting it back to fastboot global stock roms, even the old ones and still facing the same issue
im now looking at flashing my device on edl mode. I remember my old phone I have redmi 5a, I got broken sensors due to jumping from xiaomi.eu to stock rom, even fastboot roms wont help, and the only thing fixes the sensors back to normal was edl mode flashing.
but edl mode is a pain when it comes to pocof3 , it needs to short some test points and to have authorize mi accounts just to get it done
Click to expand...
Click to collapse
Just wanna ask a few questions to exclude them
Have you tried using a different USB cable /different USB port on your pc?
Have you tried entering recovery and factory reseting the phone before a new Rom flash?
Have you tried factory reseting the phone via settings after a new Rom flash, and after the phone boots up?
If you do think it's a hardware issue, it couldn't hurt to flash to stock and see what service center / xiaomi can do. I just wouldn't mention anything about the whole flashing business lol. But yeah, they might swap it out for ya best case scenario. But might be without a phone for awhile :/
fireclouu said:
View attachment 5686001
steady 100% overnight while playing for 5 hours, thats not good i think
My story before I got into this mess:
I received my phone as a christmas gift to myself on January 2022
I really want to remove those bloatwares so obviously I'll unlock its bootloader and flash custom roms. I tested every roms available on a whole month of february and stayed for xiaomi.eu since I want the feels of miui but not the global one.
So far so good and im happy with eu rom until 22.8.10 update.
August 12, lunchbreak at work I decided to push some updates on my device. After flashing I still have almost 70-60% , I used it until 10%, after charging it my phne constantly loops at fast-charging animation and low power warning. I thought my cables were faulty or the charger plug itself. I didnt do anything and after a while it was okay.
about an hour later it just reboots itself, constantly powering on and off, unable to start itself, and after a while, i think 4-6 unsuccessful reboots and it fixes itself.
I just slept for a day not noticing anything. The morning I woke up, this is where i notice omething strange happen with my battery stuck at 100% even using some battery intensive apps before going to bed, looked up at battery stats and saw it stays constant for 16 hours.
I thought might be a bad update then I factory reset the phone. Still sitting at 100. I flashed previous version. No changes. This is the point I worried. I downloaded that 5 gigabyte fastboot rom of poco f3 global and still no signs of luck, I even choose to lock bootloader , still the same issue.
After collecting some infos, someone on TG said it might be related to PMIC breaking things up, ahardware-related issue.
Anyone having this? Thanks
Click to expand...
Click to collapse
How did you flash new firmware? Via PC? If yes reflash it again then proceed with stepa below ( When flashing select clean all , you don't need to lock bootloader just yet so don't select lock )
You need to enter bootloader mode ( Power on phone while holding volume down , then type fastboot reboot bootloader. You must do it like this! Just holding volume down doesn't enter bootloader , instead it enters a stripped down version of it... Don't know what it's called... )
Reboot phone after doing this , if battery still isn't fixed flash back to stock , lock bootloader and go to service center. Don't even bother with anything else , pmic is supposed to reset when you enter bootloader ( Maybe it even resets in stripped bootloader but just to be safe do enter true boatloader like described above ) . If it isn't fixed it's likely a hardware issue
Have you tried using a different USB cable /different USB port on your pc?
Click to expand...
Click to collapse
yup i thought my cables are faulty so i borrow other cable thats also come from xiaomi
Have you tried entering recovery and factory reseting the phone before a new Rom flash?
Click to expand...
Click to collapse
done that too, I formatted the device before flashing it again, only dirty flash on eu update, after my issue arises ive done clean flash, does also too before reflashing stock rom on fastboot
Have you tried factory reseting the phone via settings after a new Rom flash, and after the phone boots up?
Click to expand...
Click to collapse
done as well, even on stock rom, i also lock my bootloader just to be sure, but still at 100%
one thing I also did was manually flashing persist but it wouldnt let me in, I tried also on recovery terminal, via orangefox, and twrp.
tried flashing persist manually too using
Code:
dd
, output says it pushed successfully but I dont think so. fastboot disabled flashing persist, needs edl mode.
Rstment ^m^ said:
How did you flash new firmware? Via PC? If yes reflash it again then proceed with stepa below ( When flashing select clean all , you don't need to lock bootloader just yet so don't select lock )
You need to enter bootloader mode ( Power on phone while holding volume down , then type fastboot reboot bootloader. You must do it like this! Just holding volume down doesn't enter bootloader , instead it enters a stripped down version of it... Don't know what it's called... )
Reboot phone after doing this , if battery still isn't fixed flash back to stock , lock bootloader and go to service center. Don't even bother with anything else , pmic is supposed to reset when you enter bootloader ( Maybe it even resets in stripped bootloader but just to be safe do enter true boatloader like described above ) . If it isn't fixed it's likely a hardware issue
Click to expand...
Click to collapse
oh this is new to me, okay ill try bootloader, wish me luck flash it rn
Rstment ^m^ said:
How did you flash new firmware? Via PC? If yes reflash it again then proceed with stepa below ( When flashing select clean all , you don't need to lock bootloader just yet so don't select lock )
You need to enter bootloader mode ( Power on phone while holding volume down , then type fastboot reboot bootloader. You must do it like this! Just holding volume down doesn't enter bootloader , instead it enters a stripped down version of it... Don't know what it's called... )
Reboot phone after doing this , if battery still isn't fixed flash back to stock , lock bootloader and go to service center. Don't even bother with anything else , pmic is supposed to reset when you enter bootloader ( Maybe it even resets in stripped bootloader but just to be safe do enter true boatloader like described above ) . If it isn't fixed it's likely a hardware issue
Click to expand...
Click to collapse
didnt fixed too, i even booted to fastbootd tried flashing there but boot_ab inaccessible, only in normal fastboot
i want to do edl mode flashing but some encryption needed, even at qfil cant flash the thing, needs to modify prog files and crack it
fireclouu said:
i want to do edl mode flashing but some encryption needed, even at qfil cant flash the thing, needs to modify prog files and crack it
Click to expand...
Click to collapse
I had to flash a ROM through EDL Mode once (I hardbricked my phone). I had to pay someone on Telegram with an Authorised Xiaomi Service Center Account 25€ and it did work.
So... it seems to be locked by Xiaomi. Apparently to stop people from importing phones from China and flashing Global ROM on them.
cyanGalaxy said:
I had to flash a ROM through EDL Mode once (I hardbricked my phone). I had to pay someone on Telegram with an Authorised Xiaomi Service Center Account 25€ and it did work.
So... it seems to be locked by Xiaomi. Apparently to stop people from importing phones from China and flashing Global ROM on them.
Click to expand...
Click to collapse
xiaomi fked up the system now blackmarket abuse this kind of restrictions
fireclouu said:
i want to do edl mode flashing but some encryption needed, even at qfil cant flash the thing, needs to modify prog files and crack it
Click to expand...
Click to collapse
What are we even talking about anymore?
You'll pay 20$ for edl that likely won't do anything, you're just delaying inevitable. If pmic is not reset via bootloader ( fastboot reboot bootloader ) that's where you start thinking it's hardware issue.
What do u even wanna flash? Open stock ROM folder and enter folder called images on pc - look what's inside, persist, cust, boot everything is in there and was flashed already...
Just take your phone to service center while you still can , if under warranty keep requesting new motherboard . They'll likely try battery replacement first.
If it's not under warranty then ok play around as much you feel the need to , it just makes no sense to beating your head with all of this when warranty covers it
Rstment ^m^ said:
What are we even talking about anymore?
You'll pay 20$ for edl that likely won't do anything, you're just delaying inevitable. If pmic is not reset via bootloader ( fastboot reboot bootloader ) that's where you start thinking it's hardware issue.
What do u even wanna flash? Open stock ROM folder and enter folder called images on pc - look what's inside, persist, cust, boot everything is in there and was flashed already...
Just take your phone to service center while you still can , if under warranty keep requesting new motherboard . They'll likely try battery replacement first.
If it's not under warranty then ok play around as much you feel the need to , it just makes no sense to beating your head with all of this when warranty covers it
Click to expand...
Click to collapse
its true , im just trying to figure this out myself if possible or not, accessing service center here is much more troublesome rather fixing it in such way i think possible
but yeah ill update soon enough, tomorrow will be my only day off for a week, will definitely take a visit, wish me luck!
update: i sent my phone to mi authorized drop points yesterday. expected to get it repaired within 2 weeks and to pick it up next month.
update: today Ill pickup my device, will ask what could be the cause of the issue
fireclouu said:
update: today Ill pickup my device, will ask what could be the cause of the issue
Click to expand...
Click to collapse
Good luck! Let us know
so I got the device, support told me about the issue: battery only replugged, no other service, no replacements needed, seems some wirings got loose.
Ive read similar incident here, s/he only did replug the cable, got it fixed. Same issue on my end