Database Users

[Q] Corrupt bootloader and black screen but live usb -- still hope?

Hi there
@bftb0 : yet another victim of the corrupt bootloader .img ! (see thread #2573015)
bftb0 said:
The versions distributed with JWR66Y and KOT49H* Google factory images are INVALID.
Click to expand...
Click to collapse
Device : Nexus 7 2012 wifi (grouper), stock 4.4.4 KTU84P, never rooted before
Symptoms : black screen, not booting at all even to bootloader. :crying:
Only faint light of hope is that my PC is still reacting to plugging the Nexus in with USB.
Windows beeps and shows an "unknown usb device" error then fails finding a driver.
Windows Device manager shows "APX" with yellow sign below "Other devices".
Question : bricked or any hope left ? Pleeease what can I do ?
How I got there :
NRT hung when flashing bootloader while reinstalling stock 4.4.0 (nakasi-krt16s-factory-da7dee49).
The story, going from bad to worse :
It started with a sudden reboot for not appearent reason (incidentally while an Avast routine scan was running).
Then endless reboot, with the 4 color balls shaking indefinitely (power plugged in or not).
Looked at forums... Reboot into bootloader. Recovery mode, wiped cache. Got plenty of error msg "E:failed to mount /cache"
Bootloop! Sometimes showing just the white Google logo, sometimes showing the rolling colors for a few seconds.
Recovery mode, erase user data (no backup, hate this thing). Again plenty of error msg "E:failed to mount /cache"
Could the missing /cache be related to Avast since the first reboot occurred while it was running? Maybe the theft protection is overly proctective?
Installed Nexus Root Toolkit 1.8.4 (extremely well done utility btw, ***huge congrats*** :good on Win 7 64bits. Installed drivers #1.
Tried flashing a clean 4.4.4 (nakasi-ktu84p-factory-76acdbe9).
FAILED (remote: Bootloader is locked.)
Successfully unlocked bootloader with NRT. Restart with an open lock below the white Google logo. So far so good.
Try flashing 4.4.4 again, same image.
writing 'bootloader'... FAILED (remote: (InvalidState))
What the heck ?!
Found the thread #2573015 I was quoting above on corrupt bootloader .img files from Google.
As it turns out, the bootloader MD5 is also WRONG in KTU84P.
Managed somehow to restart into bootloader again in spite of the bad bootloader...
Maybe the old one was not completely replaced yet?
Quick quick, let's try flashing another bootloader that works !
This time use the latest available with a non-corrupt bootloader .img : 4.4.0 (nakasi-krt16s-factory-da7dee49)
erasing 'boot'... blahblah
sending 'bootloader' (2100 KB)... OKAY [ 0.281s]
writing 'bootloader'... *** STUCK ***
Wait and wait until lost hope
Tried rebooting but nothing happens, just black screen, I end up with the symptoms I described upfront.
When plugged into the pc, keeping power button down makes windows beep, and the "APX" unknown device comes and goes in win device manager. Adding the vol+ or vol- buttons (or both) produces identical results.
Uninstalled APX device from PC. Power button down. Windows beeps "unknown usb device". "APX" shows up again in device manager... And so on.
Screen still pitch black.
Any other USB driver I can try to regain a working connection?
Worth looking into other remedies, like nkFlash?
GedBlake said:
If you corrupt, or erase the bootloader... the Nexus 7 is dead, from which there is known recovery. Although it's been speculated that an nvFlash tool could flash a new bootloader.
Click to expand...
Click to collapse
Thanks for reading me so far, I know it's long, but if you've read to this point maybe you can help?

What a similar story
this is such a coincidence as I have also had the dreaded bad to worse stage as my story started off here http://forum.xda-developers.com/showthread.php?t=2783631 and then got much worse and it continues here http://forum.xda-developers.com/showthread.php?t=2798181 .
I have been searching on the internet for the last month and so far there does not seem to be any general solution (which does not require hardware device surgery) to this particular type of problem as it is not something Google appear to have expected. I found that a lot of people seem to say its hypothetically possible to repair this thing via software means as that is how it was rendered inoperable in the first place and they also say it is not practically possible to hard brick any device through software means although with the nexus 7 there seems to be some kind of issue with crypto-signing which makes it a nightmare to access the hardware through nvflash unless there was some blob file made before hand
I am currently discussing the situation in this thread and you could join it to keep up to date
http://forum.xda-developers.com/showthread.php?t=2798181&page=2

Update Failed and Phone Cannot Start. Only Flash Blinks When Charging, NO START/Boot?

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.

Oneplus 6T hard bricked to g.co/abh loop

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

[Solved] Black screen after root attempt on XT1962-4

Yesterday I tried rooting my Moto G7 (build PPOS29.114-134-7). I managed to unlock the bootloader and install Magisk, however, I installed a wrong version for my build and got stuck in a bootloop. After being frustrated for a while by my foolishness, I managed to fix it and was able to boot it up again to OS. But instead of giving up, I decided to try once again, this time with the correct build.
I once again installed Magisk, createad the boot.img, moved it to my PC and turned the phone off, but now I cannot turn it back on. The screen is black, no matter for how long I hold the buttons, no matter the combination of them I hold, it simply doesn't respond anymore. I let it charging on a wall outlet, I let it charging on the PC, no response. It doesn't even show the battery connected or anything. The screen remais black and nothing happens.
The only sign of life it shows is when I connect it to the PC and hold the buttons - Windows plays the "hardware connected" sound, but it doesn't appear on my drive list or anything.
Is it an expensive paperweight now? Should I take it to the shop, or is there anything else I can do to try and fix this?
Thank you, and feel free to call me stupid. I feel like I deserve it.
EDIT: This issue has been resolved thanks to user EmixArian24 who messaged me with a link he found on the Telegram group regarding the G7. I attached a blankflash he sent me and by using it, I managed to boot to bootloader. I then downloaded the stock rom from Lolinet and flashed it to the phone. It then booted as normal.
Thank you very much to EmixArian24 for the magical link and everybody else who replied. I really appreciate it.
As for the G8 I bought, I chose to keep it. I will be selling my G7 as soon as possible.

AetherOmega said:
Yesterday I tried rooting my Moto G7 (build PPOS29.114-134-7). I managed to unlock the bootloader and install Magisk, however, I installed a wrong version for my build and got stuck in a bootloop. After being frustrated for a while by my foolishness, I managed to fix it and was able to boot it up again to OS. But instead of giving up, I decided to try once again, this time with the correct build.
I once again installed Magisk, createad the boot.img, moved it to my PC and turned the phone off, but now I cannot turn it back on. The screen is black, no matter for how long I hold the buttons, no matter the combination of them I hold, it simply doesn't respond anymore. I let it charging on a wall outlet, I let it charging on the PC, no response. It doesn't even show the battery connected or anything. The screen remais black and nothing happens.
The only sign of life it shows is when I connect it to the PC and hold the buttons - Windows plays the "hardware connected" sound, but it doesn't appear on my drive list or anything.
Is it an expensive paperweight now? Should I take it to the shop, or is there anything else I can do to try and fix this?
Thank you, and feel free to call me stupid. I feel like I deserve it.
Click to expand...
Click to collapse
Open device manager
How is it listed?
Likely need to use blankflash
Should be a link in my help thread
https://forum.xda-developers.com/showpost.php?p=78869857&postcount=2
Sent from my ali using XDA Labs

sd_shadow said:
Open device manager
How is it listed?
Likely need to use blankflash
Should be a link in my help thread
https://forum.xda-developers.com/showpost.php?p=78869857&postcount=2
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
It is listed as Qualcomm HS-USB QDLoader 9008. I'm trying to use the blankflash I found under one of the threads you linked in your master thread, but I'm stuck at "Waiting for firehose to get ready" now. I'm out of ideas...
EDIT: either the firehose warning or the "greeting device for command mode" followed by "FAILED (blank-flash:greet-device:error reading packet)"
EDIT2: yet another error I found:
Code:
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
OKAY [ 0.002s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x832808F5
...chip-id = 0xBA
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.006s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.005s]
validating files
OKAY [ 0.045s]
switching to download mode
OKAY [ 0.002s]
greeting device for image downloading
OKAY [ 0.001s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)

AetherOmega said:
It is listed as Qualcomm HS-USB QDLoader 9008. I'm trying to use the blankflash I found under one of the threads you linked in your master thread, but I'm stuck at "Waiting for firehose to get ready" now. I'm out of ideas...
EDIT: either the firehose warning or the "greeting device for command mode" followed by "FAILED (blank-flash:greet-device:error reading packet)"
EDIT2: yet another error I found:
Click to expand...
Click to collapse
You could try running it in several windows at same time.
Sent from my jerry_cheets using XDA Labs

sd_shadow said:
You could try running it in several windows at same time.
Sent from my jerry_cheets using XDA Labs
Click to expand...
Click to collapse
I did. I opened 15 to 25 of the batch files at once, only one of them seemed to "carry on" with the process only to result in a "Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)" error. I'm really out of ideas now.
Is there a possibility of a home-fix, or the chances of it are really low? I'm thinking it might an incorrect version of files or something, I'm having a hard time finding specifics for my model. I tried searching specifically for "XT1962-4 blankflash" and the sorts, but it really is not easy finding anything related to this specific model.
EDIT: Since I had so many files and batches to use, I decided to scrap everything and start over again. Much better. I went to Lolinet, downloaded the blankflash for my model by going to Firmware > Moto > River > Blankflash and fired up blankflash.bat.
But I have a question regarding that - the files inside this folder I downloaded are the only ones I need, or do I need to download the stock rom and put all the files of the ROM inside the blankflash folder as well before opening blankflash.bat? What I've been trying to do is just starting blankflash with the contents of the zip I downloaded from Lolinet, I haven't tried pasting any other files inside of it.
Also, with this blankflash, I managed to get this result:
Code:
D:\Downloads\blankflash_from_PPO29.114-4>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 186 (0xba)
[ 0.004] ...cpu.sn = 2200439029 (0x832808f5)
[ 0.004] Opening singleimage
[ 0.004] Loading package
[ 0.006] ...filename = singleimage.pkg.xml
[ 0.007] Loading programmer
[ 0.007] ...filename = programmer.mbn
[ 0.007] Sending programmer
[ 0.291] Handling things over to programmer
[ 0.293] Identifying CPU version
[ 0.299] Waiting for firehose to get ready
[ 60.863] Waiting for firehose to get ready
[120.958] ...MSM8953 unknown
[120.959] Determining target secure state
[120.964] Waiting for firehose to get ready
[181.059] ...secure = no
[181.080] Initializing storage
[181.082] Waiting for firehose to get ready
[241.158] Configuring device...
[241.159] Waiting for firehose to get ready
[301.235] Waiting for firehose to get ready
[361.308] Waiting for firehose to get ready
[421.378] Waiting for firehose to get ready
[481.448] Initializing storage
[481.450] Waiting for firehose to get ready
[541.524] Configuring device...
[541.525] Waiting for firehose to get ready
[601.603] Waiting for firehose to get ready
[661.687] Waiting for firehose to get ready
[721.773] Waiting for firehose to get ready
[781.852] Waiting for firehose to get ready
[841.943] Configuring device...
[841.944] Waiting for firehose to get ready
[902.031] Waiting for firehose to get ready
[962.124] Waiting for firehose to get ready
[1022.213] Waiting for firehose to get ready
[1082.309] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[1082.309] Check qboot_log.txt for more details
[1082.310] Total time: 1082.311s
[1082.310] There were some hiccups in backup and restore.
[1082.310] Please save the following files and see a Bootloader member.
[1082.310] 1) ./qboot_log.txt
[1082.310] 2) ./backup_0x832808F5_2020-03-23_215316.img
[1082.310]
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
D:\Downloads\blankflash_from_PPO29.114-4>pause
Pressione qualquer tecla para continuar. . .
Any ideas?

Just an update, I gave up and bought a new phone. I'll try sending the phone to a shop whenever this whole viral crisis ceases.

AetherOmega said:
Yesterday I tried rooting my Moto G7 (build PPOS29.114-134-7). I managed to unlock the bootloader and install Magisk, however, I installed a wrong version for my build and got stuck in a bootloop. After being frustrated for a while by my foolishness, I managed to fix it and was able to boot it up again to OS. But instead of giving up, I decided to try once again, this time with the correct build.
I once again installed Magisk, createad the boot.img, moved it to my PC and turned the phone off, but now I cannot turn it back on. The screen is black, no matter for how long I hold the buttons, no matter the combination of them I hold, it simply doesn't respond anymore. I let it charging on a wall outlet, I let it charging on the PC, no response. It doesn't even show the battery connected or anything. The screen remais black and nothing happens.
The only sign of life it shows is when I connect it to the PC and hold the buttons - Windows plays the "hardware connected" sound, but it doesn't appear on my drive list or anything.
Is it an expensive paperweight now? Should I take it to the shop, or is there anything else I can do to try and fix this?
Thank you, and feel free to call me stupid. I feel like I deserve it.
EDIT: This issue has been resolved thanks to user EmixArian24 who messaged me with a link he found on the Telegram group regarding the G7. I attached a blankflash he sent me and by using it, I managed to boot to bootloader. I then downloaded the stock rom from Lolinet and flashed it to the phone. It then booted as normal.
Thank you very much to EmixArian24 for the magical link and everybody else who replied. I really appreciate it.
As for the G8 I bought, I chose to keep it. I will be selling my G7 as soon as possible.
Click to expand...
Click to collapse
I have some zip folders I want to post concerning hardbrick moto g7. How do I do this? I get error. Image files only are accepted.
Please tell me how to post a jar file here? I have tried to attach one but my file manager only allows jpg and PNG files types.

How to recover from a dead bootloader of Oneplus 6T [Resolved]

I am trying to unlock the bootloader of the oneplus 6T I have. After got the unlock tocken(.bin) file from Oneplus support, I did the command:
./fastboot flash cust-unlock ../unlock_code.bin
Sending 'cust-unlock' (0 KB) OKAY [ 0.005s]
Writing 'cust-unlock' ^C
^C^C^C^C^C^C
So the fastboot program is hung when writing to the bootloader flash flash I guess. After powering down the phone, I can't power it up anymore -- the bootloader is dead (bricked).
I hope someone had this experience before can shed me some light or point me to some posts.
Updates:
I got this pointer: https://forum.xda-developers.com/t/...totally-sleep-dead-boot-mode-via-usb.1701471/ But it is for OMAP based.
Oneplus6T uses Qualcomm “Snapdragon” series of SoC
Got this thread: https://forum.xda-developers.com/t/tool-6t-msmdownloadtool-v4-0-59-oos-v9-0-13.3867448/ -- will update on this one
As a courtesy, I am hrer to update with a resolved status so that others can be aware of:
1) Google online for a more intuitive introduction and step by step guide on how to use MSM tool to update bootloader(s). There are multiple stages of bootloading and each has one bootloader.
2) It is not hard to get the MSM tool to see the device connected. But it is common that the tool can't update the device bootloaders/images, with the error "Sahah protocol ... " type of message. THe reason I guess is the following.
3) It is very hard to be sure if your device is in EDL mode just right for the MSM tool to talk to. I don't know what stage the device has to be in for the MSM to work correctly. It is very hard to even know what stage the device is in. SO VERY SADLY, it is a try and error and retry game. Many suggested things to try but I found the most useful one is the volume up and down button pressed together and then with power button, ALL THREE pressed for some seconds after the device is powered down. But you don't even know how long it takes to power down the device .... etc. So try the all three button procedure as many as you, with luck you will be able to see that the MSM tool will start to update.
4) I am brandnew noob in the android world. There are so much to learn about this giant world of android-ing. There are so many terms (technical/no-tech), versions of kernel/OS/Apps/Framework/devices/vendors/ROMs/etc. Instructions online are very helpful, but some of them are obsolete (be careful). Some of them are not detailed enough and some of them are just an experience of one try and some of them ..... it is not as straight forward as you imagined (as always in the software/hardware world).
5) I still am not sure what caused the failure of my first try to unlock the 6T. I guess it is due to the fact that I did it on Linux and it hasn't got an update driver. Eventually I did the unlock on Windows 10.
Some other useful links:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
[OP6T][LATEST 10.3.8] Collection of unbrick tools
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com