Guys help needed.
I was flashing a custom kernel.
Kernal was flashed and after rebooting the phone went into Qualcomm Crashdump mode.
Any help is appreciated.
Use the MSM Download Tool. It will fix your device completely. I had the same ramdisk error after flashing a custom kernel too and the tool fixed it perfectly.
FYI : all your data will be wiped too, and bootloader will be relocked again.
Related
After installing CM13 (coming from 20H stock 4.4.2 firmware) I somehow ended up in the hard-brick Qualcomm HS-USB QDLoader 9008 mode.
I fixed this using these steps: http://forum.xda-developers.com/showthread.php?t=2582142 writing that old 2.6.3.2 TWRP and other .bin files extracted from the .kdz
Phone boots OK into CM13 now, but when I try to get into recovery (either using Power+Vol Down or through Advanced Reboot in CM) I get the error:
Secure booting error
Error: Boot Certification Verify!
Click to expand...
Click to collapse
Does anyone know how I can fix this, and flash TWRP? Tried TWRP Manager, Flashify etc, but they all give a flashing error. All fixes for this which I have found online seem to be for people who are running a stock ROM.
(I know going into download mode and returning to stock again etc will sort this, but surely that's not necessary?)
Hi all,
I'm hoping someone can shed some light on this problem ..
Background:
- Was running Oxygen OS and went to update it to the new beta, booted into TWRP, flashed the file and rebooted - nothing happened, black screen with a constantly lit blue LED.
- Back into recovery but it didn't ask me for a pattern so it no longer recognised the encrypted partitions.
- Ah well, erased everything a few times and booted back into recovery to flash a new ROM, TWRP loads but no longer responds on the touchscreen, it's stuck at the "swipe to allow modifications to system partition" screen
- booted into fastboot, reflashed TWRP, same deal, Tried all 3 available versions but no difference. Also tried the clockworx build.
- flashed stock recovery and tried to sideload the rom but the first time it bombed out at 48% or so, now it just stops with "Xfer 0.0%" ..
- Saw this thread here https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169 and downloaded it but the MSM tool does not recognise any connected device even though I have "Qualcomm HS-USB QDLoader 9008 COM23" in the device manager
I'm going pretty nuts now so any tips appreciated :/
Cheers
K
Right - quick update - managed to get it re-flashed using the MSM Downloader tool after a lot of trial and error .. if anyone has any questions about the process just let me know!
on my phone TWRP shows no files on in any folder. can you pls help?
krrunch said:
Right - quick update - managed to get it re-flashed using the MSM Downloader tool after a lot of trial and error .. if anyone has any questions about the process just let me know!
Click to expand...
Click to collapse
Hi! I believe that I am in the same boat as you were. On short: was rooted & wanted to stock. Flashed stock recovery & last OS from oneplus site and got stuck in boot. Afterwards I was no longer able to see my device in the stock recovery adb install....
Can you give me a hand please! Thank you!
Edit: Got it to work with the qualcomm method
Hello,
You should install Hydrogen OS to unbrick your phone.
After that install TWRP and then install the full rom OOS 5.0.4.
As I say in the title I have a LG G3 D855 and I was trying to root it and installt twrp but I completely screwed up.
After that I managed to go into the qualcomm bootloader and restore the phone following this tutorial https://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091, but I keep on getting security error loop.
I cannot enter download mode, therefore I cannot flash my rom again. I have tried already with the tot images from EUR and HKG, and still no improve.
Any experience/help on solving this?
Thanks in advance!
Though I have some experience with rooting phones and flashing custom rooms, I still consider myself to be no more than a novice in this subject. I have a LG K20 PLUS, metro pcs, and I have it rooted running PBRP recovery and the unofficial lineage 14.1 rom. I have been trying different roms and just recently kernels. I was trying to get kali nethunter working and on here at xda two files that I could flash to install it. I will have to go and look to get the names right but one was something like kali nethunter generic rolling something and the other was a custom kernel to complement it. Both flashed without any errors. When I rebooted, after the LG logo I found myself with a kernel panic error.
Kernel crash!
DemiGod Handler : Kernel Crash!
If you want to get ram dump,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get ram dump image using QPST Configuration.
Board Info : 6
rev. : 1.0, cx_pvs: 1 mx_pvs: 1
serial : aadd87fc0000000
secure boot : enabled
[ 4.000591 / 01-01 00:00:07.439][3] Kernel panic - not syncing: adsp_loader_do: pil get failed.
Jump to Bload Mode.
I am still able to enter revory mode and through recovery boot to bootloader. I had attempted reflashing the recovery to TWRP, which was successfull, but attempting reflashing kernels (though flashing without errors) has had no effect on the kernel panic issue. I have reflashed roms as well, it seems nothing that I know how to do will fix the problem. Surfing the web for answers... has only shined light on just how little I understand a lot of this stuff. Most information ℹ have been able to find (in a lot of cases I don't even know if it applies to my specific problem) is way beyond my technical ability to comprehend. I hope that someone here can guide me through this panic and help get my K20 plus functional again. :fingers-crossed:
You're gonna need a PC with LG Windows USB drivers, LG UP v1.14, as well as LG Uppercut 1.0 which is a modified version of LG UP, and a stock .kdz image to reflash your phone back to stock. You can find those links on this forums or other LG phones threads. I'm pressed for time so I can't link them all. I've had a similar issue with kernel panic where flashing any ROM or kernel couldn't fix the issue. The only thing I could do was flash a stock image so that the partitions could be overwritten and corrected. You can find the LG stock image here https://lg-firmwares.com/lg-mp260-firmwares/#tab=firmwares I suggest an older variant like 10j or 10v, though I've had success installing 11k and reverting to 10j but I'm not certain if the newer images have any code that makes it more difficult to modify bootloaders or revert to older stock versions. MTP is your ideal image. MTD is a Metro Demo and MTK are FRU (field replaceable unit) images with some capability of having special resizable partitions but that goes beyond my understanding and scope of this post.
There's a chance you'll find Download mode on your phone doesn't stick to more than 20 seconds or so, which isn't enough to flash an image without issues. I found the fix for this was to go into recovery and wipe everything you're allowed to wipe, recovery will caution there is no operating system installed. That's fine. Rebooting to system should lead to a similar warning on boot. Custom Recovery should still work but you won't need it. You'll need to get back to download mode, plug the phone to the computer, and be sure it is recognized by Device Manager along with a COM port number associated to it. LG UPPERCUT should then be able to see the phone model and COM port and launch, it won't launch otherwise. Once LG UP is running, load up the .kdz image and click UPGRADE. As long as your phone is able to remain in Download mode for more than 30 seconds you're good. If it continues to reboot short of that, give it another thorough wipe in custom recovery.
Once you have flashed stock, you can go back to adb or fastboot and reflash a custom recovery and root program as you did initially. Your bootloader should still remain unlocked after flashing stock so there's no need to run fastboot oem unlock commands again.
CabbyKing said:
Though I have some experience with rooting phones and flashing custom rooms, I still consider myself to be no more than a novice in this subject. I have a LG K20 PLUS, metro pcs, and I have it rooted running PBRP recovery and the unofficial lineage 14.1 rom. I have been trying different roms and just recently kernels. I was trying to get kali nethunter working and on here at xda two files that I could flash to install it. I will have to go and look to get the names right but one was something like kali nethunter generic rolling something and the other was a custom kernel to complement it. Both flashed without any errors. When I rebooted, after the LG logo I found myself with a kernel panic error.
Kernel crash!
DemiGod Handler : Kernel Crash!
If you want to get ram dump,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get ram dump image using QPST Configuration.
Board Info : 6
rev. : 1.0, cx_pvs: 1 mx_pvs: 1
serial : aadd87fc0000000
secure boot : enabled
[ 4.000591 / 01-01 00:00:07.439][3] Kernel panic - not syncing: adsp_loader_do: pil get failed.
Jump to Bload Mode.
I am still able to enter revory mode and through recovery boot to bootloader. I had attempted reflashing the recovery to TWRP, which was successfull, but attempting reflashing kernels (though flashing without errors) has had no effect on the kernel panic issue. I have reflashed roms as well, it seems nothing that I know how to do will fix the problem. Surfing the web for answers... has only shined light on just how little I understand a lot of this stuff. Most information have been able to find (in a lot of cases I don't even know if it applies to my specific problem) is way beyond my technical ability to comprehend. I hope that someone here can guide me through this panic and help get my K20 plus functional again. :fingers-crossed:
Click to expand...
Click to collapse
Any updates? Were you able to get your phone up and running?
Okay, Let me explain exactly what I did here... I first flashed Twrp using SP flash tool which worked without too much problem. Then I attempted to install the latest super su zip which told me the boot.img was already patched and it could not find a ramdisk... So I moved on and flashed the latest Magisk zip which flashed no problem. Rebooted the device and it came up with a red boot state telling me it would boot in 5 sec. It did not boot at all. Turned off the tablet and rebooted into twrp again. I then flashed the OTA update system.img, boot.img, and re-flashed twrp from twrp itself instead of the SP flash tool. It booted into twrp no problem, however now it said it could not mount the system partition. I did a full data wipe, factory reset, rebooted into twrp again. Same issue. So I attempted to re-flash the firmware with SP flash tool. Did not notice i had it set to format and download and not only download. It said formatting for maybe 2 sec and gave me an error. Now the device will not turn on at all... no screen whatsoever, no recovery, etc... I have had no luck getting the asus flash tool to even recognize a com port however SP flash tool seems to be able to flash the device no problem. I extracted the .raw firmware file I have for the latest firmware, modified the scatter file to allow flashing all partitions, and I did a full firmware flash of the device using SP flash tool. However it still does not turn on... it does nothing... So I'm assuming that I accidentally formatted over the bootloader... And I cannot find a bootloader flash file for this device anywhere... So I'm stuck with an Asus ZenBrick... Does anyone know a way to fix this issue? When I plug the device into my computer and open device manager it switches between the preloader and mtk serial port very quickly not staying on either one very long. I'm assuming this is why I cant get the asus flash tool to work and SP flash tool works off just the initial preloader. I just bought this tablet from someone and managed to hard brick it in less than a days time... Any help at all with a way to revive this device will be greatly appreciated. Thank You in advance to anyone who tries to help me fix my mess up.