Hey guys, I've got a T-mobile v10 (H90120j) on 6.0 and on the most recent update as of 8/22. I tried to root via the LG UP method, but something went pretty wrong pretty quickly(I'm sure I mis-interpereted a step or made some similar rookie mistake). I'm in a boot loop of the "Your device software cannot be checked for corruption" no matter what I try to do. Luckily TWRP installed, but when I tried to reboot to finish the LG UP method it told me there's no system. When I connect it to my computer it shows as v10, but only the TWRP folder is visible on it. I was trying to find just a stock rom zip, but the ones I can seem to find are the ones that use LG UP using tot files, but I can't get the phone to go into download mode. Then I found stuff for the h90120e, which evidently hard bricks the phone. Does anyone on here know anything about this? Its not fully bricked but since it wouldn't mount the system properly, I wiped everything and repaired the system files on TWRP so I'm on a totally clean slate now. ANY help is greatly appreciated
**UPDATE** Tried installing Bliss rom, and had no errors, same with gapps. I'm still stuck in this boot loop though; I cant get past the "your device software cannot be be checked for corruption" screen
http://forum.xda-developers.com/showthread.php?t=3440359
Was this thread ever resolved for you k.wise, having the exact same issue just about with my v10.
The problem at least for me is the system partition of memory isnt even mounting and in turn is throwing error 7 and not allowing anything to be installed or read on it.
First of all, I want to apologize if I put this question in a wrong section or place. I'm a newbie around here at XDA and been following this since my eyes were opened for android stuff. I'M JUST REALLY SEEKING HELP. :crying:
It's been 6 months since I hardbricked my Huawei Y6. I only used it for two weeks but when I messed it up, it's been dead ever since. I have searched almost every corner of Google and XDA for a solution but none of them ever came up with one that is successful. I tried to recover it and sht to no avail. It's a Snapdragon 210 (MSM8909) btw, and Qualcomm. Used lots of things like QPST, EMMC DL tool, and whatever those other things are but here's really my problem..
Huawei Y6 has no firmware available online. If there is, only that ****ty UPDATE.APP. I did extract it and I don't know what to do with these files. There's no PROG_EMMC_FIREHOSE_8909.MBN, the PATCH0, and that other one which are what I am supposed to be using with QFIL. Anyway, NO DOWNLOAD MODE, NO RECOVERY MODE, NO FASTBOOT, and completely dead. I did something terrible internally to the device, I know.. messed up the partition table. I did bring it to lots of technicians around here and to the service center but all of them declined and denied me saying that it's dead and must be replaced. But if plugged in to a computer, LED will slowly blink Red. And.. it's detected as Qualcomm HS-USB QDLoader 9008.
Please help me.. 6 months = no phone = DEAD. </3 I know that this phone is not that popular because there's not that much things about this online. I really want to have this fixed.. I'm willing to do everything possible in return. Just help me. This is last resort and my only hope. HELP MEEEE. Thank you, XDA.
Update.. I somehow did something nice to it. It now can access fastboot but do not boot.
I got it in progress. Flashed system.img, boot.img, recovery.img, through fastboot flash and erased userdata and cache. If I turn it on, will just vibrate once. Can't enter recovery nor normal boot. But if plugged in, will be detected as Android Bootloader Interface. HELLLPPPPP!!!
And now.. it got even weirder. I flashed all its stock rom files (those that were extracted from UPDATE.APP) and now when booted, LED goes to RED-GREEN-BLUE cycle. What the heck is going on with this phone? It doesn't vibrate anymore and still can't go to recovery.
i also have this phone in same 9008 port condition , is there any solution to revive this ?
how to get the files to flash with QFIL ?
dear all
did you find the solution ??
Hello everyone.
First of all i was on the beta program for android 10 until like Q4 but since i was't able to play DFFOO i decided to downgrade the OS back to the last official build, and that was the android 9 june/july build.
I followed everything on the essential website in order to downgrade and i got it right, sort of. Everything was working fine except for the fact that the phone just wouldn't update at all. it'd just throw me an error, not big deal i though, until android 10 came out and since i wasn't getting it on my phone on it's own i decided to sideload it and here we are
I also folllowed everyhting on the Essential's website except for the fact of using the last Pie build i thought it was not big deal (idk if that mattered) so everything went fine until the installation reached 94% and then it said: Installation complete (i thought it was weird but not much else) next thing i do is select reboot now and boom.
All i get now is the sound of windows if i connect it to my computer and the "Qualcomm HS-USB QDloader 9008" under the ports section in device manager, no ammount of holding and pressing buttons will make it come back to life, so i come here for help, worst case scenario i'll have to buy a new one (they're pretty cheap second hand)
Hello,
The last week or so I have been trying to flash TWRP onto my Samsung Galaxy A40 (SM-A405FN) to install LineageOS. However, as I started following different guides and methods I have run into several problems that I can't get around and I was wondering if anyone here has had a similar experience or knows the solution.
The first problem I ran into was that when trying to flash onto the phone, neither ADB nor Fastboot detected the phone in download mode (when it was turned on normally they did). I tried various things to solve it: uninstalling and reinstalling different drivers, trying to find the device in device manager (it wasn't there) and nothing worked. I got around it, however, using Odin to flash. Odin did recognize the phone. I had already unlocked the bootloader and made sure VaultKeeper didn't lock it again. I believe it is fully unlocked now, I have even waited the week period to remove the RMM thing (I'm not entirely sure what it is and if I've done it properly, it's been a while since I've messed with android, but it used to display "KG state: checking" and now it's gone).
So, with Odin recognizing the phone I tried to flash the official TWRP recovery for it, following the instructions on the website. However, after flashing it, the phone bricks and boots into download mode all the time, with the error "Error validating footer (6)" on the top left corner. I have googled far and wide and the only solution I find is to reflash the stock ROM. Of course, this works, but I would like to be able to install LineageOS on the phone.
Thank you for in advance and let me know if you need more information or pictures of some sort.
Bump
Hello,
You can try the tuto on the following link:
It's for samsung A20, but you can apply the same practice for the samsung A40.
The first part of this tuto is woking for me (TWRP) but not the last one: "Rmm bypass"
Best regard's, Gregory
Hello
Let me preface this by saying: I'm not experienced in the world of rom flashing. I know very little.
I flashed my OnePlus Nord N10 5G with Lineage OS a few months ago, it was working fine until yesterday, when it got stuck in an infinite bootloop.
Whenever I start the phone, it shows the unlocked bootloader warning, then hangs infinitely on the Lineage boot animation.
I have tried multiple unbricking tutorials from this forum, and other websites. Nothing is working, because I don't think I had USB debugging enabled. My PC won't detect the Nord as a phone, so ADB and MSM won't recognize a device. Because of this I can't use ADB or MSM to install TWRP or flash a new image. I can get into Fastboot on the phone, that's all I can do.
Is there anything I can do to flash a stock rom, or any other way to restore factory settings? I don't need to save any of the data.
Thanks!
Well... if you can get to fastboot, you aren't bricked. EDL mode will let you flash a factory image over... the problem is that 100% kills anything you had on the phone.
If something "hangs infinitely", it might be possible it boots far enough to bring up ADB- meaning you could use logcat to see if there is something obvious with the startup that you might be able to fix.
I'm not familiar enough with Lineage to know how to recover it 100%... but based on the thread in XDA on this (e.g. the unofficial Lineage port) you start with flashing the Lineage recovery from fastboot. Does that not work? What fails? Most recoveries (e.g. TWRP) will unencrypt partions so you can at least copy them to SDCard and get your data off. Some of them will allow the phone side of ADB to boot, so you could do it with ADB PULL from 'puter side, too.
If you are indeed a n00b, make sure you learn the A/B thing- I can't do it justice here, but it WILL mess you up for reasons you won't understand until you've fought it many times (e.g. flash a recovery, but it does nothing because it is booting A and you flashed B).
After you have all your data off, I wouldn't bother trying to recover unless you are really bored... just EDL it to factory, then start anew if you want to go back to a custom ROM. FWIW, I found debloating and degoogling easier for me on this phone than trying to get everything else working. I am working now on CalyxOS on a Pixel 5G since it has all the proprietary blobs available to make all the hardware work, with a from-source-compiled-OS with re-lockable bootloader (when boot integrity works FOR you, it is a beautiful thing). Calyx is starting to futz with OnePlus phones, but they don't have a N10 image last I checked so I can't endorse it here... yet.
SomeRandomGuy said:
Well... if you can get to fastboot, you aren't bricked. EDL mode will let you flash a factory image over... the problem is that 100% kills anything you had on the phone.
If something "hangs infinitely", it might be possible it boots far enough to bring up ADB- meaning you could use logcat to see if there is something obvious with the startup that you might be able to fix.
I'm not familiar enough with Lineage to know how to recover it 100%... but based on the thread in XDA on this (e.g. the unofficial Lineage port) you start with flashing the Lineage recovery from fastboot. Does that not work? What fails? Most recoveries (e.g. TWRP) will unencrypt partions so you can at least copy them to SDCard and get your data off. Some of them will allow the phone side of ADB to boot, so you could do it with ADB PULL from 'puter side, too.
If you are indeed a n00b, make sure you learn the A/B thing- I can't do it justice here, but it WILL mess you up for reasons you won't understand until you've fought it many times (e.g. flash a recovery, but it does nothing because it is booting A and you flashed B).
After you have all your data off, I wouldn't bother trying to recover unless you are really bored... just EDL it to factory, then start anew if you want to go back to a custom ROM. FWIW, I found debloating and degoogling easier for me on this phone than trying to get everything else working. I am working now on CalyxOS on a Pixel 5G since it has all the proprietary blobs available to make all the hardware work, with a from-source-compiled-OS with re-lockable bootloader (when boot integrity works FOR you, it is a beautiful thing). Calyx is starting to futz with OnePlus phones, but they don't have a N10 image last I checked so I can't endorse it here... yet.
Click to expand...
Click to collapse
I'm fine with killing anything on the phone, nothing important on there. I've tried getting into EDL mode and using MSM Tool, but MSM doesn't see the phone when it's plugged in
When I try adb and enter "adb devices" in cmd prompt, no devices are listed. I also tried fastboot recovery via cmd prompt but after entering the command, it returns "<waiting for device>", so it's not seeing the phone either.
All I want to do is flash a factory image over, but I have no clue how to do that when the phone isn't being detected by any Windows program that can flash..
Thanks for your quick response, it would be incredible if you could help me sort this out!
Ok, so I assume you've read about the MSM tool here and maybe elsewhere, too, about 30 times? (Not being condescending, that's what it took me to get all of it, and I've been doing this for quite a while...).
My takeaways as I remember them:
- You need Windows. Yuck. If you are another OS, Virtualization is your friend, but make sure your USB passes through; in Linux that means some security adjustments.
- There is a SPECIAL qualcomm driver needed for Windows to see the EDL mode. This is hard to make sure you have installed correctly, but trips a lot of people- it is different than the phone/fastboot/ADB ones.
- The boot [physical] key combination only works for like 3 seconds or so to go to EDL - otherwise it will try to boot normally. That means get everything perfect, MSM running, mouse over "begin" (or whatever it is called), before you hold the keys and plug in the cable. Watch for it to appear, then quickly start once it is seen. Don't drop the keys until it says beginning firehose something or other. At that point sit back and relax.
- Make sure if you are loading a Win10 VM for this you cut it off the internet. Your friends in Redmond may try to auto-update including rebooting you in the middle of the download, which will not work out well for you.
If something goes south be specific, and I will try to help. Just remember, it is nearly impossible to brick a OnePlus due to EDL, so take your time and it will work
Oh yeah, while this is probably obvious, lemme say it for the record: (1) MSM puts it back to literal factory, so you have to re-unlock bootloader all over again to begin the quest of root/customization (2) this will absolutely wipe anything on the device data wise. SD cards are your friend.
SomeRandomGuy said:
Ok, so I assume you've read about the MSM tool here and maybe elsewhere, too, about 30 times? (Not being condescending, that's what it took me to get all of it, and I've been doing this for quite a while...).
My takeaways as I remember them:
- You need Windows. Yuck. If you are another OS, Virtualization is your friend, but make sure your USB passes through; in Linux that means some security adjustments.
- There is a SPECIAL qualcomm driver needed for Windows to see the EDL mode. This is hard to make sure you have installed correctly, but trips a lot of people- it is different than the phone/fastboot/ADB ones.
- The boot [physical] key combination only works for like 3 seconds or so to go to EDL - otherwise it will try to boot normally. That means get everything perfect, MSM running, mouse over "begin" (or whatever it is called), before you hold the keys and plug in the cable. Watch for it to appear, then quickly start once it is seen. Don't drop the keys until it says beginning firehose something or other. At that point sit back and relax.
- Make sure if you are loading a Win10 VM for this you cut it off the internet. Your friends in Redmond may try to auto-update including rebooting you in the middle of the download, which will not work out well for you.
If something goes south be specific, and I will try to help. Just remember, it is nearly impossible to brick a OnePlus due to EDL, so take your time and it will work
Click to expand...
Click to collapse
I was able to fix the issue by booting into EDL mode correctly, thank you so much for your help!
Glad to hear. Like I said, it took me many times reading over and over again, along with trial and error, before I made it happen the first time. But now that you're past it, have no more fear, flash away!
If something wasn't obvious to you, add a response to this or the OP article with your insight. It may help for many generations of phones to come.