Anyone tested AOPP ROM? - Shield Tablet Q&A, Help & Troubleshooting

Has anyone tested the AOPP (Android Open Pwn Project) ROM for our Shields? I just came across it yesterday while catching up on the Pwnie Express site.
Link: https://wiki.pwnieexpress.com/index.php/Supported_Devices
Note: ROM is *not* for the K1 variant.
Would love to hear anyone's experience.

I was going to try building from source to get it to work on the K1, as from what I'm reading the hardware is essentially the same so there shouldn't be *too* many errors... Right?
Shield's in the mail, so I'll report back with results later. Will be super excited if it works.

equi_design said:
Has anyone tested the AOPP (Android Open Pwn Project) ROM for our Shields? I just came across it yesterday while catching up on the Pwnie Express site.
Link: https://wiki.pwnieexpress.com/index.php/Supported_Devices
Note: ROM is *not* for the K1 variant.
Would love to hear anyone's experience.
Click to expand...
Click to collapse
Seeing as how it hasn't been updated since August....

It's Alive!
Managed to get it up and running on the Shield Tablet K1, which I forsaw as it's the same hardware, minus one stylus.
However, I will say this - update the nVidia app/software before doing anything or you'll be stuck in a boot loop. It flashes the firmware to be compatible with the latest TWRP, which I found out after having to flash back to the 'fallback' base image from nVidia. Other than that, smooth sailing - though it does appear to have the 'random reboot' problem still, which I've seen a few people mention on the forums.
Now I just need some OTG cables and the fun can begin.

Question
c0rsana said:
Managed to get it up and running on the Shield Tablet K1, which I forsaw as it's the same hardware, minus one stylus.
However, I will say this - update the nVidia app/software before doing anything or you'll be stuck in a boot loop. It flashes the firmware to be compatible with the latest TWRP, which I found out after having to flash back to the 'fallback' base image from nVidia. Other than that, smooth sailing - though it does appear to have the 'random reboot' problem still, which I've seen a few people mention on the forums.
Now I just need some OTG cables and the fun can begin.
Click to expand...
Click to collapse
Are the random reboots that bad?
Also for a total newbie would you recommend this ROM?

It's ancient, why would anyone want to flash this?

Related

Viewsonic update released today

I just got back to my desk and had the notification that an update was available. I ran it and my GTablet is running noticibly faster.
Not sure what was all included, but it was a nice surprise...
I'm ripping it apart, now. 1800 on Quadrant, AB works (so they grabbed something from the new Tegra drivers), no Flash that I can see.
roebeet said:
I'm ripping it apart, now. 1800 on Quadrant, AB works (so they grabbed something from the new Tegra drivers), no Flash that I can see.
Click to expand...
Click to collapse
roebeet,
So this is apparently not the update (with Flash) that's suppose to be coming out mid-December (12/16?)?
Jim
well.....
well it would seem that the update really did fix some problems. Angery Birds now runs on the factory ROM (video driver improvement)
Fixed WPA Enterprise or EAP support?
the factory linked (G-market) seems to work now to.
(For TnT Lite users) I am underwhelmed -nothing I can see worth mentioning, yet. Not even a kernel update.
I'm going to release a TnT Lite 2.3.0 tomorrow most likely, but this is not the 3.0.0 I was hoping for. Maybe you can find a bug fix in there that I might have missed.
Hi,
On my new (just picked up) Gtab, settings=>About is showing:
Tap UI version: 1.0-2736
Kernel: 2.6.32.9-000000-10.8.2-dirty
Build: FRF91
Where is that on the revisions from Viewsonic (e.g., is it the original? Or an update?)?
The reason for the question is that I haven't configured WIFI yet, and am assuming that I'll get that notification when I do, and am trying to figure if I should do the new update or not?
Jim
Update failed.
After the update downloads and then reboots the gtablet, I get an andriod image with an exclamation mark. After power down the gtablet boots find and informs me that the update failed.
The only two customizations I have are:
Z4 Root
ClockworkMod
Does anyone have any suggestions on what I should do?
jimcpl said:
Hi,
On my new (just picked up) Gtab, settings=>About is showing:
Tap UI version: 1.0-2736
Kernel: 2.6.32.9-000000-10.8.2-dirty
Build: FRF91
Where is that on the revisions from Viewsonic (e.g., is it the original? Or an update?)?
The reason for the question is that I haven't configured WIFI yet, and am assuming that I'll get that notification when I do, and am trying to figure if I should do the new update or not?
Jim
Click to expand...
Click to collapse
Hi,
Any comments about the above? The reason for the question is that I'd seen comments about how slow the stock software was, but the tablet seems to be reasonably responsive (to me)...
Jim
Let me know when you solve this one. I have the same problem. I have looked all over Google and nothing about removal
hartTamale said:
After the update downloads and then reboots the gtablet, I get an andriod image with an exclamation mark. After power down the gtablet boots find and informs me that the update failed.
The only two customizations I have are:
Z4 Root
ClockworkMod
Does anyone have any suggestions on what I should do?
Click to expand...
Click to collapse
Hi, Have you tried contacting Viewsonic tech support?
Jim
Even though this update means nothing to my gtab, it certainly does increase my respect for VS. At least they are somewhat following through with what they say.
Wise. Yes, I will do that.
hartTamale said:
Wise. Yes, I will do that.
Click to expand...
Click to collapse
Hi,
This is an older thread:
http://forum.xda-developers.com/showthread.php?t=847653&page=4c
There are some posts saying that that older update doesn't install with CWM installed. Maybe that's your problem?
Jim
jimcpl said:
Hi,
This is an older thread:
http://forum.xda-developers.com/showthread.php?t=847653&page=4c
There are some posts saying that that older update doesn't install with CWM installed. Maybe that's your problem?
Jim
Click to expand...
Click to collapse
It doesn't - you need standard recovery to use their update process. Or, just grab it from here: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-3053-user.zip
and drop it somewhere and run cwm against it. It will work, but it will change cwm back to standard recovery.
roebeet said:
It doesn't - you need standard recovery to use their update process. Or, just grab it from here: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-3053-user.zip
and drop it somewhere and run cwm against it. It will work, but it will change cwm back to standard recovery.
Click to expand...
Click to collapse
Roebeet does this zip restore the gtab to completely stock?
Bought mine today, charged it up, downloaded the update....and now I am stick in a boot loop. Had not even tried to do anything yet, just getting it updated to the latest. Any ideas what I can do, or am I doomed already?
jfholijr said:
Roebeet does this zip restore the gtab to completely stock?
Click to expand...
Click to collapse
Yes, except the user data which should be retained. This link is straight from TnT Inc. and it's what they've been pushing down to devices today.
Just ran update, and it removed GMail, Gtalk,Maps, and.... Market.
in ADW the icons are there, but they say not installed
Oh Superuser icon same thing.

Help confirm full Root/Recovery/Rom process

My wife has finally decided she'd like me to put a custom ROM on her TF101. I have experience (both good and bad) on my phones and tablets, but she doesn't want hers "messed up." So, I'm a lot less comfortable taking chances with her device than I am with mine. She still loves her TF101 and uses it daily and I don't want to mess it up. Her TF101 is still stock, not rooted, and has the last available ASUS update on it (IML74K.US_epad-9.2.1.27-20120615).
Initially my research indicated this was going to be the quickest and easiest Root/Recovery process I've ever gone though! Download Razorclaw to the device, run it to get root. Download Recovery Installer to the device, run it to get CWM. Easy peasy mac and cheesy. But, Razorclaw seems to be gone. The link to the tool gives a Page Not Found error. Another link on that site outlines a complicated process with a bunch of adb shell commands that made me a little uneasy. Recovery Installer likewise is no longer available at the link given in the first post of that thread. There's a link to a mirror location later in the thread, but if it's not available from the person who made it, then I have to worry. I've also now realized that her firmware version is not compatible with those tools to begin with!
So with my reluctance to upset my wife, some outdated information floating around in the threads, I just wanted to confirm my current plan was the proper way to go.
Use the PERI-0.42 tool to root and install TWRP. I wish I could find a video or screen shots of the process so I can know what to expect. (Or should I use the "1-Click Transformer Root" tool? I'm thinking not as TWRP would be preferable to Rogue Recovery?)
Nandroid backup from TWRP
Flash ROM following ROM's instructions
That about it?
As for which ROM, Root-Box looks interesting, but it says the camera doesn't work and my wife uses the camera (and the CamScanner app) frequently, so that's a no go. So, I was thinking about Paranoid-Android or No-name CM10?
First, Razorclaw only works on a very few firmwares, and the .27 is not one of them.
I wrote a guide on rooting the TF here: http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
This uses EasyFlasher and APX mode. It does install an older TWRP, but if you replace the twrp.SOS file in the EasyFlasher "tools" folder with the latest official 2.3.2.3 file found here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob (rename to twrp.SOS and replace the file) then EasyFlasher will flash the 2.3.2.3. EasyFlasher will show the old version in the menu drop down, however it will flash the newer version. If you want TWRP 2.5.0.0 you will need to get it from the thread in the development section.
I have used Peri 0.4 in the past, and it is very easy to follow the prompts. I have not made a tutorial or video of it, but as I said it is pretty straight forward.
As far as the ROM to flash, I am using Domination right now and have flashed the RootBox one as well. At the current time the keyboard dock has little support for both of these ROMs. Many users have had issues with SOD and RR on the CM10.1 no-name. My favorite for stability and features is still TeamEOS 4. It has full dock support and is very very fast and stable.
I am actually looking to restore my EOS 4 Nandroid later today.
Easyflasher is about as no-brainer as you can get, I would recommend using that to install TWRP recovery (note: and update to a newer version as per above poster).
http://forum.xda-developers.com/showthread.php?t=1688012
I've used it with three different PC's and three different TF101's without any issues, and I've used it to revert to stock a couple times on mine.
As far as ROMs are concerned, I have had the best luck in term of a happy blend of fully-baked (everything works)/stability/compatibility/features/speed-smoothness with the EOS 4 ROMS and KAT kernals, though I have as of yet only given the latest PA ROMs (with halo) a quick look. I am admittedly biased on that front since I switched to EOS 3.0 long ago, but I also haven't heard of any complaints from my folks or a friend who are running slightly older versions of the EOS 4 ROM.
Some people say they aren't pleased with smoothness with the stock launcher in EOS (I run Nova Prime on mine and Nova free version on the other two I've helped "upgrade", seems quite smooth to me). I don't know if that is a perception issue, a difference in hardware, or maybe installed apps/widgets. Or if it is still even an issue.
The only issues I have had on mine (SOD's/RR's) in many months was with one short-lived version of the Kat Kernal, which was fixed asap. For me, it's just as stable as the last official ASUS ICS update, and way way more stable the the preceding one.
By all means, give them all a shot, but I have never really had a problem with using EOS as a daily driver.
Thank you, Gentlemen! That's just the sort of help and information I needed. I don't know how I overlooked EasyFlasher in my research.
I had the same firmware - I used PERI to root and went with EOS nightlies v118 and KatKernel v103. Best decision I ever made. Stable, fast and enough features to sink a battleship.
I overlock to 1400mhz using smartassV2 governor. IO scheduler is set to 'sio' (settings->EOS control center->syste,->Performance settings). Since then its been a dream to use, no lag, no waiting. I stuck the dolphin browser on for good measure. Since all that was done, its smooth, fast and really enjoyable. To think a week ago I was ready to sell it and get something new, no need to do that now!
good luck!
About a month ago I had what I thought was a hardware issue with my microSD card reader and started a thread in this subforum about that. Someone suggested I try flashing a custom ROM before I try replacing hardware. Long story short I am now running TeamEOS + Kat kernel and everything is great. Tablet is faster and more stable than it ever was on stock and its nice to be running JellyBean. Only warning, you'll need TWRP not CWM to flash ROMs using Android 4.1+ but otherwise there really isn't too much to worry over.
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
I got my wife set up with the Team EOS 4 ROM last night. I ended up having to use PERI instead of EasyFlasher. I couldn't seem to get the tablet into APX mode. Vol UP + Power either did absolutely nothing, or the PC just couldn't "see" the tablet in APX mode. It could see it just fine upon regular boot, and I got the "new device" ding as soon as it started booting, but nothing when trying to enter APX. Vol DOWN + Power, then Vol UP to enter RCK mode brought up the "dead" android with the red triangle for a few seconds, then it rebooted.
But, PERI worked like a charm to root and install TWRP. Then I flashed TeamEOS 4, and she went to work setting it back up.
Thanks for the help!!
HeathicusF said:
I got my wife set up with the Team EOS 4 ROM last night. I ended up having to use PERI instead of EasyFlasher. I couldn't seem to get the tablet into APX mode. Vol UP + Power either did absolutely nothing, or the PC just couldn't "see" the tablet in APX mode. It could see it just fine upon regular boot, and I got the "new device" ding as soon as it started booting, but nothing when trying to enter APX. Vol DOWN + Power, then Vol UP to enter RCK mode brought up the "dead" android with the red triangle for a few seconds, then it rebooted.
But, PERI worked like a charm to root and install TWRP. Then I flashed TeamEOS 4, and she went to work setting it back up.
Thanks for the help!!
Click to expand...
Click to collapse
Awesome!
Check out my FAQ guide on EOS 4 to help explain many questions you may have, and how to set it up the way you (or your wife) likes.
let us know how she gets on with it ,it really is a great rom my tab has never been so quick i use nova launcher and dolphin overclock it in setting to 1400 i have mine on 1504 and still see good battery life ,,,,,,install goo manager from play for updates to rom and also pimp my rom is good for a few tweaks here and there ,,but first when its all set up and working good MAKE A BACK UP i always make back ups as i go along i have 2 all the time only takes 320 seconds ,,,,,enjoy
Sent from my Transformer TF101 using xda premium
She told me last night that she really liked the new ROM, so I think we have a winner. I like it too and wish it was available for the TF700 I recently got!
HeathicusF said:
She told me last night that she really liked the new ROM, so I think we have a winner. I like it too and wish it was available for the TF700 I recently got!
Click to expand...
Click to collapse
[AOSPA-4.2.2][June 13,2013(build #4)]ParanoidAndroid-3.6 | HALO IS HERE
[KERNEL][CM10.1 PA Liquid]bryce[overclock, gov, sched][VER 4.0][04/05]
Glad it was a smooth process. The TWRP install via peri worked? Did you use 2.5 or 2.3?
Thing O Doom said:
[AOSPA-4.2.2][June 13,2013(build #4)]ParanoidAndroid-3.6 | HALO IS HERE
[KERNEL][CM10.1 PA Liquid]bryce[overclock, gov, sched][VER 4.0][04/05]
Click to expand...
Click to collapse
I tried that ParanoidAndroid and it wouldn't get past the boot animation. I didn't try that Kernel, or an older non-Halo'd version of PA.
Thing O Doom said:
Glad it was a smooth process. The TWRP install via peri worked? Did you use 2.5 or 2.3?
Click to expand...
Click to collapse
Yep, the TWRP install via Peri worked flawlessly. It was vesion 2.5 of TWRP (Peri v0.42)

Cyanogen mod ROM repository

Hi guys, been off the scene for quite a while, so please forgive me if I'm not really up to date with the latest.
I own a OPO anad currently I have Cyanogen 12.0 installed. Lately my phone started to play up, not sure if I got some kind of malware but I thought it was a good occasion to update my ROM. Historically, I've always used CM but they seem to have disappeared completely (they used to have a nice website with all the phone models and the corresponding compatible ROMs, but I suppose that since when they went out of business things might have changed quite a bit). Can they be found somewhere? If not, I'd appreciate any advice on what ROM would be good to have - considering though that even my Teamwin Recovery needs updating as somehow it thinks I'm on an older version of android.
Cheers
duratto said:
Hi guys, been off the scene for quite a while, so please forgive me if I'm not really up to date with the latest.
I own a OPO anad currently I have Cyanogen 12.0 installed. Lately my phone started to play up, not sure if I got some kind of malware but I thought it was a good occasion to update my ROM. Historically, I've always used CM but they seem to have disappeared completely (they used to have a nice website with all the phone models and the corresponding compatible ROMs, but I suppose that since when they went out of business things might have changed quite a bit). Can they be found somewhere? If not, I'd appreciate any advice on what ROM would be good to have - considering though that even my Teamwin Recovery needs updating as somehow it thinks I'm on an older version of android.
Cheers
Click to expand...
Click to collapse
Firstly,this should be in QnA..
Secondly,
For latest recovery,
https://forum.xda-developers.com/oneplus-one/development/recovery-twrp-3-0-3-k1-t3563692
Recommended rom- https://forum.xda-developers.com/on...m-kernel-unofficial-lineageos-14-1-3-t3626403
thanks, do I need to install the recovery first and then the ROM? Also, are there any instructions for the recovery here or should I have a look on the net?
thanks
duratto said:
thanks, do I need to install the recovery first and then the ROM? Also, are there any instructions for the recovery here or should I have a look on the net?
thanks
Click to expand...
Click to collapse
Yes,to flash recovery the process is same as you did for the previous Twrp that is now on your device.

Samsung Galaxy S Relay most current CM ROM and TWRP?

Hi All,
I have a two Relays that have served me well, and I enjoyed having them, but the time has come to pass them on to someone else. Before I do that, I'd like to update them to the most recent versions of stable-release software that is available for them.
For Cyanogen, I have:
cm-11-20150831 (this is stable)
cm-11-20160523 (this is a nightly build)
For recovery I have:
philz touch 6.48.4
I'd like to replace Philz with a newer TWRP, but the Relay is no longer listed on the TWRP website. I'm also wondering if there was ever a stable CM release newer than the one I have.
Does anyone have sources for the above?
Thanks.
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
mrigancb said:
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
Click to expand...
Click to collapse
Although I'm not a developer I have been working on my SGH T699 from T Mobile. You may already know of the JellyBean and before. Recently I've noticed new builds for the samsung Galaxy S Relay 4G like the Validus 5.0.2 or the Fat Toad. I haven't tried those yet I was trying for a higher version. With 8.0 Oreo it requires partitioning and I need to brush up on that. So I went lower to the 7.0 or the 7.1 Nougat. I started noticing a lot of broken or old links so I had to resort to fishing the internet for most of the packages apparently lost in XDA. I pretty much have all of them and was just starting to try a few out when I ran into problems like I want to keep using the keyboard and Wifi calling or a related Wifi issue. It also crashed, went into bootloop or even soft bricked within a few days. The Roms and packages I've found are highly unstable and I see many had flashing issues. So far I've been tricking my device into taking the flash and even then it doesn't hold long. I'd like 6.0 MarshMallow if I can, maybe 7.1 if they ever get stabler that'd be great. But so far the ROMs for the Galaxy S (relay) are fairly horrible to say the least. I get the impression these so-called developers aren't testing their ROM creations more than 5 minutes and then handing them off to noobs who may be very likely to brick their device trying to get it in and running, only to have it crash repetedly! Or worse, hard-bricked.
I like this device. I think I'll keep working on it.
Casper Young.

Original Recalled Nvidia Shield tablet help

Hi
I have an original Shield Tablet, When Nvidia recalled the tablets I got a new tablet but kept the old one, At first I didn't use the new one, I only used the old one because I thought that if I used the new one the old one might trigger the Kil switch from Nvidia. One day the tablet simply stopped working, I was able to load into recovery mode/menu and do a factory reset but no luck, I don't remember if it was stuck at a black screen or stuck on the Nvidia logo but was one of those.
So after that I just stored the tablet and started using the new one that Nvidia sent me.
It's been a few years since that and the new tablet got stolen a couple years ago and today just out of curiosity I charged the old tablet and IT WORKED!. It booted up. It has the factory reset that I did.
So now I would like to use that tablet but I really don't know how to procced. Is it safe now to update the tablet? Nvidia still delivers the killswitch? what can I do to keep using the tablet without having to worry about some kind of auto update?
The tablet is at Android 7.0
with Shield tablet software version 5.2(24.29.404.153)
I would really appreciate the help. thanks!.
Hi
When your Tablet is really on the Killswitch List which it must be when you get a new one
(you can check it here to be sure : http://shield.bogdacutu.me) you have to avoid turn on Wifi and install a Custom Rom first. Which one depends how you want to use the Tablet. If you want it snappy and stable you should go with Unofficial Lineage OS 14.1 Rom from Saint2k which you found here : https://forum.xda-developers.com/sh...om-lineageos-14-1-15-1-shield-tablet-t3950786
Its based on Android 7.1.2 and everything works well except the Nvidia Games App (Geforce Now) because it doesnt connect to the nvidia server and loggin is not possible.
He also offers a Lineage OS 15.1 which is based on Android 8.1 . But as i know there is still a Issue with the Hardware Acceleration.
The AOSPExtended 5.8 Rom from Triodexe is also based on Android 8.1 and has working HW Acceleration. But also Nvidia Games App doesnt work ( You can start it and log in but it crashes when you start a Game)
His AOSPExtended 6.7 Rom is based on Android 9 and should work with the Nvidia Games App but i didnt tested it already.
Now we come to the Battery it is Highly recommend to change out the faulty Battery first because Nvidia Recalled those Batteries for a Reason. How you do it you can see here : https://forum.xda-developers.com/shield-tablet/help/replacement-battery-2018-t3788666
I also did it last week on one of my Tablets and its not too hard if you have access to a solderiron.
I hope this was helpfull and dont hesitate to ask if you have more questions.
I'm in the same boat. accept my tablet has been on and i can get on it still I have verified it has the y01 battery. it was purchased off ebay and hasn't been updated. not sure what the person did to prevent it from being bricked but I would like to put lineage or AOSPExtended 6.7 Rom on it. I'm not sure where to start. can someone point me in the right direction? btw the bootloader is unlocked and its currently running android 7.0. my son used it for the last year to watch youtube and what not on. the first instructions to AOSPExtended 6.7 Rom says to update to the newest firmware and I'm afraid that will brick it. any help is appreciated in advance.
dohcdragon said:
I'm in the same boat. accept my tablet has been on and i can get on it still I have verified it has the y01 battery. it was purchased off ebay and hasn't been updated. not sure what the person did to prevent it from being bricked but I would like to put lineage or AOSPExtended 6.7 Rom on it. I'm not sure where to start. can someone point me in the right direction? btw the bootloader is unlocked and its currently running android 7.0. my son used it for the last year to watch youtube and what not on. the first instructions to AOSPExtended 6.7 Rom says to update to the newest firmware and I'm afraid that will brick it. any help is appreciated in advance.
Click to expand...
Click to collapse
try installing anyway then, do not update

Categories

Resources