Database Users

[Q] [HELP] Hard Brick Nexus 7

Hi, this is my firt post, i'm going to quote this problem that's the same problem that I have...
"Device : Nexus 7
Problem : I was trying to unroot it and flash a 4.4.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean"
I did exactly the same thing that this guy did... ----> http://forum.xda-developers.com/showthread.php?t=2345874
The difference is that I don't live in USA and my Nexus doesn't have warranty... What can I do T.T my pc shows the tablet as Unknown Device and makes a sound when I puggle it, there has to be something that I can do >.<

EverAngelOn said:
Hi, this is my firt post, i'm going to quote this problem that's the same problem that I have...
"Device : Nexus 7
Problem : I was trying to unroot it and flash a 4.4.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean"
I did exactly the same thing that this guy did... ----> http://forum.xda-developers.com/showthread.php?t=2345874
The difference is that I don't live in USA and my Nexus doesn't have warranty... What can I do T.T my pc shows the tablet as Unknown Device and makes a sound when I puggle it, there has to be something that I can do >.<
Click to expand...
Click to collapse
Can you get into the bootloader still?

I can't
b3ltazar said:
Can you get into the bootloader still?
Click to expand...
Click to collapse
No, I can't. The screen is completely black.

Have you tried any of the suggestions in the thread you linked in the OP?

EverAngelOn said:
No, I can't. The screen is completely black.
Click to expand...
Click to collapse
Do you get a charging icon when you plug in the n7? did you try a diffrent cable?What exactly does ur computer do when you plug in the dead n7 (does it thy try to install a apx driver) Does toolkit see tablet like its in the bootloader? If so try to flash a new bootloader!
try this found in another thread
To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures

Wugs tool kit
First when you plug it in hold all three power buttons
Second
I also have used the tool kit it gets stuck all the time on the flashing system. I think its a time out error because of the complexity of extracting the image and flahing the image with out a retry or check command. Here is a fix that i have figured out. When in Wugs tool kit download the Os Version you want on your device locate the folder with the downloaded image and extract it using 7 zip. once extracted flash the remaing .img files seperatly under andvance setting menu select flash system then user data it should boot right up. if you forgot what version you flashed previously flash all img files boot bootloader system user etc. if you still have problems let me know. i can give you my email.
Click thanks if i helped

b3ltazar said:
Do you get a charging icon when you plug in the n7? did you try a diffrent cable?What exactly does ur computer do when you plug in the dead n7 (does it thy try to install a apx driver) Does toolkit see tablet like its in the bootloader? If so try to flash a new bootloader!
try this found in another thread
To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures
Click to expand...
Click to collapse
My tablet doesn't show the charging icon, I've tried with different cables, when I plug it to the laptop it makes a sound and shows an APX driver... I'm stressed and that instructions didn't work for me.

EverAngelOn said:
My tablet doesn't show the charging icon, I've tried with different cables, when I plug it to the laptop it makes a sound and shows an APX driver... I'm stressed and that instructions didn't work for me.
Click to expand...
Click to collapse
Unfortunately it sounds like you erased your bootloader and nvflash can do nothing for you unless you used the unbrickable mod before u f'ed up your tablet. Try sending it to asus for Warranty tell em you installed the ota update and it wouldn't boot up afterwards. I have read many threads about this issue with nobody being able to recover there tablet. Asus does have global warranty

[HOWTO] Unbrick Hardbricked (stuck onUSB Logo) MeMo Pad ME170CX (and others)

This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool

Hey @korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated

Premie said:
Hey korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated
Click to expand...
Click to collapse
I literally faught that error for a whole day. I tried 5 different computers, all had that issue. Usually my tablet would connect and disconnect once before the logo came up. Within that brief window, I was able to start the flash and it worked. I'm pretty sure that's what did it. If you aren't seeing this, turn up your PC's volume and listen for the USB sounds.
This whole thing is pretty annoying, but when it works, it works.

Thanks
I shall keep going at it until it works or I find another solution.

PLEASE help me!
korockinout13 said:
This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool
Click to expand...
Click to collapse
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?

Nandr0idC0nsumer said:
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?
Click to expand...
Click to collapse
If you have a working boot loader, you don't need to do this.

korockinout13 said:
If you have a working boot loader, you don't need to do this.
Click to expand...
Click to collapse
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore

Nandr0idC0nsumer said:
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore
Click to expand...
Click to collapse
What happens instead of fastboot mode?

korockinout13 said:
What happens instead of fastboot mode?
Click to expand...
Click to collapse
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."

Nandr0idC0nsumer said:
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."
Click to expand...
Click to collapse
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.

korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well

Nandr0idC0nsumer said:
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well
Click to expand...
Click to collapse
You have adb? That's not possible unless you are getting past the boot loader.

korockinout13 said:
You have adb? That's not possible unless you are getting past the boot loader.
Click to expand...
Click to collapse
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload

Nandr0idC0nsumer said:
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload
Click to expand...
Click to collapse
Hm... seems like you should be able to work with that if you have something flashable.

korockinout13 said:
Hm... seems like you should be able to work with that if you have something flashable.
Click to expand...
Click to collapse
Returned the tablet at Best Buy to get "fixed" (come on bestbuy, I know you mean replaced.) Thanks for your help

Repair
Hi,
I think i can help you out because i worked with the intel tool for weeks now to find a solution to root the me581cl.
Go to my thread and download a newer version of intelPhone tool.
http://forum.xda-developers.com/general/help/root-downgrade-asus-me581cl-t3075678
If you crashed your tab totaly, you must put the 4 OS IFWI,dnx files like in the first post and then also boot.img, fastboot.img, recovery.img.
Uncheck only the ifwi folder, but select it before. So its possible to check blank phone and on demand flash.
Then click start flash and the files get loadet up. Now push vol+ and vol- togehter and plug in the device.
(device must be off before you plug it in. If not, press 10 sec the power button.)
The reest you can read in my thread. A downgrade from Android 5 to 4.4 is also possible.
Good luck

Guys, my ME176CX is shafted after completing the L update, it boots to the android with the red exclamation box...i can get past this by using the volume + & power and arrive in the recovery. from there I have tried the wipe cache/wipe userdata (doesn't help) also i tried to adb sideload one of the roms in the collection of roms thread. no good. ideas??

Any solution?
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
Man I'm living in Venezuela a bad country to get damaged any gadget everything is 5 times expensive who your country and without any help in our soil by ASUS.

is this solution applicable to non-intel memopad? (e.g. me172V)

playinghier said:
is this solution applicable to non-intel memopad? (e.g. me172V)
Click to expand...
Click to collapse
No, this is very specific to the Intel chipset.

[FIX][Noob Friendly] No recovery, No download mode, No booting android, qhsusb_bulk?

No recovery, No download mode, No booting android, No fastboot? - In this case you are right here!
You are in the following situation:
If you power on your device, it goes to the LG logo and becomes black with running backlight quickly.
You have no access to the recovery mode.
You can't enter download mode.
There is no way to boot into the android system.
Usually your device is shown as qhsusb_bulk in Windows device manager.
Sometimes Windows recognizes about 13 partitions.
What you will need:
A working linux distribution (no way around that, but don't be afraid, e.g. slax)
If you want to run Linux in a Virtual Machine (no installation), preferably the VMWare Player (only for 64bit OSes) or an older Version of VMWare Player that supports 32bit.
A windows machine
A kdz for your device: 1, 2 or 3
The kdz extractor for WINDOWS!
Your broken G2
A micro USB cable
A little introduction:
We saw it a few times in the past months that people did weird things with their phone and didn't have anything more than a bootloader. This means no access to recovery nor download mode nor a booting android system. The last case was @petrasl27 (Thanks for the screenshots btw. ;D ). @bender_007 and @Art Vanderlay did an awesome job and helped petrasl27 to recover his phone within one hour. So thanks to those two! For those who want to read the original discussion, read a few pages here!
This thread here is similar to this one here, but I would say quite a bit easier to understand.
Disclaimer: I am not responsible for your phone. I did everything with my best knowledge, but I can't guarantee that your phone is working afterwards and every single command is written correctly. But I hope so, and it should ofc. If you have any issues, feel free to ask for help. We are kind, no worries. If you find mistakes, hit me up and I will correct them ASAP.
Let's start!
1) Install Linux
The easiest way is just do download the VMWare Player, installing, running it and using the .iso you downloaded before (pick other 3.x Linux Kernel if you downloaded slax). If you are unsure how to get Linux running, google it or ask here. Make sure, the usb port which you are going to use is linked through to the virtual machine.
You can also make the iso bootable and run the Linux as live system.
2) Extract the kdz
Switch to Windows, open the kdz extractor. Tick everything in the upper window, and click on extract kdz. Then open the .dz which just was created in the working directory of the kdz extractor. Tick "aboot_xxxxxx.bin", "boot_xxxxxx.bin" and "laf_xxxxxx.bin" in the lower window and hit extract dz. Then move the .bin files to your Linux desktop by using an USB stick, online storage or something like this.
Rename the files to "aboot.img", "boot.img" and "laf.img".
3) Preparing everything
Remove all your USB devices (except your G2 and your Keyboard & Mouse) from your computer, open a Terminal and type
Code:
ls /dev/sd*
The sda, sda1, sda2 etc. should be the partitions on your computer. But there should be a few others with sdb, sdb1, sdb2, etc. but no more. The sdb ones should be numbered from 1 to 36. This is your G2. Keep in mind how the three letters are (sdb, sdx, what so ever). (Make sure you run this as Super User, if you don't use slax!)
Then type
Code:
gdisk -l /dev/<insert the three letters you found out with the command above>
example:
Code:
gdisk -l /dev/sdb
It should now look something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Keep the numbers of the marked partitions in mind. In this case aboot=5, boot=7, laf=23.
4) Preparing everything
If you've managed it to get here, you are almost done. It's almost time for the final step now:
Open a terminal and type
Code:
cd Desktop
ls
You should now see the filenames of the 3 files (aboot.img, boot.img, laf.img) on your desktop in the terminal. If you do not, you either didn't type "cd Desktop" properly (The linux terminal is case sensitive!!!) or you haven't copied the files to the desktop.
5) Flashing the stuff
Code:
dd if=aboot.img of=/dev/<the 3 letters of your G2><the number of your aboot partition>
dd if=boot.img of=/dev/<the 3 letters of your G2><the number of your boot partition>
dd if=laf.img of=/dev/<the 3 letters of your G2><the number of your laf partition>
example (in my case):
Code:
dd if=aboot.img of=/dev/sdb5
dd if=boot.img of=/dev/sdb7
dd if=laf.img of=/dev/sdb23
6) Go back to stock using the kdz method
Now just follow this thread to get back to stock.

Reserved - just in case^^

bricked my lg g2 d802..plz help
i'm from india .
i had installed lollipop 5.0.2 v30b via kdz flash method on my lg g2 d802 (indian version ) .
since then i had issues wirth my bluetooth and wifi.both were not working .
in my attempts to flash back to stock 4.2.2 , i came across ur thread and i flashed "D802_PATCH_RETURN_KK_droidth" via philz latest cwm recovery ,
but after that everything went mayhem ..
i got boot error message repeatedly and was unable to enter even recovery .
after several tries i somehow managed to enter recovery mode , but stil phone wont go past it.
I GUESS I ACCIDENTALLY FLASHED A KERNEL FOR MY OLD GALAXY NOTE(due to confusion between the saved files in the download folder ) , On my g2 too....but not sure...
after i restatred the moB , it wont turn on .
battery was 85 % ..
i'm not a newbie to flashing roms and have done aTLEAST >50 times with my lg g2 and galaxy note 2 and previously sgs2 , but this is the first time i got into a hard brick mode.
when i took the phone to servie center, they told the mob is just out of warranty and so wont get any warrany related help.
they told that the EFS HAS BEEN CONVERTED TO READ ONLY mode somehow due to improper flahing and also added that the EFS IS BEING SHOWN AS 16 PARTITION S.
they tried to repair the boot sector and recovery using OCTOPLUS TOOL BOX , but failed and told me that the latest models like G2 is not supported as if now in their TOOL BOX.
THE ONE suggestion given by them was change of PCB which is almost same as a new mob.
I'M STUCK WITHOUT MY FAV MOB G2 .......PLS HELP ME OUT SOMEHOW AND HELP ME OUT...

hbk4 said:
i'm from india .
i had installed lollipop 5.0.2 v30b via kdz flash method on my lg g2 d802 (indian version ) .
since then i had issues wirth my bluetooth and wifi.both were not working .
in my attempts to flash back to stock 4.2.2 , i came across ur thread and i flashed "D802_PATCH_RETURN_KK_droidth" via philz latest cwm recovery ,
but after that everything went mayhem ..
i got boot error message repeatedly and was unable to enter even recovery .
after several tries i somehow managed to enter recovery mode , but stil phone wont go past it.
I GUESS I ACCIDENTALLY FLASHED A KERNEL FOR MY OLD GALAXY NOTE(due to confusion between the saved files in the download folder ) , On my g2 too....but not sure...
after i restatred the moB , it wont turn on .
battery was 85 % ..
i'm not a newbie to flashing roms and have done aTLEAST >50 times with my lg g2 and galaxy note 2 and previously sgs2 , but this is the first time i got into a hard brick mode.
when i took the phone to servie center, they told the mob is just out of warranty and so wont get any warrany related help.
they told that the EFS HAS BEEN CONVERTED TO READ ONLY mode somehow due to improper flahing and also added that the EFS IS BEING SHOWN AS 16 PARTITION S.
they tried to repair the boot sector and recovery using OCTOPLUS TOOL BOX , but failed and told me that the latest models like G2 is not supported as if now in their TOOL BOX.
THE ONE suggestion given by them was change of PCB which is almost same as a new mob.
I'M STUCK WITHOUT MY FAV MOB G2 .......PLS HELP ME OUT SOMEHOW AND HELP ME OUT...
Click to expand...
Click to collapse
Did you follow the guide? Just do this. If things are unclear, just ask and someone will help you.

I want to download the first linux programme but it is just for windows 64bits. I'm running windows 7 OS 32Bits..

Soufiansky said:
I want to download the first linux programme but it is just for windows 64bits. I'm running windows 7 OS 32Bits..
Click to expand...
Click to collapse
Which one are you refering to?
NVM, adjusted the OP. Either use VirtualBox or download an older version of VMPlayer (which supports 32bit obviously) by picking Version 6.0 as major version.

Sunandroid said:
Which one are you refering to?
Click to expand...
Click to collapse
VMWAREplayer

Soufiansky said:
VMWAREplayer
Click to expand...
Click to collapse
read my post above (edited it).

Sunandroid said:
read my post above (edited it).
Click to expand...
Click to collapse
I can see that it will install Linux OS on my computer , which mean i will have 2OS . Is this safe ? I mean on every boot i should choose the OS to use or what ? Because i never used Linux as i don't need it , but this time it's a must.
Thanks.

Soufiansky said:
I can see that it will install Linux OS on my computer , which mean i will have 2OS . Is this safe ? I mean on every boot i should choose the OS to use or what ? Because i never used Linux as i don't need it , but this time it's a must.
Thanks.
Click to expand...
Click to collapse
No, if you are running it as a virtual machine (in VMWare Player or VirtualBox or whatever), it's like a programm you can start on your windows system. After you've unbricked your device, you can easily uninstall the VMWare Player and there is nothing from Linux anymore.

Sunandroid said:
No, if you are running it as a virtual machine (in VMWare Player or VirtualBox or whatever), it's like a programm you can start on your windows system. After you've unbricked your device, you can easily uninstall the VMWare Player and there is nothing from Linux anymore.
Click to expand...
Click to collapse
I get it , like a virtual OS in the main OS. Installing , will report back.
---------- Post added at 09:40 PM ---------- Previous post was at 09:18 PM ----------
@sunandroid My phone is booting at LG logo and download mode is working , so i see this method isn't for me BUT .kdz method doesn't work , firmware stuck at 24% or 49% , and one LP firmware worked but it just keep rebooting after the process.
Factory reset doesn't work , the blue line down isn't there and it reboot again and again.. Is there a way to boot in fastboot using buttons combinations ? Tried multiple things but didn't work.

Soufiansky said:
I get it , like a virtual OS in the main OS. Installing , will report back.
---------- Post added at 09:40 PM ---------- Previous post was at 09:18 PM ----------
@sunandroid My phone is booting at LG logo and download mode is working , so i see this method isn't for me BUT .kdz method doesn't work , firmware stuck at 24% or 49% , and one LP firmware worked but it just keep rebooting after the process.
Factory reset doesn't work , the blue line down isn't there and it reboot again and again.. Is there a way to boot in fastboot using buttons combinations ? Tried multiple things but didn't work.
Click to expand...
Click to collapse
What button combo do you use to factory reset?

Sunandroid said:
What button combo do you use to factory reset?
Click to expand...
Click to collapse
Volume down + power button , just after LG logo i press them again , then yes , yes , it shows the green android but there is no factory reset ( the blue line isn't there if you know what i'm talking about)
Tried also the same thing then power 3 times , same also..

problem soleved.....finally
Sunandroid said:
Did you follow the guide? Just do this. If things are unclear, just ask and someone will help you.
Click to expand...
Click to collapse
finally , i solved the problem..
with the help of soombons (droidth) , i was able to fix my d802 in just 2 minutes. - USING SRK 2.0 TOOL ...
sharing the link for people with same problems
---
[LG-G2] Unbrick (qhsusb_bulk) by SRK Tool 2.0 (D8…: https://youtu.be/ERZvlJIC9dE
tonnes of thanks to SOOMBONS for the prompt help !..
CHEERS !!!

Can anyone help me out on a D801?
The phone goes into bootloop... the LG logo appears for a few seconds, disappears, then reappears. I'm not able to go into download mode, no fastboot, and also no recovery. When I do the volume down + power button combo I can get to the factory reset screen but selecting Yes both times just sends me back to the same LG logo bootloop.
What is weird is that my phone use to display as QHSUSB_BULK and it would bring up a bunch of drives... but now that doesn't happen and my phone isnt even showing in device manager anymore. Also, my phone used to show the first "Download Mode" splash screen when I held the volume up button while plugging it into my comp but it just does the same bootloop. No more errors... just bootloops...
Do I have to short the capacitors like in this thread: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
or this one: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404

Soufiansky said:
Volume down + power button , just after LG logo i press them again , then yes , yes , it shows the green android but there is no factory reset ( the blue line isn't there if you know what i'm talking about)
Tried also the same thing then power 3 times , same also..
Click to expand...
Click to collapse
Weird. Did you use this method to go back to stock: http://forum.xda-developers.com/showthread.php?t=2432476
This worked fine for me every time I used it. Try to flash a KK ROM again, but do a CSE flash.
chaitea said:
Can anyone help me out on a D801?
The phone goes into bootloop... the LG logo appears for a few seconds, disappears, then reappears. I'm not able to go into download mode, no fastboot, and also no recovery. When I do the volume down + power button combo I can get to the factory reset screen but selecting Yes both times just sends me back to the same LG logo bootloop.
What is weird is that my phone use to display as QHSUSB_BULK and it would bring up a bunch of drives... but now that doesn't happen and my phone isnt even showing in device manager anymore. Also, my phone used to show the first "Download Mode" splash screen when I held the volume up button while plugging it into my comp but it just does the same bootloop. No more errors... just bootloops...
Do I have to short the capacitors like in this thread: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
or this one: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
Yeah I guess you have to do as you mentioned. Only thing you could try before doing so:
Hold down the power button for 20 secs. Then wait a few secs and try to get into download mode. Maybe the device shows up as qhusb_bulk again.

Please help, Im stuck!!!
Since yesterday my phone is stuck, only LG Logo, no download mode, no factory mode, no recovery, no nothing but the lg logo.
I tried thw mentioned tool and what the OP posted here, but in both methods I get stuck:
The LG G2 is not recognized as as drive anymore, the one thats supposed to have many partitions, sdb, sdx, what so ever, numbered from 1 to 36.
Without this I cant continue.
Any help? Using D802 international version
Thanks

Batou069 said:
Please help, Im stuck!!!
Since yesterday my phone is stuck, only LG Logo, no download mode, no factory mode, no recovery, no nothing but the lg logo.
I tried thw mentioned tool and what the OP posted here, but in both methods I get stuck:
The LG G2 is not recognized as as drive anymore, the one thats supposed to have many partitions, sdb, sdx, what so ever, numbered from 1 to 36.
Without this I cant continue.
Any help? Using D802 international version
Thanks
Click to expand...
Click to collapse
Do you have a windows machine?
If yes, try this http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2 and see if it is displayed as qhusb_bulk in device manager after you've done this.

Sunandroid said:
Do you have a windows machine?
If yes, try this http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2 and see if it is displayed as qhusb_bulk in device manager after you've done this.
Click to expand...
Click to collapse
Hi, thanks for the quick reply
I have a windows machine, yes, but no idea how to open my device. I hope this wont be necessary...
What happened last: After using a very laggy rom for over a week, I decided to flash PA. I wiped everything except the format, so data/media is kept... i guess that the flash didnt went well, and after reboot im stuck at LG logo... manually putting it into recovery isnt working anymore.
When I connect the phone to the pc only the "LGE Android MTP Device" is identified but with a fail (yellow triangle and exclemation mark in device manager).
SRK Tool -> Disk Managment Tool shows only Disk0 which is c:
In the virtual machine, under VM> removable devices I can see the LGE Android, and when I connect it (disconnect from host) nothing changes, no sdx, sdb or anything like this, only sda (C
I installed the LG Drivers but it wont help. Here I am, with a bricked phone
What do you think?
Thanks

Batou069 said:
Hi, thanks for the quick reply
I have a windows machine, yes, but no idea how to open my device. I hope this wont be necessary...
What happened last: After using a very laggy rom for over a week, I decided to flash PA. I wiped everything except the format, so data/media is kept... i guess that the flash didnt went well, and after reboot im stuck at LG logo... manually putting it into recovery isnt working anymore.
When I connect the phone to the pc only the "LGE Android MTP Device" is identified but with a fail (yellow triangle and exclemation mark in device manager).
SRK Tool -> Disk Managment Tool shows only Disk0 which is c:
In the virtual machine, under VM> removable devices I can see the LGE Android, and when I connect it (disconnect from host) nothing changes, no sdx, sdb or anything like this, only sda (C
I installed the LG Drivers but it wont help. Here I am, with a bricked phone
What do you think?
Thanks
Click to expand...
Click to collapse
Are you sure you can't get into download mode? (hold down the power button for 20 seconds (not shorter!), then holding the vol+ button and connect the phone to a computer)?
I could imagine that you can enter the recovery after holding down the powerbutton for 20 seconds with the button combo. I think so, because the kernel must be working somehow since it still manages to get shown properly on windows.
If none of the options above is working, the pin shortage is probably the easiest way to get into qhsusb_bulk and start freshly (following this thread).

[GUIDE] Repair your Idol 3

Hi Everyone
This is Guide how to repair your phone who was dead
My phone doesn't worked for 3 days so i get small trick and successfully repaired from dead
My phone was 5 times not worked like dead,Screen not Works ...only LED works,when i connect to pc usb device not recognized and nothing....
Explanation about my Problem:
IN MY CASE!
and the worst In my case Power button and Volume Buttons doesn't working so i open the BACK COVER eject the cable from volume button and insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
So we are starting the GUIDE:
1.First you need the drivers so you can get from this https://drive.google.com/folderview?id=0B1T7tp6tJ_3kX3p6SUxWb2NfWTQ&usp=sharing
2.After you installed the Drivers go to. Download mode if not goes try this... Press Volume UP and Volume DOWN and connect to usb to your pc
3.Go to device Manager to view the Port ,so the port can be "Android HS-USB QDLoader 9008 (COM3)"
4.Download the Panasonic Firmware Eluga and Extract (don't worry this is the same like idol 3 only name changed)https://docs.google.com/uc?id=0B01OmzpKE6vAVDhaSFN2aVFzaVU
5. After Extract you wil find EB-90S55EWLv1009.exe so run as administrator wait to load data
6.select 6045 and in the list down you can find your phone
7.and press the button "download"
8.So process starting ..indetifying your device you will get informations about imei..rooted or no .....
9.so automatically started to flashing the firmware (my it's go to 45 % and then i get error)
10.Don't worry press the button Reboot Device
11.and your device will reboot and you will view 'the screen powered by android and then panasonic so i get message Encrypted device just click the button "reset" and automatically device will be reseted and when wil finish with reset automatically reboots and wait to first boot you will get welcome screen set up and finished.....
12.So device successfully repaired from dead
If you want to go to CM or Stock for Idol 3
-i will write guide to unlock bootloader and flash TWRP recovery
-You must have Minimal Adb and Fastboot
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing " .powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-You successfully unlocked the bootloader one step more to flash the recovery
-Download the TWRP RECOVERY FROM THIS LINK:
https://www.androidfilehost.com/?fid=24421527759881858
-Then copy from when you downlaod and paste the recovery in C:\Program Files\Minimal ADB and Fastboot
-Press Shift in the directory and click Right on mouse and open command promt here
-Type fastboot -i 0x1bbb flash recovery twrp-3.0.0-1.img or fastboot -i 0x1bbb boot twrp-3.0.0-1.img (if you want to test before installation)
-so successfully installed recovery and flash CM Or whatever you want
[/SIZE][/COLOR][/B]
Sorry for Grammatical Errors!
This guide will repair from dead.... ​

in my case , buttons also doesn't work , how did you opened the back cover?

xZrender said:
in my case , buttons also doesn't work , how did you opened the back cover?
Click to expand...
Click to collapse
here's video how you can open
https://www.youtube.com/watch?v=FrFE8FdTXrY

Alek Dev said:
Hi Everyone
IN MY CASE!
and the worst In my case Power button and Volume Buttons doesn't working so i open the BACK COVER eject the cable from volume button and insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb​
Click to expand...
Click to collapse
i opened back cover , but how did you press the volume button , it doesnt work for me , i ont know what to do ;/

xZrender said:
i opened back cover , but how did you press the volume button , it doesnt work for me , i ont know what to do ;/
Click to expand...
Click to collapse
Eject cable from motherboatd....insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb

problem with idol 3 4.7 6039K
Hi there,
I don't know if this is the correct section, I hope so, otherwise I really appreciate you can drive me to the appropriate one, it's new for me this forum!
I have an idol 3 4.7, where I have installed kingroot and after I took out (I didn´t reset the phone, Just unistall the app),
yesterday i received the update system message, I imagine for the marshmallow update, so I say Yes, install it.
But the phone entered in bootloop. I only have the initial screen with the options as Reboot system, adb and so on.
I tried to wipe but nothing. So now my phone stucked. I tried with an assistance center in Quito but they could't
My questions are:
may I use this system for 6039K?
Or does anybody hear about a solution in this case?
Should I open and take out the battery?
Please, any suggestion will be really welcome in order to make the phone work again.
P.

nipozzano said:
Hi there,
I don't know if this is the correct section, I hope so, otherwise I really appreciate you can drive me to the appropriate one, it's new for me this forum!
I have an idol 3 4.7, where I have installed kingroot and after I took out (I didn´t reset the phone, Just unistall the app),
yesterday i received the update system message, I imagine for the marshmallow update, so I say Yes, install it.
But the phone entered in bootloop. I only have the initial screen with the options as Reboot system, adb and so on.
I tried to wipe but nothing. So now my phone stucked. I tried with an assistance center in Quito but they could't
My questions are:
may I use this system for 6039K?
Or does anybody hear about a solution in this case?
Should I open and take out the battery?
Please, any suggestion will be really welcome in order to make the phone work again.
P.
Click to expand...
Click to collapse
Hello
This Guide only works with Idol 3 5.5
but i will explain how to restore your device
Can you try with Mobile upgrade Q to restore,if doesn't work
Use this guide from wiemar ,it should help to you because it's for your model
http://forum.xda-developers.com/showpost.php?p=63709274&postcount=113
If you any questions ask me

Hi ! I follow the guide up to the section 9, unfortunately, in the Panasonic Firmware Eluga and Extract after pressing download it stops after 2% and I have got the error message "load nprg error error code 5002". Does someone know how to fix that ?
Thanks !

Error
I get: "Master Clear: FAIL Flash Status: [COM3->PC[3]] COM3->PC[3] failed to erase misc (Error code = 40016) " :crying:
Now I get the same error that matcail... did you solved it ???

Good tutorial but it does not help me. My phone keeps on rebooting.

Schumi_wk said:
Good tutorial but it does not help me. My phone keeps on rebooting.
Click to expand...
Click to collapse
Tell me info About your phone? Model,Country,ROM...../?

All is standard, no root, no twrp and the latest software from alcatel, the model is 6045Y. But all of a sudden my phone decided to random reboot and it didn't stop
So i looked to unbrick it and came with a couple of options, first i tried to sideload software but that didn't work, than i tried it with Mobile upgrade from alcatel and that didn't work.
Than i saw this thread and tried it twice but after Panasonic and the sound it starts to reboot again. Now i'm trying again with Mobile upgrade.
All that is changed is the recovery interface it looks now like it is from MM.

Schumi_wk said:
All is standard, no root, no twrp and the latest software from alcatel, the model is 6045Y. But all of a sudden my phone decided to random reboot and it didn't stop
So i looked to unbrick it and came with a couple of options, first i tried to sideload software but that didn't work, than i tried it with Mobile upgrade from alcatel and that didn't work.
Than i saw this thread and tried it twice but after Panasonic and the sound it starts to reboot again. Now i'm trying again with Mobile upgrade.
All that is changed is the recovery interface it looks now like it is from MM.
Click to expand...
Click to collapse
More Looks like Hardware Problem Try again with Mobile q if not works...Send to warranty repair.....

Alek, thank you for this great guide. It saved my 6045k model.
I was messing around with AlekOS 3.0, had issues with lock screen and experimented with modems. I managed to permanently disable secondary sim slot (was using famewolf's modem backups). I forgot to copy modem.img backup to my PC! Also tried bunch of TWRP backups with no luck. My last hope was Mobile Upgrade Q and reverting back tu 5.0.2. Unfortunately with no success (only one sim slot is recognized again).
Finally I found this thread, followed the guide and I can confirm that it did solve sim issue. The setup finished with no errors that you mentioned. It got stuck at 45%, but after a while (10min) it completed successfully.
Cheers!

I'm in the same situation as you,but my problem is that Panasonic Eluga doesn't recognice my devide,drivers are correctly installed,I checked everything but nothing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I´ve tried everything to downgrade my device (Mobile Q doesn't work) but nothing :crying:

peito said:
I'm in the same situation as you,but my problem is that Panasonic Eluga doesn't recognice my devide,drivers are correctly installed,I checked everything but nothing:
I´ve tried everything to downgrade my device (Mobile Q doesn't work) but nothing :crying:
Click to expand...
Click to collapse
You must do something Wrong...Press Pwr button and Volume up and down and thern connect to PC and then you will get RED SCREEN....Press Volume Up until you get Black screen and then press Download and if you get again same Send me Pm with Teamviewer ID AND PASS and i will try to help you

eXoSaX said:
Alek, thank you for this great guide. It saved my 6045k model.
I was messing around with AlekOS 3.0, had issues with lock screen and experimented with modems. I managed to permanently disable secondary sim slot (was using famewolf's modem backups). I forgot to copy modem.img backup to my PC! Also tried bunch of TWRP backups with no luck. My last hope was Mobile Upgrade Q and reverting back tu 5.0.2. Unfortunately with no success (only one sim slot is recognized again).
Finally I found this thread, followed the guide and I can confirm that it did solve sim issue. The setup finished with no errors that you mentioned. It got stuck at 45%, but after a while (10min) it completed successfully.
Cheers!
Click to expand...
Click to collapse
Alek Dev said:
You must do something Wrong...Press Pwr button and Volume up and down and thern connect to PC and then you will get RED SCREEN....Press Volume Up until you get Black screen and then press Download and if you get again same Send me Pm with Teamviewer ID AND PASS and i will try to help you
Click to expand...
Click to collapse
That is exactly what I'm doing,entering in Download mode and then download in the Panasonic software,but nothing,the program cannot read my phone,I'm really tired of trying this,I will stuck in your Alek rom (btw,no matter how many times I flash your modem,I cannot get the lock screen ).Ty anyway Alek and keep it up!!!!

Was on alek 3.0 before bootloop appear after a strange warning on android about battery, now got bootloop, no twrp access etc
try ur solution but after 45% and error, reboot and no screen about panasonic only bootloop
11.and your device will reboot and you will view 'the screen powered by android and then panasonic so i get message Encrypted device just click the button "reset" and automatically device will be reseted and when wil finish with reset automatically reboots and wait to first boot you will get welcome screen set up and finished.....
Click to expand...
Click to collapse
already tried SUGAR+QCT_SP+v10.5.1(4pda source) and mobile upgrade q 5.0.9, both finished without error after 100% but still bootloop
i think it s total broke with motherboard pb or battery

thorfr said:
Was on alek 3.0 before bootloop appear after a strange warning on android about battery, now got bootloop, no twrp access etc
try ur solution but after 45% and error, reboot and no screen about panasonic only bootloop
already tried SUGAR+QCT_SP+v10.5.1(4pda source) and mobile upgrade q 5.0.9, both finished without error after 100% but still bootloop
i think it s total broke with motherboard pb or battery
Click to expand...
Click to collapse
Looks Like Problem With Motherboard and Battery ..you can try again with Panasonic Firmware Tool and if this not help Send it to Warranty Repair

ok i m gonna send it to warr:crying:antly
retry mobil q upgrage wo success bootloop again

Bricked OnePlus 6T, messed up big time! Possible long thread ahead.

Hello everyone, I have bricked my OnePlus 6T...well, actually it wasn't me who is the reason this happened. :/ Open Beta 3 user.
On Thursday, I was using my phone like I normally would, I was sending a screenshot to a friend which I cut down, and after I cut the picture down, I was writing a text to support the picture, now here is what the big issue comes in. The phone was freezing - I was like, ''alright I am on a beta afterall'', and this wasn't the first time this freezing happened. Suddenly, the phone just shut itself down and went black. After a few seconds, it boot up, but while doing so, it went into Qualcomm Crash Dump Mode, which I knew I've seen before, but not on my ''old'' 5T, which had - and still has the Open beta installed on it, for well over a year now.
This was a first time thing, I have never seen this mode on my phone before and i was panicking a bit and immediately went up to my laptop. I googled a bit, and I saw that this issue isn't a first time issue, it happened before on the OnePlus 6's Open beta firmware. And I was somewhat relieved, since I thought I may be able to fix this easily without loosing any data. Wrong thought.
After this, I tried reflashing the OS in fastboot, i downloaded fastboot ROM's and tried flashing them - one after another, none of them worked.
Then I tried to ask some friends at the OnePlus forum, since some of them have more knowledge than me, a lot more actually. They tried giving me solutions without losing any data, no luck. Then I was like ''alright, I'm f**ked, I need to give up on my data''. And since all of this happened suddenly without me having a chance to predict, I had no chance to backup any important data. Then I tried the msmdownloadtool, which firstly was a mistake, as I (as stupid as I am) used the OnePlus 6 msmdownloadtool, then i realized that I was using the wrong tool, and I downloaded the OP6T msmdownloadtool, too. After the download finished, I ran the tool with my 6T plugged in, it went through in about 300 seconds and my 6T was not booting up. Sometimes, it came to the boot animation and just crashed while booting.
Friday came and I tried the same thing over and over, no luck. I was busy doing other things, so I had not much time doing this all day.
Saturday was in and I tried the same stuff, but this time, I downloaded the msmdownloadtool with OOS 9.0.5 instead of 9.0.11, which made a very good first impression, the phone was booting up! But - I couldn't do anything and it froze on me and crashed. It was booting up, but...the system was unusable, I could drag the statusbar down and tap onto the navbar, but thats all I could do before it froze.
After this, the phone rebooted and went into Qualcomm Crashdump Mode, again! But this time, there was the usual text you get while the phone is in this mode, which was NOT there before. ''Normally'', the phone went into that mode with only the Qualcomm Crash Dump Mode showing up.
I tried everything i could, but no luck. The bootloader is locked again, so I can't flash anything over fastboot, recovery has been changed with the 6/6T anyway, so no OS flashing possible with that either, I am clueless right now and i would like you guys to help me out before having to send the phone back.
And as I could no see a thread regarding this particular issue, I was sure I could open up a new one.
If there are any language mistakes or whatever, bear with me, English is not my primary language.
Oh, now I kind of forgot to edit this - My phone is back working again after RMA.

no no,it's cool,it's readable, English is fine.Msm tool should fix it..good thing is that its not hardbricked,it's still alive and sometimes booting.thats a good sign.in my opinion some partition is cousing problems and is probably corrupt.Try flashing latest MSM for 6T few times in a row,let it overwrigh,and while I bootloader try to unlock bootloader ,and then before you let phone boot,in bootloader fastboot boot TWRP img.if TWRP works,you can try flash something ,maybe OOS again and TWRP zip and try it boot.

shawek said:
no no,it's cool,it's readable, English is fine.Msm tool should fix it..good thing is that its not hardbricked,it's still alive and sometimes booting.thats a good sign.in my opinion some partition is cousing problems and is probably corrupt.Try flashing latest MSM for 6T few times in a row,let it overwrigh,and while I bootloader try to unlock bootloader ,and then before you let phone boot,in bootloader fastboot boot TWRP img.if TWRP works,you can try flash something ,maybe OOS again and TWRP zip and try it boot.
Click to expand...
Click to collapse
Hi! Thank you for your answer, but everything you mentioned, i have tried it already, every time I try to do a fastboot command, it'll not work, as Oem unlocking is disabled in the OS, and I'm not able to enable it, as mentioned, I'm not able to enter the OS.

xnutzii said:
Hi! Thank you for your answer, but everything you mentioned, i have tried it already, every time I try to do a fastboot command, it'll not work, as Oem unlocking is disabled in the OS, and I'm not able to enable it, as mentioned, I'm not able to enter the OS.
Click to expand...
Click to collapse
Can you sideload the OOS zip via stock recovery?

MarcoLK said:
Can you sideload the OOS zip via stock recovery?
Click to expand...
Click to collapse
Let me see, what's the cmd command for doing so?

xnutzii said:
Let me see, what's the cmd command for doing so?
Click to expand...
Click to collapse
Just type
Code:
adb sideload nameofthefile.zip
while you are in sideload mode of the recovery

MarcoLK said:
Just type
Code:
adb sideload nameofthefile.zip
Click to expand...
Click to collapse
Oh, alright, thanks. I'l try

xnutzii said:
Oh, alright, thanks. I'l try
Click to expand...
Click to collapse
Did not work. It says ''cannot read (name).zip''
MarcoLK said:
Just type
Code:
adb sideload nameofthefile.zip
while you are in sideload mode of the recovery
Click to expand...
Click to collapse
Also, there is no sideload on the 6T's stock recovery.

xnutzii said:
Did not work. It says ''cannot read (name).zip''
Click to expand...
Click to collapse
Even I have the same problem while sideloading zips.
I thought it was just my PC. And I never found any working solution for it.
Have you tried the HydrogenOS msmdownloadtool?
This is the chinese Version of OxygenOS (the system is in english I think)
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-hos-9-0-4-t3875673
Edit:
There should be an option.
It should look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MarcoLK said:
Even I have the same problem while sideloading zips.
I thought it was just my PC. And I never found any working solution for it.
Have you tried the HydrogenOS msmdownloadtool?
This is the chinese Version of OxygenOS (the system is in english I think)
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-hos-9-0-4-t3875673
Click to expand...
Click to collapse
Yes, I have tried it as well, I was hoping it'd do anything, but it didn't. The phone gets to the boot screen sometimes, but mostly it'll go to the Qualcomm Crashdump Mode again

xnutzii said:
Yes, I have tried it as well, I was hoping it'd do anything, but it didn't. The phone gets to the boot screen sometimes, but mostly it'll go to the Qualcomm Crashdump Mode again
Click to expand...
Click to collapse
I am sorry but I am out of ideas.
Maybe other people have other ideas.
But you can request a repair and ask if they can repair it and if it is free.

MarcoLK said:
I am sorry but I am out of ideas.
Maybe other people have other ideas.
But you can request a repair and ask if they can repair it and if it is free.
Click to expand...
Click to collapse
No problem, thanks for your support.
That was my last option, if nothing helped.
Also, I just saw your edit, there is no option like this, there are ''wipe data and cache'', '' Advanced'' ''Exit''

You said MSM tool 9.0.11 doesn't recognize your device.. did you try to press start on the tool anyway with your device plugged in via USB?
Most times it doesn't seem to recognise my phone either but then I press start and it takes some time before it start doing is thing..

Hey m8 use MSM tool took about 10 attempts plus for the files to start downloading not sure why? But that is your answer just stick with it

xnutzii said:
Hello everyone, I have bricked my OnePlus 6T...well, actually it wasn't me who is the reason this happened. :/ Open Beta 3 user.
On Thursday, I was using my phone like I normally would, I was sending a screenshot to a friend which I cut down, and after I cut the picture down, I was writing a text to support the picture, now here is what the big issue comes in. The phone was freezing - I was like, ''alright I am on a beta afterall'', and this wasn't the first time this freezing happened. Suddenly, the phone just shut itself down and went black. After a few seconds, it boot up, but while doing so, it went into Qualcomm Crash Dump Mode, which I knew I've seen before, but not on my ''old'' 5T, which had - and still has the Open beta installed on it, for well over a year now.
This was a first time thing, I have never seen this mode on my phone before and i was panicking a bit and immediately went up to my laptop. I googled a bit, and I saw that this issue isn't a first time issue, it happened before on the OnePlus 6's Open beta firmware. And I was somewhat relieved, since I thought I may be able to fix this easily without loosing any data. Wrong thought.
After this, I tried reflashing the OS in fastboot, i downloaded fastboot ROM's and tried flashing them - one after another, none of them worked.
Then I tried to ask some friends at the OnePlus forum, since some of them have more knowledge than me, a lot more actually. They tried giving me solutions without losing any data, no luck. Then I was like ''alright, I'm f**ked, I need to give up on my data''. And since all of this happened suddenly without me having a chance to predict, I had no chance to backup any important data. Then I tried the msmdownloadtool, which firstly was a mistake, as I (as stupid as I am) used the OnePlus 6 msmdownloadtool, then i realized that I was using the wrong tool, and I downloaded the OP6T msmdownloadtool, too. After the download finished, I ran the tool with my 6T plugged in, it went through in about 300 seconds and my 6T was not booting up. Sometimes, it came to the boot animation and just crashed while booting.
Friday came and I tried the same thing over and over, no luck. I was busy doing other things, so I had not much time doing this all day.
Saturday was in and I tried the same stuff, but this time, I downloaded the msmdownloadtool with OOS 9.0.5 instead of 9.0.11, which made a very good first impression, the phone was booting up! But - I couldn't do anything and it froze on me and crashed. It was booting up, but...the system was unusable, I could drag the statusbar down and tap onto the navbar, but thats all I could do before it froze.
After this, the phone rebooted and went into Qualcomm Crashdump Mode, again! But this time, there was the usual text you get while the phone is in this mode, which was NOT there before. ''Normally'', the phone went into that mode with only the Qualcomm Crash Dump Mode showing up.
I tried everything i could, but no luck. The bootloader is locked again, so I can't flash anything over fastboot, recovery has been changed with the 6/6T anyway, so no OS flashing possible with that either, I am clueless right now and i would like you guys to help me out before having to send the phone back.
And as I could no see a thread regarding this particular issue, I was sure I could open up a new one.
If there are any language mistakes or whatever, bear with me, English is not my primary language.
Click to expand...
Click to collapse
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.

hagar006 said:
You said MSM tool 9.0.11 doesn't recognize your device.. did you try to press start on the tool anyway with your device plugged in via USB?
Most times it doesn't seem to recognise my phone either but then I press start and it takes some time before it start doing is thing..
Click to expand...
Click to collapse
I never said it doesn't recognize my phone though. I know how the phone gets recognized by msmdownloadtool, thanks for your input though.

MRobbo80 said:
Hey m8 use MSM tool took about 10 attempts plus for the files to start downloading not sure why? But that is your answer just stick with it
Click to expand...
Click to collapse
I have flashed the sh*t outta my phone already, it doesn't work out sadly enough. I have tried everything besides this ↓
twinnfamous said:
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
Click to expand...
Click to collapse
This seems very unlikely, but I thank you for your input, let's see if this actually works for me. Hope I get the timing right.

twinnfamous said:
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
Click to expand...
Click to collapse
Alright, I've tried this now and it still says "boot is not allowed in lock state" :/

xnutzii said:
Alright, I've tried this now and it still says "boot is not allowed in lock state" :/
Click to expand...
Click to collapse
Sorry about your luck. The only thing I can recommend is trying the patched msmtool that is for converting from T-Mobile to global.
I had problems getting it to connect but what I did was power off device and held volume up and volume down even after plugging it in and pushing start.
Then when I got the error it didn't connect I unplugged it and plugged it back in all while still holding volume up and volume down. It took a few tries but it will connect.

twinnfamous said:
Sorry about your luck. The only thing I can recommend is trying the patched msmtool that is for converting from T-Mobile to global.
I had problems getting it to connect but what I did was power off device and held volume up and volume down even after plugging it in and pushing start.
Then when I got the error it didn't connect I unplugged it and plugged it back in all while still holding volume up and volume down. It took a few tries but it will connect.
Click to expand...
Click to collapse
The problem is not that the phone doesn't connect, it connects right away without any issues with the volume buttons clicked together, the msmtool runs through too! But the phone does NOT boot up after all of this is finished. It goes straight to Qualcomm crashdump mode.