Calkulin's ROM and 3991 - G Tablet General

Does Calkulin's ROM have the same potential issue as the TwoTapsX ROM in that it is running on the 3991 firmware? I was planning on flashing my tablet with it, but might just go with Vegan if that is the case. However, soft bricks don't scare me. I have hacked almost every electronic device that I own (ATV2, iPhone, Wii, etc) and I am a programmer. Anyway, if the only risk is a soft brick I still think I may go with Calkulin's.

tsm26 said:
Does Calkulin's ROM have the same potential issue as the TwoTapsX ROM in that it is running on the 3991 firmware? I was planning on flashing my tablet with it, but might just go with Vegan if that is the case. However, soft bricks don't scare me. I have hacked almost every electronic device that I own (ATV2, iPhone, Wii, etc) and I am a programmer. Anyway, if the only risk is a soft brick I still think I may go with Calkulin's.
Click to expand...
Click to collapse
Tmk, no. His is similar to to my TNT Lite 4.3.0 / 4.4.0 - old bootloader / kernel, but a 3991-based system image. Risk of brickage is much lower because of that.
The only full mod based off 3991 was TNT Lite 5 / TwoTapsX.

running it for as long as it out and have 0 issue ... run it with this kernel (http://forum.xda-developers.com/showthread.php?t=895825) make it sleep and wake up as a breeze

roebeet said:
Tmk, no. His is similar to to my TNT Lite 4.3.0 / 4.4.0 - old bootloader / kernel, but a 3991-based system image. Risk of brickage is much lower because of that.
The only full mod based off 3991 was TNT Lite 5 / TwoTapsX.
Click to expand...
Click to collapse
Thanks roe. I have been lurking ever since I ordered the G-Tab, though this isn't my first rodeo. I have used the other device forums for previous ROMs etc in the past. And just so you know, I will NEVER blame a mod dev for me bricking my device. In all reality, I have only hard-bricked one device of the almost one hundred I have modified (the wii homebrew is still my favorite hack). That lovely broken device was one strange WRT-54G when I put on DD-WRT. I had done it dozens of times before and this one time, no go
Maybe if I get some time away from work projects I will get in to Android development, not only apps but core OS. Thanks for all your great work.

I really don't get all that bootloader stuff. Maybe I'm overlooking the obvious, but all it does is it gets loaded by whatever our devices use as a bios and then load the kernel (or recovery kernel) that sits in a partition. If you don't change your partition, why change the bootloader?
Whatever the case may be, that rom runs fine on my tablet. Flashed with clockwork.

magqccom said:
I really don't get all that bootloader stuff. Maybe I'm overlooking the obvious, but all it does is it gets loaded by whatever our devices use as a bios and then load the kernel (or recovery kernel) that sits in a partition. If you don't change your partition, why change the bootloader?
Whatever the case may be, that rom runs fine on my tablet. Flashed with clockwork.
Click to expand...
Click to collapse
Seems to be heavily linked to your kernel (the latter is compiled with the former in mind). The reasons why are over my head, but suffice it to say that sometimes a vendor might require a bootloader update with their stock ROM update.
This has been the case with recent Notion Ink Adam updates, as well as that GTAB 1.2 dev branch (UAT build 3991). Think about it -- why would the vendor put it in there if they didn't want you to have it? They'd sooner just leave it out, if it wasn't needed for some reason.

roebeet said:
Seems to be heavily linked to your kernel (the latter is compiled with the former in mind). The reasons why are over my head, but suffice it to say that sometimes a vendor might require a bootloader update with their stock ROM update.
This has been the case with recent Notion Ink Adam updates, as well as that GTAB 1.2 dev branch (UAT build 3991). Think about it -- why would the vendor put it in there if they didn't want you to have it? They sooner just leave it out, if it wasn't needed for some reason.
Click to expand...
Click to collapse
Apple computers are a perfect example of the bootloaders being tied to their kernel and underlying OS. Old bootloaders and ones like GRUB are flexible, but that is not necessarily the norm anymore.

I have had a serious issue for me with Caulkins rom. I play with emulators all the time especially CPS2HD.
I use WiiMotecontroller to link my classic wirless controller to my GTAB via bluetooth.
I was recently on TNT Lite and oppted to try out Caulkins. Caulkins is fast and great but freezes everytime I use Wiimotecontroller to try and play roms.
I turn on the bluetooth and link my controller and Poof,,, freezes and have to reboot.
Anyone have any ideas?
Thanks, Rob

Related

[ROM RETIRED] TwoTapsX alternative 1.2-based firmware

THIS MOD HAS BEEN RETIRED. This was a pre-release version based off of the vendor's UAT 3991 build. It was pulled shortly after it was released due to a large number of soft-bricks, and has never been reactivated. I am leaving this post up as a reference, only - and also leaving the supplement link up for current users who still need that. ​
----------------------------------------------------------------------------------
TwoTapsX is a an EXPERIMENTAL ROM for use with the GTablet. It is based off the vendor's "1.2" dev branch which replaces the bootloader on the device. What this means is that 1) you need standard recovery (not clockworkmod) to upgrade to the ROM and 2) you need standard recovery to backout to an older mod or old stock. Please read the instructions CAREFULLY and FULLY. Failure to do so can cause you to soft-brick you device. Viewsonic does not support this mod and will not help you!!!
---------------------------------------------------
REQUIRED Pre-requisites
If you are coming from a 1.0.1 or 1.1 stock ROM or mod, you need to be running the 3588 stock ROM, ESPECIALLY 3588 recovery. In other words, you need to be a complete stock device as that causes the lowest risk of soft-brickage.
Recommended Pre-requisites
1. Setup and learn how to use nvflash. This is your backout in case something bad happens, so I would highly recommend you understand how to use this, in advance. Link details: http://forum.xda-developers.com/showthread.php?t=861950. nvflash is specific to Tegra 2 devices only.
2. Setup and learn how to use adb. This is a standard Android tool that will give you a remote shell into the device. This is helpful to push and pull files, and do general troubleshooting. For example, you can do a data wipe within adb if your device boot loops by typing "adb remount" and then "Adb shell wipe data" and then reboot. A VERY helpful tool for anyone modding their device.
Information on adb and how to install it / use it can found in several areas in XDA, or on other Android sites. It's part of the Google Android SDK.
---------------------------------------------------
Installation:
The base mod has been PULLED, due to installation issues
---------------------------------------------------
Backout from TNT Lite 5 / TwoTapsX to TnT Lite 4.3.0 or 3588 stock:
Pre-requisite: You MUST have standard 3991 recovery. If you installed the 3991-friendly clockworkmod (see references below), then you need to remove it. The easiest way to do that, at the moment, is to reflash to 3991 standard recovery, using the reference update.zip (see the References area). If you did not install cwm, then you have 3991 recovery already.
Once standard 3991 recovery is confirmed installed, you can use any of the following ROM's to backout to a "legacy" 1.1-based firmware: 3588 stock, TNT Lite 4.3.0 or gADAM 1.3.0. You would just use the standard instructions for these (ie. add the update.zip and recovery folders to the root of your drive, and reboot into recovery).
I have tested all of these scenarios and the backout does work. However, as always, there is a risk here so I would HIGHLY recommend that you setup and master nvflash BEFORE you attempt backing out. That's just in case the backout fails and you need an emergency procedure to unbrick your device.
TO STRESS -- DO NOT, under any circumstances, backout directly to anything other than 3588 stock, TNT Lite 4.3.0 or gADAM 1.3.0, nor use clockworkmod as you WILL most likely semi-brick your device!!!
NOTE FOR TNT LITE 4.3.x -- recovery will be broken, after the downgrade. In this case, just run the Recovery Pack and you can fix it (see the TNT Lite first post, for details)
---------------------------------------------------
Downloads:
TwoTapsX .902 pre-release SUPPLEMENT only: http://www.mediafire.com/?k5x5if1qoeeh8u0
md5sum: be43c8a02474a0984d5f292ad55e35d4
Note: This is JUST the supplement, for TNT Lite 5 / TTx users only! I have NOT reactivated the base ROM. It has been pulled.
---------------------------------------------------
Your device is bricked, what to do:
See this post for details on nvflash : http://forum.xda-developers.com/showthread.php?t=861950
---------------------------------------------------
Reference Links
- Clockworkmod bekit v.8 only (1.2-3991 friendly) update.zip (for technical users only -- ONLY use with TnT Lite 5.x, 3991 stock or TwoTapsX!!!!): http://www.mediafire.com/?ykn3jwq7kvegc4g
This is a replacement for standard recovery. It adds the ability to backup and restore system images, for example. WARNING: YOU CANNOT BACKOUT to 1.1-based legacy mods with clockworkmod, you WILL semi-brick the device if you try. If you already installed this, then reflash to 3991 standard recovery, as mentioned below.
- 3991 standard recovery update.zip -- ONLY use with TnT Lite 5.x, 3991 stock or TwoTapsX!!!!): http://www.mediafire.com/?ripr3c96h55alg0
This will add the 3991 standard recovery back on a TNT Lite 5 / TwoTapsX system. You'd need this if you wanted a functional recovery to backout to 3588 stock, TNT Lite 4.3.0 or gADAM 1.3.0.
Extra placeholder, for future use.
I assume the theme around the new name for the rom is the next generation, or the 2nd generation of the custom Viewsonic Tap-n-tap rom.
It's a sad day in mudville, but it's probably for the best. Let's get this party started....
Woo Hoo! I'm nvflashing back to stock just for the fun of loading it all over again!
Uh Oh, ready the F5
Tegra devices and their bootloader/kernel combination differences are such a pain. This means that without a newer patch, pershoot's kernels won't work, right?
Butch1326 said:
I assume the theme around the new name for the rom is the next generation, or the 2nd generation of the custom Viewsonic Tap-n-tap rom.
It's a sad day in mudville, but it's probably for the best. Let's get this party started....
Click to expand...
Click to collapse
The initial pre-release will be the exact same code as TNT Lite 5.0.0 and 5.0.1 - I'll even keep the supplement. All I'm going to do is change the name so as to pull it out of the main TNTL thread.
So if someone has TNT Lite 5.00 and loads up this supplement, it will work just fine. And the name gets changed, too.
rothnic said:
Tegra devices and their bootloader/kernel combination differences are such a pain. This means that without a newer patch, pershoot's kernels won't work, right?
Click to expand...
Click to collapse
Correct. This is like a "Black Box" - isolated and on its own.
As a virtual middle finger I am gonna keep the name tnt lite 5.0.1 until a new supplement. Or release. Forces the change!!!!hahaha!!!
sigvader said:
As a virtual middle finger I am gonna keep the name tnt lite 5.0.1 until a new supplement. Or release. Forces the change!!!!hahaha!!!
Click to expand...
Click to collapse
A new supplement is already coming. Flash 10.2 just got released and it's actually a newer version that what got leaked.
Now I have a BIG problem, which is the problem I was trying to avoid with TNT Lite 5, which is supporting yet another build. I might have to freeze TNT Lite 4.25 until I know what Viewsonic is doing.
Again, keep in mind that if you have TNT Lite 5.0.0 or 5.0.1 you CAN update to TwoTapsX .9.02 supplement, when I build it. It will definitely work.
I realise that many people have had a very difficult, or impossible, time moving up to TNT Lite 5.0.0, and that it seems to be a frustrating, hit-or-miss situation, but I, for one, like 5.0.0, and i'm sticking with it, for now, at least. Everything is working-- ui is snappy, market is relatively complete, with full stars, camera works in both orientations, etc. In addition, it may be that VS sees this direction as its path to "Honeycreams", and if so, then we're perched on the right branch to take advantage of it. If they should abandon this path, though, I believe (hope) I have nvflash all ready to go in Win 7 just in case I need to jump back into the original roms. From what I've picked up in the 5.0 thread, VS MAY be preparing to release an update soon, and this will tell us (maybe) where they're headed.
Hopefully in a few weeks, we will know and either TNT Lite is going to phased out, or this pre-release will. They won't be supported for long - one of them is going to die.
Thanks Roebeet for all your efforts to keep the VS Gtablet alive. I have loaded up your TwoTapsx v.9.02 ROM on my Gtablet and it seems to be very stable. Looking forward to what VS has in store for us next. Knowing you and the other developers will take whatever VS dishes out and make it better for our Gtablets.
Again, thank you for all that you do....
Gramps
I agree. .. will stay with 5 until (if) it dies. Then will grieve!
Hi Roebeet...
This is your instructions to "backout" of TTx (which is the same as 5.0.1)
Backout (ie. to old stock, VEGAn, TNT Lite 4.x, etc):
I have successfully backed out of TTx in two ways:
1- Re-run a stock ROM. Specifically, I tested 3588. STOCK is important, as the bootloader will be downleveled to the necessary revision.
2- nvflash, using bekit's 1105 image.
In the case of stock, you might get stuck in a boot hang due to the possible need to wipe user data. So, I would recommend running the update.zip off a microSD so you can install clockworkmod .8 (old version) to give you the ability to wipe data.
Once you have old stock back, you'll be able to install older versions of TNT Lite, VEGAn, zPad, etc. as the bootloader is downleveled again.
using the new cwm thats on it now(blue writings) can we wipe data and cache, then put 3588 update zip and recovery folder on internal sd and things will resort back to stock with no snags?
thxs
mike
mikesal57 said:
Hi Roebeet...
This is your instructions to "backout" of TTx (which is the same as 5.0.1)
Backout (ie. to old stock, VEGAn, TNT Lite 4.x, etc):
I have successfully backed out of TTx in two ways:
1- Re-run a stock ROM. Specifically, I tested 3588. STOCK is important, as the bootloader will be downleveled to the necessary revision.
2- nvflash, using bekit's 1105 image.
In the case of stock, you might get stuck in a boot hang due to the possible need to wipe user data. So, I would recommend running the update.zip off a microSD so you can install clockworkmod .8 (old version) to give you the ability to wipe data.
Once you have old stock back, you'll be able to install older versions of TNT Lite, VEGAn, zPad, etc. as the bootloader is downleveled again.
using the new cwm thats on it now(blue writings) can we wipe data and cache, then put 3588 update zip and recovery folder on internal sd and things will resort back to stock with no snags?
thxs
mike
Click to expand...
Click to collapse
That should work. It's VS stock recovery, not cwm (it just looks like cwm). I added 3588 stock as an update.zip, with the recovery folder and ran it and it worked for me. The only caveat is that you might need a data wipe, so try to do that before you reboot after the flash update. The reason why is because 3588 stock doesn't have a "user data wipe" option in its recovery, so better safe than sorry.
I'm actually going to update the first post with that, as I think it's pretty important. Data wipes between old mods and this new one are pretty critical.
I just upgraded my 5.0.1 to .9.02 and I still have flash 10.2.155.67, where's the upgrade?
thxs Rb...
TTX and TNTL
I know it was a lot of work, but splitting the two right now is probably a good decision for novice users. The TNTL allows users with CWM to continue to flash between roms and backups until they are ready for the plunge to TTX. Thanks for all your work.
olddocwhite said:
I know it was a lot of work, but splitting the two right now is probably a good decision for novice users. The TNTL allows users with CWM to continue to flash between roms and backups until they are ready for the plunge to TTX. Thanks for all your work.
Click to expand...
Click to collapse
Honestly, when one of the moderators brought it up it made a lot of sense. TNT Lite 5 was a tough one and I kept hoping things would die down, but they never did. It was getting tough to keep it going as a "released" mod. I also didn't release how many users were still on TNT Lite and the impact it would have - I underestimated the user problems it would create.
joe2262 said:
I just upgraded my 5.0.1 to .9.02 and I still have flash 10.2.155.67, where's the upgrade?
Click to expand...
Click to collapse
You need to wipe data to get it - that's because the shell script won't (or can't) run if Adobe is already installed.
Alternatively, you can sideload it - it's under /system/etc in the supplement zip. Or, remove the old version and reboot and the shell script might re-install it (I think).

FYI, TwoTapsX (TNT Lite 5.x) flip-flopping - latest is that it's pulled again

(At the request of management). Even with all the unsticking / mod intervention and warnings up the wahzoo, there are still a lot of user problems. It may return in a week , but for now it is PULLED. The moderators have hidden the thread, at least for the short term.
For those of you on TNT Lite 5 / TTx, just keep using it and no worries. Once we know where VS is headed, I will have a plan to either ask you to downlevel or upgrade. Again, depending on what they do.
EDIT: For those of you who had issues, could you please write up the steps you used before it failed? It would help everyone to understand why there are so many problems with this 3991 stock / TNTL 5 / TTx. From the posts and PM's I've seen, the majority have been either:
1- The device was flashed with clockworkmod to 3991/TNTL5/TTx and gets stuck at the birds or
2- The device was being prepped to stock 3588 and recovery was broken, after the 3588 reversion.
But I'm hearing that others might have applied all the proper steps and still had problems. We're trying to gauge just where the problem lies with this 1.2 UAT of Viewsonic's.
From my own device, I know that clockworkmod flat-out does not work. That's because the BCT partition is being touched by standard recovery, which clockworkmod does not replicate (and seems to be required). But as long as I have a clean 3588 stock ROM running on my device, I have not had an issue upgrading to 3991/TNTL5/TTx, it has worked for me 100% of the time.
Stock 3991 / TNT Lite 5.xx / TTx .9x backout instructions:
There are two way I know of to back out of these:
- Flash to stock 3588. This assumes you have NOT added clockworkmod and have standard recovery. I have done this several times and never had a problem. Stock 3588 link: http://forum.xda-developers.com/showthread.php?t=842000
- nvflash using bekit's 1105 image: http://forum.xda-developers.com/showthread.php?t=861950. This is still the best way to back out, as far as I'm concerned. You can do a full erase first, to wipe user data as well, thread is here: http://forum.xda-developers.com/showthread.php?t=974422
NOOOOOOOOO. Hopefully VS will decide what they are going to do by the end of the month. I am enjoying TnT Lite 5.0 with no issues at all. Thank you for all your hard work Roebeet, it is unfortunate that so many have had problems with this.
Damnnn, was about to install it
Really sucks that people have had problems maybe people should read and then re-read instructions instead of jumping into things and just assuming devs and mods can help them out. They have a life and dont think that after putting in all the work in to create something they want to hear from whiny a$$, irresponsible people that probably caused their own problem
Now people, like me, that wanted to install cant. nice.
thank roebeet tho and all the other g tab devs
I'm running two tap x. 9.0.2 with absolutely no problems. Never did have any problems from the beginning of 5.0.0. I'm am ferry close to being a noob, but I just had the instructions up on my laptop and followed them step by step. Will the new version of clockwork work to go back to 3588 if nessacery?
Thanks for all your hard work Roebeet. I barely use my laptop now that I have this tab.
One of the obstacles I've had in the last 2 weeks is that this is a UAT, not a released firmware from Viewsonic - so its validity is in question (and understandably so). If they release it with the same bootloader and upgrade requirements, it's going to shake things up here a bit.
I still think the odds are that they will - from their standpoint, they are only supporting stock users so, as long as they can ensure that a user is on 3588 stock, then the upgrade should work. In our case, many of the issues were either getting from a mod to 3588 stock, or using clockworkmod by mistake. Viewsonic doesn't have to worry about either of those issues.
But, there's still the X-factor -- everything is 3588 stock and the upgrade still fails. That might be what's holding them back.
bkbrod said:
I'm running two tap x. 9.0.2 with absolutely no problems. Never did have any problems from the beginning of 5.0.0. I'm am ferry close to being a noob, but I just had the instructions up on my laptop and followed them step by step. Will the new version of clockwork work to go back to 3588 if nessacery?
Thanks for all your hard work Roebeet. I barely use my laptop now that I have this tab.
Click to expand...
Click to collapse
No, clockworkmod won't work (even the new one) - if you wanted to backout to old stock (3558, for example), you'd have to use Viewsonic's recovery. Clockworkmod will kill your device, trust me on that. nvflashing to bekit's 1105 also works, that's how I've been backing out to old stock.
Hmmm
In the last 24Hrs, my gTab v.9.02 just decided to go totally nuts. Constant FC's, lockups, lost sound. Tried every fix listed on XDA, wiped /data , re-downloaded apps from Market instead of restoring with TiB; wotked for a little bit, then the same FC's. And random loss of sound.
Going back to 3558 and CWM and 4.2.5.
We'll see what VS throws our way.
Keep up the good work Mr.Roe!!!
roebeet said:
The backout, btw, is the same -- run stock 3588 and it will downlevel you back to the old bootloader. BUT, make sure it's standard recovery and not clockworkmod.
Click to expand...
Click to collapse
Perhaps you should post the method and files in this thread. I know that it's in multiple places, but it never hurts to have them handy in a thread that is this important. Just a thought.
TwoTapsX works great for me so far. Had TNT Lite 5.0.1 but it wouldn't run some apps correctly. Tried all the ROMS and they all had sleep of death problems. TwoTapsX works the best for me without giving any glitches.
TwoTaps .9.2
Thanks Roebeet for all you do here. I am finding this ROM easier to work with than any other. I have noted that periodically it will flash the home screen while I am working. Mostly this has been while in Dolphin Brower HD.
jholmes5 said:
Perhaps you should post the method and files in this thread. I know that it's in multiple places, but it never hurts to have them handy in a thread that is this important. Just a thought.
Click to expand...
Click to collapse
Good point, since the other thread is hidden.
So far I have installed both version and removed them a few time without issue but the last time I removed it...
I needed to re-flash and wipe a few time, it was booting into the launcher but flashing the screen like crazy...
but since the nvflash recovery doesn't erase the root of the device something was making the screen flash black and reload of the desktop repeatedly.
I was able to run root explorer (that survived the nvflash restore) and copied another rom (calkulin) and even there after using his erase tool and running all wipe available from clockwork and calkulin one after the other... (I load clockwork with the part9.img trick) I had to re flash twice until the desktop loaded properly without flashing..
I would like to find a tool that can erase and rebuild the WHOLE tablet...
I have away updated to 3588 thru the online download each time. Anyway I will hold to the current rom for a bit!
P00r said:
So far I have installed both version and removed them a few time without issue but the last time I removed it...
I needed to re-flash and wipe a few time, it was booting into the launcher but flashing the screen like crazy...
but since the nvflash recovery doesn't erase the root of the device something was making the screen flash black and reload of the desktop repeatedly.
I was able to run root explorer (that survived the nvflash restore) and copied another rom (calkulin) and even there after using his erase tool and running all wipe available from clockwork and calkulin one after the other... (I load clockwork with the part9.img trick) I had to re flash twice until the desktop loaded properly without flashing..
I would like to find a tool that can erase and rebuild the WHOLE tablet...
I have away updated to 3588 thru the online download each time. Anyway I will hold to the current rom for a bit!
Click to expand...
Click to collapse
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
manikin13 said:
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
Click to expand...
Click to collapse
It does not... if you install a custom boot animation it stay there... so it's not full even if after the unit doesn't even start (red text) it's not fully wiped...
I have used clockwork with the partition option, this seem to perform a full format with either the nvflash format or bekit recovery but I am not sure why we can't get this done tru the nvflash...
manikin13 said:
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
Click to expand...
Click to collapse
It's in my first post, as well. Run that nvflash first to erase the device, then the bekit 1105 nvflash to complete the process.
What seems to happen is that the old stock / new stock user data setups are not compatible. When going to new stock, it's not so bad because new stock has a better recovery. But when reverting, old stock has a crappy recovery with no user data wipe options. Even Viewsonic understood the limitations which is why they changed their recovery in this UAT of theirs.
I mentioned to jerdog that I wanted to see if I could port their new recovery to old stock (using an old kernel). If that works, we could conceivably offer a "bekit 1105 enhanced" version that adds it. This is better than clockworkmod in that it's the vendor's own recovery and includes the ability to wipe user data, calibrate the device AND update / downlevel the bootloader. For the purposes of getting users backed out if needed, it might be a critical piece of the puzzle.
EDIT: No go. The recovery functionality is actually IN the kernel, my bad. So it can't be ported over. Oh well.
You guys are GODS at this. Simply amazing what you are all doing with this G Tab. So I guess I'm one, of some lucky few, that ACTUALLY READ the install instructions for 5.0 and 5.0.1.
Glad I did because I love the market on this thing.
Eagerly watching what happens with Viewsonic......Any chance they did this as a step to make a Honeycomb upgrade easier? I doubt it since the original G Tab with OTA updates is still crippled.
First off just want to give my thanks to roebeet and the devs here at XDA. I've been running TnT Lite 5.0 / TwoTapsX ??? since the day I bought my Gtablet on 3/11 with no problems. On Friday the 11th I was itching for a Xoom somehow managed to find out Staples had the Viewpad 10 but not in store and somehow managed to end up finding out that Office Depot had the Gtablet for $379.99 in store. I read roebeet's at the time TnT Lite 5.0 thread several times before walking to my nearest Office Depot and brought home a Gtablet within minutes of reading that thread.
Out of the box from 2967 I went to 3588 through stock recovery and not OTA; and then did the same thing to go to TnTLite 5.0.0
I have successfully backed out of TNT Lite 5 in two ways:
1- Re-run a stock ROM. Specifically, I tested 3588. STOCK is important, as the bootloader will be downleveled to the necessary revision.
2- nvflash, using bekit's 1105 image.
In the case of stock, you might get stuck in a boot hang due to the possible need to wipe user data. So, I would recommend running the update.zip off a microSD so you can install clockworkmod .8 (old version) to give you the ability to wipe data.
Once you have old stock back, you'll be able to install older versions of TNT Lite, VEGAn, zPad, etc. as the bootloader is downleveled again.
Click to expand...
Click to collapse
My question to roebeet or anyone who has gone from TnTLite / TwoTapsX back to 3588 using stock recovery. I could swear the above quote from roebeet had an additional line about using stock recovery to run the 3588 stock rom and then wiping user data from stock recovery. From TnTLite 5.0.0 can I go back to 3588 using the stock recovery and wipe user data with the stock recovery after running 3588 but before rebooting?
Android system recovery <3e>
Wipe Data/Factory Reset
Wipe Cache Partition
Click to expand...
Click to collapse
If it is possible to wipe user data after flashing back to 3588 do I need to just wipe data or do I need to use the 'wipe cash partition' as well.
edit: never mind my rambling probably better to wait until we know what Viewsonic is going to do and at that point roebeet will let TTx users know how to proceed from TTx to whatever comes down the pipe from VS
I did have a line (I think in the TwoTaps thread) about reversion and wiping data before you reboot into 3588 stock. But, I tried this once myself and it didn't work.
Maybe I should make a special 3588 "mostly stock" with clockworkmod, as a backout solution (so that, if you get into a bootloop situation post downgrade, you already have clockworkmod installed to fix it - that could work). It's the "wipe data" option, btw.
But first, lets see what the vendor does - if they stick with this new bootloader then TNTL5 / TTx users might already be one step ahead of everyone else - you may not want to backout.
Using it since first release with no problems. I always read the entire first post as well as user issues prior to updating. There are probably many users that try before reading which can lead to issues.
I think this is a great ROM.
Sent from my GTablet-TwoTapsX using Tapatalk
I'm one of the ones who ran into troubles getting this to load and I honestly believed I followed all the instructions when doing so. I've tried mostly all of the custom ROMs and was on the Vegan experimental before loading TTx. Not sure what the problem was but nvflashing with or without recovery didn't take. Kept getting stuck in APX mode. I wasn't really worried since I could always get the tablet to take the nvflash so I just kept playing with it until lo and behold, I was able to enter the TTx recovery mode. Been working fine since. I really like this ROM but I definitely feel like the disclaimer is justified - if you're not into tinkering this isn't something you wanna try.
The only problem I've run into so far is that when I recover my Angry Birds file and run the app it FC's. Runs fine if I just install either version, but when I try to restore my saves by using TB, the app refuses to run. Weird. Other than that, no problems. I don't really like the default browser, but understand that it's required at this point. FLash works fine and I haven't had any issues at all with the market. Even found a few apps that were supposedly only available with XOOM builds.
Many thanks Robeet and hopefully we can get a more "idiotproof" upgrade process.
T
roebeet,
Where can we obtain the bekit 1105 file?
I remember seeing the name somewhere but don't remember seeing the D/L source.
Rev

[A700] Moving to CM10.1 - Some Questions

Nice forum you got here, i was a passive user since about a year and now i'm going to be active:
I have a iconia A700 and i'm thinking about flashing it with cm10.1. I found some tutorials and it seems to be not too hard to perform.
But before i do it, i have some questions:
1) What backup tool do you suggest? I want to keep all my files, programs and progam settings!
2) Is CM10.1 running smooth and good / better than the stock rom?
3) Someone tested the tapped out simpsons game on cm10.1 on the a700? It does not work with stock rom (maybe because of the resolution). Is there any chance to change the resolution with cm10.1 or maybe the game works fine without any change of settings?
I believe it's taking too much time to wait for an official 4.2 release and i don't like all these Acer Apps. So can you recommend flashing with cynagonmod?
1. Titanium backup. Though you need root, it's the best back-up tool you can get.
2. From my experience, I'd say yes. Though pawitp (the person who made CM possible) says the following:
pawitp said:
Performance may be worse than stock due to the additional navigation bar introduced in 4.2.
Click to expand...
Click to collapse
3. I didn't try it. I think there is a way to change the resolution, though when you've installed the CM ROM, you should try to run it first. I thought I read about changing the resolution somewhere in the CM forum, but I'm not sure how to do it.
Yeah, Acer said it's going to be there, but it's releasing somewhere in the summer.
I can certainly recommend CM. I had to get used to the new navigation buttons place, but you'll get used to it too, I'm sure.
I really like the OTA feature in it. You can get updates right on your tablet without having to reflash or stuff. I'm not sure if it'll install future Android version updates, but I think it's possible (like Android 4.2.1).

Do you really need the latest security patch? and other thoughts for newbies et al

By all means, read @Neffy27 's FAQ if you are starting out. even as a refresher for stuff you may have forgotten.
-But do think a bit about what you are doing:
-Do not modify your phone unless you are willing to toss it into the trash, as that could well be the result, no matter how well planned.
-Always have a spare on hand. I used my old Moto G3 when my MZP died suddenly. Worked just fine. You know, things really haven't changed all that much since Gingerbread...
-If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like.
- Be aware that if you modify ANYTHING on your phone, even as little as a new boot logo to cover up the unlocked bootloader message, you will prevent your phone from taking any further OTA updates. Some mods, like adding TWRP, may still allow it to try to download and install an OTA, but when it reboots to finish that install, it will fail since it needs to re-boot through stock recovery to complete. And it will continue offering you that update.
- There is a difference between the partition structure in our phones on 8.x, and those on 9. 9 is not full Treble, only a "partial" Treble, and really only the addition of a second set of partitions which OTA updates can use to update the system - instead of modifying the single partition set, it modifies the other (a or b) set and boots to that on update completion. If it fails it can always boot the other set. Theoretically! Makes it safer than the old way of doing OTA updates, but this may cause problems if you try to flash a 2 partition set phone with a single partition set ROM. I don't believe anyone has run any experiments on this, so YOU, when you flash things without thinking about the situation, may get an unusable phone. I do not know the answer here. If you read these forums which detail other's problems, you may trod a bit more hesitantly!
-The idea here is to have fun, and sometimes to experiment with new things. To a newbie, losing the use of a $200 phone can be a tough life lesson. Let's help them out by helping them to be cautious!
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
SR3TLAW said:
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
Click to expand...
Click to collapse
I would be careful about lineage as folks don't seem to be able to get back to stock from it.
I agree about maintaining root. I will likely just stay on stock with this one.

I want to create a unofficial kernel and bootloader, ¿how do i begin?

So, i have an LG K11 Plus (LM-X410BCW), released in 2018, the hardware of this phone is pretty good but, for some reason, while its CPU does supports 64-Bits, LGE installed an 32-Bits kernel on it (thank you for mistakes like that you always do, LGE.... ugh)
I searched for another root and custom kernel for this phone, and i could not find any. No rooting, no custom bootloader, and no custom kernel. Simply, nothing.
And for the most unfortunate, this phone is now completely abandoned by the manufacturer. Their official ROM and kernel are so bad, so glitched, so awful. The phone does not use the maximum power of its hardware, it keeps rebooting, it's stuck in Android 7.0 and even its camera app is glitched (my BACK flash doesn't work on the back camera, the app recognizes it as a "frontal" flash)
I know for rooting and installing custom kernel, i need another bootloader first
So i plan to make an unofficial bootloader for this model.
But i don't know where to begin, i know nothing about Android deep-modding and developing mobile custom kernels and bootloaders, i've no clues how to do that
I only know the basics of Android app developing, Android shell scripting and i'm more advanced in J2ME applications (completely useless for today's Android standards)
So, ¿where do i begin to do that?
My initial plans is making a unofficial TWRP bootloader for this model, but i don't know how i'll do that
I'd really help you if i knew how to, i also have this phone. I got it for a realtively high price and must say that it's absolutely unworthy of it's existance in our planet and modern society. The absolute maximum of modifications it allowed me to do was to remove bloatware packages using ADB, so i removed almost everything Google/Android related and now i'm working on a list of what you can/can't remove.
I removed the included launchers to only use Evie launcher, installed XDA's Navigation Gestures app (tho it made my phone lag a bit, as any overlay/draw-over-screen app will do), replaced Play Store by F-Droid, and etc... The phone is still bad, sub-entry level hardware even for it's time, has a Vulkan-capable GPU without Vulkan drivers included in the OS, and a 64-bit CPU running a 32-bit Kernel/OS, like you mentioned. But after that, the experience became a little bit smoother, at least!
I don't know nothing about this, but maybe you can get this phone's stock ROM in KDZ format, and start doing brute-force modifications to it, to flash it with LGUp, or LGFlashTool as if it was a stock ROM, but your modified version, because i don't think this phone checks the integrity of the ROM being flashed, or at least not in a way that can't be easily bypassed.
I have found its firmware on the internet, but i don't know how to modify it yet... But maybe i'll not delay much to learn it if i begin to. But i think i'll not be able to change its kernel nor the bootloader, as i want, from the firmware only, only the ROM... So it would be a bit useless as the LG's negligency was most on its software, with that lack of Vulkan and 64-bit support stuff

Categories

Resources