Related
Hello XDA community !
LAst week I bought my Acer A700, but after a few days a dead pixel appeared...
So I was on my way to send back my toy, when I saw that CMWR was available.
"Nice ! I can do a factory reset so my toy will be clean to be sent back !"
But the factory reset didn't work... It was stuck at "Formatting /data" for a while...
So I rebooted the A700, and now it's stuck at the ACER logo... I only have access to recovery...
Any ideas ?
Thanks a lot :good:
Since you have recovery try and do data wipe, then wipe cache then davlik cache, then reboot.
If you have recovery you can install a ROM by renaming it update.zip and using CWM.
Itchiee said:
Since you have recovery try and do data wipe, then wipe cache then davlik cache, then reboot.
If you have recovery you can install a ROM by renaming it update.zip and using CWM.
Click to expand...
Click to collapse
I already tried this, when I want to install a update.zip, it stucks at "installing update".
When I want to wipe a partition, it stucks at "formating /xxx" and nothing happens...
I wanted to flash stock bootloader with Nvflash, but I can't find APX drivers for ACER A700
Can you install the update.zip without the use of CWM (By pressing the powerbutton with the vol down)?
Also, where is your update.zip located?
Edit:
I guess it could do no harm if you'd hook up your device to the PC and enter the following commands:
adb reboot bootloader
fastboot erase cache
Click to expand...
Click to collapse
TomONeill said:
Can you install the update.zip without the use of CWM (By pressing the powerbutton with the vol down)?
Also, where is your update.zip located?
Edit:
I guess it could do no harm if you'd hook up your device to the PC and enter the following commands:
Click to expand...
Click to collapse
_ update.zip putted on a extrenal SD card doesn't work, it's skipped and CWM is launched.
_ the "adb reboot bootloader" puts the A700 in "APX" mode... and the "fastboot erase cache" is stuck at "waiting for device"...
Thanks for trying to help !!!
May this be a relevant solution??
http://androidforums.com/esteem-all...w-get-out-clockworkmod-recovery-bootloop.html
Edit:
I don't think the device checks for update.zip on the sdcard. Maybe there is a way to move the file to the internal. (adb mount sdcard adb push /sdcard/update.zip update.zip ?
Yeah,
The current CWM seems to corrupt the Data partition (amongst other things). Seems to be a going thing lately. Remember, these are new tabs, and new root & recovery methods, so there are going to be some bricked tabs before things get sorted out. This happens in "ALL" development, and everybody knows the risks involved.
I had the same issue. Couldn't reboot into fastboot, as it seems the OS has to be running?
This is why Skirlax_CZ built the bootloader for the 500/501, so you could boot it into fastboot mode, bypassing the OS. Unfortunately, the stock 70x OEM bootloader doesn't seem to allow this.
Best bet if you can't find the "exact" version rom the tab was shipped with, is to try renaming some full roms to update.zip, copy to sd, reboot (vol + and PWR, and see if it will install and boot. At the worst, it will install a stock bootloader and recovery.
Also, holding PWR, Vol - (I believe) and toggling the rotation lock should wipe User Data.
At the very worse, turn it into Acer Service, suck it up and pay the repair bill.
They will just install the correct service rom and give it back to you.
MD
Touns said:
Hello XDA community !
LAst week I bought my Acer A700, but after a few days a dead pixel appeared...
So I was on my way to send back my toy, when I saw that CMWR was available.
"Nice ! I can do a factory reset so my toy will be clean to be sent back !"
But the factory reset didn't work... It was stuck at "Formatting /data" for a while...
So I rebooted the A700, and now it's stuck at the ACER logo... I only have access to recovery...
Any ideas ?
Thanks a lot :good:
Click to expand...
Click to collapse
your situation is just same as mine,seeming bricked after using fatory rest or wiping from cwm,I think it's the problem of the damn cwm.as i know from now there are several devices got bricked,all because of the goddamn cwm.as we know factory rest is the same as recovery wiping,i use the under the official recovery,everything wen fine,but after wiping via cwm from the forum,it appeared the problem.
i tried a lot of method,just as u mentioned,to flash *.img
but i found a curious thing,after dumping series of *.img from a well-mailfuntioning device i can use fastboot to flash "userdata" which the loaction is mmcblk010 or /dev/block/platform/sdhci-tegra.3/by-name/UDA,but after flashing,i can't erase userdata block in fastboot.then i reflashing the data.img to userdata block,then in cwm,i can mount /data,but it's still not able to wipe or format it.then i've found a data.img and flashing the userdata and reboot.then i enter the system,and it forced me to do a factory reset,of course as before,it's not mailfunctioning because of the cwm or the block itself damaged..
but i can enter adb,and i found that i can see the /data and the filesystem in it.then i use mount to modify it,for i can delete or modify the files in /data,and it appears normally.i delete everything in /data.then i want to try to reboot to see if it's working,but after rebooting,the device stuck at acer logo,then i reboot into the cwm,it can't be mounted again.it seems that i can flash the userdata but i can't format or wipe or modify...
and i tried to reflash the bootloader from a well-mailfunctioning deivece,not working,either.
then i go for searching the situation in google,i found there are a lot of similar problems of the tegra device,and the solution is nvflash...
i don't know if there are a block saving the information of partitions just like the PIT file of my galaxy s2,seems we should wait for nvflash?or the method to flashing PIT partitions file?
i installed the nvflash driver by modifying the usb id,but i can't do anything from nvflash,it's not matching.
I had the same problem after I upgraded to JB with CWM recovery 6.0.14 and I tried to root it. But it stuck in acer logo. Then I went to recovery mode, but it couldn't mount sdcard or external card, too.
In my case, I solved it by these steps:
1. Try to go to fastboot mode by press vol (-) + power. After it vibrate, release power, and then play lock button. Then tablet will go to fastboot mode. http://forum.xda-developers.com/showthread.php?t=1861092
2. Download these boot and recovery images: https://www.box.com/s/3321wf8gg4at639nfn06
3. Try to flash these boot and recovery images to table:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
And then, reboot tablet:
fastboot reboot
WOW, my tablet works again.
:victory:
kwaiding said:
I had the same problem after I upgraded to JB with CWM recovery 6.0.14 and I tried to root it. But it stuck in acer logo. Then I went to recovery mode, but it couldn't mount sdcard or external card, too.
In my case, I solved it by these steps:
1. Try to go to fastboot mode by press vol (-) + power. After it vibrate, release power, and then play lock button. Then tablet will go to fastboot mode. http://forum.xda-developers.com/showthread.php?t=1861092
2. Download these boot and recovery images: https://www.box.com/s/3321wf8gg4at639nfn06
3. Try to flash these boot and recovery images to table:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
And then, reboot tablet:
fastboot reboot
WOW, my tablet works again.
:victory:
Click to expand...
Click to collapse
Unfortunately, although somewhat similar, this is not the same situation as the OP had.
The first CWM originally posted a few months ago, was posted by a user who used the totally wrong partition tables, and also, didn't own the tab so it was never tested (after the fact). Basically, it damaged the chipset which required a motherboard replacement. Not to mention a specifically nasty Data_Cap bug in the CWM kernel. No image flashing via fastboot (and probably NVFlash) would repair the damage. The result was several bricked tabs till the CWM was removed. (mine included)
Also note, that the current root procedure is by the same person. Although there is an alternative.
What you had, was simple data corruption on one of the Dev Blocks. This is why you were able to fastboot an image.
Corrupting a partition can happen at any time. Whether rooted, stock, or custom rom. So it's always nice to have ADB to pull your partition images. Just in case.
MD
Hey guys!
So, i was trying to install CM13 unofficial version, and wiped the system and internal storage using TWRP recovery. I was supposed to install the rom from a zip file i had placed in the external memory card. What i did, was, i rebooted the phone by mistake, after wiping it from the recovery without installing the ROM and now the phone is caught in a bootloop. I know i am an idiot to do that. I tried removing the battery and reboot it in recovery mode using the key combination with no luck. It just starts the boot loop. I tried using fastboot and adb from pc to push files into the internal memory, but my device is not getting detected on the adb anymore (maybe the usb debugging is disabled now?).
What i guess is stopping TWRP recovery from showing up is the lack of twrp/themes folder in the internal memory since i wiped it. But there might be some other cause that i am unaware of. What do i do now? Any help will be greatly appreciated!
Hey! I'm having the same problem with my yu yureka.. Can anyone help me please!
Kaustubh M said:
Hey guys!
So, i was trying to install CM13 unofficial version, and wiped the system and internal storage using TWRP recovery. I was supposed to install the rom from a zip file i had placed in the external memory card. What i did, was, i rebooted the phone by mistake, after wiping it from the recovery without installing the ROM and now the phone is caught in a bootloop. I know i am an idiot to do that. I tried removing the battery and reboot it in recovery mode using the key combination with no luck. It just starts the boot loop. I tried using fastboot and adb from pc to push files into the internal memory, but my device is not getting detected on the adb anymore (maybe the usb debugging is disabled now?).
What i guess is stopping TWRP recovery from showing up is the lack of twrp/themes folder in the internal memory since i wiped it. But there might be some other cause that i am unaware of. What do i do now? Any help will be greatly appreciated!
Click to expand...
Click to collapse
Hi! I'm having the same problem with this post... Does anyone knows the solution of this problem. I'd be really glad if anyone could help me with this..please!
Hey are you able to boot into fastboot mode? If you can....
Prerequisites –
1. Make sure that you have 70-80% battery on your phone.
2. You need a PC and a USB cable to connect your phone to the PC.
3. Flashing the factory firmware will wipe all the data present in the internal memory. So, make a backup of that if you can.
4.Install all the necessary Device drivers.
DOWNLOADS -
1. Download the flash tools from here . http://www.mediafire.com/download/87gfz7mdch188an/Flashtools_For_Yu_Yureka.zip
2. Download the factory firmware from Here (cm 12.1) . http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
Steps To Flash Factory Firmware –
1. Extract the flashtools zip in a new folder on the desktop.
2. Extract the factory firmware zip in the same folder and make sure that all of the flashtools files are also present.
3. Now, power off your phone. If you are stuck in a bootloop, then pull out the battery and reinsert it. (Do not switch on the phone.)
4. While pressing the Volume Up key, connect your phone to the PC with the help of a USB cable.
5. You should now see the fastboot logo on your device. If you did, leave the Volume Up key. (If you do not see the logo, retry the process.)
6. Now go to the folder where you extracted the flash tools and factory firmware and run the flash-all.bat by double clicking on it.
7. A command window will open and the flashing procedure will start. (Make sure that your device does not disconnect from your PC during the procedure.)
8. The command window will automatically close once the procedure is completed.
9. Disconnect your device and boot it up by pressing the Power button. (Since this is first boot after flashing the firmware, it may take upto 5 minutes.)
Done you should be back on cm 12.1
Credits – ArnavG (Yuplaygod Forums) and Cyanogen Team.
im also having same problem i have also unknowingly wiped system & now im not able to flash any rom while flashing its rebooting automatically & i am able to enter in to fastboot mode then i have flashed factory firmware then also its not booting stucked on boot loop.
arunbiju969 said:
Hey are you able to boot into fastboot mode? If you can....
Prerequisites –
1. Make sure that you have 70-80% battery on your phone.
2. You need a PC and a USB cable to connect your phone to the PC.
3. Flashing the factory firmware will wipe all the data present in the internal memory. So, make a backup of that if you can.
4.Install all the necessary Device drivers.
DOWNLOADS -
1. Download the flash tools from here . http://www.mediafire.com/download/87gfz7mdch188an/Flashtools_For_Yu_Yureka.zip
2. Download the factory firmware from Here (cm 12.1) . http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
Steps To Flash Factory Firmware –
1. Extract the flashtools zip in a new folder on the desktop.
2. Extract the factory firmware zip in the same folder and make sure that all of the flashtools files are also present.
3. Now, power off your phone. If you are stuck in a bootloop, then pull out the battery and reinsert it. (Do not switch on the phone.)
4. While pressing the Volume Up key, connect your phone to the PC with the help of a USB cable.
5. You should now see the fastboot logo on your device. If you did, leave the Volume Up key. (If you do not see the logo, retry the process.)
6. Now go to the folder where you extracted the flash tools and factory firmware and run the flash-all.bat by double clicking on it.
7. A command window will open and the flashing procedure will start. (Make sure that your device does not disconnect from your PC during the procedure.)
8. The command window will automatically close once the procedure is completed.
9. Disconnect your device and boot it up by pressing the Power button. (Since this is first boot after flashing the firmware, it may take upto 5 minutes.)
Done you should be back on cm 12.1
Credits – ArnavG (Yuplaygod Forums) and Cyanogen Team.
Click to expand...
Click to collapse
Bro tried that but nothing........
rss3183 said:
Bro tried that but nothing........
Click to expand...
Click to collapse
Can you be more specific ? Are you facing boot loop too?
anybody please help... facing the same problem and tried the solution as mentioned above but still facing Boot loop. what to do friends. please reply
I suddenly faced bootloop.....then I tried to flash stock rom without root...as a web page suggested me that....it was flashed successfully ...but still I am facing bootloop issue .....can someone pls help me to get out of this mess....pls help me...ASAP !!!
arunbiju969 said:
Hey are you able to boot into fastboot mode? If you can....
Prerequisites –
1. Make sure that you have 70-80% battery on your phone.
Click to expand...
Click to collapse
as its in boot loop battery has come to an end.... now what? having same problem as the topic creator
If you can boot into fastboot try flashing the Twrp from a computer,if you need steps on how to flash Twrp Post here if the flash is successfull boot into recovery and flash A new rom and this should boot your device
arunbiju969 said:
If you can boot into fastboot try flashing the Twrp from a computer,if you need steps on how to flash Twrp Post here if the flash is successfull boot into recovery and flash A new rom and this should boot your device
Click to expand...
Click to collapse
I flashed the factory image via YGDP tool as well as fastboot. But it boots upto a point and then goes in bootloop. Also if i wipe data/cache still it makes no difference. Also unlocked bootloader and twrp also don't load up. Again goes in bootloop.
Yogesh1969 said:
I flashed the factory image via YGDP tool as well as fastboot. But it boots upto a p loopoint and then goes in bootloop. Also if i wipe data/cache still it makes no difference. Also unlocked bootloader and twrp also don't load up. Again goes in bootloop.
Click to expand...
Click to collapse
were you trying to flash the twrp for the first time?? Was your yureka plus on stock kitkat??
Sorry for a late reply...
arunbiju969 said:
were you trying to flash the twrp for the first time?? Was your yureka plus on stock kitkat??
Click to expand...
Click to collapse
The problem got solved bcos it had a battery problem !!!! Battery showed 90-100%, but could not hold up on boot.
A very strange case. Thanks.
Hi, I flashed my Yu Yureka AO5512 Yesterday and entered into recovery mode and selected the wipe userdata option. When it was doing the process after 20min the process stopped all together and My phone does not start at all now. If i press any button there is no response at all. Looks like phones OS and everything is wiped out. How do i go about from here?
Same problem , Stuck in BootLoop
arunbiju969 said:
were you trying to flash the twrp for the first time?? Was your yureka plus on stock kitkat??
Click to expand...
Click to collapse
Bro , my Yureka was on Stock Lollipop (5.1) and i flashed Twrp 2.8x.x on it and now it''s Stuck in bootloop , i can't turn of the phone nor it starts , what should i do , any help appreciated
Thanks
YuganshT7 said:
Bro , my Yureka was on Stock Lollipop (5.1) and i flashed Twrp 2.8x.x on it and now it''s Stuck in bootloop , i can't turn of the phone nor it starts , what should i do , any help appreciated
Thanks
Click to expand...
Click to collapse
Sorry to hear that anyway,
By stock lolipop you mean you had the yureka plus with Volte From factory right!!...if so the twrp might have been for the yureka plus with the cm bootloader which got replaced in the new Devcice
I am facing the same problem and in my case I dont think its an battery issue...I was happily using the CM 13.0 Snapshot Rom since a long time...but today morning when I did a soft reset by going into the settings in my yureka...the phone has gone in bootloop...and nothing is working...using fastboot I even flashed the twrp again and also flashed the CM 12.0 Stock firmware..but nothing is working...after the YU logo it restarts....please help...
I am also facing problem maybe worst
I dont know what wrong I am doing but I am getting "FAILED (remote: unknown command)".
Few info:
1. I get my device ID when I do "fastboot devices" but nothing on fastboot -i 0x1ebf oem device-info".
2. Also for my YU5510A fastboot screen doesnt say' "fastboot" it says "Information do not unplug the cable - Secure Phone".
3. I have red light on, phones keeps rebooting 4-5 times than red light goes off and charging stops.
Aditi Apte said:
I dont know what wrong I am doing but I am getting "FAILED (remote: unknown command)".
Few info:
1. I get my device ID when I do "fastboot devices" but nothing on fastboot -i 0x1ebf oem device-info".
2. Also for my YU5510A fastboot screen doesnt say' "fastboot" it says "Information do not unplug the cable - Secure Phone".
3. I have red light on, phones keeps rebooting 4-5 times than red light goes off and charging stops.
Click to expand...
Click to collapse
Ignore that and use other fastboot commands and go ahead, as your device is being detected in fastboot mode.
FAILED (remote: unknown command)
Yogesh1969 said:
Ignore that and use other fastboot commands and go ahead, as your device is being detected in fastboot mode.
Click to expand...
Click to collapse
But when I am executing other fastboot commands it halts the process between with error "FAILED (remote: unknown command)".
I have read about this error and people suggested that I need to get into "Download mode" not "fastboot/bootload". To get into "download" mode I tried pressing "VoulumeDown+Power+Home", but nothing happened, it simply restarted the phone.
Please advise.
-Aditi
edit: If you are just looking for the solution, plz click here: http://forum.xda-developers.com/showpost.php?p=68626049&postcount=11
Hey there,
first of all I want to say Thank You for this great community and the work at XDA. Awesome. :good:
I bricked my Honor 6 H60-L02 and I am lost to bring it back to life. :crying:
Where it started:
I was using the official ROM from this thread [OFFICIAL] Honor 6 (L02, L12, L04) Stock ROMs. To be more specific it was the latest Android 6.0 EMUI 4.0 B823 that I installed with all the different OTA-Files starting with the original 5.1 ROM B535. The Honor was rooted and also the bootloader is still unlocked (I already checked the status via Fastboot.).
After I while the Honor 6 started to crash sometimes and the headphone-buttons didn't worked anymore. Then a few days ago the phone crashed and I was not able to boot it again.
And so I tried this:
Using the Rollback-Zip to go back to 5.1. But the 3btn-method didn't worked. The phone didn't want to boot into the recovery. Also the Vol+ and Power-Button didn't work to start the Recovery of the phone. Result: Bootloop.
So I installed ADB and Fastboot (with all necessary drivers) and tried to flash the phone with the 5.1 B535 (as mentioned in Honor 6 H60-L02 Hard Bricked - Only access to fastboot (Vol+ and Usb PC)) because there isn't a 6.0 B823 ROM available. I was able to flash boot, recovery, cust, system, userdata and another one I forgot right now. But the result was the same: Bootloop and no 3-btn or recovery via Vol+ and Power-Button. I also tried to flash it with the HonorTool. Same result.
Then I tried to flash different TWRP versions as recovery. Result: The same as above.
So I tried another official ROM 5.1 B526 because someone had the same problem and was able to recover his phone with this ROM (another thread in the forum). But that didn't worked ether.
Then I tried to flash all the img-files of the 5.1. B535 as crc, ptable and so on because I thought that there could be the problem. But when I tried e.g. to flash crc I get the error FAILED: command not allowed. So I tried to unlock the phones partition via Fastboot and fastboot flashine unlock_critical. But using the command unlock_critical gives me also the Failed error. So I was lost again.
Status right now:
I'm still able to boot into the bootloader via Vol- and Power. But right now the phone was running out of battery. Means I see the red battery symbol when I try to start the phone via the power button (without connecting to the PC or charger) but it isn't booting even into the bootloop. The red battery symbol pops up for a second and the screen went black again.
When I use the charger then the symbol changes to a green battery and stays there, but not the moving one that indicates that the phone is charging. When I use the Power button with usb-charger connected to start the phone I'm trapped in the bootloop again.
You see I already tried a lot of different things I could find on the forum. But nothing worked for me.
I know that it was a fault to try to install 5.1 B535 without the rollback, but I wasn't able to rollback as mentioned under point 1.
Maybe anyone could give me a hint and help me to bring my phone back to life.
Thx a lot! I appreciate that al lot!
If you need anymore informations, plz let me know.
Greets, mike175de
P.S: Sorry for my school english. It is a little bit rusty ;o)
mike175de said:
Hey there,
first of all I want to say Thank You for this great community and the work at XDA. Awesome. :good:
I bricked my Honor 6 H60-L02 and I am lost to bring it back to life. :crying:
Where it started:
I was using the official ROM from this thread [OFFICIAL] Honor 6 (L02, L12, L04) Stock ROMs. To be more specific it was the latest Android 6.0 EMUI 4.0 B823 that I installed with all the different OTA-Files starting with the original 5.1 ROM B535. The Honor was rooted and also the bootloader is still unlocked (I already checked the status via Fastboot.).
After I while the Honor 6 started to crash sometimes and the headphone-buttons didn't worked anymore. Then a few days ago the phone crashed and I was not able to boot it again.
And so I tried this:
Using the Rollback-Zip to go back to 5.1. But the 3btn-method didn't worked. The phone didn't want to boot into the recovery. Also the Vol+ and Power-Button didn't work to start the Recovery of the phone. Result: Bootloop.
So I installed ADB and Fastboot (with all necessary drivers) and tried to flash the phone with the 5.1 B535 (as mentioned in Honor 6 H60-L02 Hard Bricked - Only access to fastboot (Vol+ and Usb PC)) because there isn't a 6.0 B823 ROM available. I was able to flash boot, recovery, cust, system, userdata and another one I forgot right now. But the result was the same: Bootloop and no 3-btn or recovery via Vol+ and Power-Button. I also tried to flash it with the HonorTool. Same result.
Then I tried to flash different TWRP versions as recovery. Result: The same as above.
So I tried another official ROM 5.1 B526 because someone had the same problem and was able to recover his phone with this ROM (another thread in the forum). But that didn't worked ether.
Then I tried to flash all the img-files of the 5.1. B535 as crc, ptable and so on because I thought that there could be the problem. But when I tried e.g. to flash crc I get the error FAILED: command not allowed. So I tried to unlock the phones partition via Fastboot and fastboot flashine unlock_critical. But using the command unlock_critical gives me also the Failed error. So I was lost again.
Status right now:
I'm still able to boot into the bootloader via Vol- and Power. But right now the phone was running out of battery. Means I see the red battery symbol when I try to start the phone via the power button (without connecting to the PC or charger) but it isn't booting even into the bootloop. The red battery symbol pops up for a second and the screen went black again.
When I use the charger then the symbol changes to a green battery and stays there, but not the moving one that indicates that the phone is charging. When I use the Power button with usb-charger connected to start the phone I'm trapped in the bootloop again.
You see I already tried a lot of different things I could find on the forum. But nothing worked for me.
I know that it was a fault to try to install 5.1 B535 without the rollback, but I wasn't able to rollback as mentioned under point 1.
Maybe anyone could give me a hint and help me to bring my phone back to life.
Thx a lot! I appreciate that al lot!
If you need anymore informations, plz let me know.
Greets, mike175de
P.S: Sorry for my school english. It is a little bit rusty ;o)
Click to expand...
Click to collapse
Just flash boot, Cust, recovery and system images and let it boot normally. Don't do any button combo. I have had instances where it works. Give it a try.
With which version?
muradulislam said:
Just flash boot, Cust, recovery and system images and let it boot normally. Don't do any button combo. I have had instances where it works. Give it a try.
Click to expand...
Click to collapse
Thx for your reply.
With which version should I flash? B535 or B526? Should I only flash the three images boot, cust and system? Nothing else?
Thx for a reply!
mike175de said:
Thx for your reply.
With which version should I flash? B535 or B526? Should I only flash the three images boot, cust and system? Nothing else?
Thx for a reply!
Click to expand...
Click to collapse
You can use any firmware but the latest one should be better, and flash four images, boot, Cust, system and boot and let it boot normally.
Then put the dload folder with update.app in sd card and do an update from settings.
Thx. I will give it a try when I'm back from work.
I let you know if it is working.
mike175de said:
Thx. I will give it a try when I'm back from work.
I let you know if it is working.
Click to expand...
Click to collapse
I meant to say flash boot, Cust, recovery and system images.
Wrote boot twice
Nothing changed
Hey muradulislam,
Thx again.
I flashed the images (boot.img twice) but without success. Still the same error (with normal booting aka without any special button combination or with button combination). The honor boots and stays in the bootmode aka bootloop with the led blinkin red. And I still can't boot into recovery via Vol+ and Power..
Any other suggestions?
mike
mike175de said:
Hey muradulislam,
Thx again.
I flashed the images (boot.img twice) but without success. Still the same error (with normal booting aka without any special button combination or with button combination). The honor boots and stays in the bootmode aka bootloop with the led blinkin red. And I still can't boot into recovery via Vol+ and Power..
Any other suggestions?
mike
Click to expand...
Click to collapse
Of all the things you have already tried, the only thing remains to take it to a Huawei service center.
May be someone else can help you here but I have read most of honor 6 and 7 posts and I don't think there is anything there for this problem atm.
Hmm, thx. That is bad...
I bought this phone in China when I was there for work. And I suppose that the german service of Huwaei will not help me at all with this phone.
Does anybody else have any clue how to bring the phone back to life?
Thx a lot.
mike175de said:
Hmm, thx. That is bad...
I bought this phone in China when I was there for work. And I suppose that the german service of Huwaei will not help me at all with this phone.
Does anybody else have any clue how to bring the phone back to life?
Thx a lot.
Click to expand...
Click to collapse
I myself have an H60-L01, bought it from china, bricked and tried everything to revive it but could not, still have to try Huawei customer service in Pakistan, am not sure whether they will be able to help me or not, but will give it a try. I wish you luck buddy. Hope you find a solution.
It's alive ;o)
The phone is working again.
Here are the steps I did for everybody else confrontated with same problem:
1. Download your last working ROM or OTA-File: In my case the OTA-File OTA-EMUI 4.0_H60-L02-L12_B811_B823.zip from this Mega-Link:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!KwhlRKYR
2. Unzip the file and extract recovery.img and boot.img with the Huawei Update Extractor (http://forum.xda-developers.com/showthread.php?t=2433454).
3. Boot the phone into fastboot mode (connect the USB cable, press the power button to turn off and immediately press the volume down button).
4. Use fastboot to flash the two images of 2. If you need fatsboot you can find it here http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip (Extract adb.zip and copy the extracted files from 2. in the folder adb. In the adb folder run cmd.exe as administrator.)
5. Use this commands for flashing:
fastboot devices => If the device is recognized correctly it is displaying a series of numbers
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot reboot
6. Charge the phone with the Huawei charger, not via USB/PC! (50% is enough.)
7. Download in the meantime the Developer ROM H60_EMUI3.1_Android5.1_6.1.1.zip from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
8. Extract the zip file from 7. and copy UPDATE.app onto your SD-Card into /dload
9. Insert the SD without connecting.
9.1. Disconnect the USB cable from your PC or charger.
9.2. Press the Power button to turn off (maybe that is not necessary.)
9.3. When you feel the vibration press 3btn (Vol+ and Vol- and Power).
9.4. When the Honor logo appears connect your SD-Card (continue to press 3btn for 8 -10 more seconds) => Wait for the recovery process, it should start automatically.
10. After installation Android boots. Skip the first step installation (you should now have the 6.1.1. Developer-Edition installed). Rollback to Android 5.1.1 with the Rollback-File Rollback 591 EMUI3.0.zip from here:
http://www.mediafire.com/download/9qrd8zm9280gy5e/Rollback+591+EMUI3.0.zip
Do do so put the unzipped UPDATE.app from the Rollback-File onto your SD-Card and do a local update via the Update Manager.
11. Boot into Android again (it will still be the 6.1.1 Developer Edition). In my case I want to install the latest Android 5.1.1 B535 from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
I did it via local update again.
12.. After installation and booting => Voila here is your working Android 5.1.1 B535 again. Have fun
13. Brick it again with updating to Android 6.0
I hope I could help somebody with my experience to bring his/her phone back to life.
CU, mike
The same can not restore brick
Hello! In what condition I have a phone? My phone is loaded in error func_boot_kernel.
igorxxl said:
Hello! In what condition I have a phone? My phone is loaded in error func_boot_kernel.
Click to expand...
Click to collapse
Have you unlocked and rooted it?
When does it says that message?
error! no func. func_boot_kernel or _recovery
zinko_pt said:
Have you unlocked and rooted it?
When does it says that message?
Click to expand...
Click to collapse
The bootloader is unlocked. Root is. Phone is loaded into the error! no func. func_boot_kernel. If you try to enter into the recovery, the error! no func. func_boot_recovery.
The error is the same as here club.huawei.com/thread-7962289-1-1.html
I tried to put EMUI4.0, then the phone stopped working. Through ADB stitched, weighting system, boot, recovery, cust.img. It shows all ok. But then the error again. He tried to put different versions of TWRP. On the 3 button also does not work.
Thank you for your attention to my problem.
igorxxl said:
The bootloader is unlocked. Root is. Phone is loaded into the error! no func. func_boot_kernel. If you try to enter into the recovery, the error! no func. func_boot_recovery.
The error is the same as here club.huawei.com/thread-7962289-1-1.html
I tried to put EMUI4.0, then the phone stopped working. Through ADB stitched, weighting system, boot, recovery, cust.img. It shows all ok. But then the error again. He tried to put different versions of TWRP. On the 3 button also does not work.
Thank you for your attention to my problem.
Click to expand...
Click to collapse
You can't use 3 button with custom recovery and root. It wont work.
You need stock recovery in the same version as the rest of files used to flash other partitions.
Flash all stock partitions, then just boot the phone. Check if it works. Forget about TWRP and root for now. One thing at a time.
Nothing helps. I sew different versions via Fastboot. Everywhere all shows OK. However, when you restart the exact same mistake again ..
igorxxl said:
Nothing helps. I sew different versions via Fastboot. Everywhere all shows OK. However, when you restart the exact same mistake again ..
Click to expand...
Click to collapse
You can also try installing custom recovery and restore a twrp backup of ROM.
zinko_pt said:
You can't use 3 button with custom recovery and root. It wont work.
You need stock recovery in the same version as the rest of files used to flash other partitions.
Flash all stock partitions, then just boot the phone. Check if it works. Forget about TWRP and root for now. One thing at a time.
Click to expand...
Click to collapse
goldfinv said:
You can also try installing custom recovery and restore a twrp backup of ROM.
Click to expand...
Click to collapse
i'm in the same situation with my honor 6 plus pe-ul00 i'll try this metod!
mike175de said:
The phone is working again.
Here are the steps I did for everybody else confrontated with same problem:
1. Download your last working ROM or OTA-File: In my case the OTA-File OTA-EMUI 4.0_H60-L02-L12_B811_B823.zip from this Mega-Link:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!KwhlRKYR
2. Unzip the file and extract recovery.img and boot.img with the Huawei Update Extractor (http://forum.xda-developers.com/showthread.php?t=2433454).
3. Boot the phone into fastboot mode (connect the USB cable, press the power button to turn off and immediately press the volume down button).
4. Use fastboot to flash the two images of 2. If you need fatsboot you can find it here http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip (Extract adb.zip and copy the extracted files from 2. in the folder adb. In the adb folder run cmd.exe as administrator.)
5. Use this commands for flashing:
fastboot devices => If the device is recognized correctly it is displaying a series of numbers
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot reboot
6. Charge the phone with the Huawei charger, not via USB/PC! (50% is enough.)
7. Download in the meantime the Developer ROM H60_EMUI3.1_Android5.1_6.1.1.zip from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
8. Extract the zip file from 7. and copy UPDATE.app onto your SD-Card into /dload
9. Insert the SD without connecting.
9.1. Disconnect the USB cable from your PC or charger.
9.2. Press the Power button to turn off (maybe that is not necessary.)
9.3. When you feel the vibration press 3btn (Vol+ and Vol- and Power).
9.4. When the Honor logo appears connect your SD-Card (continue to press 3btn for 8 -10 more seconds) => Wait for the recovery process, it should start automatically.
10. After installation Android boots. Skip the first step installation (you should now have the 6.1.1. Developer-Edition installed). Rollback to Android 5.1.1 with the Rollback-File Rollback 591 EMUI3.0.zip from here:
http://www.mediafire.com/download/9qrd8zm9280gy5e/Rollback+591+EMUI3.0.zip
Do do so put the unzipped UPDATE.app from the Rollback-File onto your SD-Card and do a local update via the Update Manager.
11. Boot into Android again (it will still be the 6.1.1 Developer Edition). In my case I want to install the latest Android 5.1.1 B535 from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
I did it via local update again.
12.. After installation and booting => Voila here is your working Android 5.1.1 B535 again. Have fun
13. Brick it again with updating to Android 6.0 [emoji14]
I hope I could help somebody with my experience to bring his/her phone back to life.
CU, mike
Click to expand...
Click to collapse
I got a problem at 9.3 or 9.4. The recovery wont start i see only honor logo i used PE_EMUI3.1_Android5.1_6.1.1.zip (as developer edition i.e sdcard/dload/UPDATE.APP) and PE-UL00-V100R001CHNC00B200.zip to extract and flash BOOT.img and RECOVERY.img
any ideas why i can't enter in recovery? =(
EDIT: "fixed with DC-Phoenix tool"
Ok so I recently upgraded to lineage OS and it had a few issues, as in it kept restarting when you left it alone, so I went into TWRP and did a factory reset and then tried reinstalling it. But when it rebooted it went straight into recovery so, I thought oh lets just use a backup I made, same issues will only boot into recovery. So looking around I couldn't find much to help with this, so I tried flashing other ROMs including stock, no luck, I then tried re-flashing TWRP including all compatible versions, no luck either. So I don't know what to do as I don't have a way to boot the phone anymore, also Windows only sees an empty TWRP folder with one file in so all the other folders have gone so I now have 22.6 GB free of 23.4GB. Any help will be great as I would like my phone back.
Ps all my backups are on an external sd card and I don't care about lost data as it's mostly on the sd card anyway
Any help appreciated
Fixed it myself
Ok so what I did was flash the stock recovery and then rebooted it fixed itself
how did you manage to go into fastboot mode to flash stock recovery??? i am unable to flash recovery via the TWRP reboot>bootloader i keep having an unknown command
mine's the same, if it goes to fastboot I can't do anything, just get a blackscreen with fastboot mode written in tiny writing in the bottom left hand corner. How do you flash the stock recovery?
andydgg said:
mine's the same, if it goes to fastboot I can't do anything, just get a blackscreen with fastboot mode written in tiny writing in the bottom left hand corner. How do you flash the stock recovery?
Click to expand...
Click to collapse
Connect to PC. Use fastboot from PC to flash recovery. From a command window type:
fastboot flash recovery original.img
Replace "original" with the name of the original recovery image.
I am using honor view 10 bkl- l09 c675 and i unlocked the boothloader and flashed cosmic rom. I didnt like the camera and the overall feel so i thought of installing the stock firmware but its not happening. After installing cosmic rom i cant use twrp. the official one doesn't flash anything and the unofficial one is not working. I have tried the sd card dload method , i have tried extracting via update extractor but there are no boot.img or recovery.img and no ramdisk recovery.img there is only system.img.
I am so confused rn. i have tried 10 different update.app form every page but nothing seems to work. The only option i can think off is funky huawie but its 40$. please help
PS : provide the links. it is stuck on bootloops and will the company help with it ?
Download full b130 package from FF, and use no check recovery to flash it.
Or flash system.img using fastboot commands
This worked for me (l09): https://forum.xda-developers.com/8-...awei-p8-lite-2017-honor-t3766652#post76463918
put the smartphone in fastboot ... holding down the volume key and insert the usb cable .... then flash the original file system, kernel stock and stock ramdisk.
- We turn off our mobile
- Keep the buttons pressed: ON / OFF + Upload Volume (do not release the buttons until the Huawei logo appears)
- Once past the Huawei logo, we release the buttons
- In a matter of seconds the recovery will appear
There are three options:
1. Reboot systema now (to exit)
2. Wipe data / factory reset (erase everything and leave it as the first day)
3. Wipe cache partition (clear the cache of all installed apps)
Very careful, just one click and do it without warning with another window
Good luck friend!!