3.2.7 to 4.0.2 direct OTA update for rooted Oneplus 3 - OnePlus 3 Questions & Answers

I decided not to update to 3.2.8 after reading all the bad reviews. Now that 4.0.2 is out and reviews are not so bad, im going to update to 4.0.2. I'm on OxygenOS 3.2.7 and the official OTA update installer is showing the message " Rooted device detected,update may fail."
After reading some posts about OTA updates failing for rooted users and causing loops, I manually downloaded 4.0.2 from here
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.0.2/
Can someone please tell how to proceed now. ( Device is rooted, twrp and xposed installed )
Can i flash the downloaded update from TWRP ? can someone please give steps to update.
Thanks

just do a clean flash like any other rom. flash super su immediately after the rom without rebooting to get root access.

jaj473 said:
I decided not to update to 3.2.8 after reading all the bad reviews. Now that 4.0.2 is out and reviews are not so bad, im going to update to 4.0.2. I'm on OxygenOS 3.2.7 and the official OTA update installer is showing the message " Rooted device detected,update may fail."
After reading some posts about OTA updates failing for rooted users and causing loops, I manually downloaded 4.0.2 from here
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.0.2/
Can someone please tell how to proceed now. ( Device is rooted, twrp and xposed installed )
Can i flash the downloaded update from TWRP ? can someone please give steps to update.
Thanks
Click to expand...
Click to collapse
I think the safest method is the following :
1. Make a copy of the Internal memory contents so that you can recover it at the end.
2. Reboot Fastboot and flash stock recovery by adb.
3. Reboot recovery and make full wipes from stock recovery (factory reset, cache and internal memory). At this point, data partition will have change to f2fs format.
4. Put the full 4.0.2 rom inside adb folder, reboot to Fastboot and connect the device to the computer again.
5. Install the rom and when it finishs, reboot system. When the rom is showed in the screen, reboot to Fastboot again and install the last official TWRP by adb again.
6. Reboot recovery, connect it to the pc and copy Supersu to the internal memory.
7. Switch it off from the pc, install Supersu from recovery and reboot system.
8. Copy the saved contents to the internal SD.
That's all...
Enviado desde mi ONEPLUS A3003 mediante Tapatalk

Crazyhat said:
I think the safest method is the following :
1. Make a copy of the Internal memory contents so that you can recover it at the end.
2. Reboot Fastboot and flash stock recovery by adb.
3. Reboot recovery and make full wipes from stock recovery (factory reset, cache and internal memory). At this point, data partition will have change to f2fs format.
4. Put the full 4.0.2 rom inside adb folder, reboot to Fastboot and connect the device to the computer again.
5. Install the rom and when it finishs, reboot system. When the rom is showed in the screen, reboot to Fastboot again and install the last official TWRP by adb again.
6. Reboot recovery, connect it to the pc and copy Supersu to the internal memory.
7. Switch it off from the pc, install Supersu from recovery and reboot system.
8. Copy the saved contents to the internal SD.
That's all...
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
Why would you want to sideload the ROM and then perform a wipe to get f2fs, also with the stock recovery. It can be done via twrp itself and the ROM can be flashed normally via twrp.
Sent from my OnePlus3 using XDA Labs

bonham1988 said:
Why would you want to sideload the ROM and then perform a wipe to get f2fs, also with the stock recovery. It can be done via twrp itself and the ROM can be flashed normally via twrp.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
I said this is the safest way to avoid the dm-verity message. Theoretically, what you propose is correct but it's not as safer. In fact, this forum is plenty of issues from people who tried to do it like you say.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk

Crazyhat said:
I said this is the safest way to avoid the dm-verity message. Theoretically, what you propose is correct but it's not as safer. In fact, this forum is plenty of issues from people who tried to do it like you say.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
No there are no issues with it apart from the DM verity splash screen. If you doing a clean install you should not have any issue and if DM verity is such a big deal you can also flash 3.2.8 or 3.5.5 forward to get rid of it.
Sent from my OnePlus3 using XDA Labs

jaj473 said:
I decided not to update to 3.2.8 after reading all the bad reviews. Now that 4.0.2 is out and reviews are not so bad, im going to update to 4.0.2. I'm on OxygenOS 3.2.7 and the official OTA update installer is showing the message " Rooted device detected,update may fail."
After reading some posts about OTA updates failing for rooted users and causing loops, I manually downloaded 4.0.2 from here
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.0.2/
Can someone please tell how to proceed now. ( Device is rooted, twrp and xposed installed )
Can i flash the downloaded update from TWRP ? can someone please give steps to update.
Thanks
Click to expand...
Click to collapse
Consider one Thing: There is no xposed available so far. That's why I stay with 3.2.8.
---------- Post added at 12:44 PM ---------- Previous post was at 12:38 PM ----------
Crazyhat said:
I think the safest method is the following :
1. Make a copy of the Internal memory contents so that you can recover it at the end.
2. Reboot Fastboot and flash stock recovery by adb.
3. Reboot recovery and make full wipes from stock recovery (factory reset, cache and internal memory). At this point, data partition will have change to f2fs format.
4. Put the full 4.0.2 rom inside adb folder, reboot to Fastboot and connect the device to the computer again.
5. Install the rom and when it finishs, reboot system. When the rom is showed in the screen, reboot to Fastboot again and install the last official TWRP by adb again.
6. Reboot recovery, connect it to the pc and copy Supersu to the internal memory.
7. Switch it off from the pc, install Supersu from recovery and reboot system.
8. Copy the saved contents to the internal SD.
That's all...
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
One question to your procedure:
Which version of stock recovery do you use in this procedure? Since you make a full wipe before installing anything else to f2fs I assume, it must be the latest version. Do you have a download link to this for safety reasons? Tks a lot!

bonham1988 said:
No there are no issues with it apart from the DM verity splash screen. If you doing a clean install you should not have any issue and if DM verity is such a big deal you can also flash 3.2.8 or 3.5.5 forward to get rid of it.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Dm-verity is a problem for many people. I won't need to go back to 3.2.8 rom again if previously I did it well so, in my modest opinion, it's much better to ensure that it doesn't happen. Anyway, you can do it whatever you like. It's not my business.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk

Crazyhat said:
Dm-verity is a problem for many people. I won't need to go back to 3.2.8 rom again if previously I did it well so, in my modest opinion, it's much better to ensure that it doesn't happen. Anyway, you can do it whatever you like. It's not my business.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
You don't actually have to go to 3.2.8 ROM. You just have to flash the firmware and modem. And DM verity is subjective there are many people myself included who don't find that extra splash screen an issue at all.
Sent from my OnePlus3 using XDA Labs

Sir Backe said:
Consider one Thing: There is no xposed available so far. That's why I stay with 3.2.8.
---------- Post added at 12:44 PM ---------- Previous post was at 12:38 PM ----------
One question to your procedure:
Which version of stock recovery do you use in this procedure? Since you make a full wipe before installing anything else to f2fs I assume, it must be the latest version. Do you have a download link to this for safety reasons? Tks a lot!
Click to expand...
Click to collapse
The safest place for that is the OnePlus site. You have to flash v2 which is the latest version. The OnePlus site will merely show you one link without indicating whether it is for v1 or v2. You can go ahead and download it as it is the v2.

bonham1988 said:
You don't actually have to go to 3.2.8 ROM. You just have to flash the firmware and modem. And DM verity is subjective there are many people myself included who don't find that extra splash screen an issue at all.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Ok, great! I have been several months with it too, but only because It never was a trouble for me neither.
---------- Post added at 02:29 PM ---------- Previous post was at 02:13 PM ----------
Sir Backe said:
Consider one Thing: There is no xposed available so far. That's why I stay with 3.2.8.
---------- Post added at 12:44 PM ---------- Previous post was at 12:38 PM ----------
One question to your procedure:
Which version of stock recovery do you use in this procedure? Since you make a full wipe before installing anything else to f2fs I assume, it must be the latest version. Do you have a download link to this for safety reasons? Tks a lot!
Click to expand...
Click to collapse
Probably, this is not the last version, but it works fine. Right now I'm working and I hope you'll understand that I don't have enough time to look for the last version. Anyway, I leave you this link just in case it is useful for you....
https://s3.amazonaws.com/oxygenos.oneplus.net/recovery.img

@Crazyhat
Tks for the link. I just downloaded it from the Oneplus Website according to @tnsmani recommendation. I didn't actually know that it is there, hidden in the depth of the OP Website mess .

Sir Backe said:
@Crazyhat
Tks for the link. I just downloaded it from the Oneplus Website according to @tnsmani recommendation. I didn't actually know that it is there, hidden in the depth of the OP Website mess .
Click to expand...
Click to collapse
Hahaha.... You will have to trust them [emoji4] [emoji106]
Enviado desde mi ONEPLUS A3003 mediante Tapatalk

Related

Can I Downgrade Nexus 5x from Android 7.0 to Marshmallow 6.0.1 ?

Can I Downgrade Nexus 5x from Android 7.0 to Marshmallow 6.0.1 ?
I Heard users report bricked device by doing so, is that true?
I really want to downgrade because this **** Nougat is soo buggy, Setting Apps crashed and all social media apps lags and sometime irresponsive.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
check this if you want to return to previous version of android
zocex said:
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
check this if you want to return to previous version of android
Click to expand...
Click to collapse
with reference to exact same post I said the users report brick device while downgrading.. I want to have more opinions about this issue if anyone tried doing so. Thanks
hasankhan222 said:
with reference to exact same post I said the users report brick device while downgrading.. I want to have more opinions about this issue if anyone tried doing so. Thanks
Click to expand...
Click to collapse
Here is what I did b/c Android N and the lack of notifications blows.
1) I got the Factory images from the normal place.
2) Extracted boot.img, system.img, and vendor.img
3) placed those on the root of my device
4) Booted into TWRP and Wiped everything except internal memory card
5) In TWRP apply those img files
6) booted as normal
7) Booted back into bootloader and flash twrp again ( yes it will wipe it )
8) reboot bootloader using keys, re-flash twrp
9) Boot into TWRP apply whatever you need to apply OR just boot as normal
carm01 said:
Here is what I did b/c Android N and the lack of notifications blows.
1) I got the Factory images from the normal place.
2) Extracted boot.img, system.img, and vendor.img
3) placed those on the root of my device
4) Booted into TWRP and apply those img files
5) Wiped everything except internal memory card
6) booted as normal
7) Booted back into bootloader and flash twrp again ( yes it will wipe it )
8) reboot bootloader using keys, re-flash twrp
9) Boot into TWRP apply whatever you need to apply OR just boot as normal
Click to expand...
Click to collapse
Thanks Sir for your detailed go through but I want to be on stock firmware + settings with no root or TWRP.
I want to do it by fastboot way if there will be no chance then will try this method maybe in future.
hasankhan222 said:
Thanks Sir for your detailed go through but I want to be on stock firmware + settings with no root or TWRP.
I want to do it by fastboot way if there will be no chance then will try this method maybe in future.
Click to expand...
Click to collapse
So your bootloader is locked and no root and you want to downgrade from 7.0 to 6.0.1 ?
carm01 said:
Here is what I did b/c Android N and the lack of notifications blows.
1) I got the Factory images from the normal place.
2) Extracted boot.img, system.img, and vendor.img
3) placed those on the root of my device
4) Booted into TWRP and apply those img files
5) Wiped everything except internal memory card
6) booted as normal
7) Booted back into bootloader and flash twrp again ( yes it will wipe it )
8) reboot bootloader using keys, re-flash twrp
9) Boot into TWRP apply whatever you need to apply OR just boot as normal
Click to expand...
Click to collapse
Did you push the files using /adb?
carm01 said:
So your bootloader is locked and no root and you want to downgrade from 7.0 to 6.0.1 ?
Click to expand...
Click to collapse
Yes... eventually i will unlock bootloader while flashing .imgs but is it safe to downgrade from 7.0 to 6.0.1..? I heard some ppl end up with bricked devices
hasankhan222 said:
Yes... eventually i will unlock bootloader while flashing .imgs but is it safe to downgrade from 7.0 to 6.0.1..? I heard some ppl end up with bricked devices
Click to expand...
Click to collapse
My bootloader is unlocked, and in past experiences ( with HTC devices ) I always thought that your bootloader has to be unlocked to go backwards.
Personally, I would not go backwards without unlocking the bootloader; but that's just me and my experiences.
Yeah you always want an Unlocker bootloader. You gain nothing by having it locked. I went back to 6.0.1 just using flashall and now I'm back to 7.0.0 with also just flash all. No issue on my side.
Sent from my Nexus 5X using Tapatalk
milan187 said:
Yeah you always want an Unlocker bootloader. You gain nothing by having it locked. I went back to 6.0.1 just using flashall and now I'm back to 7.0.0 with also just flash all. No issue on my side.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Out of curiosity, are you complete stock with encryption intact? I'm wondering why the 5X has fewer troubles moving between 7.0 and 6.0.1 but the 6P has a lot if issues with that.
Sent from my Nexus 5X using Tapatalk
milan187 said:
Yeah you always want an Unlocker bootloader. You gain nothing by having it locked. I went back to 6.0.1 just using flashall and now I'm back to 7.0.0 with also just flash all. No issue on my side.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
@milan187
How are your experiences with notifications; meaning lack of notifications aside from calls and text? i have had horrible issues with lack of notifications
carm01 said:
@milan187
How are your experiences with notifications; meaning lack of notifications aside from calls and text? i have had horrible issues with lack of notifications
Click to expand...
Click to collapse
I have no idea what issue you had but all my notifications work just the same as with M. All show up just fine. It's actually better to me.
Did you do a clean factory load? May want to try that?
I just got notified via tapatalk about your message.
Sent from my Nexus 5X using Tapatalk
i was on chroma, flashed dp5 directly,update ota to final nougat. phone works ok. then flash from 7 to factory image MTC20F,phone works ok. then update again to 7 with no problems at all. botloader was unlocked all time. i was just curious is there difference between update to 7 from dp5 and from 6.0.1. when i done it there was no nougat images to factory images site. u unpacked image and execute flash all command
only problem i have is twrp set to stick,and titanium backeup(when i delete some system apk and do clean dalvik,phone cant boot) i think this is problem with tb bcouse apk dalvik on nougat is not at same place as in mm
????
What problems do you have to return to any version of Android? You just have to flash the images (including radio and bootloader from that old version, and the rest of partitions).
To be honest, I am not even sure if returning to old bootloader/radio is even necessary.. I never needed doing that
milan187 said:
I have no idea what issue you had but all my notifications work just the same as with M. All show up just fine. It's actually better to me.
Did you do a clean factory load? May want to try that?
I just got notified via tapatalk about your message.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Let me elaborate: Phone unplugged, and after it is left alone , not touched for an hour or so, do you get notification alerts from Gmail, and any other app you installed?
I wiped everything except internal Sd card, so system, vendor, cache, app data, boot.
All my notifications except text and calls are suppressed after the phone is not touched for some time and unplugged.
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
RusherDude said:
????
What problems do you have to return to any version of Android? You just have to flash the images (including radio and bootloader from that old version, and the rest of partitions).
To be honest, I am not even sure if returning to old bootloader/radio is even necessary.. I never needed doing that
Click to expand...
Click to collapse
I left the N radio and Bootloader in tact after returning to 6.0.1, no issues
carm01 said:
Let me elaborate: Phone unplugged, and after it is left alone , not touched for an hour or so, do you get notification alerts from Gmail, and any other app you installed?
I wiped everything except internal Sd card, so system, vendor, cache, app data, boot.
All my notifications except text and calls are suppressed after the phone is not touched for some time and unplugged.
---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------
I returned to 6.0.1 and left the N radio and bootloader, no issues
Click to expand...
Click to collapse
They all come in but to be honest I keep my phone on Priority and phone calls only make sound. Everything else comes in and blinks led. That's the way I use all my devices. If it's just the sound that did not work for you I can test it for a few hours to make sure they come in.
Sent from my Nexus 5X using Tapatalk
Here's my fix:
1. Moved Nandroid backup to PC.
2. Download factory image MTC20F from https://developers.google.com/android/nexus/images.
3. Install factory image (This will erase all data on your phone so move your files to your PC).
4. Install TWRP 3.0.2-0 from https://dl.twrp.me/bullhead/twrp-3.0...lhead.img.html via fastboot.
5. Go in TWRP>Wipe>Advanced Wipe and repair all partitions that can be repaired (System, Data, Cache).
6. Restore Nandroid backup.
7. Success.
milan187 said:
They all come in but to be honest I keep my phone on Priority and phone calls only make sound. Everything else comes in and blinks led. That's the way I use all my devices. If it's just the sound that did not work for you I can test it for a few hours to make sure they come in.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for your info Sir, Can I just wipe my device and unlock the bootloader and flash 6.0.1 (MTC20F) images with fastboot including Radio and Bootloader?
hasankhan222 said:
Thanks for your info Sir, Can I just wipe my device and unlock the bootloader and flash 6.0.1 (MTC20F) images with fastboot including Radio and Bootloader?
Click to expand...
Click to collapse
That's what I did though I'm back on N now. Unlocking your bootloader will wipe the device as far as I remember.
Sent from my Nexus 5X using Tapatalk

So you cant root OOS 4.0?

I have searched and i havent find a solution
I updated, im on OOS 4.0 with F2FS everything smooth and nice.
After setting up i try to flash twrp and once i boot into it it ask me for a password wich isnt the one i put.
I saw some people are in the same problem as i but i didnt see anything taht could help me at all.
I tried with the modified twrp, same thing,
I just want to get it root, any solutions?
Thanks
Well, I managed to get OOS4 with root and data partition as F2FS.
I followed this procedure and worked out just great ! https://forums.oneplus.net/threads/...g-dm-verity-error.484019/page-2#post-15558781
Not sure if you can skip some of the steps but right now I have OOS4, with root and TWRP (modified) working and capable of decrypting !
You are encrypted.. Decrypt flash Oos 4.0 directly after that flash SuperSU. I do recommend you using freedomos
DirtyWizard said:
Well, I managed to get OOS4 with root and data partition as F2FS.
I followed this procedure and worked out just great ! https://forums.oneplus.net/threads/...g-dm-verity-error.484019/page-2#post-15558781
Not sure if you can skip some of the steps but right now I have OOS4, with root and TWRP (modified) working and capable of decrypting !
Click to expand...
Click to collapse
It requires a USB Otg, but thanks!
I read that TWRP just needs to update their recovery in case I decide to wait
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Puddi_Puddin said:
You are encrypted.. Decrypt flash Oos 4.0 directly after that flash SuperSU. I do recommend you using freedomos
Click to expand...
Click to collapse
Can you provide me baby steps or refer to ones? My op3 and I will appreciate itt
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
nickest said:
Can you provide me baby steps or refer to ones? My op3 and I will appreciate itt
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Click to expand...
Click to collapse
I do recommend you to wipe userdata then install freedomOS. (you can choose what you want and what you dont want with freedomos)
1. Boot your device into fastboot
2. Go to your Adb drivers and type "fastboot erase userdata"
3. Once that completed adb push the freedomos zip file. I do recommend 3.4 based on OOS 4.0 or you can do what ever you like. Note: to use adb push I do recommend you to put the install zip in the same folder as the adb drivers then type "adb push NAME_OF_ZIP.zip(or just press tab) /system/
4. If you go to TWRP you will find the installation zip under the folder system.
5. Once that's done boot and profit.
nickest said:
It requires a USB Otg, but thanks!
I read that TWRP just needs to update their recovery in case I decide to wait
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Click to expand...
Click to collapse
It does not require USB OTG. I managed to get it to work without. Just format Data to F2FS and reboot the phone in recovery.
You can then via MTP easily transfer the files and flash in TWRP.
DirtyWizard said:
It does not require USB OTG. I managed to get it to work without. Just format Data to F2FS and reboot the phone in recovery.
You can then via MTP easily transfer the files and flash in TWRP.
Click to expand...
Click to collapse
Don't! Do not use MTP the chance of corrupted files is to big, thats why Adb has been designed!

Back to stock OxygenOS (OP3)

I found 2 versions of the instruction about going back from custom ROM to stock OxygenOS. First one tells about ADB commands which results with full stock, with standard recovery, unrooted system and locked phone. The second one is shorter, it's just flashing official zip with TWRP.
So my question is: Am I "losing something" after going with the second option, I mean TWRP-way? As I understand the only difference is that I'll keep TWRP itself and my phone will still be unlocked, when everything else will be ok (official camera firmware, kernel, etc.).
Thank you in advance for the answer if I'm wrong
The official zips in most cases also erase your twrp recovery and you will end up with the stock recovery and unlocked bootloader
I'm also thinking about going back to Oxygenos. But haven't done it. Looking for answers for you question.
Besides, could you please give me the link for the first method? Thanks
It's like flashing any other Rom? You clean flash by wiping everything (except Internal) and flash the OxygenOS you want (plus SuperUser).
Heres what you gonna do
Download oos full zip
Flash it on twrp then after that dont do a reboot just flash twrp as recovery then reboot to recovery and then reboot to system
If you wanna lock the bootloader and stay fully stock ( this will wipe your whole phone so backup )
Then flash oos full zip through twrp then reboot to bootloader
Then sideload oos recovery
Then go back to bootloader and relock bootloader thats it
Sent from my ONEPLUS A3003 using Tapatalk
You want to ADB push?
Go to OnePlus site. There you have step by step instructions.
HIshan Pavidu said:
Heres what you gonna do
Download oos full zip
Flash it on twrp then after that dont do a reboot just flash twrp as recovery then reboot to recovery and then reboot to system
If you wanna lock the bootloader and stay fully stock ( this will wipe your whole phone so backup )
Then flash oos full zip through twrp then reboot to bootloader
Then sideload oos recovery
Then go back to bootloader and relock bootloader thats it
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I want to keep twrp and stay unlocked
1. flash the oos full zip
2. reboot to fastboot mode and flash twrp
3. go to twrp and reboot to system
Is this right?
Besides, I'm using twrp 3.0.4-1. Does it matter?
JonathanKang said:
I want to keep twrp and stay unlocked
1. flash the oos full zip
2. reboot to fastboot mode and flash twrp
3. go to twrp and reboot to system
Is this right?
Besides, I'm using twrp 3.0.4-1. Does it matter?
Click to expand...
Click to collapse
They both works but my way dont need a pc so
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
They both works but my way dont need a pc so
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Ahh. Got it.
JonathanKang said:
Ahh. Got it.
Click to expand...
Click to collapse
Good luck huh!
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
Good luck huh!
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I clean flashed the full zip. When I try to boot to bootloader, it didn't enter bootloader mode. The system boots, and it's been showing boot animation for more than ten minutes. I'll wait patiently.
BTW, how do you flash twrp while you are in twrp?
JonathanKang said:
I clean flashed the full zip. When I try to boot to bootloader, it didn't enter bootloader mode. The system boots, and it's been showing boot animation for more than ten minutes. I'll wait patiently.
BTW, how do you flash twrp while you are in twrp?
Click to expand...
Click to collapse
What i did was
Flashed the full zip
Before rebooting flashed twrp.img through twrp
Then reboot to twrp abd reboot to system i do it every time
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
What i did was
Flashed the full zip
Before rebooting flashed twrp.img through twrp
Then reboot to twrp abd reboot to system i do it every time
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
What I wanna ask is how do you flash twrp.img through twrp?
JonathanKang said:
What I wanna ask is how do you flash twrp.img through twrp?
Click to expand...
Click to collapse
When your on twrp go to install then to the right corner youll see a tab named flash img clikc that and browse to your twrp flash it then it will ask system , recovery or bootloader click recovery then flash when it finished reboot to recovery
I hope you understand if not just google it
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
When your on twrp go to install then to the right corner youll see a tab named flash img clikc that and browse to your twrp flash it then it will ask system , recovery or bootloader click recovery then flash when it finished reboot to recovery
I hope you understand if not just google it
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Okay. Never notice that tab in the corner.
So right now, I end up with oxygenos(still booting...) without twrp.
JonathanKang said:
Okay. Never notice that tab in the corner.
So right now, I end up with oxygenos(still booting...) without twrp.
Click to expand...
Click to collapse
Try holding power button till it restart and see if you can load to bootloader then sideload twrp then do what i said
Good luck
If it wont load bootloader i think its bricked or something
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
Try holding power button till it restart and see if you can load to bootloader then sideload twrp then do what i said
Good luck
If it wont load bootloader i think its bricked or something
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Force shutdown the device and entered fastboot, flashed twrp recovery. And now twrp asks me to input password to decrypt data. I have no idea about what the password is. I also got dm-verity error after flashing the full zip. Help needed.
JonathanKang said:
Force shutdown the device and entered fastboot, flashed twrp recovery. And now twrp asks me to input password to decrypt data. I have no idea about what the password is. I also got dm-verity error after flashing the full zip. Help needed.
Click to expand...
Click to collapse
Im sorry i have to say this but you might wanna sideload oos recovery then sideload oos full zip and see if its boot then try again
Edit :- you might wanna wipe everything before sideload idk try without wiping anything
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
Im sorry i have to say this but you might wanna sideload oos recovery then sideload oos full zip and see if its boot then try again
Edit :- you might wanna wipe everything before sideload idk try without wiping anything
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I did a factory reset in twrp, and the system boots well. But unfortunately I lost all my data. Factory reset also formats internal storage?
I have all my photos backed up in google photos. The only loss is the image quality is not original. Anyway it's not end of the world.
JonathanKang said:
I did a factory reset in twrp, and the system boots well. But unfortunately I lost all my data. Factory reset also formats internal storage?
I have all my photos backed up in google photos. The only loss is the image quality is not original. Anyway it's not end of the world.
Click to expand...
Click to collapse
Your good then right? Cuz i gotta go flash rr ?
Sent from my ONEPLUS A3003 using Tapatalk

Looking for Mi Mix 2 8.5.11 (leaked MiUI10, Android P style) file

Hi every one, does anyone have a file of MiUI 8.5.11 with Android P style? I've been looking everywhere, but all threads on MiUI forum are deleted, funkyhuawei's links are note active anymore
Hilus said:
Hi every one, does anyone have a file of MiUI 8.5.11 with Android P style? I've been looking everywhere, but all threads on MiUI forum are deleted, funkyhuawei's links are note active anymore
Click to expand...
Click to collapse
i got it from a site let me find the link again : http://space4.space/resources/official-mi-mix-2-global-nightly-rom-android-8-0-miui-9-x.3/
---------- Post added at 03:10 AM ---------- Previous post was at 02:33 AM ----------
BTW I'm on 8.4.24 how can I install the 8.5.11 without bootloader unlocked ??? And if I unlocked the bootloader by Xiaomi tool will it wipe all my data ??
Hilus said:
Hi every one, does anyone have a file of MiUI 8.5.11 with Android P style? I've been looking everywhere, but all threads on MiUI forum are deleted, funkyhuawei's links are note active anymore
Click to expand...
Click to collapse
Currently downloading, had to create an account on that Russian site.. Will upload to GoogleDrive and repost.
Edit: With my upload speed please expect it ready in about 10 hours
[Nanashi] said:
Currently downloading, had to create an account on that Russian site.. Will upload to GoogleDrive and repost.
Edit: With my upload speed please expect it ready in about 10 hours
Click to expand...
Click to collapse
Hahaha, thanks so much
Uploaded it to GDrive:
https://drive.google.com/open?id=1Ple1Qg9X7QMAXjqU0PKKf0J5TguK0QnJ
Hilus said:
Hahaha, thanks so much
Click to expand...
Click to collapse
No worries Looks like someone beat me to it. Here I am sitting with a 75% upload on my potato internet haha.
Just FYI the build is pretty buggy, things I've noticed so far is that opening quick settings animation can trip out a little bit and every now and then icons from the status bar go missing also search in the settings can crash the app. As expected from a first build of this new style, might be a dealbreaker for some but the new look is pretty sick so it shall stay on my device until the next developer build. :good: :good:
[Nanashi said:
;76522906]No worries Looks like someone beat me to it. Here I am sitting with a 75% upload on my potato internet haha.
Just FYI the build is pretty buggy, things I've noticed so far is that opening quick settings animation can trip out a little bit and every now and then icons from the status bar go missing also search in the settings can crash the app. As expected from a first build of this new style, might be a dealbreaker for some but the new look is pretty sick so it shall stay on my device until the next developer build. :good: :good:
Click to expand...
Click to collapse
What was the last rom you where on ? And did you dirty flash on TWRP or fast boot ?? Can you explain you're process please !! I'm on 8.4.24 bootlocked . Thx and also does the action of unlocking boot wipe data??
Should I install TWRP or just flashboot it, thx
Thanks man
I will unlock my bootloader and hopefully it will work
dangerousrun said:
What was the last rom you where on ? And did you dirty flash on TWRP or fast boot ?? Can you explain you're process please !! I'm on 8.4.24 bootlocked . Thx and also does the action of unlocking boot wipe data??
Should I install TWRP or just flashboot it, thx
Click to expand...
Click to collapse
Hey, I came from the latest developer ROM release from the official MIUI download site.
Used TWRP and did a clean flash after wiping literally everything possible twice. Getting access from Xiaomi to have the ability to unlock your bootloader does not wipe anything but does take up to 72 hours I believe. Unlocking the bootloader itself will wipe all your data and factory reset so if you're planning to flash a new ROM anyway then it's not a problem. I rarely use these nightly more experimental builds because they are less stable and I need to use TWRP which isn't much of a problem but the stable and developer released ROMs from the official MIUI download site are available as a fastboot version which you can flash with the Xiaomi Flash tool which fully wipes anything and everything from the phone and installs your MIUI ROM of choice as it were a new phone.
If you or anyone else uses Discord, feel free to hit me up on there. I have barely any status on this website but have been mucking around with ROMs for years. Kaji#4985
Has it face unlock feature?
I'm about to get Mi Mix 2 in my hands...
Adriano-A3 said:
Has it face unlock feature?
I'm about to get Mi Mix 2 in my hands...
Click to expand...
Click to collapse
No faceUnlock, little bug in setting when you use the search bar, less fluidity and google play not certified
For my use it's daily usable
Adriano-A3 said:
Has it face unlock feature?
I'm about to get Mi Mix 2 in my hands...
Click to expand...
Click to collapse
If you want face unlock you'll have to use Epic ROM or something of the sort.
Greetings, I have a problem, it is that when it finishes making the flash of the ROM it does not reboot the system it gets stuck in reboots to the recovery, someone can give me a hand ..
Thanks from Colombia
ronaldrenteria said:
Greetings, I have a problem, it is that when it finishes making the flash of the ROM it does not reboot the system it gets stuck in reboots to the recovery, someone can give me a hand ..
Thanks from Colombia
Click to expand...
Click to collapse
Hi there friend, what kind of flash are you doing? Dirty or clean. The chances are you need to wipe everything before this installation.
Also, what ROM are you coming from? If it's a version before Android 8.0 you may need to flash any of the official global oreo ROMs from the MIUI download site first which I would recommend doing the fastboot way (downloading fastboot version of the ROM and flashing with Xiaomi Flash Tool).
ronaldrenteria said:
Greetings, I have a problem, it is that when it finishes making the flash of the ROM it does not reboot the system it gets stuck in reboots to the recovery, someone can give me a hand ..
Thanks from Colombia
Click to expand...
Click to collapse
TWRP format data "yes"
Kaji said:
Hi there friend, what kind of flash are you doing? Dirty or clean. The chances are you need to wipe everything before this installation.
Also, what ROM are you coming from? If it's a version before Android 8.0 you may need to flash any of the official global oreo ROMs from the MIUI download site first which I would recommend doing the fastboot way (downloading fastboot version of the ROM and flashing with Xiaomi Flash Tool).
Click to expand...
Click to collapse
I will try to explain what I am doing.
1 - I'm in XIAOMI.EU
2 - I'm using TWRP
3 - I'm doing a complete Wipe of everything I have in the Phone
4 - I'm doing adb sideload
5 - Finish the Flash but at the time of restart returns to Recovery.
Where this error?
---------- Post added at 01:22 AM ---------- Previous post was at 01:22 AM ----------
Mackay53 said:
TWRP format data "yes"
Click to expand...
Click to collapse
I will try to explain what I am doing.
1 - I'm in XIAOMI.EU
2 - I'm using TWRP
3 - I'm doing a complete Wipe of everything I have in the Phone
4 - I'm doing adb sideload
5 - Finish the Flash but at the time of restart returns to Recovery.
Where this error?
ronaldrenteria said:
I will try to explain what I am doing.
1 - I'm in XIAOMI.EU
2 - I'm using TWRP
3 - I'm doing a complete Wipe of everything I have in the Phone
4 - I'm doing adb sideload
5 - Finish the Flash but at the time of restart returns to Recovery.
Where this error?
---------- Post added at 01:22 AM ---------- Previous post was at 01:22 AM ----------
I will try to explain what I am doing.
1 - I'm in XIAOMI.EU
2 - I'm using TWRP
3 - I'm doing a complete Wipe of everything I have in the Phone
4 - I'm doing adb sideload
5 - Finish the Flash but at the time of restart returns to Recovery.
Where this error?
Click to expand...
Click to collapse
I'm no expert but I recommend just flashing it in TWRP. Fastboot flash TWRP and boot to it, wipe everything...EVERYTHING, and then copy the zip across for this ROM then flash and reboot.
ronaldrenteria said:
I will try to explain what I am doing.
1 - I'm in XIAOMI.EU
2 - I'm using TWRP
3 - I'm doing a complete Wipe of everything I have in the Phone
4 - I'm doing adb sideload
5 - Finish the Flash but at the time of restart returns to Recovery.
Where this error?
---------- Post added at 01:22 AM ---------- Previous post was at 01:22 AM ----------
I will try to explain what I am doing.
1 - I'm in XIAOMI.EU
2 - I'm using TWRP
3 - I'm doing a complete Wipe of everything I have in the Phone
4 - I'm doing adb sideload
5 - Finish the Flash but at the time of restart returns to Recovery.
Where this error?
Click to expand...
Click to collapse
1. Use latest TWRP
2. Quick wipe
3. Flash rom
4. Factory reset
5. Boot
That's always worked for me for any rom whether it's custom or miui.
so I am doing it, but I can not make it walk, I have returned to Xiaomi.EU, the way I return to Xiaomi.EU is the same method I use for ROM 8.5.11.
Thank you.
---------- Post added at 12:41 PM ---------- Previous post was at 12:40 PM ----------
Kaji said:
I'm no expert but I recommend just flashing it in TWRP. Fastboot flash TWRP and boot to it, wipe everything...EVERYTHING, and then copy the zip across for this ROM then flash and reboot.
Click to expand...
Click to collapse
Mackay53 said:
1. Use latest TWRP
2. Quick wipe
3. Flash rom
4. Factory reset
5. Boot
That's always worked for me for any rom whether it's custom or miui.
Click to expand...
Click to collapse
so I am doing it, but I can not make it walk, I have returned to Xiaomi.EU, the way I return to Xiaomi.EU is the same method I use for ROM 8.5.11.
Thank you.
Can i flash it on device via update or i have to use TWRP? I am on unlocked mi Mix 2 with Oreo?

[RECOVERY][Official] TWRP 3.4.0-6 [T83x][mtp][otg]

TWRP 3.4 for Android 10 SM-T83x
This build of TWRP is now Official.
Official TWRP web link
Built using OMNI source
TWRP v3.4
See post #2 for install steps
Changelog...
1.0
Initial build
MTP, OTG and SDcard all working
4.0
Now in portrait mode
Brightness fixed
5.0
Updated for Android 10
TWRP Downloads
Download folder
Official device tree on twrp.me
--------------------->
Kernel Source
Source
Device Tree
Source
--------------------->
Beer fund
You can flash TWRP two ways, either directly from an existing TWRP install, using the linked TWRP.img file. Or you can flash using Odin and the TWRP.tar file.
You will need a custom kernel with dm-verity disabled to be able to boot up afterwards. You will also need to disable encryption and format data to be able to read from the sdcard (encryption isn't supported).
The flashing process is as follows.
Get yourself onto stock Pie firmware, using Odin to flash the complete package. Before proceeding. Boot up and make sure you have OEM unlock switch and its activated.
1. Boot into Download mode and Flash TWRP (Download) using Odin (use AP)
2. Immediately boot into TWRP after flashing takes place, hold vol up and power.
3. Format data partition (wipe/format data)
4. Reboot recovery
5. Copy WETA Kernel + Encryption disabler + Magisk zip to device. - (Download Kernel - Encryption disabler)
6. Flash WETA Kernel + Encrypt disabler + Magisk zip.
7. Boot up system, if it hangs on Samsung logo after 3min perform hard reboot.
8. Connect to internet and go to dev settings and check oem unlock is present before any rebooting.
** Custom kernel is universal for all bootloader v4 firmware.
--->
problem download
From croatia I cannot access this link. Can you upload on mega.
Thanks
macakfelix said:
From croatia I cannot access this link. Can you upload on mega.
Thanks
Click to expand...
Click to collapse
Your kidding? Usually people say upload anywhere but mega because of access.. haha. But sure. I'll mirror it to mega
Sent from my SM-N9600 using Tapatalk
macakfelix said:
From croatia I cannot access this link. Can you upload on mega.
Thanks
Click to expand...
Click to collapse
Mega mirrors are up,
Sent from my SM-N9600 using Tapatalk
Tested and working on T835 Pie. Finally good to have a TWRP with MTP & adb working. Thanks mate.
Mentalmuso said:
TWRP 3.3.0 for PIE SM-T83x
--------------------->
Beer fund
Click to expand...
Click to collapse
Hi friend, i flashed with odin but seems not to work, same as without flashing... im on pie now, but when on oreo was not so easy to flash twrp as this... i remember had to flash 1 or 2 more files, but not sure... any help?
EDIT im talking about TabS4_oreo_forced_encryption_disabler... do you get it work just flashing twrp or do you need any extra procedure?
Thanks in advance
My device is a SM-T835N
wallyhenderson said:
Hi friend, i flashed with odin but seems not to work, same as without flashing... im on pie now, but when on oreo was not so easy to flash twrp as this... i remember had to flash 1 or 2 more files, but not sure... any help?
EDIT im talking about TabS4_oreo_forced_encryption_disabler... do you get it work just flashing twrp or do you need any extra procedure?
Thanks in advance
My device is a SM-T835N
Click to expand...
Click to collapse
Sorry, I completely forgot that
Flash TWRP with Odin
Reboot straight to twrp.
Flash encryption disabler.
Format data.
Reboot recovery.
Mount data make sure you can read it .
Then you can flash a rom, kernel etc. I'll update the op in a bit
Sent from my SM-N9600 using Tapatalk
macakfelix said:
From croatia I cannot access this link. Can you upload on mega.
Thanks
Click to expand...
Click to collapse
https://mega.nz/#F!TZNgRYyB!7wa-W3moNILsezgkuj3nKA
Mentalmuso said:
Sorry, I completely forgot that
Flash TWRP with Odin
Reboot straight to twrp.
Flash encryption disabler.
Format data.
Reboot recovery.
Mount data make sure you can read it .
Then you can flash a rom, kernel etc. I'll update the op in a bit
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
Friend i have
Flash "TWRP-ODIN_Pie_3.3.0_sm-t83x_mentalmuso.tar" with Odin OK
Reboot straight to twrp OK
Flash encryption disabler "T83x_PIE_encrypt_disabler_+++.zip" OK
Format data OK
Reboot recovery OK
Mount data make sure you can read it OK (think ok, didnt know what to do)
And now im in a loop boot... can you help me i use phone to work and sadly will have to solve today or have to flash stock pie rom
Thanks in advance
Restored stock pie rom... seems to work fine without twrp but when trying to flash TWRP-ODIN_Pie_3.3.0_sm-t83x_mentalmuso and it says "only official released binaries allowed to be flashed (recovery)
wallyhenderson said:
Friend i have
Flash "TWRP-ODIN_Pie_3.3.0_sm-t83x_mentalmuso.tar" with Odin OK
Reboot straight to twrp OK
Flash encryption disabler "T83x_PIE_encrypt_disabler_+++.zip" OK
Format data OK
Reboot recovery OK
Mount data make sure you can read it OK (think ok, didnt know what to do)
And now im in a loop boot... can you help me i use phone to work and sadly will have to solve today or have to flash stock pie rom
Thanks in advance
Click to expand...
Click to collapse
What version of Android are you on?
Sent from my SM-N9600 using Tapatalk
wallyhenderson said:
Friend i have
Flash "TWRP-ODIN_Pie_3.3.0_sm-t83x_mentalmuso.tar" with Odin OK
Reboot straight to twrp OK
Flash encryption disabler "T83x_PIE_encrypt_disabler_+++.zip" OK
Format data OK
Reboot recovery OK
Mount data make sure you can read it OK (think ok, didnt know what to do)
And now im in a loop boot... can you help me i use phone to work and sadly will have to solve today or have to flash stock pie rom
Thanks in advance
Click to expand...
Click to collapse
Have you flashed a custom kernel? Or at least flashed magisk?
You cant boot using a stock kernel, when you have any other custom features on your device.
Sent from my SM-N9600 using Tapatalk
Mentalmuso said:
Have you flashed a custom kernel? Or at least flashed magisk?
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
it is mandatory to flash a custom kernel? will do if nessesary... i didnt... and didnt flashed magisk
---------- Post added at 11:05 PM ---------- Previous post was at 10:57 PM ----------
Mentalmuso said:
What version of Android are you on?
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
im on pie T835NKOU2BSD1
wallyhenderson said:
it is mandatory to flash a custom kernel? will do if nessesary... i didnt... and didnt flashed magisk
---------- Post added at 11:05 PM ---------- Previous post was at 10:57 PM ----------
im on pie T835NKOU2BSD1
Click to expand...
Click to collapse
Kernel - pre rooted should boot. https://nextcloud.justbeca.us/s/JMgdcpt6kxdwNzo
Sent from my SM-T830 using Tapatalk
What are the steps for flashing the twrp 3.3.0 img via an existing twrp install?
hpc305 said:
What are the steps for flashing the twrp 3.3.0 img via an existing twrp install?
Click to expand...
Click to collapse
install - img - select the img file - select recovery
Sent from my SM-N9600 using Tapatalk
Encryption Disabler was broken
Updated to V2, please use this or there will be problems.
See post #2 for downloads.
--->
Mentalmuso said:
You can flash TWRP two ways, either directly from an existing TWRP install, using the linked TWRP.img file. Or you can flash using Odin and the TWRP.tar file.
You will need a custom kernel with dm-verity disabled to be able to boot up afterwards. You will also need to disable encryption and format data to be able to read from the sdcard (encryption isn't supported).
The flashing process is as follows.
Get yourself onto stock Pie firmware, using Odin to flash the complete package. Before proceeding. Boot up and make sure you have OEM unlock switch and its activated.
1. Boot into Download mode and Flash TWRP (Download) using Odin
2. Immediately boot into TWRP after flashing takes place, hold vol up and power.
3. Format data partition (wipe/format data)
4. Reboot recovery
5. Copy Encryption disabler and WETA_Kernel or WETA_Rom to device - (Download Enryption disabler) (Download WETA_Kernel)
6. Flash Encryption disabler, Flash WETA_Kernel or WETA_Rom
7. Boot up system, if it hangs on Samsung logo after 3min perform hard reboot.
8. Connect to internet and go to dev settings and cheeck oem unlock is present before any rebooting.
**Custom kernel is pre-rooted with magisk.
**You will need to manually install magisk manager app.
--->
Click to expand...
Click to collapse
Some things to note:
0. Requirements are:
USB Cable (Samsung Tab S4 default cable recommended)
A computer where Odin works (ie. my AM4 X370 Ryzen 7 system did not work, maybe some driver issue?)
Best is to put encryption disabler & Kernel onto the micro SD card in the Tab S4 already, you can flash from SD card in TWRP!
1. Flash TWRP in AP slot - beware if you did not untick Auto Reboot, it will immediately restart and you miss 2.
2. Hold those buttons before the vibration kicks in, otherwise you are too late
4. I couldn't do that from TWRP itself for some reason (it just shut off), but button combo worked perfectly
5. [Edit] Do that before hand, I recommend the micro SD card you can put into the Tab S4
6. I flashed encryption disabler (V2) first, then you have to flash the kernel image, flash it to BOOT!
7. Don't just wait 3 min, my Tablet booted after 10 min without issue! I had this before aswell, you just need to give it more time!
Question: Can I update Magisk with this?
neuer31 said:
Some things to note:
0. Requirements are:
USB Cable (Samsung Tab S4 default cable recommended)
A computer where Odin works (ie. my AM4 X370 Ryzen 7 system did not work, maybe some driver issue?)
Best is to put encryption disabler & Kernel onto the micro SD card in the Tab S4 already, you can flash from SD card in TWRP!
1. Flash TWRP in AP slot - beware if you did not untick Auto Reboot, it will immediately restart and you miss 2.
2. Hold those buttons before the vibration kicks in, otherwise you are too late
4. I couldn't do that from TWRP itself for some reason (it just shut off), but button combo worked perfectly
6. I flashed encryption disabler (V2) first, then you have to flash the kernel image, flash it to BOOT!
7. Don't just wait 3 min, my Tablet booted after 10 min without issue! I had this before aswell, you just need to give it more time!
Question: Can I update Magisk with this?
Click to expand...
Click to collapse
Yeah flashing magisk should be fine once your data partition is unencrypted.
Sent from my SM-N9600 using Tapatalk
Mentalmuso said:
install - img - select the img file - select recovery
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
F###, thanks, bro.
Just flashed it as recovery and have this now.
Can you delete this suggestion? It should be flashed as Boot, GOD!

Categories

Resources