Related
My TF300 is unlocked. I installed the new JB and then I was trying to install CWM. I used fastboot to push it to the device. When I rebooted, holding down the volume button, It came up to the menu with RCK, USB, etc. I selected wipe data by accident. It sat there for a while saying it was going to wipe and go into the boot loader. After a while I shut it off thinking it was hung. Now when I power on the device I get only the ASUS startup screen. Volume up or down don't affect the mode. It just says "The Device is Unlocked" at the top, and the static ASUS logo in the middle. When I plug in the USB to my Windows 7 computer I get nothing in the device listing. I can't even fully turn the device off. Holding power for a few seconds, it goes off, and then it comes right back on by itself.
I think I'm totally bricked, right? I CAN get into APX mode.
Yes, wiping the data will brick your device if you don't have a working recovery.
sparky28000 said:
Yes, wiping the data will brick your device if you don't have a working recovery.
Click to expand...
Click to collapse
Actually, I just discovered that I do have access to APX. Is there a way to push a working recovery through APX?
jrfaulkin said:
Actually, I just discovered that I do have access to APX. Is there a way to push a working recovery through APX?
Click to expand...
Click to collapse
I did exactly the same thing.
I have exact same problem.
Tried it via APX mode via NVflash but no luck so far.:crying:
need the correct SBK version.
SBKv1 and SBKv2 doesn't work for the TF300t.
I send my tf300t for repair.
Lets hope that they can fix my TF300t.
jeroen.wit said:
I did exactly the same thing.
I have exact same problem.
Tried it via APX mode via NVflash but no luck so far.:crying:
need the correct SBK version.
SBKv1 and SBKv2 doesn't work for the TF300t.
I send my tf300t for repair.
Lets hope that they can fix my TF300t.
Click to expand...
Click to collapse
Unfortunately, APX and nvflash is not available for the TF300T currently. As I understand it, you're required to record some information and your Secure Boot Keys (SBK) prior to bricking to be able to access APX. Otherwise, your only recourse is to contact Asus and start the RMA process.
I'm recording my developments over in this thread : http://forum.xda-developers.com/showthread.php?t=1825265&page=2 (my post is at the bottom)
I think I'm going to hold out until someone figures out the NvFlash process as described here:
http://androidroot.mobi/technical/tf-secure-boot-key/
I had the same issue. wiped my data after the JB update as my device froze halfway through the update, so I forced a reboot and it hang at the Asus screen, so not thinking I wiped data to go do a fresh update... I wiped the update and all my data/system/recovery.
I found that in the boot loader screen (Wipe Data, Fastboot, ETC....) I was able to navigate to fastboot select it and then it would hang from there. - my computer wouldnt recognize it either however, i tried flashing a copy of TWRP anyway while in my hanging fastboot just to see what happened.
It didnt work first few times but it did eventually flash. so I had a recovery to work with. via a MicroSD put a fresh copy of the JB update on it and re-flash through the recovery via External SD Card.
It did remove my root access, TWRP and all the data on my device after flashing the JB update but it "un-bricked" me and got me booted again.
Don't know if I was just lucky or if it will work for you.
gypsyshaw said:
I had the same issue. wiped my data after the JB update as my device froze halfway through the update, so I forced a reboot and it hang at the Asus screen, so not thinking I wiped data to go do a fresh update... I wiped the update and all my data/system/recovery.
I found that in the boot loader screen (Wipe Data, Fastboot, ETC....) I was able to navigate to fastboot select it and then it would hang from there. - my computer wouldnt recognize it either however, i tried flashing a copy of TWRP anyway while in my hanging fastboot just to see what happened.
It didnt work first few times but it did eventually flash. so I had a recovery to work with. via a MicroSD put a fresh copy of the JB update on it and re-flash through the recovery via External SD Card.
It did remove my root access, TWRP and all the data on my device after flashing the JB update but it "un-bricked" me and got me booted again.
Don't know if I was just lucky or if it will work for you.
Click to expand...
Click to collapse
The difference in your situation is that you were able to access the boot loader. My boot loader is wiped. I don't get the option to select Wipe Data/Fastboot, etc. I'm stuck in a mode where I think the only option is to low-level flash the bootloader after re-initializing all of the partitions.
Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
You cant't wipe data from bootloader menu, If you do that, you will get unrecoverable brick.
Sorry I believe I mislead you -> I wiped data from within CWM.
Anyway, I used this thread:
http://forum.xda-developers.com/showthread.php?t=1757077
I went back to stock and I think i'll stay there for a little while longer, this process made me nervous (I've rooted my thunderbolt, droid DNA, galaxy tab 2 7" and my friends phones) so anyway I believe I installed the wrong CWM and that caused errors trying to install a JB rom on a ICS CWM... If you have any insight let me know...
undergfx said:
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
Click to expand...
Click to collapse
My suggestion is to flash the latest stock JB blob.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Once you get it sorted then flash the latest twrp for jb.
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Edit:
Ah didn't see your post. I did what you recommended, and actually, while my device said it was on 4.1.1 JB, when I hold pwr/vol down I see a completely different menu now than last time, so I wonder if perhaps my OTA didn't correctly load everything from the firmware update hmm...
undergfx said:
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Click to expand...
Click to collapse
The same way you flashed cwm.
Windows? Start - in search type cmd - press enter
In the cmd window cd to the directory with fastboot.
Hook cable between tablet and usb port on computer.
On tablet hold power and volume down till you see the bootloader menu.
Down volume till you are at the usb symbol - then volume up.
This should put you into fastboot mode - use the commands above.
Wait till the first command completes before you give the second command.
[INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc. You will find the stock firmware here as well as most other needs.
You will have to unzip to get the blob which you should place in the directory with fastboot.
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
undergfx said:
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
Click to expand...
Click to collapse
You're welcome.
Good Luck!
Hi. I had endless issues last night trying to install a nightly build of Cyanogenmod 10.2 on my Asus tf300t. Long story short, after the CM update from within android, the recovery mod (CWM) had trouble mounting the sd card. I then flashed the latest version of TWRP and tried to update the bootloader by installing the latest firmware from asus, at this point everything went well. Back to the updated bootloader, I tried to install the nightly CM and still got mounting problems so again, I tried switching between TWRP and CWM. Now, I'm suck. I cannot get passed the asus boot logo: after a few seconds, it falls back to the recovery mod (I may have wiped the newly installed system). At any point, holding power+vol-down has no effect, I cannot get into the bootloader menu and enable fastboot. Only thing I have left is access to CWM and access the device via ADB. Can anyone recommend me a course of action?
Also, I'm trying to get one thing straight: what is actually needed to install a recent version CM? There seems to be some intricate dependencies between the bootloader version you're using along with the version of the recovery mod and the CM / android you're about to install. (If anyone can clarify this for me, it would be really appreciated).
Any suggestion regarding any ways on how I could recover my device will be greatly appreciated!
Thanks!
Stravor said:
Hi. I had endless issues last night trying to install a nightly build of Cyanogenmod 10.2 on my Asus tf300t. Long story short, after the CM update from within android, the recovery mod (CWM) had trouble mounting the sd card. I then flashed the latest version of TWRP and tried to update the bootloader by installing the latest firmware from asus, at this point everything went well. Back to the updated bootloader, I tried to install the nightly CM and still got mounting problems so again, I tried switching between TWRP and CWM. Now, I'm suck. I cannot get passed the asus boot logo: after a few seconds, it falls back to the recovery mod (I may have wiped the newly installed system). At any point, holding power+vol-down has no effect, I cannot get into the bootloader menu and enable fastboot. Only thing I have left is access to CWM and access the device via ADB. Can anyone recommend me a course of action?
Also, I'm trying to get one thing straight: what is actually needed to install a recent version CM? There seems to be some intricate dependencies between the bootloader version you're using along with the version of the recovery mod and the CM / android you're about to install. (If anyone can clarify this for me, it would be really appreciated).
Any suggestion regarding any ways on how I could recover my device will be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
READ BEFORE YOU START!!!!!!
CM10.2 is for the 4.2 BOOTLOADER AND CWM IS NOT WORKING WITH IT! you now have a bricked tablet! sorry :'(
noahvt said:
READ BEFORE YOU START!!!!!!
CM10.2 is for the 4.2 BOOTLOADER AND CWM IS NOT WORKING WITH IT! you now have a bricked tablet! sorry :'(
Click to expand...
Click to collapse
"Bricked" seems to be oftenly abused around here. Having ADB access and being able to boot into CWM, isn't there anything I can do to enable fastboot, force a bootloader downgrade or something?
Thanks!
This is the only thing I can do for you
http://forum.xda-developers.com/showthread.php?p=45120193
Sent from my TF300T using xda app-developers app
noahvt said:
This is the only thing I can do for you
http://forum.xda-developers.com/showthread.php?p=45120193
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Moral of this story: "bricked" really is an abused word around here. For anyone in my situation, namely: stuck in a boot loop where power+volume down has no effect and thus is preventing access to fastboot, if you still have adb access, you can issue: adb reboot bootloader, it should at least allow you to access the bootloader again and from there, fastboot. The above linked post really was helpful. Thanks!
Stravor said:
Moral of this story: "bricked" really is an abused word around here. For anyone in my situation, namely: stuck in a boot loop where power+volume down has no effect and thus is preventing access to fastboot, if you still have adb access, you can issue: adb reboot bootloader, it should at least allow you to access the bootloader again and from there, fastboot. The above linked post really was helpful. Thanks!
Click to expand...
Click to collapse
"ricked" may be abused, but I don't understand your situation very well, much less how you extricated yourself from it. If you're in a boot loop, you cannot complete the booting process (much like a tab with bootloader, recovery, but no OS installed). Without it, you have no access to ADB. Which in turn doesn't allow you to issue ADB commands. If additionally, you have no access to fastboot because volume down+power, and/or reset+volume down, does nothing (bootloader with icons absent), you cannot issue fastboot commands. Without the two, and the uselessness of APX mode, I'm not sure why that's not characteristic of a soft brick.
I have a mainboard that shows nothing but the initial Asus logo (not the one with boot animation, i.e., spinning dots) and "the device is unlocked." If I use either fastboot or ADB from PC, it returns with "waiting for device..." You were in the same boat, were you not? Looks like part of the firmware is still there (I assume if you replace the nand with a brand new, blank one, nothing would show up on display) , but the bootloader is messed up. If you'd succeeded in resurrecting your tab, then how do I rectify it, if you care to enlighten? Thank you in advance.
A couple of months back, I had unlocked the bootloader (I had stock 4.2.1) and rooted this tablet in order to put Cyanogenmod on it. The current version was CM10.2 (nightlies). I was able to update to different nightly versions and then to the stable 10.2 version. Recently, I saw CM11 nightly versions beginning to appear, so I thought I'd install it.
Using TWRP 2.6.1.0, I had been able to do all of my CM10.2 updating. However, with CM11, the initial flash didn't work (I did clear cache and Dalvik), and so I thought I had to update TWRP. I downloaded TWRP 2.6.3.0 for the TF300T (both .img and .blob) and tried to fastboot them to my device. .img did not work, but then the blob fastboot was able to install TWRP, however, there was a password lock. Reading about this online, I thought I just had to reflash TWRP 2.6.3.0. I tried that and got the same password issue.
Then, I thought that CWM would be a better option (although I thought I may have seen things about it not playing well with the 4.2.1 bootloader...). I flashed a version of that (not exactly sure what version... (which may be the source of my problem) but it was for the TF300T...). Then, upon rebooting, it got stuck on the ASUS loading screen (with "The Device is UnLocked." in the corner). So then I tried rebooting into the recovery, but then I couldn't access the recovery menu from power + vol. down buttons anymore.
Basically, what I can do now is restart the tablet (via holding the power button or pressing the reset slot), but it always gets stuck on the ASUS screen, or I can enter APX mode, but don't think that'll do much good since I don't have nvFlash installed...
Is my tablet bricked?
Thanks in advance!
PS - I saw some solutions that required opening up the tablet. I would be okay with doing that, but only as a last resort!
Quevvy said:
A couple of months back, I had unlocked the bootloader (I had stock 4.2.1) and rooted this tablet in order to put Cyanogenmod on it. The current version was CM10.2 (nightlies). I was able to update to different nightly versions and then to the stable 10.2 version. Recently, I saw CM11 nightly versions beginning to appear, so I thought I'd install it.
Using TWRP 2.6.1.0, I had been able to do all of my CM10.2 updating. However, with CM11, the initial flash didn't work (I did clear cache and Dalvik), and so I thought I had to update TWRP. I downloaded TWRP 2.6.3.0 for the TF300T (both .img and .blob) and tried to fastboot them to my device. .img did not work, but then the blob fastboot was able to install TWRP, however, there was a password lock. Reading about this online, I thought I just had to reflash TWRP 2.6.3.0. I tried that and got the same password issue.
Then, I thought that CWM would be a better option (although I thought I may have seen things about it not playing well with the 4.2.1 bootloader...). I flashed a version of that (not exactly sure what version... (which may be the source of my problem) but it was for the TF300T...). Then, upon rebooting, it got stuck on the ASUS loading screen (with "The Device is UnLocked." in the corner). So then I tried rebooting into the recovery, but then I couldn't access the recovery menu from power + vol. down buttons anymore.
Basically, what I can do now is restart the tablet (via holding the power button or pressing the reset slot), but it always gets stuck on the ASUS screen, or I can enter APX mode, but don't think that'll do much good since I don't have nvFlash installed...
Is my tablet bricked?
Thanks in advance!
PS - I saw some solutions that required opening up the tablet. I would be okay with doing that, but only as a last resort!
Click to expand...
Click to collapse
Try using fastboot to install this version of TWRP: http://forum.xda-developers.com/showpost.php?p=48512729&postcount=16
It will only work if you were on 10.6.1.15 or above. It allows flashing CM11.
cmendonc2 said:
Try using fastboot to install this version of TWRP: http://forum.xda-developers.com/showpost.php?p=48512729&postcount=16
It will only work if you were on 10.6.1.15 or above. It allows flashing CM11.
Click to expand...
Click to collapse
The thing is, I can't get into fastboot the typical way; pressing power and volume down does not go into the fastboot mode like it did before. I can get into APX mode, though. Can I use that to flash a recovery? I haven't been able to find a way of doing that yet…
Quevvy said:
The thing is, I can't get into fastboot the typical way; pressing power and volume down does not go into the fastboot mode like it did before. I can get into APX mode, though. Can I use that to flash a recovery? I haven't been able to find a way of doing that yet…
Click to expand...
Click to collapse
No, you need nvflash backups to use APX mode. Since you can't get to the recovery menu, I can't think of any other solutions....?
Same here
I'm in the same state after trying to update from 10.2 to 11. Just sits at the ASUS logo screen. No fastboot or recovery. I can get it to turn off by holding the up volume and inserting a paper clip into the reset switch hole. Otherwise I have been totally unsuccessful in getting it to do anything else. At this point I'm not adverse to opening it up. Do you have the link to the solution you found that required opening the tablet? Maybe I'll give it a try.
boggessb said:
I'm in the same state after trying to update from 10.2 to 11. Just sits at the ASUS logo screen. No fastboot or recovery. I can get it to turn off by holding the up volume and inserting a paper clip into the reset switch hole. Otherwise I have been totally unsuccessful in getting it to do anything else. At this point I'm not adverse to opening it up. Do you have the link to the solution you found that required opening the tablet? Maybe I'll give it a try.
Click to expand...
Click to collapse
You would have to open it and replace the motherboard with a new one like this:
http://forum.xda-developers.com/showthread.php?t=2368372
With a new part like this:
http://www.ebay.com/itm/like/390706401658?lpid=82
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
hillg001 said:
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
Click to expand...
Click to collapse
Hey funny you should say that. I'm actually on my second Asus 3 ultra. The same thing happened to my first one got stuck during a firmware update, or corrupted firmware zip.,now the phone won't boot to twrp or bootloader, just vibrates like yours. If I plug the charging cord in vibrates then just get those red led notification light blinks,computer won't even recognize the device so can't flash the bootloader back to the phone to fix, so I guess it's hard bricked paperweight. I only had it for about a week before the brick, had to buy a new one. The thing that's funny to me the first one would boot to twrp no problem, now this new one seems to boot to twrp but just presented a black screen, it's in twrp recovery because you can feel the vibrations for the buttons, just can't see the screen. I would love to be able to fix the bricked one it's brand new, and can't send for warranty because I'm in the US, sucks.
If you have the address for the foreign country's location of manufacturing, you can send it in for repairs. That's what we are working on doing. The horrible thing is, after reading about stories of other customers, Asus really rakes you over the coals price wise for the repair, & then does similarly for return shipping. So we are still trying to find a way around the high shipping prices, at least.
.
gubbilo144 said:
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
Click to expand...
Click to collapse
What stock keeping unit (SKU) is your phone? WW, TW, CN, or JP?
What version of TWRP did you flash?
hillg001 said:
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
Click to expand...
Click to collapse
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
qbchung said:
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
Click to expand...
Click to collapse
i think the mistake people may be making is flashing stock rom through twrp
twrp only for supersu zip and other things imo
stock rom just flash through the stock recovery apply update from sd (microsd card) need to make sure the recovery and rom match
can you get to stock recovery? also charge it first to a good 80 to 90 if not 100 percent
gubbilo144 said:
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
Click to expand...
Click to collapse
After you get that black screen, just press once the power button to close and then press it again to open, just like you do when you normally close and open the screen. You will see after that the twrp interface.
qbchung said:
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
Click to expand...
Click to collapse
read your post again...noticed...
one thing-if you were on ww-14 i.e. android nougat then cannot simply flash the ww 13 marshmallow as I believe the bootloader is different - think that is why the flash did not work (know this from other zenfone forums where you cannot simply downgrade by flashing a previous android level rom) if it was not a case of downgrading then maybe because of using twrp for stock rom instead of the update process using stock recovery
I tried to flash ww 13 when on ww 14 through stock recovery and it was giving me an error (saying version is not ww which was not the case anyway)-found out through other forums that it is because one cannot downgrade in that manner - therefore I think cause of flash error is the bootloader version. For downgrading one needs the raw file. I found raw file for our ultra (WW13 level) at a Vietnamese site and the flashing tool but have not tried it (no reason to) but am keeping it just in case.
you can get stock recovery from here (note the ww 13 or ww 14 types pick the right one)
https://mega.nz/#F!9tEj2azZ!QKmvc-VJZR1Iqk6H7alQnQ
flash it through fastboot
need to have fastboot drivers installed
https://developer.android.com/studio/releases/platform-tools
or
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
make sure path variable has fastboot folder in it in environment variables of computer
preferably have recovery image in that folder too so you don't have to type some long path names
power off
volume up press and hold then press power
get to bootloader fastboot mode
connect by usb
open command prompt window in folder where fastboot installed
check fastboot devices to verify phone is seen
filename.img = filename of the twrp.img
twrp flash recovery filename.img
if successful then
twrp boot filename.img
may have to press power or volume up to get to the screen
while in stock recovery better to do factory reset too before update
then apply update from sd card
btw I have successfully used the twrp march version 3.2.1 (also at the above mega link) with the latest stock ww 14 (from jan 8 2018) backed up restored successfully, rooted, and have xposed as well
a note on twrp restore if ever having to (just don't check system image restore in twrp when restoring)
trying to do miui port
Can anyone help me???My device isn't opening after twrp flashing.when I reboot I see dark screen,not twrp recovery... please somebody help me,fast.....
Same problem with my iball tablet
Even flashing stock recovery doesn't give me recovery back i have also tried philz recovery but no luck i need help too