So I have 10 years of experience of rooting phones and flashing roms etc and I think this is the first time I really bricked my phone and until now did not find i solution my self.
So how got it bricked: I was on my work, in a bit of a hurry and wanted to update my phone (dirty flash) through TWRP but the installation hanged at the last 1% or such. I let it sit for 30 min. still hangs so decided to abort and do a clean flash but again the update hangs (maybe bad download?) but along the way (probably because I was at work and didn't take the time) I think I ****ed up switching partitions or something and now I have no OS installed on my.
I can boot in to Fastboot mode, TWRP EDL mode and such
But I can't flash an new OS through TWRP because it says the following: Unable to find Partition for path '/system_root' (will post screenshot when I get home from work )
I tried MSM tool but until now I could not get the tool to see my Phone so now I am calling for the help of the XDA Community!
So do you guys have any suggestions wich wil unbrick my phone?
Try running msm from different port on your pc. Preferably a 2.0 usb if you have. Many times makes a difference. Also make sure your adb drivers are updated to latest. Many threads around talk about it.
Extracted boot file from original oneplus rom, flashed that with fastboot and like magic my problem was solved
Related
DESPERATE FOR HELP!
I bought a LG G2 D802 after deciding that ~ thats the phone i needed and after i bought it of course it had the 4.4.2 when i really wanted the 4.2.2
The reception was horrible too in low signal zones i had 90% of time no signal so after studying a little i decided i would Root it & install a new Rom possibly a Tmobile Version so i could fix my reception with Wifi-calling. Rooting was straight forward and no problems but Twrp was horrible i tried different ways and i couldnt install a recovery that worked or opened. Before i started playing with Twrp i made a Back up of the stock just in case.
AS it was BOUND to happen ~ flash errors occurred when i installed autorec.apk and rebooted. After that all i get is:
Fastboot mode started
udc_start()
and when im connected by USB
-reset-
-portcharge-
fastboot: proccessing commands
Pretty popular on the forum. So i tried to keep my cool and went through all same cases> I tried to get Recovery ( never installed right so ) tried to fix it by a method someone shared on the forum ~ didnt work Fastboot would flash the new recovery but once i went through the reboot and factory settings would go back to same black screen with fastboot mode started. To make things worse my download mode pops out and stays half a sec before it goes to same Awful screen. Tried to fix download with Laf file ~ fastboot erase and flash new one for my version as suggested by another member who unbriked his LG G2 didnt work ~ same issue.
ADB doesnt recognize the device. I have installed all device software in the beginning when i was rooting and trying to install Twrp. its an LG G2 with no SD slot and not a removable battery. Im losing all hope i dont know what to do anymore. If you guys can help me would be a life saver im close to smashing it to pieces and go back to my old Blackberry~...~
:crying::crying::crying::crying::crying::crying::crying: Please help !
DflMaster said:
DESPERATE FOR HELP!
I bought a LG G2 D802 after deciding that ~ thats the phone i needed and after i bought it of course it had the 4.4.2 when i really wanted the 4.2.2
The reception was horrible too in low signal zones i had 90% of time no signal so after studying a little i decided i would Root it & install a new Rom possibly a Tmobile Version so i could fix my reception with Wifi-calling. Rooting was straight forward and no problems but Twrp was horrible i tried different ways and i couldnt install a recovery that worked or opened. Before i started playing with Twrp i made a Back up of the stock just in case.
AS it was BOUND to happen ~ flash errors occurred when i installed autorec.apk and rebooted. After that all i get is:
Fastboot mode started
udc_start()
and when im connected by USB
-reset-
-portcharge-
fastboot: proccessing commands
Pretty popular on the forum. So i tried to keep my cool and went through all same cases> I tried to get Recovery ( never installed right so ) tried to fix it by a method someone shared on the forum ~ didnt work Fastboot would flash the new recovery but once i went through the reboot and factory settings would go back to same black screen with fastboot mode started. To make things worse my download mode pops out and stays half a sec before it goes to same Awful screen. Tried to fix download with Laf file ~ fastboot erase and flash new one for my version as suggested by another member who unbriked his LG G2 didnt work ~ same issue.
ADB doesnt recognize the device. I have installed all device software in the beginning when i was rooting and trying to install Twrp. its an LG G2 with no SD slot and not a removable battery. Im losing all hope i dont know what to do anymore. If you guys can help me would be a life saver im close to smashing it to pieces and go back to my old Blackberry~...~
:crying::crying::crying::crying::crying::crying::crying: Please help !
Click to expand...
Click to collapse
is your fastboot working?? do you have proper drivers... please search for x64 drivers if you have 64 bit os... sometimes that help.. i can be simple driver problem.. i tried to read you post twice but couldn't understand moreover i am not familiar with specifically LG but still i have some experience in flashing samsung s devices and nexus
pushkardua said:
is your fastboot working?? do you have proper drivers... please search for x64 drivers if you have 64 bit os... sometimes that help.. i can be simple driver problem.. i tried to read you post twice but couldn't understand moreover i am not familiar with specifically LG but still i have some experience in flashing samsung s devices and nexus
Click to expand...
Click to collapse
I dont know! I can Erase and Flash .img files into the phone ~ by using CMD and the SDK but i dont seem to be able to flash a system.img the one i have is 3gb and says error allocating memory. I dont see my device on adb ~ and fastboot shows ? Fastboot as device. I went and installed Ubuntu into a Virtual drive to try to push files into phone so i could access download mode or recovery. No luck there i couldnt find the phone under devices either.
When i use CMD on the PC and flash recovery recovery.img or any other image command the phone displays the work being done. So i think i am connected to Fastboot.
Hello guys..
I really have a problem right now! I appreciate everyone who tries to help me. I´ll try to expain what exactly is my problem with my Mate8.
Also I´d like to apologize for mistakes of gramatics, because im acutally from Germany..
So, my phone was working right, and actually everything was okay. With time it got so slowly, because storage was full with datas and so on. I tried to clean up some things to get it again a bit faster and so on, but that did not make it (at all). Also windows wont recognize the phone anymore. When plug in the USB it didnt even asked for data, charging or photos.. also I had problems with charging, it took toooo long for a few %.
I was on "KANGVIP" Rom (as much I know i changed stock to this custom rom) https://forum.xda-developers.com/mate-8/development/rom-kangvip-slim-t3318572
Time passed untill 3 days I decided to flash a new rom normally, like put rom on sd card, wipe dalvic and cache, and so on. I wanted this rom; Lineage OS https://forum.xda-developers.com/mate-8/development/6-0-1-cyanogenmod-13-port-t3512985
But everything came up with different errors for different actions I did like this:
"cant mound sd card"
"cant mount inernal storage"
"cant mount data"
"cant format data"
"cant mount system"
"cant mount cache"
etc. etc...
I tried to change file system to EXT3. EXT4, EXT2, FAT, and so on, for Data and System. Nothing worked correctly (but I had still on some Filestystems instead of 0MB like 2700MB). Still not working correct... On TWRP.
Then I tried to update TWRP from 3.0.1 to 3.1 (new one released). Because I saw, more precisely, I heard that an update can fix this mount issues I had.
Said and done, I updated it and instead of 3.1 I had 3.0.2 (idk why but I didnt care). But still theese problems happend.
So then I saw in a Video on youtube (which I cant find anymore) that another recovery like CWM can fix this issues. So I downloaded CWM recovery.img and installed it with TWRP an rebooted to recovery again. And now I´m in a situation, in wich I dont know what to do.
Now the phone tries to start, but no OS installed.
Try to get into Recovery, but no recovery aviable exept eRecovery which is failing with data when trying to restore.
Problem is also that Fastboot and ADB is not working. Installed HiSuite, ADB drivers, Samsung drivers (though could help).
Tried Knife Italian, but no connection to pc..
Tried different cable, no luck.
Tried windows 7, 8.1, 10 Home and now im on Win 10 Pro 64x.
All I can do is to boot into Fastmode, but cant do anything. And when I try to boot the phone normally it stucks on "Your device is booting now..." because no OS...
PLEASE HELP ME GUYS! I REALLY NEED THAT PHONE :crying::crying::crying::crying::crying:
THANK YOU !!! :good:
Hallo,
If your phone is still recognized in fastboot mode, you can try following up my tutorial here » https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
I was experiencing the same problem. No OS, no recovery, no fastboot flash possibility, only fastboot booting. Keep in mind that you will need 15€ for this method to work but it is the only way to resurrect your device.
PM me if you need further assistance.
djmitza222 said:
Hallo,
If your phone is still recognized in fastboot mode, you can try following up my tutorial here » https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
I was experiencing the same problem. No OS, no recovery, no fastboot flash possibility, only fastboot booting. Keep in mind that you will need 15€ for this method to work but it is the only way to resurrect your device.
PM me if you need further assistance.
Click to expand...
Click to collapse
Thank you for the reply my friend.
The problem is, that it only boots in to fastbootmode, but any pc wont recognize it. I tried even with Mac...:crying:
Greetings
DC-Phoenix should recognize the fastboot brick state even if the device doesn't show up in Minimal ADB & Fastboot. Try my method and let me know if it works.
Hi guy's.
DC Phoenix save my mate 8 with factory firmware.
I was the same problem like you and search one week a solution and after I decided to pay and try Phoenix and now I write from my mate 8
Before buy 15€ of credit you can download and try to connect your phone on DC Phoenix
does the DC phoenix method take your phone to absolute stock? ie, stock firmware +recovery + Locked + no root?
Yes. You will have the factory firmware (stock) but with unlocked bootloader.
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
It doesn't turn on, can't be hard-reset, can't go to recovery/fastboot, only EDL mode via test points. Last time (April 2019) it also happened overnight, but I was able to restore it to proper function by EDL flashing it using QFIL and a modified programmer (prog_emmc_firehose_Sdm660_ddr.mbn). The rom I flashed back then was the most recent at the time, Redmi Note 6 Pro Global V10.3.2.0.
This time was a bit different in that I was actually able to hard-reset it at first (it vibrated and seemed to boot), but it then got stuck on the mi-logo during startup. I wasn't able to get it into recovery, but the fastboot screen came on ok. However, the phone didn't register on the pc and I wasn't able to actually send any fastboot commands to the phone, nor flash roms. I don't think fastboot was actually working which might be pointing to chip issues... Unfortunately...
After a few attempts at hard-resetting and failing recovery, I think the battery actually ran flat. Now it is dead-dead. Doesn't react at all, doesn't do anything, just like back in April last year. When I plug it in to my pc it delays for about 10 seconds and then shows up as if it's in EDL mode (Qualcomm HS-USB QDLoader 9008) but it's not really flashable - it doesn't react to QFIL correctly.
I then pulled the phone apart, shorted the EDL points and got it into 9008 mode immediately after plugging in the usb cable, no 10 sec delay doing it this way. However, when trying to flash the phone now it fails and reports a generic 'Firehose FHLoader error'... Please see log attached in this google drive link: drive.google[dot]com/file/d/1nj_0f95qLnLHqIgTEODmilY9ObmAkowz/view
Apologies for the link - I don't have 10 posts yet...
The most recent miui rom for the phone now is "tulip_global_images_V11.0.4.0.PEKMIXM_20200514.0000.00_9.0_global" and that's the one I primarily tried flashing. I also tried the one I had success with last year (fearing though it might re-brick due to the roll-back protection) but that didn't work either, same error. I also tried flashing using different USB cables, all high quality, but the error remains. I also tried it using a laptop, just to rule out windows issues. I've also tried the tips for resolving QFIL errors mentioned on the hovatek forum: forum.hovatek[dot]com/thread-30141.html but with no luck there either.
Have you guys got any ideas how I might proceed? Any tips I could try?
I am kind of resigned to this perhaps being a hardware issue, perhaps this particular chip has failed and that is why not even EDL mode is working properly. But I just wanted to ask the community if you had any ideas. If not, then it's not an expensive phone. However, I would love fixing it if I could, my wife loves it...
I suggest to first short the pins then open the flash tool and try to flash the factory rom. The programmer file will be inside the extracted rom directory, select that and proceed. If it does not work try installing Qualcomm driver and retry .
Talix said:
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
Click to expand...
Click to collapse
I'm sorry for re-opening an old thread, but I'm in a really similar situation.
My Redmi self-bricked, and I don't have any ideas since I have already tried a flash in ELD mode but the Flash Tool says that it's not able to receive the hello packet from the phone.
Have you been able to solve the issue in some ways?
Ps. Here's my post, in case you need further informations
Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.
I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.
.
zeroiron said:
Hey guys!
i'm a bloody noob.
i never did something like unbricking my phone or wiping it or flashing it. It was my first time doing something like this because i just hate stock roms nowadays.
to unlocking the bootloader on my phone was no problem. but the problem was, that i updated my phone to adroid 11 and all the files i found in the past (half year ago) was for android 10, i think.
BUT I DIDN'T KNEW THAT BEFORE! I didn't knew that it would cause problems or that i had to be cautions about that.
Whatever. I tried to follow the instructions on this site: https://wiki.lineageos.org/devices/guacamole/upgrade
the twrp site i used was: https://eu.dl.twrp.me/guacamole/
Is the data "https://eu.dl.twrp.me/guacamole/twrp-3.6.0_11-0-guacamole.img.html" from 2021-11-22 know for adroid 11?
Because half year ago, i think, this all didn't work because there was no twrp for adroid 11 outside.
to be honest i don't know if i tried to install something else too in the past. i don't remember anymore.
I stuck half year ago on this bootloop problem. and i didn't worked again on this phone. i thought i could just wait for a new data for android 11 and try it later again.
Later is today but i made i worse!
I downloaded from this site https://download.lineageos.org/guacamole the file:
lineage-18.1-20220227-recovery-guacamole.img
after the command 'fastboot flash boot xxx.img' i reboot my phone.
Now my phone is displaying :
qualcomm crashdump mode
dm-verity device corrupted force dump
kernel-restart
what can i do now?
If i press the sound buttons + off-button i come the the boot screen which says:
blablabla
internetsite
press power button to pause boot
but this display won't stay long enough. after few seconds it's again on this crashdump mode
edit: i think i wiped in the past the whole os. And now? What should i do?
On this MSM Tool my phone isn't recognized. even with newest driver or other cable.
What should i do know? Is my phone lost now?
If some can help me please write exactly down what i should click / download etc.
If someone can german here and knows help, please help me in german. but don't have to. i'm glad if anyone can help me.
Click to expand...
Click to collapse
From what I can gather from your details I would try to get the MSM tool to work, it sounds like a driver issue, just make sure you uninstall previous driver first then go here
https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/
and get latest driver , follow all instructions,, also make sure your PC is installing all the optional drivers in the windows update section while your phone is connected to the PC, hth,, good luck