Database Info

[Q] qhsusb dload mode xperia l

For any member of this forum.
Can you help me to unbrick my XL because my xperia l has hardbrik yesterday
That begin when I want to change external memory to internal memory and I had edited fold.fstab file
after I reboot my phone, on notification bar appear about error on my internal memory and must be format..
so I format my internal memory
and I turn off my phone..
after that I can't turn on my phone again..
maybe my phone has corrupt obout file system/partition
and haven't bootloader..
I can't flash use flashtool because my phone not detected on computer. fastboot also not detected..
but when I press vol up+vol down and connect to usb cable on my PC
it show about qhsusb-dload device ..
after I search on google and xda I feel have solution..
1 .Use QPST SOFTWARE FROM QUALCOMM
from this tutorial (indonesian) >" http://rendy37.wordpress.com/2013/08/30/tutorial-unbrick-andromax-u-dualcore-terdeteksi-qualcomm-hs-usb-qdloader-90089006/"
but I can't find mbn and hex files for msm8230 qualcom device
anyone can help to searh mbn/hex files msm8230 !
2. Use dump/backup mmcblkp0 file of xperia l
after I read this tutorial > "http://forum.xda-developers.com/showthread.php?t=2439367"
I think that trick also will work on msm8230/xperia l device because SIII use msm8960 qualcomm that same version/generation of qualcomm soc..
so anyone can upload dump/backup file of xperia 4.1.2 mmcblk0 for me.. !
3. or anyone have other solution...
thanks before..
sory for my bad english and my thread because I create it via operamini..

I have the same problem pls share hex/hxb files

Please Post
krynin said:
i have the same problem pls share hex/hxb files
Click to expand...
Click to collapse
gkohar said:
for any member of this forum.
Can you help me to unbrick my xl because my xperia l has hardbrik yesterday
that begin when i want to change external memory to internal memory and i had edited fold.fstab file
after i reboot my phone, on notification bar appear about error on my internal memory and must be format..
So i format my internal memory
and i turn off my phone..
After that i can't turn on my phone again..
Maybe my phone has corrupt obout file system/partition
and haven't bootloader..
I can't flash use flashtool because my phone not detected on computer. Fastboot also not detected..
But when i press vol up+vol down and connect to usb cable on my pc
it show about qhsusb-dload device ..
After i search on google and xda i feel have solution..
1 .use qpst software from qualcomm
from this tutorial (indonesian) >" http://rendy37.wordpress.com/2013/08/30/tutorial-unbrick-andromax-u-dualcore-terdeteksi-qualcomm-hs-usb-qdloader-90089006/"
but i can't find mbn and hex files for msm8230 qualcom device
anyone can help to searh mbn/hex files msm8230 !
2. Use dump/backup mmcblkp0 file of xperia l
after i read this tutorial > "http://forum.xda-developers.com/showthread.php?t=2439367"
i think that trick also will work on msm8230/xperia l device because siii use msm8960 qualcomm that same version/generation of qualcomm soc..
So anyone can upload dump/backup file of xperia 4.1.2 mmcblk0 for me.. !
3. Or anyone have other solution...
Thanks before..
Sory for my bad english and my thread because i create it via operamini..
Click to expand...
Click to collapse
please post someone, many of us having this problem

Hi guys, so i have the same problem with my xperia l.
But my friend have a working one. Is it possible to get the hex and mbn and that backup of mmcblk0 from that device ? If yes please tell me how to or give me a link to a tutorial and i'll upload that files.

No solution yet?

opps i also am stuck here, any idea how to solve ? or steps ? really appreciated if anyone can help

I have been stuck over here for a long time I and my Friend are trying to solve the problem at the Moment, but didn't any success yet. If you guys can help then Please Try to Search for MSM8230.HEX file.
If you get the file then please reply me through mail or reply here.

was sucessfully able to generate mbn file with a chinese tutorial (thx google for translation)
i have :
partition0.bin
partition.xml
rawprogramming.xml
8230_msm.mbn
all we need now is MPRG8230.hex or MPRG8x30.hex
anyone have this(or know how to extract? my device is working)
Sent from my C2105 using XDA Free mobile app

I have the same problem
SdtBarbarossa said:
was sucessfully able to generate mbn file with a chinese tutorial (thx google for translation)
i have :
partition0.bin
partition.xml
rawprogramming.xml
8230_msm.mbn
all we need now is MPRG8230.hex or MPRG8x30.hex
anyone have this(or know how to extract? my device is working)
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
can you share the link..??

syahru96 said:
can you share the link..??
Click to expand...
Click to collapse
sdtbarbarossa.bplaced.net
Sent from my Xperia T using XDA Free mobile app

I'm sorry for reviving such an old thread, by recently my xperia l turned off on its own. i've tried but can't enter flashmode/fastboot. no response from the phone except my pc detects it and looks for QHSUSB_DLOAD drivers. i'm wondering if anyone's found a solution to this? i've been searching for a while now and all the threads/sites i came across haven't helped.

cascabel said:
I'm sorry for reviving such an old thread, by recently my xperia l turned off on its own. i've tried but can't enter flashmode/fastboot. no response from the phone except my pc detects it and looks for QHSUSB_DLOAD drivers. i'm wondering if anyone's found a solution to this? i've been searching for a while now and all the threads/sites i came across haven't helped.
Click to expand...
Click to collapse
Dang, what did you do before it turned off?

Joel16 said:
Dang, what did you do before it turned off?
Click to expand...
Click to collapse
i went back to stock rom. everything was fine. next day i was browsing and left it on the table 'cause i had something to do. when i went back for it it was already dead.
looks like a hard brick. good news is i can try stuff i wouldn't have if it was still working. currently looking for XL's test points.:laugh:

cascabel said:
i went back to stock rom. everything was fine. next day i was browsing and left it on the table 'cause i had something to do. when i went back for it it was already dead.
looks like a hard brick. good news is i can try stuff i wouldn't have if it was still working. currently looking for XL's test points.:laugh:
Click to expand...
Click to collapse
XL dont have a testpoint.... i already searched for it .... we did so damn much trys in the past
.... as long as you dont get a MPRG8230.hex ....you are doomed...
JTag is the only option
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
XL dont have a testpoint.... i already searched for it .... we did so damn much trys in the past
.... as long as you dont get a MPRG8230.hex ....you are doomed...
JTag is the only option
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
well that's not good.
can you point me to a thread regarding MPRG8230.hex? good news is that the phone is recognized by setool. will see if anything good comes out of that.

if you have much time to try.... download qpst .... and get any mprg hex ....and try to find out what is our start code^^ (the first line....)

SdtBarbarossa said:
if you have much time to try.... download qpst .... and get any mprg hex ....and try to find out what is our start code^^ (the first line....)
Click to expand...
Click to collapse
got it. will do once i get some free time.

ok i have qpst. will be trying it this weekend (fingers crossed).
@SdtBarbarossa(or anyone interested) have you seen this: http://forum.gsmhosting.com/vbb/f672/experia-l-c2105-read-n-write-full-dump-not-success-1889128/
i can't access any of the links posted. it's probably my isp since there's a storm now and my connection is pretty unstable. just posting it for anyone who wants to take a look. you guys probably have seen it already.
Edit:
Not sure if I should be happy, but now the phone actually shows signs of life. for a split second when i plug in the cable, a green light flashes. i'm not if sure if that's a good or bad thing.

sob...still waiting
No Solution yet?
S1tool - taoshan seems not supported so our best hope is to really wait for someone to upload the hex file.

we really need the .hex file. unfortunately, no one has uploaded it anywhere. we may be able to use a .qcn file from a working phone though. not sure how much that would help, but at this point it's all we've got realistically.
---------- Post added at 05:50 PM ---------- Previous post was at 04:57 PM ----------
Does anyone still have the .mbn and .bin file?

cat s50 suddenly turn of and shows Qualcomm HS-USB QDLoader 9008

Hi I have a cat s50 qualcomm msm8926 snapdragon 400, the phone was turned off suddenly and shows Qualcomm HS-USB QDLoader 9008, I have read several posts on the forum about unbrick, but none seem to work, I think the mistake is the wrong rom.
I'm using qfil.
Where I can get the stock rom for this device?
I have also a phone running ok, I can make a backup of that rom?
Any suggestions are welcome.

Facundo Luque said:
Hi I have a cat s50 qualcomm msm8926 snapdragon 400, the phone was turned off suddenly and shows Qualcomm HS-USB QDLoader 9008, I have read several posts on the forum about unbrick, but none seem to work, I think the mistake is the wrong rom.
I'm using qfil.
Where I can get the stock rom for this device?
I have also a phone running ok, I can make a backup of that rom?
Any suggestions are welcome.
Click to expand...
Click to collapse
Try this
www.androidbrick.com/unbrick-all-qu...f-you-have-the-right-kind-of-rom-qhsusb_dload
Or this
www.androidbrick.com/ultimate-qualc...ragons-are-unbrickable-qhsusb_dload_qpst_qfil

Guys im having the same issue

Nuxon_22 said:
Guys im having the same issue
Click to expand...
Click to collapse
Refer to the links in the post above yours.
Sent from my SM-S903VL using Tapatalk

oh dude, i have tried that but its a hole mess, that at the end of the day i cant understand
---------- Post added at 11:38 PM ---------- Previous post was at 11:36 PM ----------
but i understand that qfil will help me to unbrick phone, but there are no posts with the files for the snapdragon 400, i have also tried with the stock firmware, but the firmware doesnt have the files that qfill needs, do i have to convert something before using qfil?

Nuxon_22 said:
oh dude, i have tried that but its a hole mess, that at the end of the day i cant understand
---------- Post added at 11:38 PM ---------- Previous post was at 11:36 PM ----------
but i understand that qfil will help me to unbrick phone, but there are no posts with the files for the snapdragon 400, i have also tried with the stock firmware, but the firmware doesnt have the files that qfill needs, do i have to convert something before using qfil?
Click to expand...
Click to collapse
Do a Google search for:
"Qhsusb dloader 9008 unbrick"
You'll find many different guides for fixing this.
Sent from my SM-S903VL using Tapatalk

I did that but, it seems that i need a few files, including a .mbn file, and i dont know how to convert the zipped file or its contents intro a format readable for qfil, can you help me with that, because im lost at that part of how to convert, or where to download the unbrick files for the MSM8926

Nuxon_22 said:
I did that but, it seems that i need a few files, including a .mbn file, and i dont know how to convert the zipped file or its contents intro a format readable for qfil, can you help me with that, because im lost at that part of how to convert, or where to download the unbrick files for the MSM8926
Click to expand...
Click to collapse
You need to use your model number to search for the files you need. If there is more than one stock firmware for your device then you'll also need to use the build number of the stock firmware that you had before you tried modifying the device.
If you don't know the build number of what you had then you can go by the android version you had: i.e. kit kat, lollipop, marshmallow, etc.

Dude i have tried but theres absolutely nothing
---------- Post added at 07:34 AM ---------- Previous post was at 07:31 AM ----------
There are just 2 roms found, and both look the same at the inside, there is no rawprogram.xml or etc to use with qfil, and unbricking files for the MSM8926 doesnt seem to even exist, and if i use the only rawprogram.xml that worked for me, it turns out that that the other 2 qfil needed files doesnt work

Nuxon_22 said:
Dude i have tried but theres absolutely nothing
---------- Post added at 07:34 AM ---------- Previous post was at 07:31 AM ----------
There are just 2 roms found, and both look the same at the inside, there is no rawprogram.xml or etc to use with qfil, and unbricking files for the MSM8926 doesnt seem to even exist, and if i use the only rawprogram.xml that worked for me, it turns out that that the other 2 qfil needed files doesnt work
Click to expand...
Click to collapse
All I can say is either keep searching or find someone with your same model number and stock firmware and see if they have anything to help you.
Sent from my SM-S903VL using Tapatalk

Ok, and is there something else i can do with the zipped firmware, maybe pushing it through adb?

Nuxon_22 said:
Ok, and is there something else i can do with the zipped firmware, maybe pushing it through adb?
Click to expand...
Click to collapse
If the zipped file contains the various partition .img's then yes you can extract them and possibly push them via adb or flash them via fastboot if you have fastboot. Resaca the possibility first to be sure you don't cause a worse issue.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
If the zipped file contains the various partition .img's then yes you can extract them and possibly push them via adb or flash them via fastboot if you have fastboot. Resaca the possibility first to be sure you don't cause a worse issue.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yup, there are a few .img files, including boot.img and splash.img. I have read that the EDL mode doesnt let me push the firmware, because that mode is only readable by qfil, but theres a supposed way to orded adb to work with EDL, so it wold detect the phone, and let me push the firmware, do you know something about that?

Nuxon_22 said:
Yup, there are a few .img files, including boot.img and splash.img. I have read that the EDL mode doesnt let me push the firmware, because that mode is only readable by qfil, but theres a supposed way to orded adb to work with EDL, so it wold detect the phone, and let me push the firmware, do you know something about that?
Click to expand...
Click to collapse
Unfortunately, no, I'm not familiar with that as I've never gotten myself in a mess with any of my devices, I'm too careful and dig absolutely every piece of information about a device and what I'm modifying before I ever take the first step. I also research every possible thing that could go wrong and how to correct it before I do anything.
It's not as simple as JUST looking for what is available or what can be done on a device, it's also about looking for things like stock firmware differences. Things can change from stock version to stock version, i.e. what can be done coming from "this" firmware can be different when coming from "that" firmware even on the same device. Also things like locked or unlocked bootloader can effect what can be modified and how to do it.
Sent from my SM-S903VL using Tapatalk

Oh, ok dude, thx

I have same issue. Is there any method to fix ?

I try too search full firmware and nothing, anyone can help with firmware? Anything that I found is just update rom that not have any loader or xml to can flash fully or fix the bootloader.

Xperia XA F3111 dead - red light on (not blinking)

hi, my rooted xperia xa f3111 does not turn on anymore - only the red light on (not blinking), tried another battery,tried to charge on pc and on wall charger too for long, pc doesnt recognise, tried all the button tricks but nothing.
any idea to bring it back to life?

Budaz187 said:
hi, my rooted xperia xa f3111 does not turn on anymore - only the red light on (not blinking), tried another battery,tried to charge on pc and on wall charger too for long, pc doesnt recognise, tried all the button tricks but nothing.
any idea to bring it back to life?
Click to expand...
Click to collapse
Only Sony service center can ressurect it by replacing the motherboard..
Sent from my Xperia XA using XDA Labs

aidy.lucas said:
Only Sony service center can ressurect it by replacing the motherboard..
Sent from my Xperia XA using XDA Labs
Click to expand...
Click to collapse
Yes..its true :good:

aidy.lucas said:
Only Sony service center can ressurect it by replacing the motherboard..
Sent from my Xperia XA using XDA Labs
Click to expand...
Click to collapse
i think i do not have warranty anymore after rooting and....etc
as i read it would cost a lot.
is it possible to recover data from 100% adopted microsd? ( google was not my friend )
/ i use windows 10 os /
thanks a lot for replies!
regards
mb

You can fix it via SP Flash tool
You need to get scatter file based firmware first then install VCOM usb driver and flash it via SP Flash tool.
Your sony xperia xa will back to life.

wrundawan said:
You need to get scatter file based firmware first then install VCOM usb driver and flash it via SP Flash tool.
Your sony xperia xa will back to life.
Click to expand...
Click to collapse
maybe im gonna get a working XA F3111 and im gonna try to create a scatter file.
does anyone going to need the scatter file?

Budaz187 said:
maybe im gonna get a working XA F3111 and im gonna try to create a scatter file.
does anyone going to need the scatter file?
Click to expand...
Click to collapse
Right now I need it, but it will work in a F3113?

Budaz187 said:
hi, my rooted xperia xa f3111 does not turn on anymore - only the red light on (not blinking), tried another battery,tried to charge on pc and on wall charger too for long, pc doesnt recognise, tried all the button tricks but nothing.
any idea to bring it back to life?
Click to expand...
Click to collapse
How did it happen?

ZalakVE said:
Right now I need it, but it will work in a F3113?
Click to expand...
Click to collapse
i dont know mate. im new in the android world.

Budaz187 said:
i dont know mate. im new in the android world.
Click to expand...
Click to collapse
Send it to me anyway please, I'm desperated

rrvuhpg said:
How did it happen?
Click to expand...
Click to collapse
i dont know exactly whats happened.
1 day my phone just got frozen and i could not turn it off or restart anymore and because straight after i started at my workplace and i used to use my phone for navigation i just connected to a brand new noname usb car charger with its original sony cable (it was the very first time to use this noname sh*t) and from the noname charger some smoke came out.....
-i really think that the motherboard is over cause this car charger so im not gonna be able to bring it back to life.
but some people have the same problem without using cheap charger and smoke so i wanna give a try with the scatter file.
how can i find out if the motherboard is working?

ZalakVE said:
Send it to me anyway please, I'm desperated
Click to expand...
Click to collapse
i will,
but i dont have much free time and its gonna be the first time for me to create a scatter.
and i still dont have that xperia in my hands....

Lot of people have bricked their Sony Xperia xa device and their is only way to fix this is to get scattered file based ROM and flash via sp tool.
For scattered file based ROM first need working device, then take backup of ROM through miracle box or any other in which you can create scattered file based ROM and then flash it on your bricked device via SP tool or similar.

wrundawan said:
Lot of people have bricked their Sony Xperia xa device and their is only way to fix this is to get scattered file based ROM and flash via sp tool.
For scattered file based ROM first need working device, then take backup of ROM through miracle box or any other in which you can create scattered file based ROM and then flash it on your bricked device via SP tool or similar.
Click to expand...
Click to collapse
yepp but many of them say also that their device is recognised as "vcom port" (or something like that) not?
how can i check if my device recognised like that? device manager? i dont see any changes during connecting/disconnecting in the device manager.

Need to install drives manually to get it detect as VCom device in device manager

wrundawan said:
Need to install drives manually to get it detect as VCom device in device manager
Click to expand...
Click to collapse
i did, i have the mediatek and mtk ports under the ports part in the device manager.
should i see any changes during connecting/disconnecting my xperia?
is it possible that my motherboard burnt but i still have the red light if its on charger?

Have you got scattered file based ROM from working Sony Xperia xa?
If yes then you should proceed with sp flash tool and flash it on your dead device.

wrundawan said:
Lot of people have bricked their Sony Xperia xa device and their is only way to fix this is to get scattered file based ROM and flash via sp tool.
For scattered file based ROM first need working device, then take backup of ROM through miracle box or any other in which you can create scattered file based ROM and then flash it on your bricked device via SP tool or similar.
Click to expand...
Click to collapse
No, no and no!! Don't claim that XA can be unbricked with a scatter file and SP flashtool or prove it! Show me a working scatter file for any XA or Ultra, show me that we can flash them with SP Flashtool.
Look at this links: http://forum.androidurdu.net/showthread.php?tid=1157 and http://forum.androidurdu.net/showthread.php?tid=943
It's you too??
You have successfully unbricked your device if you explain to Xda users how to do?? Can you release your scatter file?
You are giving fake hopes, and it's bad. (and make me very angry)

Not fake hopes. Sony Xperia xa is mtk6755. And can be fixed with sp tool.
If you have another way then explain here. If not then keep quite. As your making angry without any hopes and no help at all.

wrundawan said:
Not fake hopes. Sony Xperia xa is mtk6755. And can be fixed with sp tool.
If you have another way then explain here. If not then keep quite. As your making angry without any hopes and no help at all.
Click to expand...
Click to collapse
It's not because XA have an MT6755 that it works like any other MTK device and I know what I say (not you). I fully know how to unbrick a MTK device and Sony devices are an exception. Show me a working scatter file for a Sony device with SP Flashtool, the model you want!! Show me a Sony firmware ready for SP Flashtool!!
You speak like you knew it works and you did it but you are just an user with a bricked device, nothing more. You really think that nobody tried to extract a scatter file from Miracle box and use it with SP Flashtool? I repeat again, you are giving fake hopes!

Adb update! Plz help stuck in recovery! [Q&A],[SOFTBRICK/BOOTLOOP], QTAQZ3

Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat

samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
?
Click to expand...
Click to collapse
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk

SORRY
Droidriven said:
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3/4.2Jellybean/KTO49

samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse

samson716 said:
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse

ayu321 said:
samson716 said:
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
Stock
Click to expand...
Click to collapse

samson716 said:
ayu321 said:
Stock
Click to expand...
Click to collapse
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse

ayu321 said:
samson716 said:
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse

samson716 said:
ayu321 said:
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse

samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
Click to expand...
Click to collapse
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk

ayu321 said:
samson716 said:
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse

Your device probably uses SPFlashtool or fastboot.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a deuce exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .

ayu321 said:
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
Click to expand...
Click to collapse
To be compatible, the ROM typically has to be ported and that usually requires the stock firmware or stock source from the device that the ROM is being ported over to. 99% of the time you can't just flash a ROM from a different model number, even if the CPU is the same, there's quite a bit more to it than that. The android operating system is built for the specific hardware it is installed on, the two devices would have to be exactly the same and have the exact same components, any differences in hardware make he firmwares incompatible.
For this particular device, I doubt the stock firmware or stock source code area available, even if it were, porting another ROM wouldn't be necessary because if it were available it could just be flashed with that instead of porting a ROM.
About the only time a ROM from a different model number can be used without any porting or edits being made is when the devices are exactly the same device just rebranded with a different "name".
But thanks for trying to tell me something that you thought I didn't know, now it seems I've told you something that you didn't know.
Sent from my SM-S903VL using Tapatalk

samson716 said:
ayu321 said:
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse

ayu321 said:
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
Odin is for Samsung devices, not other devices.
The device they are repairing is not a Samsung device. They have this device and a Samsung device. The issue on this device occurred while they were in the process of flashing their Samsung device.
I know you're trying to help but don't post anything unless you are absolutely certain that you know what you're talking about.
In this case, you didn't and that can easily lead to a hard bricked device because they followed your instruction.
Stick to answering questions about devices you personally have dealt with, don't go assuming that you understand someone else's device. They are all different, the methods, tricks and tools for one won't necessarily work on another.
You understand android somewhat but judging by your posts, you don't understand the differences in devices and methods. But you will after you've been here a while.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
DO NOT USE ODIN ON YOUR DEVICE!!!
Odin is only for Samsung devices.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!

samson716 said:
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
Click to expand...
Click to collapse
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is there absolutely anything i can try, just a long shot in the dark?

samson716 said:
Is there absolutely anything i can try, just a long shot in the dark?
Click to expand...
Click to collapse
The only other option is pretty risky. You can try a firmware from another device that has the same CPU and hardware as your device, you'd have to compare specs. It would have to have the same CPU, same screen resolution, same camera(front and rear), same amount of RAM, same amount of internal storage, same accelerometers, etc.. It has to have all the same components that yours has.
Sent from my SM-S903VL using Tapatalk

oppo find x2 softbrick at qdloader 9008. how to

hello guys. When installing the rollback of android 10, the phone has been stuck in the installation. I cannot enter recovery, I can only turn off the phone and the pc detects it as qdloader 9008, I know that with qfil I can install the rom, but I cannot find the necessary files, the .mdn file of the cph2023 global version. somebody could help me? thank you

ferchu91 said:
hello guys. When installing the rollback of android 10, the phone has been stuck in the installation. I cannot enter recovery, I can only turn off the phone and the pc detects it as qdloader 9008, I know that with qfil I can install the rom, but I cannot find the necessary files, the .mdn file of the cph2023 global version. somebody could help me? thank you
Click to expand...
Click to collapse
I have exactly the same issue did you find a fix? or the .mdn at all?

DanTh0mas said:
I have exactly the same issue did you find a fix? or the .mdn at all?
Click to expand...
Click to collapse
Sorry for take a long time. I did not find the solution. luckily I work in an electronics store and gave it to one of our clients who repaired it.

DanTh0mas said:
I have exactly the same issue did you find a fix? or the .mdn at all?
Click to expand...
Click to collapse
I had a similar issue, got hold of some files and tried flashing with MSNDownloadTool and QFIL but kept getting errors (think the files may have been dodgy).
Sent back to Oppo and they repaired under warranty (even though mine was the Chinese version and I am in the UK and its a 2nd hand phone) - really good service from them.

klanbo78 said:
I had a similar issue, got hold of some files and tried flashing with MSNDownloadTool and QFIL but kept getting errors (think the files may have been dodgy).
Sent back to Oppo and they repaired under warranty (even though mine was the Chinese version and I am in the UK and its a 2nd hand phone) - really good service from them.
Click to expand...
Click to collapse
They didn't ask you for the purchase invoice?

Nope, I didn't have one and they didn't ask. I contacted through the Oppo Facebook page and they were really helpful.