Purchased a Shield K1 Tablet
Which will arrive this week, and there are things I would like to know about it, i.e notably on whether or not I should unlock and root it, despite the potential risk of doing so.
What I plan on using this for is primarily emulation (Snes through PSP and maybe Dolphin, no idea how well that works yet) That being said, are there things I should do to it?
Do as in, things I can root or flash to give myself the best possible experience, to get the most out of this? I've seen a lot of custom ROMs, Cyanogenmod (which I have on my
Nexus 7 2012, along with a dual boot OS). I have been thinking about having the stock Android 5.1.1, alongside Android 4.1.2 for the sake of Wii remote support since Google
foolishly broke that part of Bluetooth (and the part that never will be fixed again). The problem is, I don't know how hard or cumbersome it would be to do such a thing
without bricking the Shield tablet and ending up with a pricey paperweight. What tutorials, guides, etc should I look into before I consider such an undertaking? I want
to be sure I pick the right files and OS image(s) to install so I can do this right, if that makes sense.
I just bought it too and was coming from a Nexus 7 2012.
Rooted with the latest CM 12.1 nightly, no issues so far.
Wifi is slowish/buggy and the touchscreen has some issues, but afaik these issues are there on stock, too.
Just get the latest CM12.1 from their site, flash it with TWRP. I had issues with open gapps and ended up using CM's gapps.
koichirose said:
I just bought it too and was coming from a Nexus 7 2012.
Rooted with the latest CM 12.1 nightly, no issues so far.
Wifi is slowish/buggy and the touchscreen has some issues, but afaik these issues are there on stock, too.
Just get the latest CM12.1 from their site, flash it with TWRP. I had issues with open gapps and ended up using CM's gapps.
Click to expand...
Click to collapse
Fair enough, and I know that no device is perfect, everything has their own set of issues, so I don't think I'll regret getting a Shield Tablet, that much I know. I was going to get a Samsung Tab E 9.6, but the specs just didn't figure, esp. for someone who wants more power, you know? What about the Android OS ROM you install it with? Should I go with Android 5.1.1 or dual boot it with 4.1.2 instead so I can have Wii remote support? Thanks.
I don't know, that's your choice. I don't have that requirement, so I went with CM12 (5.1.1), single OS
koichirose said:
I don't know, that's your choice. I don't have that requirement, so I went with CM12 (5.1.1), single OS
Click to expand...
Click to collapse
Fair enough, I'll keep looking around the forums to gauge what I need to do. I can't help but feel a bit nervous on rooting and voiding the warranty on a device I just spend 200 bucks on, maybe that's just me though :laugh:
the_randomizer85 said:
Fair enough, I'll keep looking around the forums to gauge what I need to do. I can't help but feel a bit nervous on rooting and voiding the warranty on a device I just spend 200 bucks on, maybe that's just me though [emoji23]
Click to expand...
Click to collapse
Nvidia has stated that it will still honor the warranty despite it being unlocked or rooted in most cases. I'm just gonna guess that unless you accidentally wipe your bootloader, or use an overclocked kernel that fries it you should be good. What they said is if YOU fubar it that voids the warranty, but if it's anything normally covered by warranty your good.
That said, I rooted, unlocked, and installed an oc kernel as well as recovery within an hour of receiving mine and it runs beautifully. Better than pure stock actually.
Sent from my SM-G386T1 using Tapatalk
Exile1975 said:
Nvidia has stated that it will still honor the warranty despite it being unlocked or rooted in most cases. I'm just gonna guess that unless you accidentally wipe your bootloader, or use an overclocked kernel that fries it you should be good. What they said is if YOU fubar it that voids the warranty, but if it's anything normally covered by warranty your good.
That said, I rooted, unlocked, and installed an oc kernel as well as recovery within an hour of receiving mine and it runs beautifully. Better than pure stock actually.
Sent from my SM-G386T1 using Tapatalk
Click to expand...
Click to collapse
Okay, I wasn't 100% sure, only device ever rooted and unlocked was a Nexus 7 2012, never had a problem with it once I got it up and running. I don't feel comfortable with OC at all, as the power is
definitely more than enough for my needs, if that makes any sense. That being said, I don't know what kernel I need since this is my second time ever doing something like this, a little green in the gills so to speak (sad, I know). Anyways, would you guys advise to having dual boot install on this, or just a better 5.1.1 Android ROM than the stock version? I feel a bit overwhelmed at it all, and I don't know what tutorial I should truly follow, that's why I feel overwhelmed, you know?
Reasons for the tablet:
1 - The specs are insanely powerful for emulator apps, my Nexus 7 struggles with even 2D PSP games and some PSX games, lots of stuttering in the audio department, so my primary use is gaming
2 - Multimedia, movies, YT, music and so on
So really, I don't need anything fancy OS wise, just enough to help get the most out of it without having to overclock the hardware. What order would I need to do everything in? Are there good step by step guides for people like me?
http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
INSTALL DRIVER
-enable Developer Options
-enable Debugging Bridge
-do a 'adb devices' and check the dialog on your mobile and allow it 'every time'
-shutdown
-hold Volume down and Powerbutton at same time
if the bootloader showed up
-do a 'fastboot devices' if it shows your device online then
-do 'fastboot oem unlock'
after that you have flash your recovery
go to the directory where the file is and
-do 'fastboot flash recovery your_file_here'
after that you can reboot to bootloader and go to recovery
copy the SuperSu.zip which you downloaded at chainfires site or on xda and push it to your internal memory (/sdcard)
and flash it over recovery.
reboot enjoy!
the_randomizer85 said:
Okay, I wasn't 100% sure, only device ever rooted and unlocked was a Nexus 7 2012, never had a problem with it once I got it up and running. I don't feel comfortable with OC at all, as the power is
definitely more than enough for my needs, if that makes any sense. That being said, I don't know what kernel I need since this is my second time ever doing something like this, a little green in the gills so to speak (sad, I know). Anyways, would you guys advise to having dual boot install on this, or just a better 5.1.1 Android ROM than the stock version? I feel a bit overwhelmed at it all, and I don't know what tutorial I should truly follow, that's why I feel overwhelmed, you know?
Reasons for the tablet:
1 - The specs are insanely powerful for emulator apps, my Nexus 7 struggles with even 2D PSP games and some PSX games, lots of stuttering in the audio department, so my primary use is gaming
2 - Multimedia, movies, YT, music and so on
So really, I don't need anything fancy OS wise, just enough to help get the most out of it without having to overclock the hardware. What order would I need to do everything in? Are there good step by step guides for people like me?
Click to expand...
Click to collapse
wiQbold said:
http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
INSTALL DRIVER
-enable Developer Options
-enable Debugging Bridge
-do a 'adb devices' and check the dialog on your mobile and allow it 'every time'
-shutdown
-hold Volume down and Powerbutton at same time
if the bootloader showed up
-do a 'fastboot devices' if it shows your device online then
-do 'fastboot oem unlock'
after that you have flash your recovery
go to the directory where the file is and
-do 'fastboot flash recovery your_file_here'
after that you can reboot to bootloader and go to recovery
copy the SuperSu.zip which you downloaded at chainfires site or on xda and push it to your internal memory (/sdcard)
and flash it over recovery.
reboot enjoy!
Click to expand...
Click to collapse
So I just follow the guide on the thread, or do I follow the guide you just posted?. The reason I ask is because in the thread's guide, past the parts where it said to install the ADB driver and then the USB drivers for the device, I'm not sure what "debugging bridge" is, unless you meant enable USB debugging, IDK.
- Enable USB developer mode
- Enable USB debugging
- Copy the recovery image and supersu.zip to where the ADB install folder is
- Open the program to open a CMD window to the install location
- Type "adb reboot bootloader"
- Etc
I mean, because the two guides are confusing me more, the forum guide, the thread, how it's worded...now I don't know. Sorry. Is that thread and your guide the same thing, all leading to ultimate unlock and root the device using ADB and the recovery image? And is it not feasible to install Android 4.1.2 as a dual boot OS image so I can test out the Wii Classic Controller since Google broke that part of the Bluetooth code in 4.2+?
there is another tutorial from SuperPichu I think. this is the best for my understanding but I didn 't find it , up in hurry(?)
http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
and yes. usb-debugging
wiQbold said:
there is another tutorial from SuperPichu I think. this is the best for my understanding but I didn 't find it , up in hurry(?)
http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
and yes. usb-debugging
Click to expand...
Click to collapse
Okay, that thread says flashed to OTA 2.0 already, not entirely sure what that means, to be honest, or of the bootloader is locked on it, haven't gotten it yet. I take it I follow the first thread you posted, then
the one above?
the_randomizer85 said:
Okay, that thread says flashed to OTA 2.0 already, not entirely sure what that means, to be honest, or of the bootloader is locked on it, haven't gotten it yet. I take it I follow the first thread you posted, then
the one above?
Click to expand...
Click to collapse
it is a old thread. It s for kitkat..
I think you go like I said.
be sure. adb drivers are installed
Developer Options
Usb debugging
cmd
'adb devices'
check dialog
'adb reboot-bootloader'
'fastboot devices'
look for output
'fastboot oem unlock`
'fastboot flash recovery /directory/to/your-recovery-file'
'fastboot reboot-bootloader'
go to recovery
flash SuperSU.zip
reboot
wiQbold said:
it is a old thread. It s for kitkat..
I think you go like I said.
be sure. adb drivers are installed
Developer Options
Usb debugging
cmd
'adb devices'
check dialog
'adb reboot-bootloader'
'fastboot devices'
look for output
'fastboot oem unlock`
'fastboot flash recovery /directory/to/your-recovery-file'
'fastboot reboot-bootloader'
go to recovery
flash SuperSU.zip
reboot
Click to expand...
Click to collapse
And I go into recovery mode by holding vol. down and power, right? And in that mode I flash the SuperSu.zip correct? And I did get the recovery.img from nVidia's source, which I assume is the one I use in Command. Okay. Rebooting I assume is well, heh, also by holding down power. I also noticed both of those threads have the OS name Lollipop in the thread title.
Related
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
mowassasin said:
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
Click to expand...
Click to collapse
So I went and bought the factory cable from the Black Hat guys, and luckily haven't had the need to use it. Any advice you'd like to give in case I need to at some point?
I guess the only advice I can give is: don't re-lock the boot loader when you have a custom rom loaded
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
It wouldn't recognise any fastboot commands nor the RSD Lite program for me.
But if it does, then thats good.
Merely a heads up for those who were in the same situation I was
bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
yaturner said:
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
Click to expand...
Click to collapse
Over the course of a few hours I was able to fix this, so I am going to write this little walkthrough for you using a rom from bwcorvus's page (CLICK HERE) and then used the guide from dirtymindedx -(CLICK HERE)
The reason it took me this long (as well as doing other things) was because I used the wrong set up to unroot my tablet. I was using the Unofficial images that are on bwcorvus's link. Because I didn't read thoroughly enough in his breakdown, I made myself look like a fool...
What you want is NOT
UNOFFICIAL STOCK IMAGES
Click to expand...
Click to collapse
because you will not be able to lock the bootloader (IF you want it to be that way, which I did, and so it gave me a 0x000004 Error, and yes i see that you are having a 0x000002 but somewhere i read this could help that.) I just wanted to get rid of Clockwork Recovery Manager cause it was not working on my 3.2 rooted tablet, and thought that because i messed up teh whole image with playing around and upgrading and seeing how i could break the image without overclocking, i thought i should actually try and make it back to stock too. With this... I needed to do these steps...
1. Upgrade the Motorola drivers while the XOOM was plugged in, so then I would be able to use the Fastboot Correctly.
2. Download the correct roms for my tablet, (Wi-Fi is mine, just grab the one that fits your version and just follow along.)
3. Upgrade my ADB from google because for soem odd reason my fastboot did not like the xoom till i did that...
4. Used the STOCK CABLE. I can Confirm that the STOCK CABLE that allows you to recharge the phones, WILL WORK for this...
5. Once the ADB was set up, I restarted it, aka Hit the red X and then loaded it back up and then closed it again, just to make sure the services were updated somewhat...
6. Opened Command prompt and navigated to the folder that help the zipfile for the fastboot flashing guide (aka dirtymindedx's guide at the top), be using CD (Drive Letter):/location/of/the/folder/that/is/unzipped
7. I then checked over the information in the folder by using dir /a and then proceeded to read through the guide
7-1. A note here... I did the fastboot erase userdata instead, because I wanted to see if it would brick it again... (sorry, I was in a fowl mood with the world last night so I was waiting for it to get bricked so i had a reason to use it as an ice scraper on my car... (not like i would really do it... just wanted a reason for justification haha)
8. ???
9. Profit
This is only to get rid of a "already slightly bricked" device... which I had done after relocking the Rom that was not official to Motorola and now, after a few updates, i now have Android 4.0.3 for the Xoom that was OTA'ed, looking to see how easy it will be to root to reload my rpg game saves that i got caught up in (hence my disappearance from the forums haha...) but I hopefully helped you out in a direction to heads towards... and as long as you don't lock the boot-loader (which someone posted about it before i did...) you should be fine with any changes to the rom after the updates... Also, you can skip steps on this too... you can just flash the image and not the recovery menu and so forth, allowing you to keep other settings that are not part associated to the rom image.
Also sorry for the insanity in my words... I have been up for a good 36 hours with a half hour nap somewhere in there...
Having been a member on this forum for years I must admit it has been incredible the wealth of information I've gained from it. I've had all sorts of phones/pdas and I'ved used this site to help me get the most out of it and to help m "tame" the device and stop rubbish from the vendors being installed on there when I don't want it.
A couple of years ago I got an HTC Desire. Great phone although limited memory. I was happy with it. Didn't bother to root it or anything. I then got a Motorola Xoom. Didn't bother rooting that either. I got myself an HTC Sensation now. I decided one day that I was going to unlock/root the thing to see if I could do it.
Somehow, I think I managed it. I haven't really noticed a difference but then I haven't put a custom rom on it. On all my old Windows mobiles I always had a custom rom.
Now, going back to the Xoom. It's an original Xoom. I bought it in May 2011. It is running Android 3.2 after Motorola sent out an update. All is good.
However, I would like to have ICS on it. This is where my problems begin. I've tried following so many different how-to's on how to do this unyet none so far have worked. So, either I'm completely stupid or, the guides are not easy to follow or the process (that is always touted as easy) is not very easy.
So I am asking for help. Here is what I understand are the steps that I need to acheive.
1. I need to unlock the device
2. I need to install a recovery image
3. I need to install ICS
Questions: I *think* I have done 1. How do I check? After what I believe is a convoluted process, I have installed the Android SDK. I have the drivers for the device on the [Windows 7 64bit] PC and I can see it listed when I type adb devices.
Why do I need to unlock the device? What does the act of unlocking it do? When I followed this:
http://forum.xda-developers.com/showthread.php?t=1242241
I got to step 3. I typed in the first command:
adb reboot bootloader
After much faffing around I found out from another site I needed USB Debugging enabled. Nobody told me this. No, it isn't obvious that I need this.
The boot screen appeared and gave a message at the top and then I typed in:
fastboot oem unlock
I followed the instructions on the screen. I unlocked the device. It took a while. When it rebooted I found I had to set the device back up again as if it was the first time I'd used it. "Great!" I am thinking, I've lost everything. Thankfully I backed up what I wanted so I am not bothered. Slowly the apps appeared to come back after it synched with Google. I'm assuming stuff gets backed up somewhere.
I typed:
fastboot reboot
It rebooted.I typed:
adb reboot bootloader
It rebooted into the bootloader. Now here is where things started to go off track. I typed the next command:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
I get this:
unknown partition 'recovery-Tiamat-R4c-100611-1150-cwm.img'
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img'
So what now?
I cannot believe the process to unlock and flash a rom is so unbelievably convoluted. I've read dozens of walkthroughs, how-to's and forums and each one seems to be very similar unyet there is always something different on there to what I get on my screen or something doesn't happen quite the same way.
Here is what I am trying to acheive:
I have Android 3.2 on my Xoom and I would like it to be ICS.
We'll assume that I am completely stupid and need serious handholding to get to ICS. Is there anyone that can help with these seemingly simple steps?
One thing I keep reading is about the recovery image file. Is this related to Cyanogenmod? I am assuming as it is called a recovery image file it helps you get back when things go wrong.
Thanks and much love to the person that takes up the reigns and helps me out here.
Hi!
If you are rooted already that's pretty easy. But if not, try using LordAIOTool to root (yea it's mine and I think it's worth a try). After you are rooted flash a new recovery - download from development section - after, rename the recovery to recovery.img and then use the following commands on adb, fastboot and this recovery folder (simultaneously)
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Then after keep clicking the vol- after 2s of your tablet appears on Motorola logo. Then keep cycling until appears Android Recovery then press vol+
You are on recovery now, just select install zip from sdcard...
Good luck
Sent from my MZ601 using XDA Premium HD app
If you wanted your xoom rom'd, then you could try wesamothman's guide: http://forum.xda-developers.com/showthread.php?t=1717402 It is great for beginners and the experienced alike.
This is for the wifi only xoom MZ604. There is another guide by him i believe for the MZ602
Do I need to flash a new rom to get root on my MZ604? What is the easiest way to just root the stock 4.0.4 firmware? I have no desire for a different rom. I just want to root it.
Hey there.
If you don't want to flash a custom ROM and only want to root it, try this:
1) unlock your bootloader.
2) thru ADB, flash a recovery image.
3) thru Recovery, flash superuser flashable zip: http://www.4shared.com/zip/g3yzbrIa/...?cau2=403tNull
I ran the first couple of steps to unlocking. That is as far as I have got. As I said, I have tried so many of these walkthroughs and not one of them has all the steps. They all make an assumption somewhere along the line.
For example: xxlordxx replied with:
"If you are rooted already that's pretty easy".
I'm not, that is the problem.
Again:
1. adb reboot bootloader
2. fastboot flash recovery recovery.img <---- This didn't work and gave me the error I pointed out earlier and that is where it all stopped. Noone explains what to do when it goes wrong.
Anything passed this stage is irrelevant until I can sort out the problem above.
yosterwp, you mentioned wesamothmans guide. I will try that one as it looks a bit more "dummies guide-like" and it is for my exact device which is the MZ604 wifi only. I hadn't seen this one as it was only posted a couple of days ago
Just so I know, can someone anser these questions? I'm sure they're very simple but I don't know.
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
2. Is unlocking the same as setting s-off?
3. If not, what is the difference?
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
5. What is Cyanogenmod and do I need it or is this another custom rom?
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Thanks for everything so far. I will let you know how I get on with wesamothmans guide.
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
wesamothman said:
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
Click to expand...
Click to collapse
You did
Much love!
I have a sony Xperia S and i have rooted the phone. I've been trying to install some custom roms but i am unable to put the phone into fastboot because i haven't unlocked the bootloader. I'm assuming people have installed roms without the flashboot otherwise there isn't much point to rooting the phone without unlocking the bootloader.
I had a search around and found nothing. Any thoughts on installing roms with a locked bootloader?
AndrewMPhoto said:
I have a sony Xperia S and i have rooted the phone. I've been trying to install some custom roms but i am unable to put the phone into fastboot because i haven't unlocked the bootloader. I'm assuming people have installed roms without the flashboot otherwise there isn't much point to rooting the phone without unlocking the bootloader.
I had a search around and found nothing. Any thoughts on installing roms with a locked bootloader?
Click to expand...
Click to collapse
Actually, a lot of people around here should be able to help because a lot of them had a droid x, which had a locked bootloader. Of course, that device had a boot strap to over come the lock bootloader. Since you're rooted, have you installed a custom recovery yet? If you get the recovery on it, you may be able to flash a ROM of there is one available for you device...
Sent from my Nexus 7 using Tapatalk HD
mssam said:
Actually, a lot of people around here should be able to help because a lot of them had a droid x, which had a locked bootloader. Of course, that device had a boot strap to over come the lock bootloader. Since you're rooted, have you installed a custom recovery yet? If you get the recovery on it, you may be able to flash a ROM of there is one available for you device...
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
There is a problem with custom recovery and the xperia s, it doesn't support my phone apparently. My only other option is fastboot but i'm having serious driver issues with windows 8. I've followed a guide but it won't let me post this link up here yet.
my phone connects into fastboot for about 5 seconds and it just reboots. Apparently it's a common problem but i've tried everything and nothing is working haha! That guide was the closest i've got, i got the drivers to install and now my phone is coming up as "Andriod Bootloader interface"
I suppose that's some progress.
Have you had any experience with this issue?
AndrewMPhoto said:
There is a problem with custom recovery and the xperia s, it doesn't support my phone apparently. My only other option is fastboot but i'm having serious driver issues with windows 8. I've followed a guide but it won't let me post this link up here yet.
my phone connects into fastboot for about 5 seconds and it just reboots. Apparently it's a common problem but i've tried everything and nothing is working haha! That guide was the closest i've got, i got the drivers to install and now my phone is coming up as "Andriod Bootloader interface"
I suppose that's some progress.
Have you had any experience with this issue?
Click to expand...
Click to collapse
The fast boot issue on win8, yes. I don't even see toolkits working entirely like they should because of that fastboot issue. Fortunately, i have a Mac, so just use that for fastbooting usually (or minimal adb use). You could just obtain the adb, fastboot, etc. files from galaxynexusroot.com (or other places) and work around that fastboot problem with the command prompt, but the fact that you're recovery isn't supported is a problem. If there isn't a custom recovery for your device model, i don't see how you're going to be able to flash a rom. If you google "xperia s recovery" there are articles that go into detail about it (DooMRecovery looks like one that might work), but i have limited experience with that particular device. Wish i could be of more help. Maybe someone more familiar with your model will chime in...
Sent from my Nexus 7 using Tapatalk 2
mssam said:
The fast boot issue on win8, yes. I don't even see toolkits working entirely like they should because of that fastboot issue. Fortunately, i have a Mac, so just use that for fastbooting usually (or minimal adb use). You could just obtain the adb, fastboot, etc. files from galaxynexusroot.com (or other places) and work around that fastboot problem with the command prompt, but the fact that you're recovery isn't supported is a problem. If there isn't a custom recovery for your device model, i don't see how you're going to be able to flash a rom. If you google "xperia s recovery" there are articles that go into detail about it (DooMRecovery looks like one that might work), but i have limited experience with that particular device. Wish i could be of more help. Maybe someone more familiar with your model will chime in...
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
That app looks like it would do the trick! i just need to get this fastboot driver issue sorted first. Hopefully someone who has went through this can help me!
Hi everybody ! Ill try to keep it simple as I'm sure its covered somewhere but here goes ....
Ive been using my shield portable, rooted, for ages now no problems.
Like many Ive updated it in short ever since nothing whatsoever has worked properly , most annoyingly the screen doing backflips when you go near it and hundreds endless strange updates when rebooting.
Anyway I don't think you or I or any of us want to waste time trying to figure out why its done any of this but I just want to be able to fix it. I guess I'm going to have to start again somehow! its worth noting here that all my backup apps like Helium now don't seem to work.
After the update I of course ReRooted and it appears fine from boot loader , still says unlocked. but upon usage its clearly very confused about whether its rooted or not !
In short its useless. Advice please My kung Fu warriors
May your arrows fly straight and true
I have no idea about the various issues, but I would perform a factory reset, and clear cache and dalvik cache using at least 3 swipes per each function. The method of rooting I recommend is by flashing a zip of SuperSU from a custom recovery menu. CWM or TWRP are both available for the NSP. After flashing SuperSU, when you reboot and go into SuperSu you'll see that it's installed (locked down tighter) as a system app.
Downloads:
SuperSU (latest stable version) v2.65
CWM Recovery Menu (latest version) v6.0.4.4
TWRP (Modified recovery (based on TWRP v2.8.7.0)
Sorry. This is the best I can offer you right now. If this doesn't work I would reflash the stock images of whatever OTA you wanna be on. The images can be found @:
SHIELD Open Source Resources and Drivers. You'll need at least the platform-tools portion of the Android SDK (to use Fastboot to flash from recovery). A user friendly PC app that can basically do all this sort of stuff is Shield Ram v1.1. You might find that easier to use.
Oh and here's the latest Minimal ADB and Fastboot Drivers installer [v1.3.1]
If you need further help, let me know.
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
[/COLOR]
Marrhead said:
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
Click to expand...
Click to collapse
Yeah, pretty much the rule is generally "as long as you can still see the screen, it's probably fixable". Sounds to me like your best bet, would be to download the OTA you wanna be on, and flash a new install to your Shield. It's the quickest way from A-B. I'm about 99% sure that this would solve the problem (as long as you re-root it properly). Though if you have your reasons, you can try some of the other things first. You're welcome and let me know how things go!
So where does one get the latest OTA?
cheers
Marrhead said:
So where does one get the latest OTA?
cheers
Click to expand...
Click to collapse
I did link up the main Nvidia page that would lead to the OTA images, but here's a direct link to DL just the OTAs:
Edit: you can get there through the link I included in my previous post: SHIELD Open Source Resources and Drivers. I'm having issues with editing posts, and all sorts of odd **** with the link trying to post a more direct link. It's an Nvidia site, just scroll down to Shield Portable Recovery OS Images (something like that).
Unfortunately there are only Linux and Windows downloads available. I'm not sure what your best option would be, as you have a Mac. You could contact Nvidia support, and see what they say about it. Sorry, but I don't think I can probably help much more than this.When I contacted Nvidia support about a year ago, they were pretty helpful. Hopefully you get this sorted soon. Oh and the OTAs are flashed via a terminal/command prompt. So if you can emulate DOS on your Mac (which I don't see why not...DOSbox? maybe) then that sounds to me like the solution.
Ok , hit another brick wall. Im using a windows computer now, followed all the instructions i can find, and now the bootloader seems dysfunctional.
Ive got adb and fastboot and its recognising the device but once rebooted into bootloader which loads fine, the commands say no device found and nothing works in this mode.
If i hit recovery mode then a little dead android appears! poor little guy.
I tried shield ram but it had same problems, seems to run fine but cant find shield once its in bootloader...
Ive got the image zip of the update i want to flash but no idea if im doing it right- not sure how to use it.
Help!
First off, my tablet isn't bricked. I can boot it up fine. But when I try to install the factory downloaded software it just hangs on boot indefinitely. Similar things happens if I try to enter recovery. It goes fine until I have to press Volume ^, then it just freezes and I have to hold down the power key for 10 seconds. I've searched around and all I can find is threads from people stuck in a boot loop. Any help appreciated
A little more information. This tablet has been sitting for a while because it was such a disappointment. Before I decided I was fed up with it, it looks like I unlocked and rooted it. Iooks like I may have also tried to install Clockwork Mod on it. Trying to fix it has reminded me of why I stopped using it in favor of my nexus 7. The UI feels like it was designed specifically to make people not want to use tablets.
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
berndblb said:
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
Click to expand...
Click to collapse
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
RussTdesign said:
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
Click to expand...
Click to collapse
The first thing you should have done is upgrade your bootloader to the latest version. I would not actually use TWRP 3.0 for anything at this point if I were you. I have no idea if TWRP 3.0 works with that ancient JB 4.1 BL you got there, but I would not chance it. As a matter of fact, since you have to flash either stock rom or just the bootloader (and for both you use your recovery) I would highly recommend you flash an older TWRP version that is compatible with your BL. That combo - BL and recovery - is nothing you want to screw around with. You should go back to TWRP 2.4.1 or so.
TWRP Manager forced the latest TWRP version (developed for MM roms) on you and that's why I hate these apps! They do not check for compatibility at all....The proper way to flash a recovery is in fastboot and in fastboot only.
so I am going to give you a bunch of links and a general plan of attack, but you will have to do a fair share of reading.
First things is: Get fastboot working on your PC!!!!!! The first part of this guide I wrote way back tells you how: http://forum.xda-developers.com/showthread.php?t=2688891
Once you got that working flash TWRP 2.4.1 - instructions on how to are in the same thread. Reboot the tablet, then boot into TWRP.
Now flash the latest bootloader (Packaged with a slightly younger TWRP version from here: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
Reboot the tablet, then boot back into TWRP.
Now you again need to update your recovery to a version you can use with a current rom. I'd recommend this baby and it comes in a zip you can flash in your current recovery: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Flash the Kang recovery, then reboot and boot back into TWRP.
Format your data partition in TWRP. It takes an hour or so but it does a great job of leaving you with a clean slate for the new rom and is required before you flash a major change (which you are doing in any case).
Now you are ready to flash a rom.
I am going to recommend a really old one and a really new one. There are plenty of others to choose from in the Development section, but none of them is still under active development.
CROMi-X Resurrected. Based on Asus stock anno JB 4.2.1 but modded and fine tuned to the gills. LMK still puts out an update now and then, but those are more fine tunings of the fine tuning. Very slight changes - nothing major is going to happen here anymore. But it's a very stable and well working rom for those that actually like the Asus interface. http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
KatshMallow by Timudru. Yeah, Android MarshMallow for the TF700. Most Android users are still dreaming about MM and you can rock it on this ancient machine. And it's a beauty, just absolutely unbelievable what Tim has cooked up for this hardware. Trust me! Fantastic rom! http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
For both of them you should convert your data partition to f2fs which you can do in recovery. Instructions are here: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Actually, for CROMI-X Resurrected you don't have to do this - it's build into the rom installer.
You could try to short cut all this and just flash a new bootloader/recovery combo in your current TWRP 3.0. Maybe it works. Maybe it hardbricks your tablet. Nothing worse than trying to do something substantial (like flashing a bootloader) in an incompatible recovery....
Ok, now I shut up and let you read.
Have fun!
@berndblb thank you so much. I really appreciate you taking the time to help me out with this. This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions. I will get back later and let you know how it goes.
RussTdesign said:
@berndblb This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions..
Click to expand...
Click to collapse
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
berndblb said:
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
Click to expand...
Click to collapse
I have fast boot running and back-checked it via the fastboot devices. I downloaded twrp-2.4.1.0-tf700t.blob. the tried to load it. I keep getting a FAILED( command write failed (Invalid Argument)). Any thoughts
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Got fastboot running properly on my work computer with windows 7. I've gotten everything installed up to formatting the data partition. Doing that now. Super stressful & hard not to mess with it while it makes its way through a hour long process.
What did the trick to get fastboot working?
berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Looks like I got it sorted. Decided on going with the KatKiss rom. And the performance is night and day. Thanks so much for all your help. Next time I will probably do more reading before I try anything more... But then again I tell myself I will read the instructions before I start assembling ikea furniture & never do. So only time will tell. Anyway. Thanks again.
berndblb said:
What did the trick to get fastboot working?
Click to expand...
Click to collapse
Installing it on a different computer. This one runs windows 7. My laptop runs windows 8.1, could be as simple as that. But who knows.