Related
Hi all,
I installed the TWRP recovery for my mate 7 - 09 version, with lollipop 5.1. But then I unknowingly wiped something I shouldn't have: I think it was the system folder. No backups were made
My phone keeps starting up to the huawei logo and then reboots\turns off. I can get into fastboot&rescue mode, but that's it. No recovery, no 3-button fix (as far as I know).
The second problem is that I cannot get my device to be recognised by my pc. adb devices doesn't give me any results.
I don't feel like I can install the drivers properly as well. Pherhaps thats the problem? How can I do this? I have a driversetup from a mate7 download, but double clicking it doesnt show any prompts.
Anyone who can help me in any way is more than welcome!
dekraan said:
Hi all,
I installed the TWRP recovery for my mate 7 - 09 version, with lollipop 5.1. But then I unknowingly wiped something I shouldn't have: I think it was the system folder. No backups were made
My phone keeps starting up to the huawei logo and then reboots\turns off. I can get into fastboot&rescue mode, but that's it. No recovery, no 3-button fix (as far as I know).
The second problem is that I cannot get my device to be recognised by my pc. adb devices doesn't give me any results.
I don't feel like I can install the drivers properly as well. Pherhaps thats the problem? How can I do this? I have a driversetup from a mate7 download, but double clicking it doesnt show any prompts.
Anyone who can help me in any way is more than welcome!
Click to expand...
Click to collapse
Hey Buddy, here's what you can try to do:
1.) Boot connect your phone to your computer.
2.) Next, boot your phone to fastboot.
3.) Next, open command prompt from the folder where your ADB files are stored.
4.)On CMD type:
fastboot devices
5.) If your device appears then you have 2 options now. You can either:
a.) Flash Stock recovery.img or
b.) Flash back TWRP
6.) If choosing option a.) you can then save stock firmware within dload folder on your external sd card then force upgrade via 3 btn method.
7.) If choosing option b.) you can boot to twrp then either sideload a custom rom or try to save on your external sd and flash
blitzkriegger said:
Hey Buddy, here's what you can try to do:
1.) Boot connect your phone to your computer.
2.) Next, boot your phone to fastboot.
3.) Next, open command prompt from the folder where your ADB files are stored.
4.)On CMD type:
fastboot devices
5.) If your device appears then you have 2 options now. You can either:
a.) Flash Stock recovery.img or
b.) Flash back TWRP
6.) If choosing option a.) you can then save stock firmware within dload folder on your external sd card then force upgrade via 3 btn method.
7.) If choosing option b.) you can boot to twrp then either sideload a custom rom or try to save on your external sd and flash
Click to expand...
Click to collapse
I'll give that a try, thank you. With step 1, you just mean: connect the phone through usb to the computer, right?
When I rooted the phone, I did so on my work laptop, so I am hoping I can get it recognised there, but lets see what happens at home.
EDIT:
Ok, i've typed in fastboot devices, and it gave me one line with a 16-digit code (numbers and letters) some white space and then the word fastboot. What does that mean?
That should meen it recognizes your phone in fastboot mode. Next step is to flash as stated in step 5 that in the instructions.
Sent from my HUAWEI MT7-L09 using Tapatalk
dekraan said:
I'll give that a try, thank you. With step 1, you just mean: connect the phone through usb to the computer, right?
When I rooted the phone, I did so on my work laptop, so I am hoping I can get it recognised there, but lets see what happens at home.
EDIT:
Ok, i've typed in fastboot devices, and it gave me one line with a 16-digit code (numbers and letters) some white space and then the word fastboot. What does that mean?
Click to expand...
Click to collapse
EDIT AGAIN:
Ok, this is what I did. I downloaded the well known mate7 package, extracted the b119 tools folder and I put the twrp_2.8.7.0_mate7_5.1.img file from this forum (the TWRP for 5.1) inside this folder.
Then, I open cmd inside the folder, and I typed: fastboot flash recovery twrp_2.8.7.0_mate7_5.1.img. This is what happens:
target reported max download size of 471859200 bytes
sending 'recovery'(12644 KB)...
OKAY [ 1.302s]
writing 'recovery'...
OKAY [ 0.455s]
finished. total time: 1.756s
Now, I finally managed to get back into TWRP! I've only got 2% battery though (but I see a + which I think means charging...EDIT: yes, it is on 3% now. Better leave it like this...).
It tells me this:
TWRP has detected an unmodified system partition.
TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock rom from replacing TWRP and will not offer to root your device. Installing zips or performing adb operations may still modify the system partition.
I decided to swipe, to allow modifications.
So, I've got twrp back! For lollipop. This probably means I have to flash the lollipop rom? I will download the update.zip file next and put it on my sd card (using my pc and a microsd adapter...)
Keep you posted!
Ok, this is not working.
I put update.zip on my sd-card, and tried to install it. This is what I get:
Installing 'sd-ext/update.zip'...
checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:unknown command [errno]
file_getprop: failed to stat
E: error executing updater binary in zup 'sd-ext/update.zip'
Error flashing zip 'sd-ext/update.zip'...
Updating partition details...
...done
EDIT:
I tried to sideload but on my pc I get:
error: protocol fault (no status)
And on my TWRP I get:
You need adb 1.0.32 or newer to sideload to this device.
EDIT:
Updated my adb to 1.0.32 for windows, and rebooted everything. Now i'm at 6% of sideload. Hoping this will work!
EDITn the PC everything seems to go ok, but on my phone it says: E:Zip signature verification failed:1
What should I try next?
dekraan said:
Ok, this is not working.
I put update.zip on my sd-card, and tried to install it. This is what I get:
Installing 'sd-ext/update.zip'...
checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:unknown command [errno]
file_getprop: failed to stat
E: error executing updater binary in zup 'sd-ext/update.zip'
Error flashing zip 'sd-ext/update.zip'...
Updating partition details...
...done
EDIT:
I tried to sideload but on my pc I get:
error: protocol fault (no status)
And on my TWRP I get:
You need adb 1.0.32 or newer to sideload to this device.
EDIT:
Updated my adb to 1.0.32 for windows, and rebooted everything. Now i'm at 6% of sideload. Hoping this will work!
EDITn the PC everything seems to go ok, but on my phone it says: E:Zip signature verification failed:1
What should I try next?
Click to expand...
Click to collapse
I don't advise you to flash lollipop firmware first. It's more prudent to go back to kitkat first as I believe Lollipop needs kitkat as base
1.) Put stock kitkat update.app on dload folder of your memory card. Also make sure you have the LO9 stock kitkat recovery.
2.) With your phone connected to pc, go to twrp and reboot to bootloader.
3.) Once on bootloader open cmd on your tools folder then fastboot flash the stock kitkat recovery.
4.) Once done, fastboot reboot then force upgrade to install stock firmware.
5.) Once you have stock kitkat follow the drill to reach lollipop
blitzkriegger said:
I don't advise you to flash lollipop firmware first. It's more prudent to go back to kitkat first as I believe Lollipop needs kitkat as base
1.) Put stock kitkat update.app on dload folder of your memory card. Also make sure you have the LO9 stock kitkat recovery.
2.) With your phone connected to pc, go to twrp and reboot to bootloader.
3.) Once on bootloader open cmd on your tools folder then fastboot flash the stock kitkat recovery.
4.) Once done, fastboot reboot then force upgrade to install stock firmware.
5.) Once you have stock kitkat follow the drill to reach lollipop
Click to expand...
Click to collapse
Hi, thank you for your advice. I have but one question remaining: what stock kitkat update should I use? And where can I find the right recovery that goes with it?
I've tried several recovery_stock.img I found, and it does take away TWRP, so it might have done the trick. Only problem is that I cannot force upgrade to install whats on my sd-card....The phone keeps turning on (after a long push) and after seeing the logo for a little while, it turns off (short vibration)... Is there another way?
dekraan said:
Hi, thank you for your advice. I have but one question remaining: what stock kitkat update should I use? And where can I find the right recovery that goes with it?
I've tried several recovery_stock.img I found, and it does take away TWRP, so it might have done the trick. Only problem is that I cannot force upgrade to install whats on my sd-card....The phone keeps turning on (after a long push) and after seeing the logo for a little while, it turns off (short vibration)... Is there another way?
Click to expand...
Click to collapse
You should flash B137SP03 firmware. You can also refer to this guide:
http://forum.xda-developers.com/mate-7/help/5-1-to-4-4-2-bootloop-t3132888
1.)Prepare the Stock B137SP03 firmware on your SD card
2.)Download the fastboot.zip guide and extract it to a separate folder.
3.) next connect your phone to your computer and go to fastboot mode.
4.) Flash the boot.img and recovery.img you find on that guide.
5.) Once done, do the force upgrade with the B137 firmware.
blitzkriegger said:
You should flash B137SP03 firmware. You can also refer to this guide:
http://forum.xda-developers.com/mate-7/help/5-1-to-4-4-2-bootloop-t3132888
1.)Prepare the Stock B137SP03 firmware on your SD card
2.)Download the fastboot.zip guide and extract it to a separate folder.
3.) next connect your phone to your computer and go to fastboot mode.
4.) Flash the boot.img and recovery.img you find on that guide.
5.) Once done, do the force upgrade with the B137 firmware.
Click to expand...
Click to collapse
I've followed the guide you are reffering to. And I flashed the boot and recovery, and managed to get the roll back force installed. But for the life of me, I cannot get my phone to force install the B137 zip. I just can't get into force install mode. Are there tips or tricks? I am holding power up and down, and then press power untill I feel a short vibration. But all it does it show me the huawei logo screen and then shuts down again.
Very frustrating!
EDIT:
ok, I noticed that when my sd-card is not inserted, the phone easily boots into the force install mode. It shows the logo for a couple of seconds, screen goes black and then the force install loads. So this is what I did: insert the sd card half way, press vol up and down, and power on. Then after the logo when the screen goes black, insert the sd-card all the way and when the phone goes to force install mode, it can find the update!
Now installing.... hope this helps someone else out there!
Worked! And I am up and running again! Thank you for saving my mate
I got my Mate bricked and i've been trying to figure out how to solve it. I tried lots of things from different guides, but just an hour ago I found this guide and it worked! I can't tell you how happy I am right now, thanks guys!
aleksik said:
I got my Mate bricked and i've been trying to figure out how to solve it. I tried lots of things from different guides, but just an hour ago I found this guide and it worked! I can't tell you how happy I am right now, thanks guys!
Click to expand...
Click to collapse
Glad to hear both of you guys have your mates up and running again. As long as a phone turns on and is not dead as a brick there's always hope it can be restored
Hi everyone, I have the same problem with my mate 7, i was messing with unlocking bootloader(which I succesfully have done), couldn't get my phone rooted so installed TWRP recovery for Lollipop(which was already installed when i bought the phone). Ended up with soft bricked phone(no OS, no recovery at all).
I tried different tutorials how to fix it, none of them worked(including that one unfortunatelly).
I have taken some pictures to show you what the problem is but cannot post them until reach 10 posts on forum
Basically, i can get into fastboot mode by holding volume down with power button. Windows and Hisuite don't recognise my device but in fastboot mode i can check devices connected. Typing "fastboot devices" i get "P6Q7M14A15008421 fastboot", which i guess is my device indeed.
After that i try flashing boot.img and recovery.img(which are reported OK). Then rebooting with 3 button(vol up and down, power) and Huawei logo screen appears for a bit and goes into white screen saying "rescue mode" and at the bottom: "Error Func NO: 10(FUNC_BOOT_RECOVERY) Error NO:2". Trying rebooting into recovery mode(vol up and power) it shows similar "recovery mode" screen but with different errors: "Error! Func NO:12(FUNC_LOAD_IOM3) Error NO:1".
That's it! It seems like i cannot flash my device successfully for some reason. What Windows version did you guys use?? I tried Win 8.0 and Win 10, maybe i should use older systems? Please help, i had my phone for a week only and broke it(
I can't help you much because I don't have enough knowledge about these kind of things.. I use Windows 7 and from my previous experiences I can say that working with Windows 8 can be frustrating. PS. I bricked my Mate 12hrs after buying it
muzammil84 said:
Hi everyone, I have the same problem with my mate 7, i was messing with unlocking bootloader(which I succesfully have done), couldn't get my phone rooted so installed TWRP recovery for Lollipop(which was already installed when i bought the phone). Ended up with soft bricked phone(no OS, no recovery at all).
I tried different tutorials how to fix it, none of them worked(including that one unfortunatelly).
I have taken some pictures to show you what the problem is but cannot post them until reach 10 posts on forum
Basically, i can get into fastboot mode by holding volume down with power button. Windows and Hisuite don't recognise my device but in fastboot mode i can check devices connected. Typing "fastboot devices" i get "P6Q7M14A15008421 fastboot", which i guess is my device indeed.
After that i try flashing boot.img and recovery.img(which are reported OK). Then rebooting with 3 button(vol up and down, power) and Huawei logo screen appears for a bit and goes into white screen saying "rescue mode" and at the bottom: "Error Func NO: 10(FUNC_BOOT_RECOVERY) Error NO:2". Trying rebooting into recovery mode(vol up and power) it shows similar "recovery mode" screen but with different errors: "Error! Func NO:12(FUNC_LOAD_IOM3) Error NO:1".
That's it! It seems like i cannot flash my device successfully for some reason. What Windows version did you guys use?? I tried Win 8.0 and Win 10, maybe i should use older systems? Please help, i had my phone for a week only and broke it(
Click to expand...
Click to collapse
Sounds like the wrong boot.img or recovery.img has been flashed. May I know what Mate 7 model you have and which Lollipop firmwre version your phone came last with?
Try to obtain boot.img and revoery.img for your lollipop version then flash that via fastboot
blitzkriegger said:
Sounds like the wrong boot.img -recovery.img has been flashed. May I know what Mate 7 model you have and which Lollipop firmwre version your phone came last with?
Try to obtain boot.img and revoery.img for your lollipop version then flash that via fastboot
Click to expand...
Click to collapse
My phone mt7-09l, european version 16gb. Came with lollipop 5.1 when I bought it but I think I have formatted it via twrp recovery so it shouldn't matter what boot and recovery version I am trying to flash, should it? I'll extract boot and recovery from b308 today andtry that, see if this works. If not, only thing I can try is using win7 and that's it really, no more possibilities
dekraan said:
I've followed the guide you are reffering to. And I flashed the boot and recovery, and managed to get the roll back force installed. But for the life of me, I cannot get my phone to force install the B137 zip. I just can't get into force install mode. Are there tips or tricks? I am holding power up and down, and then press power untill I feel a short vibration. But all it does it show me the huawei logo screen and then shuts down again.
Very frustrating!
EDIT:
ok, I noticed that when my sd-card is not inserted, the phone easily boots into the force install mode. It shows the logo for a couple of seconds, screen goes black and then the force install loads. So this is what I did: insert the sd card half way, press vol up and down, and power on. Then after the logo when the screen goes black, insert the sd-card all the way and when the phone goes to force install mode, it can find the update!
Now installing.... hope this helps someone else out there!
Click to expand...
Click to collapse
I'm stuck on this stage, no errors while flashing but no boot either. Shows logo then like a spark a bit of music and animation (1 sec maybe) and reboot, so on and on and on...
muzammil84 said:
My phone mt7-09l, european version 16gb. Came with lollipop 5.1 when I bought it but I think I have formatted it via twrp recovery so it shouldn't matter what boot and recovery version I am trying to flash, should it? I'll extract boot and recovery from b308 today andtry that, see if this works. If not, only thing I can try is using win7 and that's it really, no more possibilities
Click to expand...
Click to collapse
If you were on Lollipop when everything went sour, you should do what I did, thanks to advice from @blitzkriegger:
You should flash B137SP03 firmware. You can also refer to this guide:
http://forum.xda-developers.com/mate...tloop-t3132888
1.)Prepare the Stock B137SP03 firmware on your SD card
2.)Download the fastboot.zip guide and extract it to a separate folder.
3.) next connect your phone to your computer and go to fastboot mode.
4.) Flash the boot.img and recovery.img you find on that guide.
5.) Once done, do the force upgrade with the B137 firmware.
I used the full steps from the link in there: flashed the right boot and recovery through fastboot. Then I flashed the rollback zip from my sd-card, and then I flashed the B137 zip from my sd-card. I can't tell you more about it, obviously
brack11 said:
I'm stuck on this stage, no errors while flashing but no boot either. Shows logo then like a spark a bit of music and animation (1 sec maybe) and reboot, so on and on and on...
Click to expand...
Click to collapse
Been there, done that. Very frustrating! I've tried several things, none of which are probably the right way, but they worked for me. sometimes....
Can you get into stock recovery (vol+ and power)? What I tried several times was wipe cache, and then hold the powerbutton untill my phone turned off. That worked occasionally to get the device totally turned off. Then try to get to force update with your sd-card half way in, and flip it in totally when the logo dissapears and the screen is black. I also tried to shut down the constant starting up by going into fastboot/recovery mode and then holding power down. As long as it takes. Good luck! And hopefully someone can give you proper advice...
I have OPO 64GB and unlocked via fastboot. Every fastboot command related to flash or erase or format gave same error, unable to erase or write the partition.
I was able to fastboot boot <custom_recovery.img> into TWRP 2.7 I believe but TWRP gives errors, unable to mount <partition>, etc. Any command in TWRP results into a failure to mount or write.
I tried ADB Sideload <zip> and at 12% it rebooted back into Cyanogen Mod ready logo.
TWRP only runs if I boot to it via fastboot, it can't write to the bootloader via fastboot. One strange thing under TWRP storage it shows Internal Storage 0MB and USB-OTG 0MB, the partitions also show 0MB excep for system, but can't format anything or resize.
I feels like there is no storage in this device, is this something that can be fixed or is this a DOA device? It was working fine and a Cyanogen update ran and bricked it!
When I try to fastboot flash I get this error, fail to write. I even tried the OnePlusRestoreTool and it fails to write to the phone.
fastboot flash recovery twrp3.img
target reported max download size of 1073741824 bytes
sending 'recovery' (13326 KB)...
OKAY [ 0.422s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.479s
Thoughts?
Thank You
It seems that your partitions are corrupt.
I had the same issue and solved it by restoreing completley to stock Rom. There must be a thread for this anywhere out, if not download a fastboot image from cyanogen support site extract it and try to flash it.
That is what I was leaning towards, but in every solution to restore the stock ROM I have to use fastboot and fastboot just fails to write anything. I can't even get TWRP to stick, fails to write every time. I tried the OnePlusRestoreTool but the driver installs ok but the tool can't find the phone, tried 2 different PCs. I was hoping for another solution other than fastboot or the OnePlusRestoreTool, I searched but could not find another method, I was hoping someone could point me in the right direction.
Thanks
newpop1_android said:
I have OPO 64GB and unlocked via fastboot. Every fastboot command related to flash or erase or format gave same error, unable to erase or write the partition.
I was able to fastboot boot <custom_recovery.img> into TWRP 2.7 I believe but TWRP gives errors, unable to mount <partition>, etc. Any command in TWRP results into a failure to mount or write.
I tried ADB Sideload <zip> and at 12% it rebooted back into Cyanogen Mod ready logo.
TWRP only runs if I boot to it via fastboot, it can't write to the bootloader via fastboot. One strange thing under TWRP storage it shows Internal Storage 0MB and USB-OTG 0MB, the partitions also show 0MB excep for system, but can't format anything or resize.
I feels like there is no storage in this device, is this something that can be fixed or is this a DOA device? It was working fine and a Cyanogen update ran and bricked it!
When I try to fastboot flash I get this error, fail to write. I even tried the OnePlusRestoreTool and it fails to write to the phone.
fastboot flash recovery twrp3.img
target reported max download size of 1073741824 bytes
sending 'recovery' (13326 KB)...
OKAY [ 0.422s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.479s
Thoughts?
Thank You
Click to expand...
Click to collapse
Try this
geowolf1000 said:
Try this
Click to expand...
Click to collapse
So I tried the link but also their method uses FastBoot and FastBoot fails to write to the OPO every time no matter what, see below. I can put TWRP in memory but can't write to the SD I guess. Any tool that can reformat the storage and put it back together since FastBoot and ADB can't write to it?
Thx
target reported max download size of 1073741824 bytes
sending 'persist' (4244 KB)...
OKAY [ 0.137s]
writing 'persist'...
FAILED (remote: flash write failure)
finished. total time: 5.208s
Has a second method from terminal
Run command from twrp rerminal
Στάλθηκε από το A0001 μου χρησιμοποιώντας Tapatalk
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Chinaroad said:
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Click to expand...
Click to collapse
He tried that one, but as the PC doesn't detect his phone that ain't gonna work...
@newpop1_android could you sent me a PM, I'll try to resolve your issue in a teamviewer session.
Chinaroad said:
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Click to expand...
Click to collapse
Hello, so I managed to get an older PC to do all this in as well and tried another PC anyway. I ran the color.zip install, drivers installed OK and phone is detected, I ran the Msm8974DownloadTool.exe and it found the phone in COM3, I see a progress bar in one file, the image file and then it reboots the phone but it comes back to the Cyanogen splash screen and it does not go anywhere, so I reboot it again manually power+VUp and the tool finds it again and tries to send the *same* file again, and then I tried this loop at least 10 times.
I conclude that it is unable to write the image to the cell, same symptom I encountered with Fastboot flash boot img. Does this mean that the cell is bricked since nothing can write to the SD?
Do the progressbars you see in Msm8974DownloadTool.exe become green?
Maybe see there:
http://www.technobuzz.net/guide-to-recover-from-hard-bricked-oneplus-one/
It is nearly the same like the one posted before, but has some screenshots.
After doing this color OS should boot up, not cyanogen os.
If only one image file is "flashed", check if your color.zip is downloaded correctly
Hope this helps
Flo9818 said:
Do the progressbars you see in Msm8974DownloadTool.exe become green?
Maybe see there:
http://www.technobuzz.net/guide-to-recover-from-hard-bricked-oneplus-one/
It is nearly the same like the one posted before, but has some screenshots.
After doing this color OS should boot up, not cyanogen os.
Hope this helps
Click to expand...
Click to collapse
Hello, not really, it does one file and then I see progress bar move on the first file, progress bar finished and then the phone boots to the cyanogen screen again, then i tried again, it still shows the same file again. It does not save the file, fails to write pretty much, same thing as fastboot.
There should be serveral progressbars. One for each image in color.zip. Try to reinstall the qualcomm 2012 drivers.
Have you restarted your PC?
Flo9818 said:
There should be serveral progressbars. One for each image in color.zip. Try to reinstall the qualcomm 2012 drivers.
Click to expand...
Click to collapse
I actually did that and tried one plus one as well, I also tried the other unbrick toll as well with other drivers. The phone is recognized no problem, but nothing can write to it, just like fastbook flash , write denied every time.
Restarted your PC after qualcomm driver install?
Maybe there be driver problems related to win10.
Also check
fastboot oem device-info if your bootloader is really unlocked
Flo9818 said:
Restarted your PC after qualcomm driver install?
Maybe there be driver problems related to win10.
Also check
fastboot oem device-info if your bootloader is really unlocked
Click to expand...
Click to collapse
It won't work, his device is not recognized by adb or fastboot.
My device is in the same state, I rebooted it and it hard bricked, I tried using the ColorOS flash tool but, when I start it, it is stuck in a loop trying to flash "8974_msimage.mbn", any solution would be appreciated, because I hard bricked it in the first day after receiving my OPO (I bought an used one).
I already tried on two different computers, the same issue happens, I also tried to find a fix, but everyone that had this issue never replied, so I think this state is really THE hard brick, with no ways to go back to the original state.
@newpop1_android did you find a solution for your problem?
MrPowerGamerBR said:
It won't work, his device is not recognized by adb or fastboot.
My device is in the same state, I rebooted it and it hard bricked, I tried using the ColorOS flash tool but, when I start it, it is stuck in a loop trying to flash "8974_msimage.mbn", any solution would be appreciated, because I hard bricked it in the first day after receiving my OPO (I bought an used one).
I already tried on two different computers, the same issue happens, I also tried to find a fix, but everyone that had this issue never replied, so I think this state is really THE hard brick, with no ways to go back to the original state.
@newpop1_android did you find a solution for your problem?
Click to expand...
Click to collapse
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
Yes, I did.
I also tried that tool before, same issue.
Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
The problem is that the device gets disconnected when flashing for some reason. I tried two different drivers, both didn't work.
I'm willing to pay 5$ to someone who can fix this issue for me.
MrPowerGamerBR said:
The problem is that the device gets disconnected when flashing for some reason. I tried two different drivers, both didn't work.
I'm willing to pay 5$ to someone who can fix this issue for me.
Click to expand...
Click to collapse
Which Windows Version do you use? I would try with win7. With win 8.1 and 10 you have to disable driver verification.
Have you disabled your antivirus?
Have you disabled UAC?
Maybe another USB cable?
If all this does not work see here:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
Flo9818 said:
Which Windows Version do you use? I would try with win7. With win 8.1 and 10 you have to disable driver verification.
Have you disabled your antivirus?
Have you disabled UAC?
Maybe another USB cable?
If all this does not work see here:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
Click to expand...
Click to collapse
Windows 7, but Windows 7 also needs to disable driver verification.
I don't use any antivirus.
No, but I ran the tool as administrator.
I already tried that, I tried with the original cable that came with the device and my Moto G 2014 cable, same issue on both.
It isn't a missing driver issue tho, Qualcomm drivers are installed and working because the ColorOS flash tool detects the device.
Anyway, thanks for helping
Hi,
I have a problem with my r7plusf.
I tried to install lineageOs, with the CM recovery I just got a "zip signature verification" problem. To avoid this problem i flashed TWRP and tried installing it without checking the zip signature. When doing that i got a "table error".
I try to reflash back the rom I had and now I am in trouble :
when i flash it it boots on TWRP instead of the rom.
I tried installing the colorOs recovery and it did not work (I just saw a message telling me "formating data and cache")
/*And now twrp is always telling me "can't mount /data".*/
I resolved this problem by formating the data partition
Does anyone know what i can do to reuse my phone?
Thank you by advance for all the help you could give me.
Little update :
I tried to build lineageOS by hand with this link : https://wiki.lineageos.org/r7plus_build.html to see if there was the cyanogenmod/lineage recovery included but when I try to brunch, I just get this error :
Code:
"ninja: error: '/home/user/android/system/out/target/product/r7plus/obj_arm/SHARED_LIBRARIES/libtime_genoff_intermediates/export_includes', needed by '/home/user/android/system/out/target/product/r7plus/obj_arm/SHARED_LIBRARIES/libandroid_servers_intermediates/import_includes', missing and no known rule to make it"
After looking at the files I just saw that the folder named "obj_arm" does not exists. For info Iam on archlinux whith linux kernel version 4.9.6-1 and I have GCC 6.3.1 .
Does anyone know how to solve this bug or has anyone got the cyanogenmod recovery?
UPDATE : I tried with the cyanogenmod recovery that someone gave to me and it didn't work either, the phone still boots on the recovery. I don't have anymore ideas anymore
Some one oppo forum just gave me the way to save my phone, i just had to boot in fastboot mode, plug the phone in my computer, open a command prompt and type the command "fastboot continue", everything just work fine now.
f22217 said:
Some one oppo forum just gave me the way to save my phone, i just had to boot in fastboot mode, plug the phone in my computer, open a command prompt and type the command "fastboot continue", everything just work fine now.
Click to expand...
Click to collapse
That just helped med A LOT
Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?
Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.
Both failed. I attached the errors I recieved.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/
It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.
Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?
Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
jwoegerbauer said:
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
Click to expand...
Click to collapse
As it turns out, I had already stumbled upon your your "ADB-FASTBOOT-Installer" during a trip down one of the many rabbit holes trying to get this tablet working again.
adb devices returns:
List of devices attached0123456789ABCDEF recovery
adb reboot restarts the tablet, which I assume means the ASUS tablet driver is working.
I can't seem to do anything else with adb, however, such as push a new TWRP version, etc. This may be a key point, as it seems likely the version I have of TWRP may be too old to support upgrade using something like Chrombi-KK.
Is this a likely theory?
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
NotTheLips said:
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
Click to expand...
Click to collapse
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
jwoegerbauer said:
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
Click to expand...
Click to collapse
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
[email protected] said:
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
Click to expand...
Click to collapse
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
NotTheLips said:
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
Click to expand...
Click to collapse
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
NotTheLips said:
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
Click to expand...
Click to collapse
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
jwoegerbauer said:
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
Click to expand...
Click to collapse
As I mentioned before, "2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine."
[email protected] said:
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
Click to expand...
Click to collapse
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
NotTheLips said:
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
Click to expand...
Click to collapse
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
[email protected] said:
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
Click to expand...
Click to collapse
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
the problem is your pc does not have adb and fastboot properly installed
try this one https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
also, use this official driver https://www.asus.com/SupportOnly/Eee_Pad_Transformer_Prime_TF201/HelpDesk_Download/
if your pc is 64 bit use win764bit version
NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
This "waiting for device" problem happens when the USB device node is not accessible to your current user. The USB id is different in Fastboot mode, so you can easily have permission to it in ADB but not in Fastboot.
Each manufacturer implements Fastboot differently. So, if not already done yet, download and install the suitable "Android USB Driver" provided by ASUS. Then Fastboot should work.
BTW: Your device actually stucks in recovery mode.
Is OEM Unlock got enabled in Android settings? If not, Fastboot never will work.