Hello,
I tried many guides on web for changing the firmware from 5.1.2.0A to 5.1.2.0G without any luck.
The phone goes in bootloop and the only way to restore it is to flash again the original 5.1.2.0A firmware.
Could someone please suggest me a good guide or give me a good hint?
Thanks much!
rizxda said:
Hello,
I tried many guides on web for changing the firmware from 5.1.2.0A to 5.1.2.0G without any luck.
The phone goes in bootloop and the only way to restore it is to flash again the original 5.1.2.0A firmware.
Could someone please suggest me a good guide or give me a good hint?
Thanks much!
Click to expand...
Click to collapse
1. turn off device
2.Press VOLUME UP+POwer key, (press Power until you see logo, VOLume UP until you go in Recovery)
3. Connect phone to computer,the computer determined removable disk Recovery, empty volume of 998 MB
4. Copy the firmware in the drive and disconnect the phone
5. DON'T Reboot!! JUST select the firmware update. You can do it without wipe data. Click Start (retry, many may be different)
6. After flashing the phone is turned on again. If root was included - will again include.
hello..
is that work on meizu pro 5?
Converting the phone from A to G isn't as simple as the classical firmware upgrade. The version is checked and flash is denied if not the same (A =>A only)
Look at this tutorial and use method 2 or 3 : https://meizufans.eu/forum/topic/25...ional-firmware-on-your-chinese-mainland-meizu
It's fine for A=>G or A=>I
Didn't worked for me
I'm the owner of a meizu pro 5 runing Flyme 5.1.2.0A and none of these two methods worked for me. When I run the terminal commands both on phone or computer, it seems to do something, but when I reboot the phone always go to bootloop, and the only way to use it again is flashing the A version of the frimware again via recovery.
BernatVM said:
I'm the owner of a meizu pro 5 runing Flyme 5.1.2.0A and none of these two methods worked for me. When I run the terminal commands both on phone or computer, it seems to do something, but when I reboot the phone always go to bootloop, and the only way to use it again is flashing the A version of the frimware again via recovery.
Click to expand...
Click to collapse
Assuming you applied the correct commandline, you have to wait several minute (about 10) to the dd=xxxxx process end. Prompt should appears when OK.
naboleo said:
Assuming you applied the correct commandline, you have to wait several minute (about 10) to the dd=xxxxx process end. Prompt should appears when OK.
Click to expand...
Click to collapse
Yes, I know. The command line says the process has finished, then the phone is inresponsibe (As it has to, following the explanation on the meizufans web tutorial). Is only then when I reboot my phone and enter to bootloop.
BernatVM said:
Yes, I know. The command line says the process has finished, then the phone is inresponsibe (As it has to, following the explanation on the meizufans web tutorial). Is only then when I reboot my phone and enter to bootloop.
Click to expand...
Click to collapse
After flash, you can try to reboot in recovery (volup+power), clear data and then reboot normaly. First restart is a bit longer but you knows it already.
PS: did it a week ago with lastest G, without trouble
Thank you for your help. I would try it!
le9ion said:
1. turn off device
2.Press VOLUME UP+POwer key, (press Power until you see logo, VOLume UP until you go in Recovery)
3. Connect phone to computer,the computer determined removable disk Recovery, empty volume of 998 MB
4. Copy the firmware in the drive and disconnect the phone
5. DON'T Reboot!! JUST select the firmware update. You can do it without wipe data. Click Start (retry, many may be different)
6. After flashing the phone is turned on again. If root was included - will again include.
Click to expand...
Click to collapse
U r right!
I have just used this way to save my pro5 xD
Telefonu A dan G ye değiştirdim. Fakat Bootloader unlock yapamıyorum. Update.zip yüklenmiyor. Hiç birşey olmuyor :S
Related
Hey guys
i just wiped all my data and tried to reboot my nexus, but now it's been stuck on the google logo for ages...
trying to flash to stock + unroot with nexus toolkit doesn't work, any way to unbrick it?
please help...
do you have fastboot driver installed?
Step 1: Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
Step 2: Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
Step 3: Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly.
now go back to Nexus 4 toolkit. Flash back to stock.
badboy47 said:
do you have fastboot driver installed?
Step 1: Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
Step 2: Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
Step 3: Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly.
now go back to Nexus 4 toolkit. Flash back to stock.
Click to expand...
Click to collapse
works
thank you very much
fabian.m said:
works
thank you very much
Click to expand...
Click to collapse
Then, press on his THANKS button. That's the way we have to measure who contributes or not in xda-developers. Please, let's follow rules...
luiseteyo said:
Then, press on his THANKS button. That's the way we have to measure who contributes or not in xda-developers. Please, let's follow rules...
Click to expand...
Click to collapse
well.. technically thanking isn't in the rules.
exb0 said:
well.. technically thanking isn't in the rules.
Click to expand...
Click to collapse
It is in the good behaviour and politeness rules. Not everything is written.
Hi guys i got a similar problem, i flashed a walkman .zip wiped cache and dalvik cache. Then the phone booted into google logo, and it went all black. The display is on but its all black. The problem is i cannot power off the device. Holding all buttons just restarts the phone. What can i do?
I was on latest PA rom
Qbsti said:
Hi guys i got a similar problem, i flashed a walkman .zip wiped cache and dalvik cache. Then the phone booted into google logo, and it went all black. The display is on but its all black. The problem is i cannot power off the device. Holding all buttons just restarts the phone. What can i do?
I was on latest PA rom
Click to expand...
Click to collapse
reflash your rom. reboot your device, hold volune down before it reboots to get into the bootloader then recovery.
simms22 said:
reflash your rom. reboot your device, hold volune down before it reboots to get into the bootloader then recovery.
Click to expand...
Click to collapse
Thanks simms, i managed to get into fast boot between the reboots, and I flashed the rom and gapps.
Damn it scared me even more then the red light issue that happened to me last month.
Qbsti said:
Thanks simms, i managed to get into fast boot between the reboots, and I flashed the rom and gapps.
Damn it scared me even more then the red light issue that happened to me last month.
Click to expand...
Click to collapse
not booting after flashing something or modding something is the easiest of all to fix, just reflash the rom(gapps and kernel too if need be), no need to wipe anything. since i test all the trinity kernels before any get released, and pre-kernels, i get many that dont boot my device or bootloop(among some other funky behaviors), reflashing a good kernel always works
I left my phone for a few minutes, and when I picked it up it was bootlooped again, and i had to use fastboot again. What should I do now? Maybe a factory reset would help me. I don't want more unexpected bootloops. :/
swyped from my nexus 4
Qbsti said:
I left my phone for a few minutes, and when I picked it up it was bootlooped again, and i had to use fastboot again. What should I do now? Maybe a factory reset would help me. I don't want more unexpected bootloops. :/
swyped from my nexus 4
Click to expand...
Click to collapse
Try another rom. You might have downloaded corrupted zips. Also, make sure you flash the things you need first. Eg, flash rom and gapps. Don't restore anything if you're using titanium backup. Try restarting the phone, see if it gets into a bootloop. If it doesn't, then try restoring apps from TB. (if you use TB.)
Hi!
I´ve got a big problem. Today i flashed the new PA version, but it seems that the download had some issue. I could install it but after a while, I wanted to reboot the phone and it got stuck at the Google logo. I can only access fastboot mode and recovery.
So the problem is, i made a full wipe, so i have no rom on the sdcard anymore. Also I am now able to enable the debbuging mode. I tried every toolkit i couzld find, but everyone needs debugging mode enabled. windows doesnt recognize the phone ( it says unkown device). So i tried to install the adb drivers, but nothing happens.
i wanted to try to push a rom with adb on the phone but it says no device found. i am such a noob, i hope some can help me.
thx
I captured the lollipop update that came out today. I have a nandroid backup and I'm going for the update. We will see if the new tethered CWM works to get root back... Stay tuned.
Turns out rooted users will need to return the tablet to KitKat stock. I found this info in 2-3 places in various languages. Here is hopefully a clear step-by-step to get back to KK stock and then take the OTA.
This can BRICK your device, so use at your own risk. Files are supplied as a courtesy and not mine
1) Download - This - AFH - kitkat-YT2-1050F_S0198_150422_ROW.7z (This updated readme file here)
2) Extract the zipfile to a directory on PC somewhere
3) Goto "tools" folder and install the exe's in this order
a) PhoneFlashTool_4.4.4.1_external_win32.exeb) iSocUSB-Driver-Setup-1.2.0.exec) IntelAndroidDrvSetup1.5.0.exe4) Start PhoneFlashTool and select settings (Upper left corner)
5) Tick "force sparcing" and change size to 500mb
6) Power off tablet and connect with usb
7) From off, hold volume up and power until tablet vibrates and release power (still holding volume up)
8) Tablet should now be in "Droidboot" and PhoneFlashTool should list it on the top
9) In PhoneFlashTool click browse and select flash.xml from the "target_bin" folder
10) WAIT!!! until you see "Result okay" on tablet AND "Flash Sucess" in PhoneFlashTool
11) Reboot
12) When Android starts skip all dialogs (tablet is going to factory reset anyway)
13) Select Contacts from desktop and make 1 dummy contact
14) In the search bar type "####6020#" and then select your country
15) Tablet reboots and you are on stock KitKat again and should receive an update notice for Lollipop
From my LG-G3 running Jasmine8.0/Skydragon Kernel 4.2
i got the 830F Update today, But i got Problems!
830F Update Log:
- It stays for 8min. at 100%. I leave it alone...
- Then 4 chinese Buttons showed up.
- I pressed the first (reboot i think)
- it reboots, it shows the white lenovo text, then black screen with background light on.
- i waited 10min., no change or start into OS.
- then i pressed 15sek power off, light goes off.
- if i power on, again white lenovo text, then black screen with background light on. nothing... ???
- i reboot into recovery and wiped cache, nothing.
i think i will make update from SD card again... see if something happend
Edit: Update from SD dont work! it says:
"/system/app/Chrome.apk" has unexpected contents...
E: Error in /sideload/package.zip
830F Update Log END
5m00v3 said:
i got the 830F Update today, But i got Problems!
830F Update Log:
- It stays for 8min. at 100%. I leave it alone...
- Then 4 chinese Buttons showed up.
- I pressed the first (reboot i think)
- it reboots, it shows the white lenovo text, then black screen with background light on.
- i waited 10min., no change or start into OS.
- then i pressed 15sek power off, light goes off.
- if i power on, again white lenovo text, then black screen with background light on. nothing... ???
- i reboot into recovery and wiped cache, nothing.
i think i will make update from SD card again... see if something happend
Edit: Update from SD dont work! it says:
"/system/app/Chrome.apk" has unexpected contents...
E: Error in /sideload/package.zip
830F Update Log END
Click to expand...
Click to collapse
Are you rooted? If so you need to "unroot". That can be done as simply as going into the settings of SuperSU and selecting - full upnroot. Or you may need to flash back to original stock...
Have you done the Update without problems?
Can i flash back original 4.4.2 without brick my YT2?
Edit: i have no ROOT
5m00v3 said:
Have you done the Update without problems?
Can i flash back original 4.4.2 without brick my YT2?
Edit: i have no ROOT
Click to expand...
Click to collapse
It keeps failing. I'm going to try flashing the original firmware, but probably not until the weekend. I have too much on my plate to deal....
SUCCESS, LOLLIPOP IS WORKING!!!
I Have restored original KitKat ROM via "PhoneFlashTool" with this ROMs / Tutorial:
http://www.android-hilfe.de/thema/tu...ianten.697884/
This time i´ve made the "Country Setting" via ContactApp ####6020# to "DE" befor download and upgrade!
And i have aborted the automatic PlayStore updates for Chrome etc...
Lollipop upgrade reboots into recovery and stays 5min. at 100%.
Then reboots into some intel-flash mode and stays for 4min.
After it reboots into Lollipop OS...
I have the same problem, only that I had the first Lollipop version for 1050F with root and then got the new Lollipop update. The Kitkat version fails to flash. But here is what helped:
Go to this post
http://forum.xda-developers.com/thi...-8-10-13-3-t2930428/post60490907#post60490907
and download the LtoKKxml.7z and copy the files into the kitkat firmware folder and then flash using flash-LtoKK-PVT-810.xml
I had to remove the parts of the XML that erase and format data. Then it worked
After that I could flash KitKat!!
@ matshias
thx, good to know...
5m00v3 said:
SUCCESS, LOLLIPOP IS WORKING!!!
I Have restored original KitKat ROM via "PhoneFlashTool" with this ROMs / Tutorial:
http://www.android-hilfe.de/thema/tu...ianten.697884/
This time i´ve made the "Country Setting" via ContactApp ####6020# to "DE" befor download and upgrade!
And i have aborted the automatic PlayStore updates for Chrome etc...
Lollipop upgrade reboots into recovery and stays 5min. at 100%.
Then reboots into some intel-flash mode and stays for 4min.
After it reboots into Lollipop OS...
Click to expand...
Click to collapse
matshias said:
I have the same problem, only that I had the first Lollipop version for 1050F with root and then got the new Lollipop update. The Kitkat version fails to flash. But here is what helped:
Go to this post
http://forum.xda-developers.com/thi...-8-10-13-3-t2930428/post60490907#post60490907
and download the LtoKKxml.7z and copy the files into the kitkat firmware folder and then flash using flash-LtoKK-PVT-810.xml
I had to remove the parts of the XML that erase and format data. Then it worked
After that I could flash KitKat!!
Click to expand...
Click to collapse
Well, I got as far as extracting the original kk firmware, installing Intel phone tool and drivers with no problems. My issue is the tablet is recognized by the Intel phone tool while the tablet is in Android but when I reboot to fastboot it isn't.
This is in a virtual machine because I don't do Windows on hardware, only VirtualBox.
I may have to take an old rig and install Windows temporarily...
From my LG-G3 running Jasmine8.0/Skydragon Kernel 4.2
VitualBox maybe a problem, but why it works when in Lollipop OS and not in droidboot?
Firewall? ADB in developer-options enabled?
Try check your device manager in fastboot-mode if there is some "Unknown device" and install ADB driver...
5m00v3 said:
VitualBox maybe a problem, but why it works when in Lollipop OS and not in droidboot?
Firewall? ADB in developer-options enabled?
Try check your device manager in fastboot-mode if there is some "Unknown device" and install ADB driver...
Click to expand...
Click to collapse
Yea, I got it to work through VB. I went to upgrade and the upgrade failed and now it won't boot.
I'm going to try flashing the KK firmware again.
Edit: Flashing again now...
workdowg said:
Yea, I got it to work through VB. I went to upgrade and the upgrade failed and now it won't boot.
I'm going to try flashing the KK firmware again.
Edit: Flashing again now...
Click to expand...
Click to collapse
Lollipop won't update for me. I had a TWRP backup so I am right back where I was. Could it be the "country code" I saw in the instructions? If so what is the dial code for US? us?Duh, it brings up a selection box... Chinese but readable.
workdowg said:
Lollipop won't update for me. I had a TWRP backup so I am right back where I was. Could it be the "country code" I saw in the instructions? If so what is the dial code for US? us?Duh, it brings up a selection box... Chinese but readable.
Click to expand...
Click to collapse
Guess that was it.. Updating to Lollipop now.
workdowg said:
Guess that was it.. Updating to Lollipop now.
Click to expand...
Click to collapse
I am glad that you made it!
So ROOT next?
5m00v3 said:
I am glad that you made it!
So ROOT next?
Click to expand...
Click to collapse
Root - no problem - Trigger 4
Update successful to YOGATablet2-1050F_S100067
Mine was a pleasant suprise.
LenovoPad YOGA Tablet 2-1050F
I already had installed Lollipop YOGATablet2-1050F_S100031 and rooted.
When advised there was a new OTA update, I did the following:
1. From within SuperSU Pro settings "Full unroot"
2. Reboot
3. Connect to PC
4. Run Lenovo Smart Assistant
5. Update was available, which downloaded to my PC
6. Lenovo Assistant began to transfer the update to the tablet, but ultimately (2 mins?) reported "Update failed"
7. Disconnected tablet from PC and turned it off
8. Simultaneously pressed volume down and power button, released volume key on vibration
9. Black screen quickly followed by the Android icon processing the update
10. Update successful to YOGATablet2-1050F_S100067
11. All data intact
12. Re-rooted using T4 (above.)
One happy camper! :laugh:
Oh, and Xposed-v67-sdk21-x86.zip successfully installed with this version!
workdowg said:
I captured the lollipop update that came out today. I have a nandroid backup and I'm going for the update. We will see if the new tethered CWM works to get root back... Stay tuned.
Turns out rooted users will need to return the tablet to KitKat stock. I found this info in 2-3 places in various languages. Here is hopefully a clear step-by-step to get back to KK stock and then take the OTA.
This can BRICK your device, so use at your own risk. Files are supplied as a courtesy and not mine
1) Download - This - AFH - kitkat-YT2-1050F_S0198_150422_ROW.7z (This updated readme file here)
2) Extract the zipfile to a directory on PC somewhere
3) Goto "tools" folder and install the exe's in this order
a) PhoneFlashTool_4.4.4.1_external_win32.exeb) iSocUSB-Driver-Setup-1.2.0.exec) IntelAndroidDrvSetup1.5.0.exe4) Start PhoneFlashTool and select settings (Upper left corner)
5) Tick "force sparcing" and change size to 500mb
6) Power off tablet and connect with usb
7) From off, hold volume up and power until tablet vibrates and release power (still holding volume up)
8) Tablet should now be in "Droidboot" and PhoneFlashTool should list it on the top
9) In PhoneFlashTool click browse and select flash.xml from the "target_bin" folder
10) WAIT!!! until you see "Result okay" on tablet AND "Flash Sucess" in PhoneFlashTool
11) Reboot
12) When Android starts skip all dialogs (tablet is going to factory reset anyway)
13) Select Contacts from desktop and make 1 dummy contact
14) In the search bar type "####6020#" and then select your country
15) Tablet reboots and you are on stock KitKat again and should receive an update notice for Lollipop
From my LG-G3 running Jasmine8.0/Skydragon Kernel 4.2
Click to expand...
Click to collapse
Thanks a lot for your description. I've been postponing this for a long time. I finally did the upgrade today. 100% successful.
I followed this guide in order to root my brand new p8lite.
The thing is that now I have a black screen. If I plug my phone via usb, adb shows me that the device is in recovery.
By adb shows me that the device is in recovery I mean this:
Code:
# adb devices
List of devices attached
W3D7N16712000718 recovery
What I did:
Checked the model. It's an ALE-L21
Chapter 1: not a windows user, but managed to get adb up and running on my linux machine.
Chapter 2: everything went fine, bootloader unlocked
Chapter 3: my phone booted up just fine
Chapter 4: skipped it, as my phone was booting fine into system
Chapter 5:
So you want to convert to a single/dual sim?
Click to expand...
Click to collapse
My answer: "no thanks", so I skipped it
Chapter 6: I did the upgrade through OTA BEFORE reading the guide. Double checked I was running 6.0, so I skipped it
Chapter 7: Downloaded the file, flashed trought fastboot. And now I'm here.
I think I may have ****ed up things in the last 3 chapters.
What I tried to fix this:
Code:
# adb reboot bootloader
phone rebooted then huawei logo then blackscreen. adb still shows it's in recovery
After searching in the forum, I came by
Code:
adb reboot-bootloader
(notice the hypen). Firing that command put my phone into fastboot. Couldn't believe it, but I took the chance to flash the files found in chapter 4 (bootloader, recovery, cust and system, in this order). No luck, still reboot, logo, black screen
Now, no matter the presence of the hypen in the command, my phone keeps going into recovery (after the usual reboot, logo, black screen)
Tried to hold down POWER to shut it down. After a while it reboots, logo and black screen again. Laptop keeps saying device is into recovery
Tried to download the official 6.0 update, put on a sd card (dload/UPDATE.APP), held down POWER+VOLUP+VOLDOWN. Again, reboot, logo, black screen. recovery mode, again.
Frustrated, I unplugged the phone. After a while, it rebooted, logo and blackscreen without me touching it. Weird. It did it again a couple of times, but now it has stopped (with a black screen and, if plugged in, adb. says is into recovery)
I really don't know what to do, please help me.
UPDATE:
After leaving a night on its own, the phone was noticeably hot.
Also, when unplugged, if I hold POWER it shows me the logo a couple of time before going black screen.
Ok. But can you enter in recovery?
Another question: you said that u flashed the necessary files. What about flashing directly twrp as recovery, and from twrp make all wipes, and afther that flash from twrp some zip-ped firmwares?
tamaskurti said:
Ok. But can you enter in recovery?
Click to expand...
Click to collapse
Apparently yes (or at least, adb says I'm into recovery). However, I just get a black screen.
Tapping randomly on the screen doesn't give any kind of feedback (no vibration, no beeps, nothing).
tamaskurti said:
Another question: you said that u flashed the necessary files. What about flashing directly twrp as recovery, and from twrp make all wipes, and afther that flash from twrp some zip-ped firmwares?
Click to expand...
Click to collapse
Since I started having those problems after I flashed TWRP, I thought it was a better idea to flash stock recovery (alongside bootloader, cust and system) and restart from there.
I have the same issue...
Have you solved the issue? In case you solved, how?
mmennella said:
I have the same issue...
Have you solved the issue? In case you solved, how?
Click to expand...
Click to collapse
Not yet. I brought the phone to a local repair shop. Tomorrow they should bring it back, hope they have good news
Mmmmmm... I go to buy new One. Huawei must have a way to reflash, but i can't wait. Thanks a lot
Inviato dal mio Redmi 3 utilizzando Tapatalk
S1cK94 said:
Not yet. I brought the phone to a local repair shop. Tomorrow they should bring it back, hope they have good news
Click to expand...
Click to collapse
i brought it to my local repairshop and they sent my phone to manufacters central repair and they fixed it for free.
AfrikanDionysus Solution
Huawei P8 lites are region specific like Middle east asia america etc so before you go in make sure you know your build number in my case ALE-L21C185B560 its the UAE variant now if you've messed go to the huawei website download the rom specific to your region any other region won't work!!! get a clean sd card extract the file and copy it to the root of the sd card its normally an update.app inside a folder named dload shutdown the phone now press vol+ and vol - and the power button till it starts installing.. If you've messed up your recovery and can get to fastboot by plugging in the phone then pressing vol down and power.. use the Huawei extractor tool and extract the recovery from the just downloaded rom and flash it.. then retry the restore as stated.. im sure you can google all the tools you need to get so im not putting any links !!! Ahsante !:good::good::good:
my problem is kind of abnormal. i couldnt find solution anywhere so i came here. my device was zenfone 5(t00f)/lollipop.
so i wanted to root my phone. i followed this guide >>
HTML:
http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
the tool i used is called ZenfoneToolkit_20160719, downloaded from here
HTML:
https://drive.google.com/drive/folders/0B0AFmAAcGS5xbWpTQzBQVTN3b1k
. its a bundle of .exe, .dll, .img, .bin files. but no need to work on them seperately, there is a simple cli tool from which you can choose what you want to do and it executes that file for you. below is the list what you can do.
1. Wipe Cache
2. Factory Reset
3. Flash Boot
4. Flash Recovery
5. Flash Fastboot
6. Flash Stock ROM
7. Root
8. Unroot
9. Unlock Bootloader
10. Relock Bootloader
11. Zenfone Rescue aka Debrick
12. Fixing Generic IMEI 004999010640000
13. Backup MicroSD
14. Flash Boretz Kernel Lollipop
so wiped cache[1] first then i tried to root[7]. sadly it didnt work, when i turned the phone on it took me to fastboot screen, there i had only a few options like, normal boot(doesnt happen), recovery mode, restart. when i turned it off and pressed power and volume up together it would go to recovery where none of the options works. i though that was what called brick, so followed this guide to make my life better
HTML:
http://zenfone-blog.blogspot.com/2015/06/guide-how-to-unbrick-asus-zenfone-4-5-6.html
.
my phone by default came with kitkat. so when i downloaded the firmware i wanted to get a kitkat. but i couldnt find a matching recovery img and firmware for kitkat on asus official page. so i downloaded jellybean. ASUS ZenFone 5(T00F/T00J) software Image: V1.18.40.9 ww for firmware from here
HTML:
https://www.asus.com/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/
. and recovery img is 1.18.40.9_ww_recovery.img from here
HTML:
https://www.asuswebstorage.com/navigate/s/644D9E0A19714899974C75FC4B6C87EDY
. i dont know what "ww" means in those name but i saw it in my software version before so i went with it.
All the steps went smoothly, by the end of it i guessed my phone charge would be low so i put it in charge and turned it on. first time it turn on without a problem. i checked out a few things and leave it for charge. after a while i came back and battery was 0%. i thought i would be wise to plug out and in charging port again. as soon as i pull out the pin, screen instantly turned black and the phone went dead after a looooong ass vibration.
now when i try to charge the orenge light at top lights up but the animation that shows battery always show its empty. if i try to turn it on while plugged, it shows asus logo/intel logo and goes dead again. if i try to turn it on without being plugged, it shows a battery logo with a question mark, which i think means the phone cannot find battery.
i am stuck here.... plz someone be my savior.
Hello my dear, to get out of this problem I did the following: I connected the phone to compuador by USB cable (with himself off), then he calls and gets the question symbol, it held the power button plus volume up he must restart to get the logo asus about 4 seconds after loose the power button and continue with the volume button up insured. It should enter into fastboot mode there do the necessary procedures to reflash the system.
I hope you helped, hug!
matheusgcdj said:
Hello my dear, to get out of this problem I did the following: I connected the phone to compuador by USB cable (with himself off), then he calls and gets the question symbol, it held the power button plus volume up he must restart to get the logo asus about 4 seconds after loose the power button and continue with the volume button up insured. It should enter into fastboot mode there do the necessary procedures to reflash the system.
I hope you helped, hug!
Click to expand...
Click to collapse
i tried. but just cannot get to the fastboot screen. :'(
nooblett said:
i tried. but just cannot get to the fastboot screen. :'(
Click to expand...
Click to collapse
use this thread and perhaps there is hope
matheusgcdj said:
use this thread and perhaps there is hope
Click to expand...
Click to collapse
thnx. i am gonna try it now.
@matheusgcdj: yes it worked
The reason I'm making this thread is because I was trying to root my Honor 8 and things just didn't work out in TWRP. Rebooted my phone and I realized I had bricked it since it would not boot after 10 minutes. Solutions seem to be scattered throughout different threads so here's guide for when you're stuck in a boot loop or you bricked your Honor 8.
What you'll need:
1. The firmware currently you are on. @Coolyou posted a guide for a firmware finder. Here is the post.
2. SD Card
What to do:
Step 1.
Download the correct firmware. It will be a .zip file.
Step 2.
Create a folder called dload in the root of your SD card, not your internal storage. Copy the .zip file the folder and unzip it or unzip it else where and copy the content into the dload folder
Step 3.
Power off Honor 8 (if possible, sometimes it'll auto boot up when forced shutdown)
Step 4.
Make sure your device is not plugged into a computer as it will load into something else.
Hold Vol+ & Vol- & Power. It will being to install the firmware from the dload folder if done correctly. If it instantly fails that means you downloaded the incorrect firmware the device is already one.
You're done! However, if your device does not go past the startup logo within 3 minutes proceed to step 5.
Step 5 is probably necessary as everytime I've bricked my device, I've had to do the next step.
Step 5.
Power off. Hold power and Vol+. Once in Recovery mode (not eRecovery), clear cache and format your device. Once done, reboot.
Ta-da, you're device is now back to normal.
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Let go off the power button after the first vibration. Also make sure your phone is not plugged to a pc. With pc connected it boots into eRecovery instead of recovery. Good luck!
Edit:Also the guide does not make it 100% specific but the dload folder on the sd card needs to have the update.app file right inside it. If the structure is sd\dload\folder\update.app it also won't work.
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
i have same problem!
i can't reboot in download mode: it vibrates twice and reboot in blue screen always, even leaving power button after first vibration.
How can i fix this?
please help..!
alec_trikki said:
i have same problem!
i can't reboot in download mode: it vibrates twice and reboot in blue screen always, even leaving power button after first vibration.
How can i fix this?
please help..!
Click to expand...
Click to collapse
i have same problem, you can fix this? help me please
Add me to the list, two soft bricked Honor 8's. Once I made the jump to Nougat and installed the Nougat version of TWRP 3.0.1-1, I started having issues. So, I tried to downgrade to FRD-L04C567B150 from FRD-L04C567B320 and had big problems installing B150. Always getting unable to load /data Has to be something to do with the new data structure of Nougat I have a copy of the full stock rom of B150 and B162 and have wiped the phone. I am trying to dload full B150 from SDcard but will fail immediately and says Wrong Version. I can get to fastboot and ADB. I also tried custom ROMs but that wont work because they need the basic Nougat structure to work from. I don't have a clue how to proceed seeing that I can't even wipe the phone and install a Full stock ROM B150 or B162??
Any help would be extremely appreciated.
thekubiaks said:
Add me to the list, two soft bricked Honor 8's. Once I made the jump to Nougat and installed the Nougat version of TWRP 3.0.1-1, I started having issues. So, I tried to downgrade to FRD-L04C567B150 from FRD-L04C567B320 and had big problems installing B150. Always getting unable to load /data Has to be something to do with the new data structure of Nougat I have a copy of the full stock rom of B150 and B162 and have wiped the phone. I am trying to dload full B150 from SDcard but will fail immediately and says Wrong Version. I can get to fastboot and ADB. I also tried custom ROMs but that wont work because they need the basic Nougat structure to work from. I don't have a clue how to proceed seeing that I can't even wipe the phone and install a Full stock ROM B150 or B162??
Any help would be extremely appreciated.
Click to expand...
Click to collapse
UPDATE : It freaking worked!!! After an entire weekend of hair pulling and going way deep into Nougat and MM trying to find the cause, it was a simple Full ROM B162 that I dloaded and three fingered from the SD card (of course it has to be the exact ROM for your phone such as FRD-L04C567B###). WOW, two phones are back. I'll stay at FRD-L04C567B162 and like it.
Lesson Learned: When you try to do an eRecovery and the Honor 8 starts downloading new firmware from the internet it creates a new folder on the sd card called something like HwOC. In that folder is stored the new firmware that erecover plans to use on the recovery. IF this HwOC folder is present and you try to do a Full ROM three finger install with the B150 or B162 firmware in the dload folder, the recovery will stop and say something like invalid version. To fix, remove the HwOC folder so that only dload is present, now do the three finger start and the firmware will install without error. Worked twice for me.
Hi, my device is still not booting up after installing the matching dload firmware on my device from the honor 8 website (FRD-L09).
Is there still anything I can do to maybe get this fixed?
I created a nandroid backup of all partitions that I were able to back up, but even rolling back all partitions did not make it boot again.
Sadly, I am not able to get the device into e.g. fastboot mode anymore because it is not booting anymore and therefore cant get an adb shell on it.
I can still enter recovery mode, but when trying to boot it just stays at the blue screen with the white "honor" text after the short boot animation with the 3d text
Hi,
my phone keeps entering eRecovery and my PC does not recognize it so please how can I access it to install files. I think I have installed a wrong boot.img and recovery.img version of firmware.
Please I need help.
Thanks
Lorog said:
Hi,
my phone keeps entering eRecovery and my PC does not recognize it so please how can I access it to install files. I think I have installed a wrong boot.img and recovery.img version of firmware.
Please I need help.
Thanks
Click to expand...
Click to collapse
Same here on a Note 8 did you find a solution?
thekubiaks said:
UPDATE : It freaking worked!!! After an entire weekend of hair pulling and going way deep into Nougat and MM trying to find the cause, it was a simple Full ROM B162 that I dloaded and three fingered from the SD card (of course it has to be the exact ROM for your phone such as FRD-L04C567B###). WOW, two phones are back. I'll stay at FRD-L04C567B162 and like it.
Lesson Learned: When you try to do an eRecovery and the Honor 8 starts downloading new firmware from the internet it creates a new folder on the sd card called something like HwOC. In that folder is stored the new firmware that erecover plans to use on the recovery. IF this HwOC folder is present and you try to do a Full ROM three finger install with the B150 or B162 firmware in the dload folder, the recovery will stop and say something like invalid version. To fix, remove the HwOC folder so that only dload is present, now do the three finger start and the firmware will install without error. Worked twice for me.
Click to expand...
Click to collapse
Do you have the link for the b162 full firmware?
edit:
also what recovery did you have installed when you did this?
nickp22127 said:
Do you have the link for the b162 full firmware?
edit:
also what recovery did you have installed when you did this?
Click to expand...
Click to collapse
Its erecovery
tiagoesbastos said:
i have same problem, you can fix this? help me please
Click to expand...
Click to collapse
i have the same pblm...how did u both managed to boot it then??
---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------
alec_trikki said:
i have same problem!
i can't reboot in download mode: it vibrates twice and reboot in blue screen always, even leaving power button after first vibration.
How can i fix this?
please help..!
Click to expand...
Click to collapse
tiagoesbastos said:
i have same problem, you can fix this? help me please
Click to expand...
Click to collapse
i have the same pblm...can u tell how did u managed to solve it???
oops, wrong thread
abbassbhai said:
i have the same pblm...how did u both managed to boot it then??
---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------
i have the same pblm...can u tell how did u managed to solve it???
Click to expand...
Click to collapse
Do you find a solution? I have the same problem!
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
Did you find a solution? I have the same problem!
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
Hi, I have the exact same problem. Have you managed to fix it?
Same problems as other people above, couldn't load any recovery. Anyone can help us out?
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
Hi even I have the same problem with Honor 8 Pro.. Did you get any solution??
Hi even I have the same problem with Honor 8 Did you get any solution??