Database Info

[MOD][Update: 12-Aug-2011]Rooted CG from CH Leak

Thanks to dangpzanco for the GREAT IDEA.
I finally got my Rooted GB working here. I can't provide a download link now but I'm going to do it later for sure.
Apparently there was a final signature check that was done somewhere after mounting the cache partition, preventing me from booting with a pure update.zip on top of froyo /system. Thanks to dangpzanco I could bypass it and get root.
Quick Guide (requires froyo, root and Droid2bootstrapper):
1. Download fixed SBF bellow. It's made from the CH leak containing ONLY: CG35.smg (boot) CG47.smg (recovery) CG61.smg (devtree) firmware.hmg (header) RAMDLD.smg (flash updater).
2. Download root_and_recovery.zip and copy it to SD Card.
3. Download full leaked SBF from General Forum (CH, signed) and use MotoAndroidDepacker to extract all images.
4. Copy the CG39.smg to /sdcard/
5. Boot into CWM
6. From CWM open adb shell and use this command: dd if=/sdcard/cg39.sm of=/dev/block/system
7. Still on CWM apply root_and_recovery.zip
8. Still on CWM wiped everything
9. Boot on bootloader and flash fixed SBF
10. Reboot

I actually did the same thing! I read it somewhere in one of the topics. I installed Defy BootMenu instead of CWM. Works great! Right now I've almost removed all the Chinese crap and got the GApps working (from CM7).
I also removed the Blur items for the Chinese SN's. I'll see if I can get Twitter and Facebook working with it.
2nd-init would be nice too actually. Does the method provided in the other thread work with this ROM?
Edit: the instructions were indeed from dangpzanco!

And right now I found a possible bug. My camera doesn't work. Everything is black and stays black. Photo's are take as they should however.
Can you check whether you have the same issue?

w0ndersp00n said:
And right now I found a possible bug. My camera doesn't work. Everything is black and stays black. Photo's are take as they should however.
Can you check whether you have the same issue?
Click to expand...
Click to collapse
Here it works fine. Have you tried to edit /system/build.prop?
Change device from ME722 to A953.

Yes, I changed it to A953...
Maybe I have deleted something that was necessary for the viewfinder... But what xD
Edit: Allright, nevermind. Somehow a reboot fixed it :-D On to the next step

Something bad happened when I tried to apply 2nd-init on this. The phone rebooted just after 2nd M logo not allowing me to get into CWM. Wierd, since CWM should take place before 2nd-init. Will need to raflash froyo and start over. We should find a way to root Gingerbread without CWM to make things faster.

That's odd indeed. I have to say, I think the CWM method of rooting is actually quite easy. For SuperOneClick I need to get my PC/laptop out every time and with the update.zip I can do it as I please.
I really hope you'll succeed wit 2nd-init. If you need help, just shout! Today and tomorrow I have enough time.
I'll make a nandroid of my current setup, so I can continue trying out stuff.

w0ndersp00n said:
That's odd indeed. I have to say, I think the CWM method of rooting is actually quite easy. For SuperOneClick I need to get my PC/laptop out every time and with the update.zip I can do it as I please.
I really hope you'll succeed wit 2nd-init. If you need help, just shout! Today and tomorrow I have enough time.
I'll make a nandroid of my current setup, so I can continue trying out stuff.
Click to expand...
Click to collapse
Yeps, it is easy indeed, but to do it I need to SBF froyo before installing GB again. In other words if I mess up the phone I will need to flash 2 versions instead of one. That's why it would be easier to flash just GB.

Hey there, nice I could help.
I think you could copy the /dev/block/system back after rooting and build the SBF with it.
@Milestone 2 (Finnaly on Gingerbread!)

dangpzanco said:
Hey there, nice I could help.
I think you could copy the /dev/block/system back after rooting and build the SBF with it.
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
I tried that with froyo but it didn't work.

you can try also this defy leaked gb rooted nandroid backup.
http://www.multiupload.com/SPZ8SIEC60
version 4.5.1-134 multilanguage.
use fixedsbf from new leaked milestone2 rom and milestone2patch from MS2Ginger thread.
In this rom /system/app/kpilogger.apk cause battery drain so delete it after install.

Something is seriously wrong... My backlight never shuts down. It's black, but when it's dark you'll see it's still on!
I actually can't change the brightness from settings. So I did a complete reinstall and the problem persists!
I'm using brightcontrol app now to adjust the brightness, but does anyone else has this issue? Or is it something I did?

r2beta0 can you please upload the nandroid of your system?
I try to get adb in CWM but it didn't recognize it.

julianlatasa said:
r2beta0 can you please upload the nandroid of your system?
I try to get adb in CWM but it didn't recognize it.
Click to expand...
Click to collapse
My system is messed. I still need to get 2nd-init to work. I'm having a lot of trouble trying to compile my custom version of logwrapper hijack. As I don't have experience in compiling stuff to ARM/Android it is being a pain in the a**. I'd appreciate some help here

Try setting up a QEMU environment with the GB leak kernel's zImage.
Edit: Now we can port CM7!!! Devtree.img is now signed.
@Milestone 2 (Finnaly on Gingerbread!)

dangpzanco said:
Try setting up a QEMU environment with the GB leak kernel's zImage
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
And how do I do that?
I tried some ways till this point:
- Installed CodeSourcery G++ Lite toolchain (could compile, but android didn't run)
- Installed NDK and tried some commands I could find on blog posts (no luck)
- Now I just finished setting up an ubuntu 10 VM with all the steps described on developer.android.com. I think I am now able to compile android system, but I don't want to as it will take a LOOONG time.
Do you know how do I build a specific module into android source? For example:
system/core/toolbox
I'm a developer, and have compiled stuff to run on linux/unix many times. But this ARM stuff is way complicated. Writing the code isn't the problem, but compiling is. Lots of flags I haven't seem before, and so on.

r2beta0 said:
And how do I do that?
Do you know how do I build a specific module into android source? For example:
system/core/toolbox
Click to expand...
Click to collapse
I just uncovered this answer by myself.
A 'make toolbox' on root folder seems to work just fine. Now I need a way to define new targets on android build system.

http://and-developers.com/
Has a page just for compiling the kernel from source. (I can't remember the link)
I also got stuck when trying to compile from AOSP... but I think you need to have ALL the files downloaded from source (specially the big prebuilt folder) even if you want to compile a single binary.
Well I'm not sure of anything...
Edit:Now I read what you wrote... so never mind you got it.
@Milestone 2 (Finnaly on Gingerbread!)

dangpzanco said:
http://and-developers.com/
Has a page just for compiling the kernel from source. (I can't remember the link)
I also got stuck when trying to compile from AOSP... but I think you need to have ALL the files downloaded from source (specially the big prebuilt folder) even if you want to compile a single binary.
Well I'm not sure of anything...
Edit:Now I read what you wrote... so never mind you got it.
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
Yeps I've made a full repo sync. It took 3 hours and is worth 6GB disk space

Great news! Can't wait to see a true custom ROM working
Just thought I'd share what I've learned: don't mess too much with your build.prop Somehow my modifications were the reason of my backlight not working right and making every app crash that wanted to use a sensor. But it's working again

[Q] Ubuntu Installation help

The instructions for installing ubuntu are not that clear. so what is the ROOTFS and whad do i do with it. also i am trying to make it dual boot with android as the default opearating system. So what kernel do i need and what else do i need to get the touchpad working and wifi working

I'm trying to figure this out myself. I really don't have much time on my hands to figure out all the 1337 lingo surrounding the installation process of the dual boot ability. For once, I'd like someone who's technically literate enough to write down all these instructions in a dummies language... much like my gtab for dummies website in my siggy.
Just remember. If you're going to ask questions here. Make sure you apologize a lot of times. 1337s don't like questions.

goodintentions said:
1337 lingo
.......
1337s don't like questions.
Click to expand...
Click to collapse
What lingo? an example would be good.
And what "1337"?

"Before using this pack back up any data that you may have on your device, this method is destructive to data, and will wipe everything. If you plan on dual-booting with android you will need to download a full system like prime and put the images (system.img boot.img recovery.img) in images/
This package does not include the ubuntu rootfs. You should have already downloaded this from the link located on this forum post located http://rootzwiki.com/showthread.php?...he-transformer or http://forum.xda-developers.com/show...p?p=16097869if you haven't downloaded it yet it is 950MB so start it downloading and grab a coffee. Decompress the gzipped tar to images/
With that taken care of, here are the instructions for use:
1) select whether you want to dual boot, and which OS you want as your default.
2) make absolutely sure that you have backed up your data, everything past this point is going to destroy your data.
3) run the appropriate sh for the choice you have made in step 1
flash-purelinux.sh for a pure ubuntu setup, this is no android recovery is ubuntu single user mode.
flash-linux-android.sh for installing android and linux dual boot with android as the default OS. To boot into linux hold power+vol-down until prompted on screen to press vol-up.
flash-linux.sh for installing android and linux in dual boot with android and linux, linux is the default OS, to boot into android hold power+vol-down until prompted on screen to press vol-up"
From the ubuntu thread's OP, instructions for doing this. Says put rootfs in the /images folder of the flash kit along with the nvflash imgs from the android rom you want to dualboot with. Even shows you the options for which dualboot method you want and how to use it. If you consider this l33tspeak, I'm wondering what you consider basic English. If you can't even understand basic instructions, then don't use it. Too many people come into somewhat advanced technical methods for enhancing tech products and expect people to hold their hands through the methods. Of you want to understand these things, start googling and take some college courses. Xda isn't the place for learning technology.
Sent from my creaky Thunderbolt

i tried to download the rootfs and when i unzip the file all that comes out is ubuntu.img is this normal and if i want to dualboot with android where do i put the files and what kernel is required

yalkowni said:
i tried to download the rootfs and when i unzip the file all that comes out is ubuntu.img is this normal and if i want to dualboot with android where do i put the files and what kernel is required
Click to expand...
Click to collapse
Yes that's normal. And gosh, is reading that hard? "If you plan on dual-booting with android you will need to download a full system like prime and put the images (system.img boot.img recovery.img) in images/"

Gibeon said:
Yes that's normal. And gosh, is reading that hard? "If you plan on dual-booting with android you will need to download a full system like prime and put the images (system.img boot.img recovery.img) in images/"
Click to expand...
Click to collapse
i thought you couldnt load recovery with the ubuntu dual boot, can you now? thats pretty much all ive been waiting for to dual load ubuntu. i want to use revolver 3.2 and clemy's kernel with theme x, but without recovery, or at least the revolver 3.2 nvflash files, it wasnt worth it for me to switch over.

You still cant dual boot in the manner in which you are thinking

thebadfrog said:
You still cant dual boot in the manner in which you are thinking
Click to expand...
Click to collapse
word, thats what i thought, thanks. guess il have to hunt down the revolver nvflash files or bite the bullet and use prime (not that prime is a bad rom at all, im just used to revolver). im sick of decompiline and editing xml's in windows, i get errors all the time., and id rather not use my laptop at all, it shuts off randomly all the time. dual booting ubuntu onto my tf would eliminate my need to use my laptop or windows all together.

well when i tried to start it it said failed didnt find bootloader

I used cuckoopt's windows kit's dual boot option, and it seems to have worked, but it then just booted into android.
How to get ubuntu to boot?

Flash the Linux.zip
Sent from my SGH-T959 using XDA App

Is there anywhere a detailed guide on how to install Ubuntu beside Android I haven't found yet?
What I did:
- I downloaded Ubuntu (950MB) and the linux-flashkit.tar.gz on my PC (my PC is already running Ubuntu)
- Data-backup
- ?
How to move on? Boot Transformer into APX-mode and execute the flash-linux-android.sh?
Thx for the APX-tip in the other thread!
---------- Post added at 08:40 PM ---------- Previous post was at 08:11 PM ----------
So, I executed the *.sh-file, but after some seconds, in termial there is this:
Code:
file not found: ./images/system.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Where do I get this file from?
---------- Post added at 09:33 PM ---------- Previous post was at 08:40 PM ----------
Ok, I've found the system.img, but where do I get the boot.img? In the first post of the Ubuntu-thread I only find 'abootimg'. Is this the right file?

Lunchbox115 said:
Ok, I've found the system.img, but where do I get the boot.img? In the first post of the Ubuntu-thread I only find 'abootimg'. Is this the right file?
Click to expand...
Click to collapse
The system.img, boot.img, and recovery.img are all from the Android ROM you want to dual-boot Ubuntu with, so either you download them (some ROMs aren't released in nvflash img format, so you'd need to install it and back it up with nvflash first) or you use the images you generated from running your backup.
Source:
Before using this pack back up any data that you may have on your
device, this method is destructive to data, and will wipe
everything. If you plan on dual-booting with android you will need
to download a full system like prime and put the images (system.img
boot.img recovery.img) in images/
Click to expand...
Click to collapse

Sh*t, I read the first post three times and I didn't see that. Time for me to go to bed!
Thank you very much! Now it MUST work.
Another question: is there any chance to hard-brick the TF so that it can't be 'rescued'? Once I read that it's nearly unbrickable cause of NVFLASH. Is that true?

If you have an nvflash-able TF (which you do, or else you wouldn't have been able to perform the backup), you can't brick it. Even if you wipe the entire internal flash, you can still boot into APX mode, which has complete write access to the internal flash.

That's good to hear! I just asked cause the Galaxy S is brickable if you flash a wrong kernel or something like that. So it's nice to have a unbrickable tab.

It comes down to what hardware the phone has and what the community has figured out how to access. Most phones and devices have a hardware-based development interface (like APX mode for the Transformer or whatever RSDLite uses on older Motorola phones). These interfaces are generally burned onto read-only ROMs for the sole purpose of making the device un-brickable.
If the device doesn't have one of these interfaces, or the community hasn't figured out how to access it, you run the risk of bricking.
---------- Post added at 04:46 PM ---------- Previous post was at 04:11 PM ----------
I just made a thread explaining the Transformer boot process:
http://forum.xda-developers.com/showthread.php?p=17888843
I'll expend further on it, but this should help everyone understand where custom ROMs and Ubuntu fit into it.

Thanks a lot! I finally got the dualboot working. Android boots without any problems, in Ubuntu I have to configure the keyboard layout and nothing goes on, so I have to wait...
Thank you for helping me!

Lunchbox115 said:
Thanks a lot! I finally got the dualboot working. Android boots without any problems, in Ubuntu I have to configure the keyboard layout and nothing goes on, so I have to wait...
Thank you for helping me!
Click to expand...
Click to collapse
Excellent news! What do you mean about the keyboard? Do you mean that you type and nothing appears on the screen?

recovering partitioned internal memory

I recently used Frank's Tools to dual boot Ubuntu on my Tablet.
After I later realized it wasn't for me, I used the generic root kit to revert to android only OS.
I now see that my internal memory is only showing as 7.36 gb
I would like to know how I can go about recovering the partitioned memory
I have tried using frank's tools, and choosing android only but it gave me the error
"Nvflash started
nvflash configuration file error: file not found"
Some help would be much appreciated.

There should be a flash.cfg file in there- monkey around with the partition sizes and see if that fixes the issue.
I'm not familiar with Frank's tools, so can't help you there. My wild guess is that the rom files aren't unzipped and in the same folder as the nvflash executables.
You might try to download and flash the nvflash version of Prime or another custom rom since it will have the stock partition sizes.

Hi there go to little stevies thread download olife.sh and set up the enviroment put the rom you want in images boot.img system.img recovery.img
Run olife.sh and go to the option flash then select stock it will resize all the partitions and flash the rom you put in images i usually use the script just for flashing new roms makes sure i get a super clean install
Sent from my tf running krakd warped an twisted 1544mhz Blades kernel

Danzano said:
Hi there go to little stevies thread download olife.sh and set up the enviroment put the rom you want in images boot.img system.img recovery.img
Run olife.sh and go to the option flash then select stock it will resize all the partitions and flash the rom you put in images i usually use the script just for flashing new roms makes sure i get a super clean install
Sent from my tf running krakd warped an twisted 1544mhz Blades kernel
Click to expand...
Click to collapse
I am very new to Linux and don't know much at all about their OS or ubuntu.
I know i can install it and dual boot my PC with ubuntu, or simply just run a VM of ubunt on my PC.
All i know to do in Ubuntu us open up the terminal by hitting Ctrl+alt+f i beleive
Can anyone show me a step by step way of doing so?
Stevies thread asumes you have knowlege of ubuntu, but I just don't.
Even better has anyone been able to acomplish this with windows?

SomethinAmazinn said:
I am very new to Linux and don't know much at all about their OS or ubuntu.
I know i can install it and dual boot my PC with ubuntu, or simply just run a VM of ubunt on my PC.
All i know to do in Ubuntu us open up the terminal by hitting Ctrl+alt+f i beleive
Can anyone show me a step by step way of doing so?
Stevies thread asumes you have knowlege of ubuntu, but I just don't.
Even better has anyone been able to acomplish this with windows?
Click to expand...
Click to collapse
You can have ubuntu run next to windows just download the wubi version from the website it lets you have dualboot and if you get sick of ubuntu you can just uninstall it like any other win program.
As for the steps to setting up there are 1000 youtube vids on how to set up adb etc on ubuntu and there very easy to follow
Once you have watched a few of those videos you will have a folder in your home folder called platform-tools thats where all the good stuff goes for android and thats where lil stevies thread pics up from..
I was completly new to linux and android when i got my gt540 but after 2-3days i was happy flashing and modding and now with my tf doing even more with the system.
If you have a little patience and dont mind watching a few youtube vids you can get the whole lot set up and done and ready for future use in an hr or so
Understanding it or what your doing is the part that will take 2-3 days lol
Sent from my tf running krakd warped an twisted 1544mhz Blades kernel

Thanks so much Danzano.
You really helped me out alot. I installed Ubuntu like you suggested, and was able to safely remove the ubuntu partition from my tf's internal memory.

SomethinAmazinn said:
Thanks so much Danzano.
You really helped me out alot. I installed Ubuntu like you suggested, and was able to safely remove the ubuntu partition from my tf's internal memory.
Click to expand...
Click to collapse
All good mate it comes in handy alot for work on the tf and other bits and pieces
Sent from my tf running krakd warped an twisted 1544mhz Blades kernel

Root Now Available For ASUS MemoPad FHD 10 Model ME302C

Update 1-21-14: Root for 5-0-11 available - go to pg 17 for details, pg 20 for new and improved method. Having said this, there are no real benefits to Android 4.3 over 4.2, so I recommend staying with 4-7-3.
Yes, folks after two days of trial and error I finally was able to build a system image file (from the US OTA update files) that you install via fastboot.
Install Instructions:
First, BACKUP! Use ASUS App Backup for installed Apps (and their data) and I also use My Backup to backup personal and system settings info. Once rooted, use My Backup Root (or keep using ASUS App Backup for Apps and My Backup (non-root) for everything else. Always Backup to your External SDcard as a Factory Reset (should you need to do one) or if you have to or accidently run 'fastboot erase userdata' will erase your internal SDcard.
Second, Charge your Battery - make sure you do any flashing with a good charge, battery going low during this process can do 'bad things'...
Linux Users Note: I'm using Ubuntu and fastboot will not recognize the MemoPad. Still trying to resolve this, the latest Windoze version of fastboot works.
Download ME302C-US-Root.img.gz from MediaFire (see below)
Install the Minimal ADB-Fastboot into a folder (google this you're on your own)
Install the ASUS USB Drivers (google this you're on your own)
Place the image file in the adb/fastboot folder (do not decompress, install as is)
Run these fastboot commands:
fastboot devices (make sure your MemoPad is connected)
fastboot erase cache
fastboot erase system
fastboot flash system ME302C-US-Root.img.gz
Reboot from MemoPad recovery menu
Install from Market:
SuperSU v1.86 Chainfire (required for all other apps to work)
Root Checker (run it to confirm you have root)
You are now rooted
Note: this install follows the ASUS update script that links various binaries in /system/bin to 'toolbox' so you may want to enhance that by installing BusyBox from the Market and use Safe Install method to add new links to the ones already set for toolbox (explained in busybox).
Enjoy your Rooted MemoPad!
Download the image file from here:
http://support.mediafire.com/download/avhe9zizn7z0t5w/ME302C-US-Root.img.gz
If the flash fails or doesn't root, you can just go back to the original OTA update by downloading it from ASUS and running:
fastboot erase cache
fastboot erase system
fastboot flash update US_ME302C-V4.7.3-0-ota-user.zip
Don't post questions about installing/using fastboot or USB drivers, it's been covered ad-nauseum here and other places - google is your friend. If you have the LTE model (ME302KL), that has a locked bootloader and requires the unlock utility available on the ASUS website before you run fastboot.
Thanks goes out to djsven for getting this idea started, then getting it done himself in Germany using the German distro from ASUS. I ended up having to extract the su binary he had as the three I tried from different downloads didn't work. Not sure where he got it but it's a winner!

gbkelley said:
Yes, folks after two days of trial and error I finally was able to build a system image file from the US OTA update that you install via fastboot. All I need to do now is find a free file upload site to host the file for you to download.
Install Instructions:
Download ME302C-US-Root.img.gz from (wherever)
Install the Minimal ADB-Fastboot into a folder (google this)
Install the ASUS USB Drivers (google this)
Place the image file in the folder
Run these fastboot commands:
fastboot devices (make sure your MemoPad is connected)
fastboot erase cache
fastboot erase system
fastboot flash system ME302C-US-Root.img.gz
Reboot from MemoPad recovery menu
Install from Market:
Root Checker (run it to confirm you have root)
SuperSU
Some app requiring root and run it - you should get a notification from SuperSU to grant su for app
You are now rooted
Note: this install follows the ASUS update script that links various binaries in /system/bin to 'toolbox' so you may want to replace that by installing BusyBox from the Market.
Enjoy your Rooted MemoPad!
I'll update this post when I have a download url for you.
Click to expand...
Click to collapse
Where can I find ME302C-US-Root.img.gz ???? Searches are finding nothing.

Turbojugend said:
Where can I find ME302C-US-Root.img.gz ???? Searches are finding nothing.
Click to expand...
Click to collapse
+1

Why not use Mega? Seems to always work and have great speed.

It is rooted...thank you.
Sent from my ME302C using Tapatalk 4

Turbojugend said:
Why not use Mega? Seems to always work and have great speed.
Click to expand...
Click to collapse
I tried RapidShare and it was crap. MediaFire was next on my list and that worked so I used it. May try Mega if there are problems with folks getting the file from MediaFire, we'll see...

Worked for me. Updated to 4.7.3 and is rooted.
Tried in Linux and could not get fastboot to recognize device.
Tried in Windows Server 2012 with this driver:
http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices
Ran setup file as Administrator with compatibility mode set to XP SP3. Required a restart before "fastboot devices" worked. If anyone can post a way to make fastboot work in Linux for this tablet, it would be appreciated.
-notten

notten said:
Worked for me. Updated to 4.7.3 and is rooted.
Tried in Linux and could not get fastboot to recognize device.
Tried in Windows Server 2012 with this driver:
http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices
Ran setup file as Administrator with compatibility mode set to XP SP3. Required a restart before "fastboot devices" worked. If anyone can post a way to make fastboot work in Linux for this tablet, it would be appreciated.
-notten
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=537508
or this...
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk

gbkelley said:
Try this:
http://forum.xda-developers.com/showthread.php?t=537508
or this...
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Click to expand...
Click to collapse
Hey, thanks, but neither of those has anything I haven't tried. I'm using the latest SDK and running fastboot as root so it's not the perms. I read on some Intel forum that someone else is having trouble getting it to work in Linux also.
Any luck with iptables? I don't think the kernel for this tablet comes with iptables enabled. I tried a few methods of getting it installed (DroidWall, iptables (beta) from marketplace). If I screw up the kernel on this, will flashing over it with the system image you upped revert it?
-notten

Thanks a lot for all of this gbkelley. Cheers!!

notten said:
. If I screw up the kernel on this, will flashing over it with the system image you upped revert it?
-notten
Click to expand...
Click to collapse
No my image is the /system folder only. Kernel is in boot.ini. The OTA update zip should fix it though as it has boot.ini

Xposed framework works great. Gravity box and app settings work great. Thanks for root.
Sent from my ME302C using Tapatalk 4

Links if you don't want to google it
Minimal ADB and Fastboot
How to install USB drivers

tdamocles said:
Xposed framework works great. Gravity box and app settings work great. Thanks for root.
Sent from my ME302C using Tapatalk 4
Click to expand...
Click to collapse
Hide battery work for you?

Got Root, Thanks so much.

gbkelley, this tablet has been out for a pretty long time, what do you think is the reason for the lack of ROM's and dev for it?

Turbojugend said:
gbkelley, this tablet has been out for a pretty long time, what do you think is the reason for the lack of ROM's and dev for it?
Click to expand...
Click to collapse
I would think that until a few days ago we didn't have a recovery image to which we could revert. I don't know precisely what's required to build a custom kernel for this tablet, but I'm guessing it's slightly more difficult since we don't know the exact kernel config. I don't think there are any source distributions of this kernel, and I somehow doubt we're lucky enough to have had ASUS build the kernel with CONFIG_IKCONFIG. Then there's probably custom patching that they've done to the code that they probably just won't release. But assuming we had a kernel config we can start building some nice ROMs or even updating the OS to kitkat, etc. As far as default apps/themes/whatever, I guess you could extract the recovery image, repackage it with your favorite APKs, themes, etc., and now you have a new ROM. I'll participate in ROM building for this tablet once we get a kernel config.
-notten
EDIT: Looks like kernel config was found a week ago by ze Germans: http://www.draisberghof.de/usb_mode...sid=c87b172460e22c6f0021f69c3bd5a601&start=15
Looks like it's time to start building custom ROMs for this tablet. I'll have to look into it sometime this week.

notten said:
I would think that until a few days ago we didn't have a recovery image to which we could revert. I don't know precisely what's required to build a custom kernel for this tablet, but I'm guessing it's slightly more difficult since we don't know the exact kernel config. I don't think there are any source distributions of this kernel, and I somehow doubt we're lucky enough to have had ASUS build the kernel with CONFIG_IKCONFIG. Then there's probably custom patching that they've done to the code that they probably just won't release. But assuming we had a kernel config we can start building some nice ROMs or even updating the OS to kitkat, etc. As far as default apps/themes/whatever, I guess you could extract the recovery image, repackage it with your favorite APKs, themes, etc., and now you have a new ROM. I'll participate in ROM building for this tablet once we get a kernel config.
-notten
EDIT: Looks like kernel config was found a week ago by ze Germans: http://www.draisberghof.de/usb_mode...sid=c87b172460e22c6f0021f69c3bd5a601&start=15
Looks like it's time to start building custom ROMs for this tablet. I'll have to look into it sometime this week.
Click to expand...
Click to collapse
Maybe I am getting my versions mixed up. Is this version of the tablet brand new, not the same that has been out for months? Mine is the ME302C version

Turbojugend said:
Maybe I am getting my versions mixed up. Is this version of the tablet brand new, not the same that has been out for months? Mine is the ME302C version
Click to expand...
Click to collapse
I believe you're right in saying that this tablet has been out for some time. I suppose there has been enough interest that things are now starting to take off. I mean, I bought it a couple weeks ago and I assumed I'd have to use the WW SKU root and try go beg ASUS for kernel configs. Seems like most of that has been taken care of in the last week. I'm actually really glad. It's a good time to be an ASUS MeMO Pad 10 FHD owner.

notten said:
I believe you're right in saying that this tablet has been out for some time. I suppose there has been enough interest that things are now starting to take off. I mean, I bought it a couple weeks ago and I assumed I'd have to use the WW SKU root and try go beg ASUS for kernel configs. Seems like most of that has been taken care of in the last week. I'm actually really glad. It's a good time to be an ASUS MeMO Pad 10 FHD owner.
Click to expand...
Click to collapse
Ok cool, I just don't want to be stuck with something that will have nothing going for it. I really like the tablet, but if it was going to be dead on XDA I would exchange it for the Sony Xperia Z Tablet. Both fit my needs for what I use it for.

New Builder Question

This should probably go in some general Q&A forum, but this is by far the most helpful community I've come across so I wanted to try here first. I've finally got my Ubuntu box up and running again (upgrading to 14.04 wasn't pretty) and was able to build for both my 700t and my n5 without error, but I'm afraid to pull the trigger and flash it. I'm building straight CM for the tablet and AOSP for the phone, so what is the worst that could happen? I haven't gotten either of them to run in the emulator, but I'm not completely sure that is even possible. Any insight you may have would be most appreciated.
Thanks in advance!
Just thought of this, since I'm running Crombi ROM2SD, could I just install my zip on external, and then refresh the right kernel?
Sent from my ASUS Transformer Pad TF700T using Tapatalk

psudeke said:
but I'm afraid to pull the trigger and flash it. I'm building straight CM for the tablet and AOSP for the phone, so what is the worst that could happen?
Click to expand...
Click to collapse
The worst thing that can happen is that you brick your device, but you must do something sufficiently stupid for that to happen. I can't say anything about your phone, but for the TF700T, as long as you have a working recovery, flashing a ROM won't brick it. You may want to create the nvflash blobs if you want to have another safety net - it is possible to brick the TF700T if you force it to boot to the recovery and the recovery is broken.
psudeke said:
I haven't gotten either of them to run in the emulator, but I'm not completely sure that is even possible.
Click to expand...
Click to collapse
That's normal - ARM devices are just too different, and the emulator is just another different device.
psudeke said:
Just thought of this, since I'm running Crombi ROM2SD, could I just install my zip on external, and then refresh the right kernel?
Click to expand...
Click to collapse
See my Android dual-booting thread in the dev subforum. I originally developed ROM2SD to be able to test my self-built ROMs without breaking my working installation.

_that said:
The worst thing that can happen is that you brick your device, but you must do something sufficiently stupid for that to happen. I can't say anything about your phone, but for the TF700T, as long as you have a working recovery, flashing a ROM won't brick it. You may want to create the nvflash blobs if you want to have another safety net - it is possible to brick the TF700T if you force it to boot to the recovery and the recovery is broken.
That's normal - ARM devices are just too different, and the emulator is just another different device.
See my Android dual-booting thread in the dev subforum. I originally developed ROM2SD to be able to test my self-built ROMs without breaking my working installation.
Click to expand...
Click to collapse
Thanks _That, I appreciate your help! After reading your post and the f2fs post, i thought i was in the clear, but i still managed to screw something up. i'm unable to get the tablet to boot off of external, regardless of whether its my ROM or CROMBi. I see a "segmentation error" listed in the output from the the preinit, and then it always boots to internal. I thought maybe i got the mount points reversed in recovered, so i reflashed recovery, but no luck. i also tried deleting the preinit script and then reinstalling CROMBi, but i still get the same error. any thoughts?

psudeke said:
I see a "segmentation error" listed in the output from the the preinit
Click to expand...
Click to collapse
For some unknown reason, dynamically linked executables don't work for preinit in KitKat. So if your *internal* ROM is not stock 4.2-based (I have no data about 4.3), the only way to run a preinit script is to use a statically linked busybox.

You still get that fault with a static busybox but it seems to copy files fine.
@psudeke you can compile the static busybox yourself simply with make static-busybox in your build folder - or just steal mine from /system/boot

sbdags said:
You still get that fault with a static busybox but it seems to copy files fine.
Click to expand...
Click to collapse
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).

_that said:
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
Click to expand...
Click to collapse
it comes from the ls -l /init* which indeed doesn't have the busybox prefix but if I do it gives some other error I forget now
Anyway it doesn't harm the boot process - just an error message

_that said:
For some unknown reason, dynamically linked executables don't work for preinit in KitKat. So if your *internal* ROM is not stock 4.2-based (I have no data about 4.3), the only way to run a preinit script is to use a statically linked busybox.
Click to expand...
Click to collapse
_that said:
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
Click to expand...
Click to collapse
Internal is the 5/17 build of Crombi, and its a brand new install. with a full format of the data partition (which in my haste to get this working yesterday, i wiped out my nandroid from right before i tried this).
is there any connection between when the internal is flashed compared to the external? in other words, if i reflash the internal rom, it should still recognize an existing external rom? hope that makes sense, i'm still shaking off the effects of a little too much whiskey last night.:laugh:

psudeke said:
Internal is the 5/17 build of Crombi, and its a brand new install. with a full format of the data partition (which in my haste to get this working yesterday, i wiped out my nandroid from right before i tried this).
is there any connection between when the internal is flashed compared to the external? in other words, if i reflash the internal rom, it should still recognize an existing external rom? hope that makes sense, i'm still shaking off the effects of a little too much whiskey last night.:laugh:
Click to expand...
Click to collapse
No currently if you reflash internal it will only see internal. You need to reflash external for that to work.

sbdags said:
No currently if you reflash internal it will only see internal. You need to reflash external for that to work.
Click to expand...
Click to collapse
Ahh, thanks sbdags! that fixed the issue with ROM2SD. i got that impression when i pulled the preinit and saw it only had an entry for internal. but, i'm still very much in a learning phase so i didn't want to jump to a conclusion.
and after getting crombi to boot on external, i swapped sd cards and my build of CM11 actually booted! now the real learning process begins as i figure out how to customize it.
Thanks again to both you and @_that, you guys are the best:good:

@sbdags and @_that
Just wanted to thank you both again for your help. After much trial and error, i was able to build the 5/27 version of CM and merge in that's 9 f2fs kernel, its running well so far. not a bad quadrant score for someone who doesn't know what they're doing!
https://www.dropbox.com/s/khq17h04b715eyd/C11%20Benchmark%20ART.png
Hats off to both of you! :good:
--- Guess I can't insert an image directly from my DropBox, link is to a screenshot of my score ---

psudeke said:
After much trial and error, i was able to build the 5/27 version of CM and merge in that's 9 f2fs kernel, its running well so far. not a bad quadrant score for someone who doesn't know what they're doing!
Click to expand...
Click to collapse
Congratulations! If you can build a working ROM from source, you're already in the top 1% of people here who know what they're doing.

_that said:
Congratulations! If you can build a working ROM from source, you're already in the top 1% of people here who know what they're doing.
Click to expand...
Click to collapse
Good to finally be a "One Percenter" in something! :laugh:
Thanks again for your help, I'm sure that was the first of many questions I can't figure out.

psudeke said:
Good to finally be a "One Percenter" in something! :laugh:
Thanks again for your help, I'm sure that was the first of many questions I can't figure out.
Click to expand...
Click to collapse
Just ask away and congrats! :good:

sbdags said:
Just ask away and congrats! :good:
Click to expand...
Click to collapse
Be careful what you wish for, I've got a laundry list of questions ranging from basic Linux commands to the nature of the multiverse, lol.
I do have one question out of the gate about the update-binary file. I'm trying to add a couple apps to either the system or data folders, but I'm not sure what commands are available from the stock CM file. I think for the most part by looking at your updater-script file I can figure out the commands to do what I want, but given the little I know about this and the size difference of the binary file between CM and the one i was looking at of yours, I'm curious. Is the best way to see what's available CM's git? I basically just want to install a different Launcher and Viper instead of DSP manager for sound. Do I need to study up on edify to look at the binary or is there an easier way?
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk

psudeke said:
Be careful what you wish for, I've got a laundry list of questions ranging from basic Linux commands to the nature of the multiverse, lol.
I do have one question out of the gate about the update-binary file. I'm trying to add a couple apps to either the system or data folders, but I'm not sure what commands are available from the stock CM file. I think for the most part by looking at your updater-script file I can figure out the commands to do what I want, but given the little I know about this and the size difference of the binary file between CM and the one i was looking at of yours, I'm curious. Is the best way to see what's available CM's git? I basically just want to install a different Launcher and Viper instead of DSP manager for sound. Do I need to study up on edify to look at the binary or is there an easier way?
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
yes the easiest way to do it is just make 2 folders with your extra apps in it say /extras/app
then add the following to the updater-script (you don't need to touch the update-binary unless you start using aroma)
package_extract_dir("extras", "/system");
delete("/system/app/DSPManager.apk");
delete("/system/priv-app/Trebuchet.apk");
What that does is copies the extras/app folder into system and deletes your unwanted apps
note apps can be installed into 2 folders /system/app or /system/priv-app
similarly you can install your user apps into /data/app but this is dangerous with launchers as if the user manually uninstalls it you can't do anything on the tab

sbdags said:
yes the easiest way to do it is just make 2 folders with your extra apps in it say /extras/app
then add the following to the updater-script (you don't need to touch the update-binary unless you start using aroma)
package_extract_dir("extras", "/system");
delete("/system/app/DSPManager.apk");
delete("/system/priv-app/Trebuchet.apk");
What that does is copies the extras/app folder into system and deletes you unwanted apps
note apps can be installed into 2 folders /system/app or /systempriv-app
similar you can install your user apps into /data/app but this is dangerous with launchers as if the user manually uninstalls it you can't do anything on the tab
Click to expand...
Click to collapse
Thanks again! i can see how this becomes addicting fast :fingers-crossed:

@sbdags do I need to mount data before installing anything to the /data/app folder? I saw in your updater-script this line, and i'm assuming i need the same:
Code:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p8", "/data");
one other quick question (hopefully), I saw in the XDA WIKI that i can possibly test the script using the update-binary, do i have to do this on the tablet itself? i spent all afternoon trying to fix a problem that amounted to an errant quotation mark in my script (and i knew it was something like that too. too many years of non-terminated string errors to not look there first:laugh, but the only way i could find to test it was to rezip the file and flash. any suggestions?
thank you good sir! :highfive:

psudeke said:
@sbdags do I need to mount data before installing anything to the /data/app folder? I saw in your updater-script this line, and i'm assuming i need the same:
Code:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p8", "/data");
one other quick question (hopefully), I saw in the XDA WIKI that i can possibly test the script using the update-binary, do i have to do this on the tablet itself? i spent all afternoon trying to fix a problem that amounted to an errant quotation mark in my script (and i knew it was something like that too. too many years of non-terminated string errors to not look there first:laugh, but the only way i could find to test it was to rezip the file and flash. any suggestions?
thank you good sir! :highfive:
Click to expand...
Click to collapse
just zip the /meta-inf folder, and flash that to test. obviously comment out any format commands as they will fail. That is what I do.

Hey @psudeke you ever need any help with anything to do with source or git let me know
I am also willing to help out
and just a FYI be careful of @sbdags :cyclops: LOL
Just kidding....
Let me know thx Josh