I'm having issues with my recovery after flashing the OOS 3.0 to the phone. My phone is working but when i boot into recovery, it stays on the page saying 1+ powered by android. Anyone else have this issue, or any ways to fix it.
I also tried re-flashing twrp, but i get "FAILED (Remote: dtb not found)" when i try to boot the recovery image.
FireForged said:
I'm having issues with my recovery after flashing the OOS 3.0 to the phone. My phone is working but when i boot into recovery, it stays on the page saying 1+ powered by android. Anyone else have this issue, or any ways to fix it.
I also tried re-flashing twrp, but i get "FAILED (Remote: dtb not found)" when i try to boot the recovery image.
Click to expand...
Click to collapse
u need modified twrp, here is the link: https://www.androidfilehost.com/?fid=24459283995297945
flo071 said:
u need modified twrp, here is the link: https://www.androidfilehost.com/?fid=24459283995297945
Click to expand...
Click to collapse
After using this twrp, and flashed with cmd: fastboot boot recovery.img, I return in twrp-recovery.
So I restart (with disable and/or not disable to change the recovery). But after that I am in the same situation. It is possible to flash the same twrp for another time but that is not what we want
This even doesn't work when I restart to recovery.
Is there another possible solution?
Thanks in advance.
retaliator said:
After using this twrp, and flashed with cmd: fastboot boot recovery.img, I return in twrp-recovery.
So I restart (with disable and/or not disable to change the recovery). But after that I am in the same situation. It is possible to flash the same twrp for another time but that is not what we want
This even doesn't work when I restart to recovery.
Is there another possible solution?
Thanks in advance.
Click to expand...
Click to collapse
i disabled reflashing the original recovery...whats is asked when you reboot in system...
for me this worked....
Thanks for answering me.
I did also disabling reflashing new recovery when reboot in system.
When reboot in recovery the 1+ logo apearred and nothing happens.
I have the same issue - I can get fastboot and flash recoveries, but the OP2 never gets beyond the boot screen. tried flashing different recoveries, no joy.
---------- Post added at 09:43 PM ---------- Previous post was at 09:02 PM ----------
update - got it working.
steps:
flashed recovery.img in this post.
booted into twrp
flashed oldmodem5.1.1 zip I had on my phone
rebooted into recovery
flashed twrp3.0.2.img
flashed new+modem.zip
flashed exdodus nightly
boom, back in business
you can keep that OOS rubbish
my phone also not going past the 1+ logo screen
as told i downloaded the recovery.img from above
restart my device in fastboot
C:\Users\imran\Downloads>fastboot oem unlock
...
OKAY [ 0.005s]
finished. total time: 0.006s
after this command my device again started n struck at that logo i restart again in fastmode to check
C:\Users\imran\Downloads>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.073s]
finished. total time: 0.074s
please help
Hello, i've the solution
Download the FirstAid :
http://forum.xda-developers.com/devdb/project/dl/?id=16684
- Unzip files
- Boot your phone in Fastboot
- Go to Firstaid_v_2_0 -> Firstaid -> then lunch ' firstaid'
Thanks for the reply..
i run the file but still no use
F:\Firstaid>fastboot oem unlock
...
OKAY [ 0.016s]
finished. total time: 0.016s
F:\Firstaid>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.078s]
finished. total time: 0.078s
F:\Firstaid>fastboot flash recovery TWRP.img
target reported max download size of 536870912 bytes
sending 'recovery' (28144 KB)...
OKAY [ 1.047s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.063s
NOTE:if i enter command "fastboot continue" my device is getting started...
Try this, I think you bootloader is still locked
fastboot -i 0x2A70 oem unlock-go
Or follow this guide
http://forum.xda-developers.com/oneplus-2/general/guide-make-oneplus-2-adb-devices-t3218332
Sent from my ONE A2003 using Tapatalk
I had this problem and got the recovery working again with the modified version from above. Where did you get this? and what modification was needed? This is very strange. I never had that kind of a problem.
I flashed my phone back from OxygenOS 3 beta to OxygenOS 2.2.1 to get a working phone again and will now try to revert to the normal recovery again. From there I hope to get twrp 3.0.2.0 and cyanogenmod 13 to work.
UPDATE: normal twrp 3.0.2.0 works again. So my steps to recover from a brick with no accessable recovery to a working phone were:
1. flash modified recovery
2. boot into recovery
3. flash latest stable stock rom
4. flash latest stock twrp
Thanks a lot dude it worked for me
Keep up the good work guys.
What I did to get a working recovery:
1. flash modified recovery from first post in this thread with flashing recovery from pc
2. boot into recovery
3. flash latest stable stock rom
4. flash in recovery the latest recovery from first post
5. flash beta version Oxygen3
6. flash again twrp in recovery
7. flash superuser
8. disable replace recovery
All is well done.
Thanks for helping me mates!
I found out that it is enough when you:
1. copy modified recovery from first post in this thread to your phone
2. flash modified recovery from your pc to your phone
3. boot in recovery
4. flash the recovery you copied to your phone in installed recovery
5. restart with disable replace recovery
Thats enough to do the trick.
I am sorry to reply to an old post but I am unsure if other people are still having issues with this like I was. Here is some info from https://twrp.me/devices/oneplustwo.html :
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
---------- Post added at 07:19 AM ---------- Previous post was at 07:18 AM ----------
I am sorry to reply to an old post but I am unsure if other people are still having issues with this like I was. Here is some info from https://twrp.me/devices/oneplustwo.html :
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
Related
Update : It is solved now.
Here's what exactly happened to my Oneplus2 -
I had successfully unlocked the Bootloader and flashed TWRP using Fastboot.
Using TWRP, I flashed SU Binary and got root privileges.
STUPID Step : I enabled ENCRYPTION on the device.
Which made it impossible for TWRP to mount the encrypted drives. But even after that I was able to boot into Recovery.
Everything was fine (obviously, I wasn't able to flash through TWRP though, due to encryption)
After some days, when I tried to boot into TWRP, the device got powered off promptly just after the boot animation flashed on screen (which hardly lasted for a second)
I don't know what happened. I was not able to reboot device into system either. It just flashes the boot screen for a second and then completely goes blank. Same is the case if I try to boot into Recovery (using Power button + Vol button)
[Currently] I am able to power off my device and boot into Fastboot Mode (using Vol Up + Power)
I tried flashing TWRP again but it fails giving the following error.
Command - fastboot flash recovery TWRP.img
target reported max download size of 536870912 bytes
sending 'recovery' (25956 KB)...
OKAY [ 0.859s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.875s
Click to expand...
Click to collapse
So I checked whether the Bootloader is still unlocked? (And unfortunately it is locked, I have no idea how)
Command - fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.078s]
finished. total time: 0.078s
Click to expand...
Click to collapse
I tried to unlock the bootloader again but still the same result.
Command - fastboot oem unlock
(I'm sure that OEM unlocking was checked and even USB debugging was enabled last time I was booted into the system)
...
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
The bootanimation flashed for a second and then again nothing happened. I again checked the bootloader status. It is still same as quoted above.
I rattled a lot around many forums to get a way to boot into the system.
So what tried was to use this command.
Command - fastboot continue
resuming boot...
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Only a charging screen appears. And on removing USB same thing happens. Device gets powered off and on trying to boot again bootanimation comes up for a second and then blank screen.
I really have no idea what to do? Any help would be appreciated.
Thanks!
Follow this
https://www.youtube.com/watch?v=R4SVSovw4Jo
Nothing to worry about, i was on MM(beta) when this happen... I try to revert back to LP but the oem is locked.. I cnt even boot my phone... But at least fastboot was ok though.. http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543 this one
Flash Stock Recovery & Flash OxygenOS Zip
muk12 said:
Follow this
https://www.youtube.com/watch?v=R4SVSovw4Jo
Click to expand...
Click to collapse
This Video is awesome saved my life...thanks a ton......
SOLVED
The Chinese recovery tool did worked in my second attempt.
Just followed the video.
First time it didn't worked but second time it did.
In my first attempt it failed with some error. I uninstalled the device from the Device Manager. Reconnected it and updated the drivers again. Installed ADB. And then just followed as done in the video and it worked in this attempt.
After the recovery process was complete the device booted normally (And didn't went into Stock Recovery as I was expecting)
I rebooted the device into recovery mode(Stock Recovery)
Then I wiped the data to remove Encryption.
Thanks for the help. Cheers !!!
Hi All,
Due to in ternal memory full, suddenly my home button stopped working and notifications were not appearing. I tried and followed advice written in one of the websites:
"f you didn't enabled developer settings and usb debug prior to the defect, you can create an icon to call this Activity using Nova Launcher.
After installing it and launching, long press home screen, select widgets, swipe right to find Activity icon, place on empty space in your home, search for setup wizard (it changes accordingly to your native language), select .SetupWizardTestActivity and voilá."
But, now my phone is stuck in SetupWizardTestActivity loop. I desperately need to recover my photos and other data on internal memory.
Please suggest.
Additional Info:
Using Moto X play (updated to Marshmallow)
Bootloader is unlocked
Can't you just boot into safe mode and try if that works.
Boot into Safe Mode
With the phone on, press and hold the power key until the on-screen “Power off” option shows up.
Long press on the on-screen button, and select “Boot into Safe Mode.”
or if you have an unlocked bootloader you can flash TWRP and use the build in file manager to transfer the files to your sd.
anujagraj said:
Hi All,
Due to in ternal memory full, suddenly my home button stopped working and notifications were not appearing. I tried and followed advice written in one of the websites:
"f you didn't enabled developer settings and usb debug prior to the defect, you can create an icon to call this Activity using Nova Launcher.
After installing it and launching, long press home screen, select widgets, swipe right to find Activity icon, place on empty space in your home, search for setup wizard (it changes accordingly to your native language), select .SetupWizardTestActivity and voilá."
But, now my phone is stuck in SetupWizardTestActivity loop. I desperately need to recover my photos and other data on internal memory.
Please suggest.
Additional Info:
Using Moto X play (updated to Marshmallow)
Bootloader is unlocked
Click to expand...
Click to collapse
If bootloader is unlocked then recovering data is easy, I guess you have TWRP recovery if not flash twrp then pop in a sd-card boot into recovery and copy everything to the card. Done.
Edit: the above comment says the same thing, I had not noticed that .
While flashing TWRP recovery, I am getting the following message in CMD:
target reported max download size of 268435456 bytes
sending 'recovery' (8362 KB)...
OKAY [ 0.276s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
In phone's bootloader logs, I can see: "Mismatched partition size (recovery).
Please help!
Lennyz1988 said:
Can't you just boot into safe mode and try if that works.
Boot into Safe Mode
With the phone on, press and hold the power key until the on-screen “Power off” option shows up.
Long press on the on-screen button, and select “Boot into Safe Mode.”
or if you have an unlocked bootloader you can flash TWRP and use the build in file manager to transfer the files to your sd.
Click to expand...
Click to collapse
Hi,
Safe mode is not helping. Same loop is continuing.
Also, I am not able to flash TWRP custom recovery. I am getting the following message:
(bootloader) Preflash validation failed
FAILED (remote failure)
In phone bootloader logs I can see: "Mismatched partition size (recovery).
bablu048 said:
If bootloader is unlocked then recovering data is easy, I guess you have TWRP recovery if not flash twrp then pop in a sd-card boot into recovery and copy everything to the card. Done.
Edit: the above comment says the same thing, I had not noticed that .
Click to expand...
Click to collapse
While flashing TWRP recovery, I am getting the following message in CMD:
target reported max download size of 268435456 bytes
sending 'recovery' (8362 KB)...
OKAY [ 0.276s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
In phone bootloader logs I can see: "Mismatched partition size (recovery).
Please help!
anujagraj said:
While flashing TWRP recovery, I am getting the following message in CMD:
target reported max download size of 268435456 bytes
sending 'recovery' (8362 KB)...
OKAY [ 0.276s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
In phone bootloader logs I can see: "Mismatched partition size (recovery).
Please help!
Click to expand...
Click to collapse
is the bootloader unlocked, did you input the code to unlock??just checking
Yes. Bootlader is unlocked with input code to unlock.
I guess adb is not authorised then. when the phone is in setup wizard connect it to pc and type 'adb devices' there will be a pop-up asking you to authorise adb. select it. the try to flash recovery again .
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
anujagraj said:
Yes. Bootlader is unlocked with input code to unlock.
Click to expand...
Click to collapse
or simply run
fastboot boot <enter twrp name>
bablu048 said:
I guess adb is not authorised then. when the phone is in setup wizard connect it to pc and type 'adb devices' there will be a pop-up asking you to authorise adb. select it. the try to flash recovery again .
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
or simply run
fastboot boot <enter twrp name>
Click to expand...
Click to collapse
"adb devices" is not working during Setup wizard.
Do you mean to say that I run fastboot boot <enter twrp name> during setup wizard?
Also, alternatively, will flashing a rom without clearing user data help in any way?
Thanks a lot for the help..
bablu048 said:
I guess adb is not authorised then. when the phone is in setup wizard connect it to pc and type 'adb devices' there will be a pop-up asking you to authorise adb. select it. the try to flash recovery again .
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
or simply run
fastboot boot <enter twrp name>
Click to expand...
Click to collapse
adb and fastboot are different things and are unrelated to each other. He doesn't need adb to flash the recovery.
anujagraj said:
"adb devices" is not working during Setup wizard.
Do you mean to say that I run fastboot boot <enter twrp name> during setup wizard?
Also, alternatively, will flashing a rom without clearing user data help in any way?
Thanks a lot for the help..
Click to expand...
Click to collapse
What happens when you just clear /cache in the stock recovery?
What recovery are you trying to flash?
Lennyz1988 said:
adb and fastboot are different things and are unrelated to each other. He doesn't need adb to flash the recovery.
What happens when you just clear /cache in the stock recovery?
What recovery are you trying to flash?
Click to expand...
Click to collapse
Clear /cache in the stock recovery didn't help. Also, I am trying to flash TWRP recovery 2.8.7.
no, boot phone in fastboot mode ...then run the command
fastboot boot <recovery>
try latest TWRP
bablu048 said:
no, boot phone in fastboot mode ...then run the command
fastboot boot <recovery>
try latest TWRP
Click to expand...
Click to collapse
Hi,
I tried re-unlocking the phone using code and got following message:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s
Any workaround?
unlocking bootloader will wipe the data in your phone.
I thought you had unlocked.
what is the problem when you try to setup the phone ? or skip the setup
---------- Post added at 05:15 PM ---------- Previous post was at 05:12 PM ----------
anujagraj said:
Hi,
I tried re-unlocking the phone using code and got following message:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s
Any workaround?
Click to expand...
Click to collapse
best option now is flashing the firmware manually without wiping data.
Read this, also read a few comments after it.http://forum.xda-developers.com/showpost.php?p=65715334&postcount=43
bablu048 said:
unlocking bootloader will wipe the data in your phone.
I thought you had unlocked.
what is the problem when you try to setup the phone ? or skip the setup
---------- Post added at 05:15 PM ---------- Previous post was at 05:12 PM ----------
best option now is flashing the firmware manually without wiping data.
Read this, also read a few comments after it.http://forum.xda-developers.com/showpost.php?p=65715334&postcount=43
Click to expand...
Click to collapse
Hi,
Where can I find firmware to flash on my phone?
Also RSDLite is not able to detect phone. Can I enter commands from fastboot?
Thanks!
anujagraj said:
Hi,
Where can I find firmware to flash on my phone?
Also RSDLite is not able to detect phone. Can I enter commands from fastboot?
Thanks!
Click to expand...
Click to collapse
RSD lite needs windows 7.
Yes you have to flash manually then using fastboot commands.
firmware
Just don't use the command to erase user data. Skip it. Open the zip there will be flashfile. xml/servicefile.xml open it , you will find the list of commands to run. Or the commands can be found here.
bablu048 said:
RSD lite needs windows 7.
Yes you have to flash manually then using fastboot commands.
firmware
Just don't use the command to erase user data. Skip it. Open the zip there will be flashfile. xml/servicefile.xml open it , you will find the list of commands to run. Or the commands can be found here.
Click to expand...
Click to collapse
Just to confirm, will any firmware will work or I need to download one specific to my phone/higher version?
Also, any risks of bricking the device while flashing?
anujagraj said:
Just to confirm, will any firmware will work or I need to download one specific to my phone/higher version?
Also, any risks of bricking the device while flashing?
Click to expand...
Click to collapse
If you are on 6.0.1 then flash 6.0.1...better flash the appropriate region firmware.
There is a risk of bricking if you are downgrading and flash old gpt.bin and bootloader
As long as you are flashing proper firmware it's safe thoughi haven't done it but as you can see the comments I linked previously others have done it.
bablu048 said:
If you are on 6.0.1 then flash 6.0.1...better flash the appropriate region firmware.
There is a risk of bricking if you are downgrading and flash old gpt.bin and bootloader
As long as you are flashing proper firmware it's safe thoughi haven't done it but as you can see the comments I linked previously others have done it.
Click to expand...
Click to collapse
Hi,
I have an Indian model and got the following error on flashing contents of XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18.1_cid7_subsidy-DEFAULT_CFC.xml using fastboot:
AP Fastboot Flash Mode (Secure)
failed to validate system image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
Please help!
For the last week I have been trying to root and install TWRP on my Huawei p8 Lite ALE21. Sofar every attempt has failed.
Steps taken:
Get Bootloader Code
Unlock bootloader with "fastboot oem unlock"
Flash TWRP with "fastboot flash recovery recovery.img"
Result:
When booting into recovery the default "Huawei eRecovery" opens, not TWRP
No app can detect root
Additional info:
TWRP form here: http://forum.xda-developers.com/p8lite/development/testing-twrp-2-8-7-x-huawei-p8lite-qcom-t3187758
Trying to debug the problem, I entered
Code:
fastboot getvar all
this returned
Code:
getvar:all FAILED (remote: Command not allowed)
Additional I have tried to downgrade to android 5.0 again, but after copying the Firmware to the "dload" folder and holding the Volume-Up and Down and Power buttons, the phone wouldn't do anything but show the huawei logo and turn off.
Any help would be very appreciated!
Thank you in advance,
Oisin
Oisins said:
For the last week I have been trying to root and install TWRP on my Huawei p8 Lite ALE21. Sofar every attempt has failed.
Steps taken:
Get Bootloader Code
Unlock bootloader with "fastboot oem unlock"
Flash TWRP with "fastboot flash recovery recovery.img"
Result:
When booting into recovery the default "Huawei eRecovery" opens, not TWRP
No app can detect root
Additional info:
TWRP form here: http://forum.xda-developers.com/p8lite/development/testing-twrp-2-8-7-x-huawei-p8lite-qcom-t3187758
Trying to debug the problem, I entered
Code:
fastboot getvar all
this returned
Code:
getvar:all FAILED (remote: Command not allowed)
Additional I have tried to downgrade to android 5.0 again, but after copying the Firmware to the "dload" folder and holding the Volume-Up and Down and Power buttons, the phone wouldn't do anything but show the huawei logo and turn off.
Any help would be very appreciated!
Thank you in advance,
Oisin
Click to expand...
Click to collapse
In order to boot in twrp recovery you should first remove your usb cable,once is done,press and hold volume up and power button,once you see huawei logo,release power button but keep press on volume up,about firmware witch build number do you have on your phone,share more info if you want a quick help
"No app can detect root"
TWRP isn't root
"fastboot flash recovery recovery.img"
Any error?
"....(remote: Command not allowed)"
i think you have to unlock bootloader
Thank you for you quick response!
Running "fastboot flash recovery recovery.img" returns
Code:
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.880s]
writing 'recovery'...
OKAY [ 2.084s]
finished. total time: 2.967s
I checked if the bootloader is unlocked with "fastboot oem get-bootinfo"
Code:
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.003s
I also tried booting into recovery without the cable plugged it, but it still just booted into "eRocovery"
More info
Product: ALE-L21
Serial: W3D4C16916992523
Build: ALE-L21C432BB574
just try this:
1) (re) boot normally
2) attach to pc with usb cable
3) reboot into recovery using adb command: adb reboot recovery
ItalianWolf said:
just try this:
1) (re) boot normally
2) attach to pc with usb cable
3) reboot into recovery using adb command: adb reboot recovery
Click to expand...
Click to collapse
The phone reboots, shows the HUAWEI logo and then turn off again.
Sorry, i didn't read the post linked.
You need twrp 3.0.2 for B5xx, i was thinking you had the right one (2.8.7 works on kk and maybe lollipop), so here you are: http://forum.xda-developers.com/p8lite/general/twrp-3-0-0-0-p8-lite-kirin-t3343320
ItalianWolf said:
Sorry, i didn't read the post linked.
You need twrp 3.0.2 for B5xx, i was thinking you had the right one (2.8.7 works on kk and maybe lollipop), so here you are: http://forum.xda-developers.com/p8lite/general/twrp-3-0-0-0-p8-lite-kirin-t3343320
Click to expand...
Click to collapse
It worked! Thank you very very much! I spend sooo much time on this... wow thanks!
Greetings everyone, I just got a new XT1640. I installed on it the ATHENE_NPJS25.93-14-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ROM from here. Went to motorola's site and unlocked the phone. But I still can't flash TWRP.
this is what happens:
Code:
fastboot flash boot twrp-3.0.2-0-athene.img
target reported max download size of 536870912 bytes
sending 'boot' (12496 KB)...
OKAY [ 0.435s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.186s]
finished. total time: 0.621s
I tried versions 3.1.1, 3.1.0 and 3.0.2 , all from the twrp site. Any ideas?
@yohanleafheart
Why do you want to brick your device ?
Check the command that you are entering, "BOOT" ???? That's "RECOVERY"
write command: fastboot flash recovery xyz.img
(Refer any Recovery or flashing thread)
EDIT:
When you used "fastboot flash boot twrp.img"
you got OKAY at last,
That means you flashed Recovery into Boot/kernel !!
If you face any kernel related problem on startup, then you will need to get original Boot.img and flash it...
Haha hey bro be careful while using commands .. u gonna poision your phone
In addition to ____Mdd's reply about TWRP being flashed to your boot (i.e. kernel!) partition, which isn't good...
The 'Image not signed or corrupt' error is normal because TWRP isn't cryptographically signed, so the bootloader reports as so. Normally, if you see [OKAY], the flash has succeeded (though in your case it's succeeded flashing to the wrong partition...) and you'd boot to recovery to ensure TWRP is not overwritten by the stock recovery (after which you can boot as normal).
If you need a stock kernel, you can pull the boot.img from the stock ROM you have and flash that to the boot partition or find the stock kernels here https://forum.xda-developers.com/showpost.php?p=72378739&postcount=262
Hopefully your device is working!
Gaaaaaaaaah didn't realize I was flashing to the wrong partition. Zomfg.
It didn't brick, i reverted to the stock before booting and relock the bootloader. I don't want the stock, I want to flash loa (did this on my s5 normally)
The problem is that even using the right command, it says that it is not signed, and wglhen I reboot in Dev mode it still won't boot on TWRP. It goes back to fastboot.
Any ideas?
I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks
unknown_geek said:
I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks
Click to expand...
Click to collapse
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.
1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A
echo92 said:
1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A
Click to expand...
Click to collapse
Hi @echo92,
Thanks for pointing out what I was doing wrong. I now realize that the TWRP recovery was being overwritten by stock recovery and I didn't know adb commands don't work while still in bootloader mode.
I did boot into recovery mode from the bootloader (using the volume buttons from the phone) and it worked.
And the ID: bad key is also gone and now it shows ID: N/A.
Thanks again for your help!
Regards
____Mdd said:
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.
Click to expand...
Click to collapse
Hi @____Mdd,
I rebooted into recovery right after flashing TWRP and it worked fine. Now, I'm able to boot into TWRP recovery.
Thanks for your response.
Regards.
Im Facing this issue while flashing TWRP
C:\adb>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (12644 KB) OKAY [ 0.422s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
vaibhavhr2010 said:
Im Facing this issue while flashing TWRP
Click to expand...
Click to collapse
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?
echo92 said:
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?
Click to expand...
Click to collapse
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3
vaibhavhr2010 said:
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3
Click to expand...
Click to collapse
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?
echo92 said:
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?
Click to expand...
Click to collapse
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.
vaibhavhr2010 said:
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.
Click to expand...
Click to collapse
That TWRP won't work, if it's for Titan. The codename for Moto G4/plus is athene, only TWRP images specifying athene in their name will work.
https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206 or https://eu.dl.twrp.me/athene/ give these a try instead