Hi,
I've been running Oxygen OS 3.2.8, rooted, with TWRP fine for a bit. I had downgraded from Oxygen OS Community Beta 9, by using the Full Unbrick Tool (detailed here: http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700) to downgrade to 3.1.2, and then I upgraded to 3.2.8 using the official OTA file, and using the USB ADB sideload in the stock OOS recovery. I did go though the motions of setting up 3.1.2 before updating to confirm that it works.
However after updating to 3.2..8, the phone bricks itself again, and when I boot I get the OnePlus logo for about half a second, and then a black screen with the LED being white. I even tried updating OOS using the OTA updater in Android, and it boots into the recovery, apparently does the update but then bricks itself again!
I can boot into Fastboot fine, but I can't boot into the recovery.
I have noticed that when I boot, because my bootloader is unlocked, I get the screen about the bootloader being unlocked, blah blah blah, but the link to learn more says "g.co/placeholder". After I attempt to update to 3.3.8, I get the proper link, indicating that the firmware has updated in some way.
If I install TWRP straight after using the unbrick tool, I can boot into it fine, and then install CM13 just fine, and it boots. However the fingerprint reader doesn't work, and I assume this is a firmware issue.
Correct, it's a firmware issue. With CM13 you have to use older firmware (from 3.2.4 or older, if I remember correctly).
Sesrch XDA for a thread with firmwares and flash that, done
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Correct, it's a firmware issue. With CM13 you have to use older firmware (from 3.2.4 or older, if I remember correctly).
Sesrch XDA for a thread with firmwares and flash that, done
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
I've got a 3.2.4 firmware file, what's the best way of flashing it?
I did attempt to flash this with stock TWRP, but it appeared to brick the device again.
Additionally, when I boot into fastboot mode it doesn't show me the bootloader version.
Someone did suggest using the commands:
Code:
Fastboot erase modemst1
fastboot erase modemst2
after flashing OOS, would this help at all?
Stock TWRP should work with that ... But you may try modified 3.0.2.1-28 by eng.stk, nothing to lose (it works with ALL ROMs and firmwares to date).
Dunno about that other suggestion, I think that's more related to IMEI problems, but I'm not 100% sure.
Sent from my OnePlus 3 using Tapatalk
I think I'm going to book a session with OmePlus and see if they can unbrick it properly, or just return it to O2 where I bought the phone.
I still find it perplexing that updating to 3.2.8 from 3.1.2 using the Android OTA updater bricks the phone!
Related
I haven't updated my phone in around a year so I'm trying to update to either Android 5 or 6. Whenever I try to update the ROM to anything newer than 4, I get an error with the rom binaries. I read somewhere that this has to do with the Recovery being outdated which makes since as I'm on TWRP 2.8.0. However, I tried to update to TWRP 3.0.0 and then 2.8.4 and both times my phone got stuck in the Recovery boot process. I also read somewhere that this might be due to an outdated firmware. After more reading, I'm confused on how to update the firmware or what I should do to remedy these other problems. I tried to use RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2 to update my phone off of a guide I found, but it failed. Any help or suggestions would be really appreciated.
I have the ATT m8 and I'm running Android 4.4.4 with CyanogenMod 11-20150106-Nightly-m8 and TWRP 2.8.0. Heres the results from running adb getvar all on my phone
i.imgur.com/QPSAEAY.png
I noticed at some point my phone had radio invalid and basically every peripheral had stopped working; no reception, wifi, bluetooth, or camera. I tried oem lock command then to unlock it with the binary downloaded from htcdev. At that point everything besides the external sd card decided to become unmountable and now only the bootloader and TWRP works. Soooooo......... any help would be appreciated
edit: So I flashed stock recovery and did a factory reset This fixed this particular problem so my phone is at least working. then reinstalled TWRP. Unfortunately, I was only able to install 2.8.0 because of the problem described above so I'm back to square one
tjm46 said:
I also read somewhere that this might be due to an outdated firmware. After more reading, I'm confused on how to update the firmware or what I should do to remedy these other problems. I tried to use RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2 to update my phone
Click to expand...
Click to collapse
This is the same firmware as the hboot number in your photo would indicate.
Relock the bootloader and run the Lollipop 4.28.502 RUU as linked in my AT&T M8 Index thread here: http://forum.xda-developers.com/showthread.php?t=2751432
Then unlock the bootloader again, wipe cache and try to install TWRP 3.0.0.0
redpoint73 said:
This is the same firmware as the hboot number in your photo would indicate.
Relock the bootloader and run the Lollipop 4.28.502 RUU as linked in my AT&T M8 Index thread here: http://forum.xda-developers.com/showthread.php?t=2751432
Then unlock the bootloader again, wipe cache and try to install TWRP 3.0.0.0
Click to expand...
Click to collapse
Thanks, this fixed it. I don't know how many different articles and stuff I read, but I must have missed locking the boot loader.
tjm46 said:
Thanks, this fixed it. I don't know how many different articles and stuff I read, but I must have missed locking the boot loader.
Click to expand...
Click to collapse
You're very welcome.
So you were able to unlock the bootloader again, update to TWRP 3.0.0.0, and flash a current ROM?
Yeah, flashed TWRP 3.0 then the latest cyanogenmod nightly. Everything works great
tjm46 said:
Yeah, flashed TWRP 3.0 then the latest cyanogenmod nightly. Everything works great
Click to expand...
Click to collapse
Nice work.
Hi, I have bought used here in Italy a op3, when turn on in the display I can see a message about the bootloader unlock, and so I think that the previously owner have unlocked the unit. Now I have a problem with the update, I have tried with ota and with USB but the phone stop the update and show me the message installation failed, then I can only reboot. How I can relock the Bootloader? Thanks in advance for your help.
before you re-lock the bootloader you should make sure that you are running the stock oxygenOS rom and receovery, see below:
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
thanks for your reply, I, think that the phone now running with OxygenOS 3.2.2 stock, so I can directly relock the bootloader? If I do an hard reset the bootloader will be relocked?
alchemist76 said:
thanks for your reply, I, think that the phone now running with OxygenOS 3.2.2 stock, so I can directly relock the bootloader? If I do an hard reset the bootloader will be relocked?
Click to expand...
Click to collapse
you might be running OOS 3.2.2 stock but still have a custom recovery - boot into recovery first just to confirm that you have the stock recovery as well
still if you have a custom recovery, it's easier to get update. Just download the full rom and flash it with TWRP (I don't think there is another custom recovery), it won't wipe the data. Even if the previous owner did a slight modification on OOS 3.2.2, it will overwrite it.
updates can be downloaded many days before the OTA appear on the phone.
Ok I think that I have a custom recovery, TWRP working with non rooted phone? I have checked and my phone not have root. Please can you explain how I can update through TWRP?
if you want to stay unlocked and use TWRP that's fine, but note that you will need to MANUALLY UPDATE every time if you're on the stock OOS ROM.
if you are not comfortable with this, follow the instructions on the link i sent you to get back to full stock with stock recovery as well, so updates OTA work correctly.
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
2x4 thanks for your help, I not have any problem to keep my phone unlocked, but I don't able to update not even in manual way, maybe I wrong something.
I have enabled usb debug on op3, have connected the phone to my laptop and opened minimal ADB, then have downloaded the oxygenOS 3.2.4 put the phone in sideload mode, cecked the connection with adb devices command and the phone is connected. Then writed adb sideload and have dragged the oxigenOs .3.2.4 . but nothing happen in adb minimal and on the phone. After a bit the phone give me the same message that appears when I try to uptade through ota, installation failed an I can only reboot. Thanks again for your suggestions.
alchemist76 said:
2x4 thanks for your help, I not have any problem to keep my phone unlocked, but I don't able to update not even in manual way, maybe I wrong something.
I have enabled usb debug on op3, have connected the phone to my laptop and opened minimal ADB, then have downloaded the oxygenOS 3.2.4 put the phone in sideload mode, cecked the connection with adb devices command and the phone is connected. Then writed adb sideload and have dragged the oxigenOs .3.2.4 . but nothing happen in adb minimal and on the phone. After a bit the phone give me the same message that appears when I try to uptade through ota, installation failed an I can only reboot. Thanks again for your suggestions.
Click to expand...
Click to collapse
sorry, im not really sure what you mean, but if you're following the instructions on that post step by step and verifying what you get it should work.
You need to successfully flash the full zip to get the stock rom+recovery on there
ok sorry for my confusion. Please can you explain to me the right way to update a bootloader unlocked phone?
alchemist76 said:
ok sorry for my confusion. Please can you explain to me the right way to update a bootloader unlocked phone?
Click to expand...
Click to collapse
the bootloader being locked or unlocked is irrelevant - your issue is your non-stock recovery.
the full Oxygen OS zip includes the stock recovery from OnePlus, which OTA updates are programmed to use to automatically update your phone.
since you have TWRP recovery instead, you'll need to download and manually flash OxygenOS
download the full ZIP for 3.2.4 from this thread and flash it via TWRP recovery:
http://forum.xda-developers.com/oneplus-3/how-to/oxygen-os-3-2-4-released-t3437911
Hi all,
finally after hours of work I got my phone unlocked (drivers w10, fastboot didnt work blabla).
So now I unlocked bootloader, flashed twrp, flash superSU all according to the guide provided here.
So here's the catch:
I deleted everything, like EVERYTHING from the system without making a back-up..
I wanted to instal the CB but everytime I get Error 7.....
So I tried to instal the Oxygen 3.2.6 and that one DID work. After I installed this one, I tried to install 3.5.5 AGAIN and AGAIN error 7...
What can I do?
Sean9319 said:
Hi all,
finally after hours of work I got my phone unlocked (drivers w10, fastboot didnt work blabla).
So now I unlocked bootloader, flashed twrp, flash superSU all according to the guide provided here.
So here's the catch:
I deleted everything, like EVERYTHING from the system without making a back-up..
I wanted to instal the CB but everytime I get Error 7.....
So I tried to instal the Oxygen 3.2.6 and that one DID work. After I installed this one, I tried to install 3.5.5 AGAIN and AGAIN error 7...
What can I do?
Click to expand...
Click to collapse
Much strange.
What TWRP are you running? Because there are two main variants:
1) The official one (v3.0.2.1) which is compatible with every stock OOS firmware;
2) The modded one (at least v3.0.2.19, purposed here) which is compatible with both stock and CE firmwares.
Then... what's the error message shown for OOS v3.2.6? Error 7 like happens in v3.5.5?
Tell me more about
Simone98RC said:
Much strange.
What TWRP are you running? Because there are two main variants:
1) The official one (v3.0.2.1) which is compatible with every stock OOS firmware;
2) The modded one (at least v3.0.2.19, purposed here) which is compatible with both stock and CE firmwares.
Then... what's the error message shown for OOS v3.2.6? Error 7 like happens in v3.5.5?
Tell me more about
Click to expand...
Click to collapse
Hi Simone, i can't remember the full Error but multiple people had this problem.
For others the problem was relative easy to solve (they had to delete 1 sentence from a format). For me it was this easy as well, only the sentence had a different name.. I figured it out and now its working fine
What I did was flash an older version of the official build like 3.2.4 and then did a firmware ota to the latest THEN sideloaded the 3.5.4. I was on stock recovery but you can always switch to twrp once up and running on 3.5.5
Jayanyway said:
What I did was flash an older version of the official build like 3.2.4 and then did a firmware ota to the latest THEN sideloaded the 3.5.4. I was on stock recovery but you can always switch to twrp once up and running on 3.5.5
Click to expand...
Click to collapse
I can't go to the recovery mode
Amar5373 said:
I can't go to the recovery mode
Click to expand...
Click to collapse
Try this link http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
That's the custom recovery. Get into bootloader and type: Fastboot flash recovery (recovery name here without the parenthesis.img)
Ok so I'm an android noob and my HTC One M9 is soft bricked, I'm not even sure if it can be fixed. It has (had) android 4.4.2, TWRP and it is unlocked. It all started because my phone randomly stopped booting up, it started freezing at the HTC logo. After trying a lot of things and nothing worked I decided to do a factory reset, but I accidentally deleted my whole OS from my recovery. I decided to flash a new ROM and I downloaded the latest version of ViperOneM9. I flashed it from my recovery, the installation went smooth with no errors. When I tried to start my phone it booted only to bootloader. I tried reinstalling the ROM several times but it didn't fix it. I read on another forum that I should update my recovery (it was an older version, maybe 2.8.7.0, I'm not sure). I downoaded the latest version and flashed it from my old recovery. After that my recovery became inaccessible as well - it says "Failed to boot to recovery mode. Press volume up or down to back to menu". I tried installing several different versions of TWRP with fastboot but none worked. I decided not to mess with my phone anymore, so I took it to a repair shop. They couldn't fix it, I just got my phone back from them. I don't know what they tried, but everything is the same- phone can't boot up, can't access recovery mode. . Can someone please help?
I'd guess your firmware is out of date. The latest version of ViperOneM9 assumes that you're on the Android 6.0 firmware. As for TWRP being non-functional, that's probably because the latest version (3.x.x.x) also assumes you're on the Android 6.0 firmware and isn't compatible with 4.4.2 firmware.
If you know your MID & CID, perhaps the easiest way to get the latest firmware on your phone is the SD-card method of flashing an RUU. You will lose everything on internal memory (probably a non-issue, since the OS was already deleted), and your phone will be reset to factory defaults. You'll need to unlock the bootloader, flash TWRP, and root (if you so choose) all over again. But the RUU will get you on your feet again, and with the latest firmware.
Alternatively, you could flash the old TWRP version and then a pre-Android 6.0 ROM onto your M9, which should restore functionality, albeit with an old version of the Android OS.
Are you sure that you own a One M9. The oldest android version for the M9 is 5.0. Your problems might be caused by the fact that you're flashing files that aren't compatible with your phone.
Sent from my HTC One S using XDA Labs
computerslayer said:
I'd guess your firmware is out of date. The latest version of ViperOneM9 assumes that you're on the Android 6.0 firmware. As for TWRP being non-functional, that's probably because the latest version (3.x.x.x) also assumes you're on the Android 6.0 firmware and isn't compatible with 4.4.2 firmware.
If you know your MID & CID, perhaps the easiest way to get the latest firmware on your phone is the SD-card method of flashing an RUU. You will lose everything on internal memory (probably a non-issue, since the OS was already deleted), and your phone will be reset to factory defaults. You'll need to unlock the bootloader, flash TWRP, and root (if you so choose) all over again. But the RUU will get you on your feet again, and with the latest firmware.
Alternatively, you could flash the old TWRP version and then a pre-Android 6.0 ROM onto your M9, which should restore functionality, albeit with an old version of the Android OS.
Click to expand...
Click to collapse
Thanks a lot for the help, I fixed my recovery but I have no idea from where can I find a pre-Android 6.0 ROM. I can't find download links on the official sites of the ROMs
Flippy498 said:
Are you sure that you own a One M9. The oldest android version for the M9 is 5.0. Your problems might be caused by the fact that you're flashing files that aren't compatible with your phone.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
5.0.1 wasn't it?..
Beamed in by telepathy.
shivadow said:
5.0.1 wasn't it?..
Beamed in by telepathy.
Click to expand...
Click to collapse
Might be. It's been some time since I used firmware 1.x. The whole point of that post was that I wanted to explain that there's never been a 4.4.2 rom.
Sent from my HTC One S using XDA Labs
Hi,
Problem starting oneplus 3, let me explain.
1) purchased oneplus3, 4 months ago.
2) Rooted,updated oxygen 3.2.8 with TWRP recovery3021 and super SU 2.74-2
3) updated oxygen4.00 with twrp32128 and super SU 2.79SR2 everything was fine.
4) Received OTA update through VPN for oxygen 4.0.1 (30mb), installed but unable start instead it was always going into twrp mode.
5) i changed twrp recovery back to 3021 and install stock oxygen 3.2.8,was working fine.
6) Now i wanted to UNROOT the device and back to stock so that i can get OTA Oxygen 4 and 4.0.1.
7) i followed steps below,
a) downloaded oxygen 3.2.1 and stock recovery.img
a) fastbootloader, and connect device.
b) fastboot devices
c) fastboot fastboot flash recovery recovery.img
d) fastboot oem lock - when i used this command and accept YES, screen got black and no further instruction for ADBsideload.
8) i used to restart the device in recovery but black screen, fastboot loader working.
FASTBOOT MODE
PRODUCT NAME - ....
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - .....
SECURE BOOT - enabled
DEVICE STATE - locked
9) and if i start the device in normal it asked for screen pattern lock but my existing unlock pattern doesnt work.
10) by using all the chance for screen pattern unlock it showed DECRYPTION UNSUCCESSFULL, clicked on RESET PHONE but again screen black in recovery mode.
11) NOW if i start my device it again shows DECRYPTION UNSUCCESSFULL and asking for RESET PHONE......
What to do now.....
regards,
Zahir
use the mega unbrick guide method 2, always work
Don't panic mate!
mirko8054 said:
use the mega unbrick guide method 2, always work
Click to expand...
Click to collapse
Thanks mirko8054, I will let you know soon......
mirko8054 said:
use the mega unbrick guide method 2, always work
Click to expand...
Click to collapse
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
samadayesha said:
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
Click to expand...
Click to collapse
Device is back to stock, this method is used by One plus asstance for unbrick hard bricked device by remote control your PC. Then device is back to completly stock. No root no custom recovery etc. You Can now use OTA for update or using adb sideload or manually flash the entire ROM from sdcard. Thank you for appreciate :good:
mirko8054 said:
Device is back to stock, this method is used by One plus asstance for unbrick hard bricked device by remote control your PC. Then device is back to completly stock. No root no custom recovery etc. You Can now use OTA for update or using adb sideload or manually flash the entire ROM from sdcard. Thank you for appreciate :good:
Click to expand...
Click to collapse
thanks a lot, I will do accordingly.
samadayesha said:
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
Click to expand...
Click to collapse
just wanted to highlight the things you did that caused the issue
1- flashing the stock rom through twrp, it's possible specially with the latest TWR0-11 but not advisable, you better always flash stock recovery and then sideload rom (full rom not update) and then fast boot TWRP back and reflash root... any other method always causes issues...
2- the 30mg updates do not work on a rooted device
3- unrooting without immediately sideloading rom will always cause the black screen and loop to recovery, it's not required to unroot unless you want to go back to full stock experience...
4- this the biggest problem you made, you relocked the devices bootloader, you also did it while the device has a lot of issues (some mentioned above) so the device bricked instantly, if you are planning on unlocking the device again ...NEVER NEVER relock the device again , there's no need to do that , all you need to do to go back to a full stock experience is to wipe everything in TWRP , flash stock recovery then wipe everything again from there, then sideload full rom (latest stable version) , then for good majors in the new rom recovery wipe everything agian and boot to system and from system do a factory reset. then recharge your device to 100% and re encrypt it if it's not...after that you're 100% on a full stock exerience and will receive ota and it'll work... and at that state only (without root or TWRP) you can relock the bootloader (which is gain not necessary at all, there's no benefit to it)