I used the toolkit to flash the stock CM image as phone is stuck at one plus one logo . Flashing the stock worked without any errors after phone rebooted it's still stuck in bootloop. Is that means phone needs RMA, I can get into fastboot and recovery ..
I think you should come take a peak at my thread. Your issue sounds familiar
http://forum.xda-developers.com/showthread.php?p=55488755
So by issuing these commands
fastboot erase persist
fastboot flash persist persist.img
and flashing OS will fix the bootloop issue ??
I am getting this error " finished. total time: 0.009s
error: failed to load 'cm-11.0-XNPH30O-bacon-signed-fastboot.zip': No such file
or directory" but the file is in the location ..
sguy156 said:
I am getting this error " finished. total time: 0.009s
error: failed to load 'cm-11.0-XNPH30O-bacon-signed-fastboot.zip': No such file
or directory" but the file is in the location ..
Click to expand...
Click to collapse
Did you try rebooting after flashing the persist?
If yes and you still have no is download 38r and flash it instead
https://forums.oneplus.net/threads/38r-factory-images-now-available.147875/
Related
Hello,
I have a Motorola Moto G XT1032 on which I have successfully unlocked the bootloader. I can access to recovery (CWM 6.0.4.7) and transfer files using adb in this mod. However, CWM does not get past the splash logo (I do get the occasionnal lag when CWM rebuilds the cache, but this is another minor issue). I have tried the following ROMs, installed each after formatting /system, /data and /cache:
cm-11-20140308-SNAPSHOT-M4-falcon.zip
cm-11-20140405-SNAPSHOT-M5-falcon.zip
cm-11-20140504-SNAPSHOT-M6-falcon.zip
cm-11-20140613-NIGHTLY-falcon.zip
cm-11-20140730-NIGHTLY-falcon.zip
cm-11-20140823-NIGHTLY-falcon.zip
None worked. I did checked the md5 checksums. I have also tried installing GApps using gapps-kk-20140606-signed.zip .
I do not know how to get more information on what happens when CM11 stucks during the boot. 'Show log' from recovery only prints some configuration information as well as:
Code:
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
From what I undersood, extendedcommand is an optional executable used to launch stuff at boot.
I found some ideas from another thread and tried locking/unlocking oem:
Code:
$ fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.057s]
finished. total time: 0.057s
$ fastboot oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.037s]
finished. total time: 0.037s
$ fastboot oem unlock
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.008s
Additionnally I also reinstalled recovery:
Code:
$ fastboot erase recovery
$ fastboot flash recovery CWM-swipe-6.0.4.7-falcon.img
I did have a message "Mismatched partition size (recovery)" but CWM starts fine. I then reinstalled CM11 again, but it did not help either.
Would you have further instruction to try and get CM11 to work?
Just a short post to avoid the thread from being buried down into oblivion.
Same happened to me days ago. I was unable to install any custom ROM. I was in Enhdroix and I flashed the original version of my ROM via fast boot but every time I tried to install a custom was stocked and bootlogo. Some how I figured that the boot loader of the original version was corrupted so I flashed a different stock ROM, after that was able to install custom.
The recovery message is normal you can check videos or post.
Hope this helps my friend.
To prevent any further problems, I also recommend that you flash twrp or philz recovery because the stock cwm recovery is outdated and it will give you problems while flashing ROMs in the future...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
ThisIsMadness said:
Just a short post to avoid the thread from being buried down into oblivion.
Click to expand...
Click to collapse
Check previous answers
Thanks for your help, I finally got it to work!
If someone gets stuck with the same problem, here is what I did:
first, fastboot flash recovery to TWRP
reinstalling (wipe and so) CM11 from TWRP did not work any better
I reinstalled a stock ROM following http://forum.xda-developers.com/showthread.php?t=2542219
I did not boot at all (no logo), but I could still get to fastboot
I reinstalled TWRP, and then CM11
it worked!
From my own diagnosis, I must have accidentely corrupted a partition with fastboot flash. Or maybe I wiped something that I should not have. Anyway, by reinstalling stock, I restored all the partitions and could install CM11. I do not think CWM is to blame here.
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,
rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?
therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?
heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,
Bump!
Does anyone have any other suggestion please?
Thanks,
Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!
Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.
I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?
I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
if you have the boot backup then restore it.
venugopalu007 said:
if you have the boot backup then restore it.
Click to expand...
Click to collapse
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
if you cannot find the boot.img
just do a rollback bro
here is the link
first dload this
http://download-c.huawei.com/download/downloadCenter?downloadId=94070&version=376169&siteCode=de-h
and this now
if your device is BLN-L21C432B151 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v84712/f1/full/update.zip
or BLN-L21C185B131 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v75593/f1/full/update.zip
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Stinks said:
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Click to expand...
Click to collapse
The guide from "cyberkey.in/how-to-root-honor-6x-100-working/" is simply wrong when it comes to flashing the twrp recovery. If you really followed this guide completely then you flashed the recovery to the boot partition.
Use "fastboot flash recovery twrp.img" to flash the recovery.
You will still have to flash the boot image to your boot partition then (fastboot flash boot boot.img).
Stinks said:
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
Click to expand...
Click to collapse
Use fastboot flash recovery twrpname.img to flash the recovery
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
V
Stinks said:
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
Click to expand...
Click to collapse
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
venugopalu007 said:
V
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
Click to expand...
Click to collapse
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
Bro y this ,just do a rollback .
Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
I recommend you to download firmware files only from the official honor website or by using the huawei firmware finder(https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146)
In this case try to use huawei firmware finder to get the right stock version for your phone. Download these two files: e.g. update.zip & update_full_BLN-L21_hw_eu.zip.
Export the following image files: recovery, system, boot and cust.
The try to flash them:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
If flashing a partition via fastboot fails then it is usually because it's the wrong image or just not made for your phone.
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Stinks said:
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Click to expand...
Click to collapse
Glad you revived your phone
question
​
Stinks said:
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
Click to expand...
Click to collapse
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
[email protected] said:
question
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
Click to expand...
Click to collapse
did you solve your issue.....I have same problem now
nokiasatyam said:
did you solve your issue.....I have same problem now
Click to expand...
Click to collapse
Hello, could you be more specific about your problem? I'll be able to help you.
Brief Explanation:
From the screen on which you're stuck, press and hold power button for about 10 seconds to forcibly restart your device. when you see the same screen again, immediately press and hold volume up button(for about 3 seconds) to boot to eRecovery.
> Choose shut down option on eRecovery. press and hold vol down button and insert the charging cable to boot to fastboot.
> Press and hold power and volume up button to boot to recovery. (You could do this even from fastboot screen and the screen you're stuck at).
Hey
I tried to downgrade from MM to Lollipop. I flashed wrong kdz file, Now after that my phone got dead.
After trying every method Qfil,in qcon 9008 mode, i used MIflash and flash H810Laf img , it resulted in waken up and booted directly into fastboot.
Im unable to erase or flash any partition.
Log:
D:\>fastboot devices
xxxxxxxx fastboot>>Device shown
D:\>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.016s
2nd
when i press volume up+usb ,no download mode,only get secure booting error.
Any help soft or hard method.
Thanks in advance.
nabeelahmad909 said:
Hey
I tried to downgrade from MM to Lollipop. I flashed wrong kdz file, Now after that my phone got dead.
After trying every method Qfil,in qcon 9008 mode, i used MIflash and flash H810Laf img , it resulted in waken up and booted directly into fastboot.
Im unable to erase or flash any partition.
Log:
D:\>fastboot devices
xxxxxxxx fastboot>>Device shown
D:\>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.016s
2nd
when i press volume up+usb ,no download mode,only get secure booting error.
Any help soft or hard method.
Thanks in advance.
Click to expand...
Click to collapse
What do you mean by flashed wrong kdz? If you where running the latest version of MM you just bricked your device. You cannot downgrade downgrading tripped antirollback. Only fix is a board replacement.
Sent from my iPhone using Tapatalk
there is fastboot mode available but unable to write.
One plus 7 pro, European version
So i was running Lineage OS on my phone for some time now (latest base update i did was to ob1 as far as i am aware), when there was an update lately
I installed it as normal, but the phone would not get past the boot animation and kept restarting, so i went back to the other slot to see if that still worked, but it only had a laggy boot animation, which never booted
I then installed the previous version that i was running before the update back to the other slot, hoping it would solve the problem of not booting (that worked before already) but it still did not boot
I saw someone post they had 10.3 installed as base so i restored the ob1 installation with a fastboot rom i still had on my hard drive, but upon finishing the phone just went into crash dump mode showing
dm-verity device corrupted force dump
kernel_restart
I tried another install just to be sure, but same result
I then tried flashing twrp to the boot partition to at least get there, but the phone just went straight to fastboot upon doing that
Fastboot boot still seems broken and just shows
D:\Minimal ADB and Fastboot>fastboot boot tw.img
downloading 'boot.img'...
OKAY [ 1.228s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.346s
I searched around if there were other ways to install twrp from fastboot, and found this tool (https://forum.xda-developers.com/an...g/apk-img-dat-br-one-click-decompile-t3886057) that promises to unpack and repack the boot.img, so i hoped i could use that to manually add twrp to it, but it failed to unpack the file
Next thing i found was this MSM tool post (https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691) instructed to hold volume up and down for 5 seconds before connecting the phone to a pc, and the program actually picked it up, however the phone started itself after a few seconds and went back to crashdump mode
At this point i'm seriously out of ideas, does anyone else have other ideas that i missed?
Does anyone have a boot img with twrp?
keep trying the MSM tool. it WILL work.
if you can get into fastboot again, type in fastboot reboot edl in ADB
Luke JC said:
Fastboot boot still seems broken and just shows
D:\Minimal ADB and Fastboot>fastboot boot tw.img
downloading 'boot.img'...
OKAY [ 1.228s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.346s
Click to expand...
Click to collapse
This is indeed what typically shows for an error when fastboot boot isn't working. Probably due to using an older fastboot ROM. I'd try to use a newer fastboot ROM, or you can flash a patched boot image, which is how the phone was being rooted before fastboot boot was fixed:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
If I recall correctly, you can't fastboot boot with android 10.