yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Nebucatnetzer:
I've never tried it myself but AFAIK it should work fine with Slim

I'll give it a try on my grouper since there's anyway nothing on it.
[Nexus 7 Original Development] Nebucatnetzer:
Worked without a problem here.
[Nexus 7 Original Development] -Tiz-:
Thanks! Just to make sure. When the encryption process started...the tablet did not reboot within a minute or so? Because this is what it does on my tablet. And this means that the tablet was not really encrypted. (You can see whether it is encrypted if you try to encrypt it again.)

Assuming that your tablet was encrypted and my tablet was not: what can be the cause? Should a fresh SLIM Rom install be sufficient to solve the problem? Or can my TWRP recovery or LBE Security or other applications be the culprit?
[Nexus 7 Original Development] Nebucatnetzer:
It did reboot. Didn't check if fully is just assumed it worked.
[Nexus 7 Original Development] -Tiz-:
Then it probably did NOT work. You can check this if you try to encrypt it again. If the option is offered, it was not encrypted before (ie the first attempt failed). Normally, the encryption process takes 30-60 minutes or so.
[Nexus 7 Original Development] Nebucatnetzer:
It's not offered again it says it is encrypted.
[Nexus 7 Original Development] -Tiz-:
1000 thanks for confirming that it works!! I will try to figure out what's wrong with my tablet.
[Nexus 7 Original Development] Nebucatnetzer:
You could try to flash the Stock images. If it doesn't work with that it's something with your device.
[Nexus 7 Original Development] -Tiz-:
I am now encrypted. Thanks so much. The app LBE was causing a conflict and prevented the encryption. I worked after I manually terminated LBE.
[Nexus 7 Original Development] Lar5:
Yes, i'm afraid so :(

I had build 1.9 running. Made a Factory reset in TWRP 2.6.3.0, and wiped /system too.

Flashed the test build (MD: f639741bbe731f0e7b6ab00865fa4575), M-kernel and latest AIO.

Reboot and the SlimBean logo stays on. I can't get an ADB connection to pull a logcat.

Hard reboot. Same reset procedure again. Flashed the test build and nothing else.

Bootloop again and still no ADB connection.

Hard reboot. Same reset procedure again. Flashed the test build and nothing else.

(this time not with a cable connected to the computer)

Still hanging at the boot logo and not able to get an ADB connection when a cable is connected.

Hard reboot and SlimBean started almost immediately. (Hmm... I thought i had too wipe dalvik) :confused:

Reboot, wiped the device and flashed the test build again.

Chose "power off" in TWRP and turned it on. Bootloop!

...and no ADB with cable connected.

Three reboots couldn't make it start this time :confused:

TWRP, wipe dalvik and it started

My N7 seems a bit sensitive to the bootloop bug.

I hate to say that the "20131024-0847" build doesn't fix it.
[Nexus 7 Original Development] Nebucatnetzer:
Just tried it here again and it's still working, I hate that bug...
[Nexus 7 Original Development] -Tiz-:
I am on build 1.9. I had multiple boot loops as well. I could finally boot the tablet when I pressed volume down button. Only then the encryption password screen appeared. After I had entered the password, the boot process worked.
[Nexus 7 Original Development] Nebucatnetzer:
The bootloop bug should only appear on the first reboot after a full wipe or when you don't use a lockscreen.

You can fixing it by wiping the cache after that it should work without a problem.

Other loops shouldn't be caused by us.
[Nexus 7 Original Development] grandluck:
I had my 1.9 on my n7 and it works fine. At 1.8 I can't run my office suite probably and fc always. I but after doing a clean flash on 1.9 everything went ok. I no boot loop and fc. I used aio gapps. Thanks for this domain.

---------- Post added at 09:59 PM ---------- Previous post was at 09:57 PM ----------
[Nexus 7 Original Development] android88:
build.2 is up, bootloop bug should be fixed!
[Nexus 7 Original Development] Nebucatnetzer:
I don't think it is.
[Nexus 7 Original Development] s33d1ing:
I will test it later. I need a reminder, is the bootloop happening on a clean install or dirty flash?
[Nexus 7 Original Development] Nebucatnetzer:
Only on a full wipe.

Means factory reset + wiping /system.
[Nexus 7 Original Development] s33d1ing:
Yeah, I just flash build 2 using using multirom, which would be the equivalent of a full wipe, and I ran into the bootloop bug. I flashed it a few times and it happened every time. It booted immediately after wiping dalvik and cache.
[Nexus 7 Original Development] MasterJ87:
Dirty flashed build 2 with no problems whatsoever.
[Nexus 7 Original Development] readinglamp:
Thank you for your help. I just installed Slim_aroma_selectable_gapps and now it works. I don't know why; I tried them before and the didn't work until now :confused:

Does someone have this issue also: When you change your wallpapers a lot (let's say about 5 times in a row, or even more) the wallpaper gets "cut" and the font gets unreadable, and folders stick together and some blurry things on the desk appear? Maybe some objects aren't deallocated properly?

Anyways, the rom is perfect, I really love it.
[Nexus 7 Original Development] carlosgardel:
I always had bootloop with none screen lock and continue to have it in version 2.
[Nexus 7 Original Development] Lar5:
Nice to hear, but unfortunately not correct about the bootloop - not on my device :(
[Nexus 7 Original Development] wotanraca:
Dirty flash without bootloop, and all works fine.
[Nexus 7 Original Development] pancham7:
Dirty flashed. No problems with the boot loop.
[Nexus 7 Original Development] Nebucatnetzer:
Dirty flashing was never a problem.
[Nexus 7 Original Development] Hasuris:
Couldn't get build 2 to boot up after a clean instal. Cache&dalvik-wipe didn't help, phone would get stuck at "starting apps". I had to flash 1.9 again and dirtyflash 2 on top of it :-/
[Nexus 7 Original Development] efan3719:
define stuck. how long did you wait?
[Nexus 7 Original Development] Hasuris:
The circle-animation stopped and nothing happend for a couple of minutes. This should only take seconds.
[Nexus 7 Original Development] coolek33:
Try this: wipe cache, dalvick, data and system. Flash rom and gapps. Power off via recovery. And then boot.
[Nexus 7 Original Development] annoyingduck:
Build 2 booted up just fine for me, and I have one of the difficult booting devices...
[Nexus 7 Original Development] WhiteiceDMSTech:
So what kernel is everyone using on stable build #2?

Thank you,

Whiteice
[Nexus 7 Original Development] Lim Wee Huat:
Running this with M kernel....
[Nexus 7 Original Development] efan3719:
Running stock slim. Have had no issues that warrant using anything else
[Nexus 7 Original Development] MasterJ87:
M-Kernel MR2
[Nexus 7 Original Development] jmark13:
My Nexus 7 is bricked after installation. I followed directions, wiped everything, formatted everything. I bootlooped like another post said, at starting apps. I then loaded into recovery and now it keeps trying to start into recovery and then restarting. I can't get it to go anywhere else. I let it go until running out of juice. I have no clue what to do now. No way to get into bootloader, no way to get into recovery. Any suggestions?
[Nexus 7 Original Development] thereal_bigjake:
Are you using twrp or cwm? Holding volume down when turning it on should bring you to the bootloader.
[Nexus 7 Original Development] Nebucatnetzer:
In addition what did you flash?
[Nexus 7 Original Development] jmark13:
I've held down the power with the volume buttons for 10 minutes straight, nothing happens, just continues to bootloop into CWM. To give a better understanding, I get the Google screen with unlocked pad at the bottom, it then tries to go into CWM, where i see clockwork mod 6.0.4.3, then it restarts and does it all over again. Can't get out till power runs out. When i try to turn it just starts looping again. I clean flashed the 2.0 build with the gapps.
[Nexus 7 Original Development] thereal_bigjake:
Try adb reboot bootloader
[Nexus 7 Original Development] Nebucatnetzer:
Pew hard one.

No chance to do anything inside the recovery?
[Nexus 7 Original Development] jmark13:
Nope, nothing. It keeps trying to startup and go into recovery, only to bootloop. If i plug in the usb cable to my pc, it doesnt stay on long enough for adb to establish and run commands. I tried to flash a stock image last night to avail. I think my N7 may finally be toast. I've had it since the day it came out on google play store. Gone through tons of ROMs, never had a problem. Oh well, just more reason to get the new N7. I have to admit this one is laggy and the 8gb hard drive was way too small. I'll add the 32gb Wifi 2013 model to my holiday shopping list.
[Nexus 7 Original Development] demkantor:
Just for fun, charge it full and let it sit for a day or two, then power on while holding the volume down key the whole time

If you end up in bootloader, plug into PC right away

fastboot erase system -w

fastboot erase boot

fastboot erase recovery

fastboot flash recovery recovery.img

Now go to new recovery and flash ROM of choice

If had devices that needed to sit a few days before I could get them functioning again, it defies logic to me but it has worked

Best of luck!
[Nexus 7 Original Development] flexfulton:
It doesn't make sense to me that it would try to go from Google logo to CWM. It should go to the fast boot screen where you can pick bootloader mode or recovery which would then be CWM.

Have you tried just holding the power button for a few seconds to turn the device off? That's always a fail safe way to power down a locked up or bootlooped or hung up device. Try that so your unit is off then start fresh with the power button and volume keys instead of trying that combo when in bootloop. I know I've had trouble in the past getting into recovery when bootlooping but powering down first really helps. Try a couple times before giving up. It can be tricky.
[Nexus 7 Original Development] flyguy914:
Does this have tablet ui
[Nexus 7 Original Development] dirtygoldfish:
Nope
[Nexus 7 Original Development] jschill31:
Hello,

Anyone who gets stuck on the Slim boot screen will need to hold the power button till the unit powers down. Then press the volume down key to allow bootloader to come up. Use the volume down to choose recovery then press the power button to execute. Once you are in recovery you will need to wipe Dalvik and cache (sometimes Dalvik is all that is needed). Once you do this you will be able to boot into the build. It seems that there still is a lock screen bug. Make sure you do not turn off the lock screen. If you leave the build on the default lock screen (swipe) you should no longer have booting issues going forward. I have no idea why this still exists, it has been present since 4.2.2 build 8.1. It does not seem to affect all Grouper devices, only older models.

Cheers
[Nexus 7 Original Development] efan3719:
on the newest build this was fixed for me. and i have an early 8 GB model. so maybe not as simple as it being older models.
[Nexus 7 Original Development] coolek33:
Dunno what U guys did to fix the bootloop problem but on my 16gb it Didnt boot at all after a clean install. None of the methods worked. For a moment i thought ill brick it like the guy few posts above. Restored backup and dirty flashed b2. First time i had to do this but seems working fine.
[Nexus 7 Original Development] jschill31:
Hello,

Although we have the same model we will have different board tolerances...probably why this bug has not been squashed. Could be as simple as a voltage spike in the final loading process (when the screen gets slightly brighter on Slim boot). All I can verify is it has been present for weeks on my personal builds as well as their releases. I only have the issue at boot if I have the lock screen disabled which is my preference for my tablets. No big deal but annoying...

Cheers

Sent from my EVO
[Nexus 7 Original Development] Markyiptw:
Guys, I think the bootloop problem is because of different recoveries. I switched from CWM and TWRP (different versions) and only twrp 2.6.3.0 booted the device.

CWM and TWRP 2.6.3.1 caused bootloop.

I'm using stable build 2.

Hope this will help;)
[Nexus 7 Original Development] coolek33:
2.6.3.0 Didnt boot it for me at all so its not recovery related.
[Nexus 7 Original Development] SiNJiN76:
Finally got past the boot screen (wiping both caches)! But now after it upgraded all the apps...It is stuck on Starting Apps. If I reboot, it gets stuck on the animation again. So I'm in a cycle here. Need to clear caches again...Then it just gets stuck on Starting Apps.
[Nexus 7 Original Development] coolek33:
Yep. Same for me. Ive dirty flashed build 2.
[Nexus 7 Original Development] ricardowec:
This is the first time I get stuck on the Slim Logo.

I am on release 2 with the latest GAPPS and I turned the tablet off.

Whe I returned home, I turned the tablet on and gets stuck on the Slim logo.. did the Cache/Dlevick wipe.. same thong... did a dirty flash of the rom.. same... turned off via recovery.. same

Anyone can help.Thank you
[Nexus 7 Original Development] stuiegreen:
Tried installing this rom coming from a stock but rooted 4.22 followed all the instruction but my nexus 7 is now stuck at a slim boot logo not moving on

Any thoughts as to what that might be and how to fix, I have a nandroid so can restore but really want to try this rom

EDIT

ive done the dalvik and cache wipe as suggested above and that fixed it
[Nexus 7 Original Development] gu_de_o:
My solution to the bootloop was to full wipe, then install an earlier weekly build (1.9 in my case), and then install the latest build directly on top without any wipe
[Nexus 7 Original Development] bettzysdaddy:
Sorry for the noobish question, but how do I get to mount my tablet using 4.3 b2 to recognize it on my PC (win7 64bit) so I can upload stuff to my tablet?

Thanks
[Nexus 7 Original Development] coolek33:
Turn on mtp in storage settings, Turn off fast charge and USB debugging.
[Nexus 7 Original Development] bettzysdaddy:
Where do I turn off fast charge?
[Nexus 7 Original Development] coolek33:
Forgat about that. Dont remember if its there. If yes U can use toggle from QS or power widget in notification drawer. Or trickster mod. But i think there is no fast charge on grouper.
[Nexus 7 Original Development] bettzysdaddy:
Thanks for the help. One more thing, is there a way to get the menu option in the navigation bar? Thanks
[Nexus 7 Original Development] wotanraca:
Only one way: menu visibility - always show
[Nexus 7 Original Development] bettzysdaddy:
I meant like a pop up menu button like on a galaxy s2
[Nexus 7 Original Development] wotanraca:
What pop up? Slim pie??
[Nexus 7 Original Development] bettzysdaddy:
See the navigation on the Samsung phone? See the menu button on the bottom? That one. Except on our navigation bar.
[Nexus 7 Original Development] dirtygoldfish:
That was removed several builds ago because it's a feature Google no longer supports since it doesn't follow holo guidelines. Unlikely it will ever be added back.
[Nexus 7 Original Development] lagoskon:
We have an updated final 4.3.1 build v2.2

Just dirty flash over build 2

Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
[Nexus 7 Original Development] ricardowec:
GPS not working on my tab after 2.2 update :mad:

Sent from The Beast + using Tapatalk 8 beta
[Nexus 7 Original Development] Nebucatnetzer:
It's always the same:

You can flash it dirty but if you experience any problems do a full wipe.
[Nexus 7 Original Development] lagoskon:
Confirmed that yesterday when I took Nexus 7 out of home and needed gps ... :(
[Nexus 7 Original Development] metalgearhathaway:
Chaps, I have an issue getting into Display settings, I get a settings has stopped, no matter what type of flash I do on the phone. All other options are all accessible. I had been on SlimKat and then reverted back to 4.3.1 build 2.2, a full wipe of course, could the issue be linked?
[Nexus 7 Original Development] lagoskon:
Display options works OK here. Did you manually wipe system also??? (twrp)

Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
[Nexus 7 Original Development] metalgearhathaway:
Found the issue, if you have no screen security set, apparantly that is a known problem, enabled slide as basic security and all ok! Cheers for responding :)
[Nexus 7 Original Development] JT1510365:
Any chance someone has the latest slimbean 4.3 ROM on hand? If you do can you please upload it and mirror it for us as the original download site does not have the builds anymore:) Thank you
[Nexus 7 Original Development] ianPhillips1:
Lols "beta" .....best beta I ever ran.

Sent from timeout

---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------

I had to use TB to convert flash to a system app after installing and is working. Flash 11.1 working in chrome and aosp.

Sent from timeout
[Nexus 7 Original Development] coolek33:
Is it only me or the contacts in trds mode are so white that i barely see them? Flashed b1 with slim gapps (clean install).
[Nexus 7 Original Development] NaveenKD:
I finally got 4.3 working after multiple reboots.

What worked for me, just flash the ROM alone after all wipes and reboot with wipe cache & dalvic.

Go back to recovery again and flash slim gapps.

Anyone has an idea how to give access to folders to restricted profiles?. I created a profile for my 4 yr old son so that he can play his games and watch cartoon movies. While the enabled apps work perfectly under his profile, all file explorers and dice player is not able to see any videos in the movie folder. This appears empty under his profile.

GTN000-Slimbean-TSF-CrimsonCobalt
[Nexus 7 Original Development] BlechMann:
yeah, thank you. confirming flash working as system app!
[Nexus 7 Original Development] mrdevil_25:
I still cant get flash to work on android browser.

Also i cannot sync my bookmarks (from google chrome) to android browser :confused:
[Nexus 7 Original Development] efan3719:
Flash was semi working until making it a system app. I think it's an issue with 4.3 and Flash.
[Nexus 7 Original Development] ricardowec:
Latest flash for Android doesn't even load into user space when converted to systems app. As a user app, it loads but hangs.

Sent from The Beast + using Tapatalk 8 beta
[Nexus 7 Original Development] kbeezie:
Cannot turn the screen on my Nexus 7, beta1

Full logcat

http://pastebin.com/qWW1pn6a

dmesg

http://pastebin.com/vhpHeiCy
[Nexus 7 Original Development] nadiros:
See attached. Firefox and Flash version 11.1.115.11
[Nexus 7 Original Development] waz675:
I recently installed this but I can't seem to find any setting to config what the navbar buttons short and long press do. Does the build have an option to configure them? Thanks
[Nexus 7 Original Development] ianPhillips1:
Settings\advanced\navigation\navigation bar \buttons click to changed primary, long press to choose long press action . Click on icon to change icon

Sent from timeout
[Nexus 7 Original Development] ianPhillips1:
The version I converted to system app

Sent from timeout
[Nexus 7 Original Development] waz675:
Thanks for the info. I was being thrown off by seeing the shortcuts options before buttons and going back. Many thanks!
[Nexus 7 Original Development] zedmarcus:
Hmm... appy geek keeps force closing for me. Apart from that all is good here.
[Nexus 7 Original Development] kufikugel:
and swipe away to delete a button :p

@ appygeek....yes we know about it....and I think I fixed it 2 min ago lol. Compiling now the fix
[Nexus 7 Original Development] clewis:
Bugs I have found with beta 1

1. Touchscreen will randomly stop working for a minute or two, sometimes need to reboot.

2. Device will completely freeze and must hold down power button to redstart the device.

3. Some apps just won't open (most will)

4. Some times issues with side loading apps.

But apart from the bugs above it works great and is very fast when not experiencing issues. Easily the fastest and smoothest 4.3 ROM out now.
[Nexus 7 Original Development] thereal_bigjake:
I haven't experienced any of those bugs on a clean flash using Faux 021.
[Nexus 7 Original Development] dareino:
I may have found my favorite ROM!....its really nice and fast..Im a PIE user so happy to see it implemented....

great job!

thxs

d
[Nexus 7 Original Development] Rechinica:
no go

Unfortunately i can;t install beta1.Tried:

1) Wipe data + cache + dalvik -> flash rom and gapps -> reboot -> stuck on slim logo -> wipe cache and dalvik -> reboot -> stuck on slim logo

2) Wipe data + cache + dalvik -> flash rom and gapps -> wipe cache and dalvik -> reboot -> stuck on slim logo -> wipe cache and dalvik -> reboot -> stuck on slim logo

3) Wipe data + cache + dalvik -> flash rom -> reboot -> stuck on slim logo -> reboot -> wipe cache and dalvik -> reboot -> stuck on slim logo

Not sure what to try next; btw works wonderful on gnex :)
[Nexus 7 Original Development] coolek33:
Try again Wiping also system.
[Nexus 7 Original Development] BlazinDroid5280:
Flashing the alpha I played the wipe/install game for a few rounds before it installed and worked correctly. Also had issues getting superSU flashed. Finally all worked.

Beta along with the new gapps installed without a problem. Still wiped cache and dalvik and is running smooth and fast.
[Nexus 7 Original Development] :
Same thing.....wiped system as well too.

---------- Post added at 02:04 PM ---------- Previous post was at 01:54 PM ----------

K.....all I did to fix was while stuck on slim logo.....booted into recovery....didn't wipe anything.....just flashed rom again....rebooted....and I'm booted up now.

Try that. ;)

---------- Post added at 02:33 PM ---------- Previous post was at 02:04 PM ----------

Downloaded titanium backup and pro key....and yes....had to change path from O to legacy as posted in lots of threads to get restore to work. Works fine now. :)

Great job Android88. Nice to see you since you've moved on from t989 and All-star too. ;)
[Nexus 7 Original Development] Rechinica:
Thanks! that worked for me also!
[Nexus 7 Original Development] :
So if anyone has trouble getting stuck at slim logo after following instructions to the letter.....just boot back into recovery and without wiping anything....flash rom again...not gapps....just rom....and reboot.

Worked for a couple of us now. ;)
[Nexus 7 Original Development] ricardowec:
Following instructions and changelog, you have to wipe cache and Dalvik after flashing the rom and all the extras. If you do things right you shouldn't have any boot issue.

This ROM just works!!

Sent from The Beast + using Tapatalk 8 beta
[Nexus 7 Original Development] :
I'm not new....I always do that. ;). And i did say to install following instructions to the letter, right? Sometimes what works for one device doesn't for another.

You should know by now that people will always have issues occasionally, even if they read perfectly well and follow instructions.

Good advice tho! You certainly are not wrong. :)
[Nexus 7 Original Development] davy917:
Seeing some serious row banding.. Anyone else?
[Nexus 7 Original Development] Mightycaptain:
Had an issue where I couldn't restore from TIB. Nothing would restore on my nexus. Had to install Supersu from the play store. Open the app and do the recovery option to install. All was well after that. I hadn't seen that commented on yet. I had enabled root on the rom prior to installing supersu. It would grant rights to TIB. But no apps would restore. I could restore Bluetooth pairings and wifi though. Otherwise Rom is real solid.
[Nexus 7 Original Development] dareino:
I was stuck on the logo screen when I first installed too , then after booting into recovery I just wiped dalvik and cache and was good to go. I normally wipe caches after installing ROM,gapps and in this case SuperSu

d
[Nexus 7 Original Development] davy917:
Its been mentioned I believe, I had the same issue. Change the directory to legacy from 0
[Nexus 7 Original Development] Mightycaptain:
Missed that...

---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------

Thanks for calling me to task. Got to read more better...