I have mediapad s7-301u, its my customer fault he said that he tried upload custom rom and now devices wont boot up.
No fastboot no recovery mode.
My PC detected as storage 31.7Mb Free, and at Device manager, at Ports it said Qualcomm HS_USB Diagnostic 9006.
Tried alredy by putting SD card with Stockrom ( /dload at root ) it wont update.
how to revive this Mediapad ?
You need to have it replaced by Huawei. No other option is available, sorry.
mrgsm said:
I have mediapad s7-301u, its my customer fault he said that he tried upload custom rom and now devices wont boot up.
No fastboot no recovery mode.
My PC detected as storage 31.7Mb Free, and at Device manager, at Ports it said Qualcomm HS_USB Diagnostic 9006.
Tried alredy by putting SD card with Stockrom ( /dload at root ) it wont update.
how to revive this Mediapad ?
Click to expand...
Click to collapse
Have a look at the qualcom debrick for SHV-E160L device, it might be able to help bring this back from the brick state.
You will need some research first thought, like which qualcomm SOC is inside,
thread is in my sig.
darkspr1te
Related
Hey all,
I am looking for a working unbrick,img for a hard bricked G900v that currently doesnt go into recovery mode or download mode. Windows recognizes the device only as Qualcomm HS-USB QDLoader 9008.
I honestly dont remember what version BL or FM i flashed it with last and I have been searching for days online and through xda-dev for versions of unbrick images to mount onto my sd card to enable it to get to download mode so I can try and revive this device.
I have tried PD1, NCG, among the ones i remember, none of which have worked.
Can someone help?
I have a thl knight 2, I tried to flash twrp and it's stuck in a bootloop. I can't connect trough adb, fastboot but I saw some ports in device manager. I downloaded mediatek drivers. As far as I know when I connect the phone it should be detected by the droid tools or sp flash tool but it isn't. All the drivers pop up, I tried setting them to mediatek DA USB VCOM (Android), Mediatek USB VCOM (android) and Mediatek PreLoader USB VCOM (Android) but still it doesn't find the phone. I can't use recovery and can't enter fastboot. My volume up key used to lower the volume instead so maybe they are both mapped to volume down? I have a orange state message on the android logo about not trusting my phone. It would have been better to just let the chinese government get my personal information than trying to mess with forces I don't comprehend! If anyone reads this and is willing to help me I will be forever in your debt.
Maybe if I brick it altogether I will have more chance than it just getting to the android logo.
maduri said:
Maybe if I brick it altogether I will have more chance than it just getting to the android logo.
Click to expand...
Click to collapse
Where did you get the mentioned twrp recovery?
Hello everyone;
I was trying to load a CM recovery file on my cell by using SP Flash tools and somehow bricked my Acer Z410 phone (carrier: Fido, 2 sim card slot) I do not know why afterwards, the cell turns white with a yellow strip down the middle. I have been able to have my computer recognize it after numerous attempts to flash firmware versions that I was not quite sure was the original. I had tried your site to load the firmware that seem to correlate to my cell configurations, but all of the links are dead. I ended up flashing with SP Flash tools firware version AVOKO 1.015, but it still can't boot in to see anything on cell. So as of today, I got my computer to recognize the phone and I can actually see the files on my phone and sd card inside. How can I boot into this puppy? I have tried within ABS and the command function to view adb devices, but it does not show up? I get an error : device 0123456789ABCDEF Unauthorized. In my device manager it shows up as ACER phone , and under the Ports section it does show Mediatek Preloader USB VCOM driver (COM 5). I hope I have given enough information to start diagnosing the problem.
Any suggestions how to go about this problem from here?
breezin123
So i have my Moto G7 right here, and recently i tried to jailbreak it, which worked fine
i then tried to use Magisk to root, which resulted in an eternal bootloop
i tried to reflash stock onto it, still bootlooping
in feeble hope that the other boot slot had a boot partition that worked, i switched to slot B
now nothing is working, however, Windows detects the device, as "Qualcomm HS-USB QDLoader 9008 (COM4)"
how do i switch the boot slot back? ADB and Fastboot do not recognize the device, so DONT GIVE ME INTRUCTIONS FOR ADB OR FASTBOOT. just tell me how i swap bootslots without loading Fastboot
@CodeWritten
I think the device is unrecoverably bricked.
Would pulling the battery and lettings the cmos battery die not work then?
There has to be a way
CodeWritten said:
Would pulling the battery and lettings the cmos battery die not work then?
There has to be a way
Click to expand...
Click to collapse
What is the point of that? Forcibly emptying/cleaning the memory chip / CMOS chip does not help.
If you power on an Android device, the Bootloader ( comparable with BIOS/UEFI on computers ) gets startet which makes accessible the RAM-disk , loads the Linux kernel into RAM, and then starts the first process called init. This is also valid for A/B-ed Android systems.
To me it seems the Bootloader is broken because you obviously can't boot into Recovery.
According to a few things iv'e read, apparently if the device is recognized as it is now (Qualcomm HS-USB QDloader 9008) it is savable
EDIT: I need the .mbn file for Moto G7 XT1962-1
Hello, guys.
Recently, I've tried to root a Cubot Power 4G following a guide I found online. I probably should have been more catious about it, cause now the phone is stuck on a bootloop. I tried to install a custom recovery to try and fix this, but as there was no official twrp for Cubot, I once again downloaded something that was probably shady. Thus, now the phone is stuck on bootloop, won't access recovery mode, is now turned off because battery gave out, but if I try to connect it to the pc, it will start to bootloop again. I cannot access adb, or at the least I don't know a way to, since it keeps bootlooping and I have no way to access a recovery mode(since there's no one, or at the least, if there is, it's faulty). What can I do here?
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
jwoegerbauer said:
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
Click to expand...
Click to collapse
I did! Or so I think... The moment I connect it to the pc, it starts bootlooping and so the pc cannot actually connect there
Bootloop is a situation where you cannot get into the "normal" Android system. Take note that as soon Android logo is shown on phone's display Android kernel got successfully initialized, ADB & Fastboot are ready.