Develop Bugs

SVN problems

I've tried using SVN multiple times, each time with the same result (failure). Can anybody tell me what I'm doing wrong?
I'm trying to download the Bliss rom. Each time, I use my Mac client and click "export" to a folder on my desktop. Next, I zip the folder up into a file called "bliss.zip" and push it with ADB to the phone. When I try to flash with CWM, I get Installation Aborted shortly after starting the install.

I use a Mac as well. Do this, download the application called SmartSVN (just Google it), set up the repo using that. Download it (the SVN files from http://code.google.com/p/bliss-sense) to a folder in your Macintosh HD (I named mine bliss-sense), then download and install dsixda's kitchen. Just follow his instructions in his thread (here: http://forum.xda-developers.com/showthread.php?t=633246). Drag the fully downloaded boot.img, data, META-INF, and system folders into a folder that you create inside the Disk.img you made for the kitchen, naming the folder WORKING_BlissSense. Open up terminal, cd into the mounted Disk.img you made with your kitchen in, run "./menu" without quotes to load the Kitchen's menu. Select option 99 "Build ROM from Working Folder" and do interactive mode (option 1). Do Y for zipalign, Y for signing the ROM, and rename if you want. Then mount your phone to the computer and drag the new ROM zip from the OUTPUT_ZIP folder in the kitchen where your ROM is after building to your SD Card. Flash in CWM and reboot. There you go. Hope it works.

Oh, you have to use the kitchen?
...
derp

Yes you have to use the Android Kitchen.
Sent from my ADR6300 using XDA App

[REF] A quick rundown of android for noobs

Hello everyone. I see a lot of very basic android questions floating around the forums, so I figured I'd give a VERY basic rundown of the android filesystem for those who don't know. (If you're even slighty experienced, this'll seem like a "duh" thread, you should skip this. This is for new people.)
Ok, to understand android, first thing you need to understand are the basic partition structures. There are 5 android partitions.
boot
cache
recovery
system
data
Before I get into the partitions, you'll have to understand what a mount point is. When you "mount" a drive, you are making it available to the system. On linux (and by extension, android), you need to have a mount point. This is a directory somewhere that serves as a path for the mounted filesystem. So for example, let's say I wanted to mount mmcblk0p1 to a temp directory to edit it. For this example I'll create a directory /data/temp. Now you'd mount mmcblk0p1 /data/temp. When you read the contents of the directory temp under the directory data, you'll see all the info stored on mmcblk0p1. Even something as simple as a flash drive needs to be mounted under linux. If you're an ubuntu user, usually it automounts to /mnt/name of device.
Now, when you boot android, the first thing it does is boot up the linux kernel (when you see the tmobile splashscreen, that's when the kernel is loading.) Next, it loads up the ramdisk. Both of these files are on the boot partition. (When you open up a cwm zip file, you'll see boot.img in there, that's where these reside.) There are two files on the boot partition. zImage (the linux kernel), and initrd.gz (the cpio archive containing the ramdisk.)
What is the ramdisk you ask? Well, very simply, it's the place where the root file system is loaded, and where the init.rc resides. The init.rc is the android startup script (again, basic analogy). If you'd really like to learn about android and how it works, this is the first file I'd start reading.
On to the partitions:
boot - Described above, containing the zimage and initrd.gz
recovery - this is where either the stock recovery or clockwork recovery is located. This is only accessed when entering recovery mode.
cache - You guessed it, this is where some parts of android cache it's file. (Not to be confused with the dalvlik cache, that's located on the data partition.)
system - this is where the system is located. (Esentially the rom you're flashing.)
data - this is the partition where all your installed apps go, as well as the location of a couple parts of the system, like the dalvik-cache and the batterystats.bin file. (Quite a few more, just givinig examples.)
So what does all this mean to you? Well, I see a LOT of people asking about wipes before installs, or asking about flashing kernels, this is why I took the time to explain this.
When you enter cwm, and do a backup, it creates 5 .img files on your sdcard. (One for each of the partitions mentioned above.) When you flash a kernel, it only replaces the boot.img, and a couple files in the system folder. Usually these are kernel modules like the wifi module, and any other modules that aren't compiled into the system. (Although most kernel builders build cifs.ko and all that right into the kernel so the modules aren't needed.)
When you flash a rom, it will always replace the /system and /boot partitions. The rest, that depends on the rom. If you'd like to know what your rom is doing, open up the cwm zip file, and go to meta-inf/com/google/android and you'll see 2 files. Updater-script and update-binary. Updater-script will tell you what it does on install. (You'll see it mounting the partitions it needs, what it does and doesn't format, and also it does a whole bunch of simlinks.) Simlinks, or symbolic links, are either files or directories that point to somewhere else. For example, let's say you are a user who uses ext-sd. What you do is create a simlink for /data that points to the ext3 partition on your sdcard. This way, anytime the system goes to /data it writes somewhere else. Most of the simlinks created in android are more for busybox commands, but that's for another post
If you'd like to see what your mount points are, from an android terminal emulator (or of course adb, but if you are experienced with adb chances are you don't need any of this info in the first place ), type mount. (You might need to type su first, hit enter, then mount). This will list all your mount info. If you'd like to know the actual device name of the mount point, you'd look here. On ours, for example, it's:
mmcblk0p24 is /system
mmcblk0p26 is /cache
mmcblk0p25 is /data
and so on.
Ok, finally, a couple other questions I see often:
Why does my system "hotboot"?
When a system hotboots, it means that zygote has crashed. This is the virtual machine that android runs in. So if you are using your phone, and you all of a sudden go back to the boot animation (NOT the splashscreen with the kernel logo), you just hot-booted. When an application allows you to hotboot all it does is the following command from inside linux: pkill zygote (or pkill -9 zygote).
How do I calibrate my battery?
The batter calibration is a file called batterystats.bin. This is located in /data/system. When you get to 100% charge, if you delete this file, it'll start over on the battery calibration. (There are also market apps to do this for you for the squeamish.)
Other notable files:
gps.conf
Located in the /system/etc folder. This has all the gps configuration, nameservers, and things like this.
build.prop
Located in /system
A lot of device info is stored in here. For more info, google it.
Hopefully this wasn't too mashed together and confusing. I tried to follow a logical order, but I've had way too much turkey and beer today, so I'll post this and let it fly.
Have a happy thanksgiving everyone!

Good stuff, thanks OP.
Powered by the SGSII....

Very very useful for someone like me who knows a bit here a bit there but not sure of the whole picture.
Thanks!!

this should be useful for alot of noobs!

Thanks so much for this, being new to android this is incredibly useful. Bookmarking!
Sent from my SGH-T989 using xda premium

This thread should help alot of new people that just joined this forum and that are new .

Very informative, thank you.

[Q] Tethering Hack attempt failed

I recently tried a tethering hack I found on here after installing the Android 4.3 OTA update. The thread can be found here: http://forum.xda-developers.com/showthread.php?t=1732262&page=11. The specific hack I used was from user BlvJohn. He created a flashable zip file and I flashed it and afterwards my phone failed to boot. My phone is rooted and running TWRP recovery (latest version).
Steps I completed:
1. downloaded zip file to flash to desktop computer
2. made a copy of the file and renamed it to org_no_tether.zip
3. opened org_no_tether.zip so I could delete the new framework-res.apk file
4. copied my phone's current framework-res.apk file to the org_no_tether directory I created when unzipping file using droid explorer to access file
5. rezipped org_no_tether directory to org_no_tether.zip
6. placed both files on my external sd card
7. flashed
When I rebooted it just hung during the AT&T boot animation sequence. I tried wiping the cache, user data, dalvik cache, etc...to try and get it to boot to no avail. I ended up just having to reinstall the ROM using a zip file I found on these forums and everything runs great now. The file I used to reinstall the ROM via recovery was loserskaters found here http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18http://. Everything works great now but I'd still like to get the tethering hack.
In the instructions it said to copy the file to the external sd card so that's what I did, but what I'm wondering is if I was supposed to copy it to my sdcard instead where I place all other files to be flashed? I just wanted to be sure I didn't do something else wrong before I go through this process again and end up having the same result.
Thanks a lot for any help!

SD-Card: write access is not enabled

Hi guys,
yesterday I flashed my Sony xperia m (C1905) single sim with this custom rom: https://forum.xda-developers.com/xperia-m/orig-development/rom-aosp-nougat-7-0-t3448481
And also I flash the gapps here: http://opengapps.org/ Arm, 7.1, micro
First, I unlocked my bootloader - all fine
Second, I install twrp recovery as boot.img
Then I go into recovery mode ->install custom rom (zip file) from sd-card and the gapps (+ wipe cache etc.) - all fine
After this, I setup the Android 7.1 correctly, and all apps work very nice...
But then, I download the fx file explorer, see here: https://play.google.com/store/apps/details?id=nextapp.fx
I installed it and want to create a folder on the sd-card, but then a error appears, which says: "Access was denied: write access is not enabled".
But I already give the app the permission to access the sd-card in the settings.
And if I use a app like Backup & Restore (Backup APKs), and select as backup folder the sd-card, it works fine...
But why?

i solved the problem, you have to go to sd-card (Media card) in fx file explorer ->next click on the three points on the right top, a menu appears, you scroll down and see "Enable write access". Click on this and select in the next step the Media Card/Sd-card.
Now is the sd-card writeable by fx file explorer.

Question TWRP does not show ROM for installation

I wanted to update to the latest version of xiaomi.eu, which is no longer for fastboot, but for recovery. At first internal storage had (0mb), I changed it to EXT4, but still the problem is no visibility/ability to install the latest ROM copied to the phone, what to do?

I download the rom with the phone, reboot with TWRP-3.6.2, install, zip archive anb install, after select system an reboot

I cant do antything in TWRP because TWRP doesnt see ROM copied on storage.. All tutorials say "just go into twrp and install the copied rom", I don't see the copied ROM!

You have to look in a sub folder it will no show at root directory can't remember off hand might be data or meta something like that, after the OTA updater works great
Useing the Skkk latest TWRP by default it was in Chinese

jefffrom said:
You have to look in a sub folder it will no show at root directory can't remember off hand might be data or meta something like that, after the OTA updater works great
Click to expand...
Click to collapse
I dont have acces to /data foler "no such file or directory"

If you don't help yourself, no one here will.
1. TWRP installation
2. wipe+factory
3. boot system
4. copy rom
5. boot twrp
6. install