As the title says, I unlocked my bootloader and rebooted and my XT1687 RETUS worked fine. Then I rebooted to TWRP using the mfastboot boot string to boot the 3.1.1. version found in this forum. This is how I've done my G4, G4 Plus, G4 Play, G LTE, E 2015, etc. Anyway, the time was off and I wanted to understand why so I rebooted without backing up or changing anything, but now I get the bootloader unlocked trust message with the ID: bad key screen and it hangs.
Any idea why this would happen when I didn't flash TWRP or anything else?
Can I flash the POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml stock boot, system, and recovery and recover and then start again? Thanks!
vettejock99 said:
As the title says, I unlocked my bootloader and rebooted and my XT1687 RETUS worked fine. Then I rebooted to TWRP using the mfastboot boot string to boot the 3.1.1. version found in this forum. This is how I've done my G4, G4 Plus, G4 Play, G LTE, E 2015, etc. Anyway, the time was off and I wanted to understand why so I rebooted without backing up or changing anything, but now I get the bootloader unlocked trust message with the ID: bad key screen and it hangs.
Any idea why this would happen when I didn't flash TWRP or anything else?
Can I flash the POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml stock boot, system, and recovery and recover and then start again? Thanks!
Click to expand...
Click to collapse
you need to format with twrp, then you need to flash supersu in twrp and the modded boot img file.
https://forum.xda-developers.com/g5-plus/how-to/how-to-how-to-supersu-moto-g5-plus-t3587684
After that you will be able to boot to system
i booted into twrp after unlocking my bootloader but i couldnt make a back up so i decided to reboot to recovery from twrp and maybe it would fix it but nope now twrp doesnt boot up and i have no back ups to go from or any img files... i need help
Can you get into the bootloader by holding volume down + power button?
If so, can you plug the phone into your laptop and do the following? fastboot boot twrp-3.1.1-0-potter.img
If you can get into twrp that way, then you SHOULD be able to flash a new rom or just the boot image.
vettejock99 said:
As the title says, I unlocked my bootloader and rebooted and my XT1687 RETUS worked fine. Then I rebooted to TWRP using the mfastboot boot string to boot the 3.1.1. version found in this forum. This is how I've done my G4, G4 Plus, G4 Play, G LTE, E 2015, etc. Anyway, the time was off and I wanted to understand why so I rebooted without backing up or changing anything, but now I get the bootloader unlocked trust message with the ID: bad key screen and it hangs.
Any idea why this would happen when I didn't flash TWRP or anything else?
Can I flash the POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml stock boot, system, and recovery and recover and then start again? Thanks!
Click to expand...
Click to collapse
This happened to me too. I'm glad I'm not the only one. I relocked using the POTTER_RETAIL_7.0_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and decided to call it quits with rooting/ROMing.
reCoded said:
This happened to me too. I'm glad I'm not the only one. I relocked using the POTTER_RETAIL_7.0_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and decided to call it quits with rooting/ROMing.
Click to expand...
Click to collapse
It's all because when twrp installs it disables the auto-flash of stock recovery by modifying system files. That's why it hangs when booting, it doesn't pass the system integrity check because system files were modified. That is perfectly normal, all you need to do is flash magisk or some other dm- verity disabler and the system will boot fine
It also happened to me, had a small heart attack when it didn't boot.
So what about just booting TWRP? Does make any difference?
Related
ok so i have a razr m i got on ebay. It looks flawless
i unlocked the boot loader and rooted it.
i went into fast boot and pushed cwm 6.0.4.4. I could only get into the boot loader with the key presses "not adb reboot bootloader"
when I go into rom manager i see that i have the latest version of cwm
but I cant boot into recovery
it just shows the boot loader unlocked screen for a while then boots to the regular red eye and regular system
also could not flash cm12 nioghtly from rom manager.
do I just need to rsd the whole thing and start overt?
i retried flashing recovery with mfastboot and it didn't work any better
adb reboot recovery
just the unlocked bootloader screen for a while and then evenutally went into regular boot
ok getting somewhere
i tried a newer version of mfastboot and put the stock recovery back on.
i can now boot to the stock recovery.
i saw that there were issues with the recovery-clockwork-6.0.4.4-xt907.img
what recovery should I be using i am on 4.4.2 183.46.15
i want to get to cm12 eventually
i have tried a number of recoveries. XT901-XT907-TWRP-2.6.3.0-recovery is one
dcooterfrog said:
ok getting somewhere
i tried a newer version of mfastboot and put the stock recovery back on.
i can now boot to the stock recovery.
i saw that there were issues with the recovery-clockwork-6.0.4.4-xt907.img
what recovery should I be using i am on 4.4.2 183.46.15
i want to get to cm12 eventually
i have tried a number of recoveries. XT901-XT907-TWRP-2.6.3.0-recovery is one
Click to expand...
Click to collapse
ha ha this one
cm-recovery-xt907-1-18-15.img
will this one work as well
twrp-2.8.4.2-xt907
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/
FIXED, Just type this adb command when you are in recovery mode....
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Click to expand...
Click to collapse
Hi guys, i have an issue....
Moto g5 plus XT1680 LATAM
I flashed with Flash Fire (security patch) in my moto g5 plus rooted with SuperSU systemless and BL unlocked, but i reboot phone and it starts on recovery TWRP, then, i tried for 3 times but keeps starting on recovery mode.
After that, i tried to power up phone on booloader and then select START And it works, it's the only way that i can start phone normally, or wait for recovery starts and select reboot in bootloader mode because if i select reboot system ... keeps starting on recovery mode.
So, if i dont use bootloader and Select START, phone into recovery mode.
PLEASE, help me i tried with fastboot cmd [fastboot oem fb_mode_clear] not works, wipe /cache doesn't work too, i dont want to flash stock firmware. Can i fix this with a cmd or flashing stock img like boot.img / bootloader.img or something?
Thanks guys. :good:
BunnyHoo said:
Hi guys, i have an issue....
Moto g5 plus XT1680 LATAM
I flashed with Flash Fire (security patch) in my moto g5 plus rooted with SuperSU systemless and BL unlocked, but i reboot phone and it starts on recovery TWRP, then, i tried for 3 times but keeps starting on recovery mode.
After that, i tried to power up phone on booloader and then select START And it works, it's the only way that i can start phone normally, or wait for recovery starts and select reboot in bootloader mode because if i select reboot system ... keeps starting on recovery mode.
So, if i dont use bootloader and Select START, phone into recovery mode.
PLEASE, help me i tried with fastboot cmd [fastboot oem fb_mode_clear] not works, wipe /cache doesn't work too, i dont want to flash stock firmware. Can i fix this with a cmd or flashing stock img like boot.img / bootloader.img or something?
Thanks guys. :good:
Click to expand...
Click to collapse
I have the same problem when i select factory mode on bootloader then the phone starts only...
Otherwise it boots into twrp recovery
I have the same problem. Only boots into system via bootloader.
Otherwise it boots into twrp recovery.
After successfully booting into system it told me "system update failed".
I guess its because the system update routine is to be flashed via stock recovery and therefore its booting into recovery until it is flashed? Just guessing, but if so could I just flash the update manually?
Thanks in Advance :good:
same here, ps. thanks for the tip of boatloader !!
bubo23 said:
same here, ps. thanks for the tip of boatloader !!
Click to expand...
Click to collapse
np, i still w8 for a solution!, i try some methods but not seems to work
Xt1687 here - same issue. Can I get confirmation that flashing the stock firmware fixes it?
Sorry if I'm wrong you cannot update when bootloader unlock ,have to wait some one make a fash zip so we can fash on twrp
Same here, I have to go to Mount then check System and then Reboot, Bootloader and finally Start. It's very annoying. I tried some ADB commands but nothing seemed to work.
Update: So I got annoyed enough by it to finally flash a different rom, wiped /data /system /cache and installed
Cosmic-OS 3.1 Universe but still can only boot via bootloader...
Any suggestions? Do I have to reformat the whole phone in bootloader via Computer?
Thanks in advance :good:
Finally found a fix, might not work for everyone though. Thanks to @aughtnaut:
https://forum.xda-developers.com/showpost.php?p=74109609&postcount=65
jcags said:
Finally found a fix, might not work for everyone though. Thanks to @aughtnaut:
https://forum.xda-developers.com/showpost.php?p=74109609&postcount=65
Click to expand...
Click to collapse
I'll try bro, thanks.:good:
jcags said:
Finally found a fix, might not work for everyone though. Thanks to @aughtnaut:
https://forum.xda-developers.com/showpost.php?p=74109609&postcount=65
Click to expand...
Click to collapse
IT WORKS!!!!, THANKS A LOT!.
Just TYPE FIRST CODE and see the magic!
It worked, thanks for the link!
Hello i have a probleme twrp in my moto g5 plus i unlock bootloader i install twrp but if i want to make a reboot into twrp didnt work . The one methode for reboot into twrp is reboot bootloader and press star , plz i need a solution for normal reboot
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 (
Currently running into some issues with TWRP. I follow the official guide on TWRP's website;
I reboot into bootloader (adb reboot bootloader)
Flash the twrp.img (fastboot flash recovery twrp.img)
Reboot straight into TWRP (without any issues) – plugging out the cable and holding the combination keys
When I try to boot up after all of these steps I end up with a bootloop, not going into recovery but getting the Sony screen over and over again. Is this a common issue or am I just a total idiot with an obvious mistake?
ImBrakkie said:
Currently running into some issues with TWRP. I follow the official guide on TWRP's website;
I reboot into bootloader (adb reboot bootloader)
Flash the twrp.img (fastboot flash recovery twrp.img)
Reboot straight into TWRP (without any issues) – plugging out the cable and holding the combination keys
When I try to boot up after all of these steps I end up with a bootloop, not going into recovery but getting the Sony screen over and over again. Is this a common issue or am I just a total idiot with an obvious mistake?
Click to expand...
Click to collapse
Which rom/version? Rooted? Bootloader unlocked? What did you do with the phone before flashing twrp?
levone1 said:
Which rom/version? Rooted? Bootloader unlocked? What did you do with the phone before flashing twrp?
Click to expand...
Click to collapse
Sorry for lack of information in the post.
Running Customized UK (8.0.0) downloaded with XperiFirm and flashed with FlashTool. I got no root, bootloader is unlocked. Phone was working fully and running like it should be before installation of TWRP, after installation of TWRP there is no way of me booting to the system.
ImBrakkie said:
Sorry for lack of information in the post.
Running Customized UK (8.0.0) downloaded with XperiFirm and flashed with FlashTool. I got no root, bootloader is unlocked. Phone was working fully and running like it should be before installation of TWRP, after installation of TWRP there is no way of me booting to the system.
Click to expand...
Click to collapse
I know that if you don't modify your boot img, (rootkernel), Sony security will cause boot failure at any sign of modification. I didn't realize that it would happen just by flashing recovery, and not modifying anything, but I guess so... Flash the rom again, then flash modified boot img before you turn it on, (you can use rootkernel to make one, or copy one from root thread in this forum), then flash TWRP...
levone1 said:
I know that if you don't modify your boot img, (rootkernel), Sony security will cause boot failure at any sign of modification. I didn't realize that it would happen just by flashing recovery, and not modifying anything, but I guess so... Flash the rom again, then flash modified boot img before you turn it on, (you can use rootkernel to make one, or copy one from root thread in this forum), then flash TWRP...
Click to expand...
Click to collapse
That makes sense, I will give it a go another day. Thanks