I decided to reflash TWRP using Fastboot (Yes, it did show up in Fastboot), and I was able to flash it using:
fastboot flash recovery twrp.img
But when I tried to boot from it using: fastboot boot twrp.img
I get the following error:
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (14698 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.274s]
finished. total time: 0.790s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.529s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.578s
plzzzhelp
Hmmmm...i don't think you can't reboot into recovery using fastboot command...you need to use power button + volume down to reboot into recovery manually....
iPusak Gaoq™ said:
Hmmmm...i don't think you can't reboot into recovery using fastboot command...you need to use power button + volume down to reboot into recovery manually....
Click to expand...
Click to collapse
i tried all things..none of them worked..still stucked at oneplus logo..
and i don't have any rom installed..i can only boot into fastboot
battery low!!!!! said:
i tried all things..none of them worked..still stucked at oneplus logo..
and i don't have any rom installed..i can only boot into fastboot
Click to expand...
Click to collapse
re-flash the recovery and don't forget to use this command after flashing recovery....
Code:
fastboot format cache
then reboot to recovery manually....
I have exactly the same problem except I still have a working OS.
After I couldn't boot into recovery I tried to flash a new recovery by using the TWRP app ("flashed successfully"), reboot to the recovery... same thing, it's stuck at the logo. I tried the flashify app as well (flashed successfully)... reboot... same thing.
I also tried to format the cache in fastboot after flashing the recovery which didn't help.
So either I am stuck with this ROM for the rest of my OPOs live or someone can help me.
I am by no means new to flashing. I flash new ROMs since my HTC Desire, I flashed my SGS3 on a weekly basis and I own my OPO since it came out and I never had any problems.
battery low!!!!! said:
i tried all things..none of them worked..still stucked at oneplus logo..
and i don't have any rom installed..i can only boot into fastboot
Click to expand...
Click to collapse
if you don't have ROM installed you can manually flash a a rom from fastboot.
Return your OPO to Stock via fastboot
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
and reinitialize the rooting process, flash Twrp and supersu
Related
Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything, S-off and Unlocked.
Any help is appreciated.
maaavy said:
Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything.
Any help is appreciated.
Click to expand...
Click to collapse
Why not just flash that recovery and then boot to it from the menu? Or you use flashify from within the Rom and change recoveries on the fly?
dottat said:
Why not just flash that recovery and then boot to it from the menu? Or you use flashify from within the Rom and change recoveries on the fly?
Click to expand...
Click to collapse
Worked like a charm. Thanks!
maaavy said:
Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything, S-off and Unlocked.
Any help is appreciated.
Click to expand...
Click to collapse
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
santod040 said:
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
Click to expand...
Click to collapse
Brain fart on my part. Such an obvious mistake. Thanks!
santod040 said:
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
Click to expand...
Click to collapse
I wanted to follow up on this. I've used his idea in the past on another htc device. I'd "fastboot boot <recovery>.img" and I could flash whole ROMs without touching the existing recovery. As soon as you reboot the old recovery is still there. His command wasn't an incorrect syntax for flashing a boot.img it was temporarily booting into a recovery. Is there any reason this wouldn't work nowadays?
cntryby429 said:
I wanted to follow up on this. I've used his idea in the past on another htc device. I'd "fastboot boot <recovery>.img" and I could flash whole ROMs without touching the existing recovery. As soon as you reboot the old recovery is still there. His command wasn't an incorrect syntax for flashing a boot.img it was temporarily booting into a recovery. Is there any reason this wouldn't work nowadays?
Click to expand...
Click to collapse
Yeah I know that was possible in the past, to flash a rom using a recovery one time, without overwriting the current one.
As I've never seen any real need or purpose to doing that, I've never done it that way.
I do know that the other command is what should be used to actually overwrite and flash a new recovery for further use.
So I can't really answer as to whether that method still works or not.
Didn't sound like it did for him though.
I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?
BoredDude said:
I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?
Click to expand...
Click to collapse
You can try to boot directly into twrp with "fastboot boot TWRP.img"
zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s
zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
BoredDude said:
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s
Click to expand...
Click to collapse
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!
ChazzMatt said:
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!
Click to expand...
Click to collapse
I fixed it erasing the TWRP folder in my internal storage
Hello,
Edit: Don't know how or why, but after a couple of more tries I was able to boot the recovery directly and flash the rom. So everything is working fine right now. Admin/mod, would you like to close this thread? Thank you
For some reason I wanted to flash a new rom on my XT1039. In the process I screwed up and got it softbricked. I already had a look at the thread started by alfread56 and although the situation seems quite similar, the offered solutions didn't work out for me.
Right now my phone doens't have any rom installed. Flashing twrp with fastboot suggest everything works allright (using a linux system by the way):
fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (8314 KB)...
OKAY [ 0.295s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.598s
After the reboot and holding the buttons for recovery mode I still get the stock recovery screen. When I select recovery in this menu, the phone shuts down. Because I know holding the recovery buttons on reboot takes some timing, I have redone the procedure of flashing twrp and holding the buttons numerous times. But it never went to the twrp recovery.
Then I tried to boot the twrp image directly with
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.290s]
booting...
OKAY [ 0.230s]
finished. total time: 0.520s
Here I made a mistake: I have also flashed the boot partition with the twrp image with fastboot flash boot recovery.img (don't know how much of problem this is).
Booting up the TWRP image works fine. Then I've wiped dalvik, cache, data, internal storage and after several runs also deleted system by accident, and factory reset. When trying to flash the lineage zip everything works out fine for about 1 second, then the screen flashes en the phone is back in the TWRP screen. Too quick for me to see what the output is, but I do see there are not red marked lines (no errors)
I have tried it with several different ROMS (al checked), with several versions of TWRP and with fastboot and mfastboot. Does anybody know a solution on how to get twrp recovery working on my phone, or why I can't flash a rom when I boot twrp directly? Any help is appreciated!
Thank you in advance.
Regards,
weisa4564
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).
after unlocking my bootloader i tried to flash magisk.zip in fastboot mode by typing fastboot flash boot magisk.zip
now im stuck in fastboot mode. Enter reason: boot failure
with oneplus devices you can always go back to stock with msm tool. is there anything like that for pixel devices? or did i just turn my new phone into a shiny new paper weight?
barbosa212 said:
after unlocking my bootloader i tried to flash magisk.zip in fastboot mode by typing fastboot flash boot magisk.zip
now im stuck in fastboot mode. Enter reason: boot failure
with oneplus devices you can always go back to stock with msm tool. is there anything like that for pixel devices? or did i just turn my new phone into a shiny new paper weight?
Click to expand...
Click to collapse
To root you flash the patched boot image (the one you patched in Magisk), not magisk.zip.
Try flashing the stock boot image to get back to normal and then flash the patched boot image in fastboot.
See this guide.
Lughnasadh said:
To root you flash the patched boot image (the one you patched in Magisk), not magisk.zip.
Try flashing the stock boot image to get back to normal and then flash the patched boot image in fastboot.
See this guide.
Click to expand...
Click to collapse
Sending 'boot_a' (65536 KB) OKAY [ 1.715s]
Writing 'boot_a' (bootloader) unable to update boot image: use unmerged...
OKAY [ 0.144s]
Finished. Total time: 1.897s
now im at "waiting for rescue commands..." what do?
barbosa212 said:
Sending 'boot_a' (65536 KB) OKAY [ 1.715s]
Writing 'boot_a' (bootloader) unable to update boot image: use unmerged...
OKAY [ 0.144s]
Finished. Total time: 1.897s
now im at "waiting for rescue commands..." what do?
Click to expand...
Click to collapse
i held the power button until it rebooted successfully. Thank you so much
barbosa212 said:
i held the power button until it rebooted successfully. Thank you so much
Click to expand...
Click to collapse
If you want to root/flash, I recommend PixelFlasher. A simple and effective tool and saves you from trouble!