Database Info

CWM flashing not possible

Hey guys,
my bootloader is unlocked - so far, so good. however though, when I want to flash cwm, I'm getting this result:
C:\xyz>fastboot flash recovery cwmrecovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6632 KB)...
OKAY [ 0.558s]
writing 'recovery'...
OKAY [ 1.838s]
finished. total time: 2.397s
so it looks successful. But I still have the stock recovery. When I'm trying the rom manager from the playstore alternatively, I'm getting an error right aways after the cwm download (looks as if nothing happened in between). Error message is simply "An error occurred while flashing your recovery"
Any suggestions?
Thanks!

After you fastboot flash recovery, IMMEDIATELY reboot to recovery. Do not reboot to Android.
Take a backup. Then boot to Android... should stick.

Yeah, I learned that the hard way....
Sent from my SPH-D700 using Tapatalk 2

jeffreyjicha said:
Yeah, I learned that the hard way....
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Weird! I had the similar issue as described above. I'm able to successfully flash the CWM flash to the SPH-710 for me. However, can't boot INITIALLY to the CWM boot; It's able to successfully go into normal boot; But Volume-UP, Center button Power button, just blinks the custom boot screen once then the screen becomes blank for some time.
Can't get out of the Stock ROM boot up to CWM;

Bricked my Honor 6 H60-L04 Indian variant while trying to install .zip files.

I recently upgraded my phone to EMUI 2.3 to EMUI 3.1 (Android lollipop 5.1), and installed CWM and rooted it. Two days ago I have downloaded cerebus app from Rom manager app and it installed by rebooting into recovery. Then a couple of minutes after rebooting the phone keep on crashing and shutting down randomly and when I tried to reboot it won't reboot but stuck for sometime at the Honor logo and since then I've tried every possible flashing and resetting I found here on XDA.
I still have access to fastboot and that is how I am able to flash ROM s and when I am trying to use the three button method it is stopping at 90 %. I couldn't even access it if my phone is not connected to my PC.
Now I've exhausted all the procedures in here and some other sites.
Somebody please suggest me something, help me.
Thank you.

Follow these steps to get it back to stock:
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
NOTE: If the manual flashing doesn't works or you get any errors, then first try only the force update method, i.e Putting the UPDATE.APP from which you extracted the files in dload folder of your external SDCARD and pressing Vol UP + Vol DOWN + Power button simultaneously after switching off your phone.

Thanks Brother.
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.

yessasikiran said:
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
Click to expand...
Click to collapse
I have the same problem with a H60-L12.
I noticed, that I get that error when I try to flash a boot.img from a different EMUI version pack.
In my case, the phone had EMUI3.0 and I can write any of the EMUI3.0 boot.img's, but cannot write a boot.img from an EMUI 3.1 or EMUI4.0 update.app

yessasikiran said:
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
Click to expand...
Click to collapse
Which recovery image are you using?
Sent from my PLK-L01 using Tapatalk

yessasikiran said:
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
Click to expand...
Click to collapse
Try
download adb.zip
http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip
extract adb.zip
download
TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
https://drive.google.com/drive/folders/0By4NGNfKPDLBMW9jTy1fOHBGTm8?tid=0By4NGNfKPDLBQTZ2S0licGhjNmc
copy TWRP in adb folder
put the devices in fastboot mode
run cmd.exe as administrator and type this command
fastboot devices
fastboot flash recovery TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
fastboot reboot
If does not work, try to reinstall HiSuite or install the lastet version
http://consumer.huawei.com/minisite/HiSuite_en/index.html
Nexus H791 using Tapatalk

Thnks you for replying so quickly.
I'm using "Honor 6_Firmware_H60-L04_Android 6.0_EMUI 4.0_C675B822_India_Flipkart India"
which is the latest stock firmware for Honor 6 H60-L04.
I have tried to force update with the thee button method and it worked (completed 100%)but unfortunately the phone is now in bootloop. This definitely made the phone a little better but once it got to the EMUI update screen its restarting again.
Thanks again man I though nobody would reply for this. its been so long since ive posted this.

Thank you for replying so quickly.
I'm using "Honor 6_Firmware_H60-L04_Android 6.0_EMUI 4.0_C675B822_India_Flipkart India"
which is the latest stock firmware for Honor 6 H60-L04.
I have tried to force update with the thee button method and it worked (completed 100%)but unfortunately the phone is now in bootloop. This definitely made the phone a little better but once it got to the EMUI update screen its restarting again.
Thanks again man I though nobody would reply for this. its been so long since ive posted this.

Thanks man, I'll get back to you once ive done this.
Nah man, Same thing again.
F:\Android\Honor root\TWRP>fastboot flash recovery TWRP_2.8.7.0_EN_EMUI_4.0_v4.i
mg
target reported max download size of 471859200 bytes
sending 'recovery' (14468 KB)...
OKAY [ 1.507s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.535s
Thank you for guiding me through.

yessasikiran said:
Thank you for replying so quickly.
I'm using "Honor 6_Firmware_H60-L04_Android 6.0_EMUI 4.0_C675B822_India_Flipkart India"
which is the latest stock firmware for Honor 6 H60-L04.
I have tried to force update with the thee button method and it worked (completed 100%)but unfortunately the phone is now in bootloop. This definitely made the phone a little better but once it got to the EMUI update screen its restarting again.
Thanks again man I though nobody would reply for this. its been so long since ive posted this.
Click to expand...
Click to collapse
You have to use that last Lollipop package which you were on before, try the three button method with that and report.

DigiGoon said:
You have to use that last Lollipop package which you were on before, try the three button method with that and report.
Click to expand...
Click to collapse
Hey,
Yeah man I'll do that now and will get bact to you.
Thanks man

DigiGoon said:
You have to use that last Lollipop package which you were on before, try the three button method with that and report.
Click to expand...
Click to collapse
Yeah man, I've tried to flash recovery of the last Lollipop Rom and still the same message FAILED (status read failed (Too many links)).
Is there any other way that we can try to unbrick the device?
Thank you man.

yessasikiran said:
Yeah man, I've tried to flash recovery of the last Lollipop Rom and still the same message FAILED (status read failed (Too many links)).
Is there any other way that we can try to unbrick the device?
Thank you man.
Click to expand...
Click to collapse
Have you used Honor Multitool? http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176

zinko_pt said:
Have you used Honor Multitool? http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176
Click to expand...
Click to collapse
Yes sir,
Same output and stopping after trying to flash recovery while using the in brick option.
Thank you.

yessasikiran said:
Yes sir,
Same output and stopping after trying to flash recovery while using the in brick option.
Thank you.
Click to expand...
Click to collapse
When you flashed manually, did you used the same IMG files from the last installed ROM?
You can´t extract and flash IMG files of a LP ROM in a last installed MM ROM and vice versa.

yessasikiran said:
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
Click to expand...
Click to collapse
bro type fastboot devices and check how many available devices it shows...if it shows more than 1 device then stop the other device...if thr is only device then try stopping adb.exe and fastboot.exe(if thr)....then again type command "fastboot devices"

yessasikiran said:
Yes sir,
Same output and stopping after trying to flash recovery while using the in brick option.
Thank you.
Click to expand...
Click to collapse
Try using the latest version of the developer ROM
chetan_dua said:
bro type fastboot devices and check how many available devices it shows...if it shows more than 1 device then stop the other device...if thr is only device then try stopping adb.exe and fastboot.exe(if thr)....then again type command "fastboot devices"
Click to expand...
Click to collapse
Check in task manager to see if you have adb.exe running. Stop all and try again.

Still bricked or have u fixed it yet?

goldfinv said:
Try using the latest version of the developer ROM
Check in task manager to see if you have adb.exe running. Stop all and try again.
Click to expand...
Click to collapse
bro i was trying to help another person that was solution according to me for him
Sry if it looks like question...

TWRP not working on NXT-L29C432B320

Hi,
I've installed the ROM NXT-L29C432B320, I then wanted to reinstall TWRP using fastboot.
Got the following output:
C:\adb-1>fastboot flash recovery TWRP-2.8.7.0-ENG.img
target reported max download size of 471859200 bytes
sending 'recovery' (31330 KB)...
OKAY [ 0.990s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 1.226s
C:\adb-1>fastboot reboot
rebooting...
finished. total time: 0.022s
C:\adb-1>​
When attempting to boot into recovery mode (using 'Volume up' + 'power')the screen is stuck at the bootloader:
Your device has been unlocked and can't be trusted.
To learn more, visite:
htt*p://zh.ui.vmallcom/emotiondownload.php?mod=restore
Your device is booting now...​
The screen is stuck here, noting is happening.
Already attempted to refllash mutliple times. No difference.
Already attempted to use 'Volume up' + 'Volume down' + 'power', does not work either.
Pressing the 'Volume up' button during boot (without 'power'), shows me the Huawai eRecovery.
Please help me making TWRP work again as I'm now unable to flash any new rom on it!

tobi061 said:
Hi,
I've installed the ROM NXT-L29C432B320, I then wanted to reinstall TWRP using fastboot.
Got the following output:
C:\adb-1>fastboot flash recovery TWRP-2.8.7.0-ENG.img
target reported max download size of 471859200 bytes
sending 'recovery' (31330 KB)...
OKAY [ 0.990s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 1.226s
C:\adb-1>fastboot reboot
rebooting...
finished. total time: 0.022s
C:\adb-1>​
When attempting to boot into recovery mode (using 'Volume up' + 'power')the screen is stuck at the bootloader:
Your device has been unlocked and can't be trusted.
To learn more, visite:
htt*p://zh.ui.vmallcom/emotiondownload.php?mod=restore
Your device is booting now...​
The screen is stuck here, noting is happening.
Already attempted to refllash mutliple times. No difference.
Already attempted to use 'Volume up' + 'Volume down' + 'power', does not work either.
Pressing the 'Volume up' button during boot (without 'power'), shows me the Huawai eRecovery.
Please help me making TWRP work again as I'm now unable to flash any new rom on it!
Click to expand...
Click to collapse
the same thing happened to me , you have the FRP locked you can not do anything about the only thing this program is Phoenix DC Unlocker in this link https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/155916-dc-phoenix
Price 15 USD release me totally , is the only way friend ..... I bought yesterday and have 72 hours to use private message to see if it's still my username and password .... greetings

Try use the more recent TWRP 3.0.2 for EMUI4.1
Use Vol up+down at power on to get to recovery and should work, this is the one that worked for me...

MuPp3t33r said:
Try use the more recent "htt*ps://drive.googlecom/file/d/0B5I_q70mNuR4N2l2cjRJbFlNSFE/view?pref=2&pli=1"]TWRP 3.0.2 for EMUI4.1
Use Vol up+down at power on to get to recovery and should work, this is the one that worked for me...
Click to expand...
Click to collapse
Seems to work, the TWRP launched. THANKS A LOT!

tobi061 said:
Hi,
I've installed the ROM NXT-L29C432B320, I then wanted to reinstall TWRP using fastboot.
Got the following output:
C:\adb-1>fastboot flash recovery TWRP-2.8.7.0-ENG.img
target reported max download size of 471859200 bytes
sending 'recovery' (31330 KB)...
OKAY [ 0.990s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 1.226s
C:\adb-1>fastboot reboot
rebooting...
finished. total time: 0.022s
C:\adb-1>​
When attempting to boot into recovery mode (using 'Volume up' + 'power')the screen is stuck at the bootloader:
Your device has been unlocked and can't be trusted.
To learn more, visite:
htt*p://zh.ui.vmallcom/emotiondownload.php?mod=restore
Your device is booting now...​
The screen is stuck here, noting is happening.
Already attempted to refllash mutliple times. No difference.
Already attempted to use 'Volume up' + 'Volume down' + 'power', does not work either.
Pressing the 'Volume up' button during boot (without 'power'), shows me the Huawai eRecovery.
Please help me making TWRP work again as I'm now unable to flash any new rom on it
Click to expand...
Click to collapse

3abdell said:
Please help me making TWRP work again as I'm now unable to flash any new rom on it
Click to expand...
Click to collapse
Which version of TWRP are you using? (Did you use the one I posted here previously?)

3abdell said:
tobi061 said:
Hi,
I've installed the ROM NXT-L29C432B320, I then wanted to reinstall TWRP using fastboot.
Got the following output:
C:\adb-1>fastboot flash recovery TWRP-2.8.7.0-ENG.img
target reported max download size of 471859200 bytes
sending 'recovery' (31330 KB)...
OKAY [ 0.990s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 1.226s
C:\adb-1>fastboot reboot
rebooting...
finished. total time: 0.022s
C:\adb-1>​
When attempting to boot into recovery mode (using 'Volume up' + 'power')the screen is stuck at the bootloader:
Your device has been unlocked and can't be trusted.
To learn more, visite:
htt*p://zh.ui.vmallcom/emotiondownload.php?mod=restore
Your device is booting now...​
The screen is stuck here, noting is happening.
Already attempted to refllash mutliple times. No difference.
Already attempted to use 'Volume up' + 'Volume down' + 'power', does not work either.
Pressing the 'Volume up' button during boot (without 'power'), shows me the Huawai eRecovery.
Please help me making TWRP work again as I'm now unable to flash any new rom on it
Click to expand...
Click to collapse
Hi 3abdell,
The version you flashed is an old one. You must flash EMUI4.1 version of Twrp.
Sent from my HUAWEI NXT-L29 using XDA-Developers mobile app
Click to expand...
Click to collapse

I am really embrassed to ask, but what is TWRP ? and what isnthe use of it ?

mseif said:
I am really embrassed to ask, but what is TWRP ? and what isnthe use of it ?
Click to expand...
Click to collapse
For #### sake
http://bfy.tw/6Jox

Can't enter TWRP

I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?

BoredDude said:
I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?
Click to expand...
Click to collapse
You can try to boot directly into twrp with "fastboot boot TWRP.img"

zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s

zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
BoredDude said:
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s
Click to expand...
Click to collapse
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!

ChazzMatt said:
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!
Click to expand...
Click to collapse
I fixed it erasing the TWRP folder in my internal storage

Fastboot mode freezing

Hi. I was following the instruction<oneplusDOTgadgethacksDOTcom/how-to/update-your-oneplus-7-pro-without-losing-root-no-computer-needed-0208078> to upgrade the os on the pro. One step is to install TWRP. I followed the instruction<twrpDOTme/oneplus/oneplus7proDOThtml> and run "fastboot boot twrp-xxxx.img". It finished and my phone displayed "fastboot mode" and freezed there. I tried to hold the power button and hold power button & volume down button. Neither worked. Aappreciate any help.
I only have a macbook pro.
Log:
> fastboot boot twrp-xxxx.img
< waiting for any device >
Sending 'boot.img' (31704 KB) OKAY [ 0.682s]
Booting OKAY [ 0.121s]
Finished. Total time: 0.868s
screenshot: i.ibb.co/pRtwJ4L/IMG-1533.jpg

buy pc
other solution is maybe to use usb2.

superflb said:
Hi. I was following the instruction<oneplusDOTgadgethacksDOTcom/how-to/update-your-oneplus-7-pro-without-losing-root-no-computer-needed-0208078> to upgrade the os on the pro. One step is to install TWRP. I followed the instruction<twrpDOTme/oneplus/oneplus7proDOThtml> and run "fastboot boot twrp-xxxx.img". It finished and my phone displayed "fastboot mode" and freezed there. I tried to hold the power button and hold power button & volume down button. Neither worked. Aappreciate any help.
I only have a macbook pro.
Log:
> fastboot boot twrp-xxxx.img
< waiting for any device >
Sending 'boot.img' (31704 KB) OKAY [ 0.682s]
Booting OKAY [ 0.121s]
Finished. Total time: 0.868s
screenshot: i.ibb.co/pRtwJ4L/IMG-1533.jpg
Click to expand...
Click to collapse
You can upgrade the is without twrp,just go for local upgrade in updater app.
Also the terminal should show downloading boot.img message which is not shown in your case and it is evident that something is wrong.
Mess around a bit and you will figure it out