I am new to this type of thing, I don't have any programming experience. But I want to learn how to "tinker" (don't know how else to put it). I've done a lot of reading and I've downloaded and setup dsixda's kitchen. Now I have to add the device. I'm supposed to get the mount points from the recovery.img but I do not know how to get the image files. Can anyone help me please?
AT&T One X+ stock rooted minus bloatware
andrewjae04 said:
I am new to this type of thing, I don't have any programming experience. But I want to learn how to "tinker" (don't know how else to put it). I've done a lot of reading and I've downloaded and setup dsixda's kitchen. Now I have to add the device. I'm supposed to get the mount points from the recovery.img but I do not know how to get the image files. Can anyone help me please?
AT&T One X+ stock rooted minus bloatware
Click to expand...
Click to collapse
First, I'd suggest learning how to code before you start. I don't think it's really possible to "tinker" around very much without actual knowledge of java and linux.
Cyanogen actually posted a thread on here somewhere giving tips for people who want to develop ROM's. It went along the lines of learn java, write a couple apps, and read ALL the developer documentation for Android before you even begin to "tinker."
Here's the post https://www.xda-developers.com/android/sage-advice-from-cyanogen-still-valid-today/
To actually answer your question, the mount points are located in /proc/emmc. I'm not too sure how you would get the mount points from a recovery image, but I'm no developer either. Here are the mount points so you don't have to go digging yourself
Code:
dev: size erasesize name
mmcblk0p5: 00800000 00001000 "recovery"
mmcblk0p4: 00800000 00001000 "boot"
mmcblk0p16: 60000000 00001000 "system"
mmcblk0p17: 10000000 00001000 "cache"
mmcblk0p20: 00200000 00001000 "misc"
mmcblk0p1: 00600000 00001000 "wlan"
mmcblk0p2: 00200000 00001000 "WDM"
mmcblk0p25: 00200000 00001000 "pdata"
mmcblk0p3: 00600000 00001000 "radiocab"
mmcblk0p18: e00000000 00001000 "userdata"
mmcblk0p24: 01a00000 00001000 "devlog"
mmcblk0p19: 00200000 00001000 "extra"
mmcblk0p14: 03400000 00001000 "mdm9k"
mmcblk0p15: 00800000 00001000 "mdm9k_config"
mmcblk0p21: 00800000 00001000 "modem_st1"
mmcblk0p22: 00800000 00001000 "modem_st2"
Thanks for helping out. Belive me i know i would really screw some stuff up if I tried to develop or go deep into a rom and try to tweak things. I have no desire to do that I'll leave that stuff to ppl who know what they are doing. What I want to do i guess is call themeing? I just want to change up the look in small ways.. I think the most complex thing i would like to do right now is take a clock widget and design a different look in photoshop would be ideal. I am not sure if this is even possible, I know im a noob but gotta start somewhere.. And any help is greatly appreciated
AT&T One X+ stock rooted minus bloatware
andrewjae04 said:
Thanks for helping out. Belive me i know i would really screw some stuff up if I tried to develop or go deep into a rom and try to tweak things. I have no desire to do that I'll leave that stuff to ppl who know what they are doing. What I want to do i guess is call themeing? I just want to change up the look in small ways.. I think the most complex thing i would like to do right now is take a clock widget and design a different look in photoshop would be ideal. I am not sure if this is even possible, I know im a noob but gotta start somewhere.. And any help is greatly appreciated
AT&T One X+ stock rooted minus bloatware
Click to expand...
Click to collapse
I dabbled around in theming before. Theming apk's is pretty easy compared to system themes. You pretty much just replace the images in the apk with new ones. The only hard part is figuring out the 9-patch stuff, a lot of images don't import into photoshop nicely so it makes editing more arduous.
I'd suggest editing something like the aosp deskclock which you can find here. There's tons of tutorials out there on editing apk's.
Awesome. Thank you very much
AT&T One X+ stock rooted minus bloatware
Related
I am trying to build a flashable zip that i compile from the stock system.img and boot.img files from 2.00.405.3 using dsixda's HTC Android Kitchen...
When i go to flash the rom that it creates (even if i dont mod anything else ...) i get a status 0 error..
I edited the update script so that every line could be identified so i could find the last error...
and the last print was "package_extract_dir"...
script follows:
Code:
...
ui_print("format");
format("MTD", "system");
ui_print("mount");
mount("MTD", "system", "/system");
ui_print("package_extract_dir");
package_extract_dir("system", "/system");
ui_print("symlinks");
....
The really interesting thing is that a few lines above this (as can be seen) i format the system partition and upon re-boot the stuff from the old device rom (before my flash attempt) is still on there! ...
What the heck is going on?
Thanks
Kris
Because the flyer/view doesn't use mtd partitions...it uses emmc.
The dsixda kitchen does some conversions on the updater-script that requires some device specific information about mounts. He created a definition folder where you drop device specific definitions for the common mount points.
Go into the kitchen folder > tools/edify_defs
Inside of that folder there are various device definitions. Create one for the flyer. There's also a template in there, but I didn't have much luck editing the template. I just looked at some of the newer defs and plugged in the View mount points.
Here's the one I used for the View, but I'm not sure if the mount points are the same on the Flyer. Also, I'm not sure what the boot mount point for the View is, but writing the boot doesn't seem to require the specific mount.
Code:
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p26
cache_mnt=\/dev\/block\/mmcblk0p31
boot_mnt=???
data_mnt=\/dev\/block\/mmcblk0p30
sdcard_mnt=\/dev\/block\/mmcblk1p1
Ahh that explains it ... i looked through my procs/mounts and found the info
sys_mnt=\/dev\/block\/mmcblk0p25
cache_mnt=\/dev\/block\/mmcblk0p30
boot_mnt=???
data_mnt=\/dev\/block\/mmcblk0p29
Kris
I put in:
Code:
format("ext3", "EMMC", "/dev/block/mcblk0p25");
mount("ext3", "EMMC", "/dev/block/mcblk0p25", "/system");
This causes the status 0 error still when i copy over the files tho with package_extract_dir
Also tried ext4 ... this produces the same issue as above (status 0)
Thanks
Kris
I tried using what was listed about for the View but it doesn't work on the wifi Flyer. How do you find out what they should be? I get a Status 1 error when trying to flash.
Try cat /proc/emmc. Boot is mmcblk0p22 on the view. Thanks to IEF for the pointer
Sent from my SPH-D700 using XDA App
Hi, could anyone please help me by either post or upload their "default.prop" file located under root directory??
Model: i9100
Rom: Lite'ning Rom 5.0 based on XXKG6
Kernel: Ninphetamine-2.0.5
STORY:
I have accidentally deleted "default.prop" file, under root directory. (not /system)
Realising my mistake, I created a new file, named it "default.prop", hoping that the system will fill it in with lines it had.
Now all I have in the file are these;
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
I have never opened the file before to see what was in there. As I had no other Galaxy S2 to compare with, I wasn't sure if these lines were all the file originally contained. I have tried reflashing the entire rom, and also restoring previous NAND backup, but none of those seemed to return the "default.prop" file into its original state.
After frantic searching, I found that the original galaxy s had those lines as well;
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.am=android-samsung
ro.com.google.clientidbase.vs=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=2.1_r2
Source: http://forum.xda-developers.com/showthread.php?t=734151&page=2
Would Galaxy S2's default.prop also have those lines?
The first weird thing I noticed after deleting default.prop was that the market app stopped showing me a lot of apps under "Top Free" or "Top Paid". It is still like that after entering the above lines from original galaxy S..
Could anyone please upload or post what's in their default.prop, so that I can copy it into mine, or use as reference?
Thank you in advance, I'm dying of knowing the fact that my phone might be missing a critical file..
All mine has in it is:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
Sent from my GT-I9100 using XDA Premium App
..then it seems like I have overreacted. The system seemed to have filled in all the lines back to original state, and im going to have to look elsewhere to solve the market problem.
Thank you very very much!! Thats all I needed
Sent from my GT-I9100 using XDA App
does anyone know the physical locations for the the system, boot, kernel, cache, modems etc?
Dev/block/??? system
Im trying to build a deodex tool for the DNA. Thanks
das7982 said:
does anyone know the physical locations for the the system, boot, kernel, cache, modems etc?
Dev/block/??? system
Im trying to build a deodex tool for the DNA. Thanks
Click to expand...
Click to collapse
Ask jcase, or dsb they know everything :beer:
From my DROID DNA
das7982 said:
does anyone know the physical locations for the the system, boot, kernel, cache, modems etc?
Dev/block/??? system
Im trying to build a deodex tool for the DNA. Thanks
Click to expand...
Click to collapse
All the mount points are in the /proc/mounts file. :good:
Sent from my HTC6435LVW using xda app-developers app
I seen this on another thread. These are the mount points for the DNA
mmcblk0p21: "misc"
mmcblk0p20: "recovery"
mmcblk0p19: "boot"
mmcblk0p32: "system"
mmcblk0p28: "local"
mmcblk0p33: "cache"
mmcblk0p34: "userdata"
mmcblk0p24: "devlog"
mmcblk0p26: "pdata"
mmcblk0p29: "extra"
mmcblk0p16: "radio"
mmcblk0p17: "adsp"
mmcblk0p15: "dsps"
mmcblk0p18: "radio_config"
mmcblk0p22: "modem_st1"
mmcblk0p23: "modem_st2"
mmcblk0p30: "cdma_record"
mmcblk0p31: "reserve"
Click to expand...
Click to collapse
das7982 said:
does anyone know the physical locations for the the system, boot, kernel, cache, modems etc?
Dev/block/??? system
Im trying to build a deodex tool for the DNA. Thanks
Click to expand...
Click to collapse
theres really no need, you can manually deodex with api 16 and baksmali/smali 1.4.0 (or higher)
or the latest version of android kitchen *should* work fine
I dont see any threads relating to the removal of the tampered flag of the htc desire 610. Can anyone tell me how to do it. I see methods for the M7 but i dont know if it will work for mine. I am S-off and bootloader unlocked
Maybe this'll work, if you want to try it, do a full nandroid backup. Not responsible for bricking.
Thanks. I'm using TWRP custom Recovery so i definitely have my backup ready. I might as well give it a shot. Everything i've done up to this point has been a gamble so why stop here
Dreamer86 said:
Thanks. I'm using TWRP custom Recovery so i definitely have my backup ready. I might as well give it a shot. Everything i've done up to this point has been a gamble so why stop here
Click to expand...
Click to collapse
A Simple backup dosent contain hboot so if u flah that thing u cant go back
I didnt. Figured it to be incompatible with my type of Htc phone and i don't wanna flash code meant for M7 or M8. I just can't find a way to erase the tampered flag.
Dreamer86 said:
I didnt. Figured it to be incompatible with my type of Htc phone and i don't wanna flash code meant for M7 or M8. I just can't find a way to erase the tampered flag.
Click to expand...
Click to collapse
You need the full Rom of ur device and extract the hboot, Then a guy from m8 section can do this for you. If u have at&t device get the ruu and see if u find that file
Dreamer86 said:
I didnt. Figured it to be incompatible with my type of Htc phone and i don't wanna flash code meant for M7 or M8. I just can't find a way to erase the tampered flag.
Click to expand...
Click to collapse
Have you tried the method I sent you? You aren't flashing anything in that guide, just changing some values.
Haven't tried the method yet. Trying to do more research before anything. I guess the whole reason i wanted the flag removed is for "looks". if it doesnt really have any negative side effects other than just physically showing that my phone has been modified in the boot loader than i guess I'm okay with that. Besides, i have no warranty on this phone. It is AT&T. I feel I need to learn more especially with the method that Porozex has mentioned above. You both have been really helpful and I will repost if and when i achieve this.
Tried the Revone Method....was a epic fail. Kept giving me a failed error -2.
Been trying to figure out the exact method
Yes, I want mine to look exactly like yours. I'm s-off and unlocked but still tampered none the less. how did you get your tampered flag removed? I've read some threads where it says that a tampered flag is displayed upon unlocking the bootloader.
Dreamer86 said:
Yes, I want mine to look exactly like yours. I'm s-off and unlocked but still tampered none the less. how did you get your tampered flag removed? I've read some threads where it says that a tampered flag is displayed upon unlocking the bootloader.
Click to expand...
Click to collapse
I've been tring to back track how i got the tampered off. I reflashed ruu but nothing seems to happen anymore but i do remember following a tutorial by scotty1223, since then dont have the tampered on hboot
Heres the pic of mine as it looks right now.
At the moment it's just hit or miss and I hate to point you in the wrong direction or bricking
You do NOT want to follow the m8,7,9, etc guides the results will be bad. Desire 610 is different. I will need to look at my notes and see what work(if any) Ive done with 610 and we'll go from there.
Again,do NOT follow guides for other devices. There's good reason for the warnings that start off at the first posts.
Sent from my HTC One
i dont appear to have any notes on 610. to start i will need the results of:
cat /proc/emmc
and
cat proc/partitions
here is the requested information and I do appreciate you very much for helping
Dreamer86 said:
View attachment 3397321
View attachment 3397322
View attachment 3397323
View attachment 3397324
here is the requested information and I do appreciate you very much for helping
Click to expand...
Click to collapse
Thanks. Can you copy that and then paste it between a couple sets of code tags? It's a little harder for me to save pictures and reference them later. I prefer to keep this kind of information as plain old text documents. I will take a closer look as soon as I get a minute
Sent from my HTC One
From that, I will need to see dumps of partitions 2, 5, & 6. Upload them somewhere, and PM me a link.
Sent from my HTC One
[email protected]_a3ul:/ $ cat /proc/emmc
dev: size erasesize name
mmcblk0p1: 00100000 00000200 "sbl1"
mmcblk0p2: 02000000 00000200 "pg1fs"
mmcblk0p3: 00004000 00000200 "board_info"
mmcblk0p4: 00ef7c00 00000200 "reserve_1"
mmcblk0p5: 00040000 00000200 "mfg"
mmcblk0p6: 017afc00 00000200 "pg2fs"
mmcblk0p7: 00040000 00000200 "sbl1_update"
mmcblk0p8: 00040000 00000200 "rpm"
mmcblk0p9: 00200000 00000200 "tz"
mmcblk0p10: 00008000 00000200 "sdi"
mmcblk0p11: 00400000 00000200 "hboot"
mmcblk0p12: 00500000 00000200 "sp1"
mmcblk0p13: 00100000 00000200 "wifi"
mmcblk0p14: 00008000 00000200 "ddr"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p17: 00500000 00000200 "wcnss"
mmcblk0p18: 00800000 00000200 "radio_config"
mmcblk0p19: 00180000 00000200 "fsg"
mmcblk0p20: 04b00400 00000200 "radio"
mmcblk0p21: 00400000 00000200 "tool_diag"
mmcblk0p22: 00a00000 00000200 "custdata"
mmcblk0p23: 006ffc00 00000200 "reserve_2"
mmcblk0p24: 00100000 00000200 "misc"
mmcblk0p25: 00180000 00000200 "modem_st1"
mmcblk0p26: 00180000 00000200 "modem_st2"
mmcblk0p27: 01400000 00000200 "fataldevlog"
mmcblk0p28: 00001000 00000200 "debug_config"
mmcblk0p29: 00040000 00000200 "pdata"
mmcblk0p30: 00004000 00000200 "control"
mmcblk0p31: 00140400 00000200 "local"
mmcblk0p32: 00010000 00000200 "extra"
mmcblk0p33: 00100000 00000200 "cdma_record"
mmcblk0p34: 00000400 00000200 "fsc"
mmcblk0p35: 00002000 00000200 "ssd"
mmcblk0p36: 00040000 00000200 "skML]ylink"
mmcblk0p37: 01900000 0000020
mmcblk0p39: 00e28800 00000200 "reserve"
mmcblk0p40: 01000000 00000200 "boot"
mmcblk0p41: 01000000 00000200 "recovery"
mmcblk0p42: 11000000 00000200 "cache"
mmcblk0p43: 90000000 00000200 "system"
mmcblk0p44: 18000000 00000200 "userdata"
[email protected]_a3ul:/ $
Hey guys! My name is Henrique and I am a new member, before I create the account I had read many posts and they were a lot helpful! Now I am with a problem here that I couldn't solve by searching, I'm helping a friend that doesn't even have a computer to study,just a mobile phone... and his cousin tried to put a custom rom in it and now the phone is hard bricked, just appears as qusb_bulk ( I installed the drivers and now is as a COM port named as smotheming 9008),actually I downloaded the flash tool that used the boot partition files in the kdz firmware, however I need the partition.txt to the phone,and I dunno where can I find it! please help me to help a friend,I know that you can do it!
partition.txt
Buthers said:
Hey guys! My name is Henrique and I am a new member, before I create the account I had read many posts and they were a lot helpful! Now I am with a problem here that I couldn't solve by searching, I'm helping a friend that doesn't even have a computer to study,just a mobile phone... and his cousin tried to put a custom rom in it and now the phone is hard bricked, just appears as qusb_bulk ( I installed the drivers and now is as a COM port named as smotheming 9008),actually I downloaded the flash tool that used the boot partition files in the kdz firmware, however I need the partition.txt to the phone,and I dunno where can I find it! please help me to help a friend,I know that you can do it!
Click to expand...
Click to collapse
Hello,
I have he same problem. I found partition.txt on my sdcard:
dev: size erasesize name
mmcblk0p1: 010000 000000 "modem"
mmcblk0p2: 000400 000000 "sbl1"
mmcblk0p3: 000200 000000 "rpm"
mmcblk0p4: 000200 000000 "tz"
mmcblk0p5: 000200 000000 "sdi"
mmcblk0p6: 000800 000000 "aboot"
mmcblk0p7: 000200 000000 "rpmb"
mmcblk0p8: 000200 000000 "tzb"
mmcblk0p9: 000800 000000 "abootb"
mmcblk0p10: 000800 000000 "pad"
mmcblk0p11: 000c00 000000 "modemst1"
mmcblk0p12: 000c00 000000 "modemst2"
mmcblk0p13: 004000 000000 "misc"
mmcblk0p14: 008000 000000 "persist"
mmcblk0p15: 005800 000000 "laf"
mmcblk0p16: 005800 000000 "boot"
mmcblk0p17: 005800 000000 "recovery"
mmcblk0p18: 000c00 000000 "fsg"
mmcblk0p19: 000200 000000 "fsc"
mmcblk0p20: 000200 000000 "ssd"
mmcblk0p21: 000200 000000 "DDR"
mmcblk0p22: 000200 000000 "encrypt"
mmcblk0p23: 000200 000000 "rct"
mmcblk0p24: 002000 000000 "drm"
mmcblk0p25: 002000 000000 "sns"
mmcblk0p26: 005000 000000 "factory"
mmcblk0p27: 008000 000000 "fota"
mmcblk0p28: 000400 000000 "sbl1b"
mmcblk0p29: 008000 000000 "mpt"
mmcblk0p30: 019000 000000 "cust"
mmcblk0p31: 000200 000000 "eksst"
mmcblk0p32: 200000 000000 "system"
mmcblk0p33: 0e1000 000000 "cache"
mmcblk0p34: 3ef600 000000 "userdata"
mmcblk0p35: 003fef 000000 "grow"
Which flash tool are you using and where can you download the firmware files for LG L40?