Related
i updated my rooted n unlocked boot-loader motog2 2014 n it was not updating just restarting so i went in twrp n fixed permissions n though it stopped starting even then everything got messed wiped to restore but noting happened now stuck on bootloader mode just can go in twrp recovery tried to go stocck by computer but says no driver plz help what do i do now. plzz :crying:
INSTALL MOTOROLA device manager 2.5.4 from motorola website for fastboot drivers you can find easy installer of full rom for xt1068 (if you have this model) in my signature download to pc unzip and read instructions inside
reefuge said:
INSTALL MOTOROLA device manager 2.5.4 from motorola website for fastboot drivers you can find easy installer of full rom for xt1068 (if you have this model) in my signature download to pc unzip and read instructions inside
Click to expand...
Click to collapse
i have drivers but doesnt detect drivers on phone when i fastboot devices some no. comes but no other process happens if we do so what do i do then?
gurjeet saini said:
i have drivers but doesnt detect drivers on phone when i fastboot devices some no. comes but no other process happens if we do so what do i do then?
Click to expand...
Click to collapse
have you a xt1068 ? if so use links in my signature and read instructions if not tell me you xt106x model and i will see what i can help, can you get phone to ap fastboot mode (boot loader)
unlocked bootloader is not the problem its the root that caused problem, did you not make a backup via twrp you can restore?
or heres a TWRP backup Clean TWRP back up of LXB22.99-16.3 - lollipop 5.0.2 stage fright fixed for XT1068 only (DUAL SIM)
save above zip on sd card inside TWRP>backup>xxx123xxx (this is your fone id will be different)
reefuge said:
have you a xt1068 ? if so use links in my signature and read instructions if not tell me you xt106x model and i will see what i can help, can you get phone to ap fastboot mode (boot loader)
unlocked bootloader is not the problem its the root that caused problem, did you not make a backup via twrp you can restore?
or heres a TWRP backup Clean TWRP back up of LXB22.99-16.3 - lollipop 5.0.2 stage fright fixed for XT1068 only (DUAL SIM)
save above zip on sd card inside TWRP>backup>xxx123xxx (this is your fone id will be different)
Click to expand...
Click to collapse
can i just put it in external sd card cauz in computer it does not shows internal storage.???
gurjeet saini said:
can i just put it in external sd card cauz in computer it does not shows internal storage.???
Click to expand...
Click to collapse
yes when you restore from twrp just switch restore location to restore from external sd card
reefuge said:
yes when you restore from twrp just switch restore location to restore from external sd card
Click to expand...
Click to collapse
sir it did not happened i did as u told now what do i do
:crying:
gurjeet saini said:
sir it did not happened i did as u told now what do i do
:crying:
Click to expand...
Click to collapse
try downloading to pc full rom number 3) in my blue signature link 5.0.2
download to pc unzip and read instruction
install both mdm 2.5.4.exe AGAIN
and ADB v1.31
then follow instruction in folder
reefuge said:
have you a xt1068 ? if so use links in my signature and read instructions if not tell me you xt106x model and i will see what i can help, can you get phone to ap fastboot mode (boot loader)
unlocked bootloader is not the problem its the root that caused problem, did you not make a backup via twrp you can restore?
or heres a TWRP backup Clean TWRP back up of LXB22.99-16.3 - lollipop 5.0.2 stage fright fixed for XT1068 only (DUAL SIM)
save above zip on sd card inside TWRP>backup>xxx123xxx (this is your fone id will be different)
Click to expand...
Click to collapse
hi..i need a little help after updating to latest 5.0.2 ...used about phone to download n flashed stock recovery backup wid flashify n den unrooted n updated...n den flashed twrp after update..so..if i in future restore d stock recovery i just restored before update..it will wrk??if not..can u give me d backup of latest stock recovery compatible wid latest 5.0.2 26 aug ...indian one..one more ques..falcon got 5.11..my cousin has dat..but y didnt we??
Naman rana said:
hi..i need a little help after updating to latest 5.0.2 ...used about phone to download n flashed stock recovery backup wid flashify n den unrooted n updated...n den flashed twrp after update..so..if i in future restore d stock recovery i just restored before update..it will wrk??if not..can u give me d backup of latest stock recovery compatible wid latest 5.0.2 26 aug ...indian one..one more ques..falcon got 5.11..my cousin has dat..but y didnt we??
Click to expand...
Click to collapse
stock recover for lxb22.99-16.3 see post #2
to install future ota updates you need to unroot and have stock recovery (they will download but not install and or cause a bootloop)
falcon got 5.1.1 as its gen 1 we are gen 2 and still waiting - not fair - but how motorola does it (to try to sell more gen 3)
reefuge said:
stock recover for lxb22.99-16.3 see post #2
to install future ota updates you need to unroot and have stock recovery (they will download but not install and or cause a bootloop)
falcon got 5.1.1 as its gen 1 we are gen 2 and still waiting - not fair - but how motorola does it (to try to sell more gen 3)
Click to expand...
Click to collapse
this what cauz the problem to my device i updated my rooted moto g2 n it was just crazy n was restarting n went to twrp it self didnt knew what to do
gurjeet saini said:
this what cauz the problem to my device i updated my rooted moto g2 n it was just crazy n was restarting n went to twrp it self didnt knew what to do
Click to expand...
Click to collapse
reefuge sir lots of love n tons of thank u.. you are sheer genius helped me alot now my phone works fine just one thing to ask now phone bootloader is locked? n unrooted so now it shows update can i update the phone?
gurjeet saini said:
reefuge sir lots of love n tons of thank u.. you are sheer genius helped me alot now my phone works fine just one thing to ask now phone bootloader is locked? n unrooted so now it
shows update can i update the phone?
Click to expand...
Click to collapse
bootloader unlocked is only needed to install twrp - you will get ota updates with locked or unlocked bootloader and they will install if locked or unlocked
its only rooting that causes bootloops and of course you need stock recovery to install - so yes just install updates without worry
reefuge said:
bootloader unlocked is only needed to install twrp - you will get ota updates with locked or unlocked bootloader and they will install if locked or unlocked
its only rooting that causes bootloops and of course you need stock recovery to install - so yes just install updates without worry
Click to expand...
Click to collapse
is it now necessary to install twrp now. ? before update sir. n i have other moto g2 which is rooted how do i unroot it n update it it will be normal update?
gurjeet saini said:
is it now necessary to install twrp now. ? before update sir. n i have other moto g2 which is rooted how do i unroot it n update it it will be normal update?
Click to expand...
Click to collapse
no updates only work with stock recovery you need stock rom and stock recovery - NO TWRP
to unroot I always flash full stock rom ( no. (3) in my signature link blue
reefuge said:
no updates only work with stock recovery you need stock rom and stock recovery - NO TWRP
to unroot I always flash full stock rom ( no. (3) in my signature link blue
Click to expand...
Click to collapse
thank u reefuge sir
u are just n:angel:
Which current version of android do u guys have?
I have moto g (2014) 2nd gen [XT-1068 model] and Android 5.0.2 on it. When I go to system updates it shows:
"New system software avaliable!"
New version: 22.56.3.en.DE
When I try to update it stops on halfway it after boot I get the message something like: Software update unsuccessful no changes were made."
Yes, my device is rooted via KingRoot and interesting is that when I try to find updates via USB cable and Motorola device manager. Device Manager says that there are no updates found. *WHAT?*
I managed to remove root permission (unroot) but the update always fail.
hrc3000 said:
Which current version of android do u guys have?
I have moto g (2014) 2nd gen [XT-1068 model] and Android 5.0.2 on it. When I go to system updates it shows:
"New system software avaliable!"
New version: 22.56.3.en.DE
When I try to update it stops on halfway it after boot I get the message something like: Software update unsuccessful no changes were made."
Yes, my device is rooted via KingRoot and interesting is that when I try to find updates via USB cable and Motorola device manager. Device Manager says that there are no updates found. *WHAT?*
I managed to remove root permission (unroot) but the update always fail.
Click to expand...
Click to collapse
Don't use kingroot. It's a risky method and nobody really knows what it does (except searching for exploits). It may change things in your system that are not reversible.
To root the Moto G 2014 unlock bl, flash twrp and then flash latest superSU or use chainfires autoroot. These are the only solid methods.
Sent with somewhat
Wolfcity said:
Don't use kingroot. It's a risky method and nobody really knows what it does (except searching for exploits). It may change things in your system that are not reversible.
To root the Moto G 2014 unlock bl, flash twrp and then flash latest superSU or use chainfires autoroot. These are the only solid methods.
Sent with somewhat
Click to expand...
Click to collapse
But, umm how can I update to latest android or should I say, am I able to uptade it on higher version than 5.0.2?
you can try it with this tool
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
I have the same issue. I have downloaded update and and let it install. when it reboot to install the update it reboot in to twrp and gives an error in the log; after I normally reboot through twrp the phone turn up and after a while it reboot in to twrp show to fix this?
if you use ota update(stock-rom) you need STOCK RECOVERY.
twrp doesn't work because its a custom recovery
Gesendet von meinem Moto G 2014
Same problem here. Moto G 2014 XT1068, rooted and no twrp. The update in recovery makes it till halfway, then it shows an error and Andy with a red exclamation mark and the phone reboots. After that, MOTOROLA OTA shows a message that something went wrong and no change has been made.
Got the update message, let it install without knowing it would brick with TWRP.
Now I got a automatic boot into TRWP, I choose reboot to system, it goes pass the lock screen and then.... automatically reboots into TRWP again. I'm in a loop, what do to? Would like some help please. Would a wipe as a last resort solve this problem?
update: I decided to restore a rom backup using TWRP, no more official updates for me unless there's another way of doing it correctly.
What a joke... 3 months to release a security update... Android 6 only next year... Update fails apparently because the phone is rooted... Thank god nexus 5x has come out, bye bye motorola
unroot your phone and make sure that you are using stock recovery.
I did exactly the same mistake today.
My solution was to flash SuperSU in recovery, delete cache and dalvik and reboot the phone. The phone reverted the update and everything looks fine for now. Now it prompts me again for the ota update.
RobaL4 said:
I did exactly the same mistake today.
My solution was to flash SuperSU in recovery, delete cache and dalvik and reboot the phone. The phone reverted the update and everything looks fine for now. Now it prompts me again for the ota update.
Click to expand...
Click to collapse
You could use the SuperSU app and do a full unroot using the app, do the update and reflash SuperSU.
Sent from my SM-T530NU using Tapatalk
daywalk3r666 said:
if you use ota update(stock-rom) you need STOCK RECOVERY.
twrp doesn't work because its a custom recovery
Gesendet von meinem Moto G 2014
Click to expand...
Click to collapse
Will it be different if I try to install it via motorola update manager in PC?
How do I go back to stock recovery?
no its the same.
you must flash the stock firmware for your device
Tel864 said:
You could use the SuperSU app and do a full unroot using the app, do the update and reflash SuperSU.
Sent from my SM-T530NU using Tapatalk
Click to expand...
Click to collapse
And this way you don't need to flash a stock recovery?!
svendsvin said:
And this way you don't need to flash a stock recovery?!
Click to expand...
Click to collapse
No, that's only if you have rooted stock. If you're on a custom recovery you'll need to flash stock.
But I do have custom recovery I have only rooted it with KingRoot.
So if I want OTA update I have to do this:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
EDIT: Bruh it's works as a charm. I've flashed stock rom and OTA update passed.
Thnx guys.
I received the notification OTA update for stagefright patch few days ago, I downloaded, but when the device reboots the installation fails. The system version is: 22.21.28.titan_retaildsds.retaildsdsall.en.03 reteu. The build number is LXB 22.46.28. I had a chat with a Motorola techcinian two days ago and he informed me that my phone is rooted and that’s is the reason that I cannot get the update.!!! This is really strange, because I NEVER try to unlock the bootloader. My phone is not rooted . The indication in fastboot mode shows 0.
kompostas said:
I received the notification OTA update for stagefright patch few days ago, I downloaded, but when the device reboots the installation fails. The system version is: 22.21.28.titan_retaildsds.retaildsdsall.en.03 reteu. The build number is LXB 22.46.28. I had a chat with a Motorola techcinian two days ago and he informed me that my phone is rooted and that’s is the reason that I cannot get the update.!!! This is really strange, because I NEVER try to unlock the bootloader. My phone is not rooted . The indication in fastboot mode shows 0.
Click to expand...
Click to collapse
Just do what i did. From previous post.
Question: OP, did you UNROOT the device and then flash the update via fastboot, or not?
And, one more thing: Did it wipe everything on your phone? I read the readme file and it says that it does not, but I find it strange to flash the rom from scrath and keep your files, apps etc untouched.
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
It is stock, updated to lollipop 6.0. I got the adb stuff on my pc to run cmds. All I want to do is root it for now. Every search I keep finding is not XT1064(other models show) or if it is, its not on lollipop or it is but not 6.0. I can't seem to find any for XT1064 already running on lollipop 6.0 that just simply needs to be rooted, no custom rom.
TWRP
Just flash by the bootloader the most recent version of TWRP (search for TWRP titan). And then, flash the latest SuperSU on TWRP recovery (search for SuperSU Beta).
Hope i've helped
blades_of_honor said:
It is stock, updated to lollipop 6.0. I got the adb stuff on my pc to run cmds. All I want to do is root it for now. Every search I keep finding is not XT1064(other models show) or if it is, its not on lollipop or it is but not 6.0. I can't seem to find any for XT1064 already running on lollipop 6.0 that just simply needs to be rooted, no custom rom.
Click to expand...
Click to collapse
XPS3Johann said:
Just flash by the bootloader the most recent version of TWRP (search for TWRP titan). And then, flash the latest SuperSU on TWRP recovery (search for SuperSU Beta).
Hope i've helped
Click to expand...
Click to collapse
Latest TWRP recovery for titan: twrp-3.0.2-4-titan.img https://dl.twrp.me/titan/twrp-3.0.2-4-titan.img.html
Latest stable superSU:SuperSU-v2.79-201612051815 https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
You have to flash SuperSU beta otherwise you'll be in a bootloop.
nilanko said:
You have to flash SuperSU beta otherwise you'll be in a bootloop.
Click to expand...
Click to collapse
Thanks, I tried flashing the latest stable supersu (2.79) and no luck. I flashed sr3 supersu and it worked so thanks
Thank you all! Finally got around to doing it. I used the beta SU as nilanko suggested. I ran a backup before trying SU(thank god I didn't forget!). I was stuck on the bootloader unlocked warning after doing it. At first I though maybe it just takes awhile the first time. So I went out for a smoke. Came back & it was still on the bootloader unlock warning screen still. I ran a restore through twrp & rebooted. Booted up fine now. I am wondering what happened exactly.
Only things I can think of is
A)The SU file was corrupted(something in it didn't download right when I downloaded it off my computer)
B)I put the SU file in the internal memory, not on the SD card. I thought it doesn't matter as long as you had the space on either.
SR3-SuperSU-v2.79-SR3-20170114223742 worked!:good:
Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance
First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
Yiannis75 said:
i flashed the TWRP Recovery and flashed the SuperSU zip
Click to expand...
Click to collapse
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
Yiannis75 said:
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still
Click to expand...
Click to collapse
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.
Yiannis75 said:
Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance
Click to expand...
Click to collapse
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot
Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
Click to expand...
Click to collapse
You can verify by booting to TWRP. It says version number on the splash screen.
Did you look at, or try my recommendations in my last response?
redpoint73 said:
First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.
Click to expand...
Click to collapse
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse) ...thanks in advance
Yiannis75 said:
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Click to expand...
Click to collapse
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
Yiannis75 said:
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
Click to expand...
Click to collapse
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
Yiannis75 said:
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
Click to expand...
Click to collapse
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Yiannis75 said:
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse)
Click to expand...
Click to collapse
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!
Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot
Click to expand...
Click to collapse
Inta mou laleis??
Coming to Cyprus soon bro!
About your issue, use TWRP bluespark 8.61, just to be sure.
Never had issues with this version.
Unleashed by my rooted OP3T on 8.0
redpoint73 said:
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!
Click to expand...
Click to collapse
So, got home fixed the drivers so that my pc could recognize my device while on TWRP recovery, flashed the zip file through TWRP and it worked like a charm
Thanks for all the help bro
Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
mannulko said:
Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
just like me, if u flash oos 5.0.2 from twrp u will be just fine. Just flash magisk instead of supersu like i did and all will be working just fine
mannulko said:
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
If posting on a thread, related to your issue; it would make sense to actually read the responses in the thread. Since your question is already answered.
In short, you need to use SuperSU 2.82 SR5. The "stable" version 2.82 won't work, and will result in no boot. Or use Magisk 16.0.
If the phone still won't boot after (only) flashing the proper version SuperSU or Magisk; then flash the full stock update file using TWRP. Then flash the right version SuperSU or Magisk.