Related
I was given a g Tablet last week for my birthday. I've spent hours digging through this site and I installed Clockworkmod and TNTLite 4.2.4. I have the following questions/problems...
1) I can't get Market to run. I've installed it using the instructions in this thread but when I click it, the screen briefly flashes white and then the menu page returns. When I go to the Applications menu, the cache is empty.
My other two spring from not being able to get Market running.
2) I desperately need to get Root Explorer running so I can unprotect the system directory and enable Graffiti. I loathe virtual keyboards.
3) I'd like to figure out how to sideload apps. I learned how to install .apk files, but not how to install an app that doesn't have an .apk file.
Again: I've spent hours on this site looking for answers, so please don't 'search is your friend' me. That being said, I'm more than happy to get a snarky, "This took me 3.5 seconds to find" with a link to the answer.
Thanks in advance for any help.
Shawn Stanford said:
That being said, I'm more than happy to get a snarky, "This took me 3.5 seconds to find" with a link
Click to expand...
Click to collapse
This took me 0.4 seconds to find...
http://forum.xda-developers.com/showthread.php?t=861044
Once you get market working, you can install root explorer and you're good.
Shawn Stanford said:
3) I'd like to figure out how to sideload apps. I learned how to install .apk files, but not how to install an app that doesn't have an .apk file.
Thanks in advance for any help.
Click to expand...
Click to collapse
Sideloading apps just means installing the apk from somewhere other than the market. You can't install an app if it doesn't have an apk. The apk is the app. Unless they give you an update.zip or something, and even then, there is an apk in it.
I know this is off topic I got one for my best too I love it
Sent from my VEGAn-TAB using XDA Premium App
Shawn Stanford said:
I was given a g Tablet last week for my birthday. I've spent hours digging through this site and I installed Clockworkmod and TNTLite 4.2.4. I have the following questions/problems...
1) I can't get Market to run. I've installed it using the instructions in this thread but when I click it, the screen briefly flashes white and then the menu page returns. When I go to the Applications menu, the cache is empty.
My other two spring from not being able to get Market running.
2) I desperately need to get Root Explorer running so I can unprotect the system directory and enable Graffiti. I loathe virtual keyboards.
3) I'd like to figure out how to sideload apps. I learned how to install .apk files, but not how to install an app that doesn't have an .apk file.
Again: I've spent hours on this site looking for answers, so please don't 'search is your friend' me. That being said, I'm more than happy to get a snarky, "This took me 3.5 seconds to find" with a link to the answer.
Thanks in advance for any help.
Click to expand...
Click to collapse
Try this to fix your market
Step 3.
Open the Market app. Once it loads close it (press the home button).
Step 4.
Go into Settings - Applications - Manage Applications - Market - Clear CACHE - Force Stop
(For TnT/TnT Lite... Settings - Applications - System Applications)
Step 5.
Press back once - Google Services Framework - Clear DATA - Force Stop
Step 6.
Go back to your home screen and open up the market. You should get an error. If not, redo steps 4 and 5 until you do.
Step 7.
Reboot your device. After it starts back up let it sit for a minute or two to let things in the operating system normalize. Open the Market. Reboot your device.
Step 8.
Open the market again and enjoy
And to side load my apps i use something like dropbox and place the apps in there and then load the dropbox app on your gtab and any files and folders that you placed in there you can side load. Hope this helps!
Might as well gotten the TNTL 4.4.0, has alot the fixes implented already and stable.
Here the page if you are interested
http://forum.xda-developers.com/showthread.php?t=842004
Here's the problem: all of the fixes to Market require that Market actually loads:
6) Now you are going to re-do the original Market Fix. ... First, make sure Market is running, and browse around in it for a few seconds. If you don't do this, there may be no cache to clear and for some reason the market fix may not work. ...
Click to expand...
Click to collapse
As I mentioned: Market has never successfully loaded for me. I get a brief white screen and then the panel I launched from reloads. This is the only app where I'm having this problem.
And, of course, without Market, I'm dead in the water on pretty much everything else...
Use an updated ROM
As posted before, use the latest ROM for what you are trying to accomplish. The fix has already been done. Try the Vegan 5.1 then the 5.1.1 supplement. It is really stable and stuff works.
I know you're asking about getting the market to work with TNT lite, but nobody seems to have an answer for you. So, if you want your tab to just work, including the market, google apps, etc...
1 - Go here http://vegantab.gojimi.com/downloads/ and download VEGAn-TAB GingerEdition
2 - Plug in a USB cable and drop that zip file onto the root of your SD card
3 - Reboot into ClockworkMod (power off, then hold volume + while powering on)
4 - Use ClockworkMod to do these steps:
- wipe data/factory reset
- wipe cache partition
- wipe dalvik cache (it's under advanced)
- install zip from sdcard
- - choose zip from sdcard
- - - select VEGAn-GE-7.0.0-RC1-Harmony-signed.zip
- reeboot system now
5 - after it boots up, do the setup
6 - POWER OFF once setup is done - don't skip this
7 - power back on
8 - enjoy the Gingery goodness including the market, google apps, a juicy speed boost, etc, etc, etc.
It will be running VTL.Launcher v1.5. If you like the launcher, or if you just want to thank Gojimi for the awesome rom that was so easy to install (and it just worked with no futzing around), go into the market and buy the new version of VTL.Launcher. It costs almost nothing and you're not going to find a better launcher for a tablet. More info on VTL.Launcer here http://forum.xda-developers.com/showthread.php?t=1046302
Just in case you got desperate, started playing around with things and accidentally upgraded to the locked bootloader:
http://forum.xda-developers.com/showthread.php?t=1036956
And here's the official post about the release of GingerEdition:
http://forum.xda-developers.com/showthread.php?t=1031250
DanLynch said:
8 - enjoy the Gingery goodness including the market, google apps, a juicy speed boost, etc, etc, etc.
Click to expand...
Click to collapse
Ah, man...
Initial reboot after installing VEGAn is unsuccessful: I'm not getting past the birds.
Crappity, crap, crap...
Is this the 'locked' bootloader? If so, I wish I'd figured that out before I moved on. I can see the instructions for fixing it in that thread, but how do I get the .zip file to tablet memory now?
NVM: Found the 'mount' option in CWM. I'm on it like a jimmie hat. Further updates as events warrant...
Frack! Still stuck on the birds...
After several painstaking attempts to get VEGAn installed, I'm going to reinstall the downgrade to regain use of my pad while I decide where to go from here.
It is a common issue for the tablets to have been shipped with some mixed up partitions. It doesn't seem to bother the Froyo based ROMs, but it causes the GB based roms to hang at the 'birds'.
Find the thread/directions on doing nvFlash. That will restore the tab to the true stock state (including the proper partitions) and you can then flash GB based roms with no issues.
I got my gtab less than a week ago. In this short time, i have tried the stock rom, vegan 5.11, vegan 7 gingeredition and cynogenmod 700/702 and TNT lite 44! And i have to tell you that i loved each one of them!
But before I flashed anything, i followed the instructions in this thread to the letter.
httpi://forum.xda-developers.com/showthread.php?t=865245i
My recommendation to you will be to start over and read first then read again and then implement!
For now i am settling on TNTlite 44 as it offers the best combination of what i need. I decided to stay away from gingerbread as hardware acceleration and video playback suffers on it. Vegan 511 is based on 2.2 but somehow i felt graphics were not up to my expected level. Again these are all my personal preferences, so you definitely want to try them all before you settle on your rom.
Having said all this, i greatly appreciate all the hard work from all developers of these rom and thank them for such great options for the gtab!
Shawn Stanford said:
After several painstaking attempts to get VEGAn installed, I'm going to reinstall the downgrade to regain use of my pad while I decide where to go from here.
Click to expand...
Click to collapse
Shawn, take a break from it and come back later. It really is worth your time once you get rolling.
nimiaj said:
I got my gtab less than a week ago. In this short time, i have tried the stock rom, vegan 5.11, vegan 7 gingeredition and cynogenmod 700/702 and TNT lite 44! And i have to tell you that i loved each one of them!
But before I flashed anything, i followed the instructions in this thread to the letter.
httpi://forum.xda-developers.com/showthread.php?t=865245i
My recommendation to you will be to start over and read first then read again and then implement!
For now i am settling on TNTlite 44 as it offers the best combination of what i need. I decided to stay away from gingerbread as hardware acceleration and video playback suffers on it. Vegan 511 is based on 2.2 but somehow i felt graphics were not up to my expected level. Again these are all my personal preferences, so you definitely want to try them all before you settle on your rom.
Having said all this, i greatly appreciate all the hard work from all developers of these rom and thank them for such great options for the gtab!
Click to expand...
Click to collapse
Could you clarify what you mean by this?
I am currently running VEGAn 5, and have no huge problems with it at all, but if TnT offers something better, then I may jump on that.
What do you mean by the graphics not being up to the expected level?
Thanks for the advice, everyone. I did a repartition when I started installing TNT Lite. I assumed it would 'stick', but I'll restart from scratch and shoot for VEGAn for a change of pace. Prolly give it a try tomorrow if I hit a slow patch at work.
Just had a thought...if you just got your Gtab the other day, there is a chance you may have been running the new 1.2 dev instead of the old 1.1(which is what most all the ROMS available are based on) and supposedly the two don't really play well without NVFlashing first...so that may be the issue you are having. Then again it may not. Good luck and I hope it all works out.
When using Vegan 5.1.1 I noticed that some of the graphic elements of the UI would look "shaded" or "grainy" (from a proper viewing angle). Also I have some standard wallpapers that I migrate over whenever I reflash. These were also looking a little lower in quality. Now it may be just me or my specific GTab, but that's what I observed. I did not see this when using either of the Gingerbread roms or the stock rom or the TNTLite.
Before you jump on, remember that TNT Lite 4.4 is essentially closed, and I moved over to try it and plan to stay on it until there is any news about hardware accelerated drivers for Gingerbread or Honeycomb comes along! Hope this helps.
Okay, I tried getting Ginger to work three additional times, including following the original instructions I followed to load TNT Lite step by step: no dice. I'm out of patience with it; at this point I'm running the 4349 downgrade.
I was planning on reloading TNT Lite, but I'm not sure it's worth the effort. I never did get Market or Graffiti to work.
So now that Jelly Bean for Bionic is out and there is a root method that works, what should be kept and discarded as far as apps go such as, ROM Manager, superuser, superuser#, SuperSU, and VoodooOTA Root Keeper, Bootstrap, safestrap.
Obviously I do not know, and many may not also know, which of these apps is essential and which is outdated. Is there a forum that I missed, if so I apologize. I can guess that Voodoo should be kept because Motorola may, as unlikely as it may seem, might update Bionic with a fix or other small software update.
Is there anyone making ROMS that work with Jelly Bean 4.1.2, ? I have been out of the searching for some months and now not knowing where to look for the best answer to these questions.
Well the Liquid Smooth 2.2.1 and the CM10.1 are built on Kexec so they will work on the JB OTA kernel, I'm running both on the OTA rooted .22 build. I'm reading that some odd functionality seems to be happening but they are already being ironed out in the nightly builds. Anything not on a Kexec build i would assume will not work on your JB OTA kernel.
Just keep reading the posts and help out with the nightlies (load new ones and report any bugs or that its all good) b/c that helps them fix the bugs faster and faster to a new stable ROM.
As far as whats what to keep, I'm keeping Titanium Backup, OTA root keeper, Superuser (obviously) I'm on Safestrap v3.11 to flash ROMs
As for ROMs... the JB 4.2.2 ROMs.. Liquid Smooth, CM10.1 and any other JB ROMs i would think would be ported over. Just keep an eye out. People are all giddy over the Bionic again so im sure it will be strong for awhile longer.
Well I know what's next for my Bionic. After I've jumped up an down on it a bunch of times I plan to toss it in my driveway and drive over it...then backup and do it again a few times.
For me it's been a complete disaster and still have never got my lapdock to work right.
Middle of June my contract is up and I'm going for the Galaxy Note II. Depending upon what kind of deal I can get out of VZW I might switch carriers too.
June!? I might be the harbinger of bad news but the Bionic was released in September of 2011 so that means if you got the Bionic at launch, you cant upgrade till September. They used to let you update at the 20 month mark instead of going to the full 24 months. Well 2 weeks ago Verizon announced that they will no longer be letting people upgrade early. Hence you have to go the full 24 months now.
Eric
Eric214 said:
Well the Liquid Smooth 2.2.1 and the CM10.1 are built on Kexec so they will work on the JB OTA kernel, I'm running both on the OTA rooted .22 build. I'm reading that some odd functionality seems to be happening but they are already being ironed out in the nightly builds. Anything not on a Kexec build i would assume will not work on your JB OTA kernel.
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but the fact that a ROM is based off KEXEC means that those ROM's don't care what base kernel you're running, whether you're on the ICS or JB OTA. Those ROMs bring in their own kernel that's booted with KEXEC. Safestrap handles the KEXEC process, and Safestrap works properly on the JB OTA so there's nothing to really worry about.
Also I'm not even sure how you'd ever use ROM Manager on the Bionic. Especially if you have Safestrap installed.
Hey, I just updated and established root with ubuntu method. Now I want to install Liquid (I hate the feel of stock Bionic) but when I reboot, and hit menu for safestrap, it just boots into android... I have deleted TWRP and safestrap folders, uninstalled and reinstalled, but to no avail. any ideas?
Eric214 said:
June!? I might be the harbinger of bad news but the Bionic was released in September of 2011 so that means if you got the Bionic at launch, you cant upgrade till September. They used to let you update at the 20 month mark instead of going to the full 24 months. Well 2 weeks ago Verizon announced that they will no longer be letting people upgrade early. Hence you have to go the full 24 months now.
Eric
Click to expand...
Click to collapse
MyVerizon still says I can upgrade at discount on 6/6/13. I probably won't right away because I want to wait for the Motorola/Google X phone.
Yeah i know and mine still says May 14th but good luck for me getting to update then. My guess is they haven't updated their systems yet. Likely they have instructions to disreguard that and go the full 2 year from start of contract.
If you can update early still then AWSOME! 1 other thing is maybe they are grandfathering in people who are close? like over 16 or 18 months into the contract so they are only 2-4 months from the early update. IDK I just know that 2 weeks or so ago VZ said they are done with allowing ppl to update at 20 months and that you must now go to the full 24 months or just new contracts will get the full 24 months till upgrade?
Eric
Thanks for the info, I am interested in trying some of the Roms you mentioned, so correct me if I am wrong please but I need safestrap, not bootstrap to load a Rom on the side of the JB stock ROM. I am rooted so no problem there.
Thanx in advance
Sqwaller said:
Thanks for the info, I am interested in trying some of the Roms you mentioned, so correct me if I am wrong please but I need safestrap, not bootstrap to load a Rom on the side of the JB stock ROM. I am rooted so no problem there.
Thanx in advance
Click to expand...
Click to collapse
Yes you have to use safestrap and you must install Liquid in the rom-slot 3 or it wont work. Now on the safestrap. I think you also need to have SS v3.11 for Liquid so make sure you have that one. Once you install it make sure you open the Safestrap app and install recovery then reboot. Once it starts to boot up and you see recovery, make sure you're tapping the setting button, not the screen, and just keep tapping it till you feel the vibration then it will enter recovery.
Eric
Eric214 said:
Yes you have to use safestrap and you must install Liquid in the rom-slot 3 or it wont work. Now on the safestrap. I think you also need to have SS v3.11 for Liquid so make sure you have that one. Once you install it make sure you open the Safestrap app and install recovery then reboot. Once it starts to boot up and you see recovery, make sure you're tapping the setting button, not the screen, and just keep tapping it till you feel the vibration then it will enter recovery.
Eric
Click to expand...
Click to collapse
OK sounds good, will work on that this weekend.
Thank You very much I really appreciate the help.!
NewtG
Eric214 said:
Yes you have to use safestrap and you must install Liquid in the rom-slot 3 or it wont work. Now on the safestrap. I think you also need to have SS v3.11 for Liquid so make sure you have that one. Once you install it make sure you open the Safestrap app and install recovery then reboot. Once it starts to boot up and you see recovery, make sure you're tapping the setting button, not the screen, and just keep tapping it till you feel the vibration then it will enter recovery.
Eric
Click to expand...
Click to collapse
I am a little confused about the setting for the 1,2 or 3 GB is this on the external SD or the internal SD that they are asking about. I have a 32 gb card installed but stock JB ROM I have all my usual apps that take up about 3.5 gb of internal space. And can you tell me if the addition of this other ROM slows down my stock ROM games?? no big deal but my son likes to play some multiplayer games with me on his droid x.
You really should go to hashcodes site and read about safe strap. It is asking the amount of space you want to allocate for apps on the phones internal memory. It will show you how much total spacee you have for all 4 room slots.
---------- Post added at 01:22 AM ---------- Previous post was at 01:14 AM ----------
if you use a lot of apps then you would want to use 3 gigabytes if you use few apps then you want to use one gig.for example my Bionic has a 16 gig internal memory which is allocated an unusable for safestrap which leaves me eight gigs to use for my rom slots. it will use roughly one gig for the system and then what you allocate for data space for apps. so since I have eight gigs everyone get partition I use really uses two gigs. hope this helps
projektorboy said:
Someone correct me if I'm wrong, but the fact that a ROM is based off KEXEC means that those ROM's don't care what base kernel you're running, whether you're on the ICS or JB OTA. Those ROMs bring in their own kernel that's booted with KEXEC. Safestrap handles the KEXEC process, and Safestrap works properly on the JB OTA so there's nothing to really worry about.
Also I'm not even sure how you'd ever use ROM Manager on the Bionic. Especially if you have Safestrap installed.
Click to expand...
Click to collapse
KEXEC kicks out the existing (Motorola) kernel after the system is booted, and starts a new boot sequence with a new kernel. The issue with this system is the availability of specific hardware drivers for the custom kernel.
The KEXEC kernel from your custom ROM does not have all the specific hardware drivers needed for, for example, hardware accelerated graphics, because these drivers are generally not available (closed source), and older available drivers are not compatible with newer kernels.
Now that we have a full JB ROM, custom ROM bakers can borrow the drivers and use them in their creations.
This should mean that new revisions of your custom rom can be made fully functional now. Common missing links that can now be completed are: native camera app and hardware accelerated video playback. I also heard Bluetooth may have been a problem but I don't use it.
Hey, I'm having issues getting into safestrap. I have it installed, with root, on OTA, and it boots to the option to go to it, but when I press menu it goes straight to DROID and boots.... Ideas?
Sometimes hitting menu doesn't catch. tap it till you feel the phone vibrate some. I think the spot to hit really is just above the menu key and the actual screen in the black area. Just tap it a few times till you feel it vibrate and it will boot in to the recovery.
Eric214 said:
Sometimes hitting menu doesn't catch. tap it till you feel the phone vibrate some. I think the spot to hit really is just above the menu key and the actual screen in the black area. Just tap it a few times till you feel it vibrate and it will boot in to the recovery.
Click to expand...
Click to collapse
IT does vibrate, that's why im so confused. I used it for cm10.1 before, but I cant even get into SS now!
EDIT: I just noticed it is not creating a safestrap or TWRP folder... I have root... WTH?
Did you try uninstalling it and reinstalling it? Then install recovery. If that doesnt work are you truely rooted and not partially rooted? Have you installed Titanium BAckup and was it granted root?
Eric214 said:
June!? I might be the harbinger of bad news but the Bionic was released in September of 2011 so that means if you got the Bionic at launch, you cant upgrade till September. They used to let you update at the 20 month mark instead of going to the full 24 months. Well 2 weeks ago Verizon announced that they will no longer be letting people upgrade early. Hence you have to go the full 24 months now.
Eric
Click to expand...
Click to collapse
Everyone with an upgrade date prior to 9/1/2013 is being allowed to keep their current date (source is here). So he will be fine in June.
well that is awsome news!
DISCLAIMER: This is my personal experience, it may not be the same for you, YMMV and all that.
Well, short story is that I got fed up with my Nexus 7 having performance of my ancient Win Mobile smart phones. It got to a point where no matter what ROM I ran, be it stock 4.2.1, 4.2.2 or custom Roms from XDA, my Nexus would struggle with even simple tasks.
Examples:
closing tab in chrome - 2-3 seconds
Rotating a screen (nova launched home, only 1 page total) - 3-6 seconds
Launching NFS (game) - 3-6 seconds before I'd see the loading screen, would load for about 15-20 seconds. In game fps would dip to what felt like around 25-30 fps.
Battery dying at 10-15% (tried everything, including disassembly).
After trying everything I decided to ditch the 4.2+ and go back to how it was when I bought it. Reason being that I remember sudden increase in overall system lag when Google released 4.2.
So, here I am running 4.1.2, so far on my second day of use. Here's what I see:
Chrome - much more responsive, tabs client immediately, pages redraws quicker on scroll.
Rotating screen - 1, maximum 2 seconds.
Launching NFS - immediate, loads for about 5-7 seconds. Game interface way more fluid and responsive. Game runs at what feels like fluid 60 fps most of the time, with many cars on screen dips to, I'd say, around 40 fps.
Battery is now at 5%, not shutting down, which is good news to me.
Obviously, things like performance can be very subjective, but overall I do see huge improvement in performance.
Maybe it will work for other people as well who are as annoyed by 4.2.2 sluggishness as I was.
Did you reinstall 4.1.2 from scratch - including fastboot erasure/formatting of file systems suggested by the factory install instructions?
I'm wondering if you would see essentially the same performance if you now reinstall 4.2.2 using exactly the same procedure. (Obviously, you might want to make a full Nandroid backup of the 4.1.2 install so you could nuke 4.2.2 and restore back to 4.1.2 easily).
For instance, if the performance issues were related to filesystem corruption or just simply buildup of app "cruft" over time, or a misbehaving app due to some fault condition happening sometime after the original 4.2.x ota upgrade. (Kinda like re-installing the same version of Windows always seems to speed it up, LOL)
I guess the point is that the most likely root-cause of "lag" is something to do with flash memory (filesystem) I/O as it is the slowest operation in the device. A fair comparison would be fresh install vs. fresh install.
cheers
Try using Clemsons Elite 1500 Extreme Kernel and Cookies and Cream if you can find them, they blow away any 4.2 Kernel/Rom combo and its not even close.
I agree with darkdvr with games being laggy on the 4.2.2. Playing nova 3 stutters a lot.not too pleased with it.the battery drain is also pretty crazy compared to what they say the battery should last with certain usages.I'm also going to downgrade to 4.1.2 to see the difference.hopefully it works and plays better than this 4.2.2. I also think that rooting has something to do with a lot of lag. When stock its smooth and fluent opposed to after rooting. You get pauses and stutters.gonna give it a go tonight
I never delete fastboot, but I formatted sdcard/system, and all caches. I holy doubt that this case is that "build up" that we are all familiar with on Windows, since 4.2.2 was laggy for me right away, as soon as apps are installed and launcher configured - nexus immediately becomes a slow ass lag sloth. It was always rather terrible for me, although I am hyper sensitive to lags and delays on any system. I know most people aren't that anal about it.
Interestingly enough, I restored almost all my apps with titanium, including their data, s I can say that its not the apps, its the system. Using android since 2.1, I can safely say that 4.2.2 is the laggiest and most messed up release since, probably, eclair. They really dropped the ball here. I hope 4.3 will be QAed more thoroughly.
bftb0 said:
Did you reinstall 4.1.2 from scratch - including fastboot erasure/formatting of file systems suggested by the factory install instructions?
I'm wondering if you would see essentially the same performance if you now reinstall 4.2.2 using exactly the same procedure. (Obviously, you might want to make a full Nandroid backup of the 4.1.2 install so you could nuke 4.2.2 and restore back to 4.1.2 easily).
For instance, if the performance issues were related to filesystem corruption or just simply buildup of app "cruft" over time, or a misbehaving app due to some fault condition happening sometime after the original 4.2.x ota upgrade. (Kinda like re-installing the same version of Windows always seems to speed it up, LOL)
I guess the point is that the most likely root-cause of "lag" is something to do with flash memory (filesystem) I/O as it is the slowest operation in the device. A fair comparison would be fresh install vs. fresh install.
cheers
Click to expand...
Click to collapse
I'm interested. Could you post the steps to do the downgrade?
hotsync100 said:
I'm interested. Could you post the steps to do the downgrade?
Click to expand...
Click to collapse
It's really easy with the Nexus 7 toolkit - get it HERE (dev forum).
Basically, I backed up user apps with Titanium Backup and copied the backup to my PC.
Launched the toolkit, created nandroid backup of 4.2.2 ROM (option 4 in the Toolkit AFAIR).
Booted into the recovery, formatted everything (sdcard, system, all caches).
From recovery booted into fastboot mode (all volume buttons + power button).
With toolkit, downloaded and installed 4.1.2 factory ROM and installed it onto Nexus.
For some reason first one didnt boot for me (stuck at nexus X), so I cleared cache/system data, redownloaded it and flashed it again. Thankfully, Toolkit guides you through the steps.
Then, an optional step, I used a hack apk from xda to prevent nexus from checking for ROM OTA updates. Now I'm at 4.1.2 and my Nexus is finally back to its original snappiness.
is it possible to run 4.1.2 with 4.2.2 bootloader?
RobYyY said:
is it possible to run 4.1.2 with 4.2.2 bootloader?
Click to expand...
Click to collapse
I highly doubt it, and it would ruin your experiment "cleanliness", I'd say.
I recently attempted to downgrade to 4.1.2, to see what all the fuss is about... but without flashing the bootloader. My attempt didn't get very far...
Code:
checking product...
OKAY [ 0.031s]
checking version-bootloader...
FAILED
Device version-bootloader is '4.18'.
Update requires '3.41'.
finished. total time: 0.250s
Press any key to exit...
I'm loathe to unnecessarily flash the bootloader (unless absolutely required to do so). So I abandoned my attempt...
----
All I can say is 4.1.2 must be pretty damned fast, because I've never had any problems with 4.2.2.
I have noticed though (and this could just be the 'placebo' effect), that wiping CACHE and DALVIK CACHE does seem to make for a marginally more smoother experience.
LagFix (fstrim) Free is also widely reported as fixing lag issues in 4.2.2... although I can't say I've noticed much difference after running it.
But then, as I say, 4.2.2 (custom ROM - see sig) runs liquid smooth for me anyway.
Rgrds,
Ged.
hotsync100 said:
I'm interested. Could you post the steps to do the downgrade?
Click to expand...
Click to collapse
If you wanna try manual method here is step by step guide to downgrade from 4.2.2 to 4.1.2 using fastboot.
Following instruction in this thread http://forum.xda-developers.com/showthread.php?t=1907796 except for
1.Download the Nexus 7 4.1.2 factory image from the link instead of 4.2.2 .
2.On Flashing the Factory Image step.
Change following line
fastboot flash bootloader
and
fastboot -w update
to match the name of 4.1.2 factory image instead of 4.2.2 for example
change from
fastboot flash bootloader bootloader-grouper-4.18.img TO fastboot flash bootloader bootloader-grouper-3.41.img
and
fastboot -w update image-nakasi-jdq39.zip TO fastboot -w update image-nakasi-jzo54k.zip
Downgraded for a bit, and did not particularly enjoy 4.1.2, and I wound up going back to 4.2.2 after completely wiping the system and accidentally having to re-update my recovery. I've noticed my battery life has finally gone back to the way it used to be when I first got my N7, and the performance seems better to me when I play Voxel Rush (only game I really play on here). I believe my problems with 4.2.2 earlier were indeed caused by a lot of crud built up from flashing previous ROMs and kernels over time.
dwxvi said:
Downgraded for a bit, and did not particularly enjoy 4.1.2, and I wound up going back to 4.2.2 after completely wiping the system and accidentally having to re-update my recovery. I've noticed my battery life has finally gone back to the way it used to be when I first got my N7, and the performance seems better to me when I play Voxel Rush (only game I really play on here). I believe my problems with 4.2.2 earlier were indeed caused by a lot of crud built up from flashing previous ROMs and kernels over time.
Click to expand...
Click to collapse
4.2.2 after flashing seems to be somewhat on par with 4.1.2, but please report back to us in several days, I bet it will slow down to a crawl.
Another easy way to downgrade would be to install cyanogenmod 10.0.0. Also, please don't start downgrading your bootloader. It shouldn't be necessary for flashing stock 4.1.2 and it might complicate things if you want to flash custom kernels in the future.
For what it's worth, I'm running 4.2.2 with no noticeable lag. I just bought it used so I did a factory reset just before updating. Maybe that has something to do with it?
Sent from my Nexus 7 using xda app-developers app
Hm. I have none of the problems you had on 4.2.2. I'm running 4.2.2 and it's pretty snappy.
Rotating the screen takes about 1-2 seconds.
Closing tabs in Chrome is instantaneous.
Apps launch quickly.
Battery holds out to about 3% before I plug it in.
Hm. Maybe you had a lot of apps installed? I have quite a few but not as much as some people
Do you guys have multiple user accounts? I've been playing around with it a bit, and maybe it's just me but I feel it's a bit slower when you have more than on user. Anyone else noticed this? I did a quick Google search and seems others have noticed it too.
dwxvi said:
Downgraded for a bit, and did not particularly enjoy 4.1.2, and I wound up going back to 4.2.2 after completely wiping the system and accidentally having to re-update my recovery. I've noticed my battery life has finally gone back to the way it used to be when I first got my N7, and the performance seems better to me when I play Voxel Rush (only game I really play on here). I believe my problems with 4.2.2 earlier were indeed caused by a lot of crud built up from flashing previous ROMs and kernels over time.
Click to expand...
Click to collapse
My battery life also sucks,I want to try this.
Which way did you downgrade?
demolition23 said:
My battery life also sucks,I want to try this.
Which way did you downgrade?
Click to expand...
Click to collapse
You won't have to downgrade to do this, you would just have to back up your data (the important stuff) and completely wipe your internal storage so that everything is cleaned up and ready for a re-install of 4.2.2. Then you can re-load your data. I would reccommend using Wugfresh's Nexus Toolkit for this.
dwxvi said:
You won't have to downgrade to do this, you would just have to back up your data (the important stuff) and completely wipe your internal storage so that everything is cleaned up and ready for a re-install of 4.2.2. Then you can re-load your data. I would reccommend using Wugfresh's Nexus Toolkit for this.
Click to expand...
Click to collapse
I just did that, and will post results when I have a clear picture.
Ok, I have been searching for a couple of weeks now but I have not found a soulution. I recently recieved a replacement Note 4. I updated it to Lollipop, then rooted and flashed Rapture.
Ever since, I have been experiencing random reboots and the occasional loss of data. This is not a Rapture problem it appears. I have had the issue with both versions of the Rapture Lollipop builds, DarthStalker, and stock Deodexed COD6. I did not have this problem on my last Note 4 which had the first Rapture build on it.
I have factory reset, I have Odined back to stock and repeated the rooting process, following the guides posted here to the letter and I still have the problem. Any help in resolving this issue is greatly appreciated.
KingBeef said:
Ok, I have been searching for a couple of weeks now but I have not found a soulution. I recently recieved a replacement Note 4. I updated it to Lollipop, then rooted and flashed Rapture.
Ever since, I have been experiencing random reboots and the occasional loss of data. This is not a Rapture problem it appears. I have had the issue with both versions of the Rapture Lollipop builds, DarthStalker, and stock Deodexed COD6. I did not have this problem on my last Note 4 which had the first Rapture build on it.
I have factory reset, I have Odined back to stock and repeated the rooting process, following the guides posted here to the letter and I still have the problem. Any help in resolving this issue is greatly appreciated.
Click to expand...
Click to collapse
Seeing that it's happening on so many different Roms; it's something you're installing on your device.
Does it happen on a fresh stock rooted COD6 with nothing installed 3rd party?
I have not tried a stock run without third party apps installed. I will try a fresh install of stock COD6 with root and see how that fairs. It normally happens the first time within an hour of flashing so it won't take long to see if it happens I believe.
I was getting one or two random reboots a day after updating to LP. I noticed most reboots happened after I finish or during use of Google All Access. I have a lot of tracks stored on my SD cards. Once I refreshed the tacks [in all access settings], I haven't has a reboot since.
Jammol said:
Seeing that it's happening on so many different Roms; it's something you're installing on your device.
Does it happen on a fresh stock rooted COD6 with nothing installed 3rd party?
Click to expand...
Click to collapse
So I tried stock rooted without third party apps installed. Got 2 reboots but no loss of data. Seems like it's something with the device itself or should I try just running without root?
dkb218 said:
I was getting one or two random reboots a day after updating to LP. I noticed most reboots happened after I finish or during use of Google All Access. I have a lot of tracks stored on my SD cards. Once I refreshed the tacks [in all access settings], I haven't has a reboot since.
Click to expand...
Click to collapse
I wish it was something that simple. The only consistency I am getting in terms of reproducing it is trying to multitasking and possibly having too many apps running in the background, but sometimes it happens with just 2 or 3 apps running so I am not sure.
What's really annoying about it all is the first unit I had ran flawlessly, even after the 5.0 update.
KingBeef said:
I wish it was something that simple. The only consistency I am getting in terms of reproducing it is trying to multitasking and possibly having too many apps running in the background, but sometimes it happens with just 2 or 3 apps running so I am not sure.
What's really annoying about it all is the first unit I had ran flawlessly, even after the 5.0 update.
Click to expand...
Click to collapse
Does your device get really hot right before it does the random reboots? Could be thermal function of the Note 4. 805SOC is a very hot chip albeit not as bad as the 810 but pretty dang close if you ask me!!! If no heat issues then see below
Give this a try:
This will require you to Odin to COD6 Stock NO ROOT!!!
Shut down and take out your External SDCard.
Boot into TWRP or Flash TWRP if you don't have it on there right now
Do a FULL WIPE: Factory Reset 3x, Advanced Wipe(Everything there) 3x, and finally Format Data(where you have to type yes) 3x
Power off your device and start it up into Download mode and Odin COD6 Stock Firmware(the full one not the partial)
Let it do it's thing and then simply use the device for a few hours on just pure stock.
DO NOT INSERT YOUR SD CARD!!! Why? We want to make sure it isn't something on your card causing Indexing to hang and force reboot.
If you get no reboots then go ahead and shutdown and insert your SDCard and use your device. Still no reboots? Then go ahead and Root. Still no reboots? It's resolved.
This process of elimination is lengthy but it is effective.
Jammol said:
Does your device get really hot right before it does the random reboots? Could be thermal function of the Note 4. 805SOC is a very hot chip albeit not as bad as the 810 but pretty dang close if you ask me!!! If no heat issues then see below
Give this a try:
This will require you to Odin to COD6 Stock NO ROOT!!!
Shut down and take out your External SDCard.
Boot into TWRP or Flash TWRP if you don't have it on there right now
Do a FULL WIPE: Factory Reset 3x, Advanced Wipe(Everything there) 3x, and finally Format Data(where you have to type yes) 3x
Power off your device and start it up into Download mode and Odin COD6 Stock Firmware(the full one not the partial)
Let it do it's thing and then simply use the device for a few hours on just pure stock.
DO NOT INSERT YOUR SD CARD!!! Why? We want to make sure it isn't something on your card causing Indexing to hang and force reboot.
If you get no reboots then go ahead and shutdown and insert your SDCard and use your device. Still no reboots? Then go ahead and Root. Still no reboots? It's resolved.
This process of elimination is lengthy but it is effective.
Click to expand...
Click to collapse
I can't say that I have noticed it in the past, however, it froze up shortly after I read the email notification of your response and was quite warm towards the top half. I pulled the battery expecting it to reboot anyway. Is there anyway to mitigate the thermal affect if it is indeed the culprit?
I will try the second method this evening and see if there's any change in behavior and report back sometime tomorrow. Thank you for your assistance with this.
KingBeef said:
I can't say that I have noticed it in the past, however, it froze up shortly after I read the email notification of your response and was quite warm towards the top half. I pulled the battery expecting it to reboot anyway. Is there anyway to mitigate the thermal affect if it is indeed the culprit?
I will try the second method this evening and see if there's any change in behavior and report back sometime tomorrow. Thank you for your assistance with this.
Click to expand...
Click to collapse
Yes but it is not recommended. Using Synapse from the playstore will do such a thing but it requires a custom Kernel. If it is a thermal issue your device may be defective seeing that it's spiking so much so quickly and just crashing.
Definitely give the process of elimination a try that I suggest in my previous post. If it fails at the first step of being pure stock no SDCard then I'm afraid you need a new device.
Hi KingBeef,
Unfortunately, I have the exact same issues you do. Except I've tried literally everything. Even Odin back to stock KitKat. Seems to reboot or randomly shut off if more than 3-4 apps are running at completely random times. No SD card as well to confirm it's not that. The only difference I see with your situation is my phone will degrade after 3rd day of use. First 2 days are flawless, then almost like a failing hard drive, things start to domino progressively worse. My last attempt was to run it only in wifi mode, no SIM card.
The only thing left is to consider unfortunately is swapping again under warranty. I myself am waiting until I go back to the US (Cad user here) to swap with TMo for another handset.
Good luck!
Sent from my D6503 using Tapatalk
Hello all. Generally I've been able to troubleshoot all my Android issues on my own. Most of the time someone has had the same problem (amirite?!). However, I'm stumped and could use a little help from the community.
I've been going along on Marshmallow with FK as my kernel. Generally, waiting a bit to take an update til SuperSU was confirmed all working correctly and that there wasn't any surprises. I had been putting off the MMB29V update for a bit just because everything was running fine and I had no real reason to upgrade. Well, one day I started getting a few FCs and things seemed a bit off performance wise so I decided that I'd go and move on to the next release.
Now, since I've had my N6 I really haven't had the need to run a custom ROM which is completely unlike my old habits on the S3. I decided that it's been a while since I've checked out AOSP so I flashed MMB29V using the batch file with no issues and then DU and their recommended GApps. Here's the first hint of an issue. When I loaded up the OS for the first time I got acore and phone FC's constantly. I instantly thought that I didn't wipe something or that I had a bad zip. I re-downloaded everything and checked MD5s. Everything looked good and after the flash I was able to get through the setup wizard without any issues. As I was sitting there checking out the tweaks and options available I started getting FCs again. It seemed related to Google apps. I did the whole process a second time and still had the same issues. Basically it seemed like at some random point in time the FCs would come and then shortly after the device would be highly unstable. I'd get random reboots, etc. Looking at the stack traces the errors seemed like odd NPEs and native errors.
I decided that AOSP wasn't going to cut it right now if I was going to have a relatively unstable phone and went to flash completely back to stock. Much to my surprise I still got the same errors! Apps like Feedly would never even be able to open. They would just FC on launch. The device hot reboots. The phone process seems to crash during most calls. I triple checked my MD5 on the download from Google. Made sure I wasn't doing something super stupid. I even tried doing the factory flash, booting to the welcome screen, then powering down, going to stock recovery, and factory resetting before continuing. All the same errors.
I've flashed back to complete stock a few times before without any issues. I've been able to flash system.img without any issues. Now it seems like the phone is completely unstable no matter what I do. I get the "Your device is corrupt. It can't be trusted and may not work properly." (red) message when doing a cold boot.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?
I've burned through two backup cards of Google 2-Step backup codes! I'd really like to figure this one out!
mikejr83 said:
.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?!
Click to expand...
Click to collapse
You could read the OP of the following thread and flash a debloated and prerooted ROM.
http://forum.xda-developers.com/showthread.php?t=3059493
I guess I'll try that. I'm still scratching my head why a flash from the factory image is still suffering from FC's and general instability. It also concerns me that I get the corrupted message at boot. It would be one thing if I flashed factory, then put a recovery, kernel, and rooted, but I haven't done that.
Hopefully I'll get a chance to try that this evening. Thanks for the link to that image. It's pretty much what I run when I take an update.
N, n, ne, necromancy!
I brought this thread back to life because I've never been able to solve the instability issues since my last post back in March.
Having some free time lately I decided to nuke my device and start again. I first grabbed the latest stock image and flashed stock. Then I downloaded the latest TWRP and Dirty Unicorns and decided that I'd give it a whirl again. I had FC issues right after the first go at it. I decided to try another GAPPs and do it again. I was able to get through setup. It took a few hours but the FCs started again.
I decided that I would try factory resetting the device and then starting a setup. I remembered that on my previous devices that I sometimes would have to do an immediate factory reset after flashing.
Well that did crap. FCs are random. The device is stuck booting now after a hot reboot.
How can I debug this? What do I need to grab from a logcat? Is there a way to run something like memtest to see if there is a bad section of RAM and something against storage to see if there is a bad sector?
This is frustrating as hell!