Database Info

XT926 - not sure how best to proceed

First off, I just switch to my first android phone from iOS, so although I have plenty of experience jailbreaking and unlocking over there, I'm new to this, so hand-holding is appreciated
I have a developer XT926 phone. Fastboot says it's unlocked with status code 1. It came running 4.0.4, and I rooted it using motofail2go. I now want to install CyanogenMod 10.1 (or some other version 4.2 rom that you guys think is better), as described here. However, I have been unable to find detailed instructions on how to install it after booting into recovery mode. (I'm guessing those steps are well-know on xda, but forum and google searches didn't help.)
Additionally, since I have an unlocked dev phone, can I install one of these unsigned roms directly, or will I need to first install clockworkmod, safestrap, etc (and if so, any advice on which one).
Thanks the any help you can give me

You need to install a custom record very like twrp or cwm. Either is fine and you can easily switch later if you want to try them both out. Once you have your custom recovery installed, you'll need to boot into recovery. From there you will v be able to backup your current setup followed by a factory wipe and ROM install. Good luck

SFG said:
You need to install a custom record very like twrp or cwm. Either is fine and you can easily switch later if you want to try them both out. Once you have your custom recovery installed, you'll need to boot into recovery. From there you will v be able to backup your current setup followed by a factory wipe and ROM install. Good luck
Click to expand...
Click to collapse
Thanks. So I have twrp installed and working, and made a successful backup. I was about to install CW 10.1, when I noticed comments that it seems to have a lot of issues. What rom would you recommend I install? Liquidsmooth? Eclipse? CM 10.1 anyway? Thanks again!

reaver9 said:
Thanks. So I have twrp installed and working, and made a successful backup. I was about to install CW 10.1, when I noticed comments that it seems to have a lot of issues. What rom would you recommend I install? Liquidsmooth? Eclipse? CM 10.1 anyway? Thanks again!
Click to expand...
Click to collapse
Try em all!
I'm an Eclipse man myself.

[Q] Help understanding my current rom/recovery situation

Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.

Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The stock Asus firmware includes bootloader, kernel, recovery and apps. You have flashed the stock recovery. Head over to the twrp thread or my ROM thread in my sig to see how to get twrp 2.5 onto your tab.

Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
Yes, you did. Everytime you install stock file of any version, it will update your bootloader, rom, and kernel. Just use Motochopper to root your device and reinstall your custom recovery with goomanager.
No, it is stock recovery. Just reroot with motochopper and install custom recovery with goomanager. Have fun. :good:

Right, thanks! If I want to stay completely stock I just need to figure out why the newer update is failing. Could be the file name now I think about it.
Otherwise I'll re-root and re-TWRP...

Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The Android on his back is your stock recovery and it does not find a valid update file.
Weird is, that your system seems to see the 10.6.1.14 file (I assume you get an automatic notification and click "install" or "update" ) and then the recovery does not seem to install it...?
You could have a bad download, so try that first if you want to get the latest stock rom, or you can try to rename the downloaded file to EP201_768_SDUPDATE.zip, put it on your microSD card and reboot into recovery. The recovery should recognize the update file and start flashing it.
But since you are unlocked anyway - why don't you give CromiX a try? It runs so much better than the stock rom!
And for that, yes you would have to root again using the Motochopper tool and then install TWRP 2.5 with Goo Manager.
If you go that route make sure you flash the latest bootloader from the OP of the CROMiX thread first, boot back into your old rom once before you flash CROMiX.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?

Anatosuchus said:
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Click to expand...
Click to collapse
It's based on the stock rom, cleaned up and tweaked and optimized. Everything works - and better than on stock! I recommend selecting the option to disable fsync during installation. It boosts performance considerably, and since the rom is totally stable, the "risk" is neglible.
You will love it!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

OK, ChromiX installed! Looks interesting already, will tinker with it over the next couple of days.

Custom ROM Issue... Stuck Booting...

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

Unable to flash any Custom ROM, why?

Hey all,
As I am getting fed up with the 5.1.1 stock ROM of Nvidia, I want to flash a custom Nougat ROM to my Nvidia Shield. I have already unlocked the bootloader, installed TWRP, and rooted my device. This all went without problems.
But then I tried installing a custom ROM, but after installation of both the ROM and the Gapps, the tablet just doesn't want to get past the Nvidia boot logo. Then I have no choice but to back up in recovery, and to recover my backup.
The process I mentioned I have tried for at least 6 different ROM's, and all of them don't get passed the nvidia boot logo. So this means Im still stuck with the 5.1.1 version from Nvidia (don't worry, I won't brick it)
I have the original non-K1 32-bit Shield. I have a feeling that it has something to do with this, and that that is the reason why I cant flash ROM's.
My question is, does anyone recognize this issue, or, does anyone know how to fix this?
Kind Regards,
Horizon
Edit1: Another thing worth mentioning (maybe) is that it can't a md5 file for each custom ROM I try to install, but this shouldn't be a problem right?

HorizonR2 said:
But then I tried installing a custom ROM, but after installation of both the ROM and the Gapps, the tablet just doesn't want to get past the Nvidia boot logo. Then I have no choice but to back up in recovery, and to recover my backup.
Edit1: Another thing worth mentioning (maybe) is that it can't a md5 file for each custom ROM I try to install, but this shouldn't be a problem right?
Click to expand...
Click to collapse
I could be that the custom Roms need the newer bootloader.
So you should try install latest OTA, avoid the kill switch and than you should be able to install a custom rom
And the md5 is just to check if the ZIP is damaged or so, which happens nearly never.
And it doesnt matter if you have a k1 or an original Shield Tablet

is there a partial blob I can flash for the new bootloader without installing the entire Stock ROM? I have the same problem and really don't want anything to do with Nvidia software unless absolutely necessary.

ddvche said:
is there a partial blob I can flash for the new bootloader without installing the entire Stock ROM? I have the same problem and really don't want anything to do with Nvidia software unless absolutely necessary.
Click to expand...
Click to collapse
Read this guide on how to install Nougat; it explains all: https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541

Rooted Stock ROM, trying to update TWRP and flash a new custom ROM

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 ^_^