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
Related
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.
Hello guys,
I installed CM11 a while ago on my Nexus 5. I had no trouble installing it through Cyanogenmods own installer, but now i want to install
the official rom again, so android 4.4.4 Kitkat. But when I want to flash it through TWRP i get the error that there is no MD5 file found.
I got the rom from the official site from Google.
I want to install the clean version of android again because i have some trouble with my battery and want to try if its still a problem with original software
installed.
So can you help me with this?
Thanks in advance.
Eelke91
When you after trouble shooting a battery issue you should wipe your phone and flash the stock image. Do not trouble shoot a battery issue with a custom ROM. Period. There are too many factors involved. And bugs can arise that won't be in a stock image.
I do want to flash to my stock image, but sadly i didnt backup so i want to manually install stock android kitkat.
Eelke91 said:
I do want to flash to my stock image, but sadly i didnt backup so i want to manually install stock android kitkat.
Click to expand...
Click to collapse
You don't have to wipe internal. Just Data and Cache. Go fastboot a stock image. If you aren't backing up Your Apps and you aren't clean flashing ROMs, that's why you are having so many issues. Never dirty flash a ROM unless your ROM Dev says otherwise.
Okay, but im pretty sure I wiped everything trying to install stock android. Atleast i got the message when i wanted to reboot that there was no OS installed..
So if its still possible to fastboot to my stock image can you tell me how to? I've now restored my phone to CM11, which was the last ROM i had installed, so i still can use my phone but its not the stock
image.
Eelke91 said:
Okay, but im pretty sure I wiped everything trying to install stock android. Atleast i got the message when i wanted to reboot that there was no OS installed..
So if its still possible to fastboot to my stock image can you tell me how to? I've now restored my phone to CM11, which was the last ROM i had installed, so i still can use my phone but its not the stock
image.
Click to expand...
Click to collapse
Google nexus factory image. Use that with fastboot.
Sent from my Nexus 5 using XDA Free mobile app
Eelke91 said:
Okay, but im pretty sure I wiped everything trying to install stock android. Atleast i got the message when i wanted to reboot that there was no OS installed..
So if its still possible to fastboot to my stock image can you tell me how to? I've now restored my phone to CM11, which was the last ROM i had installed, so i still can use my phone but its not the stock
image.
Click to expand...
Click to collapse
The instructions to flash a factory image are on the same page you download the image from. You need to flash it with fastboot, not recovery.
Okay i flashed it back to the stock os but still problems with my battery so i think its broken..
Eelke91 said:
Okay i flashed it back to the stock os but still problems with my battery so i think its broken..
Click to expand...
Click to collapse
Not likely. Probably just wakelocks. Go visit the battery help thread in my signature
So when the whole shield tablet recall program started, I installed blisspop on my old tablet. Now I want to return that tablet to stock. I downloaded the 2.2.2 recovery image and tried to flash it off of a micro SD card through twrp, but I keep getting a error that's says failed to sysMapFile and nothing happens. How can I revert back to stock? And I picked 2.2.2 because I was worried about the killswitch, can I actually use the 3.1.1 image and then re root and remove the Tegra update file? When I return to stock rom, will I be able to reinstall a custom recovery but keep the stock rom? Sorry for all the questions, I'm pretty new at this. Thanks for the help!
Flash what ever you want in fastboot.
IF you let it boot make sure it's been factory reset, if it connects to WiFi your F****D.
From recovery delete the "TegraOTA" folder/apk from /system/app (or /system/priv-app, I forget). As long as you nuke the updater before it connects to WiFi you're fine.
fro03 said:
So when the whole shield tablet recall program started, I installed blisspop on my old tablet. Now I want to return that tablet to stock. I downloaded the 2.2.2 recovery image and tried to flash it off of a micro SD card through twrp, but I keep getting a error that's says failed to sysMapFile and nothing happens. How can I revert back to stock?!
Click to expand...
Click to collapse
As the poster above me said, you must flash this with fastboot.
fro03 said:
And I picked 2.2.2 because I was worried about the killswitch, can I actually use the 3.1.1 image and then re root and remove the Tegra update file?
Click to expand...
Click to collapse
You can use whatever image you want as long as you remove TegraOTA.
fro03 said:
When I return to stock rom, will I be able to reinstall a custom recovery but keep the stock rom?
Click to expand...
Click to collapse
Yes, you can also just flash the custom recovery from fastboot when you are installing the custom ROM. Or you can just not flash a new recovery at all. If you leave your current recovery partition intact you can still flash your custom ROM using fastboot.
weedy2887, sockusminimus
would either of you be up to creating a potential debrick image for this device ?
thanks
m
HI all
i was using my recalled tablet normally alongside with the other and at some point i decided to put on a custom rom.
Before this a friend of mine unlocked the bootloader , rooted the tablet and putted on it the CWM , flashing the nomoreota.zip
After a long period without any problems i decided to go on custom trying to flash the Blisspop first, then Dirty Unicorn and then another one i don 't remember.
The result was the same with every single one : black screen and nvidia logo and that was it.
I successfully flashed TWRP adn used it to install the roms but there was no different response.
Can anyone please help me ?
i wouldn t mind to go back on stock but i fear to brick my tablet due to the kill switch, so i prefer to go on custom to be invisible to nvidia servers.
Thank you for your help in advance
Any Ideas ?
up
If you change from a 5.x to a 6.x ROM, you need to flash the correct blob as detailed in the follwing thread
http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
You also need to install a 3.x.x TWRP.
If you still get into recovery and are able to flash roms, this is pretty much the only possible problem I know of.
njhuiz said:
If you change from a 5.x to a 6.x ROM, you need to flash the correct blob as detailed in the follwing thread
http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
You also need to install a 3.x.x TWRP.
If you still get into recovery and are able to flash roms, this is pretty much the only possible problem I know of.
Click to expand...
Click to collapse
thanks a lot. i will try it tomorrow
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