Hi
I have a ASUS TF300T and have installed the TWRP bootloader as recommended by another site.
I have tried Cyanogenmod 9, Cyanogenmod 10 and Cyanogenmod 10.1 nightly and none of them will boot. The device gets stuck at the ASUS logo screen and I get no further.
Obviously I have cleared cache etc (I'm familiar with the basics of installing a different ROM).
Can anyone advise me what to do? I have restored to the default ASUS software through a backup I made but I am really not happy with the performance of this.
I either want to be able to get Cyanogenmod on this tablet or I'd like to restore it to the default bootloader to make it ready for sale.
Thanks so much in advance.
You need to make sure that the version of CM you're flashing will work with your bootloader. So far, it doesn't seem like you're paying attention to that. CM9 only works with the ICS bootloader. Early CM10 builds only worked with the ICS bootloader, but newer CM10 builds only worked with the 4.1 bootloader. The official CM10.1 only works with the 4.1 bootloader. The unofficial CM10.1 is testing support for the 4.2 bootloader and only works with the 4.2 bootloader.
If you don't know which bootloader you have, there are a couple ways to tell. First, do you remember the last OTA update you took? If it was version 9.something, you are on the ICS bootloader. If it was 10.4.something, you are on the 4.1 bootloader. If you are up to 10.6.something, you are on the 4.2 bootloader. If you do not remember the last OTA you took, you can boot the tablet to the bootloader, and it will tell you which version it is at the top of the screen.
And yes, the whole bootloader version thing is needlessly complicated, but it's not the devs' faults. ASUS is the one that kept changing how the bootloader worked. Complain to them if you want. I and the others here will be happy to help you figure it out, but we had nothing to do with making this difficult. We all hate it, too.
EndlessDissent said:
You need to make sure that the version of CM you're flashing will work with your bootloader. So far, it doesn't seem like you're paying attention to that. CM9 only works with the ICS bootloader. Early CM10 builds only worked with the ICS bootloader, but newer CM10 builds only worked with the 4.1 bootloader. The official CM10.1 only works with the 4.1 bootloader. The unofficial CM10.1 is testing support for the 4.2 bootloader and only works with the 4.2 bootloader.
If you don't know which bootloader you have, there are a couple ways to tell. First, do you remember the last OTA update you took? If it was version 9.something, you are on the ICS bootloader. If it was 10.4.something, you are on the 4.1 bootloader. If you are up to 10.6.something, you are on the 4.2 bootloader. If you do not remember the last OTA you took, you can boot the tablet to the bootloader, and it will tell you which version it is at the top of the screen.
And yes, the whole bootloader version thing is needlessly complicated, but it's not the devs' faults. ASUS is the one that kept changing how the bootloader worked. Complain to them if you want. I and the others here will be happy to help you figure it out, but we had nothing to do with making this difficult. We all hate it, too.
Click to expand...
Click to collapse
Hi there. Many thanks for your detailed and helpful response. I've never had to worry about this before as I've only rooted Samsung and HTC devices.
The bootloader is version 10.6.1. Judging by what you've said, I should be able to use Cyanogenmod 10.1 nightlies but unfortunately the same problem is replicated across this too.
How should I proceed?
Many thanks!
mattburley said:
Hi there. Many thanks for your detailed and helpful response. I've never had to worry about this before as I've only rooted Samsung and HTC devices.
The bootloader is version 10.6.1. Judging by what you've said, I should be able to use Cyanogenmod 10.1 nightlies but unfortunately the same problem is replicated across this too.
How should I proceed?
Many thanks!
Click to expand...
Click to collapse
No, the official CM10.1 nightlies are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader. You have two options here:
1. Downgrade to OTA version 10.4.2.20 and flash the official CM10.1 nightlies. There are several guides in these forums for doing this. The process is easy, but there are caveats. See CAUTION below.
Or
2. Use the unofficial CM10.1 for the 4.2 bootloader. You can find it HERE. I believe that the only thing broken right now is the camera.
CAUTION: Keep in mind, if you choose the downgrade method, you must be absolutely sure that you're flashing the correct recovery version. With the 4.2 bootloader like you have now, you need a recovery that ends in "-42". With the 4.1 bootloader, you need a recovery that ends with "-JB". Obviously, you have the correct recovery now, but if you decide to downgrade to the 4.1 bootloader, then back to the 4.2 bootloader, each requires a different recovery version. If you were to flash a "-JB" recovery with the 4.2 bootloader, you WILL BRICK YOUR TABLET. Not trying to scare you, but it happens a lot. Just skim through a few of the threads involving bricked tablets, and more often than not, it's because they use the wrong recovery for their bootloader. As long as you're careful, read the OP of any development threads, and double check which files you're flashing, you should be fine.
Honestly, if you don't need a working camera, it's probably best to stay on the OTA you're currently on, and flash the unofficial CM10.1. Otherwise, if you downgrade, just take baby steps and read carefully.
EndlessDissent said:
You need to make sure that the version of CM you're flashing will work with your bootloader. So far, it doesn't seem like you're paying attention to that. CM9 only works with the ICS bootloader. Early CM10 builds only worked with the ICS bootloader, but newer CM10 builds only worked with the 4.1 bootloader. The official CM10.1 only works with the 4.1 bootloader. The unofficial CM10.1 is testing support for the 4.2 bootloader and only works with the 4.2 bootloader.
If you don't know which bootloader you have, there are a couple ways to tell. First, do you remember the last OTA update you took? If it was version 9.something, you are on the ICS bootloader. If it was 10.4.something, you are on the 4.1 bootloader. If you are up to 10.6.something, you are on the 4.2 bootloader. If you do not remember the last OTA you took, you can boot the tablet to the bootloader, and it will tell you which version it is at the top of the screen.
And yes, the whole bootloader version thing is needlessly complicated, but it's not the devs' faults. ASUS is the one that kept changing how the bootloader worked. Complain to them if you want. I and the others here will be happy to help you figure it out, but we had nothing to do with making this difficult. We all hate it, too.
Click to expand...
Click to collapse
EndlessDissent said:
No, the official CM10.1 nightlies are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader. You have two options here:
1. Downgrade to OTA version 10.4.2.20 and flash the official CM10.1 nightlies. There are several guides in these forums for doing this. The process is easy, but there are caveats. See CAUTION below.
Or
2. Use the unofficial CM10.1 for the 4.2 bootloader. You can find it HERE. I believe that the only thing broken right now is the camera.
CAUTION: Keep in mind, if you choose the downgrade method, you must be absolutely sure that you're flashing the correct recovery version. With the 4.2 bootloader like you have now, you need a recovery that ends in "-42". With the 4.1 bootloader, you need a recovery that ends with "-JB". Obviously, you have the correct recovery now, but if you decide to downgrade to the 4.1 bootloader, then back to the 4.2 bootloader, each requires a different recovery version. If you were to flash a "-JB" recovery with the 4.2 bootloader, you WILL BRICK YOUR TABLET. Not trying to scare you, but it happens a lot. Just skim through a few of the threads involving bricked tablets, and more often than not, it's because they use the wrong recovery for their bootloader. As long as you're careful, read the OP of any development threads, and double check which files you're flashing, you should be fine.
Honestly, if you don't need a working camera, it's probably best to stay on the OTA you're currently on, and flash the unofficial CM10.1. Otherwise, if you downgrade, just take baby steps and read carefully.
Click to expand...
Click to collapse
Fantastic, thanks for that. I never use the camera - so I just wanted to check. I flash the "cm-10.1-20130430-EXPERIMENTAL-tf300t.zip - 161.95 MB" file found at http://forum.xda-developers.com/showthread.php?t=2252990 just as I would with any other Cyanogenmod version?
Thanks!
mattburley said:
Fantastic, thanks for that. I never use the camera - so I just wanted to check. I flash the "cm-10.1-20130430-EXPERIMENTAL-tf300t.zip - 161.95 MB" file found at http://forum.xda-developers.com/showthread.php?t=2252990 just as I would with any other Cyanogenmod version?
Thanks!
Click to expand...
Click to collapse
Yup. Other than the bootloader version fiasco, flashing ROMs and stuff is just like any other device.
Oh, make sure you have the Gapps, too (I'm sure you knew that already, though). The normal ones at Goo.im work fine.
Oh, and just for future reference, if you want to apply a brand new OTA update and go back to CM, wait a week or two before taking the OTA update. Don't go flashing willy nilly. Let the devs figure out the changes they need to make, if any. This is especially important for recoveries. Sorry for hammering in the whole "CAREFUL!" thing so hard, but I've seen way too many threads about bricked tablets. It gets depressing.
EndlessDissent said:
Yup. Other than the bootloader version fiasco, flashing ROMs and stuff is just like any other device.
Oh, make sure you have the Gapps, too (I'm sure you knew that already, though). The normal ones at Goo.im work fine.
Oh, and just for future reference, if you want to apply a brand new OTA update and go back to CM, wait a week or two before taking the OTA update. Don't go flashing willy nilly. Let the devs figure out the changes they need to make, if any. This is especially important for recoveries. Sorry for hammering in the whole "CAREFUL!" thing so hard, but I've seen way too many threads about bricked tablets. It gets depressing.
Click to expand...
Click to collapse
That seems to have done the trick!! Thanks so much for your help.
So, if Cyanogenmod asks me to update I should wait a while before applying it?
Cheers!
mattburley said:
That seems to have done the trick!! Thanks so much for your help.
So, if Cyanogenmod asks me to update I should wait a while before applying it?
Cheers!
Click to expand...
Click to collapse
Since you're using the unofficial build, you won't be able to use the CM Updater. Or, at least, I would assume you can't. I'm pretty sure that it would download the newest official version, and the official ones won't boot. So you'll have to watch the unofficial thread for updates for now, until everything's fixed and it becomes official.
As for waiting to update, that applies to the ASUS OTA updates, not the CM updates. ASUS, as I've mentioned, makes changes to the bootloader in some of their OTAs that can cause bricks. If you're just updating CM nightlies, you shouldn't have anything to worry about. It's the stock updates that get hairy.
If you would like more stuff working, you could downgrade your tablet to 4.1 (forum.xda-developers.com/showthread.php?t=2195883), and install CyanogenMod 10.
I just flashed the experimental on the 4.2 bootloader and I'm stuck on the CM boot screen with the spinning circle. Any idea why this might have occurred?
Me too. Just sits there spinning. Went to my backup for now.
Yeah, I just restored my backup as well after several attempts at getting CM 10.1 to work
roberto767 said:
Yeah, I just restored my backup as well after several attempts at getting CM 10.1 to work
Click to expand...
Click to collapse
I have the 4.2 boot loader. So I finally figured out you the 4.2 version recovery instead of the JB version. That unofficial one still would not work so I flashed this and it works great.
http://forum.xda-developers.com/showthread.php?t=2204166
thx for this thread, I had these issues myself,,, shame it wont work on 4.2 bootloader
Stuck at CyanogenMod Logo durng boot
Your detailed explanation is very much appreciated.
I am using the 4.2 bootloader and TWRP. I flashed the CM 10.1 Experimental version referenced in your post.
When I try to boot, I get stuck in at the CyanogenMod logo. This is the same place I got stock when I tried using the Nightlies and the Stable version. Any thoughts on what is going wrong?
EndlessDissent said:
No, the official CM10.1 nightlies are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader. You have two options here:
1. Downgrade to OTA version 10.4.2.20 and flash the official CM10.1 nightlies. There are several guides in these forums for doing this. The process is easy, but there are caveats. See CAUTION below.
Or
2. Use the unofficial CM10.1 for the 4.2 bootloader. You can find it HERE. I believe that the only thing broken right now is the camera.
CAUTION: Keep in mind, if you choose the downgrade method, you must be absolutely sure that you're flashing the correct recovery version. With the 4.2 bootloader like you have now, you need a recovery that ends in "-42". With the 4.1 bootloader, you need a recovery that ends with "-JB". Obviously, you have the correct recovery now, but if you decide to downgrade to the 4.1 bootloader, then back to the 4.2 bootloader, each requires a different recovery version. If you were to flash a "-JB" recovery with the 4.2 bootloader, you WILL BRICK YOUR TABLET. Not trying to scare you, but it happens a lot. Just skim through a few of the threads involving bricked tablets, and more often than not, it's because they use the wrong recovery for their bootloader. As long as you're careful, read the OP of any development threads, and double check which files you're flashing, you should be fine.
Honestly, if you don't need a working camera, it's probably best to stay on the OTA you're currently on, and flash the unofficial CM10.1. Otherwise, if you downgrade, just take baby steps and read carefully.
Click to expand...
Click to collapse
---------- Post added at 05:32 PM ---------- Previous post was at 05:15 PM ----------
I resolved this problem by wiping data using the Bootloader Wipe Data option and the TWRP Wipe Data option. (I probably did not need both.)
roberto767 said:
I just flashed the experimental on the 4.2 bootloader and I'm stuck on the CM boot screen with the spinning circle. Any idea why this might have occurred?
Click to expand...
Click to collapse
rdh23 said:
Your detailed explanation is very much appreciated.
I am using the 4.2 bootloader and TWRP. I flashed the CM 10.1 Experimental version referenced in your post.
When I try to boot, I get stuck in at the CyanogenMod logo. This is the same place I got stock when I tried using the Nightlies and the Stable version. Any thoughts on what is going wrong?
---------- Post added at 05:32 PM ---------- Previous post was at 05:15 PM ----------
I resolved this problem by wiping data using the Bootloader Wipe Data option and the TWRP Wipe Data option. (I probably did not need both.)
Click to expand...
Click to collapse
Just an FYI: the official CM10.1 now supports the 4.2 bootloader. It has for over a month now. Plus, the experimental build has been abandoned.
Same story again
Hello.
I am having the exact same problem : I unlocked my tf300t, flashed it with twrp 2.6.3.0. That went well, so I then installed cyanogen CM10.2.0-tf300t (I am summarizing here, but I did follow all the necessary steps, including the backup, the cache wipe etc). My latest android version was 4.2.1 and I have bootloader 10.6.1.27.5 which, as far as I know, should be compatible with CM 10.2
After flashing the CM install, upon reboot I get the cyanogen logo with the arrow spinning eternally while it just hangs there.
The worst part is that when I restored from my backup, upon reboot it does the exact same thing : I see the asus logo and a spinning circle below and nothing more.
Any idea what I should to to try and fix that ? I was thinking of trying the CM11 (nightly). Thanks.
M
p.s. I did make sure to get the right recovery for my bootloader, i.e. openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Emalice said:
Hello.
I am having the exact same problem : I unlocked my tf300t, flashed it with twrp 2.6.3.0. That went well, so I then installed cyanogen CM10.2.0-tf300t (I am summarizing here, but I did follow all the necessary steps, including the backup, the cache wipe etc). My latest android version was 4.2.1 and I have bootloader 10.6.1.27.5 which, as far as I know, should be compatible with CM 10.2
After flashing the CM install, upon reboot I get the cyanogen logo with the arrow spinning eternally while it just hangs there.
The worst part is that when I restored from my backup, upon reboot it does the exact same thing : I see the asus logo and a spinning circle below and nothing more.
Any idea what I should to to try and fix that ? I was thinking of trying the CM11 (nightly). Thanks.
M
Click to expand...
Click to collapse
What OS is your PC running??
lj50036 said:
What OS is your PC running??
Click to expand...
Click to collapse
windows 7 64bits...
adb
Emalice said:
windows 7 64bits...
Click to expand...
Click to collapse
You have the adb driver install?? if so turn your tablet off and in a command window move to the directory that adb is in and type
Code:
adb logcat > logcat.txt
now boot your tablet.... your PC will pick it as adb device and output the logcat to a text file in that directory post the logcat file....Let the logcat run for about 90 sec or so.....
Could someone please provide me with the latest Cyanogen Recovery for bacon?
They removed the option of writing recovery from CM12 so I can't get the latest version.
I'm looking for Cyanogen Recovery built from source not CWM or TWRP.
Thanks!
DJXMMX said:
Could someone please provide me with the latest Cyanogen Recovery for bacon?
They removed the option of writing recovery from CM12 so I can't get the latest version.
I'm looking for Cyanogen Recovery built from source not CWM or TWRP.
Thanks!
Click to expand...
Click to collapse
You can simply extract it from the official fastboot zip on this page: cyngn.com/products/oneplusone/ (sorry, not allowed to post links)
DJXMMX said:
Could someone please provide me with the latest Cyanogen Recovery for bacon?
They removed the option of writing recovery from CM12 so I can't get the latest version.
I'm looking for Cyanogen Recovery built from source not CWM or TWRP.
Thanks!
Click to expand...
Click to collapse
They didn't remove it, you are working with nightlys why would they put it in nightlys
I'm not looking for the OnePlus Recovery, I would like the latest Cyanogen Recovery.
Besides, that recovery is fairly dated back to KitKat.
They do allow you to flash recovery in CM11 nighties so I'm afraid you are mistaken.
There is a patch on the CM Gerrit that is waiting to be committed that will allow users to update recovery in CM12.
I guess I'll just have to wait for that but I was hoping to have a flashable IMG as well.
DJXMMX said:
I'm not looking for the OnePlus Recovery, I would like the latest Cyanogen Recovery.
Besides, that recovery is fairly dated back to KitKat.
They do allow you to flash recovery in CM11 nighties so I'm afraid you are mistaken.
There is a patch on the CM Gerrit that is waiting to be committed that will allow users to update recovery in CM12.
I guess I'll just have to wait for that but I was hoping to have a flashable IMG as well.
Click to expand...
Click to collapse
What do you mean? The stock recovery on this device is the CM recovery, there's no such thing as a OnePlus recovery. You can't flash nightlies with it. As previously stated you can just extract the recovery image from the stock fastboot images.
Transmitted via Bacon
Negative.
The stock recovery is Cyanogen based but is modified by OnePlus.
Much like how CM11S is Cyanogen based but is modified by OnePlus.
Now, I'm running CWM 6.0.5.1 but I would like to get the latest recovery which, when you build from source, is called Cyanogen Recovery and is more up to date.
Cyanogen took over development of CWM and eventually renamed it to Cyanogen Recovery.
I have a build, dated 20150118, for my old XT926 that someone graciously provided but I'm looking for bacon now.
Thanks.
DJXMMX said:
Negative.
The stock recovery is Cyanogen based but is modified by OnePlus.
Much like how CM11S is Cyanogen based but is modified by OnePlus.
Now, I'm running CWM 6.0.5.1 but I would like to get the latest recovery which, when you build from source, is called Cyanogen Recovery and is more up to date.
Cyanogen took over development of CWM and eventually renamed it to Cyanogen Recovery.
I have a build, dated 20150118, for my old XT926 that someone graciously provided but I'm looking for bacon now.
Thanks.
Click to expand...
Click to collapse
Where are you getting this information? CM11S is not modified by OnePlus.
Transmitted via Bacon
I'm sorry, I thought this was a well known fact.
Just Google "CM11S vs CM11"
CM11S is a customized version of Cyanogen just for the OPO.
Anyway, we are on CM12 now and I'd like to get the Cyanogen Recovery that is built against CM12 source.
Thanks.
DJXMMX said:
I'm sorry, I thought this was a well known fact.
Just Google "CM11S vs CM11"
CM11S is a customized version of Cyanogen just for the OPO.
Anyway, we are on CM12 now and I'd like to get the Cyanogen Recovery that is built against CM12 source.
Thanks.
Click to expand...
Click to collapse
Sorry, but you're mistaken, it is the exact opposite of a fact (it's completely untrue). Yes, CM11S is a customised version of CM11, but it is developed solely by Cyanogen (Steve Kondik is even the lead developer). Go and ask OnePlus or CM themselves, they'll tell you exactly the same thing. In fact, ask anyone who knows anything about this phone and they'll tell you exactly the same thing. OnePlus have absolutely nothing to do with the actual development of CM11S or CM12S, CM do all the work, CM do all the testing, CM submit it to Google for approval, CM provide the release once it receives accreditation. Why on earth do you think everyone was worried that this device wouldn't receive CM12S after the OnePlus/CM/Micromax drama in India? Because CM have 100% control over CM11S/CM12S.
Transmitted via Bacon
Ok.
Either way, it doesn't change the fact that there is a newer recovery available (I saw the commits on the CM Gerrit).
If someone could build it against CM12 sources for Bacon, that would be appreciated.
Thanks!
DJXMMX said:
Ok.
Either way, it doesn't change the fact that there is a newer recovery available (I saw the commits on the CM Gerrit).
If someone could build it against CM12 sources for Bacon, that would be appreciated.
Thanks!
Click to expand...
Click to collapse
There may be commits, but there definitely isn't a version available, and I highly doubt that anyone is going to build it because of two reasons:
1. It will be included with the CM12S update (coming very soon).
2. It has very limited functionality, it doesn't hold any value for the modding community.
Exactly what do you want it for? Why not use one of the available recoveries (TWRP/CWM/Philz/Cannibal)? They actually have functionality that is useful, CM recovery can only install signed zips (official OTA's), it's only ever been able to do that.
Transmitted via Bacon
Has anyone one used the latest twrp recovery? I know know there have been issues with past versions.
Been working fine for me. I only use it for a little before flashing ktoonsez recovery. If you aren't having issues with your current one, really no need to change. I just always grab the latest when "starting over" from a full firmware flash.
El.Dante565 said:
Has anyone one used the latest twrp recovery? I know know there have been issues with past versions.
Click to expand...
Click to collapse
I always grab the latest. So I snatched it up when 2.8.7 hit the floor. In fact this was my first time installing twrp with twrp. I have always used Odin but it's easy and it's been working great for me since the day it was released
Sent from my SM-G900P using Tapatalk
elesbb said:
Been working fine for me. I only use it for a little before flashing ktoonsez recovery. If you aren't having issues with your current one, really no need to change. I just always grab the latest when "starting over" from a full firmware flash.
Click to expand...
Click to collapse
I'm currently on NK5 4.4.4 and haven't updated it.. I know there's a current L update I can download, OTA, but I rather try some roms.. The thing is I'm not too sure about what recovery I can install. Is TWRP 2.8.7.0 gonna work with me or do I have to use SafeStrap? There's a bunch of options but not too clear on what will work with the current state my phone is in. I'm ready to root. Just need to know what custom recovery to flash..
kaslopis said:
I'm currently on NK5 4.4.4 and haven't updated it.. I know there's a current L update I can download, OTA, but I rather try some roms.. The thing is I'm not too sure about what recovery I can install. Is TWRP 2.8.7.0 gonna work with me or do I have to use SafeStrap? There's a bunch of options but not too clear on what will work with the current state my phone is in. I'm ready to root. Just need to know what custom recovery to flash..
Click to expand...
Click to collapse
Well I have used twrp recovery pretty religiously it has an good interface. Some find the Phil's CWM is good as will although I don't think that they is any more support for that, but there is one floating out there. I have never used SafeStrap. I believe that is used for lock bootloader which would be unnecessary for our Sprint phone which are unlocked.
Hey androids, I submitted this question as a reply to the guide thread already earlier... just thought it might get noticed in this forum alittle quicker... any help would be appreciated
I'm working on a recalled tablet that I rooted to keep using, and up until recently the ROM i had installed on it worked famously (bliss pop with android 5.1.1). Now, I was having some issues with it and thought "Well, i'll try out a different rom!"
So, I already had root (obviously) and I had already successfully installed a rom to this tablet... Using TWRP (both the 2.8.x.x I used previously and the newest one available for the shield) I have backed up, wiped, and flashed the images to 3 different roms + gapps for the appropriate versions...
first, I was going an issue with it mounting the \data partition so it wouldn't flash anything... then I repaired and rewiped the partitions, and got (what appeared to me in the logs) a clean and successful install of the roms. Each time I successfully flashed a ROM and GAPPs zips I would go to boot the ROM and my table would sit on the "NVIDIA" boot screen forever, never advancing to boot the ROMs.
I was worried that I had made a mistake and bricked the thing (though, it's been on borrowed time anyways being a recalled tablet). But I was able to force shutdown the tablet and reboot it into TWRP for another try. Each time I cleared the previous flash, wiped the cache and system partitions, and would get another clean install... but each time, it would get stuck on that same boot screen....
Anyone have any suggestions? thoughts? ideas? fixes? answers?.... anything? lol
Thanks folks!
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Is the newest TWRP *not* a MM bootloader?
TWRP is a recovery. A bootloader is a bootloader.
This is covered in every rom thread that updated from L to M.
lafester said:
This is covered in every rom thread that updated from L to M.
Click to expand...
Click to collapse
I'll re-look, the guides i've read have only covered flashing TWRP, then using them to flash the ROM and GAPPs... Which is what I did the first time I rooted it and put on a custom ROM... though maybe I didn't delete the original bootloader the first time and did so accidentally this time?
Thanks for the heads up though people, we'll see if I can straighten it out now that I know what I'm looking for
edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Ok, so I've downloaded the shield recovery zip, flashed the boot.img to the boot... nothing, then I read on one of the guides here that the "blob.img" is the bootloader... but the zip has a blob, without the .img
So I then attempted to add .img, and flash it to "boot" in TWRP, and there was an error, saying the file is too large...
do you (or someone else) know where to find a guide on where to find/how to flash a MM bootloader?
thanks
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
MilesD37 said:
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
Click to expand...
Click to collapse
Im stuk with the same probem, can you sendme the Link to the gide please
Ok so I figure I'll just ask since there is so much old information, and dead links or links that lead to no real answers. I'm already rooted and on a stock rom. Build number is LMY48C. I tried flashing a new TWRP version, 3.2.3.0 official version, but every time I try to reboot to recovery it just stays on the Nvidia logo. I can boot back to the tablet and flash my old version, 2.8.7.1 and everything works fine. But nothing remotely new will flash with that version lol. Any ideas of what I'm missing? Thanks in advance for anyone that can help, I'm sure it's something stupidly easy that I'm messing up lol.
I'd recommend flashing back to stock using the latest Nvidia image...then allow it to upgrade itself...they only have 5.2 available on their site...after it upgrades you'll have the newest bootloader...then in fastboot flash your recovery.
Make sure you're bootloader unlocked the whole time! And don't lock it...leave it unlocked.
You should be good to go after that.
Extra info...I'm on LOS 14.1 using opengapp (custom config so it only installs what I want)
I also flash a few other things but everything is working on my shield....even Nvidia Games
HaRdC0r3 said:
I'd recommend flashing back to stock using the latest Nvidia image...then allow it to upgrade itself...they only have 5.2 available on their site...after it upgrades you'll have the newest bootloader...then in fastboot flash your recovery.
Make sure you're bootloader unlocked the whole time! And don't lock it...leave it unlocked.
You should be good to go after that.
Extra info...I'm on LOS 14.1 using opengapp (custom config so it only installs what I want)
I also flash a few other things but everything is working on my shield....even Nvidia Games
Click to expand...
Click to collapse
Thanks for the reply. I was honestly just hoping there was a way to flash the newest bootloader without going to stock, but it looks like that's not an option. Ohh well, One more question, since you're actually on u custom ROM, does HDMI out work? I use that a lot with my TV haha.
If you want the easy quick way then you could pull the bootloader from the newest 15.1 zip as steel included it....flash the bootloader through fastboot and then proceed to flash twrp then wipe wipe wipe and install whatever rom you wanted...I still suggest 14.1 and yes the HDMI works.
HaRdC0r3 said:
If you want the easy quick way then you could pull the bootloader from the newest 15.1 zip as steel included it....flash the bootloader through fastboot and then proceed to flash twrp then wipe wipe wipe and install whatever rom you wanted...I still suggest 14.1 and yes the HDMI works.
Click to expand...
Click to collapse
Thanks for the reply, computer was messed up so couldn't see this sooner lol. Anyway, since I have no idea how to just pull the bootloader from a file, I'll have to do the whole thing it seems. Thanks for your reply ^_^