I'm creating this thread because i have a moto G4 xt1621 bricked by OTA android 7.0 update.
my phone is from latin america dual sim model 16gb rom.
bootloader unlocked, twrp installed plus lineage oficial 7.1.2 for ATHENE running for more than a year no problems.
one day i was using it for videos and realized the quality was not very good so i decided to install the original android 6.0.1 from motorola to check if the quality of the main camera improved, all went ok thru fastboot and the phone rebooted to android 6.0.1 no problems, so the downgraded android was not the problem, yes the cam improved the video quality a little, moto cam vs ported lineage cam is one step down in my opinion the later, flashed a custom logo.bin to hide the unlocked bootloader screen of pain and all was ok, then the phone asked for an update OTA to android 7.0 and i declined but days later i decided to test the 7.0 flavor against the marshmallow in camera quality tings, why why i'm such a nerdddd whyyyyyyy.....
the update 990 Mbit downloaded in under 10 min, i got 100 meg fiber lol.
the phone started to install the update and after 85% 20 min or so, pum! dead screen in front of me, i was like wth is connected to the pc plus the battery have over 75%, hit the power on, nothing, disconnected from pc, connected again, only the famous bricked flashing white led of dead pulsing was alive no combination of buttons or usb connections did nothing.
googling find lost of threads talking about OTA 7.0 from motorola bricking phones that dont do it in steps like marshmallow to the first nougat then the next security update and so on, when you go from 6.0.1 to the latest nougat OTA lost of ATHENE´s die bricked with no hope.
the problem is in the GPT.bin and BOOTLOADER.bin binaries of the marshmallow and the latest nougat NOT BEING COMPATIBLE AT ALL.......
FIX
after a full day and i meant 20 hours in front of the pc i find the right combination of tools for my problem:
in W10 64bit turn test mode on and driver integrity check off from admin powershell (remember to do it backwards after, changing on by off and disable by enable)
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
RESTART PC
download QualcommDrv.zip in this post and install the correct x64 or x86 version of the driver, google motorola usb drivers and install them. (MotorolaDeviceManager_2.5.4.exe)
RESTART PC
connect the phone thru usb 2.0 (regular usb in the MB not add cards or hubs or keyboards) and open device manager, when the pc tell you it do not recognize the usb device or any usb error pop, hit at the same time power and volume down in the phone until the pop in device manager go away or the error disappear.
in device manager you have to look for COM/LPT new entry in the tree and when open it say qualcomm stuff of some kind. (is over 9000 kind 9008 or so dont remember) lol
Download blankflash.zip in this post and unzip it in a folder, run blank-flash.bat
when you do this steps the phone should boot a generic fastboot, there you will have the phone ready to do some magic like installing twrp if the bootloader is unlocked before you bricked the moto or reflash a stock moto original rom, plenty of threads for both that routes here in xda. WORKS FOR ME.
Related
Hello XDA
As title say, I 'm going share my experience in this thread.
History
I purchased this device almost 8 month back.Purchased from a local store.Was very smooth and i was satisfied with the performance.Battery was good.Got regular update and these updates are from google,so why not install it,right?Then this Android N came,and i was so happy.7.0.0 was good.Then the nightmare 7.1.2 came.Phone started to lag continuously,Battery drained too much.But I was like Okay.May be this will fixed in new update.Then suddenly one day my phone was stuck.Not booting.Stucked at Google.I understood that phone already booted and fingerprint was too working but it showed nothing on display just black light.I was afraid as i didn't purchase it from Google Play or any authorized seller.So no warranty or chance of having replacement.So I started searching about this issue and found not only me many people are facing this.But there are no proper guideline or solving this issue.Tried everything and ended up with Locked Bootloader Irony!
Journey
As i never try to mess with my phone because it was Nexus 5x! So i never touch OEM or try to unlock the bootloader.So i tried to access stock recovery,But Alas! in recovery Volume up and down wasn't working.So I couldn't wipe or factory reset.So Now ended up with :
1.Locked Bootloader
2.Locked OEM
3.Recovery Stuck
Googled and found many solutions but none of them came to solve my issue.So i thought why not flash stock rom.But HOW! Cause fastboot only work with unlocked bootloader.And you can't unlock bootloader when your OEM is locked and you can't unlock it with fastboot.It can be only unlocked from developer option only.GOD!
Now I have only 2 options left:
1.Fastboot mod where no functions working
2.Download Mod (This will save you)
Now fastboot option is out and only download mod option is available.So what can i do with Download Mod?
LGUP TOOL helped me.Downloaded a tot file for Global version (LGH791) and flashed it and stucked at google logo and in recovery too.But next time i flashed the same file in a different way.Ok here it is:
1.Drivers are important here.I'm using windows 10.I have adb and fastboot and Lg drivers.Workplace okay.
2.Opened device manager and change the com port of Android phone 3 to 41. Port Changed!
3.Connected my phone to pc using 3rd party cable (Careful here,try to use original cable.) and entered into download mod and.
4.Opened LGUP Tool ,checked REFURBISHED mod,checked BIN file and select the tot file downloaded before.And quicky close it.(No need to click start)
5.Then again opened lg tool and click start.(BIN Checked and it showed the previously selected tot file).No need add anything new this time,just open and click START.
6.Rebooted and again stucked at Google screen.But wait! recovery is working.Pressing and holding volume up button for a while then a android logo with red cross inside will come up.Now holding power button and volume down button at the same time,Recovery will show and menu is working.Great!
7.Now Wiped cache and factory reset.And after that selected Apply update from Adb sideload
8.My device was connected to pc from the beginning,right? Now i downloaded a file previously called bullhead-ota-opp2.170420.019-c449d2bb.zip from Google Nexus 5x OTA update page.
9.In Adb folder,copied the file and named it ota.zip.Opened a command prompt using shift+right click in the folder.Phone was on Adb sideload mode.Typing this command adb sideload ota.zip
10.This took more than 8-9 minutes to finish.After flashing and phone rebooted.WOW
11.Couldn't believe my eyes.The OTA update was about Android O.I quickly enabled the developer menu and made oem unlcocked and usb debugging on.Boot into bootloader and unlock bootloader with this command fastboot flashing unlock
12.Now bootloader is unlocked and i flashed TWRP recovery for future need.
13.Rebooted the phone and after using for 1 minute the phone freezed again
14.This is the end of the story for today.
Planning
I'm thinking the OTA update was the problem.Now I'm downloading 6.0.1 version.And will do a clean install.Let's see what happens next.
Any kind of help is appreciated.If you think there is something i'm missing here then please suggest.
And Thanks to XDA.I got all these helps from here.Will update the post tomorrow.
You downloaded Android O Developer Preview. Final OTAs are here:
https://developers.google.com/android/ota
Just try flashing newest Factory Image via fastboot, but don't forget to flash TWRP back:
https://developers.google.com/android/images
TBH I NEVER thought this phone will be dead by hardware failure all of a sudden, I dont mind another few hundreds bucks but the problem now is the fking data within it.
Cant even pass google logo if you choose Recovery Mode
GG LG, well played
I have a 16gb variant dead....same issue like urs .....can i use the same lgh791 tot file?... in fastboot it says lgh791 16gb
usefully
usefully
I STRONGLY recommend that the original post is corrected to change "Download mod" to "Download mode" in all of its four occurences.
Same for one ocurrence of "Fastboot mod".
It is horribly confusing as it is, as calling them "mod" implies some modification you have to apply to the phone (be it software or hardware).
same of my expirience, flash 4CoreOreo..
my nexus 5x now is fully working
the_uker said:
I STRONGLY recommend that the original post is corrected to change "Download mod" to "Download mode" in all of its four occurences.
Same for one ocurrence of "Fastboot mod".
It is horribly confusing as it is, as calling them "mod" implies some modification you have to apply to the phone (be it software or hardware).
Click to expand...
Click to collapse
I suppose that makes sense. Then again, when an instruction is telling you to boot into download mod.....using common sense I'm gonna understand that's a typo and they meant download mode. But you're right, for some folks that may be a bit of a challenge. Common sense isn't as common as it was when I was young.
And the links?
I'm brazilian and i'm having a hard time to find the links to download stuff. Mine is dead and bootloader blocked. The tutorial seems to work but i can't understand well
Interesting. Thanks
I am an Yu Yureka user starting March, 2015. I have waited 2 years to get the Marshmallow update through OTG before getting root. But this new update is full of glitches such as
1. When my phone is switched off and charging no percentage of charge completion is shown.
2. When pictures taken in HDR mode, camera screen turns green and stay like that until the phone is restarted. Also the picture quality degraded.
3. This new update takes away the advanced reboot option which was under the Developer Options( in Lollipop), so there is no way to go into recovery mode without connecting phone to pc through usb.
Now coming to the main part,
4. There is nothing that can root my phone. Starting from phone applications to pc applications nothing can root it.:crying:
5. So I tried the cmd Process by using command window through PC by unlocking my Bootloader first, after that I installed TWRP.
6. When the above processes were successful, I transferred the Supersu Zip file in the internal and external of my phone and then executed them from TWRP. Surprisingly it was also successful.:good:
7. Now when I turned my phone on and checked with 2 different root checker apps, my phone was still not rooted.:crying:
8. Then I probably tried the Supersu installation more than 10 times, factory reset it more than I can even remember but still nothing.
9. My phone developed a new problem that is it randomly reboots itself.:crying:
If anyone knows any solution to the above problems, specially on how to successfully root my Yu Yureka, plz help me. I lost all my hope and confidence.
Thank You for taking your time and reading this.
I don't know if u have done stuffs properly....so here's the thing...IF U R RUNNING LOLLIPOP OR ABOVE!!!!!! then------------
1. Download latest TWRP from the official site and flash it
2. Flash any latest nougat based roms like ---- lineage os, official RR, aosp extended etc. (there r so much astonishingly beautiful roms and i can't name all of them....please don't mind devs )
X. Flash GApps if you want to from here : opengapps.org (arm64,7.1.x,pico variant)
3. Very imp. for you !!!!!!Flash magisk (latest v13.3) from here : (tiny.cc/latestmagisk) and flash it
P.S. Lineage might not support magisk so you have flash there supersu addon which can be found on their official website (in device tree on the left side search for "extras" on the very last option)
Hit Thanks Button if I helped you
yureka plus not getting detected in pc
hey i too have the same problem but one more is that i cannot connect it to pc its just charge my phone unable to connect it and if i connect it in switched off position it just act as is its charging for a second and stop yu boots abd again it charge and yu boots
Need some input to downgraded from marshmallow to official lollipop for YU Yureka...
I am facing the some issues like automatic restart for yu yureka due tounstable Marshmallow update. Can you please share the steps to downgraded to official update like lollipop.
What a bad day... :crying:
Spent many hours still can't find a fix.
Was running Android 6.0 Stock with TWRP and bootloader unlocked installed, then thought of upgrading to Android 7.0 Stock so I flashed manually the image (Line by Line) using CMD.
After I was unable to flash the stock Nougat ROM, I flashed back to 6.0. Everything was perfectly fine, as I manage to boot into the fresh clean Android 6.0 cause I realized I couldn't flash through Android 7.0 (cuz' errors like (bootloader) slot-count: not found (bootloader) slot-suffixes: not found (bootloader) slot-suffixes: not found keep on popping out...)
So I decided to get update to Nougat via OTA upgrade, so I received the security update for 6.0 first, then when it booted into the Android robot installing, out of sudden, the screen turn black, and I couldn't do anything.
So I panicked and ran to my Windows desktop, connect my Moto X Pure XT1575 to it, device manager detected as Qualcomm HS-USB QDLoader 9008 (COMM 5).
Note: I bought the Moto X Pure through eBay 1.5 years ago, as my country - Singapore didn't have any Moto phones at that point of time and no store sells it. And when I bought it, it was in mint condition and in black. I changed the screen, body, accents and battery. I invested a lot on this phone because I really love this special phone, so I really hope someone could help me find a solution, I can donate to you if there's a solution that works. :crying:
Questions:
1. How to make loader.img for XT1575?
2. How to boot to fastboot when connected to computer? Power + Volume Down? Volume Down all the way? Power all the way? Power + Vol Up & Vol Down?
3. Can I use XT1572 loader.img?
Might want to try and read this. https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Some had success. To get into fast boot its power and volume down. Other than that good luck.
Hi,
I'm not sure I'm posting in the right section but, I had a really bad experience upgrading to android 10. Really sluggish and slow... so I tried to downgrade to android 9 by using Lenovo's Rescue and Smart Assistant.
What I did, is to find the stock ROM for my model, and replace the files downloaded by the Rescue Assistant (which downloaded the latest firmware). The process went through, but now the device wont power on.
When I plug in the USB, windows makes a sound, the charging light comes on, but The rescue Assistant nor SP flash tool is able to flash the latest firmware.
Is it bricked for good?
Model : TB-XF606F
Hardware number : 60
Maybe your computer doesn't recognize your tablet. Did you ever try using sp flash tool with your tablet before? You can try reinstall or install a driver for your table if you haven't done it yet.
Well the tablet is recognized as the "mtk vcom..." in device manager. I guess it is the driver that the lenovo rescue app installed.
I have never used sp flash tool with my tablet, just the lenovo rescue.
I tried on 2 different pc and it is the same thing. I think the problem is that I can't turn off the tablet properly, even though, all I can see is a black screen.
I will try to drain the battery by keeping the power button pressed with some scotch tape. I don't know what I can do else.
Edit: I tried a few other times with flash tool using different setting for the connection (with battery and full speed) and nothnig happened. But now windows says it does not recognize my tablet.
did the same thing exactly. . bricked lenovo m10 fhd plus x600v after i flashed a downgrade version. dont try to downgrade this thing. i had already flashed it with 3 or 4 versions the same way , but when i chose to flash the oldest version available with the model , this tab got completly unresponsive , no feedback when try to boot into recovery, fastboot, or system . neither does it gets recognised in windows or anything - device manager dowsnt recognise this usb device ( in device manager properties comments it reads- USB\DEVICE_DESCRIPTOR_FAILURE). if you find a way to reflash the device please let us know. good luck .
Bricked mine after being completely running smoothly on Lineage, then was messing around trying to get gapps installed and jacked up the partitions. TWRP said no OS. Kept messing around and mistakenly locked the bootloader again with apparently an unverified boot partition. . I couldn't get SP Flash tool to work ever either. Pretty sure it's a door stop now.
Hello everyone !
I'm new on this forum but I really need your help. I tried to fix my mistake all day long yesterday (9am to 2am non stop).
So, basically, I have a OnePlus 8 Pro, Model IN2023.
I had OOS 11 updated. I tried to install OOS 12 Bêta and I did but I had a indian version so a lot of bugs.
I wanted to go back to OOS 11 but it was impossible because I was now in an indian version.
I tried with MyApplication2 to local upgrade and downgrade as recommand in Internet.
I tried to unlock bootloader and the following steps but here my problem:
I unlocked my bootloader then I misclick and I locked again my bootloader.
Then my phone just crashed and put this message:
"The current image (boot/recovery) have been destroyed and can not boot."
So, I forced to turn off the phone and try to go in EDL mode but:
1. ADB doesn't work anymore
2. Fastboot work fine
3. EDL mode is impossible
So, my bootloader is unlocked again. My phone is stuck on Fastboot mode:
Fastboot mode
Product_name - kona
Variant - SM8 UFS
Bootloader version -
Baseband version -
Serial number - eed52b71
Secure boot - yes
Device state - unlocked
I used the official firmware on OnePlus website, I used Python and Payload_dumper.py to have the .img from the .bin of the official firmware.
I tried to flash all the images, I tried to install TWRP, I tried almost everything I found but still stuck in Fastboot. Recovery mode doesn't work.
I tried to boot, to flash, to do everything I could.
I also tried MSM Download Tool but nothing appears inside.
Now, when I connect my phone, it's with a cable in USB-C but 3.0, not 2.0. Maybe that's the problem ?
When I plug my phone, in Device Manager, I have a "!" but the phone is recognized under
"Qualcomm HS-USB QDLoader 9008 (COM6). When I click on it, it says (sorry, I'm about to translate from french):
"Windows can not verify the numeric signature for the drives required for this peripheric. It is possible that a material ou software modification has been installed a corrupted file or with an incorrect signature, or it is a malware from an unknown source (Code 52)"
Please help me, contact me on Whatsapp, or here. Let's do this in direct.
Btw, I have a Macbook Pro to do all this. I used also Windows with Bootcamp.
So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.
andshura said:
So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.
Click to expand...
Click to collapse
Im happy you fixed your phone.
Read this before you even think to go to A12 again on this device.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com