Hey guys, tried install lineage os and have a brick now. No one able blankflash for our device? Or any idea :crying:
solved, just need to be more attentive. https://forum.xda-developers.com/one-power/how-to/bricked-device-doing-stupid-stock-rom-t3896721 comment by colorist. Only one detail remained, blankflash didn't work for me, so I held the phone's power button until the signal "device disconnected" appeared, after about one second a signal "device connected(windows signal)) will appear, and at this very moment it is necessary to run the script.
Related
Hi everyone,
I own a Motorola Moto G2 (XT1068, dual sim) that came used with Android 6.0 on it.
I installed TWRP (twrp-3.0.2-3-titan.img) on it but failed to root Android 6.0 as well as 5.0 for whatever not yet understood reason. I don't do Android development for a living but I'm an IT professional, so handling adb and fastboot as well as reading and understanding instructions isn't a problem.
I flashed stock Android 4.4.4 (RETDEALL_XT1068_4.4.4_KXB21.85-14) which I successfully rooted by installing SuperSU via TWRP.
Next I updated SuperSU, verified that root access is indeed working and installed FlashFire, which I hoped to use to install OS upgrades, possibly without losing root. FlashFire is new to me (as of yesterday), everything else mentioned up to here is not.
I used the "Flash ZIP or OTA" action from within FlashFire and the previously downloaded update file in the /cache directory. I can't reproduce the file name since the phone is currently unusable and I didn't write the file name down prior to using FlashFire.
The state of the phone after this unsuccessful attempt was that of a broken USB device, i.e. unable to even register as whatever type of USB device. I learned that this can be fixed by holding the power button down for more than one minute, after which I managed to
get the phone to be shown as working "RELINK HS-USB QDLoader 9008" USB serial device in Windows 7 device manager.
I used the information in these two threads:
http://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Since I started with Android 4.4.4 trying to upgrade to 5.0, I had hoped that the blank flash package for one of these Android versions would help fix my problem, but as of now, this doesn't seem to be the case. At the end of the blank flashing process, I get the message
FAILED <blank-flash:sdl-transfer-image:sdl-hello: error sending packet>
After that, the phone still has a black screen and cannot boot into anything. Repeating blank flash works after resetting whatever part of it is still working by holding the power button down for about 30+ seconds.
Is there anything obvious (or maybe even not so obvious) that I missed?
Thanks for reading and any help and/or pointers in the right direction.
hey , contact me on pm
salkollizz said:
hey , contact me on pm
Click to expand...
Click to collapse
Did you solved the problem of hard brick of Moto G 2014?
Okay,
I have just created this account to ask this even though being aware that the phone is outdated. What is the solution for a phone which can be reached (connected) via USB without a problem, variables can be read and apply fastboot commands.
After reading countless topics, trying many softwares, trying many different original RUUs (HTC__M27 region especially considered) (since android is not booting, impossible to enable usb debugging and of course not possible to try custom roms etc. At this point s-off is not possible either) watching many many videos and such i started to think the only solution to revive this phone might be nothing but replacing the mainboard on it.
I remove the battery for sometime and when i try to switch it on normally, it vibrates 7 times (very common problem for most cases) and stuck with HTC logo forever.
If i apply the volume down, power up combo, phone can enter into Hboot, Bootloader, Fastboot, Recovery, Simlock, Barcode, Factory Reset options. When i try Recovery, Factory Reset nothing happens always stuck on HTC logo forever.
Even with the original ROM for my region which is Turkey HTC__M27 i get Error 131 Customer ID error.
I want to ask the community is there any solution for this kind of a situation?
Please kindly inform if you have time.
Thanks.
Answer to my own problem.
Simply phone is dead because 99% the emmc is either damaged or needs to be reprogrammed.
If your phone is S-ON and you are trying to S-OFF it and if your phone is unable to boot into android os you can not s-off it. All S-OFF methods needs "USB debugging function enabled". Since no os to reach and modify settings, you can consider your phone is a dead one and not going to rise at all.
DeadPhoneRising said:
Okay,
I have just created this account to ask this even though being aware that the phone is outdated. What is the solution for a phone which can be reached (connected) via USB without a problem, variables can be read and apply fastboot commands.
After reading countless topics, trying many softwares, trying many different original RUUs (HTC__M27 region especially considered) (since android is not booting, impossible to enable usb debugging and of course not possible to try custom roms etc. At this point s-off is not possible either) watching many many videos and such i started to think the only solution to revive this phone might be nothing but replacing the mainboard on it.
I remove the battery for sometime and when i try to switch it on normally, it vibrates 7 times (very common problem for most cases) and stuck with HTC logo forever.
If i apply the volume down, power up combo, phone can enter into Hboot, Bootloader, Fastboot, Recovery, Simlock, Barcode, Factory Reset options. When i try Recovery, Factory Reset nothing happens always stuck on HTC logo forever.
Even with the original ROM for my region which is Turkey HTC__M27 i get Error 131 Customer ID error.
I want to ask the community is there any solution for this kind of a situation?
Please kindly inform if you have time.
Thanks.
Click to expand...
Click to collapse
Hello guys, I'll try to explain what happened giving just a few context that may help give me some right direction to recover the user data that were in the phone.
As this thread got longer than I expected, summarising:
Moto G XT1033 drained battery, got into bootloop, only fastboot was working, couldn't get into recovery mode ("boot up failed"). When I tried to replace battery, after power on it's now bricked (as "qhsusb_bulk" in PC). My main goal, save user data (whatsapp folder mainly), to flash and restore Android.
Whole situation detailed, what happened:
I have a Motorola Moto G 16GB Music Edition Dual SIM XT1033 (Music edition) 2014, sold in Brazil. It was working for all these years fine, avoided upgrading Android KitKat from 4.4 because it just worked fine. In past months I noticed the battery holding less and less charge, but as I intended to buy a new phone soon I didn't care.
Unfortunately, couple days ago I heard the sound of notification "low battery... powering off". Then I plugged the charger cable and waited some time, after that, I thought it would just boot up normally, it showed "M" loading screen, with the animation etc, but it went to black screen and loop to loading screen again and again.
I tried to hold power and volume down, it went to fastboot, and when I tried start "recovery mode" but it would just say "boot up failed".
I searched for threads and people who had issue like mine and in fact, I found someone who described exactly the same problem I had, user named @ravibhat here: https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
While he didn't say he was able to fully flash his smartphone and get it back working, he said he was able to recover all his user data. I was really trying to follow his steps to at least, recover all user data, BUT, before that, my Moto G got hard bricked.
As I have another Moto G XT 1033, the exact same model as this one, but with a working battery, I thought it would be plausible to replace the battery so I could have more safety when fixing the phone, but it didn't work as that. Instead, after I disconnect and reconnect the battery, the Moto G is now hard bricked, as it doesn't boot up anymore, not even holding power + volume buttons, holding for 60s or 120s, none, nada. Rarely, the LED light blink once, nothing more. I connected to PC and it recognized as "qhsusb_bulk", after disconnecting and connecting the phone back to Windows 7, it automatically tried to install drivers and now it would just show "Qualcomm HS-USB QDLoader...." in device manager .
Now I have two issues, first, make it come back to state where I could open fastboot. Second, try to dump/save all user data, to then make a total flash/factory reset to see if I can get it working again.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) and this (https://forum.xda-developers.com/moto-g/general/guidy-to-unbrick-hard-bricked-moto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
I don't want to just go and try a bunch of (possible danger) commands and guides without having some experienced people giving advices on how to perform actions, or even if it's possible to "make some backup" of current situation, "copying whole partition", etc, before installing and flashing anything.
Device INFO:
Android version was 4.4. No Root. Bootloader is LOCKED. No customizations.
ADB Debugging state is unknown, probably it was just the default value.
What I want:
I want to get a copy of all my internal storage data, eg: WhatsApp folder, etc. Better if I could get whole storage image and just flash OS and boot loader to get back as it was...
Trying to flash it in any way that causes data loss would be my last option, but @ravibhat who had same issue few years ago couldn't even get it back working again.
What @ravibhat found out:
He thought bootloader UNLOCK would wipe all internal memory user data, but he did it and still could get all files using TWRP 2.8.x.x.
"To root the phone, I’ll have to UNLOCK the Bootloader."
"ADB can be used to backup using PUSH, PULL (may or may not require Android USB Debugging enabled)": he couldn't get it to work using adb push/pull.
Please, I would really appreciate any help from anybody, also from following users @ravibhat , @lost101 , @Teddy Lo , @Kamin4ri , @oversleeper , @jdawc7 , @sd_shadow , @SahilTech , @liveroy , @bouba148 , @bejunk , @Wolfcity, @skad00sh, @FabioSan.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/mot...oto-g-t2833798) and this (https://forum.xda-developers.com/mot...oto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
Click to expand...
Click to collapse
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
oversleeper said:
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
Click to expand...
Click to collapse
Thanks @oversleeper, I was a bit afraid because of the "blank-flash.bat" name.. but as I don't know of any other method of beginning this recovery other than unbricking using this qboot bat script, I will end up giving it a chance.
As I said before, Windows 7 auto installed the "Qualcomm HS-USB QLoader 9008" driver as soon as it recognized the "qhsusb_bulk". Do you think I should try to uninstall it and start from step 1 on this guide (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) installing the "Riff BOX JTAG drivers + Driver Signature Enforcement Overrider"?
Yes, I suggest that you install the driver's as advised in that old thread. Also, you will need to use the right qboot utility, for the right model and version of the bootloader that you have or it won't work. Unfortunately I can't help with that, you will need to search the internet and may luck be with you.
Good day all. Long time lurker of these forums, and I am officially throwing in the towel on my amateur attempts to update my P20 Pro (CLT-L29 C636) from Android 8 to something newer. I've managed to soft brick the thing, getting stuck in a boot loop. I can get to fastboot, and I can (sometimes) get it to enter dload mode with an OTG cable and a thumb drive. I messed something up early on in the process and I am completely unable to go any further. Dload gets to 5% then fails every time, with every thumb drive I've used.
I am willing to accept that I just don't have the technical ability to take this journey any further. Being that I live in the US (Western New York), Huawei lists no official repair centers in the states. Are there any trusted 3rd party repair services I could send my phone to and have an expert attempt to repair the software? At this point it's been bootlooping so long the Huawei logo is ghosted onto the AMOLED screen. I would love to have this phone operational again.
Any thoughts I would greatly appreciate it!
Hold Both Vol + Power until Emergency Rescue pops up.
After that, restore Stock, unlock Bootloader, install any android 10/11/12 GSI u want.
Tried that. It's stuck in bootloop and only occasionally responds to boot prompts. On the couple of times it got past dload failed and prompted me with invalid install and offered to boot to Emergency Recovery, it fails to load the recovery dialog and drops back into a boot loop.
I promise, I have been back and forth with attempts on this phone for four months, and if I thought there was any new surface level tip or trick I haven't tried, I would still be searching. I feel like it's at a point where only specialized software or a physical test point, or something else beyond my technical ability will fix this phone.
I do appreciate the suggestion, though.
Unlocked Phone? So it *might* be possible to recover i imagine if u get twrp running, might need some dirty work, but not impossible.
Edith did forget to mention; Can u see ur Phone via adb/fastboot on your PC?
aLcaTr4z said:
Unlocked Phone? So it *might* be possible to recover i imagine if u get twrp running, might need some dirty work, but not impossible.
Edith did forget to mention; Can u see ur Phone via adb/fastboot on your PC?
Click to expand...
Click to collapse
Sorry if I sent the wrong impression. The bootloader is still locked. It is only carrier unlocked.
I can locate it on DC-Unlocker on fastboot but it won't let me load any files to it.
With locked BL is not much hope left i guess. Hisuite Recovery fails too i imagine?
aLcaTr4z said:
With locked BL is not much hope left i guess. Hisuite Recovery fails too i imagine?
Click to expand...
Click to collapse
Oh yeah. HiSuite recovery states that this model isn't compatible with eRecovery and to take the phone to a service center.
Well, i tried to flash a custom rom on my Moto g5s plus (XT1805 dual sim) i made a EFS backup through TWRP. At some point i got an error in the fastboot screen, something that says like "Startup failed", i fixed it with Lenovo RSA, then when i try to install the stock rom, with efs backup and everything, it doesn't have signal, and in the moto actions app doesn't appear the "one button navigation" option, then i installed different kernels to try to fix it, the thing is that it hardbricked, i don't remember exactly what i did to hardbrick because it was a couple months ago, but i'm pretty sure it was a custom kernel.
The phone was completely dead, except for a white led blinking when i connected it to my computer. Did a bit of research here on XDA and some forums, and found a "blankflash" file, it worked like magic and my phone was again alive, but without signal and moto fingerprint gestures option not appearing, everything else was fine, Wi-Fi, Bluetooth, Camera. Then i tried to flash again the kernel that hard bricked it, believing it would work this time, and big surprise, hard bricked again. I tried to fix it using the method that worked me in the past, but then the blankflash file was giving me an error, i tried to search another blankflash but no luck, no one was working. Then i found a reddit post and finally worked, alive again but in same conditions, no signal and moto actions not working.
I don't really know what is wrong with my phone, i'm believing that Lenovo RSA installed a wrong version of whatever it fixed. I'm on a dead end, and i cannot find more info about a similar problem anywhere, and Lenovo RSA now says something like "The model associated with the IMEI for your device is not currently supported by RSA."
I'm out of options, and my last chance is to ask here if someone can give me a hand.
Edit: I also tried fastboot erase abl and fastboot erase bootloader idk why, but it gives me an error like "Permission denied".
p.s that command deletes bootloader partition, high risk of hardbrick