yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] jrocc28:
Hey All,

You guys seem to be headed in the right direction. Hopefully you guys crack this soon! Skell-fring-heX keep up the good work and Thank You!! After numerous rooting attempts using auto-root tool kits and scripts for the N7 and one for the A110 and after just shy of a months time, along with a whole lot of reading and searching the web for countless hours upon hours, my task is finally complete! I was able to manually root this puppy! FINALLY!! THANKS to Skellums post two pages back I was able to flash the rebuilt Clockwork image then followed it with busybox and su and it was a done deal! I couldn't be happier, this tab felt different immediately! Just after the reboot I jumped into my box account and started downloading all my root apps, threw some tunes on updated the binary, along with about 20 or some odd background processes going on, 7 market updates, incoming messages, I mean I really floored the pedal here, with the internal memory full and the ram about to top out, I verified su binary and busy box one last time and checked my clockwork backup, installed titanium not knowing what to expect, I hesitantly press open, and the very second my finger released that key, the su access promt popped out of nowhere faster than I could blink an eye, I can't explain it, its like I give this thing a task, it does a 360, completes it in a couple of seconds then it wants five more tasks..... seems a little abnormal so i had to take a look in system tuner, when I got there; appx. 2 seconds later I was distracted by the 4 cores flexing at me as they were peaking two at a time @ 1.3 then for a split second the other two bottomed out simultaneously and when I flipped to landscape all four instantly peaked and started hang out together.... after staring at them for well over a minute, I glanced at the gov setting and it read interactive.....? Three minutes prior to this this tab sort of felt like it was set to a limitless gov and was OC'd? I can only imagine if or should I say when this thing can be OC'd. It might feel like its doing somewhere around mach 1? I have no idea whats going on with this thing but I think its happy I set it FREE! :)
[Nexus 7 Q&A, Help & Troubleshooting] Skellums:
Were you running 4.1.1 or 4.1.2?
[Nexus 7 Q&A, Help & Troubleshooting] jrocc28:
4.1.1
[Nexus 7 Q&A, Help & Troubleshooting] Skellums:
So I followed this:

http://www.mydroidworld.com/topic/9778-how-to-create-an-insecure-boot-image/

And got the attached, if anyone wants to take a stab at flashing it! Definitely make a backup of your current boot with the recovery first, or pull your boot.img using the dd command I used:

dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img

And as always, I take no responsibility for the outcome of using the file. I hold no liability for loss of data or causing your device to no longer function.
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
Yay! in seven more hours I'll be able to give it a shot. I read the thread that you followed, I was surprised at how quickly something like this could be done. I'm hoping this works, then the recovery can mount /system and our issues are solved!

Do you think there's a difference between kernel 3.1.10 running 4.1.1 and 3.1.10 on 4.1.2? I only ask cause "some" people were able to get root on 4.1.1, and others couldn't. From everything I've read so far, the failure to mount /system seems to be the issue in this ordeal, and some had this issue with 4.1.1.. It's kinda strange.
[Nexus 7 Q&A, Help & Troubleshooting] Skellums:
I have no clue.. There's likely some underlying changes (obviously the secured /system), but I wouldn't know what other "fixes" they had thrown in there. Wasn't one of the fixes in 4.1.2 for the SD-card unmounting causing a system reboot? I'm not sure if that would be at kernel or OS level.
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
Hmmm, could be a mounting problem that triggered a kernel panic? heh, not sure.

I won't be able to test your boot img... Unfortunately CWM will NOT perform a backup, it attempts to start, get's to backing up boot... then immediately goes back to the menu. It seems to be related to the /cache and the log errors. There are a lot of E: log related errors that show up when it first loads. It does seem to have the ability to flash, though.

I checked out the clockworkmod folder on my external_sd, and the backup folders are empty.

Edit: After thinking, for maybe a minute, I decided I'll try a dd of the boot directory to a boot.img, if I can dump the stock boot, I'll give it a try, as I can always flash the boot.img back in with fastboot.
[Nexus 7 Q&A, Help & Troubleshooting] Skellums:
It's likely due to the "generic" CWM I built using the builder site. Likely can't mount /cache or something.. When you can, see if you can grab some of the exact errors, see what we can find.
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
I will load it up again and type out the errors. It has to do with "/dev/block/platform/sdhci-tegra.3/by-name" as that shows up a lot.

Could you upload the boot.img dump that you made the unsecured img from? I forgot I need root to pull mine, and that might save me later!

Unless fringle wants to flash it, to confirm it loads ok?

Edit*** I was thinking, maybe we should start a new thread so we can control the OP with the latest information!

As it stands now, if someone is using 4.1.1 and the all-things-root-toolbox method doesn't work, they have an alternate option via your CWM build.

And we also know that unlocking the bootloader is extremely simple.
[Nexus 7 Q&A, Help & Troubleshooting] fringle:
Doing a backup now and will post results of flashing unsecure boot.img. He just made it from my boot.img which is posted I belive on page 9

EDIT:

Unsecured boot.img booted successfully and able to do adb remount without issue
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
Awesome! I would have thanked you, but XDA limits us to 8 per day, lol..

I'll give this a test shortly, can anyone upload the stock boot.img for me, just incase I get, stuck?
[Nexus 7 Q&A, Help & Troubleshooting] Skellums:
fringle uploaded it on post #87:

http://xdaforums.com/showpost.php?p=36217638&postcount=87
[Nexus 7 Q&A, Help & Troubleshooting] fringle:
The original one I posted on page 9 is stock. At least from 4.1.1
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
Guess I should have "searched" first, huh? lol

Thanks guys, I'm hoping this 4.1.1 kernel runs flawless on 4.1.2. The kernel build is the same for both, 3.1.10...
[Nexus 7 Q&A, Help & Troubleshooting] Skellums:
Check to see if the last_log has changed at all on your tab

shell@android:/ # cd /cache/recovery
shell@android:/cache/recovery # ls -l
-rw-r----- 1 root root 66638 Dec 5 19:57 last_log
shell@android:/cache/recovery #

If it did, see if you can copy it to sdcard through adb shell, it might have the full errors.. That's if the recovery was able to write to it at all!

Edit: Since busybox isn't present you won't be able to just cp it over, you'll need to cat it..

cat /cache/recovery/last_log > /sdcard/last_log

Edit2... Scratch that, you need root to cat the file.
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
Tried it, throws Permission denied at me :\
[Nexus 7 Q&A, Help & Troubleshooting] Skellums:
I have no idea if this will make any difference.. I repacked the recovery image with ro.secure=0, as it was =1 before.. Not sure if this will have any effect for you or not in the recovery when trying to remount /system but it's worth a shot.. I was able to flash it to fringle's tab without issue, I'm in the recovery now.

Same disclaimer, I'm not responsible for the outcome of using this file. I hold no responsibility for loss of data or the inability to use your device.
[Nexus 7 Q&A, Help & Troubleshooting] BryanAM7:
Can you

Can you pliz give me you boot.img?
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
Here's the feedback on the recovery:

Each line starts with E: for the error

E: can't mount /cache*

E: can't open /cache*

E: can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC

(No such file or directory)

Error mounting /system!

I think once it can mount /cache, our issues are solved, which may require the modded kernel.
[Nexus 7 Q&A, Help & Troubleshooting] Skellums:
Hmmm... It seems that it doesn't like the symlinked files..

From adb (in normal boot), are you able to get here and do ls -l ?

shell@android:/ # cd /dev/block/platform/sdhci-tegra.3/by-name
shell@android:/dev/block/platform/sdhci-tegra.3/by-name # ls -l

lrwxrwxrwx root root 2013-01-02 07:55 APP -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-01-02 07:55 CAC -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-01-02 07:55 LNX -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-01-02 07:55 MSC -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-01-02 07:55 ROM -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-01-02 07:55 SOS -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-01-02 07:55 TSS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-01-02 07:55 UDA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-01-02 07:55 USP -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-01-02 07:55 WKX -> /dev/block/mmcblk0p1

I'm curious if it just doesn't like the symlinks to the block devices? I could try directly mapping the fstab to the block devices.. But if they're different on 4.1.2 it won't matter anyway. If they all match up to your 4.1.2 device I'll repack the recovery again with a modified recovery.fstab pointing directly to the devices.
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
shell@android:/ # cd /dev/block/platform/sdhci-tegra.3/by-name
shell@android:/dev/block/platform/sdhci-tegra.3/by-name # ls -l

lrwxrwxrwx root root 2013-01-02 07:55 APP -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-01-02 07:55 CAC -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-01-02 07:55 LNX -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-01-02 07:55 MSC -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-01-02 07:55 ROM -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-01-02 07:55 SOS -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-01-02 07:55 TSS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-01-02 07:55 UDA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-01-02 07:55 USP -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-01-02 07:55 WKX -> /dev/block/mmcblk0p1

-- Mine is identical, the only difference, is the date and time: 1999-12-31 -- 19:00
[Nexus 7 Q&A, Help & Troubleshooting] Skellums:
Here's the new one with the fstab directly linked to the block devices rather than by-name.

Before:

# mount point	fstype	device

/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA	length=-32768
/sdcard vfat /dev/block/platform/sdhci-tegra.0/by-num/p1

After:

# mount point	fstype	device

/recovery emmc /dev/block/mmcblk0p4
/boot emmc /dev/block/mmcblk0p5
/system ext4 /dev/block/mmcblk0p6
/cache ext4 /dev/block/mmcblk0p7
/misc emmc /dev/block/mmcblk0p8
/staging emmc /dev/block/mmcblk0p9
/data ext4 /dev/block/mmcblk0p10	length=-32768
/sdcard vfat /dev/block/mmcblk0p1

Once again (broken record!), I take no responsibility for the outcome of using this file. I hold no responsibility for loss of data or the inability to use your device.
[Nexus 7 Q&A, Help & Troubleshooting] BryanAM7:
how

How do you flash the recovery cwm touch?
[Nexus 7 Q&A, Help & Troubleshooting] sky007:
For flash recovery:

First: unlock Bootloader. That is easy through fastboot.

Second: flash recovery through fastboot.
[Nexus 7 Q&A, Help & Troubleshooting] Skellums:
You have to unlock your bootloader first through fastboot (it will wipe your device), then fastboot flash the recovery image. Touch doesn't actually work, you need to scroll with the volume keys and press power to select.

Unlock bootloader:

fastboot oem unlock

Flash recovery:

fastboot flash recovery <location of recovery image>

Again, this WILL wipe your tablet.
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
# mount point	fstype	device

/recovery emmc /dev/block/mmcblk0p4
/boot emmc /dev/block/mmcblk0p5
/system ext4 /dev/block/mmcblk0p6
/cache ext4 /dev/block/mmcblk0p7
/misc emmc /dev/block/mmcblk0p8
/staging emmc /dev/block/mmcblk0p9
/data ext4 /dev/block/mmcblk0p10	length=-32768
/sdcard vfat /dev/block/mmcblk0p1

Recovery won't boot... Sat there holding vol+ for ever! It dimmed, then lit back up (like it normally does before loading the recovery) but just sat there doing what appeared to be, nothing lol

I'm going to try once more. I will edit this post with any changes...

*Update: Correction; it doesn't dim at all, the screen comes on (black) and just hangs there. I held it for a while, to make sure it had more than enough time to load. Could that mean the bootloader can't find it? Or maybe it has to do with the security change that was made?
[Nexus 7 Q&A, Help & Troubleshooting] Skellums:
Weird.. You should be able to flash back to the previous version. Try the insecure one and see what happens, the fstab change was not made in that one.
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
None of them so far, have mounted anything. My recovery doesn't stick, so I've temp flashed them all. For the superuser, the flash says it went in, but it's just displaying ui prints from the script, no error messages.

It is weird.. But again, it might be the kernel that's required, I'm just a bit hesitant with the 4.1.1 kernel... The tab has the same specs, as the one it was taken from. But the butterflies are in the stomach, lol
[Nexus 7 Q&A, Help & Troubleshooting] BryanAM7:
Can i?

Can i do some backup of recovery.img before do this?
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
If you're not rooted, no you can't.
[Nexus 7 Q&A, Help & Troubleshooting] BryanAM7:
waht

Wath ver of android do you use? 4.1.1 or 4.1.2?

the insecure recovery boot succesfull?
[Nexus 7 Q&A, Help & Troubleshooting] fringle:
Stock recovery is already posted in the tread on one of the pages but as far as I'm aware you can't dump recovery without root.
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
4.1.2, yes the recovery can be flashed with fastboot, but to get into it after, involves selecting power off form the bootloader (after the recovery has flashed) and then holding down vol+ and power, once the tab vibrates, let go of power but continue to hold down vol+ until the recovery screen shows up.

If you're not rooted, there is a file on your phone that will restore the factory recovery when you reboot, you have to be rooted to delete that file. So the recovery at this point, will not stick, as we're still in extreme alpha stage of this project.
[Nexus 7 Q&A, Help & Troubleshooting] BryanAM7:
question.

look, i flashed the boot.img of the pague 9, but it doesn work, it brick my phone, but for luck in the acer support pague they release the update for recorvery mode, i used it and it works, the phone boot normal again, that mean the update have a boot.img inside, can you find it and make it insecure for unlokc the r/w mode?

sry for my fuking bad english lol
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
That might work. You flashed the wrong kernel, but it might not make much difference if it wouldn't boot. The insecure kernel is on page 10.

What version are you running, Bryan? 4.1.2? Can you go to Settings > About tablet and give us your Image version?
[Nexus 7 Q&A, Help & Troubleshooting] BryanAM7:
ver is

yes 4.1.2, but lol i dont have any idea of how do taht on linux lol
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
Open your app drawer > Click on Settings > Then scroll down to About tablet and click on it.

You should see Image version, in the list, just type it out here if you don't mind. :)
[Nexus 7 Q&A, Help & Troubleshooting] sky007:
Looks like 4.1.1 kernel won't work on 4.1.2.

And checked update script in official release, there is a patch applied to root.

ui_print("Patching boot image...");

apply_patch("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:4378624:cb8804a51c45d39276ec57f118f6cf25e2d621b2:4401152:7886a9b48ec9b3fcac5706f0efc1f0f097145b3e",

"-", 7886a9b48ec9b3fcac5706f0efc1f0f097145b3e, 4401152,

cb8804a51c45d39276ec57f118f6cf25e2d621b2, package_extract_file("patch/boot.img.p"));

Just an idea, can we just manually apply patch on 4.1.1 boot.image, and then unsecured it?
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
Good catch! That might do it!
[Nexus 7 Q&A, Help & Troubleshooting] BryanAM7:
image ver

the image ver is: Acer_AV051_A110_RV00RC09_WW_GEN1
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
Same version as mine, other than that mine ends with CUS1

It's getting confusing, there are a few different images that apprently can only be upgraded from the older image of that SKU. Not sure how valid this is for the Kernel, though. Could be minor OS tweaks depending on your location.
[Nexus 7 Q&A, Help & Troubleshooting] fringle:
Pretty sure the version has to do with country. As mine ended in u the only country I could select during initial setup was United States even though I'm in Canada.
[Nexus 7 Q&A, Help & Troubleshooting] BryanAM7:
it say

It say boot failed.... :crying:
[Nexus 7 Q&A, Help & Troubleshooting] DjDom:
How would you like me to give you it?

Tell me what to do ~

---------- Post added at 08:59 PM ---------- Previous post was at 08:53 PM ----------

I may sound like a total noob right now, but Acer's website has the kernel source code for 4.1:

http://global-download.acer.com/GDF...A TAB&Step3=A110&OS=a10&LC=en&BC=Acer&SC=PA_6

They also have the OS Upgrades, if that's any use..

Trying anything I can to help, since I'm not exactly a coder like the rest of you here.
[Nexus 7 Q&A, Help & Troubleshooting] fringle:
So I've decided to download an update from the acer website for two differnet model numbers and the boot.img.p file inside each is a different size so it appears the kernel is slightly different.

The one from Acer_AV051_A110_RV00RC07_PA_CUS1 is 3982kb and the one from Acer_AV051_A110_RV00RC07_WW_CUS1 is 3978kb. And those are both 4.1.1 The file sizes for 4.1.2 were slightly bigger then both of these. But if there is a way we can unpack the boot.img.p it appears we could make the necessary changes. I just don't know enough about it to attempt it at the moment.
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
It is strange, might be worth it to figure out a way to get our hands on the stock 4.1.1 ROM from Acer, and flash it back, if it's even possible to go backwards. A good tip for any new comers to this tab, would be to keep the 4.1.1 should you want a quick root method.

I've requested some help from a recognized, well respected Kernel developer here on XDA. Let's keep the fingers and toes crossed, maybe a custom kernel will solve the issues accross the board. I've run older custom kernels on newer ROMS before with my Nexus S, I'm sure we're just missing something in the configuration. Let's see how this plays out.

I have to say, that in the last couple days, this tablet has come a long way. It's nice when you have a bunch of people all willing to help each other and pitch in, what they can.

Regardless, I love this tablet, I won't give up on it.. Even if I have to delete a few things to make room for a new game, so be it, lol.
[Nexus 7 Q&A, Help & Troubleshooting] DjDom:
My tablet won't turn on after the battery died.

It reboots at the lockscreen even after it's been charged.

Tried wiping cache in stock recovery.

Can you tell me how to unlock the bootloader on V. 4.1.2, since I'm gonna need to do a hard reset anyway to fix this issue.

Either way, when I go to root, I'll lose everything..
[Nexus 7 Q&A, Help & Troubleshooting] heX79:
It's the same method. Make sure the drivers are installed on your PC. Have the SDK unzipped to the desktop > navigate to: adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools -- or whatever folder you have ADB and Fastboot in. Then, while holding down Shift on the keyboard, right click in the folder and select "Open command window here".

Turn USB debugging mode on, under Settings > Developer options > USB Debugging

Plug in the tablet,

In the command window, type: adb devices -- make sure you see a device in the list.

Then type: adb reboot bootloader

Once in the bootloader, type: fastboot oem unlock -- hit enter, then on the tablet, scroll down via the volume keys and select "do it" -- I believe is the option, lol.
[Nexus 7 Q&A, Help & Troubleshooting] jrocc28:
heX ,

I totally agree with you. The development on this tab was almost non existent a week and a half ago and the progress that has been made in the last couple of day by yourself, Skellums, and fringle has been a tremendous step toward the goal of every XDA member that owns a A110 Tab; achieving root. As I see you guys have narrowed it down to the final obstacle that stands in the way in achieving that goal for the updated firmware 4.1.2 which is the secured boot.img and something has already been accomplished here; without that rebuilt recovery that was posted a few pages back, I would not have root today. It took me one month to figure out how to root this Amazing little device. As my Tab came with the alternate version of 4.1.1 which was indeed immune to the "Data Restore" exploit used in the auto root tool kits of the N7 and some A110's . What a frustrating month it has been, on several occasions I even thought of returning this Tab for the "ShowStopping" Google branded frontrunner that rhymes with Texas. I'm glad I did not ! :) Man was it worth the wait!! I noticed the diff immediately upon my 1st reboot from manual root. After updating su binaries, removing the bloat and installing several must have root apps, a few ram tweaks, granting and fixing perms, then clearing all caches; this little tab rebooted as a completely different tab! It's a more efficient Tab, Everything just feels So Responsive and Fluid it's almost to good to be true! You all will see what I'm talking about hopefully soon!!! It is such a noticeable difference its' not even funny! When this lil guy gets a custom ROM and an OC'd / UC'd kernel, this bad boy will be eating N7's for bfast, lunch, & dinner!!!!! Cheers :beer: :D:thumbup: :beer:

Thanks Guys!

I will be pulling for all of the 4.1.2 Faithfuls!!!!!!
[Nexus 7 Q&A, Help & Troubleshooting] DjDom:
I can't boot cause NVCPL stopped working..

Any way to fix it? It's getting quite annoying.
[Nexus 7 Q&A, Help & Troubleshooting] izakum:
I am wondering if the following applies... It is from the developer who developed recovery for Acer Liquid, one of the earliest Android Phone by Acer... Apparently Rogers/Fido Rom will prevent the recovery from sticking when reboot so you have to unplug the battery and reboot into recovery with vol down + power.. I know this tablet does not have removable battery so either let the battery runs down and then charge up or open it somehow.....

Source: Malez Recovery
[Nexus 7 Q&A, Help & Troubleshooting] DjDom:
Pulling out the battery means the phone is fully shut down..

Pressing and holding the power button on the tablet should also shut it down fully.

Unless I'm not understanding something here.

---------- Post added at 01:53 AM ---------- Previous post was at 01:51 AM ----------

Update to this:

I gave up, so I did a hard reset through recovery.

While I was at it, I unlocked the bootloader.

So, my tab is currently 4.1.2 w/ an unlocked bootloader.

Still curious as to what exactly NvCPL is and why it caused my tab to fail randomly.
[Nexus 7 Q&A, Help & Troubleshooting] jasmineloveflower:
hi please help just purchase a110 tab yesterday. I haven't updated still on firmware 4.1.1. However i still can't seem to root. I have tried rooting with the universal root with no success i trying to flash with boot loader however i cant seem to understand how to do it. I have boot loader install however i do what are the steps in unlocking it. after that how do i install the flash recovery image you guys have posted here thank you jazz