Related
*** The issue is resolved!!! Thanks to xda, the solution is provided in the link in the comments.***
Couple of days ago I got this OTA notification that Android 7.1 preview is available for update. As my phone is rooted I started the manual update procedure. After the flashing was finished, I restarted the phone and then I saw it was stuck at the Google screen. Just stuck, no response. Seemed unusual to me.
Let me tell you that I have been modding my Nexus 5 for about two years. I am familiar with most of the tweaks that can be done to a Nexus device. Nexus 5 served me amazingly. I bought Nexus 5x 3 months ago.
So, after it was stuck I restarted. Still stuck. I will tell you step by step what I did then:
1. Flashed the OS 7.1 again (I dunno why, the flash.all script doesn't work for me, so I always do that manually) - result is the same.
2. Last October update (NBD90W) was available in the folder so I flashed that - same result.
3. I downloaded the previous one (NRD90S) and flashed that - same result.
4. I locked the phone and unlocked again to erase everything (not sure if that's a good idea), then flashed the OS again - same result.
5. Then I tried LGUP and the tot files to give it the factory version. LGUP detects the phone, started installing. When the installation is finished and the phone restarted - same result.
6. Now that I gave it the factory version the phone got locked!
7. I searched google for hours but couldn't find a way to unlock it as the OS is not booting and I cannot turn USB debugging on!
8. Then I tried the default recovery mode (Android recovery, from the recovery screen Power + volume up) as it doesn't require unlocking the device. Wiped the cache and restarted - same result.
9. My phone is detected by the pc and ADB. So, I wiped everything and tried ADB sideload and get this error E: footer is wrong
10. I tried Nexus root toolkit. It detects the phone in fastboot mode, then restarts it and then it again is stuck on the Google screen.
I am extremely depressed!
I am from Bangladesh and there is no authorized LG servicing center here. So, I can't ask for their help.
All that I did over the past two years was the awesome threads of xdadevelopers. So, a big thumbs up for you guys . :good:
I learnt from the web that phone can be hard bricked if a wrong bootloader is flashed. That's impossible for me as I always remove the factory image extracted files after flashing is done from the ADB>platform-tools folder.
Now, is the phone hard-bricked? If it is, what to do with it? Will replacing the motherboard get my phone back? Any kind of suggestion will be very much appreciated.
Bummer. This sounds a lot like what I just posted here: http://forum.xda-developers.com/nexus-5x/help/req-help-bootloop-7-1-1-beta-ota-enter-t3486957
I really hope someone has an idea how to fix this...
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
what is your model H790 or H791
16 or 32 GB?
DC_Knight said:
Bummer. This sounds a lot like what I just posted here: http://forum.xda-developers.com/nexus-5x/help/req-help-bootloop-7-1-1-beta-ota-enter-t3486957
I really hope someone has an idea how to fix this...
Click to expand...
Click to collapse
Well, I don't get bootloops, my phone is just stuck at the Google screen and I can enter recovery mode (lying Android with red exclamation mark), from there I can enter Android recovery mode, where ADB sideload is available.
harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
Like I mentioned in point 5, I did exactly that as mentioned in this link.
Duckscreen said:
what is your model H790 or H791
16 or 32 GB?
Click to expand...
Click to collapse
It's H791, 32 GB.
There is no more reply
I need to know one thing. Will replacing the motherboard fix the phone? Anyone??
jadu45 said:
There is no more reply
I need to know one thing. Will replacing the motherboard fix the phone? Anyone??
Click to expand...
Click to collapse
How about trying to get a replacement if you're still within the 1 year warranty?
Sent from my Nexus 5X using Tapatalk
EeZeEpEe said:
How about trying to get a replacement if you're still within the 1 year warranty?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
"I am from Bangladesh and there is no authorized LG dealer/servicing center here. So, I can't ask for their help."
I'm on my own...
jadu45 said:
"I am from Bangladesh and there is no authorized LG dealer/servicing center here. So, I can't ask for their help."
I'm on my own...
Click to expand...
Click to collapse
Ah my bad. TL;DR on my end.
Sent from my Nexus 5X using Tapatalk
Please say something about replacing the motherboard. It's very very pricey, so I want to be sure -_-
sounds like its hardware problem, contact seller to replace it. if not going to happen, then buy a new phone from a company that does have a dealer in your country to warrant. aside of camera, the specs of other phones at this price range are better
That thought is also roaming around my head, still Nexus is Nexus!
What's the price going for the 5X over there? It's as low as $280 here in the US which is easy better then it's original.
Sent from my Nexus 5X using Tapatalk
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
questionquince said:
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
Click to expand...
Click to collapse
Thanks for this, it looks interesting and I definitely didn't try that. I'm at office right now, I'll let you know after trying this.
harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
There was a difference in the method here and I didn't realize that before; as it was written at the bottom. Sorry about that. I'll try this method and let you know. Thanks!
jadu45 said:
There was a difference in the method here and I didn't realize that before; as it was written at the bottom. Sorry about that. I'll try this method and let you know. Thanks!
Click to expand...
Click to collapse
Goodluck, and let us know the result.. :fingers-crossed:
A warranty is a warranty, it doesn't matter what country you're in or where the repair place is. People in Canada send stuff to the USA for warranty issues all the time. I'd get on the phone with LG until I heard what I wanted, but I'm a stubborn old goat lol.
ShishkaBerry said:
A warranty is a warranty, it doesn't matter what country you're in or where the repair place is. People in Canada send stuff to the USA for warranty issues all the time. I'd get on the phone with LG until I heard what I wanted, but I'm a stubborn old goat lol.
Click to expand...
Click to collapse
Well, there is no authorized dealer here; I had to buy it from a local shop. So, there is no warranty!
harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
questionquince said:
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
Click to expand...
Click to collapse
Both of you provided me the link. I don't know who you are, but I if I find you you guys are going to have a treat for sure. I literally cried when I got my phone back. Thank you guys. Thanks xda!
Hello, Iam having a bricked Google Pixel XL 128GB with black screen, no fastboot, no recovery(phone only detected as HS-USB QDLoader 9008).
Is there anyway to unbrick the phone?
What was your setup before this happened? What were you trying to do before this happened?
chapelfreak said:
What was your setup before this happened? What were you trying to do before this happened?
Click to expand...
Click to collapse
Bad Flash on OTA update
Hey... Actually, there's no easy way to get the pixel back up and running. I tried to read a bit about the issue on different phones. I'm not sure it could be of some use for our device.. It also involves, either having someone to pull a full backup of his phone for you which you'll have to find... Or finding special Qualcomm files and firmware used for flashing using Qualcomm tool QFIL... I haven't found Qualcomm files/firmware on the internet yet... And i'm not 100% sure the first solution would work either, since we have now different system partitions.
If you don't have any warranty on your phone, you could try it. Otherwise, send it back. There's likely no way to recover personnal datas anyway...
Also about getting out of EDL mode, i've read in the N6P forum, someone saying you'll have to push the power button for no less than 40 seconds. Try it maybe and try to reboot into bootloader afterward...
Good luck...
5.1 said:
Hey... Actually, there's no easy way to get the pixel back up and running. I tried to read a bit about the issue on different phones. I'm not sure it could be of some use for our device.. It also involves, either having someone to pull a full backup of his phone for you which you'll have to find... Or finding special Qualcomm files and firmware used for flashing using Qualcomm tool QFIL... I haven't found Qualcomm files/firmware on the internet yet... And i'm not 100% sure the first solution would work either, since we have now different system partitions.
If you don't have any warranty on your phone, you could try it. Otherwise, send it back. There's likely no way to recover personnal datas anyway...
Also about getting out of EDL mode, i've read in the N6P forum, someone saying you'll have to push the power button for no less than 40 seconds. Try it maybe and try to reboot into bootloader afterward...
Good luck...
Click to expand...
Click to collapse
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
droidan said:
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
Click to expand...
Click to collapse
Yeah I haven't found anything either. I think it will take some time before someone share those.
Check this thread:
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This part:
2. REVIVING YOUR YU BACK
2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE
As I said earlier, since our phone has a different partition layout, I don't know if the same process can be achieved. Also you'll have to pull the IMG from a working device.
You don't have a valid warranty?
5.1 said:
Yeah I haven't found anything either. I think it will take some time before someone share those.
Check this thread:
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This part:
2. REVIVING YOUR YU BACK
2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE
As I said earlier, since our phone has a different partition layout, I don't know if the same process can be achieved. Also you'll have to pull the IMG from a working device.
You don't have a valid warranty?
Click to expand...
Click to collapse
Thank you for your reply and information.
I believe I have an OLD 9008 mode.
Here's what I have found:
1. The 8996 firehose is specific to the device. Other 8996 version do not work. (Oneplus 3T, ZUK, Xiaomi, LEECO)
2. Quote from Ghassani on Le Pro3 bricked thread:
"Since it was suggested to contact me about this issue, I am going to answer here what I told the OP through email:
This is a hard brick. Meaning, you probably flashed a wrong SBL partition, or you flashed in the wrong order, or in the wrong mode.
When this happens, and the device has secure boot enabled (which all production devices do) you only have two options:
1) Using a signed recovery programmer to send via emergency mode (Sahara mode), then transferring to that programmers protocol (streaming DLOAD or the newer firehose). From there you can recover the emmc.
2) JTAG on the emmc for direct recovery.
It is easy to find these programmer files, both signed and unsigned. The problem is each device is using a different private key generated by the OEM to build the SoC. Without a properly signed programmer, Sahara will reject the programmer and go into a no-interrupt loop until you power cycle the device. Pretty much all OEMs do not give out these files. The ones you can find floating around for various devices are generally leaked, or rarely given out by the OEM. For most devices, JTAG is the only option.
I have a small collection of both signed and unsigned programmer files on this github repository:
https://github.com/ghassani/openpst-assets
If anyone has properly signed files for devices I do not have, please send them in to me and I can add them or you can put in a pull request directly to the repository and add it that way."
Hopefully someone from Google/HTC can share those 3 files.(eMMc_firehose_8996.elf, rawprogram0.xml and patch0.xml for Google Pixel XL 128GB)
Or maybe I can ask Google assistant to leak the files..lol
droidan said:
Bad Flash on OTA update
Click to expand...
Click to collapse
What does that mean? Were you rooted, unlocked? If so return the device, no?
droidan said:
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
Click to expand...
Click to collapse
Sent from my Pixel using XDA-Developers Legacy app
droidan said:
Thank you for your reply and information.
I believe I have an OLD 9008 mode.
Here's what I have found:
1. The 8996 firehose is specific to the device. Other 8996 version do not work. (Oneplus 3T, ZUK, Xiaomi, LEECO)
2. Quote from Ghassani on Le Pro3 bricked thread:
"Since it was suggested to contact me about this issue, I am going to answer here what I told the OP through email:
This is a hard brick. Meaning, you probably flashed a wrong SBL partition, or you flashed in the wrong order, or in the wrong mode.
When this happens, and the device has secure boot enabled (which all production devices do) you only have two options:
1) Using a signed recovery programmer to send via emergency mode (Sahara mode), then transferring to that programmers protocol (streaming DLOAD or the newer firehose). From there you can recover the emmc.
2) JTAG on the emmc for direct recovery.
It is easy to find these programmer files, both signed and unsigned. The problem is each device is using a different private key generated by the OEM to build the SoC. Without a properly signed programmer, Sahara will reject the programmer and go into a no-interrupt loop until you power cycle the device. Pretty much all OEMs do not give out these files. The ones you can find floating around for various devices are generally leaked, or rarely given out by the OEM. For most devices, JTAG is the only option.
I have a small collection of both signed and unsigned programmer files on this github repository:
https://github.com/ghassani/openpst-assets
If anyone has properly signed files for devices I do not have, please send them in to me and I can add them or you can put in a pull request directly to the repository and add it that way."
Hopefully someone from Google/HTC can share those 3 files.(eMMc_firehose_8996.elf, rawprogram0.xml and patch0.xml for Google Pixel XL 128GB)
Or maybe I can ask Google assistant to leak the files..lol
Click to expand...
Click to collapse
Yeah, unless someone leaks official programmer, you are SOL...
Good luck... :good:
Hi guys,
I've opened a similar thread on google forum - related to pixel 128gb being bricked and in chipset download mode.
If there are enough bricked pixels out there perhaps google will (hopefully) share those files?
Cheers,
Dan
The deluge of bricked Pixels resulting from the Oreo update continues...
I did, however, find these pages posted in the last couple weeks, and wondering if they're the answer to the Q's posted earlier ITT (sry I'm too new to post live links, so you'll have to paste these):
- androidauthority.com/download-android-8-0-oreo-794622/
- androidauthority.com/install-android-oreo-758342/
- developers.google.com/android/ota
Earlier ITT, posters were saying that they couldn't find the firmware or other files that would allow someone to recover from the hard-bricked state...but are those 'official' factory images and OTAs what they were saying they needed, but which they couldn't find at the time? In short, might we now actually have the files necessary to save our bricked Pixels without engaging in Macguyvering that would void the warranty?
Out of curiosity, was your bootloader locked prior to running into this issue?
Pain-N-Panic said:
Out of curiosity, was your bootloader locked prior to running into this issue?
Click to expand...
Click to collapse
I assume so...I bought the Pixel directly from Google, so assumed I was getting the purest Android installation possible / no provider bloatware etc...if i'm not mistaken, the bootloader would have been Locked when I initially received the phone, right?...if so, then yes it would still have been locked when it bricked, as I didn't take any actions to unlock it (nor would i know how)
hopefully files will be shared soon for sure it is exists
I have the same problem and all I can do is rma.
Is it possible to pull the files from a working pixel?
I wonder if the files in question would hold the key to VZW Pixel XL customers to somehow use /find an exploit to gain temp root to ultimately unlock their bootloader.
mattwheat said:
I wonder if the files in question would hold the key to VZW Pixel XL customers to somehow use /find an exploit to gain temp root to ultimately unlock their bootloader.
Click to expand...
Click to collapse
Maybe that's why they aren't giving the files
This happened to mine as well
Went from 8.0 to 8.1 - wiped data and re-locked bootloader. Ran fine for two days then powered down and now I'm in this qualcomm mode. Thankfully I purchased the 2-year through Google. Unfortunately their support is dogsh**.
Update: Ok Google's support rep was actually pretty solid but their system is awful. I'm already on a refurb and it doesn't have the IMEI printed on the sim tray. Either way they worked it out and I'm down $80 for the deductible.
I have the same problem
Ok so i was just rooting when my phone decides to die during so commands in adb. :crying:
Now i cant turn on the phone or boot into fastboot or bootloader. everytime i plug it in the charging light just flashes. Also my computer recognises the device as qualcomm hs-usb qdloader 9008 . ive read around the internet and ive found two methods. blank flash and qfil. issue is those tutorials were made for the moto g5 plus. I have searched around the internet and im beginnign to lose hope now. Can someone tell me how to fix this or give me the right blankflash version.
much appreciated
Im sorry that i cant post a useful reply for your problem that you cant even boot into fastboot / hardbricked phone.
The following link is for all those that are stuck in fastboot mode / boot loop.
This post says its for indian version, but i have EU version (1676) and it worked for me to get back my phone as it was when bought:
https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
Kim Il said:
Im sorry that i cant post a useful reply for your problem that you cant even boot into fastboot / hardbricked phone.
The following link is for all those that are stuck in fastboot mode / boot loop.
This post says its for indian version, but i have EU version (1676) and it worked for me to get back my phone as it was when bought:
https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
Click to expand...
Click to collapse
Thanks but unfortunately still cant access bootloader or fastboot to do so :/
rajibahmed said:
Thanks but unfortunately still cant access bootloader or fastboot to do so :/
Click to expand...
Click to collapse
if you cant access bootloader take it to a repair shop - you need specialist software and hardware to re-image your phone
how on earth did you do that - you do know to root this device its just a simple zip flashing in recovery mode - no fancy commands or anything required once you have unlocked the bootloader via the very easy to follow guide on the moto unlock bootloader website
TheFixItMan said:
if you cant access bootloader take it to a repair shop - you need specialist software and hardware to re-image your phone
how on earth did you do that - you do know to root this device its just a simple zip flashing in recovery mode - no fancy commands or anything required once you have unlocked the bootloader via the very easy to follow guide on the moto unlock bootloader website
Click to expand...
Click to collapse
Its a long story. Basically i rooted it successfully but one of my favourite apps (snapchat) wasnt letting me sign in because i was rooted. I tried everything to mkae it work. Eventually i tried to unroot sign in and reroot to make it work. At that moment something went terribly wrong idk what but now im hardbricked.
rajibahmed said:
Its a long story. Basically i rooted it successfully but one of my favourite apps (snapchat) wasnt letting me sign in because i was rooted. I tried everything to mkae it work. Eventually i tried to unroot sign in and reroot to make it work. At that moment something went terribly wrong idk what but now im hardbricked.
Click to expand...
Click to collapse
If you are using LineageOS all you had to do was just go into dev settings switch root to disable & restart the phone
If you used magisk just use the magisk uninstaller then reflash the kernel
I don't understand why you touched the bootloader partition
TheFixItMan said:
If you are using LineageOS all you had to do was just go into dev settings switch root to disable & restart the phone
If you used magisk just use the magisk uninstaller then reflash the kernel
I don't understand why you touched the bootloader partition
Click to expand...
Click to collapse
I dunno y either. Luckily I had insurance on it so now I got a new device
Although even though I'm sorted it think we need a way to fix hardbricked devices because the Moto g5plus and g4s have fixes but I haven't found any that work for Cedric devices
rajibahmed said:
Although even though I'm sorted it think we need a way to fix hardbricked devices because the Moto g5plus and g4s have fixes but I haven't found any that work for Cedric devices
Click to expand...
Click to collapse
How did u fix
infixremix said:
How did u fix
Click to expand...
Click to collapse
I had insurance so I just replaced the whole device
rajibahmed said:
I had insurance so I just replaced the whole device
Click to expand...
Click to collapse
Wtf insurance covers it ?
infixremix said:
Wtf insurance covers it ?
Click to expand...
Click to collapse
Ish. I had Argos insurance and they basically take any dead device. Plus they don't check if it's been tampered with . I just said it didn't turn on
rajibahmed said:
Ish. I had Argos insurance and they basically take any dead device. Plus they don't check if it's been tampered with . I just said it didn't turn on
Click to expand...
Click to collapse
Motorola warranty takes hardbricked dvices with locked bootlloadder?
CypherPotato said:
Motorola warranty takes hardbricked dvices with locked bootlloadder?
Click to expand...
Click to collapse
How the hell did u hradbrick ur device without an unlocked bootloader. And idk I think that after you start tampering with the os and system it kills ur warranty. You'll have to chat with someone at Motorola
hello people, I have a black screen after flashing the FW and can't get out of it.
Battery is fully charged
Pressing key combinations doesn't help.
when the mobile phone is connected to the pc, there is a brief message that a device has been connected to the pc.
please urgently for help
thx
neroes said:
Pressing key combinations doesn't help.
Click to expand...
Click to collapse
Fastboot mode not working?
NOSS8 said:
Fastboot mode not working?
Click to expand...
Click to collapse
No ... pressing VOL+down dosnt work
fastboot devices
negativ
neroes said:
No ... pressing VOL+down dosnt work
fastboot devices
negativ
Click to expand...
Click to collapse
I sent you a PM
So just a Black Screen? No Recovery or Fastboot?
You might have to flash a ROM via EDL Mode... The unfortunate thing though is that it will cost you money, unless you still have Warranty...
You said your PC briefly says that your phone got connected. In Device Manager, does it say "Qualcomm 9008" ? That would indicate that your phones' SOC detected that the Bootloader isn't working, and so, instead booted into the EDL Mode (Emergency DownLoad Mode), which is a read-only Mode inside the SOC itself.
cyanGalaxy said:
So just a Black Screen? No Recovery or Fastboot?
You might have to flash a ROM via EDL Mode... The unfortunate thing though is that it will cost you money, unless you still have Warranty...
You said your PC briefly says that your phone got connected. In Device Manager, does it say "Qualcomm 9008" ? That would indicate that your phones' SOC detected that the Bootloader isn't working, and so, instead booted into the EDL Mode (Emergency DownLoad Mode), which is a read-only Mode inside the SOC itself.
Click to expand...
Click to collapse
is now fixed, yes was in EDL mode.
it's a shame that I didn't know about the guarantee... the phone is only 6 months old... now I've paid $25 to "unlock" it
neroes said:
is now fixed, yes was in EDL mode.
it's a shame that I didn't know about the guarantee... the phone is only 6 months old... now I've paid $25 to "unlock" it
Click to expand...
Click to collapse
Sorry about that.
What did you do to make that happen? From which FW to which FW did you upgrade to?
cyanGalaxy said:
Sorry about that.
What did you do to make that happen? From which FW to which FW did you upgrade to?
Click to expand...
Click to collapse
My mistake was to listen to someone else and downgrade the firmware
neroes said:
My mistake was to listen to someone else and downgrade the firmware
Click to expand...
Click to collapse
that is weird because noting shoould happen when you change firmware.did you use twrp or adb sideload via recovery?
neroes said:
My mistake was to listen to someone else and downgrade the firmware
Click to expand...
Click to collapse
Downgrading is not a problem if the instructions are followed correctly.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
This is why it is important to give as much detail as possible when asking a question.
If you had specified that the phone was less than 6 months old, I would have directed you to the warranty as suggested by CyanGalaxie.
Currently the guarantees are under contracted by Xiaomi and the returns are very bad (loss of the phone, broken screen, long delays, etc.).
In your case you got your phone back in 15 minutes, maybe it's better that way.
So I'm satisfied that it really worked within half an hour to "unlock" my cell phone again instead of sending it in etc.
I just tried to downgrade via sideload. that led to the EDL
All in all I'm glad that my cell phone is working again ... I'm just annoyed because I've been playing around with all sorts of cell phones for over 10 years and I couldn't figure it out myself
neroes said:
So I'm satisfied that it really worked within half an hour to "unlock" my cell phone again instead of sending it in etc.
I just tried to downgrade via sideload. that led to the EDL
All in all I'm glad that my cell phone is working again ... I'm just annoyed because I've been playing around with all sorts of cell phones for over 10 years and I couldn't figure it out myself
Click to expand...
Click to collapse
The best way to downgrade is to use Miflash or the bat file (Fastboot rom)included in the rom folder to avoid ARB.
Phones have since changed, notably with dynamic and A/B partitions.
If you were trying to downgrade/upgrade the FW due to requirement/recommendation by your Custom ROM, you can simply flash the FW inside TWRP/OrangeFox.
cyanGalaxy said:
If you were trying to downgrade/upgrade the FW due to requirement/recommendation by your Custom ROM, you can simply flash the FW inside TWRP/OrangeFox.
Click to expand...
Click to collapse
This method to have the right firmware for for example an aosp rom does not always work sometimes it is necessary to flash the full rom.
For a version change on a stock rom use fastboot roms which contain all the imgs.
Yeah, stupid anti-rollback thing. Threads like these make me wish someone already unlocks the EDL flashing. I heard developers need some source code or something for it, I'm not sure. But that needs to happen ASAP.
It's totally evil to keep EDL restricted.
user0u said:
Yeah, stupid anti-rollback thing. Threads like these makes me wish someone already unlocks the EDL flashing. I heard developers need some source code or something for it, I'm not sure. But that needs to happen ASAP.
It's totally evil to keep EDL restricted.
Click to expand...
Click to collapse
For ARB okay but for EDL mode it's just a matter of security, you lose or your phone is stolen and just flash in edl mode and the phone is yours, no.
Then the guy will only be able to flash AOSP roms as he will be blocked by the Xiaomi account.
Note that this only concerns Qualcomm Socs,Mediatek are more less secure.
@NOSS8 We are modders and tinkerers here man. We were doing just fine before these restrictions. These restrictions have been added less for "security" and more to take control away from the end users anyway.
user0u said:
@NOSS8 We are modders and tinkerers here man. We were doing just fine before these restrictions. These restrictions have been added less for "security" and more to take control away from the end users anyway.
Click to expand...
Click to collapse
Not everyone is like you or me, there are thieves and crooks,otherwise we would be in a perfect world.
user0u said:
Yeah, stupid anti-rollback thing. Threads like these make me wish someone already unlocks the EDL flashing. I heard developers need some source code or something for it, I'm not sure. But that needs to happen ASAP.
It's totally evil to keep EDL restricted.
Click to expand...
Click to collapse
There are patched Firehose files (for QPST) on the internet (apparently circumvents the required Account authorisation). I can't provide a link, but you can google it.
But I'm not sure if those work, because I couldn't find one for Poco F3, and so I too had to pay 25$
It's very annoying that people buy into these pseudo-security lies we're getting fed so often (especially Apple Users). People don't realise this is not about protecting consumers, but simply for lé money. It has always been about the money.
Xiaomi locked the EDL Mode, because people kept buying their phones from China and import them to EU/USA, flash software with GMS and sell them here.
And locking EDL Mode causes more people to pay for Xiaomi Service Centres. xddd
I wish people would just have a healthy amount of criticism and not fanboy for any company, except for Valve. Valve is cool. Valve is love
Hey guys! I finally got my OnePlus 11 yesterday in the USA! Love this phone! I'm reading into how to recover this phone if it ever bricks (mine isn't bricked lol) and I'm seeing we CAN'T just download and use MSM Tool like we could on previous OnePlus devices??? How does this work now with the 11 in mind? Thanks y'all!
H4X0R46 said:
Hey guys! I finally got my OnePlus 11 yesterday in the USA! Love this phone! I'm reading into how to recover this phone if it ever bricks (mine isn't bricked lol) and I'm seeing we CAN'T just download and use MSM Tool like we could on previous OnePlus devices??? How does this work now with the 11 in mind? Thanks y'all!
Click to expand...
Click to collapse
no msm tool for op 10 and op11 and newer ( only with Auth.)
ChrisFeiveel84 said:
no msm tool for op 10 and op11 and newer ( only with Auth.)
Click to expand...
Click to collapse
With auth? Like, you would have to get with OnePlus and THEY would have to MSM this device if it ever needed it?
H4X0R46 said:
With auth? Like, you would have to get with OnePlus and THEY would have to MSM this device if it ever needed it?
Click to expand...
Click to collapse
if your op11 bricks and you want to fix it yourself, it can no longer be done with the msm tool, your only option is to go to a services center or someone who can do it via remute session
ChrisFeiveel84 said:
if your op11 bricks and you want to fix it yourself, it can no longer be done with the msm tool, your only option is to go to a services center or someone who can do it via remute session
Click to expand...
Click to collapse
That's SUCH a terrible decision on their part! Damn! All other OEMs freely make unbricking tools available, OnePlus SUCKS for this decision. Well alrighty.
Side question, you may or may not be able to answer this one. Is there any way to do local upgrades on the 11? Like, that was always the easiest way to update a rooted OnePlus phone in the past, but now that option is gone from their newer devices?
H4X0R46 said:
That's SUCH a terrible decision on their part! Damn! All other OEMs freely make unbricking tools available, OnePlus SUCKS for this decision. Well alrighty.
Side question, you may or may not be able to answer this one. Is there any way to do local upgrades on the 11? Like, that was always the easiest way to update a rooted OnePlus phone in the past, but now that option is gone from their newer devices?
Click to expand...
Click to collapse
bootloader unlock, root and co still work just not anymore unbricking by msm tool
and which manufacturer still has an unbrick tool?
H4X0R46 said:
Side question, you may or may not be able to answer this one. Is there any way to do local upgrades on the 11? Like, that was always the easiest way to update a rooted OnePlus phone in the past, but now that option is gone from their newer devices?
Click to expand...
Click to collapse
If you turn on the "programmer's options", the "local updates" option will be activated.
qriozum said:
If you turn on the "programmer's options", the "local updates" option will be activated.
Click to expand...
Click to collapse
Developer options you mean? Alright, I activated developer options, where is the local update button added? Not seeing it.
H4X0R46 said:
Developer options you mean? Alright, I activated developer options, where is the local update button added? Not seeing it.
Click to expand...
Click to collapse
Settings/Device information/tile OxygenOS - in the upper right three dots - the last item of three is "local update"
hi, really doesnt exist chance myself repair bricked 1+ 11?
qriozum said:
Settings/Device information/tile OxygenOS - in the upper right three dots - the last item of three is "local update"
Click to expand...
Click to collapse
I don't have that And developer options is activated for me. Weird.
H4X0R46 said:
I don't have that And developer options is activated for me. Weird.
Click to expand...
Click to collapse
Usa devices ?
And you look here ?but if I remember correctly, usa devices don't have a local update included because they get the updates via Google (correct me if I'm wrong)
ChrisFeiveel84 said:
Usa devices ?
And you look here ?but if I remember correctly, usa devices don't have a local update included because they get the updates via Google (correct me if I'm wrong)
View attachment 5839835View attachment 5839843
Click to expand...
Click to collapse
Streamable Video
Watch this video on Streamable.
streamable.com
Yeah check this out Maybe it's different for the 11? I notice yours is a 9 pro
H4X0R46 said:
Streamable Video
Watch this video on Streamable.
streamable.com
Yeah check this out Maybe it's different for the 11? I notice yours is a 9 pro
Click to expand...
Click to collapse
Usa devices
This have no lokale update
the usa mostly only gets incremental updates (every now and then a full rom pack)
but someone who has a usa model himself can certainly say more about whether there is a local update in it
H4X0R46 said:
Streamable Video
Watch this video on Streamable.
streamable.com
Yeah check this out Maybe it's different for the 11? I notice yours is a 9 pro
Click to expand...
Click to collapse
Unfortunately on US devices there's no local update. It's been this way for awhile. On the 9pro and 10pro you could use the local update apk from OnePlus to do local updates but considering the US rarely gets full zips anymore (we only get incremental from Google servers in US), there isn't much point for us to use it. You can still root and re-root after updates but you need to be more careful without having the full updates (and without having the freely available MSM tool like we used to have). On the 10 pro I would always replace the patched boot.img with stock then do the incremental update and then re-root after the update. Not so sure on 11 right now since it uses the init_boot.img and you can't just boot that, you have to flash it. Until more people post on rooting and updating the US model, I think I'll hold off on root, and I always root all of my phones.
jeffsga88 said:
Unfortunately on US devices there's no local update. It's been this way for awhile. On the 9pro and 10pro you could use the local update apk from OnePlus to do local updates but considering the US rarely gets full zips anymore (we only get incremental from Google servers in US), there isn't much point for us to use it. You can still root and re-root after updates but you need to be more careful without having the full updates (and without having the freely available MSM tool like we used to have). On the 10 pro I would always replace the patched boot.img with stock then do the incremental update and then re-root after the update. Not so sure on 11 right now since it uses the init_boot.img and you can't just boot that, you have to flash it. Until more people post on rooting and updating the US model, I think I'll hold off on root, and I always root all of my phones.
Click to expand...
Click to collapse
Shoot and I'm exactly the same! I really want to root my OnePlus 11, but knowing this phone absolutely isn't easy to recover, it does deter me a bit... Shoot I can't even get this phone into fastboot mode, holding volume up and down goes into recovery instead How the hell do I get this phone into fastboot mode to begin with?
H4X0R46 said:
Shoot and I'm exactly the same! I really want to root my OnePlus 11, but knowing this phone absolutely isn't easy to recover, it does deter me a bit... Shoot I can't even get this phone into fastboot mode, holding volume up and down goes into recovery instead How the hell do I get this phone into fastboot mode to begin with?
Click to expand...
Click to collapse
Should be able to just enable USB debugging and use adb reboot bootloader. Haven't personally bothered yet until I'm sure there's a good way to root, un-root, update and re-root. Don't want to brick and have to send back to OnePlus to repair, granted they do fix it for free, but we still shouldn't have to send it in to fix it. We should be able to recover our phones ourselves.