Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding
Related
EDIT: Fixed! Big thanks to @S0wL , @bkores , @tamahouse02 and @tron1 for the help. I made a guide to help other people with the same problem:
Guide to get TWRP again HERE
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Try the menu on the boot screen.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Sounds like the issue is with the ROM like it is somehow blocking you from accessing bootloader mode. It's definitely not my toolkit.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Choose an username... said:
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Click to expand...
Click to collapse
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
tamahouse02 said:
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
Click to expand...
Click to collapse
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Choose an username... said:
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Click to expand...
Click to collapse
Not same my axon7tool. I use this https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
DrakenFX said:
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
Click to expand...
Click to collapse
I was thinking about that, but does mifavor let you roll back from an SD update? I'll try later, but i doubt it.
Besides from that is there any way to flash stuff from the stock recovery? It tells me that ZIPs have to be signed only
tamahouse02 said:
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
Click to expand...
Click to collapse
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
dnlilas said:
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
Click to expand...
Click to collapse
Official 3.0.4.1
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"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."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
dnlilas said:
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"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."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
Click to expand...
Click to collapse
I use 3.0.4.1 because I flash plenty things before without any issue, so I keep using it.
After write recovery by axon7tool, it's reboot automatically and override the recovery, that why I have to unplug to stop the reboot, and also flash all I can - fortunaeally it also stop recovery be overrided
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
I've been in the same situation like you @Choose an username... Updated to nougat on G model and I had not bootloader. This is what I did :
1. Downloaded the tool from here https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
2. Installed the driver using the install driver option that you can choose once you connect you phone to your computer
3. Use the tool to perform the unlock bootloader command again even though you have unlocked it before
4. Use the tool to install twrp, it will boot the phone in twrp
5. Flash Supersu before you boot the system first time after flashing twrp
5. Install whatever version of android want after
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Choose an username... said:
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Click to expand...
Click to collapse
Use Zadig then and let me know if it worked
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Choose an username... said:
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
Click to expand...
Click to collapse
I try your version once, but it seems not work for me, so I keep using the old one.
---------- Post added at 03:42 AM ---------- Previous post was at 03:39 AM ----------
Choose an username... said:
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Click to expand...
Click to collapse
I thought you had already unlocked bootloader? Why have you done it twice?
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
[email protected] said:
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
Click to expand...
Click to collapse
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
madbat99 said:
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
Click to expand...
Click to collapse
Thanks for your reply and thinking with me, but like I wrote, all there is left is the option to use ADB. Pressing volume up and power no longer gets me into a choice menu, only a black screen with small white letters telling me to attach a cable.
No tapping whatsoever will change that. Volume up gets the orange state message again. So....
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
KevMetal said:
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
Click to expand...
Click to collapse
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
[email protected] said:
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
Click to expand...
Click to collapse
Don't forget to join us on telegram
We have a lot going on and if we chat via one central chat development , bug fixing and general help happens fast .
https://t.me/joinchat/G3XDFEO7AR4fGdyBRfwVOw
http://telegra.ph/woods-development-01-07
twrp for 1762 ?
I can't seem to find TWRP-3.2.1.-0_woods_UNOFFICIAL.img annywhere on the internet
I found this but i don't realy trust that site.
https://romprovider.com/2017/12/twrp-3-2-0-moto-e4-xt1762-woods/
I have a Axon 7 A2017U, bootloader unlocked. My recovery is corrupted after attempting to flash a older version of TWRP in recovery. I can no longer reboot into TWRP via recovery, it hangs at the ZTE powered by screen. I can't boot into the o/s, it too was corrupted while attempting to restore to stock using the DrakenFX's guide.
Booting into fastboot is a no go either, it just hangs at bootloader screen.
Any suggestions on where to go from here or how to fix the corrupted recovery?
You need to go into EDL mode and use MiFlash and flash a back to stock package. You can find a package here: https://androidfilehost.com/?w=files&flid=160532
Hello maybe i have same problem here. I have A2017G and maybe i have only woked unlocked bootloader. I dont think my EDL is working becouse i cant connect with ADB. Dont have any acces to recovery... i messed up step by step remember.
1. downloaded toolkit and woked fine - 2 installed drivers and working fine with EDL. 3 unlocked with no problems , 4 flashed TWRP with no problems and then i wanted to install lineage os. Downloaded last version lineage , and google apps and one file "A2017G_N_Modem.zip" and put all 3 files on my SD card. I wipe everything and then first installed modem file OK, but on second try with Lineage OS i have any errors and i just cant continue. After this i wanted to go back to original OS and i just locked my bootloader with axon toolkit and after restart i have acces only to Unlocked Bootloader. tryed everithing with axon7toolkit but nothing working. If i try to EDL mode when press volumeUP+volumeDOWN+power my phone have black screen and i thing is powered OFF.
OMFG i just typed "fastboot oem unlock" 5-6 time when i started phone to my bootloaders and now it unlocked and have acces to my TWRP.
Teet1 said:
You need to go into EDL mode and use MiFlash and flash a back to stock package. You can find a package here: https://androidfilehost.com/?w=files&flid=160532
Click to expand...
Click to collapse
Thanks, I flashed it with A2017U_B19-NOUGAT_FULL_EDL and was able to flashed twrp recovery. I was hoping the o/s would be fixed too but I get this error message as soon as o/s load "settings keeps stopping, close app". It appears it's a bad or incorrect stock file. I had to format data in TWRP recovery as the drive was encrypted. So now i'm back at square one.
Bad o/s but working recovery, so I attempted to flash these files to get back to stock but was unsuccessful. It would flash halfway and then just restarts and hung at the bootloader unlock screen.
A2017UV1.0.0B29_RollBackModded.zip
A2017UV1.1.0B32_bootstack_by_DrakenFX.zip
A2017UV1.1.0B32_StockSystem_by_DrakenFX.zip
Am I on the right track? Or should I be flashing with a different os variant?
freeb0rn said:
Hello maybe i have same problem here. I have A2017G and maybe i have only woked unlocked bootloader. I dont think my EDL is working becouse i cant connect with ADB. Dont have any acces to recovery... i messed up step by step remember.
1. downloaded toolkit and woked fine - 2 installed drivers and working fine with EDL. 3 unlocked with no problems , 4 flashed TWRP with no problems and then i wanted to install lineage os. Downloaded last version lineage , and google apps and one file "A2017G_N_Modem.zip" and put all 3 files on my SD card. I wipe everything and then first installed modem file OK, but on second try with Lineage OS i have any errors and i just cant continue. After this i wanted to go back to original OS and i just locked my bootloader with axon toolkit and after restart i have acces only to Unlocked Bootloader. tryed everithing with axon7toolkit but nothing working. If i try to EDL mode when press volumeUP+volumeDOWN+power my phone have black screen and i thing is powered OFF.
OMFG i just typed "fastboot oem unlock" 5-6 time when i started phone to my bootloaders and now it unlocked and have acces to my TWRP.
Click to expand...
Click to collapse
So you didn't read all of the hurdles and warnings about locking the bootloader with non-stock firmware?
Plus you also didn't find out about the Universal Bootloader? Did you even read the installation steps???
You had an error 7, which is that you forgot to install the Universal Bootloader. Do so this time.
EDL has nothing to do with ADB. You can access it with the phone completely off... (volume up and down, and insert usb)
Hello,
I have lenovo k4 note 32GB ROM, 2GB RAM with stock 6.0 MM. I've unlocked the bootloader with the command ''fastboot flashing unlock'', confirmed it by pressing volume down and returned to fastboot, then successfully flashed twrp from here https://forum.xda-developers.com/k4-note/development/recovery-twrp-3-0-2-0-touch-recovery-t3530374 , i used the latest version 3.2.1. Now the phone remains in bootloop. After pressing vol- with pwr it enters meta mode for a few seconds but then returns to bootloop again. Attempts to anything lead to bootloop. My computer does not recognise it. Is there anything I can do to revive it? Maybe SP flashtool? I have not tried that yet. Help me please, I would be very thankful for any help.
Thank you
bfbl said:
Hello,
I have lenovo k4 note 32GB ROM, 2GB RAM with stock 6.0 MM. I've unlocked the bootloader with the command ''fastboot flashing unlock'', confirmed it by pressing volume down and returned to fastboot, then successfully flashed twrp from here https://forum.xda-developers.com/k4-note/development/recovery-twrp-3-0-2-0-touch-recovery-t3530374 , i used the latest version 3.2.1. Now the phone remains in bootloop. After pressing vol- with pwr it enters meta mode for a few seconds but then returns to bootloop again. Attempts to anything lead to bootloop. My computer does not recognise it. Is there anything I can do to revive it? Maybe SP flashtool? I have not tried that yet. Help me please, I would be very thankful for any help.
Thank you
Click to expand...
Click to collapse
1. Flash stock version (This will lock you bootloader again).
2. Unlock bootloader and let it reboot (donot flash recovery now)
3. It will wipe the device and boots up.
4. After the boot is successful, go back to fastboot and flash recovery.
senthilvigneshkumar said:
1. Flash stock version (This will lock you bootloader again).
2. Unlock bootloader and let it reboot (donot flash recovery now)
3. It will wipe the device and boots up.
4. After the boot is successful, go back to fastboot and flash recovery.
Click to expand...
Click to collapse
I appreciate your reply, but could you please elaborate on the first step? How am I supposed to flash stock recovery when I cannot enter fastboot? The phone is in bootloop no matter what I try. I can't seem to find a way to communicate with the phone from computer.
bfbl said:
I appreciate your reply, but could you please elaborate on the first step? How am I supposed to flash stock recovery when I cannot enter fastboot? The phone is in bootloop no matter what I try. I can't seem to find a way to communicate with the phone from computer.
Click to expand...
Click to collapse
Flash full stock rom, not just recovery using flashtool. You can't flash recovery alone at this point.
For flashtool, you need to power off the mobile completely.
senthilvigneshkumar said:
Flash full stock rom, not just recovery using flashtool. You can't flash recovery alone at this point.
For flashtool, you need to power off the mobile completely.
Click to expand...
Click to collapse
Thank you soooo much, you helped me a lot. The phone is now running!
Btw, before I restored it, I got into TWRP once, I think i pressed some of the nav buttons to get there. But in mount partitions system was missing and data partition was showing 0B, so something was definitely wrong.
Gonna try flashing it again, this time I'll reboot after unlocking bootloader and only then flash. I hope this time I'll succeed
bfbl said:
Thank you soooo much, you helped me a lot. The phone is now running!
Btw, before I restored it, I got into TWRP once, I think i pressed some of the nav buttons to get there. But in mount partitions system was missing and data partition was showing 0B, so something was definitely wrong.
Gonna try flashing it again, this time I'll reboot after unlocking bootloader and only then flash. I hope this time I'll succeed
Click to expand...
Click to collapse
Good, might be problem with twrp. Flash the correct version of twrp provided for k4 note(2/3gb/
senthilvigneshkumar said:
Good, might be problem with twrp. Flash the correct version of twrp provided for k4 note(2/3gb/
Click to expand...
Click to collapse
It works now, successfully rooted!
I know it's OT, but could you recommend me a reliable custom AOSP ROM? I don't have time to spend trying to find one. You seem to have experience with the phone
thanks!
bfbl said:
It works now, successfully rooted!
I know it's OT, but could you recommend me a reliable custom AOSP ROM? I don't have time to spend trying to find one. You seem to have experience with the phone
thanks!
Click to expand...
Click to collapse
Try resurrection remix. More stable one as far as i know. Follow the install steps exactly as said in OP
Deleted
I stupidly tried using franco's app to flash cleanKernel on my rooted phone on 9.0.11, it failed of course and now can't boot my phone. I'm able to fastboot boot twrp.img but I'm not sure what is needed next. I've downloaded the full 9.0.11 ota file thinking something in it (or all of it) needs to be flashed from twrp. Afraid to do anything at this point for fear of losing data. Any tips are appreciated.
I've downloaded mauronofrio's rom-stock-fastboot utility but see he says it will clear data. I'm assuming all the .bat files will do this. Any way to avoid clearing internal storage?
soundneedle said:
From bootloader screen, using fastboot boot twrp.zip results in OP going to "Fastboot Mode" screen...and staying there. The zip is pushed to the phone but won't boot into TWRP. This started after I stupidly tried using franco's app to flash cleanKernel on my rooted phone. It failed of course and now can't boot my phone. My phone recently updated itself to 9.0.11, fyi.
Any ideas on how to fix this boot issue? Is it just a matter of flashing something from the full ota 9.0.11 file---some img file or something?
Click to expand...
Click to collapse
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
I was able to recover...thank god. Just used mauronofrio's flash utility. Removed the "-w" flag from the flash-all.bat file and all is good.
Stuck on Fastboot Mode screen once I run fastboot boot twrp.img
bp328i said:
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
Click to expand...
Click to collapse
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Is the twrp.img even being flashed
SimmoMaz said:
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Click to expand...
Click to collapse
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
SimmoMaz said:
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
Click to expand...
Click to collapse
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
TWRP isn't there
lilbrat said:
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
Click to expand...
Click to collapse
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
SimmoMaz said:
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
Click to expand...
Click to collapse
Ok.. are you using the latest TWRP? If you want in the guide section you can you the msmdow like ad tools to reset you phone to stock, and retry again..
THIS. I have the exact same issue. In short, I have the T-mobile version, and was able to unlock successfully. I am using twrp-3.2.3-0, and I have the img and zip in the same folder, same way Techibee does on Youtube. I then type "fastboot boot twrp-3.2.3-0-fajita.img", I get the "OKAY... OKAY... Booting... Finished" response in console. Then, the Fastboot screen appears and never leaves. I have done this 3 times now. I kept tweaking the process, but I'm nervous to keep debugging.
Stuck (
Hello guys,
I wanted to overclock my 6t global. so i had unlocked the bootloader then flashed the twrp. In twrp i firstly reset the os to factory setting and then i flash magisk and smurf kernel. but when i reboot after this my phone is stuck on the phone unlocked message.
ive tried flashing magisk only and then boot, it works. but when i flash smurf kernel i get stuck . why this happening plz help (