Related
One morning i restarted my phone( Moto G 2nd gen.) with Android Marshmallow because it went slow, but after that it restarted in fastboot mode when i pressed the power on button. Normal startup or recovery were also not working.
I checked this forum, then unlocked the bootloader and downgraded to Android 4.4.4 . My phone operated well, then at night it started asking for lollipop update again and again, i allowed for OTA update (that was my biggest mistake), and after downloading the data and during update, my phone went off and didn't start again.
Although the indicator light glows solid for sometime when connected to wall charger or to PC via USB cable.
I have tried blankflash, ADB and fastboot utility, Volume down + Power combination, pressing power button for over 120 seconds, but all in vain.....
Please suggest me a way to solve this problems, i have important data in my phone and i want to save those too.
Welcome to the hardbrick club ^^
They all did the same mistake like you did. When you go throught the motoG Threads you will see all did the same.
The only solution is a clean flash what is not given from motorola for moto g2. The only existing is for moto g what did not work for our phones
Feel blessed, you don't have to use moto g anymore.
Anniepoo said:
Welcome to the hardbrick club ^^
They all did the same mistake like you did. When you go throught the motoG Threads you will see all did the same.
The only solution is a clean flash what is not given from motorola for moto g2. The only existing is for moto g what did not work for our phones
Click to expand...
Click to collapse
I tried with blankflash which supports android 4.4 but not 5.0, so it must be a requiring MBM-CI 5.0 ? is it available or any expected month of arrival?
aninishu said:
I tried with blankflash which supports android 4.4 but not 5.0, so it must be a requiring MBM-CI 5.0 ? is it available or any expected month of arrival?
Click to expand...
Click to collapse
. I wish I could say it was, but unfortunately Motorola won't release this file. There have been some serious attempts to solve this problem but none have succeeded.. As far as I know the only way to fix this problem is by getting a new motherboard..
Hellow
friend, do not know if motorola and released this file, or if there are already solution ?, I appreciate your answer
Diego799 said:
friend, do not know if motorola and released this file, or if there are already solution ?, I appreciate your answer
Click to expand...
Click to collapse
no blankflash.zip for our model available
if you are from india then you can try out this solution for xt1068 by an guy mobile unbrick something contact him but remember it will be paid not free
Code:
https://www.youtube.com/watch?v=WynBaVyW0oU
if you from another region then need to wait for blank flash zip
There are some methods to extract the partition layouts...one can be using dd cloning & extracting img files...another can be through B2bSupportLg Tool, also calleld BoardDiag. It does have MSM8226 chipset option, but that device is W7 G2MDS. Take a working Moto G 2014 from someone, ask them to use this tool to extract the partition schemes, then you'll get .mbn files, especially prog_emmc_filehorse_msm8226.mbn . Use that to dump into the bricked device using either QFIL Tool or use this blankflash tool, replace it's singleimage files with the one you got, then execute blank-flash.bat.
Also I had some emmc prog firehorse files, all 4 related to 8x26...You can try those & confirm me if they work or not
help pls
i have nexus 6 and it just stuck on fastboot icant unlock bootloader and cant boot recovery i cant flash it even with rsd its not show as motorola device
just adb reinstalled the windows and just put driver for motorola and its read android again
tested the driver with moto e and its work
so how i can recover my device if i cant flash it :crying::crying::crying::crying:
Slow down...
Give some (as much as possible really) details as to what you've done to end up where you are.
Preferably in a normal non-centered text because what you've done there is hard on the eyes (read: annoying) and almost put me off answering...
Prince_Eugen said:
help pls
i have nexus 6 and it just stuck on fastboot icant unlock bootloader and cant boot recovery i cant flash it even with rsd its not show as motorola device
just adb reinstalled the windows and just put driver for motorola and its read android again
tested the driver with moto e and its work
so how i can recover my device if i cant flash it :crying::crying::crying::crying:
Click to expand...
Click to collapse
Well as you get the info ready, I will give you some advise. RSD is useless on the nexus 6. It is moto software for moto software and the nexus is is moto in name only.
Also the drivers for the moto E and nexus 6 might not be the same thing. Just because it is a moto doesnt mean anything.
zelendel said:
Well as you get the info ready, I will give you some advise. RSD is useless on the nexus 6. It is moto software for moto software and the nexus is is moto in name only.
Also the drivers for the moto E and nexus 6 might not be the same thing. Just because it is a moto doesnt mean anything.
Click to expand...
Click to collapse
ok thaks but what should i do now ?
Provide details. LOTS of them.
Basically, we need to know what you're attempting to do here.
Strephon Alkhalikoi said:
Provide details. LOTS of them.
Basically, we need to know what you're attempting to do here.
Click to expand...
Click to collapse
wake up found it stuck in bootloader i didnt do anything
i cant flash rom or do any thing
If you have no ROM, cannot enter recovery, and did nothing to bring this state of affairs about, your phone most likely has a dead EMMC storage chip. You can verify this by trying to flash a stock ROM using the fastboot command, but be aware that attempting to use that Lenovorola program you mentioned could have done significant damage to the device, as that program is not intended for this device.
Should we be able to confirm a dead EMMC chip, there's not that many options available. If you are still under manufacturer warranty you can send the device to Lenovorola for repair at no cost. Otherwise, you'd have to pay for the repair. You could instead purchase a replacement, or purchase a device with a broken screen and swap motherboards (and SIM trays).
I need help with my corrupted moto g7 bootloader. I need someone who has the file mmcblk0.img to help me, because it would be the only way to try to recover my moto g7.JA I tried several options here on the forum, but my case would be a little different, unlocking the bootloader then I tried to root and corrupted everything, I'm a little bad at it and ended up doing nonsense.Now my moto g7 doesn't turn on, there is no charging and nothing appears on the screen, it doesn't connect normal usb so qualcomm 9008, it doesn't run adb, it doesn't recognize rsd .. . Could someone please help me ... The only option I saw would be a mmcblk0 file for the moto g7 to try to boot from memory card, because it was the only way I haven't tried it and unfortunately with my smatphone without working I can't extract it mmcblk0.img. Wait with a good heart to help me?
How did you find the info about needing this file? I've been searching around for several years... (not for the phone or any Motorola phone I am referring to).
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.
Foreword: My time with Vivo has come to an end. After flashing a wrong devicecfg and accidentally rebooting my device it is now in a hard bricked state.
Vivo has locked down EDL, there is absolutely no way to flash or backup anything in EDL mode without the official Tools (namely Vivo AFTool 5.9.80).
Vivo India refers me to Vivo Germany - Vivo Germany has outsourced its customer support to bulgaria.
The people on the other side of the line know absolutely nothing about the technical aspect and refuse to put me through to anyone with any kind of knowhow.
Due to their anti consumer and anti repair attitudes I will not buy another Vivo phone.
With this out of the way: You might end up like me with a hard brick. Or without signal.
Even if this will not save you from a hard brick I can not stress this enough: Make a BACKUP! And backup your data. This will wipe your phone.
This process is IRREVERSIBLE unless you have a split ROM of the chinese Firmware or your own Backup.
THIS or BL UNLOCK will break your portrait mode. No more bokeh, neither in Origin OS nor FunTouch.
Do NOT flash fsg, modemst1 and modemst2. They are commented out in the COMMANDS file.
You do this at your own risk. As said before this might brick your device.
Unlock your Bootloader
Backup your Partitions
Download my Flash Folder and Extract it: Android File Host
Open 01COMMANDS.txt and read the instructions
Open a command shell in the same folder that you can find 01COMMANDS.txt in
Run the given commands in blocks or one after the other
If you do not have signal after flashing you might have to erase modemst1 and modemst2 partitions, so that they get replaced by the backup in fsg.
A magisk flashed boot.img and adb-modded recovery is included so you can flash it after booting up FunTouch once and backup all your partitions again.
Thanks again to @Pervokur for helping me along the way. There is definitely an easier method that involves less risky flash operations.
My phone died on the cross while I was trying to figure it out, so maybe someone else will pick up the torch.
I will not be able to offer any kind of support.
RIP @Killuminati91's Vivo, who died for the cause.
Sorry to hear that, man, you were so close to what looked like an easy switch between ROMs.
I know you said you were no developer but you are still a leap ahead of most of us here. Long do we miss the good old days where ROMs, kernels and pure innovation shortly followed our much-wanted phone when flashing a few ROMs a week was normal.
Thanks for all your help, perhaps one day there will be a way to recover your phone.
Many thanks, may I relock the bootloader when i finished change to Global rom?
amos0609 said:
Many thanks, may I relock the bootloader when i finished change to Global rom?
Click to expand...
Click to collapse
Same question
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
how did you relock the bootloader, does the portrait mode work again?
does any one change the origin os /ocean into funtouch?
version? how to relock after it can switch to funtouch?
by the way, I saw the post on the taiwan vivo phone of fb
the second hand goods, it wrote he change the origin os into funtouch
and he sell this service , it charge 2000 nt dollars in taiwan.
maybe someone can save your phone.
Killuminati91
I think the only problem that keeps the phone from being recognized as official FunTouch is dm-verity.
In theory both phone versions have the same exact hardware.
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
stevenkh168 said:
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
Click to expand...
Click to collapse
Message?
silence360 said:
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
Click to expand...
Click to collapse
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Killuminati91 said:
Message?
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Click to expand...
Click to collapse
did you try using the OriginOS's camera app on FuntouchOS ? I find it when u use the front facing camera, the portrait mode still work. In the other hand, the back camera is not working in portrait mode. I follow your guide and using the FuntouchOS about 2 days. Everything works fine, except the portrait mode and the AOD. Cant use it anymore.
Oh I see, now that is weird that the portrait mode is not working. So even if you switch not all functionality has returned. Thanks for the explanation. Hopefully someone can continue your work, and find a solution for a seamless transition.
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
hope to see some good news from you sir.
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
Update us...
have you been able to solve it?
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
NHQ Thang said:
how did you relock the bootloader, does the portrait mode work again?
Click to expand...
Click to collapse
same question
adkana4310 said:
Update us...
have you been able to solve it?
Click to expand...
Click to collapse
If u asking me so no im still on the same cant flash
redwatch99 said:
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Click to expand...
Click to collapse
Someone who can help me solve it ?