[Q] Help for Htc Desire 610 Tampered flag removal - HTC Desire 610

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:/ $

Related

anyone know the dev/block for system?

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

how to get. Img

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

[ROM][BASE]][10e][TMOBILE][769BK]

stock 10e Odex
- stock 10e (tmobile)
- rooted
- zipaligned
- busy box
- tmobile bloat removed
- made a change to build.prop to stop ota nag
- base for others to play with
update
ok, I had a chance to play with the 769BK again, and was able to get this far, Since i sold my Phone I cant do much more. This might have bugs,and problems i missed, The problem is The locked bootloader and Formatting /system the correct way. LG did some interesting security things i give them that, but i wont start my rant ..
Anyway, Make a nandroid backup, and use at your own risk, you have been warned!, for anyone that wants to use this and fix anything I missed feel free just mention me somewhere in your description, I put a lot of time into this, and again since i don't have the phone anymore this is all i can do (feel free to email me another one ), hope this helps someone in getting tons of roms for users here. again use with caution, make something out of this, and fix anything i missed!
A big thanks to my friend for letting me play with her 769BK, your a brave girl
Known issues
- deleteing apks causes some weirdness on reboot (again only had 3 hours to test this)
think it might be a permission thing and or LG lol
- deleting carrier iq from rom would have caused setup wizard to crash
Click to expand...
Click to collapse
"I am not responsible if your phone does the following"
bricks / blows up / or stops loving you
download
iB4STiD said:
minimal display of boredom
- based off stock 10e (tmobile)
- deodexed
- rooted
- zipaligned
- busy box
- tmobile bloat removed
- carrier iq removed
- adblocking, no need for an app
- boot sounds removed
- other stuff i forgot
update
well well, look like lg has a little security check.. after i flashed my rom...
I'm greeted with a lg security error boot screen , looks like the bootloader is indeed locked​
Click to expand...
Click to collapse
WOW, you did it you know what will be great? including your JB theme! this way we gonna have our first CUSTOM ROM :good:
too bad i have a P760. but still i look further for the development of this one.
hamdimo said:
WOW, you did it you know what will be great? including your JB theme! this way we gonna have our first CUSTOM ROM :good:
too bad i have a P760. but still i look further for the development of this one.
Click to expand...
Click to collapse
just have to figure out a way around this security problem.. anyone have any ideas?
Re: [ROM][MDOB][v1][BETA][10e][TMOBILE][769BK]
Maybe Artas might have an idea?
Sent from my LG-P769 using Tapatalk 2
iB4STiD said:
just have to figure out a way around this security problem.. anyone have any ideas?
Click to expand...
Click to collapse
Do you mean the "Security Error"?
Is the P769 bootloader unlocked? If yes, maybe we can flash its bootloader to a P760..
As far as I know these commands will dump the bootloader:
Code:
su
dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/x of=/sdcard/external_sd/x-loader.img
dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/u of=/sdcard/external_sd/u-boot.img
sguerrini97 said:
Do you mean the "Security Error"?
Is the P769 bootloader unlocked? If yes, maybe we can flash its bootloader to a P760..
As far as I know these commands will dump the bootloader:
Code:
su
dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/x of=/sdcard/external_sd/x-loader.img
dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/u of=/sdcard/external_sd/u-boot.img
Click to expand...
Click to collapse
after hours of playing with this, heres what i found...
1) the bootloader is not letting me write over system, i can wipe the system but i cant write it, I dont think its my updater script, cause i never had this problem b4, then again i never had to deal with a locked bootloader,
2) the boot.img seems to flash but then im met with the lg logo with security error,
tried flashing with out boot.img but then i get a status 0 error, if some1 wants to look over the updater script and see if im missing something let me know, signing the rom doesn't help either so ya,
Im using the bootstrap recovery not sure if that could be an issue also, sigh to many what ifs here. btw soft bricking the phone is fun
iB4STiD said:
after hours of playing with this, heres what i found...
1) the bootloader is not letting me write over system, i can wipe the system but i cant write it, I dont think its my updater script, cause i never had this problem b4, then again i never had to deal with a locked bootloader,
2) the boot.img seems to flash but then im met with the lg logo with security error,
tried flashing with out boot.img but then i get a status 0 error, if some1 wants to look over the updater script and see if im missing something let me know, signing the rom doesn't help either so ya,
Im using the bootstrap recovery not sure if that could be an issue also, sigh to many what ifs here. btw soft bricking the phone is fun
Click to expand...
Click to collapse
Post your script and the output of the mount command so I can look at it.
kevev said:
Post your script and the output of the mount command so I can look at it.
Click to expand...
Click to collapse
Mount points
Code:
# mount point fstype device [device2]
/data ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
/cache ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
/system ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/system
/misc emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/misc
/persist ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/persist
/mlt ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/mlt
/dvp ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/divxkey
/ve ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/ve
/boot emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/boot
/recovery emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
updater-script
Code:
#ui_print("---------------------");
ui_print("MDOB v1 10e 769BK DEODEX");
ui_print("by iB4STiD");
ui_print("---------------------");
ui_print("");
ui_print("Applying Update");
show_progress(0.1, 0);
format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/system");
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");
package_extract_dir("system", "/system");
symlink("dumpstate", "/system/bin/dumpcrash");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/cmp");
symlink("debuggerd", "/system/bin/csview");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/dmesg");
symlink("toolbox", "/system/bin/getevent");
symlink("toolbox", "/system/bin/getprop");
symlink("toolbox", "/system/bin/hd");
symlink("toolbox", "/system/bin/id");
symlink("toolbox", "/system/bin/ifconfig");
symlink("toolbox", "/system/bin/iftop");
symlink("toolbox", "/system/bin/insmod");
symlink("toolbox", "/system/bin/ioctl");
symlink("toolbox", "/system/bin/ionice");
symlink("toolbox", "/system/bin/kill");
symlink("toolbox", "/system/bin/ln");
symlink("toolbox", "/system/bin/log");
symlink("toolbox", "/system/bin/ls");
symlink("toolbox", "/system/bin/lsmod");
symlink("toolbox", "/system/bin/lsof");
symlink("toolbox", "/system/bin/mkdir");
symlink("toolbox", "/system/bin/mount");
symlink("toolbox", "/system/bin/mv");
symlink("toolbox", "/system/bin/nandread");
symlink("toolbox", "/system/bin/netstat");
symlink("toolbox", "/system/bin/newfs_msdos");
symlink("toolbox", "/system/bin/notify");
symlink("toolbox", "/system/bin/printenv");
symlink("toolbox", "/system/bin/ps");
symlink("toolbox", "/system/bin/reboot");
symlink("toolbox", "/system/bin/renice");
symlink("toolbox", "/system/bin/rm");
symlink("toolbox", "/system/bin/rmdir");
symlink("toolbox", "/system/bin/rmmod");
symlink("toolbox", "/system/bin/route");
symlink("toolbox", "/system/bin/schedtop");
symlink("toolbox", "/system/bin/sendevent");
symlink("toolbox", "/system/bin/setconsole");
symlink("toolbox", "/system/bin/setprop");
symlink("mksh", "/system/bin/sh");
symlink("toolbox", "/system/bin/sleep");
symlink("toolbox", "/system/bin/smd");
symlink("toolbox", "/system/bin/start");
symlink("toolbox", "/system/bin/stop");
symlink("toolbox", "/system/bin/sync");
symlink("toolbox", "/system/bin/top");
symlink("toolbox", "/system/bin/touch");
symlink("toolbox", "/system/bin/umount");
symlink("toolbox", "/system/bin/uptime");
symlink("toolbox", "/system/bin/vmstat");
symlink("toolbox", "/system/bin/watchprops");
symlink("toolbox", "/system/bin/wipe");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 06755, "/system/bin/ip");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm_recursive(0, 2000, 0755, 0755, "/system/vendor/bin");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor/etc");
set_perm_recursive(0, 0, 0755, 0644, "/system/vendor/firmware");
set_perm(0, 2000, 0755, "/system/vendor/firmware");
set_perm(0, 2000, 0755, "/system/vendor/lib");
set_perm(0, 2000, 0755, "/system/vendor/lib/egl");
set_perm(0, 2000, 0755, "/system/vendor/lib/hw");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 1000, 0755, "/system/xbin/busybox");
symlink("/system/xbin/busybox", "/system/bin/busybox");
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su", "/system/bin/su");
show_progress(0.1, 10);
show_progress(0.2, 0);
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
show_progress(0.2, 10);
unmount("/system");
That looks like python. Is it?
If it is I need to see the "mount" function to check if it is mounting read/write or just read. The problem could be there.
Also, do you have the output of this code? Need to see where it errors.
the updater-script is in edify format, as far as the the log from cwm, heres the problem once the system formats its taking the bootstrap recovery with it. so i cant even get a log file. If this wasn't a bootstrap recovery life would be much much easier, cause after it softbricks i lose everything and have restore the whole system losing bootstrap in the process. Normally i would just be able back into recovery and restore nandroid backup and try again. But no that would be to simple
actually, let me see something brb...
Im going to try to mount system with busybox ... lets see, what the hell brb
ok, got it to write but not wipe right.... getting closer
iB4STiD said:
ok, got it to write but not wipe right.... getting closer
Click to expand...
Click to collapse
I know busybox. Shell is my friend. Let me know if I can help with anything.
kevev said:
I know busybox. Shell is my friend. Let me know if I can help with anything.
Click to expand...
Click to collapse
lol, well lets see, didn't need to use the busybox way around..
update
1) able to format and write to system
2) problem is something is wrong there is an extreme lag when phone starts up ...
3) getting very tired of playing with this
4) hating LG more and more each passing second!!
5) did i mention I hate LG?
ok going to try this for a bit more, off to brick my phone *again*
Update
well, b4 i throw this phone against the wall, im going to pull the system img from this piece of (censored) and try this again. If you guys don't hear from me its because I took a vacation....
someplace nice and warm, with lots of blonde chicks, and phones that arent made by LG.. i feel a rant coming on i should go
iB4STiD said:
Update
well, b4 i throw this phone against the wall, im going to pull the system img from this piece of (censored) and try this again. If you guys don't hear from me its because I took a vacation....
someplace nice and warm, with lots of blonde chicks, and phones that arent made by LG.. i feel a rant coming on i should go
Click to expand...
Click to collapse
lol! Good luck
p.s. Check the block size of the original system partition. The default size may be way too small or way too large on the new partition and this can cause slow read/write.
dumpe2fs /dev/sda1 | grep "Block size" (Replace sda1 with the correct device)
But this may be something hanging at load, so I may be way off. Just grabbing at straws here as I can't see what is happening.
kevev said:
lol! Good luck
p.s. Check the block size of the original system partition. The default size may be way too small or way too large on the new partition and this can cause slow read/write.
dumpe2fs /dev/sda1 | grep "Block size" (Replace sda1 with the correct device)
But this may be something hanging at load, so I may be way off. Just grabbing at straws here as I can't see what is happening.
Click to expand...
Click to collapse
Thanks.. i'll check sizes again everything is hazy at this point
Ok here what i found and yes after all this time im still doing this lol,
this doesnt work why? doesn't want to mount
Code:
ui_print("-Writing SYSTEM");
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");
package_extract_dir("/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");
this does work to mount and write but LAG!!
Code:
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("system", "/system");
what i will try last, then i give up
Code:
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");
if the above doesnt work i will package this up and if someone wants to give it a go, god bless you
ebay and this phone are looking good , soon very soon!
iB4STiD said:
if the above doesnt work i will package this up and if someone wants to give it a go, god bless you
ebay and this phone are looking good , soon very soon!
Click to expand...
Click to collapse
I'll probably be seeing you over on the Nexus 4 side eh? Even though it's LG it's unnnlooocccckkkeedddd
Re: [ROM][MDOB][v1][BETA][10e][TMOBILE][769BK]
I originally got the Galaxy S Blaze but traded it for this phone cause I wanted the bigger screen. I really hope it gets easier to develop on this phone
Sent from my LG-P769 using xda app-developers app
iB4STiD said:
Thanks.. i'll check sizes again everything is hazy at this point
Ok here what i found and yes after all this time im still doing this lol,
this doesnt work why? doesn't want to mount
Code:
ui_print("-Writing SYSTEM");
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");
package_extract_dir("/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");
this does work to mount and write but LAG!!
Code:
run_program("/sbin/busybox", "mount", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p10", "/system");
what i will try last, then i give up
Code:
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");
if the above doesnt work i will package this up and if someone wants to give it a go, god bless you
ebay and this phone are looking good , soon very soon!
Click to expand...
Click to collapse
This should let you know if the symlink is correct:
`ls -la /dev/block/platform/omap/omap_hsmmc.1/by-name/system`
Are you mounting twice in the second command? Maybe try `mount -t ext4 -o defaults,rw /dev/block/mmcblk0p10 /system`
or if /system is already mounted try this `mount -t ext4 -o rw,remount /dev/block/mmcblk0p10 /system`
I know the "rw" is redundant because "defaults" should include it. But i am just paranoid.
Jrkoffjonson said:
I'll probably be seeing you over on the Nexus 4 side eh? Even though it's LG it's unnnlooocccckkkeedddd
Click to expand...
Click to collapse
after I get my tax return, i'm ordering one, myself.

Porting MTK6752 devices (A7000-Vibe 2.5 specific)

Hi Guys,
It is important to know that the porting process for lollipop pretty much remains the same to a large degree.. There are some hits and misses. But I am adding below a list of files that have been used as a replacement on the vibe 2.5 ROMs .
The Vibe 2.5 ROMS seem a little complicated and seem to need a large replacement set. If we find a shorter way or if you find a shorter way, please comment that and it can be a part of this guide.
This is specific to the Lenovo A7000 series . The source ROM is from a K3 note.
When you port an AOSP ROM , you may need lesser replacements in libs and bins, but you may need to replace the sdcard binary sometimes. so be careful and happy porting.
here is a list
-------------------------------------
bin
etc
lib
lib64
******************************************************
-------------------------------------
/system/bin
-------------------------------------
audiocmdservice_atci
bcc
bootanimation
ccci_mdinit
downloader
factory
gzip_static
hostapd
installd
ip6tables
ipod
iptables
make_ext4fs
mdnsd
mtkbt
ndc
netd
pq
recovery
vold
wpa_cli
wpa_supplicant
-------------------------------------
******************************************************
-------------------------------------
/system/etc
-------------------------------------
/system/etc/.tp overwrite
/system/etc/firmware replace all
/system/etc/mddb replace all
apns-conf.xml
spn-conf.xml
-------------------------------------
******************************************************
-------------------------------------
/system/lib
-------------------------------------
lib3a.so
lib3a_sample.so
libacdk.so
libadpcm.so
libAGifEncoder.so
libaudioflinger.so
libaudiopolicymanager.so
libaudiopolicymanagerdefault.so
libaudiopolicyservice.so
libbcc.so
libbcinfo.so
libbtcusttable.so
libc.so
libcam.camadapter.so
libcam.camnode.so
libcam.camshot.so
libcam.client.so
libcam.hal3a.v3.so
libcam.halsensor.so
libcam.iopipe.so
libcam.jni.lomohaljni.so
libcam.metadataprovider.so
libcam.paramsmgr.so
libcam.sdkclient.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libcameraservice.so
libcamera_client_mtk.so
libdpframework.so
libexif.so
libextsimap.so
libfeatureio.so
libhwui.so
libimageio.so
libimageio_plat_drv.so
libinputflinger.so
libjpeg.so
libLLVM.so
libm4u.so
libmdnssd.so
libmedia.so
libmediaplayerservice.so
libMiraVision_jni.so
libn3d3a.so
libnetd_client.so
libpng.so
libpq_cust.so
libquickshot.so
libRS.so
libRScpp.so
libRSCpuRef.so
libRSDriver.so
libshowlogo.so
libsqlite.so
libssl.so
libstagefright.so
libstagefright_omx.so
libstagefright_soft_aacdec.so
libstagefright_soft_aacenc.so
libstagefright_soft_flacenc.so
libstagefright_soft_hevcdec.so
libstagefright_wfd.so
libsurfaceflinger.so
mtk-ril.so
mtk-rilmd2.so
-------------------------------------
******************************************************
-------------------------------------
/system/lib64/egl
-------------------------------------
libGLES_mali.so
-------------------------------------
******************************************************
-------------------------------------
/system/lib64/hw
-------------------------------------
audio.primary.mt6752.so
audio_policy.default.so
gps.default.so
mmsdk.default.so
sensors.mt6752.so
-------------------------------------
******************************************************
-------------------------------------
/system/lib64
-------------------------------------
lib3a.so
lib3a_sample.so
libacdk.so
libaudiopolicymanager.so
libaudiopolicymanagerdefault.so
libaudiopolicyservice.so
libbcc.so
libbcinfo.so
libbinder.so
libbtcusttable.so
libc.so
libcam.camadapter.so
libcam.camnode.so
libcam.camshot.so
libcam.client.so
libcam.hal3a.v3.so
libcam.halsensor.so
libcam.iopipe.so
libcam.jni.lomohaljni.so
libcam.metadataprovider.so
libcam.paramsmgr.so
libcam.sdkclient.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libcameraservice.so
libcamera_client_mtk.so
libdpframework.so
libexif.so
libfeatureio.so
libhwui.so
libimageio.so
libimageio_plat_drv.so
libinputflinger.so
libjpeg.so
libLLVM.so
libm4u.so
libmdnssd.so
libmedia.so
libMiraVision_jni.so
libn3d3a.so
libnetd_client.so
libpac.so
libpng.so
libpq_cust.so
libquickshot.so
libRS.so
libRScpp.so
libRSCpuRef.so
libRSDriver.so
libsoundtrigger.so
libsqlite.so
libssl.so
libstagefright.so
libstagefright_omx.so
libstagefright_soft_aacdec.so
libstagefright_soft_aacenc.so
libstagefright_soft_flacenc.so
libstagefright_soft_hevcdec.so
libsurfaceflinger.so
-------------------------------------
Have these files ready in a folder separated into their respective folders.
NOTE:
DO NOT REBOOT THE PHONE AFTER YOU FLASH THE ZIP.
once you are done flashing the zip, mount the system and delete the recovery-from-boot.p (this is very important else you will end up with a messed up recovery )
once that is done, keep the system mounted and use the following commands
open the folder you have the files arranged correctly in.
it should have the folders as bin, etc , lib , lib64 .
press shift and right click , select open command window here.
when you open the command window use the command below to push the files to the phone.
adb push . /system
******************************************************
pull the build.prop with
adb pull /system/build.prop
--------------------------------
edit build.prop with the values below
ro.lenovo.region=row
ro.sf.lcd_density=320
ro.product.locale.language=en
ro.product.locale.region=US
#add below lines for adb debugging.
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
----------------------------------------------------------------------------------------------
save this file and push it back with the command
adb push build.prop /system
----------------------------------------------------------------------------------------------
Boot.img editing.
This is the same as the others but ensure your default prop is as below to enable debugging.
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.adb.secure=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
persist.service.acm.enable=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
ro.zygote=zygote64_32
ro.mount.fs=EXT4
camera.disable_zsl_mode=1
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
ro.dalvik.vm.native.bridge=0
--------------------------------------------------------
Remember some ROMS need the partition to be 2.6 GB. i have scatter that can make the system partition 3 GB. I will upload that and share a link here.
--------------------------------------------------------
flashing the rom
the updater-script needs a bit of edit to flash the Rom as it is on the phone. Delete the lines in red.
replace the boot.img with the edited boot.img (I hope you all know how to do that edit)
--------------------------------------------------------------------------------------------------------------------
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/data", "");
get_lenovo_custom1("1431948134") == "OK" || abort("Can't install this package (Mon May 18 19:22:14 CST 2015) over newer build (" + getprop("ro.build.data") + "). Or lenovo can't allow to rollback.");
unmount("/data");
getprop("ro.product.device") == "aio_otfp" || abort("This package is for "aio_otfp" devices; this is a "" + getprop("ro.product.device") + "".");
show_progress(0.750000, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p6", "0", "/system");
block_image_update("system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "bootimg"),
delete("/tmp/boot.img"));
assert(run_program("/system/bin/dd", "if=/dev/zero", "of=/proc/driver/mtd_writeable", "bs=3", "count=1"));
assert(package_extract_file("logo.img", "/tmp/logo.img"),
write_raw_image("/tmp/logo.img", "logo"),
delete("/tmp/logo.img"));
assert(package_extract_file("uboot.img", "/tmp/uboot.img"),
write_raw_image("/tmp/uboot.img", "uboot"),
delete("/tmp/uboot.img"));
assert(package_extract_file("mobicore.bin", "/tmp/tee1.img"),
write_raw_image("/tmp/tee1.img", "tee1"),
delete("/tmp/tee1.img"));
show_progress(0.200000, 10);
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/data", "");
delete_recursive("/data/data/com.chinamworld.main/.cache");
unmount("/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/data", "");
!(get_lenovo_custom2("1431948134") == "OK") || format("ext4", "EMMC", "/dev/block/mmcblk0p3", "0", "/data");
unmount("/data");
---------------------------------------------------------------------------------------------------------------
Resized Scatter
https://drive.google.com/folderview...04YnE0V2UxXzVtOTBseWd5T2FqWmh5TDg&usp=sharing
Remember you will need to format the phone. If you format the phone you will lose IMEI and you will see the wifi 0x0 error showing up in the access point settings (safe to ignore that). you can use the maui meta tool in that share to fix the imei and you can search for the sn write tool to fix the wifi error (i didnt bother , it just shows up and doesn't bother me) .
Click to expand...
Click to collapse
To flash with the new scatter you will select the upgrade or format + download option. ensure the DL all with checksum is selected. You will need to select the right files and all the files need to be selected. Ensure you check tutorials on xda before you undertake this.
Remember to start from scratch, you will need to flash the custom recovery. you can find the custom recovery on xda. start there.
Disclaimer:
I am not responsible for any mess you get into with these steps. Remember, if in doubt ask questions, watch videos and learn before you mess things up.
Press THANKS if this helps you and rate this thread the way it helped you. Thanks again. Took some time to write this for you all. :fingers-crossed:
BEST
maxritz said:
Hi Guys,
It is important to know that the porting process for lollipop pretty much remains the same to a large degree.. There are some hits and misses. But I am adding below a list of files that have been used as a replacement on the vibe 2.5 ROMs .
The Vibe 2.5 ROMS seem a little complicated and seem to need a large replacement set. If we find a shorter way or if you find a shorter way, please comment that and it can be a part of this guide.
This is specific to the Lenovo A7000 series . The source ROM is from a K3 note.
When you port an AOSP ROM , you may need lesser replacements in libs and bins, but you may need to replace the sdcard binary sometimes. so be careful and happy porting.
here is a list
-------------------------------------
bin
etc
lib
lib64
******************************************************
-------------------------------------
/system/bin
-------------------------------------
audiocmdservice_atci
bcc
bootanimation
ccci_mdinit
downloader
factory
gzip_static
hostapd
installd
ip6tables
ipod
iptables
make_ext4fs
mdnsd
mtkbt
ndc
netd
pq
recovery
vold
wpa_cli
wpa_supplicant
-------------------------------------
******************************************************
-------------------------------------
/system/etc
-------------------------------------
/system/etc/.tp overwrite
/system/etc/firmware replace all
/system/etc/mddb replace all
apns-conf.xml
spn-conf.xml
-------------------------------------
******************************************************
-------------------------------------
/system/lib
-------------------------------------
lib3a.so
lib3a_sample.so
libacdk.so
libadpcm.so
libAGifEncoder.so
libaudioflinger.so
libaudiopolicymanager.so
libaudiopolicymanagerdefault.so
libaudiopolicyservice.so
libbcc.so
libbcinfo.so
libbtcusttable.so
libc.so
libcam.camadapter.so
libcam.camnode.so
libcam.camshot.so
libcam.client.so
libcam.hal3a.v3.so
libcam.halsensor.so
libcam.iopipe.so
libcam.jni.lomohaljni.so
libcam.metadataprovider.so
libcam.paramsmgr.so
libcam.sdkclient.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libcameraservice.so
libcamera_client_mtk.so
libdpframework.so
libexif.so
libextsimap.so
libfeatureio.so
libhwui.so
libimageio.so
libimageio_plat_drv.so
libinputflinger.so
libjpeg.so
libLLVM.so
libm4u.so
libmdnssd.so
libmedia.so
libmediaplayerservice.so
libMiraVision_jni.so
libn3d3a.so
libnetd_client.so
libpng.so
libpq_cust.so
libquickshot.so
libRS.so
libRScpp.so
libRSCpuRef.so
libRSDriver.so
libshowlogo.so
libsqlite.so
libssl.so
libstagefright.so
libstagefright_omx.so
libstagefright_soft_aacdec.so
libstagefright_soft_aacenc.so
libstagefright_soft_flacenc.so
libstagefright_soft_hevcdec.so
libstagefright_wfd.so
libsurfaceflinger.so
mtk-ril.so
mtk-rilmd2.so
-------------------------------------
******************************************************
-------------------------------------
/system/lib64/egl
-------------------------------------
libGLES_mali.so
-------------------------------------
******************************************************
-------------------------------------
/system/lib64/hw
-------------------------------------
audio.primary.mt6752.so
audio_policy.default.so
gps.default.so
mmsdk.default.so
sensors.mt6752.so
-------------------------------------
******************************************************
-------------------------------------
/system/lib64
-------------------------------------
lib3a.so
lib3a_sample.so
libacdk.so
libaudiopolicymanager.so
libaudiopolicymanagerdefault.so
libaudiopolicyservice.so
libbcc.so
libbcinfo.so
libbinder.so
libbtcusttable.so
libc.so
libcam.camadapter.so
libcam.camnode.so
libcam.camshot.so
libcam.client.so
libcam.hal3a.v3.so
libcam.halsensor.so
libcam.iopipe.so
libcam.jni.lomohaljni.so
libcam.metadataprovider.so
libcam.paramsmgr.so
libcam.sdkclient.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libcameraservice.so
libcamera_client_mtk.so
libdpframework.so
libexif.so
libfeatureio.so
libhwui.so
libimageio.so
libimageio_plat_drv.so
libinputflinger.so
libjpeg.so
libLLVM.so
libm4u.so
libmdnssd.so
libmedia.so
libMiraVision_jni.so
libn3d3a.so
libnetd_client.so
libpac.so
libpng.so
libpq_cust.so
libquickshot.so
libRS.so
libRScpp.so
libRSCpuRef.so
libRSDriver.so
libsoundtrigger.so
libsqlite.so
libssl.so
libstagefright.so
libstagefright_omx.so
libstagefright_soft_aacdec.so
libstagefright_soft_aacenc.so
libstagefright_soft_flacenc.so
libstagefright_soft_hevcdec.so
libsurfaceflinger.so
-------------------------------------
******************************************************
edit build.prop
ro.lenovo.region=row
ro.sf.lcd_density=320
ro.product.locale.language=en
ro.product.locale.region=US
------------------------------
Add below for Adb debug in build as well as default.prop
------------------------------
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
----------------------------------------------------------------------------------------------
Boot.img editing.
This is the same as the others but ensure your default prop is as below to enable debugging.
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.adb.secure=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
persist.service.acm.enable=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
ro.zygote=zygote64_32
ro.mount.fs=EXT4
camera.disable_zsl_mode=1
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
ro.dalvik.vm.native.bridge=0
Click to expand...
Click to collapse
Best detailed tutorial.... Thanks mate
but the question is brother how do they flash this to their phones... :-/
Bro I am unable to fix IMEI pls help me i that respect
How To Fix Invalid IMEI
Hi, you have an idea to correct the LED notification? (Lenovo)
maxritz said:
Press THANKS if this helps you and rate this thread the way it helped you. Thanks again. Took some time to write this for you all. :fingers-crossed:
Click to expand...
Click to collapse
Thanks bro,
A very useful guide indeed :good:
Sir you can port the Elephone P7000 to Ulephone be touch . Can port my phone not turning on

Lg (l40 d175) hard bricked (9008) , where I find partition.txt?or how can i create?

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?

Categories

Resources