I got an update notification. And clicked to update.
When restarted the phone, the phone went to die. I could not start my phone.
I tried these:
1) Kept my fingers on VOL Down and POWER buttons for 2 minutes (even more), but NO USE.
2) Tried to open screws but my screwdrivers could not fit for them.
I bought it 3 months back, but in Flipkat and no service center near me. Any solution for it?
What update did you flash, and what OS were you on?
What device did you have, and was it charged up when you accepted the update?
echo92 said:
What update did you flash, and what OS were you on?
What device did you have, and was it charged up when you accepted the update?
Click to expand...
Click to collapse
* I got June update I guess.
* My device is moto g4 plus 1643 model India variant.
* When I connected charger, LED light blinks that was near Fingerprint zone.
* Tried device manager software, it helped nothing.
* Tried to put my fingers on POWER and VOLUME DOWN buttons, but no use.
Really disappointed as it was a gift from my brother.
TrueUniue said:
* I got June update I guess.
* My device is moto g4 plus 1643 model India variant.
* When I connected charger, LED light blinks that was near Fingerprint zone.
* Tried device manager software, it helped nothing.
* Tried to put my fingers on POWER and VOLUME DOWN buttons, but no use.
Really disappointed as it was a gift from my brother.
Click to expand...
Click to collapse
Just to clarify - you installed the update and then rebooted or just accepted the notification to begin the update (and then rebooted, after which your device failed to boot)?
Did you have TWRP/root and were you on the stock ROM prior to flashing (or a custom stock ROM)?
echo92 said:
Just to clarify - you installed the update and then rebooted or just accepted the notification to begin the update (and then rebooted, after which your device failed to boot)?
Did you have TWRP/root and were you on the stock ROM prior to flashing (or a custom stock ROM)?
Click to expand...
Click to collapse
The update was downloaded, when installing it went blank and never started up.
* I have TWRP custom ROM before it.
TrueUniue said:
The update was downloaded, when installing it went blank and never started up.
* I have TWRP custom ROM before it.
Click to expand...
Click to collapse
Did you flash a stock recovery before attempting to update? Having TWRP might be causing the hang; try these suggestions from abhi212b https://forum.xda-developers.com/mo...date-build-t3584982/post72114657#post72114657
Can I ask which custom ROM you were on? You won't be able to flash stock OTA updates with TWRP/customised stock ROM.
echo92 said:
Did you flash a stock recovery before attempting to update? Having TWRP might be causing the hang; try these suggestions from abhi212b https://forum.xda-developers.com/mo...date-build-t3584982/post72114657#post72114657
Can I ask which custom ROM you were on? You won't be able to flash stock OTA updates with TWRP/customised stock ROM.
Click to expand...
Click to collapse
My phone is in blank screen. NO start up. No fastboot or recovery mode available. Only light blinks when charger is connected. Then how can I do your suggestions? You didn't understand my problem.
TrueUniue said:
My phone is in blank screen. NO start up. No fastboot or recovery mode available. Only light blinks when charger is connected. Then how can I do your suggestions? You didn't understand my problem.
Click to expand...
Click to collapse
My apologies - I looked through your post history and was wondering if the TWRP/rooting performed previously might have prevented your device from booting.
What is your device detected as when you plug it into your computer, is it Moto G4 or is it Qualcomm HS-USB- 9008 (or similar)?
echo92 said:
My apologies - I looked through your post history and was wondering if the TWRP/rooting performed previously might have prevented your device from booting.
What is your device detected as when you plug it into your computer, is it Moto G4 or is it Qualcomm HS-USB- 9008 (or similar)?
Click to expand...
Click to collapse
When I connected to laptop, it took detected and installed port Qualcomm HS-USB- 9008. But I didn't see special drive detecting beside my other drivers.
TrueUniue said:
When I connected to laptop, it took detected and installed port Qualcomm HS-USB- 9008. But I didn't see special drive detecting beside my other drivers.
Click to expand...
Click to collapse
Right, 2 things to try:
1) Try holding the power button down for 2-3 minutes, this may force a hard restart which might break your device out of whatever state it's in.
2)If 1 doesn't work, you may wish to look into trying a blank-flash (here: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 or here: https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 ) Depending on what happened with the update, you might be lucky. You may wish to have a look at these blank-flashes too, heed the warning: https://forum.xda-developers.com/showpost.php?p=73151763&postcount=6
3)If 1 and 2 don't work, then unfortunately you'll have to locate a repair centre (or try to find a Motorola service centre) that you could send the device to, or ask Flipkart for assistance. Alternatively, save up for another device. Currently, we don't have another option, though it appears that a member is trying to patch a blankflash for the new update: https://forum.xda-developers.com/showpost.php?p=73152979&postcount=21
echo92 said:
Right, 2 things to try:
1) Try holding the power button down for 2-3 minutes, this may force a hard restart which might break your device out of whatever state it's in.
2)If 1 doesn't work, you may wish to look into trying a blank-flash (here: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 or here: https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 ) Depending on what happened with the update, you might be lucky. You may wish to have a look at these blank-flashes too, heed the warning: https://forum.xda-developers.com/showpost.php?p=73151763&postcount=6
3)If 1 and 2 don't work, then unfortunately you'll have to locate a repair centre (or try to find a Motorola service centre) that you could send the device to, or ask Flipkart for assistance. Alternatively, save up for another device. Currently, we don't have another option, though it appears that a member is trying to patch a blankflash for the new update: https://forum.xda-developers.com/showpost.php?p=73152979&postcount=21
Click to expand...
Click to collapse
I got this when I clicked blankflash:
C:\Users\*****\Downloads\Compressed\blankflash1\blankflash>.\qboot.
exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 4.009] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.009] Check qboot_log.txt for more details
[ 4.010] Total time: 4.010s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
C:\Users\*****\Downloads\Compressed\blankflash1\blankflash>pause
Press any key to continue . . .
I think, if any one can find new blankflash, I can fix my phone. I think those blankflases are old. I'm on April update, and failed when I tried for June update.
Related
Hullo,
I succesfully installed Lineage with no problems in the OS, but was unable to access TWRP as it asked for a decryption pattern that didn't seem to match the pattern I set on my phone. I then tried a password in the OS but this also didn't work in TWRP.
After checking the thread again, I found Unjustified had recommended the TWRP found in his bootloader, which I then downloaded and proceeded to install via fastboot. The installation appeared to go smoothly but after that I was unable to turn on my phone.
After pressing the power button I am presented with either the battery icon or the ZTE logo, which disspears after a few seconds followed by three flashing red lights. The last flashing light seems to be cut off part way.
I thought this might be a dead battery but even after charging for an extended period of time the result is the same.
Any help would be very much appreciated!
mvortex3710 said:
Hullo,
I succesfully installed Lineage with no problems in the OS, but was unable to access TWRP as it asked for a decryption pattern that didn't seem to match the pattern I set on my phone. I then tried a password in the OS but this also didn't work in TWRP.
After checking the thread again, I found Unjustified had recommended the TWRP found in his bootloader, which I then downloaded and proceeded to install via fastboot. The installation appeared to go smoothly but after that I was unable to turn on my phone.
After pressing the power button I am presented with either the battery icon or the Axon logo, which disspears after a few seconds followed by three flashing red lights. The last flashing light seems to be cut off part way.
I thought this might be a dead battery but even after charging for an extended period of time the result is the same.
Any help would be very much appreciated!
Click to expand...
Click to collapse
Your phone doesn't seem to be bricked at all.
That was a known issue many G users encountered...
Just boot into TWRP by pressing Power and volume + or choosing it from the bootloader warning screen and reflash the universal B15 N bootloader.
Reboot your phone and from now on it should boot every N rom just fine :fingers-crossed:
Good luck,
Martin
mischa_martin said:
Your phone doesn't seem to be bricked at all.
That was a known issue many G users encountered...
Just boot into TWRP by pressing Power and volume + or choosing it from the bootloader warning screen and reflash the universal B15 N bootloader.
Reboot your phone and from now on it should boot every N rom just fine :fingers-crossed:
Good luck,
Martin
Click to expand...
Click to collapse
I'm glad to hear it is quite common, but I should mention that the three lights persist when I try to load TWRP... I can only get as far as the ZTE logo.
The bootloader warning also hasn't shown since I attempted to flash TWRP as the phone appears to cut off after showing ZTE.
I will try an overnight charge in case the battery is completely empty and somehow slow charging. But any other suggestions are most welcome.
Kind regards,
James
mvortex3710 said:
I'm glad to hear it is quite common, but I should mention that the three lights persist when I try to load TWRP... I can only get as far as the ZTE logo.
The bootloader warning also hasn't shown since I attempted to flash TWRP as the phone appears to cut off after showing ZTE.
I will try an overnight charge in case the battery is completely empty and somehow slow charging. But any other suggestions are most welcome.
Kind regards,
James
Click to expand...
Click to collapse
You should try some button combinations like
Power + volume down
Power + volume down + volume up
And see how the device reacts
It helps connecting the device to a PC to look up in device manager to determine the mode its booted in
mischa_martin said:
You should try some button combinations like
Power + volume down
Power + volume down + volume up
And see how the device reacts
It helps connecting the device to a PC to look up in device manager to determine the mode its booted in
Click to expand...
Click to collapse
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.
mvortex3710 said:
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.
Click to expand...
Click to collapse
As you are in EDL now you have some options.
First I would try to flash a recovery and boot image that is proven to be working fine e.g official twrp https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715 or some A2017G stock boot.img
If that doesn't help you could get in contact with @jcadduono to be a tester for that miflash method. (As your device is already pretty badly bricked)
I don't exactly know how EDL flashing works if it depends on a exact GPT table or not.
But I can say that I flashed every single part of the A2017U bootloader except for NON-HLOS (modem) on my A2017G for each B29 and B15 and it worked just fine. So maybe we just have to exchange the modem file in the EDL package :silly:
If you don't want to take that risk you also could try sending it back to ZTE and hope they don't check the bootloader :fingers-crossed:
(Just a thought: Maybe if the EDL package won't work on your device it will be so heavily damaged ZTE can't check for bootloader unlock and accept it as a warranty case, but don't take that too seriously )
Regards,
Martin
mvortex3710 said:
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.
Click to expand...
Click to collapse
If you are not afraid then try to use my package for A2017G with MiFlash: https://mega.nz/#!88BjXKhA!TnVSobBw5PkmShSqZ-Ni8MCCbnhJP2SWRNvvXqYHSjc
I really appreciate all this advice!
Looks like the MiFlash is promising. I was able to load the phone into MiFlash from the [EDL] thread. I have just tried the A2017G package provided by djkuz and will report back with any updates.
Just got to the mifavor screen, charging the battery from empty, although quickcharge appears to be functional again.
The charging battery logo is different from before so appears that this bootstack has done the trick.
The flashing red light has gone now, appears to be loading Lineage as before! I'm so grateful for all this help
However, now the unlock pattern is coming up as 'wrong pattern'. Is there anything that can be done? My settings appear to be saved as before (wallpaper and quick settings are the same).
I will attempt to reinstall twrp recovery and fix the lockscreen over adb. Thanks very much for the help. The brick has gone!!
Urgent help needed, is there anyone who knows how to start the phone when it gets bricked. I just downgraded it and when I updated it to official android N the phone just got bricked, it is giving no response to the keys, when I keep it on charging the led on the right of the FP sensor blinks. Is there anyway to on it?
Please help me!!!!!
osmrv said:
Urgent help needed, is there anyone who knows how to start the phone when it gets bricked. I just downgraded it and when I updated it to official android N the phone just got bricked, it is giving no response to the keys, when I keep it on charging the led on the right of the FP sensor blinks. Is there anyway to on it?
Please help me!!!!!
Click to expand...
Click to collapse
What stock ROM did you have prior to flashing RR, and what update did you attempt to apply?
2 things to try:
1)Try holding the power button down for 2-3 minutes, this can force a hard reboot which might get your device to run.
2)If that doesn't work, plug your device into your computer, does it register as 'Moto G4' or as 'Qualcomm HS-USB Bulk 9008' or similar?
If the 2nd, you may wish to look into using a blank-flash (https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23), however this blank-flash only appears to work if you were on the March 2017 stock firmware or lower, the June 2017 firmware will not accept the blank-flash.
Firstly I was on the june security patch update then I moved to RR, when flashed MM and updated then it got bricked.
I have tried all the methods to boot it into bootloader but all went in veins..
Ah, so you were on the June update previously? Unfortunately, the blank flash we've got doesn't work and sadly you're not the only one, we've got many reports now of devices updating to the June 2017 update and then bricking from downgrading, or somehow downgraded and then bricked when flashing an OTA.
Currently, the only resolutions appear to be sending your device for repair at a service centre (and you may have to pay for the repair), or save up funds for a new device
when will the blankflash file will be available, any idea?
I have a set of 3 different blankflash files available from different locations. I haven't tested these, so don't blame me if your device doesn't work as expected:
https://www.androidfilehost.com/?w=files&flid=175273
EDIT: I know a way of getting out of the bootloader but it requires me to unlock it (even though I left it unlocked after initially doing it). Unfortunately, though, I think I'm left with a £150 paperweight since I need an OS on the device to enable OEM unlocking and the device literally has no OS or recovery after the hard brick. Motorola have been very "supportive" about my situation even after sending them a 10 paragraph email explaining everything which obviously, they didn't read because I wrote on the first line that the device has been rooted so they knew beforehand. I wrote 10 paragraphs, they replied with six lines, so... Yeah.
I installed LineageOS 14 on my Moto G4 months ago with TWRP and I've never had any issues until today. Literally, just updated to a new nightly build for LineageOS and my phone screen went black and didn't turn back on. I plugged it into my computer and it showed up as QHSUSB_BULK. Obviously, at this point, my device was hard bricked but I found a way online of using Qualcomm's recovery thing they have to get my phone working again, which I did. But now, I've sorta ended up soft bricking the device now.
The device boots up into the bootloader (or what I think is the bootloader). What comes up is just white text at the bottom which basically just tells me information about my phone (product/variant, serial number, CPU, eMMC, DRAM etc.) The menu for the bootloader is just one string of text that only reads 'Start' and when I press the volume buttons, it will show up with more options but they're all highlighted in red and they all lead to the same error message, as follows:
Bootloader logs
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer
to repair your device.
Connect your device to your computer to get
the Software Repair Assistant.
I've looked around Google for the Software Repair Assistant and it appears to only be for Verizon Wireless and since I'm in the United Kingdom, Verizon Wireless doesn't even exist over here, nor do I even have them as my phone carrier. I'm with O2.
Also, I've tried a few things with Minimal ADB and Fastboot but every time I enter a command, it fails and say's 'FAILED (remote failure). My phone is detected in Fastboot, but not in ADB.
Hopefully, I can get this fixed.
Thanks,
Gabriel.
Guys, i am having the same issue too. I am getting the same issue. Since verizon is not available in india, unable to repair the phone since soft bricked. Kindly help.
did you try to enter fastboot>recovery and get the robot? if you can get that try holding the the power key and tap the up volume. that should give you a drop list with a factory reset option. click it and see what happens?
same problem here.
my phone is rescued.
llaalways said:
same problem here.
Click to expand...
Click to collapse
So, i flashed a stock android 7 rom on my moto g4 plus. It was working fine, until, i updated it for a new security update(the rom had security version of December,2017) and it restarted. The update started to install but after sometime minutes, it switched off. I tried charging it up, but only the LED at the bottom is blinking but i can't start it up. I tried going into bootloader mode but i can't go in the bootloader mode. Any possible way i can get this phone working? Even going into bootloader will be okay for me as i will then factory reset my device. Please help me. The service centre people are taking like $155 but the phone itself is slightly more than it.
Fantastic Lord said:
So, i flashed a stock android 7 rom on my moto g4 plus. It was working fine, until, i updated it for a new security update(the rom had security version of December,2017) and it restarted. The update started to install but after sometime minutes, it switched off. I tried charging it up, but only the LED at the bottom is blinking but i can't start it up. I tried going into bootloader mode but i can't go in the bootloader mode. Any possible way i can get this phone working? Even going into bootloader will be okay for me as i will then factory reset my device. Please help me. The service centre people are taking like $155 but the phone itself is slightly more than it.
Click to expand...
Click to collapse
It got hard bricked because you downgraded ROM and then tried to update..
Now try blank-flash,
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Download latest firmware from here :
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Try using the blankflash here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 for GPT or bootloader files, have a look here https://drive.google.com/folderview?id=0B-GUyOfb8OgzcUl1NUtHYWNIR2M
What device do you have and what firmware did you have? In future, please avoid using ota updates if you flashed an old stock firmware.
echo92 said:
Try using the blankflash here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 for GPT or bootloader files, have a look here https://drive.google.com/folderview?id=0B-GUyOfb8OgzcUl1NUtHYWNIR2M
What device do you have and what firmware did you have? In future, please avoid using ota updates if you flashed an old stock firmware.
Click to expand...
Click to collapse
i can't blank flash as the phone is not getting detected by the PC.
____Mdd said:
It got hard bricked because you downgraded ROM and then tried to update..
Now try blank-flash,
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Download latest firmware from here :
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
i can't blank flash as the phone is not getting detected by the PC.
Fantastic Lord said:
i can't blank flash as the phone is not getting detected by the PC.
Click to expand...
Click to collapse
Hmm, do you have the Motorola drivers installed https://support.motorola.com/us/en/drivers and do you have driver signature enforcement disabled if running Windows 10 or 8.1? https://www.google.co.uk/amp/s/www....so-that-you-can-install-unsigned-drivers/amp/
Are you also using the original USB cable or a high quality USB data cable?
echo92 said:
Hmm, do you have the Motorola drivers installed https://support.motorola.com/us/en/drivers and do you have driver signature enforcement disabled if running Windows 10 or 8.1? https://www.google.co.uk/amp/s/www....so-that-you-can-install-unsigned-drivers/amp/
Are you also using the original USB cable or a high quality USB data cable?
Click to expand...
Click to collapse
currently i am using an original data cable, also, i have the moto usb drivers installed.
Fantastic Lord said:
currently i am using an original data cable, also, i have the moto usb drivers installed.
Click to expand...
Click to collapse
From your description, you said: you have already flashed firmware, is it same PC ?
If it's same PC, and Cable then i see no problem with PC, drivers, and Cable.. all fine..
Just make sure charging your phone for couple of minutes,
In addition, have service center guys made any changes in device ?
____Mdd said:
From your description, you said: you have already flashed firmware, is it same PC ?
If it's same PC, and Cable then i see no problem with PC, drivers, and Cable.. all fine..
Just make sure charging your phone for couple of minutes,
In addition, have service center guys made any changes in device ?
Click to expand...
Click to collapse
i don't think the service center people did anything to it, but yeah they tested it and said that the phone was having 86% battery. Any ideas?btw thanks for replying
hi yesterday i was far from home with 5% battery and i take some calls some photos and battery 0%
when i got home i plugged in and battery is too laow message screen appear and after the message:
The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device to learn more:
g.co/ABH
can.t be power off when this message appear, i need to let battery drain and power key do nothing
and msmdownloand show nothing
Oneplus 6T on latest beta
Windows 10 i don.t know if has all drivers needed for a unbricked process
amkulcsar said:
hi yesterday i was far from home with 5% battery and i take some calls some photos and battery 0%
when i got home i plugged in and battery is too laow message screen appear and after the message:
The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device to learn more:
g.co/ABH
can.t be power off when this message appear, i need to let battery drain and power key do nothing
and msmdownloand show nothing
Oneplus 6T on latest beta
Windows 10 i don.t know if has all drivers needed for a unbricked process
Click to expand...
Click to collapse
I've had this before. If your phone has fully discharged and you plug in the charger the phone will boot up and stay on that message.
Just leave it to charge for five minutes, unplug the charger, then force reboot it by holding the power and volume down buttons together until it reboots. It should then boot normally and then you can plug in and continue charging.
ebproject said:
I've had this before. If your phone has fully discharged and you plug in the charger the phone will boot up and stay on that message.
Just leave it to charge for five minutes, unplug the charger, then force reboot it by holding the power and volume down buttons together until it reboots. It should then boot normally and then you can plug in and continue charging.
Click to expand...
Click to collapse
SOLVED
wait till screen get of install drivers correctly then press volume keys (+ and -) and connect to pc, in device manager appear at ports as qualcom... and open msmdownload tool and press start
amkulcsar said:
SOLVED
wait till screen get of install drivers correctly then press volume keys (+ and -) and connect to pc, in device manager appear at ports as qualcom... and open msmdownload tool and press start
Click to expand...
Click to collapse
Yeah you didn't need to do that. Just disconnect the charger and hard reboot and you would have been fine like I said, but oh well.
amkulcsar said:
SOLVED
wait till screen get of install drivers correctly then press volume keys (+ and -) and connect to pc, in device manager appear at ports as qualcom... and open msmdownload tool and press start
Click to expand...
Click to collapse
Did you manage to get rid off the corrupted screen message doing this?
That's a standard message if you've unlocked your bootloader. It doesn't signify corruption or an actual issue. You won't get rid of it without locking your bootloader.
Hello everyone, I unlocked my bootloader, but unfortunately I made an error when unlocking it but flashing it. so that he writes me when starting qualcom crashdump mode. and I don't know how to get out of it. also where I get the original onplus6 t software. and i work with linux via terminal. who can help me with this? on the one hand, where can I get the original os9 andriod software? and the second question is how I get the whole thing back on my cell phone and that it comes out of this warning from the grass dump
Hello. Please look on XDA for MSM tool for your device (enchilada or fajita depending on 6 or 6t). It will reinstall OOS back on your phone and relock the bootloader. There are a few videos on YouTube that will guide you through the process. It's a (short) but stressful process, but it does really work.
carrabelloy said:
Hello everyone, I unlocked my bootloader, but unfortunately I made an error when unlocking it but flashing it. so that he writes me when starting qualcom crashdump mode. and I don't know how to get out of it. also where I get the original onplus6 t software. and i work with linux via terminal. who can help me with this? on the one hand, where can I get the original os9 andriod software? and the second question is how I get the whole thing back on my cell phone and that it comes out of this warning from the grass dump
Click to expand...
Click to collapse
If your original plan was to get custom firmware don't bother with msm tool and getting stock, it's unnecessary. Twrp can be booted from fastboot if your bootloader is unlocked and you can do anything you need to do from there.
carrabelloy said:
Hello everyone, I unlocked my bootloader, but unfortunately I made an error when unlocking it but flashing it. so that he writes me when starting qualcom crashdump mode. and I don't know how to get out of it. also where I get the original onplus6 t software. and i work with linux via terminal. who can help me with this? on the one hand, where can I get the original os9 andriod software? and the second question is how I get the whole thing back on my cell phone and that it comes out of this warning from the grass dump
Click to expand...
Click to collapse
I'm in the same boat. Have you found any solution yet? I also use linux.
Brettroth said:
If your original plan was to get custom firmware don't bother with msm tool and getting stock, it's unnecessary. Twrp can be booted from fastboot if your bootloader is unlocked and you can do anything you need to do from there.
Click to expand...
Click to collapse
This was my plan and I soon realized I was not ready. I have unlocked the phone and the bootloader but I'm stuck, not able to get twrp to flash. Here's my error message:
[email protected]:/home/chad/Downloads# fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (32628 KB)...
OKAY [ 0.973s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 0.975s
[email protected]:/home/chad/Downloads#
ce_lloyd said:
This was my plan and I soon realized I was not ready. I have unlocked the phone and the bootloader but I'm stuck, not able to get twrp to flash. Here's my error message:
[email protected]:/home/chad/Downloads# fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (32628 KB)...
OKAY [ 0.973s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 0.975s
[email protected]:/home/chad/Downloads#
Click to expand...
Click to collapse
Should be fastboot boot (path and filename of twrp.img) once it boots then you can flash twrp from within.
I have done that as well. It appears to work, but then I get QUALCOM CrashDump Mode Attempted to kill init! wxitcode=0x0000000b complete..and..exit
This is a T-Mobile branded phone, does that matter or change anything?
ce_lloyd said:
I have done that as well. It appears to work, but then I get QUALCOM CrashDump Mode Attempted to kill init! wxitcode=0x0000000b complete..and..exit
This is a T-Mobile branded phone, does that matter or change anything?
Click to expand...
Click to collapse
If you are on a11 you have to use the twrp.img that is posted on the cross development thread that works for opt6 and 6t. TWRP-3.6.0_11-OP6xT.img