Related
Updating my friend's stock Tigerdirect G-Tab via OTA updater to what it says is:
Version 1.2-4349
This came up after the 3588 update when I opened the updater again.
So what is different?
lllGurulll said:
So what is different?
Click to expand...
Click to collapse
The update notes are:
-Adobe Flash Support in the Browser
-Support for an external Docking station
-Support for USB keyboard and mouse
-Support Weather for international cities
-Support for Spanish and French languages
-Lock screen that optimizes power consumption when idle
Wondering if there's a clockworkmod style recovery in this like what was in the pulled 3991 update.
Volume up while powering on to check it.
interesting.
This is the first I've heard of this version. I wonder if it has all the changes from the previous (now pulled) version 3991
Anyone want to make a quick video of the new stock with the enhancements?
Sent from my GT-I9000M using XDA App
going back to stock to check this out
Everyone be VERY careful, please
I didn't get this earlier today - but it's showing up now on my 3588 stock device.
Let us test it first, as this is their first 1.2 release and we want to check that bootloader. Thanks!
I know what I'm doing, tonight.
Btw, the release notes:
- Flash
- Dock support
- USB KB AND mouse support
- Spanish / French language
- Lockscreen
This is the one we've been waiting for.
updated my gtablet:
very good lock screen
Native Adobe Flash player browser
added Spanish and French
Energy saving screen
roebeet said:
I didn't get this earlier today - but it's showing up now on my 3588 stock device.
Let us test it first, as this is their first 1.2 release and we want to check that bootloader. Thanks!
I know what I'm doing, tonight.
Btw, the release notes:
- Flash
- Dock support
- USB KB AND mouse support
- Spanish / French language
- Lockscreen
This is the one we've been waiting for.
Click to expand...
Click to collapse
I know what I'll be doing; patiently awaiting your verdict on this update. =]
Updating as we talk . let's see what it bring to us...
Important, please read
I just went back to 2967, and I'm only seeing 3588 as an update.
I think 3588 is a gateway ROM, which is what I suspected last month. If you update your stock device to 4349, please do NOT flash to any mods, after that (at least not yet). Please let us test this, first - give me about an hour to run a few scenarios.
I will explain the reasons for this, as I do my tests to confirm what's going on.
EDIT: 2967 stock to 4349 stock causes a soft-brick. I think we have the same bootloader issue. Still running tests.
Thanks!
Updateing now. Wonder how much this will be like two tap x?
roebeet: Love your work man.
This is my first post ever and I just wanted to say thanks to all the Dev's out there.
Made some spelling mistakes and couldn't edit this post for five min.
Thanks Roebeet!!! I feel like you made this happen.
hmm for some reason i can boot after i use nvflash to go to stock...its stuck on the tnt screen...any ideas how to get past that??? I am coming from the Vegan GB RC1 rom
Its not bad, my only issue at the moment is long holding on the desktop and trying to change the wallpaper gives me an error. The on screen keyboard is definitely faster though.
I never got much chance to play with the previous builds, so I can't give comparisons. I had an issue where everything came to a halt. I had to to a hard shutdown. When it rebooted, I had to reinstall everything I downloaded from the Amazon Appstore. Seems to be working fine now.
rbansal2,
It takes a long time to get past the Tnt screen. If being patient doesn't work, you will need to load or flash CWM and go in and do the repartition, wipe dalvic cache, fix permissions, wipe cache, wipe/reset factory data routine to clean the tablet up.
Then reflash stock again and see if you don't get a usable base to OTA up to 3588.
Rev
P. S. -- This was a quik note so if you don't remember, ask me.
Seems good to me! Of course I like the stock tnt setup
I didn't play with custom roms because they looked like my tab was a giant phone most even had a phone icon.
rbansal2 said:
hmm for some reason i can boot after i use nvflash to go to stock...its stuck on the tnt screen...any ideas how to get past that??? I am coming from the Vegan GB RC1 rom
Click to expand...
Click to collapse
You'll probably need to repartition the sdcard. You can install clockworkmod using the microSD method or nvflash method and then use it to repartition to 2048 and 0. Remember that repartitioning will delete everything on the user partition (what's called "sdcard" in the rom). Back up your data before doing this.
I had this same problem a while ago after a nvflash and that's how I fixed it.
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)
I just bought a TF700T and immediatelly decided to install a Custom ROM. I had a Motorola Xoom before, so I recognize that was a monster hard to brick, but in my first hours with this new child, I'm suffering quite a lot, so I decided to ask for help.
First, the tablet was at Android 4.1. I unlocked the booloader, then I installed a new Recovery Menu. From what I read, it seems that TWRP is the recommended one recently, so I took it (version 2.6.3.1).
In there, I tried to install a Custom ROM, PAC-man, I downloaded a non nightly image, a little over 170MB (So I guess it's full and not just some random update), wiped the tablet (Full), flashed, restarted and the custom loader started, but soon it froze and restarted. It was the first infinite loop.
Then I decided to get the nightly image. Did the same thing, wipe, flash, restart, got the same results.
Then I gave up from PAC-man, and got BAM Android. Got their RC version, wipe, flash, restart, loading screen, freeze, and restart loop.
So am I forgetting something that should be done for the TF700?
ssj4maiko said:
I just bought a TF700T and immediatelly decided to install a Custom ROM. I had a Motorola Xoom before, so I recognize that was a monster hard to brick, but in my first hours with this new child, I'm suffering quite a lot, so I decided to ask for help.
First, the tablet was at Android 4.1. I unlocked the booloader, then I installed a new Recovery Menu. From what I read, it seems that TWRP is the recommended one recently, so I took it (version 2.6.3.1).
In there, I tried to install a Custom ROM, PAC-man, I downloaded a non nightly image, a little over 170MB (So I guess it's full and not just some random update), wiped the tablet (Full), flashed, restarted and the custom loader started, but soon it froze and restarted. It was the first infinite loop.
Then I decided to get the nightly image. Did the same thing, wipe, flash, restart, got the same results.
Then I gave up from PAC-man, and got BAM Android. Got their RC version, wipe, flash, restart, loading screen, freeze, and restart loop.
So am I forgetting something that should be done for the TF700?
Click to expand...
Click to collapse
Your on 4.1, thus you have 4.1 bootloader. Those roms require a 4.2 bootloader. My recommendation would be to read through CROMI-X thread from sbdags for detailed instructions for upgrading.
JoinTheRealms said:
Your on 4.1, thus you have 4.1 bootloader. Those roms require a 4.2 bootloader. My recommendation would be to read through CROMI-X thread from sbdags for detailed instructions for upgrading.
Click to expand...
Click to collapse
Oh, what a relief, thanks for the extra note, I didn't knew even the bootloader has versions, but it seems that now I understand another doubt that I had, though unrelated to this case.
I'll give it a look, at first I was looking at the latest Xenogenesis 5 thread, but I just saw the previous version (4.7.0 - http://forum.xda-developers.com/showthread.php?t=2223492 ) and seems like I found my answer in the first post. I'll try it tonight.
Thanks for fast answer
Yeah, it worked, thanks.
Just installed the bootloader, and the ROM worked.
Ok first, I did a lot of research into the topic and spent more than a few months in thinking it over and seeing if I wanted to attempt this. In a day long research fest, I finally decided to just try rooting and installing my daily-driver Nexus 7 2013 Wi-Fi with CyanogenMod. I chose a method that wasn't too daunting, using the Nexus Root Tools to push the CM rom and finally into working... I used RootJunkie on YouTube, "How to Flash a rom with the Nexus Root Tool Kit plus make a Backup with one click" as a refrence, watchign and rewatching the video and all he referenced over and over.
I loaded the zips into the "Flash Zips" section (It loaded the GApps zip in first and then the CM image). It seemed to install without a hitch except the GApps weren't there. Figuring that it installed the GApps first and then wiped them, I redid the flash with the CM first and the GApps second. Now I'm stuck in the Cyanogenmod loading screen. Problem is, since it's hit the point where it installed everything and hasn't let me into the device, I haven't been able to enable USB debugging. Now the computer isn't able to recognize the device at all and I cannot push just the CM image to fix it nor can I restore factory since the computer doesn't recognize it.
I've attempted to boot into recovery mode, which just results in the android laying on its back with a red ! in a triangle over it. I'm sorry if this makes no sense but I'm slightly panicked because I can't afford to have this thing professionally fixed nor replace it at the moment and I use this tablet daily. Is there something I'm missing? I'm going to lay down for now and try to calm myself, letting the thing sit at the loading screen, hoping that it'll let me in after a while. What options do I have, I'm sorry if this is the wrong place, the wrong crowd... I've just browsed quietly and used XDA as my source for information for everything from rootig my first device to this and it seems I've overstepped my abilities in this.
Problem solved
I stepped away from my computer and tablet for an hour or two to calm down from a panic I was in and found that it let me into the bootloader finally where I flashed the stock image and then restarted the process.
I discovered my problem in trying to use the 'stock' level of GApps from opengapps when the Cyanogenmod wiki pointed directly for the 'nano' version. Sorting out a silly wizard crash later and my tablet is happy, healthy and working much better than the stock at the moment aside some setup I need to do.
Thread closed as OP solved his issue
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!