[Q] Cannot flash any recovery or ROM! - General Questions and Answers

Hello.
I have an Alcatel One Touch 908F running on Android 2.2.2 that I successfully rooted. Then I installed a CWM 5.0.2.7 recovery. But then, after flashing a custom ROM Android 2.3, it turns on but does not boot up anymore (Stuck at Alcatel One Touch logo).
So I booted to recovery and tried to flash my stock ROM, but it shows me "E: Cannot mount /sdcard". I got the same error by selecting the option "Mount /sdcard".
Then I booted it up into Fastboot mode and connected it to my PC. I typed the command "fastboot flash recovery ..." but then after sending the recovery successfully and when trying to write it, it shows me "FAILED (remote:flash write failure)". I tried to run the command "fastboot -w" and I got this :
Erase successful, but not automatically formatting.
File system type not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
OKAY [ 0.599s]
erasing 'cache'...
OKAY [ 0.229s]
finished. total time: 0.834s
I always get the same errors though I slow-formatted the 2GB memory card in my phone to FAT32 multiple times and changed the USB port.
I guess that my phone is soft-bricked and that its internal memory is messed up (I am 80 percent sure).
Can you help me, please ? I looked for the solution for several weeks and couldn't figure it out. I'm now desperate.
Thank you very much.

try this if ur stuck in bootloop, soft bricked or any kind of problem during boot....
Try flashing your phone's stock firmware using flashrool
Step 1:- download flashtool
Step 2:- install flashtool ( if u dont know how to install then check out the right way)
Step 3:- install driversv from driver folder in flashtool
Step 4:- check the last two box
Step 5:- copy your phone/tablet Stock firmware and paste it in firmware folder in flashtool ( u can get ur stock firmware from Google just search there)
Step 6:- open flashtool
Step 7:- connect your phone/tablet in flash mode
Step 8:- now,clicl on flash icon in flashtool selct flash mode
Step 9:- select ur phone/tablet firmware at left corner
Step 10:- check both the boxes at right upper corner
Step 11:- and click flash ( it will take about 20 mins so take a cup of tea)
Now, disconnect ur phone and start..... Now, you have
To root again... Happy rooting
NOTE:- THIS METHOD CAN HELP YOU IN EVERY WAY EITHER YOUR STUCK IN BOOTLOOP OR YOUR PHONE IS SOFT BRICKED ETC.....
Download Link for flashtool:- http://forum.xda-developers.com/xperia-z/development/tool-flashtool-v0-9-10-1-windows-linux-t2229790
PLZZ DONT FORGET TO HIT THANKS BUDDY

Maybe CWM Recovery 5.0.2.8 wil work

Sorry. But it does not detect my firmware. I tried selecting the other mode (fastboot) but it does not seem to work. Plus, I think flashtool is only for Sony Xperia devices while I have an Alcatel. Any other suggestions, please ? Thank you.

Thank you all for my help. I finally managed to get it right.
I changed the SD card and updated my CWM to 6 and it worked!

Related

[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !

Alot of the guides floating around showing how to flash back to stock rom is incomplete ( missing a few steps ) and will result in boot loop most of the time. the correct procedure is :
Part 1 : Setting up Fastboot.
1. Make sure you have java installed, if not get it from here : http://java.com/ and install it.
2. Download the Android SDK manager from here : http://developer.android.com/sdk/index.html ( get the exe download )
3. Install SDK manager, then run the android SDK manager.
4. Once launched it will show you available updates, choose ONLY these two "Android SDK Platform Tools and Android SDK Tools" and update them.
5. After update is complete close the sdk manager and go to the SDK manager platform-tools folder, normal path is : ( C:\Program Files\Android\android-sdk\platform-tools )
6. Copy the following 3 files from this folder : "adb.exe" , "AdbWinApi.dll" and "fastboot.exe"
7. go to your c drive ( c:\ ) and make a new directory called "fastboottools"
8. copy the 3 files above into your fastboottools folder.
9. so now your should have a folder like this : "c:\Fastboottools" with the following 3 files in it "adb.exe" , "AdbWinApi.dll" and "fastboot.exe".
Click to expand...
Click to collapse
That is it, Fastboot tools is setup. Proceed to next guide.
Part 2 : Flashing guide.
1. download the ROM from here:
ruu_chacha_htc_asia_wwe_1.57.707.2_radio_47.23.35. 3033h_7.51.35.19_release_228383_signed.zip
or here ( mirror link ) : ruu_chacha_htc_asia_wwe_1.57.707.2_radio_47.23.35.3033h_7.51.35.19_release_228383_signed.zip
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
3. Enter the fastboot mode on your phone by pressing volume down + power button after the device has been turned off.
4. Choose fastboot on the phone by pressing power button, and then connect your phone to your PC
5. Using fastboot tools, open the Command prompt and navigate to "C:\fastboottools" then run this command on cmd: "fastboot flash system system.img"
6. Dont reboot, Using fastboot tools, run this command on cmd: "fastboot flash boot boot.img"
( The two commands in step 5 and 6 are different, make sure to type each one correctly and to do them straight after each other )
7. Reboot phone. let it boot up, you will still get bootloop or error message.
8. Take out the battery.
9. Boot back into bootloader ( Volume down + power ).
10. Now choose recovery.
11. Phone should now reboot itself and bam, all should now work fine.
Click to expand...
Click to collapse
after trying EVERYTHING else, this is the method that worked for me, i tried to cover every step possible ( alot of the other guides skipped few steps and that is where i got problems ).
hope this helps.
( PLEASE BE AWARE : This will remove recovery and root. if you flash back to stock rom using this method you will have to root your phone again. It will still be unlocked, just recovery and root will be removed. to re add recovery and root check part 3 below. )
Part 3 : Add recovery and root access back after installing stock rom.
1. Download the following 2 files, you will need them :
PH06IMG.zip
su-2.3.6.1-ef-signed.zip
2. Extract PH06img.zip to your "c:\fastboottools" directory. it will add the "recovery.img" file to fastboot.
3. Copy the file su-2.3.6.1-ef-signed.zip to your phones SD card, dont change the name, keep it standard, just put it in the root directory of your SD card.
4. go to the settings on your phone "Settings -> Power -> and Uncheck Fast boot" ( This is important, make sure fastboot is unchecked.
5. Take out your battery, put battery back in and boot into bootloader ( hold down volumedown + power )
6. Choose fastboot on the phone by pressing power button, and then connect your phone to your PC
7. Go to the Fastboottools directory "c:\fastboottools", Hold CTRL+Shift and right click in that Folder and open Command Prompt.
8. type inside command prompt : "fastboot flash recovery recovery.img" and let it finnish, takes less than a minute.
9. reboot your phone, but reboot it back into bootloader ( hold down volumedown + power )
10. Now using volume keys choose "recovery" and press "enter" ( not power button, rather use enter button in recovery else you sometimes get a "hat like" picture on the screen )you should now see the recovery options.
11. find the "install zipd from sd card" option and press enter, then choose su-2.3.6.1-ef-signed.zip and confirm to flash it.
12. once flashed reboot the phone and you will now have recovery and root access back again.
Click to expand...
Click to collapse
it is recommended you update superuser to newer version and also install busybox.
Now that you have recovery installed you can also flash custom roms again.
I STRONLGY recommend once you reach this step that you make a backup of your rom via the bootloader recovery menu, that way you dont have to go through all this pain again next time.
The End !!!
feel free to post any problems you encounter below.
stuck on bootloop at step 10
I've attempted the recovery and get as far as step 10, but unfortunately
"still suffer the bootloop.
what am I supposed to do in the recovery step to get it working fine!
do i load the update.zip?
please reply if availale... am stuck on bootloop
ty
bootloop ussualy happens when you dont clear your cache properly before flashing.
Make sure to clear ALL cache, and also make sure to follow the steps exactly as they are posted, even if it looks like you can skip a step DON'T. do each step as posted, and clear all cache when you are told to. then you wont get boot loops.
Hi,
I bought HTC chacha locally at a online retailer. Its not tied to any sim/operator. However I am stuck at android version 2.3.3. (firmware version 1.20.720.1). If I try to run the (ota)software update, the phone says no updates available.
I really need to unlock the boot loader. However if I try the htcdev.com, the RUU utility says that the please update to 1.57.XX and then try unlocking the bootloader. I am really stuck here.
My question is can I try the steps mentioned above in this post to get the firmware update, with a locked bootloader?
Any other suggestions to update my firmware to the latest 1.57.XX?
--Thanks in Advance..
htc status restore factory 2.3.3
No, I didn't make a real backup! I thought titanium backup would cover that, it didn't, so I have no backup of the stock stuff.
I have a HTC Status (aka chacha) US ver with att. I unlocked the boot loader by htc's site, worked fine. Then I rooted it with cmw, worked great.
Recently the ota 2.3.5 update (48mb) became available. I downloaded it and tried to install it, it failed with checksum. I know it is the cmw mod. How can I get the stock load 2.3.3 back onto my htc status? The above directions mention the "asia" load. Are the files mentioned generic for all phones with the exception of the cid?
p.s. It would be great if someone out there had the stock 2.3.3 recovery file for the status! That would be easier to load than the sdk stuff.
update : both ruu files listed above show to be corrupt when unzipping.
Update: I installed a newer zip utility than the stock win xp one and it unzipped without any trouble. Moving on to the next step.
Update: all went well, except the "english" option, I chose english singapore. Installed cwm and rooted again. updated to 2.3.5. Thanks for the info above.
thank you!
raymerjacque said:
Alot of the guides floating around showing how to flash back to stock rom is incomplete ( missing a few steps ) and will result in boot loop most of the time. the correct procedure is :
Part 1 : Setting up Fastboot.
That is it, Fastboot tools is setup. Proceed to next guide.
Part 2 : Flashing guide.
after trying EVERYTHING else, this is the method that worked for me, i tried to cover every step possible ( alot of the other guides skipped few steps and that is where i got problems ).
hope this helps.
( PLEASE BE AWARE : This will remove recovery and root. if you flash back to stock rom using this method you will have to root your phone again. It will still be unlocked, just recovery and root will be removed. to re add recovery and root check part 3 below. )
Part 3 : Add recovery and root access back after installing stock rom.
it is recommended you update superuser to newer version and also install busybox.
Now that you have recovery installed you can also flash custom roms again.
I STRONLGY recommend once you reach this step that you make a backup of your rom via the bootloader recovery menu, that way you dont have to go through all this pain again next time.
The End !!!
feel free to post any problems you encounter below.
Click to expand...
Click to collapse
thank ! but dont update rom to 1.57.707.3,why?
Does the phone need an unlocked bootloader?
Can the be a way to debrand the firmware? Is the firmware attached the latest generic one?
Thanks
can't flash new htc status att rom 2.14.502.2 ruu security fail
Goatman5467 said:
No, I didn't make a real backup! I thought titanium backup would cover that, it didn't, so I have no backup of the stock stuff.
I have a HTC Status (aka chacha) US ver with att. I unlocked the boot loader by htc's site, worked fine. Then I rooted it with cmw, worked great.
Recently the ota 2.3.5 update (48mb) became available. I downloaded it and tried to install it, it failed with checksum. I know it is the cmw mod. How can I get the stock load 2.3.3 back onto my htc status? The above directions mention the "asia" load. Are the files mentioned generic for all phones with the exception of the cid?
p.s. It would be great if someone out there had the stock 2.3.3 recovery file for the status! That would be easier to load than the sdk stuff.
update : both ruu files listed above show to be corrupt when unzipping.
Update: I installed a newer zip utility than the stock win xp one and it unzipped without any trouble. Moving on to the next step.
Update: all went well, except the "english" option, I chose english singapore. Installed cwm and rooted again. updated to 2.3.5. Thanks for the info above.
Click to expand...
Click to collapse
A new ota update was available (1.57.707.3) but it won't install, it says the current rom seems to be altered and it refuses to install. So I went to htc.com/support and found the status page and downloaded the latest installer for 2.14.502.2 rom image. It fails with "security fail" under ruu in the phones bootloader screen.
The installer on the pc say's I must get the correct rom installer for my phone. I think it might have something to do with the asia chacha system and boot.img 2.3.3 stuff I installed.
Current software is android 2.3.5 and software 1.57.707.2
Is there anyway to get rid of cwm or force the new rom to install over the old?
Thanks man
Tried and made it
Work very fine except I cannot update sofware to newer version... Stuck on 1.54.401.2
Goatman5467 said:
A new ota update was available (1.57.707.3) but it won't install, it says the current rom seems to be altered and it refuses to install. So I went to htc.com/support and found the status page and downloaded the latest installer for 2.14.502.2 rom image. It fails with "security fail" under ruu in the phones bootloader screen.
The installer on the pc say's I must get the correct rom installer for my phone. I think it might have something to do with the asia chacha system and boot.img 2.3.3 stuff I installed.
Current software is android 2.3.5 and software 1.57.707.2
Is there anyway to get rid of cwm or force the new rom to install over the old?
Click to expand...
Click to collapse
I'm having the same issue.
You need the stock rom for the update to work. But frankly, I did not see any improvement. Battery life sucks.
I'm back to CM9
Goatman5467 said:
A new ota update was available (1.57.707.3) but it won't install, it says the current rom seems to be altered and it refuses to install. So I went to htc.com/support and found the status page and downloaded the latest installer for 2.14.502.2 rom image. It fails with "security fail" under ruu in the phones bootloader screen.
The installer on the pc say's I must get the correct rom installer for my phone. I think it might have something to do with the asia chacha system and boot.img 2.3.3 stuff I installed.
Current software is android 2.3.5 and software 1.57.707.2
Is there anyway to get rid of cwm or force the new rom to install over the old?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1752473
good lesson
Hi everyone.
I want to take my htc cha cha for warranty service by HTC. It means that I need to un-root the phone and take it back to official rom by HTC.
My phone is in Asia area, anyone has this stock/ official rom? Plzz share to me.
Thanks so much.
...
Hi ..
i have a problem with coming back to the stock arabic rom
the wizard stops and gives 2 errors !!
Signature check fails
Is there a way to switch off or bypass signature checking?
>fastboot flash system system.img
sending 'system' (254104 KB)...
OKAY [ 57.650s]
writing 'system'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 293.043s
>fastboot flash boot boot.img
sending 'boot' (2584 KB)...
OKAY [ 2.340s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 4.633s
thanks!, it worked for me
Link doesn't work
Dear, thank you for the super thread. But I have 2 problems (as I'm a newbie to HTC Chacha).
1. The download links for the files PH06IMG.zip & su-2.3.6.1-ef-signed.zip does not work. and 2. I cannot get the code from HTCDev website.
Please Help.
Thanks in advance.
Hello Everyone
Currently my ChaCha is running on GB 2.3.5 with version 1.57.720.1 (ASIA)
i want to the stock rom of this verison may be upgraded also
The links mentioned for the stock rom in this thread is not working
can i get the working links
P.S if i flash my ChaCha with CyanogenMod9 can i switch back to my stock verison without any issues (sorry if my question is annoying)
Thank you

(soft)bricked my device. Is there a fix?

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...

[ROOTING] Ulefone Be Touch 2 with TWRP recovery

Hi Folks,
Disclosure: No responsibility taken or accepted in any form if the following process failed.
As forum rules prevented me from posting links try to understand how to find referred files.
1. Prepare a PC with Windows 7 installed and the automatic Windows driver update lookup function possibly disabled.
2. Download BETA-SuperSU-v2.49.zip (appr. 4 MB, from chainfire eu and copy it to the phone's SD card or to an external micro SD card.
3. Download the latest stock ROM and flash tool packed together (e.g. 'Be-Touch-2_150702_s7yler.zip') from needrom com . Search for ulefone-be-touch-2.
4. Download TWRP recovery image file from needrom com . Search for be-touch-2-twrp-2-8-7-0.
Extract the rar archive and rename recoverye.img to recovery.img
5. Extract 'Be-Touch-2_150702_s7yler.zip' and replace the recovery.img file in the "Be-Touch-2_150702_s7yler\One Key Flashing(Be Touch 2_150702)\software" folder with the one from the TWRP archive (see point 2).
6. Install the MTK chipset driver (it works on Win7 only at the present time):
- Navigate to the "Be-Touch-2_150702_s7yler\One Key Flashing(Be Touch 2_150702)\Driver Auto Installer" folder.
- Open a Command Window to see what happens on the command line.
- Run Install.bat with real Administrator priviledges (in most cases Run as Administrator may not be enough - refer to UAC).
- Wait until the driver installation is finished. You will see on the screen if the drivers were installed successfully (e.g. "Driver install done").
7. Flashing ROM
Notes:
- Flashing ROM will wipe all your data. If you have not done a backup before you will permanently lose your data!
- The doc file containing pictures included in the zip file can also be followed.
- Do NOT format your phone with the flashing tool, that can result in lost IMEI.
- For anvanced users: the flash_tool.exe in the Smart Phone Flash Tool package can also be used only to flash recovery.img using an enclosed scatter.txt file.
a/ Open the Be-Touch-2_150702_s7yler\One Key Flashing folder and run SP_Facility_DL_Tool.exe
b/ Turn off the phone, take out the battery, press the Scan button in the SP_DownLoad window then connect your phone to the PC via USB.
c/ After the text "N/A+COM(x)" appears on the left hand side of the window disconnect your phone, reinsert the battery, press the Start button and reconnect your phone via the USB cable.
d/ Wait until the flashing utility finishes updating the phone (e.g. the process bar shows 100 % on yellow background and "DL OK" can be read to the left of the process bar).
8. After flashing, enter the TWRP custom recovery: press vol up + power to boot for a few seconds then install BETA-SuperSU-v2.49.zip from your (external) SD card.
9. You are done with rooting.
Fastboot
litokraz said:
- Flashing ROM will wipe all your data if you have not done a backup before!
- The doc file containing pictures included in the zip file can also be followed.
- Do NOT format your phone with the flashing tool, that can result in lost IMEI.
- For anvanced users: the flash_tool.exe in the Smart Phone Flash Tool package can also be used only to flash recovery.img using an enclosed scatter.txt file.
Click to expand...
Click to collapse
Again, for advanced users: You can also use fastboot (get it elsewhere) to flash just the TWRP recovery without wiping the rest of the phone: (e.g. "fastboot.exe flash recovery recovery-betouch2.img"), then use it to install supersu. You can also then flash the stock recovery back over it if you wish. Works like a charm.
marblemunkey said:
Again, for advanced users: You can also use fastboot (get it elsewhere) to flash just the TWRP recovery without wiping the rest of the phone: (e.g. "fastboot.exe flash recovery recovery-betouch2.img"), then use it to install supersu. You can also then flash the stock recovery back over it if you wish. Works like a charm.
Click to expand...
Click to collapse
Yes you are right. The method I described above also updates to the latest(?) Ulefone ROM as of 02-07-2015.
Even you can flash a Carlive recovery (tried and works) based on the downloadable from the "Ulefone Be Touch 2, 5.5 Inch Full HD, Metal Frame, MT6752 64-bit, 3050mAh Battery" thread Post #76. Carlive (originated from CWM) lacks the annoying splash screen which is included in TWRP.
UPDATE: Never mind, I got it. WooHoo
Guys, how do I get to Fastboot mode on my BE Touch 2? I tried power + volume down, yet it takes me to chinese menu I do not understand.
Odesláno z mého Be Touch 2 pomocí Tapatalk
Thank you Litakraz .... Good job done ... works like charm ..well explained
marblemunkey said:
Again, for advanced users: You can also use fastboot (get it elsewhere) to flash just the TWRP recovery without wiping the rest of the phone: (e.g. "fastboot.exe flash recovery recovery-betouch2.img"), then use it to install supersu. You can also then flash the stock recovery back over it if you wish. Works like a charm.
Click to expand...
Click to collapse
Hi, i have one Be Touch 2 and i can't find the fastboot mode in my recovery mode ( chinese recovery )
here is a screenshot of a similar recovery mode i got
youtu.be/RwpUyc7ig5w
Can you explain how to enter in Fastboot mode please ?
Thanks
Sorry for my bad english
UPDATE : I finally tried the command "adb reboot bootloader"
and after this I was able to flash recovery.img with fastboot (fastboot flash recovery recovery.img)
but i still can't boot on TWRP (still chinese bootloader)
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13540 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.207s]
finished. total time: 0.665s
UPDATE 2 :
My bad, to enter in TWRP mode reboot the phone using POWER+VOL UP
worked like a charm with the recovery img from needrom , thanks !
PS : /!\ AVOID TO UPDATE YOUR DEVICE OR YOU WILL BE BLOCKED ON THE ULEFONE LOGO !!! /!\
dkpiit said:
Hi, i have one Be Touch 2 and i can't find the fastboot mode in my recovery mode ( chinese recovery )
here is a screenshot of a similar recovery mode i got
youtu.be/RwpUyc7ig5w
Can you explain how to enter in Fastboot mode please ?
Thanks
Sorry for my bad english
UPDATE : I finally tried the command "adb reboot bootloader"
and after this I was able to flash recovery.img with fastboot (fastboot flash recovery recovery.img)
but i still can't boot on TWRP (still chinese bootloader)
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13540 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.207s]
finished. total time: 0.665s
UPDATE 2 :
My bad, to enter in TWRP mode reboot the phone using POWER+VOL UP
worked like a charm with the recovery img from needrom , thanks !
Click to expand...
Click to collapse
Tried that method, always get stuck in <waiting for device> !!!
Any advice ???
Heshamvido said:
Tried that method, always get stuck in <waiting for device> !!!
Any advice ???
Click to expand...
Click to collapse
Yes, just download and install adbdriver[DOT]com/downloads/
Thanks to the OP for the guide. I am now rooted & the phone is working perfectly.
Now just waiting for cyanogenmod to be released for it & I'll be a happy man.
Is there a way to root the Ulefone be touch one which is compatible with the last firmware ? (15/08/11)
The solution given by @Pasi_K don't work with the update
Darkstar2r1 said:
Is there a way to root the Ulefone be touch one which is compatible with the last firmware ? (15/08/11)
The solution given by @Pasi_K don't work with the update
Click to expand...
Click to collapse
I am curious on that too! Did you get it running?
I will try a different recovery.... hope that works.
hi guys..
anyone has NVRAM for this device..? it is black screen now but it is working..

Bricked? Please help!

My OPO is 100% stock currently running the second latest OTA update(coz I'd received a notification saying theres new update today but i haven't updated)
It was working perfectly fine until just now when I withdraw it from my pocket it shows the 1+ Powered by android loading screen.
I re-booted and it stuck at the same screen. I then boot into recovery and factory reset, wipe data wipe cache and boot and its still stucking at the same loading screen.
P/S : I was on wifi for a while in the cafe maybe it had downloaded the new OTA and maybe when the screen rubs against my pants in my pocket idk how it unlocks itself and it update itself with the downloaded(maybe) software update and eventually it dies. This might be one of the possibilities because if otherwise, it just dies itself without reason lel.
I've researched abit and someone suggested me to flash a stock rom using fastboot mode and PC adb command prompt which idk wtf is that lel. But in order to use that u need to unlock bootloader right, being 100% stock my bootloader is probably locked right?
omfg please guide me through this i need to solve this asap i dont have a backup phone. :silly::silly::silly::silly::silly::silly:
kingdew11 said:
My OPO is 100% stock currently running the second latest OTA update(coz I'd received a notification saying theres new update today but i haven't updated)
It was working perfectly fine until just now when I withdraw it from my pocket it shows the 1 Powered by android loading screen.
I re-booted and it stuck at the same screen. I then boot into recovery and factory reset, wipe data wipe cache and boot and its still stucking at the same loading screen.
P/S : I was on wifi for a while in the cafe maybe it had downloaded the new OTA and maybe when the screen rubs against my pants in my pocket idk how it unlocks itself and it update itself with the downloaded(maybe) software update and eventually it dies. This might be one of the possibilities because if otherwise, it just dies itself without reason lel.
I've researched abit and someone suggested me to flash a stock rom using fastboot mode and PC adb command prompt which idk wtf is that lel. But in order to use that u need to unlock bootloader right, being 100% stock my bootloader is probably locked right?
omfg please guide me through this i need to solve this asap i dont have a backup phone. :silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Follow this
http://forum.xda-developers.com/oneplus-one/help/solved-how-to-recover-oneplus-soft-t2864800
OR
Agai u can manually download any cm firmware
Then go to recovery
Factory reset
And flash desired firmware
FOLLOW this ( this is cm12 os)
http://webtrickz.com/guide-to-update-oneplus-one-to-cm12-lollipop-os/
If u don't like lollipop u can flash cm11s
FOLLOW this
http://www.technobuzz.net/update-oneplus-one-cm-11s-44s-resolve-several-bug-fixes/
note: u can find most guides on Google just search with keywords of your problems
Second mentioned flashing methods are most easiest prrocess
Factory reset and flash u r zip file
Problem solved. Detailed solutions for noobs like me!
OKAY here is what I DID. it may not work for u, but it worked for me. so if ur gonna follow these steps do it at ur own risk. and please dont expect me to helpp u to counter any special circumstances i.e. any condition not stated here coz im a perfect noob too, lel.
FYI this is called flashing roms in fastboot mode. And i had successfully flashed my OPO back into CM12.
STEPS :
Using a windows PC:
1) Download the UNIVERSAL ABD driver for Windows and freaking INSTALL IT.
2) Download the OnePlus One CM12 factory image “cm-12.0-YNG1TAS0YL-bacon-signed-fastboot.zip” (fastboot flashable package).
3) Download the flashing tools. ( it contains 4 things: adb.exe AdbWinApi.dll AdbUsbWinApi.dll and fastboot.exe)
the download links are available from this link:
ok im not allowed to attach links but u can search for it " webtrickz[dot]com how to flash cm12 factory image fastboot mode"
however, the steps given in the above link are crappy as well so follow mine =P just do the downloadings only from there.
4) Extract the 4 things from the flashing tools zip file into a folder, name it whatever****ing folder u want. we call it folder X.
5) and then extract all the things in the CM12 rom zip file into folder X.
6) Boot ur phone into fastboot mode simply by pressing and holding down the power button and the volume up button simultanoesly until u see "fastboot mode" with an Android face appears.
7) Connect ur phone to your PC with a USB cable. Now ur phone should be connected to the pc in fastboot mode.
8) open up folder X. then right click in folder X while holding down the Shift button, and click on "Open command window here"
p/s : this, I think, is like a special way to open up a cmd prompt used specifically for abd/fastboot. U can also actually open up cmd prompt normally but in order to do that you need to install idk some **** so that ur NORMAL cmd prompt will recognise abd or whatever **** it is. however, if u do that, u do not need to extract the CM12 rom files into folder X as the NORMAL cmd prompt will have the ability to, sorta like detect the CM12 ****s. anyways, forget it, just ****ing use the special way i.e. go to folder X , shift + right click to open up the SPECIAL cmd prompt)
9) a command prompt(cmd) should appear, Now check if u are connected by keying in "fastboot devices" in the cmd. Then the serial number of ur phone should turn up, and not " waiting for device" "devices not found" or any messages of that sort.
If the latter appears, idk how to help u sort that out urself lel.
10) Now u have to unlock the OEM in order for this flashing process to work. idk whats unlocking oem but just unlock it FFS. To do this, simply key in "fastbook oem unlock"
11) I think that under normal circumstances, a pop-up will appear in ur phone to let u choose if u really wanna unlock this oem thingy. BUT for me, my phone just rebooted back into the ****ing 1+ Powered by android screen idk why, but its alright i was on the right track as my oem has been unlocked. Then i powered off my phone and booted in back into fastboot mode once again. (FYI whenever I have to boot my phone to fastboot mode I disconnect the usb cable idk if this is necessary but thats what i DID)
12) go back to the CMD just now, and freaking paste the commands listed below into the CMD.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
13) Wait for several minutes, and when everything's done, the commands will stop at the last command which is "fastboot reboot"
Press Enter! and ur phone will reboot normally! =)
walpanmad said:
Follow this
http://forum.xda-developers.com/oneplus-one/help/solved-how-to-recover-oneplus-soft-t2864800
OR
Agai u can manually download any cm firmware
Then go to recovery
Factory reset
And flash desired firmware
FOLLOW this ( this is cm12 os)
http://webtrickz.com/guide-to-update-oneplus-one-to-cm12-lollipop-os/
If u don't like lollipop u can flash cm11s
FOLLOW this
http://www.technobuzz.net/update-oneplus-one-cm-11s-44s-resolve-several-bug-fixes/
note: u can find most guides on Google just search with keywords of your problems
Second mentioned flashing methods are most easiest prrocess
Factory reset and flash u r zip file
Click to expand...
Click to collapse
I can't flash it with recovery, as i cant 'insert' any ROM into my internal memory, as i cannot access my Internal memory, coz the phone wont boot?
However thank you so much! problem solved =)
kingdew11 said:
I can't flash it with recovery, as i cant 'insert' any ROM into my internal memory, as i cannot access my Internal memory, coz the phone wont boot?
However thank you so much! problem solved =)
Click to expand...
Click to collapse
Phone wont boot means?
If u are able to get in to recovery then its always possible to flash any official firmware without root with factory reset its easiest process to solve soft bricked device
First method mentioned is the same process u had done
(fastboot recover) but its automated process with OPO tollbox
Again fastboot method is usefull if u already enabled usb debugging in developer option before u went in to bootloop
I think u have previously enabled usb debugging
So it is also a method to recover u r problem
Any way its great news u got it worked

[SOLVED] Mi4i continuous reboot issue, Fastboot not detecting, MI4i stock recovery

I wanted to try brand new Nougat ROMs. So, I flashed twrp using Mi4i Toolkit and took backup of my MIUI8.
I tried many ROMs and decided to return to my MIUI8 nandroid backup.
But when I tried to restore the nandroid backup, It went successful but after restoring, Phone started rebooting in each 4-5 minutes. Searched and found that many people were facing this issue and they stayed on custom ROMs just because of this issue. So. I thought to create a new thread so this major problem can be easily solved.
How I got it fixed that,
REBOOT ISSUE​
Download Full stock MIUI ROM pack here : http://en.miui.com/download-263.html
1. Boot into TWRP
2. Wipe Dalvik/ART, Cache, Data (Internal Storage not required to wipe)
3. Flash ROM zip.
4. If It gets failed, No need to worry.
5. Go to advanced options in TWRP and select "Fix Contexts".
6. Try flashing Again.
7. It is successful now. Boot device and Perform a full reset ( again deleting Internal storage is not needed.)
8. Here you go, No reboots now, You get brand new performance of MIUI ROM flawlessly
Hit thanks if it works for you or ask me in replies.
Fastboot Not Detecting​
It has been noticed even after installing Minimal ADB and Fastboot drivers properly and performing all adb commands flawlessly, some computers can't detect devices in fastboot mode. Here's the solution.
1. Download Minimal ADB and Fastboot here : https://forum.xda-developers.com/showthread.php?t=2317790
2. Install and extract in a folder
3. Open command prompt in the folder.
4. connect your device in fastboot mode. (By holding power and vol- key, you can enter in fastboot mode)
5. Type
Code:
fastboot devices
and press enter
6. If it detects , then you've no problem.
7. If it doesn't detect go to device manager on your PC ( Press Windows+X, M on win10)
8.It might be detecting your device with some name, look for it.
9. Once you find, choose to uninstall its driver
10. Now click on action in menu bar and "Scan for hardware changes"
11. It now detects your device. If It doesn't, Uninstall and Install ADB drivers again and repeat above steps.
12.
Code:
fastboot devices
now should be showing your device.
MI4i Stock Recovery​
Found stock recovery on MIUI forum for MI4i but there's a problem with that. It shows option to wipe External SD (which isn't supported for MI4i), So I doubt this could be pulled from the same MI4i.
So, I backed up Genuine MI4i Stock Recovery from my MI4i with flashify.
Steps:
1. Boot into fastboot mode.
2. Connect with PC and open command prompt in the same folder of fastboot and ADB
3. Put this file https://docs.google.com/uc?id=0B98eukQ9ePc-NnljcmxjWWJvUHc in same folder
4. Type
Code:
fastboot flash recovery mi4istockrecovery
press enter
5. Cheers! You're now on stock recovery.
6. Boot into recovery mode to verify.
Hit thanks if helped
madhurajkumar said:
7. If you are unable to flash stock recovery, bootloader maybe locked, unlock the bootloader and then try again.
Click to expand...
Click to collapse
The bootloader never locks for the Mi4i ? why'd you add a step for this ?
sharan.nyn said:
The bootloader never locks for the Mi4i why'd you add a step for this ?
Click to expand...
Click to collapse
Read it somewhere, so thought to add. Edited
madhurajkumar said:
I wanted to try brand new Nougat ROMs. So, I flashed twrp using Mi4i Toolkit and took backup of my MIUI8.
I tried many ROMs and decided to return to my MIUI8 nandroid backup.
But when I tried to restore the nandroid backup, It went successful but after restoring, Phone started rebooting in each 4-5 minutes. Searched and found that many people were facing this issue and they stayed on custom ROMs just because of this issue. So. I thought to create a new thread so this major problem can be easily solved.
How I got it fixed that,
REBOOT ISSUE
Download Full stock MIUI ROM pack here : http://en.miui.com/download-263.html
1. Boot into TWRP
2. Wipe Dalvik/ART, Cache, Data (Internal Storage not required to wipe)
3. Flash ROM zip.
4. If It gets failed, No need to worry.
5. Go to advanced options in TWRP and select "Fix Contexts".
6. Try flashing Again.
7. It is successful now. Boot device and Perform a full reset ( again deleting Internal storage is not needed.)
8. Here you go, No reboots now, You get brand new performance of MIUI ROM flawlessly
Hit thanks if it works for you or ask me in replies.
Fastboot Not Detecting
It has been noticed even after installing Minimal ADB and Fastboot drivers properly and performing all adb commands flawlessly, some computers can't detect devices in fastboot mode. Here's the solution.
1. Download Minimal ADB and Fastboot here : https://forum.xda-developers.com/showthread.php?t=2317790
2. Install and extract in a folder
3. Open command prompt in the folder.
4. connect your device in fastboot mode. (By holding power and vol- key, you can enter in fastboot mode)
5. Type
and press enter
6. If it detects , then you've no problem.
7. If it doesn't detect go to device manager on your PC ( Press Windows+X, M on win10)
8.It might be detecting your device with some name, look for it.
9. Once you find, choose to uninstall its driver
10. Now click on action in menu bar and "Scan for hardware changes"
11. It now detects your device. If It doesn't, Uninstall and Install ADB drivers again and repeat above steps.
12.now should be showing your device.
MI4i Stock Recovery
Found stock recovery on MIUI forum for MI4i but there's a problem with that. It shows option to wipe External SD (which isn't supported for MI4i), So I doubt this could be pulled from the same MI4i.
So, I backed up Genuine MI4i Stock Recovery from my MI4i with flashify.
Steps:
1. Boot into fastboot mode.
2. Connect with PC and open command prompt in the same folder of fastboot and ADB
3. Put this file https://docs.google.com/uc?id=0B98eukQ9ePc-NnljcmxjWWJvUHc in same folder
4. Type
press enter
5. Cheers! You're now on stock recovery.
6. Boot into recovery mode to verify.
Hit thanks if helped
Click to expand...
Click to collapse
can you help us about hardbricked Mi4i? what should we do a proper guide can make a huge support to me
There is no led, only access to fastboot mode but when i tried to flash stock rom via miflash the whole completed in just 2 sec and phone doesn't boot up completely and stuck again
aa_vi said:
can you help us about hardbricked Mi4i? what should we do a proper guide can make a huge support to me
There is no led, only access to fastboot mode but when i tried to flash stock rom via miflash the whole completed in just 2 sec and phone doesn't boot up completely and stuck again
Click to expand...
Click to collapse
If you can boot into fastboot mode,
Flash twrp from your pc using Minimal adb and fastboot.
If you face issues and need help about this, Ask me
i flashed a fastboot mode rom through cmd everything goes perfect there is no issue in the whole process but after reboot it does not reboot only show mi logo and turn off then the display of device fluctuate again and again i never experience this issue
suggest something
aa_vi said:
i flashed a fastboot mode rom through cmd everything goes perfect there is no issue in the whole process but after reboot it does not reboot only show mi logo and turn off then the display of device fluctuate again and again i never experience this issue
suggest something
Click to expand...
Click to collapse
Which ROM?
This issue is called Bootloop.
1.Flash twrp through cmd
2. Wipe everything ( except the internal storage, as it's not needed )
3. Try repeating the same.
If you again face the issue, try downloading flashable zip of the same ROM and try flashing via twrp.
madhurajkumar said:
Which ROM?
This issue is called Bootloop.
1.Flash twrp through cmd
2. Wipe everything ( except the internal storage, as it's not needed )
3. Try repeating the same.
If you again face the issue, try downloading flashable zip of the same ROM and try flashing via twrp.
Click to expand...
Click to collapse
Thanks! it worked but there is a little bit problem the internal. memory of device is reducing to 2.57 gb instead of 12.xx gb what the hell is this the partion of memory is reduced to this much
aa_vi said:
Thanks! it worked but there is a little bit problem the internal. memory of device is reducing to 2.57 gb instead of 12.xx gb what the hell is this the partion of memory is reduced to this much
Click to expand...
Click to collapse
Partition Issues there.
Boot into twrp
Go to wipe
Select System
Tap on "Repair or Change File System"
Confirm the action
Repeat the same for data and cache partitions ONE BY ONE ( you can select one partition once)
Now after formatting all the partitions,
Wipe all partitions
Flash the ROM zip through TWRP
Reboot
madhurajkumar said:
Partition Issues there.
Boot into twrp
Go to wipe
Select System
Tap on "Repair or Change File System"
Confirm the action
Repeat the same for data and cache partitions ONE BY ONE ( you can select one partition once)
Now after formatting all the partitions,
Wipe all partitions
Flash the ROM zip through TWRP
Reboot
Click to expand...
Click to collapse
when we select system it show a warning in that is says some roms and kernels didn't support this and at bottom some options are shown
EXT2
EXT3
EXT4
FAT
exFAT
F2FS
which option supports the process?
aa_vi said:
when we select system it show a warning in that is says some roms and kernels didn't support this and at bottom some options are shown
EXT2
EXT3
EXT4
FAT
exFAT
F2FS
which option supports the process?
Click to expand...
Click to collapse
Try Ext4
Help
help my xiaomi mi4i cannot solved it ,
target reported max download size of 268435456 bytes
sending 'recovery' (32768 KB)...
OKAY [ 1.030s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 1.404s
dstyo said:
help my xiaomi mi4i cannot solved it ,
target reported max download size of 268435456 bytes
sending 'recovery' (32768 KB)...
OKAY [ 1.030s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 1.404s
Click to expand...
Click to collapse
What is your miui version currently? And which twrp you use that has 32mb? 3.1.1.1 only 24mb if im not mistaken
yumm91 said:
What is your miui version currently? And which twrp you use that has 32mb? 3.1.1.1 only 24mb if im not mistaken
Click to expand...
Click to collapse
i'm not used twrp , but i install mi4istockrecovery still failed. my miui version is 7 , now my phone stuck in mi logo if i restarted my phone then always started fastboot mode , i still confused
dstyo said:
i'm not used twrp , but i install mi4istockrecovery still failed. my miui version is 7 , now my phone stuck in mi logo if i restarted my phone then always started fastboot mode , i still confused
Click to expand...
Click to collapse
I would suggest you to first install TWRP, then flash the stock ROM from TWRP and then flash mi4i stock recovery in fastboot mode. ( As I faced similar issue and got it solved this way. )
dstyo said:
i'm not used twrp , but i install mi4istockrecovery still failed. my miui version is 7 , now my phone stuck in mi logo if i restarted my phone then always started fastboot mode , i still confused
Click to expand...
Click to collapse
The easiest way to do this is by dowloading fastboot ROM for your miui version. Once you extract the files, there will be a recovery.img inside.
Then u can flash the recovery via fastboot flash recovery recovery.img to return the recovery to stock.
Done.
Help needed
I hae this same problem my MI4i is stuck in fastboot mode it's not even going off. Device's bootloader is locked so can't flash twrp
aamir93 said:
I hae this same problem my MI4i is stuck in fastboot mode it's not even going off. Device's bootloader is locked so can't flash twrp
Click to expand...
Click to collapse
Try to boot into twrp by using this command
rename downloaded twrp img file to twrp.img
connect in fastboot mode and in Minimal ADB ad Fastboot cmd, type
Code:
fastboot boot twrp.img
wich rom ?
aa_vi said:
Thanks! it worked but there is a little bit problem the internal. memory of device is reducing to 2.57 gb instead of 12.xx gb what the hell is this the partion of memory is reduced to this much
Click to expand...
Click to collapse
I try rom global stable and china dev but just stay bootlop in miui boot
Mi4i twrp flash without data loss
madhurajkumar said:
If you can boot into fastboot mode,
Flash twrp from your pc using Minimal adb and fastboot.
If you face issues and need help about this, Ask me
Click to expand...
Click to collapse
Mi4i device stuck at mi logo (Came to know this is called Bootloop, Note that not flashed or installed anything on device automatically this issue happened) .As non technical person i need help from you guys to get my device alive. I need to save all my data in the mobile so Googled some topics and came to know that for this i have to flash TWRP in fastboot mode where we can able to save the data . Can anybody help me on this?
Really appreciate your support ....!!!!

Categories

Resources