Related
Hi.
My OnePlus One wont boot up anymore.
I was playing dead trigger 2, when suddenly the phone froze (first time the it happend)
I restarted it with holding down the power button.
After restart, it hung on CM11 boot screen, not boot loop, but let it load for 10min, still at CM11 boot screen.
Restart again with power button, but this time it wont boot past OnePlus One boot screen, after the first boot screen, it is a never ending boot loop.
I was able to get to recovery (TWRP), tried to reinstall ROM (CM11 nightly 04.10.14), still boot loop after OnePlus One boot screen.
Tried to wipe date, cache, dalvik, and reinstall, still boot loop.
I am able to get to fastboot.
So what is the next thing to do?
Try to flash back to stock? How can I do this without format internal storage?
Use "adb pull" to extract any files you want to recover.
Then flash back to stock. It will automatically wipe everything.
Gamm86 said:
Use "adb pull" to extract any files you want to recover.
Then flash back to stock. It will automatically wipe everything.
Click to expand...
Click to collapse
Well, I got the 64GB version, and last time I checked, I had 4GB free.
Can I pull whole titanium backup folder?
ole12 said:
Well, I got the 64GB version, and last time I checked, I had 4GB free.
Can I pull whole titanium backup folder?
Click to expand...
Click to collapse
Sure...assuming it is still there...
Code:
adb pull /sdcard/TitaniumBackup/
ole12 said:
Hi.
My OnePlus One wont boot up anymore.
I was playing dead trigger 2, when suddenly the phone froze (first time the it happend)
I restarted it with holding down the power button.
After restart, it hung on CM11 boot screen, not boot loop, but let it load for 10min, still at CM11 boot screen.
Restart again with power button, but this time it wont boot past OnePlus One boot screen, after the first boot screen, it is a never ending boot loop.
I was able to get to recovery (TWRP), tried to reinstall ROM (CM11 nightly 04.10.14), still boot loop after OnePlus One boot screen.
Tried to wipe date, cache, dalvik, and reinstall, still boot loop.
I am able to get to fastboot.
So what is the next thing to do?
Try to flash back to stock? How can I do this without format internal storage?
Click to expand...
Click to collapse
data/wipe and then advanced and wipe system as well. then reflash rom and gapps. do this after you backup all your stuff but you should not try and restore with TB after you get it back up and running. Just my opinion
Same Issue here..
playya said:
data/wipe and then advanced and wipe system as well. then reflash rom and gapps. do this after you backup all your stuff but you should not try and restore with TB after you get it back up and running. Just my opinion
Click to expand...
Click to collapse
I tried literally everything..
I was on multi rom and using Mahdi and CM11s(Internal).
Then i stuck in black screen that my phone wont wake up but LED was blinking. Did a reboot holding power button.
After that when I selected the internal rom it just gave a vibration and came to CM boot logo. Now I tried reflashing 3-4 roms doing whole wipe but no change. Then I flashed Stock with toolkit and it says successful but no booting..
Totally worried.. Please someone help here.. :crying:
rana103 said:
I tried literally everything..
I was on multi rom and using Mahdi and CM11s(Internal).
Then i stuck in black screen that my phone wont wake up but LED was blinking. Did a reboot holding power button.
After that when I selected the internal rom it just gave a vibration and came to CM boot logo. Now I tried reflashing 3-4 roms doing whole wipe but no change. Then I flashed Stock with toolkit and it says successful but no booting..
Totally worried.. Please someone help here.. :crying:
Click to expand...
Click to collapse
you flashed stock with toolkit? first off leave toolkit alone.... Did you flash the .img files? or you flashed a zip file to get back to stock?
I know you are upset but you say you have tried everything. Did you try this thread http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Edit: Also there's no crying in rooting!
So, I just used fastboot to restore it back to stock, and it is STILL bootlooping after OnePlus One screen.
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Downloaded files from this site, and extraced the XNPH33R zip file, and run the flash.all file.
It says completed after writing everything, no error. But still wont boot up:/
So I tried installing every file manually following this guide: http://www.androidheadlines.com/page/2. No luck
The same problem here. I started facebook, It rebooted, 10 mins of CM logo, power off - neverending bootloop.
Reinstalled all via fastboot, ... still in bootloop.
RMA ?
peyooo said:
The same problem here. I started facebook, It rebooted, 10 mins of CM logo, power off - neverending bootloop.
Reinstalled all via fastboot, ... still in bootloop.
RMA ?
Click to expand...
Click to collapse
ole12 said:
So, I just used fastboot to restore it back to stock, and it is STILL bootlooping after OnePlus One screen.
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Downloaded files from this site, and extraced the XNPH33R zip file, and run the flash.all file.
It says completed after writing everything, no error. But still wont boot up:/
So I tried installing every file manually following this guide: http://www.androidheadlines.com/page/2. No luck
Click to expand...
Click to collapse
flash persist.img and reserve4.img as decribed here: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
BACKUP FIRST!
I have the same issue! Suddenly the screen froze. He did not respond to any button, either physical or capacitive. It was well for several minutes (20). Finally I opted for a "hard reset". I turned it on again and this time the screen froze while loading Cyanogen (Hexagon logo). Never happened there. 30 minutes later, I opted for a new "hard reset". Since then, never goes to the home screen (1 + logo and "powered by android"), reseteándose again and again, over and over again without end. Bootlooping :crying::crying:
I have tried everything to get it back, enter in the "recovery", delete data, cache, factory reset ... nothing makes then pass the initial screen.
I even managed to flash with CWM recovery and ADB one posteriomente whole mod, nothing works...
---------- Post added at 04:42 PM ---------- Previous post was at 04:02 PM ----------
luka1002 said:
flash persist.img and reserve4.img as decribed here: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
BACKUP FIRST!
Click to expand...
Click to collapse
YOU ARE MY HERO!! THANK A LOT... at least it's working again. Flashing persist.img and reserve4.img was the right key! :good::laugh:
For the records, I flash too the XNPH30O... upgradeing it now to 38R
Hello,
I have big problem. I tried to upgrade to lollipop version, used it for one hour and then decided to get back to kitkat. For the procedure I used some tool from killerdogKD which name is MT7-L09 Unbrick (it is a fastboot). The procedure went, phone rebooted and got stuck in boot loop (only logo is showed for few seconds). Now I can only get in fastboot and rescue mode. I've tried to flash stock rom, but without success. Any suggestions? PS. Yes, I now I am jackass and sorry for my bad English:angel:
Stock recovery installed (extracted from official KK ROM)??? 3 button procedure already tried?
Will not work. Are there no going back. He can recover only 5.1.
For the people hanging in Bootllop because they have the 4.4.X Recovery flashed.
Load zip, go to the boot loader and the two flash imgs.
command:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
If both of the 5.1.
https://mega.co.nz/#!DNw13JhK!7ATC9p...G50saLGZG3vKzM
KK is not possible 5.1, just with dload the flash 5.1 again. Is indeed just about the one that has 5.1 Recovery again.
Here read next time.
http://forum.xda-developers.com/mate-7/general/mate-7-update-to-lollipop-screenshots-t3125227/page28
I have the same problem and probably caused by same thing. But I can' even enter bootloader. When phone was bootlooping, I turned it off. Then I tried to get into recovery (by holding power + volume down), but phone always shut down after Huawei logo appears (shut down with short vibration).
It does not matter when I release the buttons, I also tried the recovery (vol up + power) or the force update mode (vol up + vol down + power).
Is there any solution to this? I really hope so...
Look at my post and Liks.
Thank you Fooox1 for trying to help, but the problem is, that I can't even enter the bootloader (and your steps require that). I think that international Mate7 have different key combination for entering bootloader? Check also this: http://forum.xda-developers.com/mate-7/help/fastboot-mode-t3086531
It is true that even before I was not able to get into bootloader with vol down + power, so maybe there is just different key combination or it is not possible at all...
I think I will try to write to Huawei support.
In the bootloader you come when the power is off and you Vol - holding down, then to the PC. To turn it off properly you must Vol - and Power button until it vibrates.
Key combination is the same for all.
I know, that is what I am doing it. And I already did it with many other phones successfully, so its not like this is my first time.
I am holding down power + vol down
Phone vibrates, I am still holding both buttons
Huawei logo appears, I am releasing power button, but still holding vol down button
Phone vibrates and turn off
I also tried to release power button when phone vibrates, or not release both buttons at all or I don't know what else. Tried 100x times.
I will try to contact Huawei, maybe it is known issue. It should really be same key combinations for all devices.
Thank you.
The Mate mus but this depend on the USB, otherwise it does not come into the bootloader.
Whoa! I did it. Yes, it was connected in USB, but in quickcharge USB. I tried different one and I am in!
For some reason, it did not like the quickcharge USB port, strange.
@Fooox1: but thank you, with your last comment I got the idea to try different USB
Well, I am little bit furhter, but still not working unfortunately. I got into bootloader, I flashed the boot and recovery. Then I was trying to three buttons force update and it is still failing.
I have Update.zip in dload folder on sd card, but update is failing immediatelly...
So now, I started the three buttons update while connected to computer via USB and it is actually doing something. But it is too soon to say if it helped (43%).
can't boot too
I need your help Guy's
My Mate 7 did not start after i rooted the lollipop rom with kingroot. I tried to put back the 5.1 boot.img and the recovery.img. After that i tried to flash the ota 5.1 rom agian with the 3 bottons mode. The phone startet the Update but it get stocked by 90%. I waited ca. 10 min after i just rebooted the phone. Now the Phone starts with the Huawei Ascend sign two times and after that i am in recovery mode. I don't know what i can do now! Can anyone help me please?
Yes, I have the same problem
driver84 said:
I need your help Guy's
My Mate 7 did not start after i rooted the lollipop rom with kingroot. I tried to put back the 5.1 boot.img and the recovery.img. After that i tried to flash the ota 5.1 rom agian with the 3 bottons mode. The phone startet the Update but it get stocked by 90%. I waited ca. 10 min after i just rebooted the phone. Now the Phone starts with the Huawei Ascend sign two times and after that i am in recovery mode. I don't know what i can do now! Can anyone help me please?
Click to expand...
Click to collapse
Same here! Help!
must we send in warranty?
So it seems to me, that problem is Huawei. Once, they are using Update.APP and later Update.ZIP, not sure why.
- recovery from 5.1 is working, but it is expectin Update.APP, but 5.1 update is in Update.ZIP, so it fails immediately (with error Update.APP not found). Yes, when you connect to phone to computer, it seems that it is doing something and it will get to 90%. But it is actually doing nothing, you can even pull out the sd card and it is the same. I think it is waiting for some action from computer, but not sure which (I also tried to install HiSuite and do something with it, but no success).
- recovery from update B137 will accept Update.ZIP, but when you try to flash it you won't be able to get in it, it is not working (I also tried B127).
So now, we either need recovery, which will work on 5.1 and will accept Update.ZIP or we need update packed as Update.APP (and yes, I tried to rename it etc.). So actually, our phones are pretty ok, we can get in recovery etc., but Huawei is messing with this different formats for some reason
@Fooox1: Do you have any ideas? Maybe you have another bootloader / recovery image? How did you got the 5.1? Thank you...
Edit: maybe the problem is, that we are trying to run the update OTA (Update.ZIP) instead of full rom (Update.APP)? Is this how it is divided, Update.ZIP is just incremental update, while Update.APP is full rom? If that is the case, we will need the full rom, maybe Huawei can release it?
I have not the problem, but users in our forum. I have the boat and recovery.img from the update unzip, a user has then flashed via fastboot and sin device was running again. For him only recovery was gone after he has the Kang Recovery flashed. The Update.zip he did not need to flash.
Other users have only the boot and recovery.img flashed and then the not unpacked update.zip in a folder (dload) on the SD and these then flashed three fingers method. What also has to work.
Here is still the boat and recovery.img of 5.1.
https://mega.co.nz/#!DNw13JhK!7ATC9pAUID0VyX5N3pQwQLbb_VyuOG50saLGZG3vKzM
And update.zip
https://mega.co.nz/#!vdYlxQIA!P34e3RI-hQT1ZY2WnfOosGmkq2wlr6NViq6ehQuWN5k
I think it may help if somebody will create *.img files from Lollipop, then we might be able to flash it via fastboot (the same as it is in this MT7-L09 Unbrick). I think we will need:
boot.img - ok
cache.img
cust.img
recovery.img - ok
system.img
userdata.img
Can make you yourself. Unzip, when present therein Update.app the extension .app in change .zip and unpack. Now you have another Update.app, this you can unpack the Huaweiextraktor, you've got your files. However, it does not contain all IMGs.
You could try but the resulting Update.app to pack in the dload folder and flash. If so, then the original and encrypted.
Hallo again,
i just called the Huawei Service Center in Germany. They openend up a Ticket for me. They told me to make a factory reset and after that the Phone should boot normaly. I did that, but still the same is happening. The shows the Huawei Ascend Logo 2 times and after that i am in recovery mode again.
The only thing i can do next, is to send the phone to the Huawei Service Center and hopefully i will get it back in 7 Days.
I found a guide to downgrade my honor h60 l02 and it said to replace the recovery and system with the stock ones from SYSTEM.img and RECOVERY.img in official roms (through fastboot) and I got those files from version b535 using huawei extractor. After flashing those 2 I couldn't start the 3 button format procedure to update with the b535 rom in the dload folder on my sdcard. So I searched for an unbrick procedure and found one on multitool honor 6 xda page. I flashed the boot,cust,system,recovery from b535 with multitool unbrick procedure and still couldn't get in the emui installation screen by pressing vol+vol-power. I tried reformatting sdcard to fat 32 and put again dload folder with update.app inside. I even tried to press the 3 buttons with card partially introduced but still can't start the update procedure. Used another microsd card but no starting. I finally tried to install a custom recovery but only got to install twrp 2.8.70 v2 for emui 4.0 . Before the whole BIG problem I think I had rom with 6.1.19 version which actually had problems with the bluetooth not starting and that was the reason I wanted to downgrade. I also tried to install 2 custom roms for h60 l02 but I got error on zip installation which seems weird considering at list that should work if I can't use the update procedure. I could probablly use fastboot to install all images required for rom but I can't find a scatter file info or a partition guide anywhere for h60 l02 because I cant install any zip from twrp recovery except gapps.
Any help is welcomed! I'll buy you a bear if u can help me !
Problem solved
So I finally got to fix the phone. I found out that the phone was updated to a Marshmallow rom in the beta stage by my friend who gave it to me. The rom was identified succesfully after some searches on 4pda.ru forums where a couple of russians are experimenting how to put android 6 on honor 6 devices. The version was 5.12.31_beta which in device id I think it apears as h60-C00b690sp01. I put the stock recovery and boot from that image with fastboot on phone. Wanted to put also system and cust images but the rom is an update zip which has mixt type of data (system, cust and a few other partition datas are directly in the zip with meta and inf datas while boot,recovery and a few other partition datas are inside the update.app in the zip). Luckilly for me after the boot and recovery flash I could start stock recovery with vol+power button press and also could finally start force update procedure with vol+vol-power buttons pressed (keep in mind that from fastboot I pressed the 3 buttons continuoselly while the phone restarted , went to a honor logo display, after about 5 seconds it restarted and started emui installation screen; for some reason even from powered off state the device needed to go to the honor screen before on the restart to emui installation screen and Ive seen videos where the devices just go straight to emui installation screen). I got a downgrade package from 4pda.ru forums and tried to install it with forced update procedure but it got stuck at 5%. After 1 more day I figured out that I need to pull the usb cable out before the emui installation screen because it would show a usb connected icon on screen instead of showing emui installation icon (I thought at first that thats how it should look for marshmallow stock roms xD) and Im thinking that if u keep usb cable plugged in it tries to get flash image from usb and if that is unplugged it tries to get image from sdcard dload folder. So I flashed the downgrade version and after restart to honor logo screen I restarted device to fastboot mode with ofc vol-power buttons pressed and pulled the sdcard out. I replaced downgrade package (update. app from H60-LX2_EMUI4.0_2_EMUI3.1 dload) with the dload folder of the b535 stable rom (H60-L02-L12_EMUI3.1_Android5.1_C00B535 rom) on the sdcard. I restarted device and used again 3 button update without usb plugged in xD and it installed all the way. After 100% installation the device rebooted and after showing a big „w” it got to pulsating honor logo screen and after about 10 minutes it showed me language menu for language selection. And the desperation saga ended xD. Happy ending!!!
My Honor 8 (FRD-L04) with official firmware (latest), unlocked bootloader and TWRP recovery, ended in a boot loop
turns on, blue screen, gives the orange unlocked bootloader screen, loads animation and stays on blue screen with honor in white, dims screen and reboots
happened after tinkering around with Magisk and AppSystemizer
moved GPS Joystick to /system/app/ and enabled the options in app, rebooted my phone and it kept rebooting
I can get to fastboot and twrp,
I made the not so wise decision of a partial backup after installing twrp, only backing up Boot, Cache, System and Vendor (didn't have enough space for full)
I downloaded HuaweiUpdateExtraxtor and did the following:
1. Extracted the recovery.img from update.app
2. Fastboot flashed the extracted recovery.img
3. Copied the update.app to a folder named dload located on my uSD root
4. Unplugged and rebooted while pressing vol up, vol down and power
It loads the EMUI update screen says installing update, 5% and fails
tried those steps with B122, B141, B150, B162
Am I missing something?
I had a very similar experience about a month ago.
I was never able to get back to stock because the dload method failed on all my tries on my L04 at 5% so maybe I'm not one to say whether you're doing it correctly but that's the same method I've used that I found from multiple sources.
If you don't have a back up phone I'd suggest flashing twrp and going to a custom rom, aospa is working very well for me, otherwise I think the best bet is to wait for a new update and get that update.app because every link I've tried thats supposed to direct to hicloud L04 B385 update.app is broken, while the L09 links seem to work.
Edit: According to this guide , you should only be pressing volume up and power, so try that.
progress so far, I followed Rommco05 instructions and downloaded
http://update.hicloud.com:8180/TDS/d...ull/update.zip
from https://forum.xda-developers.com/ho...tock-firmware-packages-honor-8-t3501942/page8
flashed TWRP and installed the first one through TWRP, when rebooted gave me a red exclamation! (can't remember what it said)
Downloaded B360 from
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=FRD-L04&firmware_page=0
and copied the update.app to dload folder on uSD
vol up, vol down and power and it finally installed something, but was asking for storage password and keyboard was missing
read somewhere that the recently flashed firmware was trying to use the previous firmware storage or something like that and was fixed by deleting /data
so I went to erecovery (vol up, power) and wiped data... it fixed the storage password but it booted a weird firmware (very laggy, said it was B389 and had no keyboard!!! )
finally followed instructions on link provided by gophillyourself (Thanks!) and that rolled me back to B122!
Currently updating using updater
Hi,
I got some issues since this morning and I went through all the forum but can't find any solution.
I explain my issue :
I unlock the boot loader, than install TWRP-3.1.1-1-frd. Here everything is fine.
After that I wipe all my phone with TWRP (including internal storage...) and I tried to install OpenKirin's RROS v5.8.4 Rom. I got some error (something like unable to mount /curst and multiple error like this)
But here, I got my first issue, after reboot the phone wasn't going after the first honor logo (when I tried to turn off the phone it was restarting directly)
So I start my phone in fast boot mode and refresh the TWRP.
Now I go through the first honor blue loading and I get stuck on "Your device is booting now..." (if I try to go to TWRP) and if I try to run normally my phone, I get into a loop between this screen and honor blue loading... I cannot turn off totally the phone (it's always trying to reboot)
If somebody could help me it would be so nice from you !
Edit :
I can't launch dload as it run into the screen "your device is booting now..." when I do the touch combination
I tried to flash the system boot curst and recovery from the latest official firmware (FRD-l09C432B403 I think) using the extractor Huawai and fast boot but nothing appears...
I'm totally lost at this point...
Sorry for my english, I'm french
Ps: My phone is FRD-L09
See you !
i have same issue