Help
I tried to relock my bootloader but when the device restarted it went straight to error mode.
I managed to boot straight back to full system but whenever I restart it goes back to error mode. I cant enter fastboot or recovery mode.
I sont know what to do now any help
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.
How can I unlock bootloader without fastboot? If I attempt to enter fastboot or anything that requires reboot I end up on that screen.
Hmm....
Have you tried rebooting to fastboot using adb?
Johnny TDN said:
Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.
Click to expand...
Click to collapse
Johnny TDN said:
Hmm....
Have you tried rebooting to fastboot using adb?
Click to expand...
Click to collapse
I tried but still get to error mode.....I have tried many times
Then i don't know anymore dude. Have you tried reinstalling the firmware using the 3 button method?
elliotn said:
I tried but still get to error mode.....I have tried many times
Click to expand...
Click to collapse
Hello
tested with the toolkit 0.0.0.12.
to see if he recognizes the phone.
he should at least write your serial number.
if that is the case.
you can use DC-unlocker. to open FRP and can be the bootloader.
just an idea.
Dc unlocker needs cash and it doesn t always work.
I am doubting buying DC,unlocker in case,it doesn't work and I will lose money.... I will try toolkit.
3 button upgrade doesn't work either.
I have the same problem after I tried to relock my bootloader using SRKToolHuawei-STABLE-V1.3-20160619 with my bootloader code.
Have you found a solution?
I can boot back into os b394 after I let the battery run out to 0%
I haven't found a way to repair my recovery and fastboot yet because rebooting into fastboot always get's me back to that first error
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
Then I have to wait for my battery to run out again
Any help to get fast boot and a working recovery back would be appreciated.
Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method
shankarjdhv125 said:
Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method
Click to expand...
Click to collapse
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..
Same problem for me
No way to shutdown the phone, someone have solved?
Now I'm waiting for the battery to full drain
Hi guys i ve made mistake because i wanted to update to latest release media pad m3 but i could not be able to boot to stock recovery after i flash recovery img extracted from update.app and second time i flash recovery2.img to erecovery partition and i got the same issue error Func No 11(recovery image) and Error NO 2 (load failed) . I also put the update.app to dload folder on sd card but update system is not starting i press volume up and down and power button at same time but is not working.I tried also with huawei multitool but is not working is not recognize my device. Please guys is any other solution to fix this ?Thank You!
I just fixed after power off device and then press volume down and plug the usb cable to pc and i was able to recognize my device and i have use huawei multiTool to unbrick my tablet media pad m3 and has work.
Almost the same problem, help please!!!
Hi guys someone can help me? I have a Honor 9 lite(LLD-L31). Android version 8.0
I apologize but I'm a new user and i don't have much practice with modding in general.
I tried to install root permission in my device. I get bootloader unlock code by DC-unlocker and installed TWPR on my device.
When i went in recovery the error " Failed to unmount '/system'(Device or resource busy)" rushed, so I tried to format data in order to give partition available. I tried again to flash file.zip but the search was empty so I downloaded a most recent version(3.2.3) of TWPR in recovery ramdisk.
Now if i try to log into recovery mode appear the same error (Error! func NO 11 / NO 2).
I can do everything aside going in recovery mode. How can I resolve it? Is it possible to reset to factory settings and try again?
I hope I have explained well the problem.
elliotn said:
3 button upgrade doesn't work either.
Click to expand...
Click to collapse
how about this 3 button method??
Astarothkun said:
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..
Click to expand...
Click to collapse
Could you write down the steps you took to get back in fastboot for me? I'm having troule geting there myself after draining battery.
I fixed it after nothing else here worked.
So this is mostly so I dont ever forget the solution again, but also to possibly help others.
I also have to say that I had the problem with an P8 Lite, but all my problems matched almost exaclty, so It might help you too.
And a third disclaimer: I have no idea if you can flash the stock firmware without having the bootloader unlocked.
If you dont have it unlocked, try this wonderful updated guide: [Links are disabled for me so google this: "Droidhunter unlock huawei bootloader" and pick the article by droithunter.com]
And yes DC-Unlocker, suprisingly actually works (at least for me) and buying their bootloader unlock code was worth the 4 bucks.
So here is the solution:
1. Somehow, however needed get into fastboot. As I couldn't use the volume/power key combo myself, I somehow force reset the phone, pressing various buttons until I managed to boot into it again. I then used the adb bridge to boot into fastboot (google how to connect adb, then use "adb reboot bootloader" to get into the fastboot menu).
2. Download your phone models default stock rom/Update.app (also google that).
3. Extract the Update.app file.
4. Download and use the HuaweiUpdateExtractor tool and open the Update.app file (google again helps).
5. Select the "09.recovery.img" entry (the one with the green arrow on the left), rightclick and select "extract selected" and save it somewhere where you can find it.
6. Open your Fastboot console on PC (its often the same as the ADB console used before, especially if you use Minimal Fastboot and ADB, which I would recommend).
7. Make sure your phone is in Fastboot mode (not recovery) and connected to the pc.
7.1 Make sure your bootloader is unlocked. It might work with a locked one because youre just flashing stock firmware but eh might break more. Its worth the 4 bucks to unlock the bootloader first. (and yes DC unlocker looks super sketchy but somehow it actually worked for me and wasnt a scam).
8. Flash a custom recovery onto the phone (pretty much the same way you flash twrp, but instead of the twrp image you use the .img file you just extracted from the Update.app; Also dont try flashing twrp directly, it will probably not work).
The command to do so is: "fastboot flash recovery [filepath to the .img file without the brackets]".
9. Use the command "fastboot reboot".
10. If your phone doesnt boot normally, use the key combinations to get into the normal recovery screen and recover from a file or whatever (other guides should work from here).
Extra Steps:
As my recovery image was obviously so broken that even flashing twrp on top of it didnt work until I flashed the original reovery image, I went into my phones settings and did a factory reset. Directly after I installed twrps (see google) and set it up so it had full control. Afterwards I rooted and installed LinageOS cause frick EMUI rn).
Hope this helps anyone. If you have any questions feel free to ask me.
Related
Hey guys,
I was hoping you might help me as I was struggling to find an answer through google search.
After using the ZUK Z1 (Cyanogen OS 12.1 with the latest update), a few days ago the phone suddenly restarted and entered an endless restart loop
I've tried wiping the data, the cache and the user files.
I've tried applying the latest CyanogenOS zip for the Z1 either through sideload or locally from the device.
Nothing worked and I'm becoming very frustrated
I thought that maybe if I could wipe the system partition and then apply the COS zip than maybe it would work.
Does anybody have any ideas?
Thanks in advance,
Yoav.
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too too.
Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone has any idea what that means? Does that mean that it is a hardware failure?
yoavk said:
Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
Does anyone has any idea what that means? Does that mean that it is a hardware failure?
Click to expand...
Click to collapse
Ok, so first, don t panic. If you re able to acces recovery and fastboot mode, there is a strong hope. I have Windows 7 on my PC, btw.
I tried the qpst tool to flash the stock, but i couldn t. That is why i turned to the Zuk Tool Kit, which did the trick for me.
To use this tool, FIRST OF ALL YOU MUST INSTALL ADB AND FASTBOOT. you can find varius tutorials about this on te interent. I provide you some, too:
http://forum.xda-developers.com/showthread.php?t=2588979
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
It was hard for me too to understand what is going on at first, but i did some research on the topic, and i got it.
After you installed adb, you can check if it is instaled by running the command "adb version" in CMD:
You should recieve something like this if it is installed.
After you installed fastboot and adb, install the Zuk Toolkit following the steps provided in the thread of Lenvo Zuk toolkit. Download cygwin, open cygwin terminal and drag start.sh from zuk toolkit folder into terminal window, press Enter, and you will have the menu open like this:
Here, just naviagte by writing the number corresponding to the menu you want to access and hitting enter.
Under "6. Do some basic ADB and Fastboot commands.
" coomands, you will have this menu:
Do note that [fASTBOOT] marked commands will work only when your phone is in fastboot mode. To acces your fast boot mode of your phone, just select "reboot to bootloader" option from recovery menu.
Once you managed to reach this state, you can put your phone in fastboot mode, and try the command "10. [Fastboot] Reflash to stock using a manually downloaded factory image."....
IF this doesn t work, try to flash the stock rom via sideload option from recovery menu of your phone. To do this, you must chose the sideload option from recovery menu. Download the stock signed rom from here https://cyngn.com/support(NOT THE FASTBOOT ONE, JUST THE SIGNED ONE.) Rename your stock rom zip file you just downloaded "sideload" and place it on desktop. Then use THE command "4. [ADB] Sideload a zip file.
" from zuk toolkit to flash the rom. Also you must have the phone connected to pc with the USB-c cable during the whole process, of course. If it works, your phone will show the animation of flashing procees on its screen. Wait until the phone stops, chose wipe dalvik and reboot.
Use the snipping tool or PrtSc to take screen images from where you are stuck or you don t know what to do, and post them here.
Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
C:\ WINDOWS\ system32> fastboot -i 0x2b4c oem device-info
< waiting for device >
Click to expand...
Click to collapse
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg
yoavk said:
Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg
Click to expand...
Click to collapse
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
When you chose the install Update pacakge option, what options are displayed on your phone?
Also, if u installed qpst, you shoudl have in your PC a program callled QFIL, which is the flasher tool for all lenovos including ZUK. You must flash the zui stock rom using qfil. Read this thread for more info and downloads: http://forum.xda-developers.com/zuk...ui-version-t3265741/post64865607#post64865607
Also, here is a thread of a guy who had pretty much the same problem as you and managed to flash the stoc using QFIL : http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257
Extentho said:
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
Click to expand...
Click to collapse
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.
yoavk said:
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.
Click to expand...
Click to collapse
I think you could try un-bricking it by yourself. It is not that hard. But if those guys from coolicool will change your phone, that s ok too. Blease be advised that rooting voids warranty...soo
Lucky me I didn't have the chance to do it
I didn't even have the chance to unlock the bootloader
Does anyone here have any experience with the guys over at coolicool?
i flashed coldbird's zip for capacitive touch on the fingerprint sensor. got into an endless restart loop after that. to every option, the toolkit replies command not found.
eg: ./xposeduninstallbootloop.sh: line 128: adb: command not found
followed by whatever option was ordered, that has been done successfully but can see no change.
Try this
https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056
Easy bro easy, the steps that you are following are a bit confusing, aren't they?
Please tell me the current status of your phone. I might be able to help.
Have rooted my phone, unlocked.
Had all updates up to B140. Wanted to update to B170. Managed to do that by flashing all the image files from B121 and then did update on all zipfiles up to B170
So far so good.
But guess what...no recovery any more!!!!!
Started to reflash all the files one by one from original B100 files. Just from basic i thought.
Now the phone wont start and gets into bootloop.
Doesn´t matter if i reflash userdata.img, boot.img, system.img....and recovery.img.
even if i put update.app (from B100 whole image) into a microsd and start up the phone...it will not enter recovery mode at all. EVEN if it sais OK when flashing using command.
fastboot flash recovery recovery.img
is sais OK. But the phone just bootloops.
The only thing that works now is entering fastboot & rescue mode. (bootloader)
I have NO idea at all what to do now. Have even tried honor 7 multi tool....chosed unbrick....putted in all the desired files under files/unbrick (boot, cust, system,recovery), Everything sais ok after flashing.
But phone will not enter recovery mode at all?
this is starting to annoying me...
PLEASE....help....
crowhater said:
Have rooted my phone, unlocked.
Had all updates up to B140. Wanted to update to B170. Managed to do that by flashing all the image files from B121 and then did update on all zipfiles up to B170
So far so good.
But guess what...no recovery any more!!!!!
Started to reflash all the files one by one from original B100 files. Just from basic i thought.
Now the phone wont start and gets into bootloop.
Doesn´t matter if i reflash userdata.img, boot.img, system.img....and recovery.img.
even if i put update.app (from B100 whole image) into a microsd and start up the phone...it will not enter recovery mode at all. EVEN if it sais OK when flashing using command.
fastboot flash recovery recovery.img
is sais OK. But the phone just bootloops.
The only thing that works now is entering fastboot & rescue mode. (bootloader)
I have NO idea at all what to do now. Have even tried honor 7 multi tool....chosed unbrick....putted in all the desired files under files/unbrick (boot, cust, system,recovery), Everything sais ok after flashing.
But phone will not enter recovery mode at all?
this is starting to annoying me...
PLEASE....help....
Click to expand...
Click to collapse
You need to put the full rom of either B100 or B121 or B130 on your SD card in the dload folder then boot into updater mode.(it's either volume up or both volume up and down) make sure you do not have a USB plugged in or you will get an error!
Basically if you can boot into fastboot mode then there is always a way!
I may have forgotten a step but check the forums and look for the rooting guide. In there you will find my tale of misery and how to fix it!
hmmm
Thanx mate....appreciate your help...
. I followed your instructions. Had forgotten not to have the usb cable inserted.
Got into bootloader again and it said... error recovery ...think it was #11...and then #2 (errors)
Tried to flash recovery again...success...as it said OK. stock recovery that is.
Now back into boot lock...restarts all the time.
Inserted whole image..3Gig file.. .update.app (note...update.app....not update.zip) into micro sd card in folder dload
Tried to restart the phone ...volume up...+ down...+ power (no usb connected)
But it wont enter to the mode where the update is beeing processed at all. ...just looping the boot....restarts the phone after 8seconds after honor logo appears.
Very strange........
So after the cable is plugged out...i can not enter neither fastboot...nor recovery. Need to insert the USB to be able to enter fastboot mode again.
Seems that something strange happens with recovery part..?? EVEN if is sais ok during flash...something happens...
can one force the update to start via fastboot? or something else?
try to connect it to HiHuawei suite at first! Sometimes it help to break the bootloop.
If you have used the B170 update file, the recovery has changed! Now you need to install B300 MM rollback file at first.
The update procedure with B300 rollback breaks at nearly 98% but it doesn’t mater! You will get into status B300.
Then you can flash B121 full (dload). hope this should help.
BTW: there are quiet more partitions active as you think!! I think, you will have mixed conditions now.
The own way to correct it is to flash a full backup now!
DON’T FORGET TO FULLY UN ROOT AT FIRST!! NOT ONLY UN INSTALL; FULL REMOVE OF SuperSU!
crowhater said:
Thanx mate....appreciate your help...
Seems that something strange happens with recovery part..?? EVEN if is sais ok during flash...something happens...
can one force the update to start via fastboot? or something else?
Click to expand...
Click to collapse
To get out of bootloop and turn off the phone, go to eRecovery. Press volume up and connect to PC. HOLD until phone drop into it. There you will be able to power off the phone. Next three buttons switch the flashing process
erecovery???
inside!out said:
To get out of bootloop and turn off the phone, go to eRecovery. Press volume up and connect to PC. HOLD until phone drop into it. There you will be able to power off the phone. Next three buttons switch the flashing process
Click to expand...
Click to collapse
Well..the problem is that i can not enter anything else except for bootloader (fastboot)
Tried to press volume up... + pwr. holding for 10 seconds. Nothing.
same without usb...nothing.
Tried with volume down.....+pwr. .without usb.... nothing....
both up & down....with...without usb....nothing.
*******
Only that works is USB cable ...volume down and pwr.
When in fastboot. Computer sound is heard and HiSuite is started...but no connection at all....
I have as i said a whole imagefile in sd card. Both in root of sdcard (update.app). and inside dload folder (update.app)...but it wont boot to start install process at all.
I went from B170 to B100...and after that it did not work.
The reason...was "only" because recovery was lost when i had B170...just wanted to redo everything..no nothing works.
sight...
can not enter erecovery at all......
crowhater said:
Well..the problem is that i can not enter anything else except for bootloader (fastboot)
Tried to press volume up... + pwr. holding for 10 seconds. Nothing.
same without usb...nothing.
Tried with volume down.....+pwr. .without usb.... nothing....
both up & down....with...without usb....nothing.
can not enter erecovery at all......
Click to expand...
Click to collapse
Did I wrote anything about the power button???
I said hold the volume up and pluci cable to the PC, and hold it until you get to eRecovery.
inside!out said:
Did I wrote anything about the power button???
I said hold the volume up and pluci cable to the PC, and hold it until you get to eRecovery.
Click to expand...
Click to collapse
Sorry...forgot to write that i also tested that. Held the volume up button for 60 seconds and it rebooted 4 times during that time.
tested to plug in cable both when seeing the logo...and also directly after the logo disappears...but no success...
inside!out said:
Did I wrote anything about the power button???
I said hold the volume up and pluci cable to the PC, and hold it until you get to eRecovery.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have debranded phone. My eRecovery in chinese. You need last item this menu.
Sent from my HONOR 7 via TapaTalk
---------- Post added at 16:04 ---------- Previous post was at 16:00 ----------
crowhater said:
Sorry...forgot to write that i also tested that. Held the volume up button for 60 seconds and it rebooted 4 times during that time.
tested to plug in cable both when seeing the logo...and also directly after the logo disappears...but no success...
Click to expand...
Click to collapse
try it after vibro
inside!out said:
I have debranded phone. My eRecovery in chinese. You need last item this menu.
Sent from my HONOR 7 via TapaTalk
---------- Post added at 16:04 ---------- Previous post was at 16:00 ----------
try it after vibro
Click to expand...
Click to collapse
inside!out..
yes i know....i have had this erecovery before....i was able to get into this menu before. But i can not enter it now. It is gone. I can not reflash TWRP aswell...neither stock recovery. EVEN if it sais success...OK....it still loops around the boot.
Thanks for your patience and help though....
WOW.......i bit on my way...
JUst maneged to flash the B170 img files....all of them.... extracted everything from B170 update using extractor...and run all of them ...using fastboot (some of the img were not able to load. just userdata...boot..cache....and recovery)
And now it restarts.... JIHAAAAAA....
...but i do not have any recovery at all.....the phone starts...but no recovery possibility at all.
Tried to shut down.......ok.
Phone totally off. presses volume up....inserted usb cable...after a while it booted up...but still after 8 seconds it reboots without entering any recovery at all.
But now the phone starts without reboot loop.
Okay..that means that we are back on track....with the first problem. I can not reboot into a recovery mode.....neither using TWRP...or stock recovery....
hmmmm
Hmm...okay ...
Just did all the updates until B170.
The TWRP_Honor7_EN.img seems to be the problem. I have now erecovery...the stock recovery. But when flashing using fastboot flash recovery TWRP_Honor7_EN.img and then try to enter the recovery...it fails.
sooo..... is there some new TWRP that works for B170?
Added---
Here is the problem.....one needs to use this one..
http://forum.xda-developers.com/honor-7/development/recovery-twrp-2-8-7-0-hwplk-plk-l01-t3290306
SOLVED...!!!!!!!!!!!!
crowhater said:
Hmm...okay ...
Just did all the updates until B170.
The TWRP_Honor7_EN.img seems to be the problem. I have now erecovery...the stock recovery. But when flashing using fastboot flash recovery TWRP_Honor7_EN.img and then try to enter the recovery...it fails.
sooo..... is there some new TWRP that works for B170?
Added---
Here is the problem.....one needs to use this one..
http://forum.xda-developers.com/honor-7/development/recovery-twrp-2-8-7-0-hwplk-plk-l01-t3290306
SOLVED...!!!!!!!!!!!!
Click to expand...
Click to collapse
in my honor 7 multi-tool used this TWRP for Android 6.0 and B170/B190.
i had flashed a recovery with the RASHR app and was fallen into a bootlopp!
I have taken HUAWEI EXTRACTOR and extract all files from B121 to a folder on my pc.
Than i flashed Boot.img; cust.img; recovery.img; recovery2.img; Cache.img: Data.img
IF YOU GET A ERROR DURING FLASHING A FILE, PLEASE RESTART DEVICE INTO FASTBOOT AGAIN AND CONTINUE WITH THE NEXT FOLLOWING IMAGE!
after next reboot, i was able to start my system! I had make a rollback to B300 (B313 to interim) and than flashed the B121 followed from B170. This solved my problem. Maybe it can help you too.
After trying to flash the latest 7.1.1 cm 14 ropms many people ended up in bootloop where your phone switch on ,shows mi logo and rebbot again. Many where not able to enter recovey mode also.. Now i come up with a perfect soluton for you all on how to fix these issues in your phone..Lets Get started..
If anything goes wrong iam not responsible.Do it At your Own Risk.
Requirements
------------------
1. Enter edl .rar (attached below)
2.Miui Stock Rom (FastBoot). Download it from(only use this version) here
3.Phone Must have Charge of 50% or more.
4.Unlock Boot loader.zip (Attched Below)
6.MIPhone Tools and install it .Get it from here
6.Extract all the file
7. PDA Net.(Optional,but installing will be useful). Get it from here
Once you have all of the file we can move on
Steps
------
1. Put Your Phone into fastboot mode by pressing Vol Down and power button at same time.
2.Connect your Phone With Your PC
3.Run EDL Mode.exe from the zip Enter edl.. Now your phone must be in edl mode. You can see a light blinking at the top of your phone.
4. From the Unlock Boot Loader folder copy "emmc_appsboot.mbn" to the rom folder ie)
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global--> images--> paste it there (replace/overwrite if existing)
5. Once the above step is done, Open MIFlash tool as administrator. Browse the folder
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global and select it..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6.From the drop Down Menu Select Advanced.
7.Set Fastboot Script As Flash_ALL.Bat.
8.Set Flash Programmer As prog_emmc_firehose_8976_ddr.mbn from images folder.
9. Set RAW Xml File as rawprogram*.xml from images folder
10. Set Patch XML File as patch*.xml from images folder.
11. Video Help HERE.... Watch from 2.40 (Ignore the other portion,We dont need that Part)
Special [email protected] for the video.. I didn't made that video..
12. Once The Above step is done. Click REFRESH OPTION,and you will see Phone detected By The Name COMXX.(XX will be a number)
13.Click Flash and Wait for some time and allow the phone to reboot.
14.Once all the step is done your phone will be good to use..:fingers-crossed: :fingers-crossed:
UNLOCKING BOOT LOADER AND INSTALLING TWRP AGAIN
-------------------------------------------------------------------------
1.Once Your Phone Reboots successfully enable USB Debugginf From Developer Option.
2.Connect Your phone to your PC and Open CMD as administrator.
3.Type in "adb devices".
4. Cmd will show a random number and Device (Everyone will be knowing this,but for info only iam writing it here)
5.Type "adb reboot bootloader". Now your phone will boot into fastboot mode.
6.Type "fastboot oem device-info" to get device status.
7.Type "fastboot oem unlock-go" to unlock bootloader.
8.Again type "fastboot oem device-info" to check to find if device is unlocked.(Do not reboot YET)
9. Now Downlaod TWRP from HERE
10. Now Got to the folder containig TWRP . By holding the Shift Key Of key Board ,right click the mouse and select OPEN COMMAND WINDOW HERE.
11. Type "fastboot flash recovery recovery_filename.img"
12.Type "fastboot reboot".
You Phone will be good to go. If anything goes wrong or you have any doubt Comment Below do not pm me..i will not reply..
If this thread helpef you thumbs up and do comment and shre this post
So i do not need to unlock the boot loader before using MiTool to flash phone via EDL
ahh988 said:
So i do not need to unlock the boot loader before using MiTool to flash phone via EDL
Click to expand...
Click to collapse
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool
adithyan25 said:
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool
Click to expand...
Click to collapse
I did that but phone is still stuck . I'm getting infinite boot animation ?
ahh988 said:
I did that but phone is still stuck . I'm getting infinite boot animation ?
Click to expand...
Click to collapse
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed
adithyan25 said:
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed
Click to expand...
Click to collapse
I am stuck at boot animation with the three white dots spinning for ever ? will try to do as you said
I tried fastboot oem unlock-go but i get response: token verification failed and device still stuck on bootanimation
well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful
nitephoenix said:
well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful
Click to expand...
Click to collapse
always my pleasure
For some mi unlock stucks at 50%.. I was one of them...every time I try fails...so I found this was the only way for those who can't access it using mi unlock
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
Yeah...I know that...but it does not support volte. .only abhisheks fw sprt volte
nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks
Pleroma said:
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks
Click to expand...
Click to collapse
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe
nitephoenix said:
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe
Click to expand...
Click to collapse
I used to flash it via twrp ..(by deleting bootllader file) followed by flashing lazyflasher...I didn't faced any prblm yet
Mine behaves different
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.
sarabeshsab said:
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.
Click to expand...
Click to collapse
Probably the problem with bootloader file
not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.
Jjleininger said:
not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.
Click to expand...
Click to collapse
Download eiter China based ROM or ROM from post.
Mi flash tool have many prolems.
Some tips:-
Make sure driver enforcement is disabled in PC.
All drivers including PDA net is installed.
Copy paste the unlocked bootloade file inside images folder and replace original one. Even after tryig this method it fails try my other method unbrick viafasrboot
uhm, this does not work for some reason...
i did everything as you said but in the end it just says cathasrophic error and something
After flashing i get Mi logo, vibration and reboot, please help
I wanted to reinstall the stock rom (B360). I booted into TWRP and for some reason I wiped System, Dalvik cache, cache and internal memory (I dont know why I did that). Then I installed the Firmware but it failed probably because my frp was locked and I didnt know about it. Then I rebooted and now I cant boot to the system. When I boot into TWRP it just hangs on the TWRP logo and doesnt go on, eRecovery doesn't work. I can boot into fastboot. Its says that phone is unlocked but frp is locked. I hope that there's a way to unbrick my phone without dc-phoenix
DeathBell said:
I wanted to reinstall the stock rom (B360). I booted into TWRP and for some reason I wiped System, Dalvik cache, cache and internal memory (I dont know why I did that). Then I installed the Firmware but it failed probably because my frp was locked and I didnt know about it. Then I rebooted and now I cant boot to the system. When I boot into TWRP it just hangs on the TWRP logo and doesnt go on, eRecovery doesn't work. I can boot into fastboot. Its says that phone is unlocked but frp is locked. I hope that there's a way to unbrick my phone without dc-phoenix
Click to expand...
Click to collapse
Install the stock recovery and then stock ROM. (You can install the stock recovery when your phone is in bootloader mode and you install it by the cmd in Windows)
Tiagohsoares said:
Install the stock recovery and then stock ROM. (You can install the stock recovery when your phone is in bootloader mode and you install it by the cmd in Windows)
Click to expand...
Click to collapse
Sorry for the late reply. Whenever I try to flash the stock recovery it says FAILED (remote: Command not allowed):crying:. I tried both fastboot flash recovery_ramdisk and fastboot flash recovery, neither of them worked.
After doing some more research (like 3+ hours) I think that the error can't be easily fixed:crying:. Some solutions that I've found that may work all involve either disabling USB debugging and then rebooting and re-enabling it or somthing like that which I can't do since I can't boot into the system or relocking and then unlocking my bootloader which I also can't do without dc-phoenix since my frp is locked. Also I don't know if the dload method will work as I can't access the sd card when I plug my phone to the PC. It may be possible to push files there using adb but I'm not sure if it will work even when I get the right files to my sd card. So unless you guys don't have a better solution, I'm probably going to buy the HCU + DC-Phoenix 3 day licens for 20€ (still a lot better then changing my motherboard for 100+€). Also here's the adb window with the error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: I'm not going to buy DC-Phoenix until somebody says that there's no way to fix my device without it. It's so unfortunate that I probably can't fix my phone for free even when things like fastboot, charging and adb are working and bootloader is unlocked.
DeathBell said:
After doing some more research (like 3+ hours) I think that the error can't be easily fixed:crying:. Some solutions that I've found that may work all involve either disabling USB debugging and then rebooting and re-enabling it or somthing like that which I can't do since I can't boot into the system or relocking and then unlocking my bootloader which I also can't do without dc-phoenix since my frp is locked. Also I don't know if the dload method will work as I can't access the sd card when I plug my phone to the PC. It may be possible to push files there using adb but I'm not sure if it will work even when I get the right files to my sd card. So unless you guys don't have a better solution, I'm probably going to buy the HCU + DC-Phoenix 3 day licens for 20€ (still a lot better then changing my motherboard for 100+€). Also here's the adb window with the error.
Edit: I'm not going to buy DC-Phoenix until somebody says that there's no way to fix my device without it. It's so unfortunate that I probably can't fix my phone for free even when things like fastboot, charging and adb are working and bootloader is unlocked.
Click to expand...
Click to collapse
It seems that you need just to perform FRP unlock with HCU client.... After that you can flash twrp, etc....
Also you can try method from @vovan1982
"Small manual: removing frp lock.
If you have frp_lock and have not TWRP. Download in FF (FirmwareFinder) third file of firmware (example: update_full_WAS-L21_hw_ru.zip), unpack. Run DCPhoenix small update.app, and when DC Phoenix open back_door, detach usb-cable. On PC run cmd.exe and flash this frp.img"
Good luck!
Alexxxx1 said:
It seems that you need just to perform FRP unlock with HCU client.... After that you can flash twrp, etc....
Also you can try method from @vovan1982
"Small manual: removing frp lock.
If you have frp_lock and have not TWRP. Download in FF (FirmwareFinder) third file of firmware (example: update_full_WAS-L21_hw_ru.zip), unpack. Run DCPhoenix small update.app, and when DC Phoenix open back_door, detach usb-cable. On PC run cmd.exe and flash this frp.img"
Good luck!
Click to expand...
Click to collapse
I fixed my phone using the 1th method in dc-phoenix already :laugh:, the HCU frp thing didnt work because my device model wasn't supported. And I didn't know where to flash the frp.img file. But now my device is working great:fingers-crossed:.
if someone read this or newers, watch this video: it works for frp lock
Hi. First i want to say is sorry for my bad english.
I unlocked the bootloader of my g6 and i have flashed Twrp recovery, but when i try to go to recovery mode i have this messege : " your device cannot be checked for corruption . please lock the bootloader ".
Can anyone tell me how to resolve this because i want to flash custom roms but i cant because i cant go to recovery mode..
Help me please.
Sorry if there was a topic like this, but i can not find a solution to this problem.
Now i see when i go to ADB folder and write the command " adb reboot recovery " after the reboot it says " No Command " and i cant do nothing .. I cant flash.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you mean this screen ^ that is a normal screen that appears, with every power up / restart, after the bootloader has been unlocked.
I think of it as a "red badge of courage".
As to the question about adb commands, what is it that you are trying to accomplish?
Some more information is needed to help you.
What is your model (h870, us997)?
Are you sure you properly installed twrp (reboot to bootloader, fastboot flash recovery twrp.img)?
Which version of twrp did you use (official, Melina, eliminater's (recommended))?
Regarding your adb problem - do you fail to reboot to recovery using adb from within? Have you tried to turn it off and on again?? I mean, turn it off and try the button combination to enter recovery (turn on holding vol- and power, when logo appears, release power and quickly press again and keep holding both until "factory reset", confirm twice).
Information is key!
PS as the previous poster wrote - if you unlock your bootloader you get the warning screen, just ignore it.
niksjdm said:
Hi. First i want to say is sorry for my bad english.
I unlocked the bootloader of my g6 and i have flashed Twrp recovery, but when i try to go to recovery mode i have this messege : " your device cannot be checked for corruption . please lock the bootloader ".
Can anyone tell me how to resolve this because i want to flash custom roms but i cant because i cant go to recovery mode..
Help me please.
Sorry if there was a topic like this, but i can not find a solution to this problem.
Now i see when i go to ADB folder and write the command " adb reboot recovery " after the reboot it says " No Command " and i cant do nothing .. I cant flash.
Click to expand...
Click to collapse
the "your device cannot be checked for corruption" screen is normal, it happens when you unlock the bootloader, no issue there, in order to install TWRP you must:
1. plug your phone in and type 'adb reboot-bootloader' to boot into fastboot mode
2. flash the twrp image via 'fastboot flash recovery TWRPIMAGENAME.img'
3. This is important!: type 'fastboot reboot' and hold the rear button and volume down during the shutdown!, when the LG logo shows up quickly release JUST the rear button and press/hold it again, you should see a factory reset prompt screen, press yes both times, and you should be dumped into TWRP, at this point you can reboot from within TWRP and you should be fine.
Explanation:
the stock LG rom with overwrite the recovery if it determines it has been changed, by booting to TWRP before booting the ROM, TWRP will modify the ROM to stop it from overwriting the recovery allowing TWRP to stay after booting.
I hope this helps
Mnky313 said:
the "your device cannot be checked for corruption" screen is normal, it happens when you unlock the bootloader, no issue there, in order to install TWRP you must:
1. plug your phone in and type 'adb reboot-bootloader' to boot into fastboot mode
2. flash the twrp image via 'fastboot flash recovery TWRPIMAGENAME.img'
3. This is important!: type 'fastboot reboot' and hold the rear button and volume down during the shutdown!, when the LG logo shows up quickly release JUST the rear button and press/hold it again, you should see a factory reset prompt screen, press yes both times, and you should be dumped into TWRP, at this point you can reboot from within TWRP and you should be fine.
Explanation:
the stock LG rom with overwrite the recovery if it determines it has been changed, by booting to TWRP before booting the ROM, TWRP will modify the ROM to stop it from overwriting the recovery allowing TWRP to stay after booting.
I hope this helps
Click to expand...
Click to collapse
THANK YOU SO MUCH .. It works .. The problem was in the buttons.
I have another problem.. When i try to go to recovery..the only what i see is the logo of TWRP and then the phone just reboot and i cant do nothing.. The phone is h870. What i have to do to have normal TWRP because i want to root it..
Try another twrp version. For Oreo afaik only Melina and Eliminater (which is a continuation of Melina) work. I recommend Eliminater's version, it's up to date (v3.2.3) and backup works - at least for me. I'm on H870 Oreo 20b.
For Nougat I have no experience, as I got my phone recently and never downgraded. But as I understand it from others' experiences, for full custom ROM functionality (e.g. fingerprint) Nougat bootloader is preferable. Search the forum, the information is there!
niksjdm said:
I have another problem.. When i try to go to recovery..the only what i see is the logo of TWRP and then the phone just reboot and i cant do nothing.. The phone is h870. What i have to do to have normal TWRP because i want to root it..
Click to expand...
Click to collapse
grushnickij said:
Try another twrp version. For Oreo afaik only Melina and Eliminater (which is a continuation of Melina) work. I recommend Eliminater's version, it's up to date (v3.2.3) and backup works - at least for me. I'm on H870 Oreo 20b.
For Nougat I have no experience, as I got my phone recently and never downgraded. But as I understand it from others' experiences, for full custom ROM functionality (e.g. fingerprint) Nougat bootloader is preferable. Search the forum, the information is there!
Click to expand...
Click to collapse
Yes, I use Melina TWRP, flash Version rel_o2 (or latest) using the method I said above.
Where i can find those versions of Twrp ( melina, eliminater ) ?
niksjdm said:
Where i can find those versions of Twrp ( melina, eliminater ) ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-g6/development/twrp-t3828254
https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-2-1-unofficial-fixes-t3722199
https://forum.xda-developers.com/lg-g6/development/recovery-twrp-lg-g6-us997-unofficial-t3629883
https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-1-x-t3627595