Ok, so got my brand new shiny Oneplus 3T yesterday after waiting aged for it to come in.
Using it for a bit, noticed an OTA update to nougat came out (about 900mb) which downloaded in the background.
Triggered the upgrade, now the phone won't boot. I'm also having trouble installing any recovery roms on to it, because I was never intending to root the phone in the first place, and as a result didn't unlock the bootloader using the phone interface when it was on.
So now, it appears I'm stuck! My phone won't accept any side-load roms, (fails), full roms don't read (cannot open file) and fastboot won't unlock the bootloader (Not allowed)
....um.. not having a clue what I'm doing here....help???
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
To fix it - see "[UNBRICK] Unbrick Tutorial For The OnePlus 3T!!!!!!!! by Harris K". You have to download his two files onto a laptop or desktop computer and install a qualcomm driver (one of the files). The qualcomm driver will open a serial port into the phone's chipset. The other file will download a stock system, recovery, and fastboot to your phone through the qualcomm serial port. Harris is a genius, buy him a beer. This will fix the following problems.
1) It sounds like the OTA patch screwed up your /system where it doesn't even try to boot. You can still boot into /recovery and /fastboot but just not into /system. Since the phone is still "locked" (flashing prohibited) you cannot flash anything to fix it.
2) dm-verity does not allow any changes to /system. dm-verity checks a hash of hashes of /system. If the hash check fails when you boot /system, dm-verity will "brick" your phone (by design) leaving you with a black screen.
The OTA updates the system and downloads a hash key corresponding to that version. After the OTA, everyone has to end up with exactly the same system in order to pass the dm-verity check.
When you enable flashing (called "unlocking the bootloader") dm-verity will wipe /data to prevent someone from flashing a non-stock recovery to access your data.
infamousvincci said:
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
Click to expand...
Click to collapse
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
bunburyist said:
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
Click to expand...
Click to collapse
I deserve a thank you button haha
Related
I'm a newb..
Atrix HD with unlocked bootloader and rooted. Installed cwm recovery, flashed to the latest nightly cm 11 for atrix hd, rebooted and stuck at cyanogenmod loading screen (head with the spinning circle around it). left it that way over night with no change still stuck on bott.
I've spent several hours following several guides with no success
I think the problem started whn I did a factory reset and clear cache in cwm before I flashed cm 11. it gave an error on data or something.
fastforward several hours later I now have philz touch 6 recovery which I read on this guide http://forum.xda-developers.com/showthread.php?t=2577447 you could use to fix the corrupted data partition. problem is when booted to philz recovery the driver for phone is not installed correctly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone is recognized fine in fastboot mode however.
Is there a way to fix the corrupted data partition using fastboot?
I've already tried fastboot -w and reflashing but that did not work.
I have the latest motorola drivers and latest sdk with google usb installed etc.
Unfortunately I was stupid and didn't make a nandroid backup so I hope there is another way to get this phone working.
thanks
Solved
After 2 days of monkeying around I finally got it fixed.
I never could get the phone recognized in recovery mode (philz mod) and using ADB as suggested by the guide I linked.
Finally what worked is I downloaded the stock rom zip, extracted it, edited the xml file in MS word deleting the 2 lines with "getvar" in them, booted the phone into fastboot mode, connected the phone to my PC and made sure it was recognized in device manager, loaded the xml from the stock rom into RSD Lite and flashed back to stock, rebooted, and all was working fine.
I know there's a million and 1 guides that say to do what I just described and believe me I tried the exact things I posted above for the better part of 2 days and rsd lite would always fail with some kind of error. Finally I rebooted my PC, downloaded the stock rom again, edited the xml, and tried one last time and it finally worked...I don't know what made the difference.
Now if I could just find a trick around this darn subsidy (hard) lock this Atrix HD would be back in business.
So before I start I just wanted to say that I have been rooting and installing roms back at the time when I had my galaxy s3, I knew this stuff before upgrading to my nexus 6.
So the problem as you can see on the title that I cant unlock the oem option, means I cant unlock my bootloader, but there is a twist.
When I bought my nexus, I remember it was 5.0, and there was an update to 5.1, the update was OTA, and I remember the update had problems, it couldn't finish and the phone stayed on 5.0 and you could not
update to 5.1 unless you flash 5.0 again. So I unlocked my bootloader back at the time, and installed 5.0 all over again, and everthing was fine until now(now I am on 7.0)
Now I want to root my phone and install things and I cant do that, because of the oem options, but when i go into fastboot it says device is unlocked, and when I turn my phone on under the google sign there is small open lock sign that I know tells the bootloader is unlocked.
So there is my problem, I cant root it and so on, very sorry of the long post but I think it was necessary so I could explaine my problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not quite sure what your problem is. Your bootloader is already unlocked, you just flash twrp via faatboot
Code:
faatboot flash recovery nameoffile.img
then flash SuperSU. If it asks for a password, or you can't find any files on your device in twrp, that means you're encrypted, and will have to completely wipe data on device. You do that by hitting cancel (if it's asking for a password) then go to wipe. Then select format. You'll have to type yes. Now you'll be unencrypted.
As a side note, you may be able to get away with just flashing twrp, and then sideloading the SuperSU zip
dictionary said:
Not quite sure what your problem is. Your bootloader is already unlocked, you just flash twrp via faatboot
Code:
faatboot flash recovery nameoffile.img
then flash SuperSU. If it asks for a password, or you can't find any files on your device in twrp, that means you're encrypted, and will have to completely wipe data on device. You do that by hitting cancel (if it's asking for a password) then go to wipe. Then select format. You'll have to type yes. Now you'll be unencrypted.
As a side note, you may be able to get away with just flashing twrp, and then sideloading the SuperSU zip
Click to expand...
Click to collapse
Thank you very much, apparently it worked even if the oem option is not available, hope I wont get into more troubles.
I managed to brick my ME375CL in my attempt to root it, it only shows the "Intel Inside" logo when I boot it up.
After much driver install/reinstall and cursing at my computer, I managed to get it to be recognized in Intel Phone Flash Tool.
I've read the instructions on doing custom flashes in blank phone mode for other tablets, but for the life of me, I can't figure out which file is supposed to go in which field.
I would greatly appreciate any insight into this that anyone can provide.
I already have the firmware downloaded.
This is where I am at:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the list of files I have to work with from the firmware download:
Thanks in advance!!!
The link below may be your best bet to reload the system and root it. I would recommend reading the entire thread first.
https://forum.xda-developers.com/memo-pad-7/help/official-rom-att-asus-memo-pad-7-lte-t3554127
johnkirchner said:
The link below may be your best bet to reload the system and root it. I would recommend reading the entire thread first.
https://forum.xda-developers.com/memo-pad-7/help/official-rom-att-asus-memo-pad-7-lte-t3554127
Click to expand...
Click to collapse
Thanks for the reply. I've already read through that post and attempted the steps within. The problem is that I followed those steps and they failed, now it can only be recognized as an Intel SoC by my computer, so ADB, fastboot commands and Asus Flash Tool will not work.
The only programs I've gotten to recognize the tablet is Intel's Phone Flash Tool and Flash Tool Lite.
If you haven't yet, try using the boot, system and recovery images from the firmware you downloaded in the android section of the flash tool and see what happens.
johnkirchner said:
If you haven't yet, try using the boot, system and recovery images from the firmware you downloaded in the android section of the flash tool and see what happens.
Click to expand...
Click to collapse
I've tried all kinds of combinations in this software, but it always fails at either the IFWI step or gives me this error:
10/08/17 14:03:09.468 INFO : Port 5/1/1: Rebooting in Provisonning OS (current state = UNKNOWN_STATUS)
10/08/17 14:03:09.468 INFO : Port 5/1/1: Cannot Reboot android device, status is UNKNOWN_STATUS
Based on the reading I've done in other threads, the only way to correct this is through a firmware flash in blankphone mode, but it won't accept any of the IFWI files that I have found for this tablet.
I appreciate you trying to help, but I can't do what you are suggesting when it's not even being detected as an Android device. Fastboot commands will not work because there's nothing on the tablet for ADB to make a connection to.
Here's what happens when I try:
Here is what my tablet is doing:
When it's detected by Intel Phone Flash Tool, it usually has a blank screen. Otherwise, it just shows that Intel logo for about 15 seconds, reboots and then does it again, endlessly.
Oh, I forgot to mention that Asus support was kind enough to offer a repair or replacement for $155, since it's out of warranty. I'm hoping for a much cheaper option.
I have never seen the intel logo on mine? Have you tried booting the tablet in to fastboot mode by shutting it down and then turn it on by holding the volume up button and the power button? If you can get to fastboot mode, you should be able to use adb commands. Unfortunately, i am not familiar with the flash software you are using.
This method is actually dangerous. Do not try this unless you have a good reason to do so
This method erases IMEI. Backup EFS with official or enhanced TWRP. Do not use any other TWRP as these might not backup EFS correctly and you will lose IMEI
Only use this as a last resort if everything else fails to revive your device.
First open the download tool. I will assume you at least know how to use it in the default upgrade mode
Press the verify button. The unbrick tool will freeze for a bit. Wait until it shows something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that close the verification window. An SMT download mode option will be unlocked
Yes, red signifies danger. Don't ask
Now press start
You'll see this box
The password is te123
Warnings: type the password exactly as it is. Do not make typos
Select your exact storage size
If you do not do this correctly you'll worsen the situation
Hit ok and the download will start
When the download completes you'll see this screen:
Disconnect your phone. Now exit the program
You might see this message but if it says download complete like in the screenshot above it is safe to press yes
Your device will not auto reboot like it did in the standard download mode. You'll have to press and hold the power button to force a reboot
Boot oxygenos fully and immediately use TWRP to restore your EFS backup
If you get an NV backup warning first restore EFS and then follow the steps given here https://forums.oneplus.com/threads/nv-backup-warning.474643/
I had a person who badly messed up his bootloader. The unbrick tool in upgrade mode didn't help. SMT fixed the issue and thankfully he had an EFS backup so the device was back to normal
Hi, meat I know where is the link to this download tool?
kakrona said:
Hi, meat I know where is the link to this download tool?
Click to expand...
Click to collapse
HERE
Um, hello guys, has anyone been able to unlock bootloader of a T-Mobile OP after SMT download?
Cuz I couldn't as it's giving me an error when flashing unlock_token.bin that says something like "Verify error (3:-2)".
If anyone had experience please report, thx in advance.
anupritaisno1 said:
I had a person who badly messed up his bootloader. The unbrick tool in upgrade mode didn't help. SMT fixed the issue and thankfully he had an EFS backup so the device was back to normal
Click to expand...
Click to collapse
How did you get SMT mode to work?
Hello to all!
Two years after I bought my awesome 6/128 ZUK Z2 Pro ("international" rom, android 6.0.1, ZUI 2.1.120, no updates), I decided to mess with it. After getting some trouble done, I flashed via QFIL the stock 1.9 (possibly updated to 2.5 yet? not sure...) and the SuperSU, which I couldn't flash on stock ZUI 3.1.194. Last two days I was trying to find a way to flash TWRP but I couldn't, because I tried through fastboot and it always told me "waiting for device". I could only boot TWRP through the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", as it was described at a guide here (BTW, guys thanks a lot for everything you share with us!). But still, it didn't let me install some roms I've tried (AOSP 6.7, AOSP 7.0), because "Updater process ended with ERROR:7". Also, after flashing the SuperSU, I couldn't open the stock recovery, it automatically redirected me to fastboot.
My (big) problem started when I randomly chose "Boot to FFBM" through fastboot, so the "All Failed" screen was appeared. It couldn't be so bad, but is behaved like having a bad stroke, and the "buttons" on the bottom or anything else, can't be selected or scrolled properly. After rebooting (holding the power button), it sent me there, again. So now, it is impossible to boot at the rom. I can still boot into bootloader, but it doesn't recognize QFIL yet, in order to install the rom again. I can also boot into twrp via the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", but nevertheless i cannot install another rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I mean, I REALLY need your help, otherwise I had to buy another phone! (I'm stuck with my mother's, old J5 2015 for now)
I still cannot boot into stock recovery, and I can install nothing from that twrp. I think my only hope is, if you know another command through powershell, which my phone can obey (except it often tells me "waiting for device"). Or else, this would be the hard way for me of learning what "hard-brick" is.
Thanks in advance for your time, sorry for grammar/spelling mistakes, I would really appreciate any help given! :crying:
Images:
Oh, unfortunately the images aren't shown, I hope they are here:
For some reason they aren't shown, I got them by a shareable link in google Drive.. If anyone is interested in helping me, I can send the images private. In fact, I would even pay some bucks for this!
Ok, I noticed that there are also many "bricked" (or not) cases from another members here that haven't be answered, but since I found the solution for my case I'm leaving the thread for anyone who possibly need it:
https://zukfans.eu/community/thread...-read-this-before-creating-a-new-thread.7603/
In my case, the answer was on the last Q & A, about the accidentally stuck to the FFBM mode, so I just thanked this guy. Have a nice day!