coolpad f1 not opening - General Questions and Answers

coolpad f1 not opening - General Questions and Answers

Hello guys . After a restart of my coolpad f1 8297w my phone was in bootloop . I entered in recovery mode and this message appeared :E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open/cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
I tried to use Sp flashtools and even that it was successful the phone does not open at all anymore .. Any ideas ? Thank you .

peej2014 said:
Hello guys . After a restart of my coolpad f1 8297w my phone was in bootloop . I entered in recovery mode and this message appeared :E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open/cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
I tried to use Sp flashtools and even that it was successful the phone does not open at all anymore .. Any ideas ? Thank you .
Click to expand...
Click to collapse
I have that phone and had the same problem. Re-format the cache partition to fix the recovery. And then reflash a stable rom.
---------- Post added at 12:42 ---------- Previous post was at 11:44 ----------
Universal unbrick guide:
Terminology - types of bricks:
Soft brick - often occurs in the shape of a bootloop or any other problems with booting such as always getting to recovery or not getting past the carrier logo. This type of a brick, which shows some signs of life, can in most cases be fixed.
Hard brick - As the name implies, your phone can essentially used as a brick and it shows no signs of life. This kind of a brick is rare and in theory should be unfixable. However there are advanced methods of fixing your phones such as JTAG, but they require extra tools and accessories.
The decision:
Is my phone soft or hard bricked?
If you answer yes to all of the questions below you probably have a hard birck:
Test as said in order!
Nothing happenes when you hold or press the power button
You cannot get the screen to even turn on by pressing or holding any combination of buttons on your phone
Nothing happenes if you do the same as about but with your phone plugged into a charger
Nothing happenes when you plug your phone into a computer
When you plug in your phone into a computer it does not recognize it as a phone, storage or any other media device
Nothing happenes when you try all of the above again, but with removing the battery in between steps for 10 seconds and putting it back in again
Nothing happenes when you try all of the above again, but after leaving the phone plugged into a charger for 2 hours
If all of the questions are a "yes", then you either have a broken charging port and and a discharged battery or you have a hard brick.
The unbricking:
There are many methods of unbricking and they are all different to each phone. Here I will list the most common methods that often succeed.
Samsung users skip to 4. method.
1. If you have access to a stock recovery:
Method 1:
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Choose “Wipe Cache Partition”.
5. Choose “Wipe Data / Factory Reset” to delete all your settings and apps, using the correct ROM.
6. Reboot your device.
Method 2:
Download the stock rom for your phone. It should be in ".zip" format. Make sure it's the official version
(Find it by Googling something like "[your phone model] stock rom")
Put the file on your phone's external SD card.
Make sure that the rom is for your exact phone model.
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Select "apply update from external storage"
5. Navigate to the zip file you copied to your phone
6. Install it.
If you get Status Error 7 that means you didn't download an official stock rom.
2. If you have access to a custom recovery:
Method 1:
Try stock recovery method 1
Method 2:
1. Find a stable custom rom for your phone or if you want to download the stock rom
Make sure that the rom is for your exact phone model.
2.. Copy the zip file to the phone's external SD.
3. Install the zip
(If you have a custom recovery you probably know the drill)
3. If you have access to fastboot mode:
First install ADB and fastboot drivers (if you haven't already):
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Once you have the drivers installed you have to find a recovery image for your phone to install a custom recovery.
You can try one of the popular recoveries such as CWM or TWRP.
You need to get the recoveryNameHere.img file for your phone.
Find it by Googling:
"[your phone model] TWRP recovery"
or
"[your phone model] CWM recovery"
Make sure that the recovery is for your exact phone model.
Now on your phone enter fastboot mode:
Turn your phone off.
You can try different button combinations. For my phone it's holding power and volume down buttons.
Once you're in fastboot mode plug your phone into a computer and open your terminal/cmd.
Type in:
Code:
fastboot devices
You should see a list of devices. There should be only one device ID number.
If you see the ID it's working. If you don't you didn't install the Google USB driver properly (on Windows) and if it says "'fastboot' is not a recognized command" or "No command 'fastboot' found" then you didn't even install your drivers.
If you have problems with installing Google "how to install adb and fastboot drivers"
Now that you know fastboot is working type in:
Code:
fastboot flash recovery C:\Path\To\Recovery.img
Replace "C:\Path\To\Recovery.img" with an actuall path of the recovery file you downloaded.
It should say success.
If it doesn't try to execute:
Code:
fastboot oem unlock
This will delete all data you had on your phone (games, game progress, apps...).
Now try
Code:
fastboot flash recovery C:\Path\To\Recovery.img
again.
Once you're done type in:
Code:
fastboot reboot
And your phone should still not work. Now what you have to do it try the custom recovery method above (number 2.)
4. If you have a Samsung device:
Try this tutorial of unbricking with Odin: click here

How can you un brick if it wont powrr on? I'm letting mine charge, it was gave by a friend. Id like to get it running..

Related

HELP! Soft-bricked Transformer tf300 - sdcard mounting issue

Hi everyone,
First post (brilliant video!).
My tablet:
Asus Transformer Pad TF300 (rooted)
CWM 5.8.2
My problem:
- We decided to give our Transformer to my gf's dad for his birthday. I tried to backup using a later version of CWM (6 something) but it didn't work. I downgraded to 5.8.2 and it worked fine. I then did a factory reset (which I realise now was not the way to go).
- CMW bootloop : restored my backup, successful - still bootloop.
- Have spent the last 4 hours figuring out ADB and managed to push both a new recovery (rogue) and the latest ASUS firmware to the SDCARD. Despite it confirming the transfer from the cmd line I could not see the zip files in the directories. I tried several times to several different directories. On the last try before the SD card decided to go on vacation I did see one of the files in the root directory.
- Now, no matter what I do, I get a "can't mount /SDCARD" error. Trying to erase/format/factory reset the pad results in errors when trying to access DATA and SDCARD.
- I've located and tried several different scripts from different threads that supposedly create a fake SDCARD directory but nothing has worked
http://forum.xda-developers.com/showthread.php?t=1679274&highlight=encrypted&page=3
- I've also tried to run the install package remotely from ADB but the mounting problem reoccurs
http://www.addictivetips.com/mobile/how-to-install-a-rom-to-an-android-phone-device-without-sd-card/
It appears that many people have encountered similar problems but none of the recommendations have been successful for me so far.
There also seems to be a strange anomaly with the adb shell timing out before I can finish the command. Is this a cable issue?
I'd be super grateful to anyone that can help me sort this out.
Cheers
Sam

Anyone?
I should mention that I had installed Super SU / Super User on the tablet... if that makes any difference.
I woke up this morning and booted the tablet to get this:
E:can't mount /cache/recover/command
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
Error mounting /cache!
In addition to all the previous problems.
Super!

Nobody? Anybody?! Please help!

Hi,
If you have fastboot mode, try to inject twrp (the last 2.2.x.x or something like that) ...
--> read the way to do that on the http://teamw.in/project/twrp2/97
With last TWRP you can mount sd card (first download & extract stock rom .zip and put it on root of your sdcard)
After that, flash stock rom with TWRP ...
Choose fastboot method...be careful (there is 2 versions : JB or ICS)

SOFT BRICK fixable!!! although root repair not yet covered...
I seemed to have a simular problem on my tf300t.
tried to install a CM 9.1.0 (stable)
Stuck at asus cold boot screen.
Solution i found+
*download Fastboot and an adb.shell brigde if you dont already have it.
*place the downloaded systemware (AVALIBLE ON THE ASUS SUPPORT WEBSITE) you wish to install in the same folder you have fastboot. (example-US_epad_10.4.3.13.blob)[432.3MB]
*Boot tablet into CWM [NOTE: I used CWM-Touch. 6.0.3.1 or something along those lines] (TWRP- im unsure if the process is the same).
-from advanced settings at the bottom, wipe dalvik cache.
-no need to wipe your user data cache, but wipe other data cache.
-reboot to bootloader and select fastboot option. (3rd one with pic of usb) DO NOT PLUG IT IN YET.
*Back on your WIN pc open your windows explorer, find the folder containing the Fastboot.exe and hold shift and right click at the same time for an admin operations menu. You should see an option "Open Command Prompt Here". Click it to begin a Fastboot session.
*NOW CONNECT YOUR TABLET!!!
*TYPE THE FOLLOWING AS SHOWN! DO NOT DIVERT OR YOU SCREW UP-
fastboot -i 0x0B05 flash system blob
***NOTE THAT THIS METHOD WILL TAKE QUITE SOME TIME AND YOUR COMPUTER MAY EVEN LOOK LIKE ITS FROZEN...STOP! JUST LET IT DO WHAT YOU ASKED IT TO...THIS IS QUITE A LARGE TASK AND WILL TAKE TIME. MY PC IS AN OLD DELL E300 dem. I KICK THE PROCESS ATLEAST A DOZEN TIMES BEFORE I JUST LEFT IT ALOOOOONNNE and it worked...although i cant seem to figure out how to delete the old su binary i install so i could re-root it....ANYONE GOT ANSWER? PLEASE HELP. EMAIL IS ALWAYS UP.
IF THESE INSTRUCTIONS ARE UNCLEAR, OR YOU DONT UNDERSTAND SOMETHING, MESSAGE ME...
AND IF THIS HELPED YOU...SHARE THE LOVE-GIMME A THANKS!

Encryption unsuccessful help

Hello,
I turned on my Xoom to see "Encryption Unsuccessful" tonight. If i boot into stock recovery and try to factory reset, it cannot mount Cache. If I plug the device into my computer, fastboot can find it but ADB cannot. I have the proper drivers installed. I can't get into my tablet to turn on USB debugging. I just bought an OTG cable to try to fix it, but cannot find the update.zip file that I need. If i try to fastboot oem unlock, it fails. I've tried everything I can find, I've done hours worth of playing/trial and error to no avail. Any help would be fantastic. Truly at a stand still. Please ask with any specifics needed to assist me.
Is it possible to flash to CWM recovery without being able to boot/find it in ADB?
Thank you,
Bradon

>.<
Nearly to the point of offering some sort of payment for assisting me. I'd rather not ship it out, but more than glad to work something out paypal or giftcard wise. This tablet is the only thing keeping my wife entertained, and another tablet is not in the budget.

But u can connect with fastboot to device ?
if yes this should help you
http://forum.xda-developers.com/showthread.php?t=1451655&page=7
http://forum.xda-developers.com/showthread.php?t=1049485
Probably you will lose all data on it ... Why u wanted to encrypt u device ...
I did it too but it was missunderstanding specialy when flashing a lot .

Alright so...
I've used fast boot flash user data, system, recovery and boot. Those are all successful, but if I reboot.. Nothing changes.
I've loaded many zips onto a flash drive with an otg cable, boot into the stock recovery and try to update, unable to verify signature.
Adv will not find the device, reinstalled drivers many times
Rsd will not find the device
Factory reset fails, cannot mount cache and about 10 other cache/recovery errors
Fast boot OEM unlock fails, unable to write a certain 3 letter file
I'm at work right now, so I can post specifics/pics later.
I didn't try to encrypt it, it seemed like a virus that my wife got. She clicks on advertisements, downloads sketchy files/apps.
It is unrooted, stock recovery.
20+ hours of research and trial.. No success.

Can u use this ?
http://forum.xda-developers.com/showthread.php?t=1074979
Use 2 method.
Write response what happend and it does flash recovery .
You have to unlock bootloader
look here simillar problem :
http://forum.xda-developers.com/showthread.php?t=1571827
http://forum.xda-developers.com/showthread.php?t=1952628
And u do not need any special otg cabel - use stock xoom from package. OTG is for host-usb.
Anyway u will have to do it with fastboot , probably /cache partialy encrypted.

Alright, I just followed the CWM recovery guide.
First off, ADB does not find my device, meaning I cannot reboot into the bootloader. I can flash the recovery only after flashing userdata for some reason. After flashing, it says complete though when I reboot nothing changes. The other 2 links, first one I can't use because adb doesn't find my device, and the 2nd one.. I don't think xoom has a "download mode".
Thanks

Ok, so when u push down button in booting u have only recovery ?
U should have fastboot too ... try to press up vol 1 s after booting, then connect to pc, and check in device manager rmb on "My pc"
And ? .... This must working ... Use fastboot.exe in cmd ( in windows 7 ) on Administrator User.

Also, when I first boot up recovery I get
E: failed to mount /cache (invalid argument.)
E: Can't mount /cache/recovery/command
E: Failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E: Failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_install
E:can't open /cache/recovery/last_install
E: Failed to mount /cache (invalid argument)
If i try to factory reset or clear the cache, I get the same message.

U do not understand what u reading, u cant do this from recovery ...
U have partialy crypted storage ... its normal!
1. download fastboot on windows
2. install drivers from
1) Get the Motorola USB drivers MOTODEV > Documentation & Tools > USB Drivers (you need to sign up on their but maybe you can google this and find it as well)
2) Get the Android SDK Android SDK | Android Developers (you only really need the fastboot executable file for your host OS)
Click to expand...
Click to collapse
3. run fastboot protocol on xoom press down vol "find fastboot" if not press top vol in booting - should fastboot protocol ... in output
4. Use fastboot.exe from android sdk - run in in cmd ( Run ad Administrator , right click on cmd)
4. unlock bootloader
5. flash rom boot recovery in *.img format!
This must working...

When I connect it to my PC in fastboot mode, it comes up as "Mot Single ADB Interface"

bcwest said:
When I connect it to my PC in fastboot mode, it comes up as "Mot Single ADB Interface"
Click to expand...
Click to collapse
Is it bad ? - now when u show up "fastboot protocol ... " on xoom run fastboot from android sdk .

Fastboot ran from cmd with admin privileges.
fastboot oem unlock
used volume controls to select yes/i accept
Device unlock operation in progress...
Formatting UDA.
hardware/tegra/core/system/moto/fastboot_sparse.c:324 NvStorMgrFileOpen("UDA"):196624
ERROR: Failed to format UDA.
Error while unlocking device.

unplug mmc card from xoom and try again, where did u get files ... system.img ,recovery.img,boot.img ?

I've tried with both the mSD card in, and out. I got the boot/system/recovery/userdata from the stock image post from XDA.

ok, I didnt tryed this with stock rom, try to change recovery with http://forum.xda-developers.com/showthread.php?t=1074979
reboot and try to get to new recovery.
do this:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img <- from http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
Which model of xoom u have ? Did u restart xoom after flashing ? Is there any output ? (without up,down vol )

mx600 is the model that I have.
All of the flashing goes through fine
fastboot erase cache fails instantly (Failed to format PDB)
fastboot erase userdata fails instantly (Failed to format PDB)
fastboot reboot
volume down for recovery to see if CWM changes went through
stock android recovery

If I put my mSD card back into the unit, and try to do it all over again..
Flashes go through fine
Cache fails instantly, same error
Erase userdata causes my cmd to hang up, and the xoom sits at "StorMgr Formatting UDA STATUS: | | |"
5 minutes later, still sitting at that message.

Mx600, I restarted the device after flashing everything, If I let it go past the Dual Core Technology big red M, it boots into android but all that I get is the Encryption Unsuccessful screen. It says push restart, but it does nothing.
Which model of xoom u have ? Did u restart xoom after flashing ? Is there any output ? (without up,down vol )[/QUOTE]

Damn, that mean bootloader is locked or he have problem with gpt ?
ok... I'm not sure what will hapend but u can try to lock it again
fastboot oem lock
then reboot
fastboot oem unlock
output ?

Device Lock operation in progress...
Formatting UDA.
hardware/tegra/core/system/moto/fastboot_sparse.c:350 NvStorMgrFileWrite(ff, 0x00004000:00000000):196608
ERROR: Failed to format UDA
Device lock operation FAILED.

[Q] weird problem on Nexus S - please assist

This is going to be pretty long and have had the problem for months so please bear with me, read and see if you could assist.
Borrowed a friends Nexus S a while back. Used it for a few days, turned it on one day and it stays on the black google screen with the open padlock at the bottom
I am able to enter Fastboot mode is shown in image 2; lock state is unlocked.
I followed the instructions as in post 2 on the following thread
HTML:
http://forum.xda-developers.com/showthread.php?t=1787169
and as copied below but when i got to the part where i needed to mount my sdcard i get the error " unable to write to ums lunfile (no such file)".
Originally Posted by SamuelDebruyn View Post
Ok, you'll need a Windows computer to fix this. Linux should work too but if you're using Linux I guess you could figure out what would be the instructions for Linux yourself. Mac would work too but I don't know how.
Download and install the Android SDK on your computer from http://developer.android.com/sdk/index.html
Open the SDK Manager (there should be a shortcut in your start menu) and install "Android SDK Tools" and "Android SDK Platform-tools" and "Google USB Driver" (it's in Extra).
Turn your phone off, take the battery out, look at the bottom of the phone and write down the model number.
Now go to https://developers.google.com/android/nexus/images and download the factory image for your model for version 4.0.4.
You'll need something like 7-Zip (http://www.7-zip.org/) to open it.
Copy image-so....zip, radio-crespo...img and bootloader-crespo...img from the factory image to the platform-tools directory (on most computers it will be C:\Program Files (x86)\Android\android-sdk\platform-tools and you'll need Administrator rights).
Now open the platform-tools directory from the Android SDK and right click on an empty space while holding the SHIFT button and select "Open command prompt here".
Put the battery back in your phone and press Power while holding the Volume-Up button so it will boot into fastboot mode. Then connect it to your pc.
If Windows starts complaining about drivers then point it your SDK installation directory (include subfolders) or use 7-Zip to unpack http://www.mediafire.com/?5a7gou9droidi53 and point Windows to the directory where you unpacked it. More info on http://www.sevenforums.com/tutorials...e-manager.html
When you type "fastboot devices" and press Enter in the command prompt you opened before it should list one device (being your phone).
If you haven't unlocked your phone before type "fastboot oem unlock" and press Enter. Follow the instructions on the screen on your phone to complete the unlock.
Next type "fastboot flash bootloader bootloader-crespo...img" (you can press TAB to auto-complete) and press Enter. (THIS IS THE MOST IMPORTANT STEP, IF THIS GOES WRONG YOUR PHONE IS SCREWED. Don't continue if another step didn't succeed. If this works, then you can do anything with it.)
Now type "fastboot reboot-bootloader" and press Enter and wait for your phone to reboot into fastboot mode.
Next type "fastboot flash radio radio-crespo...img" (you can press TAB to auto-complete) and press Enter.
Now type "fastboot reboot-bootloader" and press Enter and wait for your phone to reboot into fastboot mode.
Next type "fastboot -w update image-....zip" and press Enter.
Now type "fastboot reboot-bootloader" and press Enter and wait for your phone to reboot into fastboot mode.
Next download http://download2.clockworkmod.com/re...0.7-crespo.img and also put it in the platform-tools directory.
Then type "fastboot flash recovery recovery-clockwork-6.0.0.7-crespo.img" and press Enter.
Now type "fastboot reboot-bootloader" and press Enter and wait for your phone to reboot into fastboot mode.
Now use the volume keys on your phone to navigate to the word Recovery and press the Power button to boot into recovery.
You're now in CWM Recovery, use the volume keys and the power button to go to Mounts & Storage > Mount USB Storage (you might have to scroll down). Now it will come up on your pc and you can transfer the update file for Jelly Bean to your phone. You can find it here: http://forum.xda-developers.com/show...68&postcount=1 (use the one for your model for IMM76D).
Unmount the usb storage, go back to the main menu and go to Install Zip from sdcard > Choose zip from sdcard and open the update file you just transferred to your phone.
You can now go back to the main menu and choose "reboot system now". It will ask you if you want to remove the auto recovery installation, do that.
That's all, you now have a clean and working Jelly Bean installation.
Someone else wrote down the same instructions if mine are not clear enough: http://forum.xda-developers.com/show....php?t=1785672
Click to expand...
Click to collapse
This prevented me from putting the stock image on the sdcard for flashing via CWM.
is there another way i can get this working, maybe via fastboot or via ODIN so i can return my friends phone.
Thank you.

Hi I had this problem to, mine was from a bad flash / bad firmware.
First I suggest http://forum.xda-developers.com/showthread.php?t=2284670 better recovery.
After from recovery
select factory reset, wipe cache, and from advance wipe dalvic cache.
then select mount usb, copy to card slim bean 3.1.0 http://www.slimroms.net/index.php/downloads/dlsearch/viewdownload/465-crespo/2505-slim-ns-3-1-0-official plus gaps http://www.slimroms.net/index.php/downloads/dlsearch/viewdownload/461-addonsfullpackages-412/2501-aio-addons, flash them in this order.
After first boot and config u can use http://www.wugfresh.com/nrt/ to write the OEM firmware.

Sorry this didn't work because nothing can be written to system and the sdcard is still not able to mount
Sent from my GT-N7100 using xda app-developers app

[GUIDE] Repair bootloop wrong recovery flash Huawei Honor 3X G750-u10

this tutorial, is for repairing the huawei g750-u10 in case you flashed the wrong recovery and now you're stuck in a bootloop.
First of all you will need (it's all in the link to download, make shure you have a sdcard on your phone before starting):
-Adb install setup
-Adb toolkit
-vcom drivers
mega.co.nz/#!gURHXDoZ!QNmv7LaK8r4WIQBGaUyoNho3TPX0YZp9jwHaEHgDmII
note:the recovery.img provided on the rar file only works for the U10, the method might work for other models but with a diferent recovery file.
-Installation of the phone mediatek drivers:
-Start with installing th vcom drivers i provided on the rar file, type HDWWIZ on the windows search tab:
Install the hardware manually>Ports(com&lpt)>Have a disk>select the file wich corresponds to you windows>mediatekpreloader usb vcom port> restart your computer. (if this method doesn't work for you try to search for vcom driver installation tutorials)
-Installing adb
-double click on the adb-setup.exe file provided and install it including drivers.
-the adb tool kit doesn't need installation just run the Adb toolkit Gui
on adb toolkit, type the command fastboot continue as shown in the picture
s13.postimg.org/yuauaawpj/Untitled.jpg
Remove the battery from your mobile phone, wait 5s plug it in again. Connect the usb to the computer and pluh it to your phone and at the same time push the power button till it turns on but keep your finger in the VOLUME DOWN all the time, it may reboot 2 times but then you will get the fastboot/repair mode image you can now lift your finger.
When you are in fastboot connected to your computer (the mediatek drivers will install wait for installation to complete).
Now return to the Adb GUI and press the execute command, (it will appear 3 lines starting with something saying error dont mind that it's normal) and wait a few seconds then your phone will restart it self and boot normally.
You're allmost there:
-When your phone boots, select the usb connection to usb mass storage device.
-copy the recovery.img provided to the root of your sdcard, safely unplug the phone from your pc.
-download and install the mobile mtk uncle tools app from the playstore.
-turn off wifi and mobile data, start the app and give it root permission.
-press the recovery update, select the chinese character file that you copied to your sd before and proceed, VERY IMPORTANT when it asks if you want to reboot into recovery select NO.
- get out off the app and restart your device normally, it's all done you have your phone back.
this is my first tutorial on xda, hope it is easy to follow and i'm thankfull for any suggestions to improve it.

Not rebooting automatically after fastboot continue command
sevenr33 said:
this tutorial, is for repairing the huawei g750-u10 in case you flashed the wrong recovery and now you're stuck in a bootloop.
First of all you will need (it's all in the link to download, make shure you have a sdcard on your phone before starting):
-Adb install setup
-Adb toolkit
-vcom drivers
mega.co.nz/#!gURHXDoZ!QNmv7LaK8r4WIQBGaUyoNho3TPX0YZp9jwHaEHgDmII
note:the recovery.img provided on the rar file only works for the U10, the method might work for other models but with a diferent recovery file.
-Installation of the phone mediatek drivers:
-Start with installing th vcom drivers i provided on the rar file, type HDWWIZ on the windows search tab:
Install the hardware manually>Ports(com&lpt)>Have a disk>select the file wich corresponds to you windows>mediatekpreloader usb vcom port> restart your computer. (if this method doesn't work for you try to search for vcom driver installation tutorials)
-Installing adb
-double click on the adb-setup.exe file provided and install it including drivers.
-the adb tool kit doesn't need installation just run the Adb toolkit Gui
on adb toolkit, type the command fastboot continue as shown in the picture
s13.postimg.org/yuauaawpj/Untitled.jpg
Remove the battery from your mobile phone, wait 5s plug it in again. Connect the usb to the computer and pluh it to your phone and at the same time push the power button till it turns on but keep your finger in the VOLUME DOWN all the time, it may reboot 2 times but then you will get the fastboot/repair mode image you can now lift your finger.
When you are in fastboot connected to your computer (the mediatek drivers will install wait for installation to complete).
Now return to the Adb GUI and press the execute command, (it will appear 3 lines starting with something saying error dont mind that it's normal) and wait a few seconds then your phone will restart it self and boot normally.
You're allmost there:
-When your phone boots, select the usb connection to usb mass storage device.
-copy the recovery.img provided to the root of your sdcard, safely unplug the phone from your pc.
-download and install the mobile mtk uncle tools app from the playstore.
-turn off wifi and mobile data, start the app and give it root permission.
-press the recovery update, select the chinese character file that you copied to your sd before and proceed, VERY IMPORTANT when it asks if you want to reboot into recovery select NO.
- get out off the app and restart your device normally, it's all done you have your phone back.
this is my first tutorial on xda, hope it is easy to follow and i'm thankfull for any suggestions to improve it.
Click to expand...
Click to collapse
Hi, I've followed the instructions you gave and now I'm stucked at the part which it wouldn't reboot by itself after i typed the "fastboot command".
1) Before I've had chance to charge my phone, it ran out of battery and fastboot mode does not charge the phone. I've also tried to flash the recovery image in fastboot mode, but i got Err:0x2017, what is this error about?
2) And the GUI should run in location bin files as my fastboot driver, not the 0KB fastboot in default location.
2) Do all these steps require unlocking bootloader? I don't think I've unlocked, all I did was just root the phone.

Help
Hi
I have a rooted Huawei Ascend Mate but I installed the wrong TWRP recovery a few days ago. My phone keeps booting and I can't use my recovery, because it is a touch version but it doesn't respond to my touch. So, I don't know if I can flash my stock rom or another recovery...
Can I use this tutorial to fix my phone or can you please make one for the Huawei Ascend Mate?
kind regards

Turning on to stock recovery

I have a J7 prime, on7xelte, g610f, oreo 8.1.0, stock firmware, no custom recovery. I wanted to root it and for that wanted to install twrp. I did NOT use Samsung Antiroot Removal Tool, RMM State Bypass zip, No Verify Encrypt zip. I tried to flash it using adb but no matter what it wont detect my phone in recovery/fastboot, only when its on or sideload. On sideload i got an error. So i tried to do it with odin, since odin detects my phone EVEN though windows doesnt. After doing that somehow my system got corrupted. i couldnt mount /data once in twrp and trying to boot it up caused bootloop. i couldnt get it to mount usb either. then i force restarted it into download mode and reinstalled stock firmware, retried the twrp .tar, and failed again. and again. then i saw a video rooting j7 prime with a root file The link to the video:
. the file was for g610fd, i thought the "d" was a typo and flashed it anyway. Now I boot up into the stock recovery with the exact following lines:
Installing system update (loading)
no command (exclamation triangle)
(after a while)
Android recovery
samsung/on7xeltedd/on7xelte
8.10/MIAJQ/G610FDDS1CTE3
user/release-keys
[the regular options here]
#fail to open recovery_cause(no such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
File based OTA
supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
#MANUAL MODE V1.0.0#
Successfully verified dmverity hash tree
:/ so apparently at this point, only the volume buttons work. i mean i can only go up and down but not select a thing. its bad. so i tried force rebooting into the download mode. THERE, the VOLUME buttons dont work. means i cant confirm and proceed into the download mode fully. my pc doesnt recognize the device in either states so i cant command in adb. one thing is that even before this error my pc didnt notice my phone in either states. so i might be missing the right drivers. my wire isnt flawed, i have 3 wires. i have hand typed everything here so will be great if you take your precious time to type any advice here for this poor fellow who is scared of losing his only phone.

Database Info

welcome