[Urgent Help] TWRP keeps rebooting instead of booting in system. - OnePlus 3T Questions & Answers

I am stuck with TWRP... It just keeps rebooting..
Tried methods:
Unbrick tool is of no use to me..
flashed the beta of TWRP... 3.0.3 beta 1... in this I can install a rom successfully but it does not boot the system.. it just boots to TWRP back..
TWRP old version 3.0.2 does not install a system... throws error unknown..
formatted data everything.. but no luck....
tried restoring nandroid backup but it still same thing happens..
Please help urgently....

ok i finally booted up in system...
flashed the stock recovery via toolkit and then again flashed TWRP beta version via toolkit and then installed OOS 4.0 and rebooted back in system.... but the thing is no setting was lost... this means the os was installed successfully but was not booting... looks like twrp issue...
but now I want to go back completely stock.. no root... nothing... until all this TWRP stuff becomes stable.... or is there any alternative to this...
Can someone please guide me on this...

Check the following link
https://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308
and especially check the " dm-verity and forced encryption disabler " part...there's your problem I guess

jackgreyhat said:
Check the following link
https://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308
and especially check the " dm-verity and forced encryption disabler " part...there's your problem I guess
Click to expand...
Click to collapse
Yea may be that was the problem. Every time I did both steps, supersu and dm-verity. This time I didn't and it is fine as of now...
I hope it stays well..
But I am noticing quite a lot of battery drain on nougat.. Tried quite a lot of methods. Some improvement but not much... I am just getting around 3hrs SOT.
Gotta disable some services maybe..
Thanks

samsexy98 said:
ok i finally booted up in system...
flashed the stock recovery via toolkit and then again flashed TWRP beta version via toolkit and then installed OOS 4.0 and rebooted back in system.... but the thing is no setting was lost... this means the os was installed successfully but was not booting... looks like twrp issue...
but now I want to go back completely stock.. no root... nothing... until all this TWRP stuff becomes stable.... or is there any alternative to this...
Can someone please guide me on this...
Click to expand...
Click to collapse
Help me! How to boot in system ?

Try the last TWRP release, should work!

I had the same problem and debating going back to stock. I had to flash a full OTA of 4.0.2 through twrp to get it to boot. I also then flashed the dm-verity but still get the error about dm-verity. I am using twrp 3.0.3-1 from the twrp thread.

Related

T stuck in recovery mode,ROM not installing,5% battery.

So I decided to install cyanogenmod WhiteNeo ROM on my xperia T
did the entire process alright.
for recovery, CWM din't work so downloaded app from playsore and got TWRP from there.
the followed the steps from here to reach till step 8 from wiki.cyanogen guide.
stuck at step 8. DOn't get how to perform it because it is confusing.
altenrately sentthe zip package to sd card and tried there but says Error executing updater binary in zip.
I am stuck.
5%battery left.
and I dont know what to do.
can't even get out of Recovery mode.
device is unresponsive when connected to USB and is powered off.
can anyone please sort this out and explain in simple words how to get out of this mess?
p.s: if battery expires,then what happens?
tried installing stock firmware using flashtool
but
07/014/2015 19:14:54 - ERROR - Error in processHeader
all the time
googled all the solutions
none works
help please?
You should be able to flash official CM12 and proceed from there.
First, revert to stock FOTAKernel, then flash my ROM's boot.img via Fastboot mode in Flashtool. Then reboot to TWRP and check versions. Should be 2.8.7.0.
Then flash the ROM zip, gapps and supersu. Done.
WhiteNeo said:
You should be able to flash official CM12 and proceed from there.
First, revert to stock FOTAKernel, then flash my ROM's boot.img via Fastboot mode in Flashtool. Then reboot to TWRP and check versions. Should be 2.8.7.0.
Then flash the ROM zip, gapps and supersu. Done.
Click to expand...
Click to collapse
Thankyou soo much!
could you just elaborate a bit on how to revert to stock FOTA kernel and check TWRP version. confused about that.
btw... how do I use CM recovery instead of TWRP?
also if you have time.
another issue
before you posted this, I already flashed CM12 official, it works fine. But I am having an issue flashing gapps.
have tried
gapps-L-4-21-15.zip
pa_gapps-stock-5.0.1-20150215-signed (1).zip
gapps-lp-20141212-signed (1).zip
For installing
proceeded to install through sdcard and in recovery mode.
installs fine.
as soon as phone starts, google errors(stopped working) start spamming the screen and pressing ok just causes more to come.
reset all to factory version, reinstalled cyanogenmod with gapps, still no good.
can you point out the correct process for it or where am I going wrong.
aber96crombie said:
Thankyou soo much!
could you just elaborate a bit on how to revert to stock FOTA kernel and check TWRP version. confused about that.
btw... how do I use CM recovery instead of TWRP?
also if you have time.
another issue
before you posted this, I already flashed CM12 official, it works fine. But I am having an issue flashing gapps.
have tried
gapps-L-4-21-15.zip
pa_gapps-stock-5.0.1-20150215-signed (1).zip
gapps-lp-20141212-signed (1).zip
For installing
proceeded to install through sdcard and in recovery mode.
installs fine.
as soon as phone starts, google errors(stopped working) start spamming the screen and pressing ok just causes more to come.
reset all to factory version, reinstalled cyanogenmod with gapps, still no good.
can you point out the correct process for it or where am I going wrong.
Click to expand...
Click to collapse
Reverting to stock FOTA and getting official CM recovery (which won't flash anything but official CM builds and gapps) can be done with flashtool and a suitable ftf or using a Terminal command that you will find on the last pages of my CM12.1 thread for Xperia T.
TWRP version should be visible in settings or what one would call a "status bar".
And the force-closing gapps are just the result of a broken or outdated recovery. I've already been reported the same issue after creating a FOTAKernel TWRP for a friend.
You should be able to flash official CM12 gapps from Cyanogen Recovery.. Just google those.

Failed update :/

Right guys, I was on the Android Nougat nbd90z (flashable & image, no encryption, no dm verification) ROM and an update icon notification did pop up. In the heat of the moment I tried to update and now whatever I do phone constantly reboots to TWRP. I even tried to restore to old backup and nothing helps, phone boots into recovery...
HELP
xywojtek said:
Right guys, I was on the Android Nougat nbd90z (flashable & image, no encryption, no dm verification) ROM and an update icon notification did pop up. In the heat of the moment I tried to update and now whatever I do phone constantly reboots to TWRP. I even tried to restore to old backup and nothing helps, phone boots into recovery...
HELP
Click to expand...
Click to collapse
To update via OTA, you need to be completely on stock.
Go to TWRP and wipe system,cache,dalvik cache partition and flash rom again. Take nandroid backup first.
If you're in TWRP you can easily sideload the OTA in TWRP's Advanced/Sideload - the OTA & instructions are here:
https://developers.google.com/android/nexus/ota#shamu
There isn't an OTA posted just the version you're on
Sent from my Nexus 6
Except that it's not working...?
ok, it's sorted after going into bootloader and a few random actions in TWRP. I still can not understand how nandroid restore did not work?

Stuck in recovery after 4.0.1 OTA

Hi,
I was running Oxygen 4.0.0 and a beta build of TWRP 3.0.3 which works with new encryption. I used the android update mechanics to get the 4.0.1 OTA. System rebooted to recovery, recovery threw an error (zip file corrputed) and since then I am not able to boot the system. Whatever I do I land in TWRP recovery.
Things I did so far:
- Tried installing the full 4.0.1 zip. Install worked without errors, device still boots to recovery.
- Tried to get stock recovery, since another post (https://forum.xda-developers.com/oneplus-3t/help/stuck-recovery-mode-t3532524) indicates stock recovery might fix the problem
--> stock recovery is not obtainable anymore. Seems deleted from all the download links I could find. Example is here: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
- Wipe cache and dalvik cache in the hopes, the instruction to boot to recovery is there somewhere.
I did not do the unbrick tool, since I run linux and didnt want to fiddle with windows yet.
I did make a nandroid backup, so once my system boots again I should be fine.
Any Idea where to either get a mirror of stock recovery or how to fix this problem otherwise?
I had this same problem, and I solved downloading the unbrick tool and extracting the recovery from there. Here is the file
https://drive.google.com/file/d/0BwaafKaXbak3d1RFblFOWVd5eGs/view?usp=sharing
Also locking the bootloader worked for me. Booted into system then unlocked again.
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
mad-murdock said:
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
Click to expand...
Click to collapse
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
mariospizza said:
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
Click to expand...
Click to collapse
Yeah, worked totally normal as it should.
My educated guess about this whole dilemma is, the system sets a flag to boot to recovery which TWRP doesn't clear and only stock recovery clears. Usually those flags should be in cache partition, but in this case isn't.
Tldr: don't use build in update mechanisms if you modified Rom and recovery.

LG L90 D415 Constant Recovery

So I was in the middle of using Lineage OS 14.1 when it notified that there was a May 20th update. I allowed it to update, when for some reason it just took me straight to Recovery.
When I tried to reboot back to the system, for some reason it continued to boot straight to recovery.
I tried wiping everything and reinstalling Lineage, but the same thing happened. Same with AICP.
I figured it was an issue with the recovery, so I flashed the latest img from recovery (since I can't do it from fastboot) yet the problem continues to persist..
Can anybody help? I can't do anything with fastboot because it always fails, I can't flash anything, I'm just stuck on TWRP no matter what I do. I even checked the system and everything and despite TWRP saying I "successfully installed rom" or whatever, nothing gets installed into the system or anything, it just stays empty. How do I fix this?
I read somewhere that it may be because it's trying to update something, and since TWRP is installed instead of the actual LG recovery, it can't install it or whatever. I was previously on a stock rom before I installed Lineage. Could that be it? I figured I can fix it using THIS method, but I'm not sure. The link to the KZD is dead and the only download available for D415 is "old" so I don't want to risk bricking my device.
Help is appreciated ahead of time!
I also just realized that I can't really do anything about flashing the stock rom manually because the download mode is registered as fastboot and it doesn't seem to properly register in the Device Manager at all...
I've also just attempted to factory reset the device, but the only thing that does is also boot into TWRP..
Fivavoa said:
I've also just attempted to factory reset the device, but the only thing that does is also boot into TWRP..
Click to expand...
Click to collapse
In twrp there is a terminal so you might be able to get access to fastboot by removing download mode.
Look at the thread below.
https://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
Hi :3
Fivavoa said:
So I was in the middle of using Lineage OS 14.1 when it notified that there was a May 20th update. I allowed it to update, when for some reason it just took me straight to Recovery.
When I tried to reboot back to the system, for some reason it continued to boot straight to recovery.
I tried wiping everything and reinstalling Lineage, but the same thing happened. Same with AICP.
I figured it was an issue with the recovery, so I flashed the latest img from recovery (since I can't do it from fastboot) yet the problem continues to persist..
Can anybody help? I can't do anything with fastboot because it always fails, I can't flash anything, I'm just stuck on TWRP no matter what I do. I even checked the system and everything and despite TWRP saying I "successfully installed rom" or whatever, nothing gets installed into the system or anything, it just stays empty. How do I fix this?
I read somewhere that it may be because it's trying to update something, and since TWRP is installed instead of the actual LG recovery, it can't install it or whatever. I was previously on a stock rom before I installed Lineage. Could that be it? I figured I can fix it using THIS method, but I'm not sure. The link to the KZD is dead and the only download available for D415 is "old" so I don't want to risk bricking my device.
Help is appreciated ahead of time!
Click to expand...
Click to collapse
Hello, look at this page, this would solve the problem:
https://www.androidsis.com/solucionar-problema-bootloop-recovery-actualizacion-ota-linageos/

stuck on mi logo but can use twrp

after losing my mind because all the methods to install twrp and root my device, i decided to start from here: https://twrp.me/xiaomi/xiaomiredmi4x.html
and use the Fastboot Install Method, i followed the tutorial, boot my phone, have the "password issue" > wipe data > and reboot again to a bootloop nightmare.
now its a bit tricky, but i can enter into twrp, if i put new rom on my SD card and flash it with twrp, will it solve the problem ? any suggestions ?
my phone BL is unlocked but its not rooted yet, any restart attempt via twrp, ends with endless mi logo
thank you.
clean flash new rom from twrp, issue will be solved.
i have try to flash new rom (miui_HM4XGlobal_V8.5.2.0.MAMMIED_973da51a2e_6.0), the process went well but my device is still in bootloop. is there any recommended rom for that situation ?
psoneseven said:
clean flash new rom from twrp, issue will be solved.
Click to expand...
Click to collapse
inCider said:
i have try to flash new rom (miui_HM4XGlobal_V8.5.2.0.MAMMIED_973da51a2e_6.0), the process went well but my device is still in bootloop. is there any recommended rom for that situation ?
Click to expand...
Click to collapse
new rom bootup takes 7- 15+ mins, give it time, or try to flash any custom rom.
Flash stock ROM via mi flash then it boots up,it takes little longer time to boot.
All the best....
An update...
As a professional noob, i have installed twrp and then reboot without rooting, so the device went into loop, rooting the device solved the problem, now i am happy.
Thank you and sorry for the hassle.
inCider said:
An update...
As a professional noob, i have installed twrp and then reboot without rooting, so the device went into loop, rooting the device solved the problem, now i am happy.
Thank you and sorry for the hassle.
Click to expand...
Click to collapse
Or you needed just simple wipe dalvik/cache
tried that of course and it didn't help .
Jakuza001 said:
Or you needed just simple wipe dalvik/cache
Click to expand...
Click to collapse
inCider said:
An update...
As a professional noob, i have installed twrp and then reboot without rooting, so the device went into loop, rooting the device solved the problem, now i am happy.
Thank you and sorry for the hassle.
Click to expand...
Click to collapse
The weird thing is how could you achieve rooting the device if when in a bootloop because TWRP + reboot leads an zero SD storage and you cant mount anything... I mean, how could you flash the zip from nowhere? and solve the storage thing btw (its encrypted)
inCider said:
after losing my mind because all the methods to install twrp and root my device, i decided to start from here: https://twrp.me/xiaomi/xiaomiredmi4x.html
and use the Fastboot Install Method, i followed the tutorial, boot my phone, have the "password issue" > wipe data > and reboot again to a bootloop nightmare.
now its a bit tricky, but i can enter into twrp, if i put new rom on my SD card and flash it with twrp, will it solve the problem ? any suggestions ?
my phone BL is unlocked but its not rooted yet, any restart attempt via twrp, ends with endless mi logo
thank you.
Click to expand...
Click to collapse
Here are the steps I followed:
Go to fastboot (volume down + power)
Go to twrp by running `fastboot boot twrp-3.2.1-0-santoni.img`. i.e. Flashing and getting into recovery is a tricky thing.
Install miui if it is not installed, by downloading miui rom from their site.
Install lazy flasher to disable dm-verity. - https://forum.xda-developers.com/xi...very-recovery-redmi-4x-redmi-4-india-t3613560
Restart the phone. You should see 3 moving dots in the bottom area of the screen. It took around 7 mins to boot.

Categories

Resources