Hi There,
I wonder if anyone can help to recover Yureka?
I was trying to update rom using fastboot rom on the phone and it has broken the phone.
I am now getting Qualcomm HS-USB QDLOADER 9008.
Can anyone please me to recover my phone?
Thanks in advance.
Samir
flash stock rom using ADB
thearjunraju said:
flash stock rom using ADB
Click to expand...
Click to collapse
I guess ADB access only possible when you have working phone.
so I think not possible using ADB.
I can't go to bootloader either.
so not possible using fastboot either
if you can boot into the bootloader mode, do so.
to boot into the bootloader mode:
>switch off the phone
>press and hold the volume up button
>while pressing the volume up button, plug in the usb cable. (needless to say, the other end should be attached to your computer, and the required drivers should be installed)
prerequisites:
download the stock zip from here htt p:// builds.cyngn. c om/factory/tomato/cm-11.0-XNPH52O-tomato-signed-fastboot. zip
download the fastboot tools
make a *.bat file of the following code:
<code>
@ECHO off
echo Flashing kernel
fastboot -i 0x1ebf flash boot boot.img
echo Flashing system
fastboot -i 0x1ebf flash system system.img
echo Wiping Data
fastboot -i 0x1ebf flash userdata userdata.img
echo Flashing recovery
fastboot -i 0x1ebf flash recovery recovery.img
echo Flashing model
fastboot -i 0x1ebf flash modem NON-HLOS.bin
fastboot -i 0x1ebf flash rpm rpm.mbn
echo Flashing bootloader
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
echo Flashing complete. Disconnect device and reboot
</code>
extract both the zips in the same folder and run the bat file while your phone is plugged in in the bootloader mode.
cheers!
My Yu Yureka is Hard Bricked
My Yu Yureka is Hard Bricked .....can anyone help me to unbrick it
my phone is not start in Fastboot Mode and Normal Mode
In QPST it always shows download mode
please help me out
I want 8916_msm.mbn,MPRG8916.hex files
I have tried to install twrp recovery via fastboot and I get this error
1.C:\fastboot>fastboot flash recovery recovery.img
2.target reported max download size of 1526722560 bytes
3.error: cannot load 'recovery.img': No error
All other commands work to erase, reboot etc, but cannot flash recovery twrp on to my LGG2 D803 , any help will be appreciated.
Got it to work but flashed 3 different twrp and cm mod img and will not boot into recovery
Well if you ever Brick your phone to the point that the only thing that works is Fastboot, I was able to recover my phone using this procedure, It was a lifesaver. The phone works perfectly now, follow the Youtube instructions, I also typed the procedure out too. Always type fastboot flash then the command
https://www.youtube.com/watch?v=hQVTc2m6U-I
Use above link to completely redoo your LGG2 from fastboot, re loading all the partitions.
fastboot flash boot boot.img
aboot aboot.img
recovery recovery.img
laf laf.img
dbi dbi.img
modem modem.img
persist persist.img
PrimaryGPT PrimaryGPT.img
rpm rpm.img
stli stli.img
tz tz.img
fastboot flash reboot
after flashing all the partitions it should load so you can flash the tot/kdz file via flash utility 2014 in the command mode, by holding the volume up mode and plugging in the usb into the phone. then reload the original firmware and install twrp and if you want wipe it and reload one of the custom roms.
Well if you ever Brick your phone to the point that the only thing that works is Fastboot, I was able to recover my phone using this procedure, It was a lifesaver. The phone works perfectly now, follow the Youtube instructions, I also typed the procedure out too. Always type fastboot flash then the command
https://www.youtube.com/watch?v=hQVTc2m6U-I
Use above link to completely redoo your LGG2 from fastboot, re loading all the partitions.
fastboot flash boot boot.img
aboot aboot.img
recovery recovery.img
laf laf.img
dbi dbi.img
modem modem.img
persist persist.img
PrimaryGPT PrimaryGPT.img
rpm rpm.img
stli stli.img
tz tz.img
fastboot flash reboot
after flashing all the partitions it should load so you can flash the tot/kdz file via flash utility 2014, in the command mode, by holding the volume up button and plugging in the usb into the phone. then reload the original firmware and install twrp and if you want wipe it and reload one of the custom roms.
I accidentally disconnected my OnePlus 8 Pro while running the MSM Tool to restore back to oxygenos from lineage. Now it is stuck in a loop where it says:
<Error!>
Upgrade download failed!
This is caused by download interruption. Recommend you use download tool try again.
You need to confirm if there is failure message on download tool or not when you see this error.
also please check if you disconnect usb or click stop button when the download is not finished yet.
You can press any key exit this message
I can boot into fastboot from this state, but I am unable to flash a recovery or use a fastboot rom.
The recovery just doesn't work when I try to boot into it, and the fastboot rom gets stuck at
"Flashing is not allowed for critical partitions"
and when I try running
fastboot flashing unlock_critical
it says something along the lines of 'device already unlocked'
I cannot boot into EDL mode either, and trying to do so doesn't work.
I feel as if I am out of options, and am very worried about my phone.
Please help!!!
I was able to successfully follow all the steps for a fastboot rom, but it still didn't work. This was through using fastboot boot on the lineageos recovery.
Dapherino said:
I was able to successfully follow all the steps for a fastboot rom, but it still didn't work. This was through using fastboot boot on the lineageos recovery.
Click to expand...
Click to collapse
Use MSM Tool. Hold all buttons very until your device appears in msm tool. YOu can start before you connect it and it should work.
xtcislove said:
Use MSM Tool. Hold all buttons very until your device appears in msm tool. YOu can start before you connect it and it should work.
Click to expand...
Click to collapse
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Dapherino said:
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Click to expand...
Click to collapse
Try to press start while the device is connected and then restart it. MSM tools trys to hook in first.
Dapherino said:
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Click to expand...
Click to collapse
Turn phone completely off. On msm tool, hit start so its waiting for device. Hold down ONLY the volume up and volume down buttons, plug in USB cable and you're good to go
jamescable said:
Turn phone completely off. On msm tool, hit start so its waiting for device. Hold down ONLY the volume up and volume down buttons, plug in USB cable and you're good to go
Click to expand...
Click to collapse
Thank you for the advice. I've tried this and it doesn't do anything, since I can't get to EDL mode.
xtcislove said:
Try to press start while the device is connected and then restart it. MSM tools trys to hook in first.
Click to expand...
Click to collapse
Thanks, I've tried this as well. It didn't work, since I cannot enter EDL mode.
Dapherino said:
Thank you for the advice. I've tried this and it doesn't do anything, since I can't get to EDL mode.
Click to expand...
Click to collapse
Your phone is in EDL mode when its powered off and holding ONLY both volume bottons
jamescable said:
Your phone is in EDL mode when its powered off and holding ONLY both volume bottons
Click to expand...
Click to collapse
I understand that. When I do so, it just boots into fastboot. And when I tried to enter EDL through using 'fastboot boot' with a custom recovery, it did the same thing. Now I can't even use 'fastboot boot' anymore for some reason though.
Dapherino said:
I understand that. When I do so, it just boots into fastboot. And when I tried to enter EDL through using 'fastboot boot' with a custom recovery, it did the same thing. Now I can't even use 'fastboot boot' anymore for some reason though.
Click to expand...
Click to collapse
So you tried fastboot boot recovery?
Fastboot boot will never work to boot edl
jamescable said:
So you tried fastboot boot recovery?
Fastboot boot will never work to boot edl
Click to expand...
Click to collapse
Yes. Even from a temporary custom recovery, I cannot enter edl from there.
Dapherino said:
Yes. Even from a temporary custom recovery, I cannot enter edl from there.
Click to expand...
Click to collapse
Do this. Install a custom ROM using fastboot
Download any ROM you want. Extract the payload and put it in the payload input folder.
jamescable said:
Download any ROM you want. Extract the payload and put it in the payload input folder.
Click to expand...
Click to collapse
I've tried this with 4 different roms [stock oneplus one, lineageos, pixel experience, and evolutionx]. Even though they flash successfully, I still encounter the exact same error when trying to boot into it, and I still cannot enter recovery or EDL.
Dapherino said:
I've tried this with 4 different roms [stock oneplus one, lineageos, pixel experience, and evolutionx]. Even though they flash successfully, I still encounter the exact same error when trying to boot into it, and I still cannot enter recovery or EDL.
Click to expand...
Click to collapse
This wont work and idk why. If i try a custom rom i always have to use msm tool to go back to oos.
I flash every partition with fastboot but i end in a boot loop if i where on a custom rom before.
xtcislove said:
This wont work and idk why. If i try a custom rom i always have to use msm tool to go back to oos.
I flash every partition with fastboot but i end in a boot loop if i where on a custom rom before.
Click to expand...
Click to collapse
Yeah, you need to wipe internal storage. In fastboot you can type
fastboot format userdata
fastboot format cache
Also, you can type
Fastboot -w
Dapherino said:
I accidentally disconnected my OnePlus 8 Pro while running the MSM Tool to restore back to oxygenos from lineage. Now it is stuck in a loop where it says:
<Error!>
Upgrade download failed!
This is caused by download interruption. Recommend you use download tool try again.
You need to confirm if there is failure message on download tool or not when you see this error.
also please check if you disconnect usb or click stop button when the download is not finished yet.
You can press any key exit this message
I can boot into fastboot from this state, but I am unable to flash a recovery or use a fastboot rom.
The recovery just doesn't work when I try to boot into it, and the fastboot rom gets stuck at
"Flashing is not allowed for critical partitions"
and when I try running
fastboot flashing unlock_critical
it says something along the lines of 'device already unlocked'
I cannot boot into EDL mode either, and trying to do so doesn't work.
I feel as if I am out of options, and am very worried about my phone.
Please help!!!
Click to expand...
Click to collapse
This happened to me. I tried downloading Qualcomm drivers and reinstalling them and moved my platform tools to root of C:\, among other things. I was using OEM red cable and had been having to flip it a certain way to get WARP charge, so in desperation, I switched to a non-OEM cable, C to C, and that got me back in EDL. Good luck.
jamescable said:
Yeah, you need to wipe internal storage. In fastboot you can type
fastboot format userdata
fastboot format cache
Also, you can type
Fastboot -w
Click to expand...
Click to collapse
thats part of my batch script anyway.
Code:
:choice
set /P c=Do you want to wipe all the data ( Reccomended )[Y/N]?
if /I "%c%" EQU "Y" goto :wipe
if /I "%c%" EQU "N" goto :continue
goto :choice
:wipe
fastboot -w
goto :continue
:continue
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot fastboot
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot reboot-bootloader
pause
wgs1028 said:
This happened to me. I tried downloading Qualcomm drivers and reinstalling them and moved my platform tools to root of C:\, among other things. I was using OEM red cable and had been having to flip it a certain way to get WARP charge, so in desperation, I switched to a non-OEM cable, C to C, and that got me back in EDL. Good luck.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!!!! Using a different cable worked!!!!!!!!!!!!!!!!!!!!!!!!!!!! I'm so glad my phone is ok. Thank you again, I really appreciate it.
Hello Everyone
My Oneplus 8 Pro won't turn on at all , not to recovery mode , not to fastboot mode , not to EDL mode , not even to charge... nothing
And I'm pretty sure everything is set up correctly , the msm tool , the qualcomm drivers , the cable and the port because i have an old oneplus 3t which i'm using for now and it got recognized in the msm tool as soon as i connected it
Here is some context of what happened before my Oneplus 8 Pro died :
I never flashed any custom roms on it , i've been using the stock firmware with root the whole time
I had a custom kernel installed on Android 11 before updating to Android 12 , when i updated to Android 12 (OTA update) the kernel went back to the stock one
after updating to Android 12 there was another OTA update that always fails to install (I believe it was 11.c.16), i got tired of it so i decided to manually updating to the latest firmware including that 11.c.16 incremental update and be done with it
I couldn't sideload it using TWRP becuase i couldn't install TWRP , everytime i tried to flash it using fastboot it seems like it succeeded but when i boot to recovery it boots to fastboot mode
so i googled how to install a firmware using fastboot commands , i found a method to flash the files one by one after extracting them using payload dumper and i tried it , when i was done flashing the files , as soon as i hit enter on the last command to reboot the phone it went to a black screen and has been dead ever since
Here are the fastboot commands i used to flash the firmware :
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot -w
fastboot reboot
Sorry for taking so long , I'm desperate
Any kind of help , suggestions or ideas are much appreciated
I haven't been keeping up on that thread since since it doesn't affect me, but I think you fell into the known "OOS Deathtrap" that's been explained here.
Like I said - no idea if it has a solution, or even if there is one now, but it couldn't hurt to read it.
Well... at least now i know what caused the issue , unfortunately i don't think there is a solution other than replacing the motherboard (which was the the solution i wanted to avoid)
I think it's time to say goodbye to oneplus
I wish i had read that article before flashing , Oneplus should put a disclaimer or a warning or something
Hi all,
This is a long shot, I hope there is someone somewhere that can help with this issue. I know it's a fairly old phone now, but if anyone has any knowledge about android recovery, it would be greatly appreciated!
Version: OxygenOS 3.6.1.
Rooted via Magisk and Bootloader Unlocked years ago.
The problem was unexpected. It was suffering battery drains for the past month, and last night, whilst on charge, I noticed it restarted. And now it's stuck on the OnePlus LOGO Screen. D:
I can only access FASTBOOT and NOT RECOVERY mode.
What I've tried:
MSM RECOVERY TOOL (w/ QCOM drivers)
Installing ABD Interface Drivers to try an ADB Sideload (but can't get to recovery)
Fastboot flashing stock and TWRP recoveries (can't boot into it - error dtb not found).
Fastboot flash_Ox211.cmd *
Spoiler: * flash_Ox211.cmd does the following
Code:
rem adb reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
rem fastboot erase recovery
rem fastboot flash recovery unofficial_twrp_2.8.7.0-bacon.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sdi sdi.mbn
fastboot flash pmic pmic.mbn
fastboot flash hyp hyp.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oem_stanvbk static_nvbk.bin
rem fastboot flash userdata userdata_64g.img
pause
rem fastboot reboot
None of the above has worked or has fixed recovery mode.
I want to keep my userdata. Is it possible to access that partition, and/or somehow do an 'adb backup'. It might be impossible without the recovery
To keep documenting my findings on extra things that I have done or will do.
Reseating the battery
I have drained the battery and taken the battery connection out the phone for an hour.
UPDATE: After re-plugging, and putting it into charge, the phone bootloops now instead of staying stuck on the OnePlus/Android LOGO continuously. NO CHARGING INDICATOR.
Replacing the battery
If it's a battery issue, then a replacement might work. I have ordered one.
UDPATE: TBD
Fastboot Flashing other recovery img's
dtb not found (or device tree blob) - was an issue when I tried booting into a flashed recovery (stock or TWRP). According to some forum posts, it may be due to flashing the wrong recovery version on the device.
UPDATE:
stock []
twrp-2.8.7.0-oneplus2 [] - no dtb error
twrp-3.0.0-1-oneplus2 []
twrp-3.0.2-1-oneplus2 []
twrp-3.2.1-0-oneplus2 []
...
↑ Doing a fastboot boot <recovery>.img bootloops the phone.
Try asking in the op2family discord server, there are some pretty knowledgeable ppl there. Also you could try asking _undead, he's the one who made lineage 19.1 for op2, see in Original Android Development on this forum.
Huh, it sounds like you're having a similar issue as me. Except I can access recovery but not fastboot... and sideloading isn't working for me.