I've got this new OnePlus 3t A3003. I'm happy with the performance battery and everything but there's this one issue that troubles me. I got the device unlocked bootloader and flashed aospa. Everything was nice and smooth then I flashed SuperSU later. The phone got reset and wiped except for the internal storage. I didn't know what to do and I just left it. Then later I came across some audio mods and tried flashing it again the same thing happened. So I tested and came to the conclusion that flashing anything wipes device. Why does this happen?
What versions TWRP and SuperSU? Just a guess, but maybe an older version with some compatibility issue? Try another version TWRP?
Otherwise, what version firmware? I don't know if AOSPA updates firmware (as some ROMs do). Maybe try to update OOS to current version 4.1.6 and start with fresh firmware, and install current version TWRP again, etc.
My phone is encrypted so what happens is I flashed something then the phone boots and asks for the password to unlock first then after entering it resets. I didn't know why I even switched roms rn using resurrection remix 7.1.2 latest version and still same problem.So im pretty sure the problem isn't with the rom. Twrp is latest version afaik and with rr rom magisk comes so I'm on v12 of magisk. I'll try using another version of twrp and oos.
redpoint73 said:
What versions TWRP and SuperSU? Just a guess, but maybe an older version with some compatibility issue? Try another version TWRP?
Otherwise, what version firmware? I don't know if AOSPA updates firmware (as some ROMs do). Maybe try to update OOS to current version 4.1.6 and start with fresh firmware, and install current version TWRP again, etc.
Click to expand...
Click to collapse
Thanks mate, there was something wrong with the twrp version I had. I flashed the latest version of twrp 3.1.1 I think and that seemed to solve the issue.
Related
Here's an attempted TLR of what has happened
Tried installing LineageOS. Got Error 7. Tried a bunch of things to make it work like editing the updater-script and things like that but it didn't work.
Then I simply wanted my phone to work again. Installed Clean Stock ROM + Stock Recovery straight out of OnePlus webpage. Now I have permanent dm-verity error (tried going back to 4.0.2, disabling dm-verity via fastboot commands and restoring 4.0.3) and still appears.
So yeah, basically that.
I messed up like a month ago too, bricked the OP3T and managed to revive it with a chinese program.
Any ideas on why I can never manage to install LineageOS?
EDIT: After the last factory reset, the phone wouldn't find any wifi network. After an hour or so, it found my wifi and got a 92mb update that fixed the dm-verity error
What firmware are you running and what's your Android version? If you're running 7.1.1 on 4.1.0 you should be good to go just by flashing all the latest LOS files
sakumaxp said:
What firmware are you running and what's your Android version? If you're running 7.1.1 on 4.1.0 you should be good to go just by flashing all the latest LOS files
Click to expand...
Click to collapse
I just received the 4.1.0, going to try again tonight. Hope it works
Hello dear community. Today, i just recieved my OP3T and I am super happy. Since I am a manian with new android versions + root + xposed, what i did is charge my new device and then start experimenting.
Firstly, i used this tool (https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729) to unlock bootloader, flash TWRP.
Then I used some VPN to change my location to Canada, and get the Oreo OTA.
Oreo OTA replaced TWRP, so I did some research to find out if its safe to reinstall TWRP 3.1.1, but i stumbled uppon some contradicting opinions both for TWRP and for Root. In the guides I read, some users commented that it might be very dangerous to either reinstall TWRP and/or supersu, so since I am not a guru, and my technical knowledge is kinda limited, I thought I'd create this thread before doing something stupid.
So, is it safe to reinstall TWRP in the latest Oreo OTA? (ONEPLUS A3003_28_171116)? Which version of TWRP do you suggest?
Is it safe to use the latest supersu?
Also, should i do a factory reset after the update?
I know for sure that xposed is not available for Oreo, so I wont be asking anything for it here.
Thanks in advance!
For Oreo, the latest TWRP is not recommended. You need the bluspark TWRP for Oreo. Here is the link. https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Careful, there are two Bluspark TWRP, one for nougat and one for Oreo. Also it is unified for both op3 and op3t
I do not know about SuperSU but the beta version of Magisk works on Oreo. The stable version does not work yet. Here is the link for beta https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
I am using the beta Magisk and BluSpark TWRP atm. It works fine. I did a clean flash using the full Oreo zip file (1.5gb). I think you can find this as a download on the XDA forum since OnePlus has not put it online yet. DO NOT CLEAN FLASH THE PARITAL OTA.
The other problem i have is when i try to flash bluesparks twrp and go to recovery the sceen is blank and only the led glows but i can flash the officaial twrp and flash roms but they come with error 7 and when i flash a oxygen os it gets stuck in updating system image
ak_bagade said:
but i can flash the officaial twrp and flash roms but they come with error 7 and when i flash a oxygen os it gets stuck in updating system image
Click to expand...
Click to collapse
Error 7 often means you are trying to flash an Oreo ROM with an older version TWRP which does not support Oreo.
But we can't tell from the info provided by you. Always give version numbers and other details for TWRP (and blu_spark TWRP) you are having trouble with, as well as the ROMs you are trying.
Also, make sure you are using the right TWRP and ROMs for 3 versus 3T (another reason for Error 7).
redpoint73 said:
Error 7 often means you are trying to flash an Oreo ROM with an older version TWRP which does not support Oreo.
But we can't tell from the info provided by you. Always give version numbers and other details for TWRP (and blu_spark TWRP) you are having trouble with, as well as the ROMs you are trying.
Also, make sure you are using the right TWRP and ROMs for 3 versus 3T (another reason for Error 7).
Click to expand...
Click to collapse
its the latest bluesparks
ak_bagade said:
its the latest bluesparks
Click to expand...
Click to collapse
I said: always give a version number. "latest bluesparks" isn't a version number. I can't count how many times I've seen folks claim they flashed the "latest" recovery. And when prompted for more info, we find out that they aren't even close, sometimes flashing a version TWRP from 2 years ago or older! Not saying this is necessarily your case. But we don't know for certain, if you don't give us precise and accurate info to work with.
You also said you flashed official TWRP. What version number exactly?
You also need to tell us what custom ROMs (and versions) you tried to flash. And what version OOS did you try to flash?
Some friendly advice, try to take more than 5 seconds to type a response to questions we ask you. Provide as much detail as possible, and answer all the quesions. For that matter, when asking for help, posting 2 or 3 (poorly typed) sentences is rarely enough info to go on. Again, provide as much detail and specific info as possible.
this is mostly an outdated firmware issue, Always make sure you have the latest firmware for your device
Firmware 4.5.1/nougat/3T
Firmware 4.5.0/nougat/3
or you can try the Oreo ones
(Stable)
Firmware 5.0.0/Oreo/3T
Firmware 5.0.0/Oreo/3
(Open Beta)
Firmware OB20/Oreo/3T
Firmware OB29/Oreo/3
OP3T firmware thread https://forum.xda-developers.com/oneplus-3t/how-to/firmware-modem-collection-flashable-zips-t3565535
OP3 firmware thread https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
redpoint73 said:
I said: always give a version number. "latest bluesparks" isn't a version number. I can't count how many times I've seen folks claim they flashed the "latest" recovery. And when prompted for more info, we find out that they aren't even close, sometimes flashing a version TWRP from 2 years ago or older! Not saying this is necessarily your case. But we don't know for certain, if you don't give us precise and accurate info to work with.
You also said you flashed official TWRP. What version number exactly?
You also need to tell us what custom ROMs (and versions) you tried to flash. And what version OOS did you try to flash?
Some friendly advice, try to take more than 5 seconds to type a response to questions we ask you. Provide as much detail as possible, and answer all the quesions. For that matter, when asking for help, posting 2 or 3 (poorly typed) sentences is rarely enough info to go on. Again, provide as much detail and specific info as possible.
Click to expand...
Click to collapse
the bluesparks twrp which i flashed is 8.61 op-3t
and the official twrp which works is 3.2.1-0
so when i use the official twrp i have to remove the "assert" from the updater script and flash the rom or else i get the error 7
Something which has come up recently is that my homebutton/fingerprint sensor does not work (its like it doesnt exist) when i flash any rom from android 7-8.1.
So i came to stock by relocked the bootloader by the way like it happens when you hardbrick your device. now im in marshmallow.
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
The other funny thing is that when i called oneplus to help me with flashing the latest software there method helps me to get the bluesparks twrp but since i keep flashing i lose the twrp so thats the only way i can bliuesparks twrp
ak_bagade said:
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
Click to expand...
Click to collapse
Doesn't work like that, the home button, fp sensor "files" are not in TWRP, or managed by FW in any way. All of these are in the /system folder of the ROM that is installed. Which is why they don't work in TWRP.
Have you been on MM since you got this phone? If so, your firmware is heavily outdated, and that's why you end up with the White LED of Death. Try flashing the latest Open Beta over stock recovery. Make sure to unlock your bootloader first. Then flash any variant of TWRP you want, and then see if you still get the White LED of Death.
ak_bagade said:
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
Click to expand...
Click to collapse
You shouldn't be locking the bootloader if you are flashing custom recovery and custom ROMs, and you don't need a locked bootloader to flash official updates either. Really, there is no reason to lock the bootloader unless you are worried about security concerns; want a "full stock" conditions, etc. And for most xda users, an unlocked bootloader is going to be the highly preferable condition. Further, locking the bootloader requires be full stock (including stock recovery, not TWRP). And trying to lock the bootloader under any other condition, is asking for trouble.
I agree with the recommendation above, to flash the full zip of the Open Beta or official OOS update, which will put you on a fully "stock" baseline including firmware. Then go from there.
---------- Post added at 09:19 AM ---------- Previous post was at 09:07 AM ----------
ak_bagade said:
The other funny thing is that when i called oneplus to help me with flashing the latest software there method helps me to get the bluesparks twrp but since i keep flashing i lose the twrp so thats the only way i can bliuesparks twrp
Click to expand...
Click to collapse
If flashing the official zips with TWRP (including blu_sparks), you will always lose TWRP (overwritten with stock recovery) if you reboot after flashing the update. You can prevent this by flashing root (SuperSU, Magisk) or a custom kernel before rebooting (after the update).
So I have spent a lot of time messing around with roms and roots on nougat but I have recently restored my device to factory to use the recent official 8.0 OTA update and I now want to root the device. However with the new kernel Im not sure if I should use a different twrp or I just install the same as I used before with the modified flash command (recovery_ramdisk).
I used to use twrp-3.1.1-0-vtr.img or twrp-3.1.0-0-vtr.img, can I just flash this or do I need an oreo version?
If so what new twrp should I be using?
Jyndon said:
So I have spent a lot of time messing around with roms and roots on nougat but I have recently restored my device to factory to use the recent official 8.0 OTA update and I now want to root the device. However with the new kernel Im not sure if I should use a different twrp or I just install the same as I used before with the modified flash command (recovery_ramdisk).
I used to use twrp-3.1.1-0-vtr.img or twrp-3.1.0-0-vtr.img, can I just flash this or do I need an oreo version?
If so what new twrp should I be using?
Click to expand...
Click to collapse
Bump!
no one knows what recovery works on 8.0???
Jyndon said:
Bump!
no one knows what recovery works on 8.0???
Click to expand...
Click to collapse
I guess you should go for 3.2.1-0
I use this since @espaciosalter20 posted it and it works very good, I never noticed any issues. Data encryption works well.
Hello, I used to modify my android a lot, but it's been a while now. So before I soft brick my device, I'd like to get some advice.
My OT3T used to have a custom TWRP, and rooted with Magisk. Today, I found out, that for some reason, it has rollbacked back to default recovery and the root no longer works. My bootloader is still unlocked though.
So questions. Which version of TWRP would be the best for the new 9.0.3? Can I flash the latest TWRP version straight away or I have to install an older version and then update it?
Which version of Magisk? I guess the latest will do.
Then if the TWRP is installed properly, I guess, I can just follow the guideline from this thread: https://forum.xda-developers.com/on...l-oxygenos-5-0-1-android-8-0-t3728119/page135
TheoKondak said:
Hello, I used to modify my android a lot, but it's been a while now. So before I soft brick my device, I'd like to get some advice.
My OT3T used to have a custom TWRP, and rooted with Magisk. Today, I found out, that for some reason, it has rollbacked back to default recovery and the root no longer works. My bootloader is still unlocked though.
So questions. Which version of TWRP would be the best for the new 9.0.3? Can I flash the latest TWRP version straight away or I have to install an older version and then update it?
Which version of Magisk? I guess the latest will do.
Then if the TWRP is installed properly, I guess, I can just follow the guideline from this thread: https://forum.xda-developers.com/on...l-oxygenos-5-0-1-android-8-0-t3728119/page135
Click to expand...
Click to collapse
Just flash the latest version of TWRP (3.3.1-0) and the latest stable version of Magisk (19.3). Then follow the instructions.
Make sure you backup your user data (/sdcard) to your PC before updating OOS.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Just flash the latest version of TWRP (3.3.1-0) and the latest stable version of Magisk (19.3). Then follow the instructions.
Make sure you backup your user data (/sdcard) to your PC before updating OOS.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thanks Bill. I will try that today. I hope it will run smoothly.