Hello
So H2OS boots up just fine. Fastboot mode works. When I boot into recovery mode the oneplus logo shows up, but it is as nothing happens afterwards. I left the device there for more than an hour and still nothing. Flashing from the OS twrp 2.8.7.0 or 3.0.0-2 has no change on this. Flashing from fastboot the same. When I try to boot from fastboot,I get the following error:
[email protected] ~/Downloads $ fastboot boot twrp-3.0.0-2-oneplus2.img
downloading 'boot.img'...
OKAY [ 0.807s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.873s
[email protected] ~/Downloads $ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (31700 KB)...
OKAY [ 0.815s]
writing 'recovery'...
OKAY [ 0.534s]
finished. total time: 1.349s
Any ideas?
Had the same problem. I just flashed MM firmware and then TWRP 3.0.1. It did not worked when i was flashing 3.0.0. Download official TWRP from their site, version 3.0.1.
I know it seems strange but it did help for me. Was not expecting that to fix the problem tho ..
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967
redh4t said:
Had the same problem. I just flashed MM firmware and then TWRP 3.0.1. It did not worked when i was flashing 3.0.0. Download official TWRP from their site, version 3.0.1.
I know it seems strange but it did help for me. Was not expecting that to fix the problem tho ..
Click to expand...
Click to collapse
From what I see there is no, 3.0.1 here,
twrp-3.0.0-2-oneplus2.img 31M
twrp-3.0.0-1-oneplus2.img 30.9M
twrp-3.0.0-0-oneplus2.img 29.2M
twrp-2.8.7.0-oneplus2.img 27.5M
https://dl.twrp.me/oneplus2/
Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.
I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...
Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.
Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?
Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again
Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .
Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Thanks
bijilidk said:
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Thanks
Click to expand...
Click to collapse
This happens when you flash wrong version. You must be using the twrp for KK, while MIUI is LP.
So try this one
https://userscloud.com/a25aszfwkn2z
Tried but not working same error is showing.
[email protected]:~/Desktop/TWRP/img$ sudo fastboot flash recovery twrp.img
[sudo] password for user:
Sorry, try again.
[sudo] password for user:
target reported max download size of 268435456 bytes
sending 'recovery' (13204 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 2.022s]
finished. total time: 2.438s
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.417s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.449s
Once i did this before 'fastboot erase recovery.img' is that a problem?
bijilidk said:
Tried but not working same error is showing.
Once I did this before 'fastboot erase recovery.img' is that a problem?
Click to expand...
Click to collapse
Give these a try too
Twtp 3.0.2 http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=55585
Twrp 2.8.6 https://userscloud.com/m4jy6u5chkkp
Cwm http://www15.zippyshare.com/v/j9lHGdJf/file.html
sasukay said:
Give these a try too
Twtp 3.0.2 http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=55585
Twrp 2.8.6 https://userscloud.com/m4jy6u5chkkp
Cwm http://www15.zippyshare.com/v/j9lHGdJf/file.html
Click to expand...
Click to collapse
No hope tried everything..same error.
bijilidk said:
No hope tried everything..same error.
Click to expand...
Click to collapse
Extract "boot.img" from the root of MIUI rom zip and flash that with "fastboot flash boot boot.img"
Then flash the twrp for lollipop
Otherwise, you'll need to flash the firmware through QFIL Downloader
bijilidk said:
Tried but not working same error is showing.
[email protected]:~/Desktop/TWRP/img$ sudo fastboot flash recovery twrp.img
[sudo] password for user:
Sorry, try again.
[sudo] password for user:
target reported max download size of 268435456 bytes
sending 'recovery' (13204 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 2.022s]
finished. total time: 2.438s
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.417s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.449s
Once i did this before 'fastboot erase recovery.img' is that a problem?
Click to expand...
Click to collapse
It seems you successfully flashed the twrp recovery...............
If your recovery is right i.e.according to your previous os
Then just u need to enter into recovery by pressing 3 buttons at the same time....
if not worked then flash another twrp version....
-Sourav_8434
Thanks for the support @sasukay @Sourav_8434 Revert back to Stock lolipop via Lenovo firmware software.
bijilidk said:
Thanks for the support @sasukay @Sourav_8434 Revert back to Stock lolipop via Lenovo firmware software.
Click to expand...
Click to collapse
Please explain how you did it. I'm also stuck with blank screen and only vibration
neerut said:
Please explain how you did it. I'm also stuck with blank screen and only vibration
Click to expand...
Click to collapse
Refer this link. I used the ( THIRD METHOD )Installing the firmware using Lenovo Downloaders.
https://boycracked.com/2015/06/03/unbrick-lenovo-a6000/
So everything is solved here right ? you can close this thread now i think !
So I tried to flash a custom recovery and got this
C:\Users\kevin>fastboot flash recovery twrp.img
sending 'recovery' (13134 KB)...
OKAY [ 0.432s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.453s]
finished. total time: 0.886s
Was curious if it flashed or not?
EDIT: I got the SU from here and it's still not giving me root after flashing SU to the device.
KevinDel said:
So I tried to flash a custom recovery and got this
C:\Users\kevin>fastboot flash recovery twrp.img
sending 'recovery' (13134 KB)...
OKAY [ 0.432s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.453s]
finished. total time: 0.886s
Was curious if it flashed or not?
EDIT: I got the SU from and it's still not giving me root after flashing SU to the device.
Click to expand...
Click to collapse
From what I've seen so far, you may be trying to flash a custom recovery that is not made for your device, which variant are you using? (ex: XT1760, XT1764, you can see them as SKU in fastboot mode)
Also, from where did you download the twrp?
Moderi said:
From what I've seen so far, you may be trying to flash a custom recovery that is not made for your device, which variant are you using? (ex: XT1760, XT1764, you can see them as SKU in fastboot mode)
Also, from where did you download the twrp?
Click to expand...
Click to collapse
I got the TWRP to actually work now, now it's trying to get SU to work. I got TWRP from here I can't get majisk or SU to run at all though now.
Moderi said:
From what I've seen so far, you may be trying to flash a custom recovery that is not made for your device, which variant are you using? (ex: XT1760, XT1764, you can see them as SKU in fastboot mode)
Also, from where did you download the twrp?
Click to expand...
Click to collapse
Also it's the XT1768 model.
Try installing magisk the new way (without a custom recovery). There are instructions in the main magisk thread.
Good evening everyone. I needed a deep format and in the twrp wipes I selected Internal Storege ... before installing Lineage 17 ... now the twrp is gone too and it's in loop on Fastboot and I can't get out. Which flash software should I use?
I tried to install via fastboot all the twrp that I found on the various sites ... but after the usual two steps ... ok .... ok write ... succes .... reboot with up key and power. ... and back to fastboot
i use twrp 3.4.0, 3.3.1.8, 3.3.1.3, 3.3.1.0
....Desktop\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.504s]
Writing 'recovery' OKAY [ 0.348s]
Finished. Total time: 2.852s
Deaddo6 said:
Good evening everyone. I needed a deep format and in the twrp wipes I selected Internal Storege ... before installing Lineage 17 ... now the twrp is gone too and it's in loop on Fastboot and I can't get out. Which flash software should I use?
I tried to install via fastboot all the twrp that I found on the various sites ... but after the usual two steps ... ok .... ok write ... succes .... reboot with up key and power. ... and back to fastboot
i use twrp 3.4.0, 3.3.1.8, 3.3.1.3, 3.3.1.0
....Desktop\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.504s]
Writing 'recovery' OKAY [ 0.348s]
Finished. Total time: 2.852s
Click to expand...
Click to collapse
Never format persist partition u will be stuck in a fastboot loop, flash this twrp with the pc it has its own script and boot into twrp i guess u just have a missing vbmeta that can cause twrp to disappear in some cases
https://forum.xda-developers.com/mi-9t/how-to/recovery-unofficial-twrp-3-4-0-1-t4135159
Deaddo6 said:
Good evening everyone. I needed a deep format and in the twrp wipes I selected Internal Storege ... before installing Lineage 17 ... now the twrp is gone too and it's in loop on Fastboot and I can't get out. Which flash software should I use?
I tried to install via fastboot all the twrp that I found on the various sites ... but after the usual two steps ... ok .... ok write ... succes .... reboot with up key and power. ... and back to fastboot
i use twrp 3.4.0, 3.3.1.8, 3.3.1.3, 3.3.1.0
....Desktop\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.504s]
Writing 'recovery' OKAY [ 0.348s]
Finished. Total time: 2.852s
Click to expand...
Click to collapse
Also you can use MiFlash and fastboot rom file to flash stock rom from scratch from fastboot.
Deaddo6 said:
Good evening everyone. I needed a deep format and in the twrp wipes I selected Internal Storege ... before installing Lineage 17 ... now the twrp is gone too and it's in loop on Fastboot and I can't get out. Which flash software should I use?
I tried to install via fastboot all the twrp that I found on the various sites ... but after the usual two steps ... ok .... ok write ... succes .... reboot with up key and power. ... and back to fastboot
i use twrp 3.4.0, 3.3.1.8, 3.3.1.3, 3.3.1.0
....Desktop\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.504s]
Writing 'recovery' OKAY [ 0.348s]
Finished. Total time: 2.852s
Click to expand...
Click to collapse
Flash stock rom using miflash,
Uncheck clean and lock
finally I used mi flash ... I modified the "format all and lock" file, to circumvent anti-rollback.
I installed miui 11. Now everything is fine ... thanks