Hi, I've got a problem regarding TWRP and the recovery partition.
I have downloaded and flashed TWRP following the guide in the development section, but everytime I boot into recovery I get a black screen and the notification led glows white.
If I use the "fastboot boot" command I can access TWRP, but that's only temporary and won't work for me. I've tried flashing from fastboot in windows and flashing from the temporarily booted TWRP on the phone. If the custom recovery won't work at all, I'd at least like to get back to stock recovery.
Thx for your help!
lspflr said:
Hi, I've got a problem regarding TWRP and the recovery partition.
I have downloaded and flashed TWRP following the guide in the development section, but everytime I boot into recovery I get a black screen and the notification led glows white.
If I use the "fastboot boot" command I can access TWRP, but that's only temporary and won't work for me. I've tried flashing from fastboot in windows and flashing from the temporarily booted TWRP on the phone. If the custom recovery won't work at all, I'd at least like to get back to stock recovery.
Thx for your help!
Click to expand...
Click to collapse
i had this problem did you update to 3.5.3 version? or you are still on 3.5.1
btouareg said:
i had this problem did you update to 3.5.3 version? or you are still on 3.5.1
Click to expand...
Click to collapse
Still on 3.5.1
lspflr said:
Still on 3.5.1
Click to expand...
Click to collapse
that's why you have this problem
download 3.5.3 and flash it manually
try to open twrp via fastboot
then do a clean flash for 3.5.3
then everything will work normally
btouareg said:
that's why you have this problem
download 3.5.3 and flash it manually
try to open twrp via fastboot
then do a clean flash for 3.5.3
then everything will work normally
Click to expand...
Click to collapse
Ok, I ended up dirty flashing 3.5.3 via booted TWRP and then it worked! I'm just wondering what the rom version has to do with the recovery partition, as they - from my understanding - are two separate things and shouldn't interfere with each other.
My problem is solved though so thank you for your help!
lspflr said:
Ok, I ended up dirty flashing 3.5.3 via booted TWRP and then it worked! I'm just wondering what the rom version has to do with the recovery partition, as they - from my understanding - are two separate things and shouldn't interfere with each other.
My problem is solved though so thank you for your help!
Click to expand...
Click to collapse
Cool!! enjoy your new op3t and im glad that i helped you
Related
I was trying to fix my google play "no connection error" but it didn't work so i just reset my phone as a last resort to try and fix this problem. It restarted in recovery mode i thought this was just a procedure and i just hit reboot -> system. it rebooted again into recovery mode i checked if there were any wtuck volume rockers but there aren't any help?
(FYI: one plus 3T: Rooted)
(FYI: link to what i used to try and fix my google play store:https: //forum.xda-developers.com/showthread.php?t=2273994)
What recovery are you running? Stock or TWRP?
bealer said:
What recovery are you running? Stock or TWRP?
Click to expand...
Click to collapse
TWRP
And telling TWRP to boot system just bring you back into TWRP?
Hmm... sounds like you might need to reflash whatever rom you were on.
bealer said:
And telling TWRP to boot system just bring you back into TWRP?
Hmm... sounds like you might need to reflash whatever rom you were on.
Click to expand...
Click to collapse
already did that but still brings me back into TWRP
TrappleV3 said:
already did that but still brings me back into TWRP
Click to expand...
Click to collapse
This happened to me. I installed custom rom then I went into fastboot and installed stock recovery. I would search in this forum for the stock recovery img file. Once installed, I rebooted and it loaded the rom. I had this problem on the latest twrp version. I installed the previous twrp and I am all good now.
Droid-2 said:
This happened to me. I installed custom rom then I went into fastboot and installed stock recovery. I would search in this forum for the stock recovery img file. Once installed, I rebooted and it loaded the rom. I had this problem on the latest twrp version. I installed the previous twrp and I am all good now.
Click to expand...
Click to collapse
you have a link to the file because i can't seem to find it. But thank you anyway for your help.
TrappleV3 said:
you have a link to the file because i can't seem to find it. But thank you anyway for your help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
mximer said:
https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
Click to expand...
Click to collapse
Thank You.
Issue has been resolved. OP is my little cousin who's been messing around a bit too frantically [emoji14]
I restored his device with the unbrick tool by Haris K., all's peachy again. There are still some issues with TWRP for 3T, doesn't run nearly as smooth as on the OPO. It completely failed to restore any working system (both from backup or from reflashing). Sideloading seemingly worked, but rebooted to recovery again, adb push only resulted in errors. Are there any tweaked TWRP releases that can do better?
Cooked with Resurrected bacon!
Hello lovely XDA-members,
this morning a new OTA update/patch came out for my OnePlus 3T, so I downloaded and tryed to install it right away. My phone is rooted on android 7.0 and I have TWRP 3.0.3-0 installed as my recovery. Normally (when I updated to nougat) after downloading a new update the phone reboots itself into TWRP and installs the update by itself, but not this time. I had to seqrch through my phone and had to install thw update manually. After that I rebooted the phone and it started booting the TWRP recovery again, I tried it again and again and again, nothint changed. So I tried to restore my backup with everything functioning, but this wouldnt help either. :/ I read the few existing threads with this problem and heard of a recovery flag that isnt cleared and the bootloader being the problem. One solution that I found was only for an LG phone and I'm afraid that I'll brick my brand new phone I have absolutely no idea what to do now, I would be so happy if someone could help me with this :$
I thank you in advance <3
Encoutered the same problem. Either you reflash the official or twrp recovery (neither did the trick to me) or use this "emergency tool" (which helped me):
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
Btw: TWRP 3.0.3-0 is not working well, switch to 3.0.3-1 beta
Good luck to you
I had the same problem.
How you can ''unbrick it'':
1. Flash a any rom available for the oneplus 3t via twrp
a. after this you will be still in twrp bootloop, to solve this go to step 2
2. Flash back stock recovery via twrp
Now your system will boot again
Optional: Flash back twrp
Just flash stock recovery via adb and you're done. It will fix the problem, you won't lose any data
Isus <3 said:
Just flash stock recovery via adb and you're done. It will fix the problem, you won't lose any data
Click to expand...
Click to collapse
@Isus <3 and @koentdm Do you have a download for the stock recovery, cause the oneplus download-site isnt working and I cant find any other downloads for it
EYT said:
@Isus <3 and @koentdm Do you have a download for the stock recovery, cause the oneplus download-site isnt working and I cant find any other downloads for it
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B0pr-ZA5b-1pNVlxV3ljMUFaUHc/view
Thank you so much, it worked
EYT said:
Thank you so much, it worked
Click to expand...
Click to collapse
No problemos my friendos
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Anova's Origin said:
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Click to expand...
Click to collapse
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
ddaharu said:
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
Click to expand...
Click to collapse
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Anova's Origin said:
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Click to expand...
Click to collapse
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
ddaharu said:
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
Click to expand...
Click to collapse
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Anova's Origin said:
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Click to expand...
Click to collapse
One last question. Is there any twrp version you'll recommend? Or anyone is good?
ddaharu said:
One last question. Is there any twrp version you'll recommend? Or anyone is good?
Click to expand...
Click to collapse
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Anova's Origin said:
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Click to expand...
Click to collapse
MY PHONE IS RUNNING AGAIN! thanks for your help man.
Btw! Seeing that the positions were somewhat corrupted, I actually had to use stock recovery to sideload the stock ROM then flash TWRP and finally on freedom is 2.6.1
Thanks again, mate. :highfive:
ddaharu said:
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Click to expand...
Click to collapse
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
9891ishu said:
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
Click to expand...
Click to collapse
Thanks. I got through.
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.
Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?
rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can
Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.
Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)
Hello,
As the title suggests, I've flashed a custom rom (EvolutionX to be exact), upon booting it up, mediatek Ims stops working, but that appears only on boot so it's not that big of a deal.
However, Upon rebooting into recovery (through system or via vol up+power) i get greeted by the SHRP logo but it powers off and on.
Fastboot mode works just fine, ROM works too, the recovery doesnt want to work though. I had the phone modded for 2 weeks and this is the first time this happened.
Any idea on i can fix it? I've already tried flashing the same recovery via fastboot but to no avail, i get an error saying:
fastboot: error: cannot load 'SHRP_v3.1_stable-Official_CD6-1630047089': Permission denied
That's weird, because my phone has an unlocked bootloader.
Any help would be greatly appreciated!
Friend Maybe you had a small error in the firmware of your device, if I'm not mistaken I think that later the equipment will be in a hardbrick and you will have to wait for the bootloop cycle to pass, which is when the battery runs out and you will have to resort to SP Flash Tool to fix mobile
I hope I have helped you, it is something that I have learned
HaroldTech312 said:
Friend Maybe you had a small error in the firmware of your device, if I'm not mistaken I think that later the equipment will be in a hardbrick and you will have to wait for the bootloop cycle to pass, which is when the battery runs out and you will have to resort to SP Flash Tool to fix mobile
I hope I have helped you, it is something that I have learned
Click to expand...
Click to collapse
i will try flashing stock xiaomi and then install a custom rom again
NewtonPL said:
i will try flashing stock xiaomi and then install a custom rom again
Click to expand...
Click to collapse
try it I can't guarantee you anything but if it comes back and the same thing happens it means that the rom is not compatible with your mobile and you will have to look for another one
If you still have doubts tell me that I can try to help you
the ROM was glitchy and broke the recovery, i flashed miui a11 and flashed everything again, works now
NewtonPL said:
the ROM was glitchy and broke the recovery, i flashed miui a11 and flashed everything again, works now
Click to expand...
Click to collapse
did you flash the .zip using the SHRP recovery or did you use the fastboot method? I just used the Install Magisk feature and now my phone it bootlooping. I can enter the SHRP and fastboot. It just bootloop after the lock icon disappears.
Mineplayerminer said:
did you flash the .zip using the SHRP recovery or did you use the fastboot method? I just used the Install Magisk feature and now my phone it bootlooping. I can enter the SHRP and fastboot. It just bootloop after the lock icon disappears.
Click to expand...
Click to collapse
what zip? this isnt about magisk mate.
NewtonPL said:
what zip? this isnt about magisk mate.
Click to expand...
Click to collapse
I mean the MIUI ROM in zip. But I figured it out, I unbricked mine by installing the MIUI from the SHRP.