Hi, I am new to this forum but old on android. My oneplus 3t brick yesterday and i don't know why. I never rooted phone and always update phone via OTA. I contacted Oneplus support yesterday and they arrange a remote session where they are unable to install anything via msmdownload tool. I download msmdownload tool yesterday from this forum and my phone works but there is no modem in it. I am unable to connect to wifi and SIM internet. Oxygen OS version install at the moment is 3.5.1 and android version is 6.0.1. Need help from some seniors.
Update by using on the of the official "full zips"? These include the modem, so I would think that would fix the problem, unless there is a more serious issue (hardware failure, etc.):
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
redpoint73 said:
Update by using on the of the official "full zips"? These include the modem, so I would think that would fix the problem, unless there is a more serious issue (hardware failure, etc.):
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
I tried multiple time but device stuck in boot loop. Downloaded ROM from Oneplus official site.
xusmanmalik said:
I tried multiple time but device stuck in boot loop. Downloaded ROM from Oneplus official site.
Click to expand...
Click to collapse
The full zip or the OTA?
Is your phone rooted/TWRP installed, or is it stock?
redpoint73 said:
The full zip or the OTA?
Is your phone rooted/TWRP installed, or is it stock?
Click to expand...
Click to collapse
Phone is stock not rooted. When i upgrade locally or through adb process phone stuck in bootloop.
xusmanmalik said:
Phone is stock not rooted. When i upgrade locally or through adb process phone stuck in bootloop.
Click to expand...
Click to collapse
Now i updated from 3.5.1 to 3.5.4 but issue still exist
xusmanmalik said:
Now i updated from 3.5.1 to 3.5.4 but issue still exist
Click to expand...
Click to collapse
Upgrading from 3.5.4 to 4.0.2 phone again stuck at boot screen. I don't know what to do know. Should i go for warranty claim or try something else. Need HELP!!!!
Thanks in Advance.
Are you able to go to fastboot mode? If yes, go for it:
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Install TWRP too. Now you're able to wipe everything and upload a full ROM to your device (Thanks to MTP-mode via TWRP, so handy!). Flash the full ROM and have a try .
MickyFoley said:
Are you able to go to fastboot mode? If yes, go for it:
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Install TWRP too. Now you're able to wipe everything and upload a full ROM to your device (Thanks to MTP-mode via TWRP, so handy!). Flash the full ROM and have a try .
Click to expand...
Click to collapse
Micky Thanks for the help. I will give a try and will inform further.
I ****ed up somewhere. Encryption unsuccessful Error.
xusmanmalik said:
I ****ed up somewhere. Encryption unsuccessful Error.
Click to expand...
Click to collapse
Do you have TWRP installed? Just wipe your phone, get an otg cable and a flash drive, you can flash everything from the flash drive
I revert back trying again now.
xusmanmalik said:
Micky Thanks for the help. I will give a try and will inform further.
Click to expand...
Click to collapse
Hi Micky Foley, I successfully followed all steps and now i am on twrp and su installed.
But still i am unable to install other ROM than 3.5.*
Your last option is the warranty then mate
Related
I was trying to fix my google play "no connection error" but it didn't work so i just reset my phone as a last resort to try and fix this problem. It restarted in recovery mode i thought this was just a procedure and i just hit reboot -> system. it rebooted again into recovery mode i checked if there were any wtuck volume rockers but there aren't any help?
(FYI: one plus 3T: Rooted)
(FYI: link to what i used to try and fix my google play store:https: //forum.xda-developers.com/showthread.php?t=2273994)
What recovery are you running? Stock or TWRP?
bealer said:
What recovery are you running? Stock or TWRP?
Click to expand...
Click to collapse
TWRP
And telling TWRP to boot system just bring you back into TWRP?
Hmm... sounds like you might need to reflash whatever rom you were on.
bealer said:
And telling TWRP to boot system just bring you back into TWRP?
Hmm... sounds like you might need to reflash whatever rom you were on.
Click to expand...
Click to collapse
already did that but still brings me back into TWRP
TrappleV3 said:
already did that but still brings me back into TWRP
Click to expand...
Click to collapse
This happened to me. I installed custom rom then I went into fastboot and installed stock recovery. I would search in this forum for the stock recovery img file. Once installed, I rebooted and it loaded the rom. I had this problem on the latest twrp version. I installed the previous twrp and I am all good now.
Droid-2 said:
This happened to me. I installed custom rom then I went into fastboot and installed stock recovery. I would search in this forum for the stock recovery img file. Once installed, I rebooted and it loaded the rom. I had this problem on the latest twrp version. I installed the previous twrp and I am all good now.
Click to expand...
Click to collapse
you have a link to the file because i can't seem to find it. But thank you anyway for your help.
TrappleV3 said:
you have a link to the file because i can't seem to find it. But thank you anyway for your help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
mximer said:
https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
Click to expand...
Click to collapse
Thank You.
Issue has been resolved. OP is my little cousin who's been messing around a bit too frantically [emoji14]
I restored his device with the unbrick tool by Haris K., all's peachy again. There are still some issues with TWRP for 3T, doesn't run nearly as smooth as on the OPO. It completely failed to restore any working system (both from backup or from reflashing). Sideloading seemingly worked, but rebooted to recovery again, adb push only resulted in errors. Are there any tweaked TWRP releases that can do better?
Cooked with Resurrected bacon!
Hello lovely XDA-members,
this morning a new OTA update/patch came out for my OnePlus 3T, so I downloaded and tryed to install it right away. My phone is rooted on android 7.0 and I have TWRP 3.0.3-0 installed as my recovery. Normally (when I updated to nougat) after downloading a new update the phone reboots itself into TWRP and installs the update by itself, but not this time. I had to seqrch through my phone and had to install thw update manually. After that I rebooted the phone and it started booting the TWRP recovery again, I tried it again and again and again, nothint changed. So I tried to restore my backup with everything functioning, but this wouldnt help either. :/ I read the few existing threads with this problem and heard of a recovery flag that isnt cleared and the bootloader being the problem. One solution that I found was only for an LG phone and I'm afraid that I'll brick my brand new phone I have absolutely no idea what to do now, I would be so happy if someone could help me with this :$
I thank you in advance <3
Encoutered the same problem. Either you reflash the official or twrp recovery (neither did the trick to me) or use this "emergency tool" (which helped me):
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
Btw: TWRP 3.0.3-0 is not working well, switch to 3.0.3-1 beta
Good luck to you
I had the same problem.
How you can ''unbrick it'':
1. Flash a any rom available for the oneplus 3t via twrp
a. after this you will be still in twrp bootloop, to solve this go to step 2
2. Flash back stock recovery via twrp
Now your system will boot again
Optional: Flash back twrp
Just flash stock recovery via adb and you're done. It will fix the problem, you won't lose any data
Isus <3 said:
Just flash stock recovery via adb and you're done. It will fix the problem, you won't lose any data
Click to expand...
Click to collapse
@Isus <3 and @koentdm Do you have a download for the stock recovery, cause the oneplus download-site isnt working and I cant find any other downloads for it
EYT said:
@Isus <3 and @koentdm Do you have a download for the stock recovery, cause the oneplus download-site isnt working and I cant find any other downloads for it
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B0pr-ZA5b-1pNVlxV3ljMUFaUHc/view
Thank you so much, it worked
EYT said:
Thank you so much, it worked
Click to expand...
Click to collapse
No problemos my friendos
My OnePlus 3T is freezing. I've tried wiping it, fastboot erasing/formatting and custom ROMs/stock. Is my unit defective? I've had it since release with a glass screen protector and tudia case. What will happen if I ask for a replacement? How quickly will they replace it or repair it?
Thanks!
woundman said:
My OnePlus 3T is freezing. I've tried wiping it, fastboot erasing/formatting and custom ROMs/stock. Is my unit defective? I've had it since release with a glass screen protector and tudia case. What will happen if I ask for a replacement? How quickly will they replace it or repair it?
Thanks!
Click to expand...
Click to collapse
Try sideload of stock rom with stock recovery.
Sent from my Funk Tuned 3T
Funk Wizard said:
Try sideload of stock rom with stock recovery.
Sent from my Funk Tuned 3T
Click to expand...
Click to collapse
Will try now. Just clean flashed stock ROM and phone won't boot now.
Edit: Can't seem to get ADB to function. Only fastboot works. Does it matter?
woundman said:
Will try now. Just clean flashed stock ROM and phone won't boot now.
Edit: Can't seem to get ADB to function. Only fastboot works. Does it matter?
Click to expand...
Click to collapse
Check the ADB drivers, ABD has to work in order to sideload.
Funk Wizard said:
Check the ADB drivers, ABD has to work in order to sideload.
Click to expand...
Click to collapse
Sorry, I'm pretty tired. Sideloading fails with stock recovery for some reason. Error is: "Installation Failed".
Edit: Figured it out. Rebooted PC and phone, then it worked. Time to see if it still crashes.
Funk Wizard said:
Check the ADB drivers, ABD has to work in order to sideload.
Click to expand...
Click to collapse
I successfully sideloaded the stock ROM / recovery, but the phone won't fully boot. The phone goes black or shuts down after it's about to start the initial setup phase. Is there anything else I should try? I've contacted support and they want to remote flash the device on the 24th...
I would recommend you to follow the unbrick guide which restores your phone to factory state, and then try again to update to 4.1.3.
https://forum.xda-developers.com/showthread.php?t=3515306
woundman said:
I successfully sideloaded the stock ROM / recovery, but the phone won't fully boot. The phone goes black or shuts down after it's about to start the initial setup phase. Is there anything else I should try? I've contacted support and they want to remote flash the device on the 24th...
Click to expand...
Click to collapse
Try the unbrick guide as said above
Sent from my Funk Tuned 3T
pitrus- said:
I would recommend you to follow the unbrick guide which restores your phone to factory state, and then try again to update to 4.1.3.
https://forum.xda-developers.com/showthread.php?t=3515306
Click to expand...
Click to collapse
Funk Wizard said:
Try the unbrick guide as said above
Sent from my Funk Tuned 3T
Click to expand...
Click to collapse
So I followed the unbrick tool and everything worked great flashing back to 3.5.4. However, once I sideloaded to 4.1.3, the phone freezes nonstop. I had to manually restart the phone just to get to the initalize setup screen, but now the phone is completely frozen. Why is 3.5.4 working fine, but 4.1.3 crashing? Is my 4.1.3 corrupt or something? I'm really confused.
I left OOS around 4.0.1 and has been using LOS 14.1 instead, but from what I've heard from those still using OOS, 4.1.3 of it should work just fine.
pitrus- said:
I left OOS around 4.0.1 and has been using LOS 14.1 instead, but from what I've heard from those still using OOS, 4.1.3 of it should work just fine.
Click to expand...
Click to collapse
So, you think the phone is defective? I'm really confused why 3.5.4 worked fine, but flashing stock 4.1.3 causes the phone to crash.
woundman said:
So, you think the phone is defective? I'm really confused why 3.5.4 worked fine, but flashing stock 4.1.3 causes the phone to crash.
Click to expand...
Click to collapse
Just unbricked the device again and sideloaded the latest OxygenOS update. Phone froze while typing in wifi password during setup. Think it's safe to say it's defective? I've tried everything.
woundman said:
So I followed the unbrick tool and everything worked great flashing back to 3.5.4. However, once I sideloaded to 4.1.3, the phone freezes nonstop. I had to manually restart the phone just to get to the initalize setup screen, but now the phone is completely frozen. Why is 3.5.4 working fine, but 4.1.3 crashing? Is my 4.1.3 corrupt or something? I'm really confused.
Click to expand...
Click to collapse
May be a bad download, you don't have to sideload.
Just flash the new recovery and install via internal from stock recovery or you can also ways flash full zip via twrp
Sent from my OnePlus 3T using XDA Labs
Funk Wizard said:
May be a bad download, you don't have to sideload.
Just flash the new recovery and install via internal from stock recovery or you can also ways flash full zip via twrp
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I've tried downloading the file multiple times, still freezes every time for some reason. I'll try installing from internal and see if that helps. After that, I think I'm gonna give up.
woundman said:
I've tried downloading the file multiple times, still freezes every time for some reason. I'll try installing from internal and see if that helps. After that, I think I'm gonna give up.
Click to expand...
Click to collapse
Install from internal and install Beta its much better
Sent from Funk Tuned 3T
woundman said:
I've tried downloading the file multiple times, still freezes every time for some reason. I'll try installing from internal and see if that helps. After that, I think I'm gonna give up.
Click to expand...
Click to collapse
did you try installing 3.5.4 then using the OTA updates to update to the latest version?
nhshah7 said:
did you try installing 3.5.4 then using the OTA updates to update to the latest version?
Click to expand...
Click to collapse
Just reran the unbricking tool and now it's freezing on 3.5.4. Phone is defective, returning it.
Hey guys,
My younger brother had TWRP installed on his OP3. Yesterday he applied OTA and his phone got bricked. I unbricked it from MSMtool method (Qualcom Driver). It got unbricked and i have stock rom now however phone is stuck at android is upgrading (45 minutes). I tried restarting it and now it is in boot loop. i tried to flash latest OxygenOS from adb sideload and it got bricked again. Can anyone tell me what to do now or what is wrong with the device.
abdullah.ahsan11 said:
Hey guys,
My younger brother had TWRP installed on his OP3. Yesterday he applied OTA and his phone got bricked. I unbricked it from MSMtool method (Qualcom Driver). It got unbricked and i have stock rom now however phone is stuck at android is upgrading (45 minutes). I tried restarting it and now it is in boot loop. i tried to flash latest OxygenOS from adb sideload and it got bricked again. Can anyone tell me what to do now or what is wrong with the device.
Click to expand...
Click to collapse
You have TWRP installed? Use Method 2 of the unbrick guide. Now you want to wipe every partition then adb push your rom (not sideload) and manually flash it. Make sure you are on the latest Bluspark twrp.
Puddi_Puddin said:
You have TWRP installed? Use Method 2 of the unbrick guide. Now you want to wipe every partition then adb push your rom (not sideload) and manually flash it. Make sure you are on the latest Bluspark twrp.
Click to expand...
Click to collapse
I am using method 2, the OS gets stuck on bootloop that's why i tried to sideload later
I don't have a working recovery, all i can get is stock recovery, how can i install twrp?
I've tried flashing (fastboot flash recovery recovery.img) it but it is not working
abdullah.ahsan11 said:
I am using method 2, the OS gets stuck on bootloop that's why i tried to sideload later
I don't have a working recovery, all i can get is stock recovery, how can i install twrp?
I've tried flashing (fastboot flash recovery recovery.img) it but it is not working
Click to expand...
Click to collapse
Why is it not working? Does it give an error or something?
Puddi_Puddin said:
Why is it not working? Does it give an error or something?
Click to expand...
Click to collapse
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.
abdullah.ahsan11 said:
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.
Click to expand...
Click to collapse
Nah, In windows, go to Device Manager. How does your device show up? It has to do with wrong drivers.
Puddi_Puddin said:
Nah, In windows, go to Device Manager. How does your device show up? It has to do with wrong drivers.
Click to expand...
Click to collapse
Yes It shows up correctly.
abdullah.ahsan11 said:
Yes It shows up correctly.
Click to expand...
Click to collapse
What is correctly? What does it say? You might want to try different ADB drivers. You should be able to always flash In fastboot..
abdullah.ahsan11 said:
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.
Click to expand...
Click to collapse
Check again the bootloader to be unlocked. Use the tool for that, is it on OP3 forum, then retry to get a stock rom up before anything else (TWRP, custom rom, etc)
Sent from my OnePlus3 using XDA Labs
follow this instruction -
1- go into twrp and wipe everything even internal and formate it .
2- unistall all adb driver and oneplus driver also .. then clean tmp file from window
3rd- install latest adb+ oneplus 3 driver ..again restrat ..
4th-boot in fastboot mod and lock your bootloader
5th-flast latest build of oxygen stock recovery from fastboot
6th than again wipe or factory reset the device via stock recovery
7th open stock recoery than flash latest build of oxygen os via sideload
8th reboot the device and setup quikly
9th-unlock bootloader, flash bluespark recovery , flash rom, flash supersu ..
10th play with device
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/rosemary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
OK nevermind I successfully got the phone booting again with miflash tool by reflashing an official firmware...
Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/t/twrp-on-android-12.4522273/), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Click to expand...
Click to collapse
Hope it helps! ; D
dona3000 said:
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/ros mary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
Click to expand...
Click to collapse
Did u make sure ur on Miui 12.5.16.0.RKLMIXM?
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
fol!s said:
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
Click to expand...
Click to collapse
Greetings!
As this phone has an MTK processor, we don't really have a recovery image, it's stored in the boot img I suppose. That link, you can download the official rom to this. DISCLAIMER: There are two types of ROMs listed here, one type is fastboot, that you need now in order to flash it through a computer for example. The another type is the recovery rom, that you can flash from recovery like a magisk package, or anything flashable zip, or with adb sideload.
https://mifirm.net
You should choose global if you are in Europe, but it's suitable for devices in the US or USA probably, ony feature differences are here between an EEA and Global rom.
Also, if you install pixel experience recovery, you can install the firmware by going into recovery, and do it via sideload. Or, you can try flashing the rom with TWRP (tutorial linked below), but then you won't able to install updates automatically.
One question: Did you checked in OEM unlocking in developer options before flashed PE?
Hope it helps!
Yeah, I did checked the oem unlocking. I think the reason why i failed because my bootloader probably updated and I forgot to check. You need bootloader version 12.5.16.0.RKLMIXM to install the pixel experience. Also thank for help
Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/members/gurtnyi.11842195), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Hope it helps! ; D
Click to expand...
Click to collapse
Can I do that on newer firmware or should I roll back to version 12.5.16.0.RKLMIXM? And if I roll back then I need to unlock device again?
I think you can. I've flashed it successfully on the latest version too. Currently I don't use PE but it was good for me.
Well, regarding to the unlock, it's not a big deal, you don't have to wait 168h again, once you've firstly unlocked your device, you can re-unlock it again, and again, no matter how many times, you don't have to wait a lot again.
But depending on how you rollback it,
I mean, with xiaomi flasher (i think that's its name) you can choose between clean all and lock, save userdata, and clean all, but in the first case, it'll lock back the bootloader. With SP flash tool (if you need, I can provide a link for the modified version of it, that doesn't require an auth file, but if fails, you need a python script, I can link that too), as I remember it won't lock back the device, but I'm not a 100% sure
Hope it helps!
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
raven17a said:
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
Click to expand...
Click to collapse
Corrected, thank you!
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
raven17a said:
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
Click to expand...
Click to collapse
Happy to hear that!
By the way, yes, pe recovery is better for sideloading, or eventually any not stock recovery. Also, if you install PE recovery, you can apply updates automatically, and in the future you won't need to flash it manually.