HOWTO port NAND ROM to NATIVESD
STEP-BY-STEP
This method based on SecureCRT with my modifications and comments[/COLOR]
Click to expand...
Click to collapse
HD Video GUIDE
Click to expand...
Click to collapse
PC Requiments:
PC with installed MS Windows XP/Vista/Se7en and VirtualMachine with Linux based OS (I'm used Ubuntu 11.10 OEM at VMware 8)
Installed Nottepad++
Mobile Requiments:
NAND ROM ported to HTC LEO HD2 (In my example, I used NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13] this rom is based)
Blank template file BareBoneCM7_NativeSD_installer_Diff_Nand.zip
Some NativeSD ROM with compatible kernel files what you want to use in your NativeSD port (In my example, I used HyperDroid-CM7-v6.0.1_NativeSD e.g. my port is CM7 based so I used powerful GB kernel files fro this rom)
Step1. Prepare port files
Create any folder on your PC (example: C:\myport\) and extract in the blank template file
You should have this:
C:\myport\kernel\boot\place kernel + nand ramdisk here
C:\myport\kernel\bootsd\place kernel + sd-ext ramdisk here
C:\myport\kernel\checksys.sh
C:\myport\kernel\mkbootimg
C:\myport\kernel\mkbootimg
C:\myport\META-INF\com\google\android\aroma\ etc... etc... etc...
C:\myport\META-INF\com\google\android\aroma-config
C:\myport\META-INF\com\google\android\update-binary
C:\myport\META-INF\com\google\android\update-binary-installer
C:\myport\META-INF\com\google\android\updater-script
C:\myport\sdcard\NativeSD\clrcad.exe
C:\myport\sdcard\NativeSD\haret.exe
C:\myport\sdcard\NativeSD\startup.txt
C:\myport\system\place the rom system folder contents in here
C:\myport\install.sh
Click to expand...
Click to collapse
Delete 3 blanked information files:
This files is only for you know where need to put kernel files and system folder of base
C:\myport\kernel\boot\place kernel + nand ramdisk here
C:\myport\kernel\bootsd\place kernel + sd-ext ramdisk here
C:\myport\system\place the rom system folder contents in here
Click to expand...
Click to collapse
Extract /system folder from (NAND ROM) in C:\myport\:
You should have this:
C:\myport\system\app\ ... include files, folders & subfolders
C:\myport\system\bin\ ... include files, folders & subfolders
C:\myport\system\etc\ ... include files, folders & subfolders
C:\myport\system\fonts\ ... include files, folders & subfolders
C:\myport\system\framework\ ... include files, folders & subfolders
C:\myport\system\lib\ ... include files, folders & subfolders
C:\myport\system\media\ ... include files, folders & subfolders
C:\myport\system\tts\ ... include files, folders & subfolders
C:\myport\system\usr\ ... include files, folders & subfolders
C:\myport\system\vendor\ ... include files, folders & subfolders
C:\myport\system\xbin\ ... include files, folders & subfolders
C:\myport\system\build.prop
Click to expand...
Click to collapse
Delete all kernel module files:
This step req. because, In my example, I used kernel files from HyperDroid-CM7-v6.0.1_NativeSD
C:\myport\system\lib\modules\alsa-mix-htc-leo.ko
C:\myport\system\lib\modules\alsa-pcm-htc-leo.ko
C:\myport\system\lib\modules\bcm4329.ko
C:\myport\system\lib\modules\cifs.ko
C:\myport\system\lib\modules\fuse.ko
C:\myport\system\lib\modules\kineto_gan.ko
C:\myport\system\lib\modules\msm_rmnet.ko
C:\myport\system\lib\modules\tun.ko
Click to expand...
Click to collapse
P.S. Your module files may be diffirents, just delete it all
C:\myport\system\lib\modules\ no one files exist
Click to expand...
Click to collapse
Extract zImage file from HyperDroid-CM7-v6.0.1_NativeSD rom in two folders:
Duplicate it for boot as NAND and boot as SD
C:\myport\kernel\boot\zImage
C:\myport\kernel\bootsd\zImage
Click to expand...
Click to collapse
Extract module files (.ko)
From: HyperDroid-CM7-v6.0.1_NativeSD modules folder:
HyperDroid-CM7-v6.0.1_NativeSD.zip\system\lib\modules\
Click to expand...
Click to collapse
To: C:\myport\system\lib\modules\
Click to expand...
Click to collapse
It should be like this:
C:\myport\system\lib\modules\bcm4329.ko
C:\myport\system\lib\modules\cifs.ko
C:\myport\system\lib\modules\fuse.ko
C:\myport\system\lib\modules\kineto_gan.ko
C:\myport\system\lib\modules\msm_rmnet.ko
C:\myport\system\lib\modules\reiserfs.ko
C:\myport\system\lib\modules\tun.ko
C:\myport\system\lib\modules\zram.ko
Click to expand...
Click to collapse
Extract initrd.gz from HyperDroid-CM7-v6.0.1_NativeSD (smaller file ~143 Kb):
From: HyperDroid-CM7-v6.0.1_NativeSD.zip\kernel\boot\initrd.gz
To: C:\myport\kernel\boot\initrd.gz
Click to expand...
Click to collapse
Extract initrd.gz from HyperDroid-CM7-v6.0.1_NativeSD (bigger file ~893 Kb):
From: HyperDroid-CM7-v6.0.1_NativeSD.zip\kernel\bootsd\initrd.gz
To: C:\myport\kernel\bootsd\initrd.gz
Click to expand...
Click to collapse
Step2. [Windows] Change port name & port folder name
Open in Nottepad++ file C:\myport\install.sh
Find ths string:
# Set the ROM name
ROM_NAME=EXAMPLE
Click to expand...
Click to collapse
And chenge (red selected: EXAMPLE) to your likly port name:
# Set the ROM name
ROM_NAME=NexusCM7
Click to expand...
Click to collapse
P.S. This is example. Do not use spaces!!
Remeber this name, save changes and exit Nottepad++
Step3. [Linux] Change port name & port folder name
I'm used Ubuntu Linux v11.10 OEM & WinHHTP FileServer to exchange files from my Windows to Linux (at VMware)
Copy your initrd.gz (bigger file) to your Linux
From: C:\myport\kernel\bootsd\initrd.gz
To: \username\home\myport\initrd.gz
Click to expand...
Click to collapse
Where \username\home\ is your own home folder in Linux, and \myport\ is temprary folder to this step. Create it if don't exists
Execute Linux terminal application (window based) by Ctrl+Alt+T
It is should by like this:
[email protected]:~$ _
Click to expand...
Click to collapse
Now you must be in your home folder, but you can check it by command:
[email protected]:~$ ls ./
Click to expand...
Click to collapse
If you see root folder or some other forlder, not [email protected]:~$ you can change it by this command:
[email protected]:~$ cd /username/home
Click to expand...
Click to collapse
Now create temporary work folder, if it wasn't exist by command:
[email protected]:~$ mkdir myport
Click to expand...
Click to collapse
Copy to /username/home/myport/ your initrd.gz (bigger file) as you want
I'm used WinHTTP FileServer for this
Create in your work folder new folder named as "works"
It is should be like this:
/c1cl0n/home/myport/work/
Click to expand...
Click to collapse
Now extract your initrd.gz file to change init file for your port
[email protected]:~/myport$ cp ./initrd.gz ./work
[email protected]:~/myport$ cd ./work
[email protected]:~/myport/work$ gunzip initrd.gz
[email protected]:~/myport/work$ cpio -i < initrd
3261 Blocks
Click to expand...
Click to collapse
Done! Now in /username/home/myport/work/ folder you must have this files and folders:
/bin /data /dev /proc /sbin /system
default.prop init init.android init.htcleo.rc init.htcleo.usb.rc init.rc initrd.gz
logo.rle ueventd.htcleo.rc ueventd.rc
Click to expand...
Click to collapse
Done! initrd.gz now is extracted
Now moveing init file to /username/home/myport/ folder and changing permissions to it (to do it editable)
[email protected]:~/myport/work$ cp ./init ../
[email protected]:~/myport/work$ chmod 777 ../init
Click to expand...
Click to collapse
Now you must edit this file to change a name of your port, what you did in Nottepad++ with install.sh file
Run GEdit and open /username/home/myport/init file
Find this string:
rom_name="NexusHD2"
Click to expand...
Click to collapse
and change it to your name, what you did in Nottepad++ with install.sh file
rom_name="NexusCM7"
Click to expand...
Click to collapse
Save all changes and exit GEdit
Return to terminal window
Now you must replace this file to older and repack initrd.gz
Deleting old file:
[email protected]:~/myport/work$ rm -rf ./init
Click to expand...
Click to collapse
Deleting old initrd.gz it is very important becase we will save all changes in old initrd.gz file in /username/home/myport/initrd.gz
[email protected]:~/myport/work$ rm -rf initrd
Click to expand...
Click to collapse
Putnig new init file in our work folder:
P.S. No req. original permission to it!
[email protected]:~/myport/work$ cp ../initrd ./
Click to expand...
Click to collapse
Repacking your old initrd.gz
[email protected]:~/myport/work$ find . | cpio -o -H newc | gzip > ../initrd.gz
3261 Blocks
Click to expand...
Click to collapse
Done! In the Linux our work is finished
Upload/Copy your changed /username/home/myport/initrd.gz file to your Windows
And trash files and folders of this step:
[email protected]:~/myport/work$ cd ../..
[email protected]:~$ chmod 777 ./myport
Click to expand...
Click to collapse
If Linux talks about permissions, like Access Denied!, change your username to root by command:
[email protected]:~$ sudo su
[email protected]:~$ _
[email protected]:~$ rm -rf ./myport
Click to expand...
Click to collapse
This step is done! Turn off Linux (if you are used it on VirtualMachine and return to Windows
Step4. Replace changed initrd.gz
Put your changed (in Linux OS) initrd.gz file to C:\myport\kernel\bootsd\initrd.gz
Done!
Step5. Change updater-script
Run Nottepad++ and open for edit a file C:\myport\META-INF\com\google\android\updater-script
Find this lines:
run_program("/tmp/install.sh");
if file_getprop("/tmp/nfo.prop","NativeSD") == "true"
then
Click to expand...
Click to collapse
In new tab of Nottepad++ open for edit updater-script file of ported NAND rom:
In my example it is NexusHD2-Gingerbread_V3.2a_NAND_(Android-2.3.7).zip\META-INF\com\google\android\updater-script
Copy into the buffer all text from line:
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
"/system/xbin/arp", "/system/xbin/ash", "/system/xbin/awk",
"/system/xbin/basename", "/system/xbin/bbconfig", "/system/xbin/brctl",
Click to expand...
Click to collapse
To:
set_perm(0, 0, 06755, "/system/xbin/busybox");
set_perm(0, 0, 06755, "/system/xbin/su");
Click to expand...
Click to collapse
It is must be like this:
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
"/system/xbin/arp", "/system/xbin/ash", "/system/xbin/awk",
"/system/xbin/basename", "/system/xbin/bbconfig", "/system/xbin/brctl",
"/system/xbin/bunzip2", "/system/xbin/bzcat", "/system/xbin/bzip2",
"/system/xbin/cal", "/system/xbin/cat", "/system/xbin/catv",
"/system/xbin/chgrp", "/system/xbin/chmod", "/system/xbin/chown",
"/system/xbin/chroot", "/system/xbin/cksum", "/system/xbin/clear",
"/system/xbin/cmp", "/system/xbin/cp", "/system/xbin/cpio",
"/system/xbin/cut", "/system/xbin/date", "/system/xbin/dc",
.........
.........
.........
.........
.........
set_perm(0, 0, 06755, "/system/xbin/hcitool");
set_perm(0, 0, 06755, "/system/xbin/librank");
set_perm(0, 0, 06755, "/system/xbin/procmem");
set_perm(0, 0, 06755, "/system/xbin/procrank");
set_perm(0, 0, 06755, "/system/xbin/tcpdump");
set_perm(0, 0, 06755, "/system/xbin/busybox");
set_perm(0, 0, 06755, "/system/xbin/su");
Click to expand...
Click to collapse
Goto first tab of Nottepad++ (it is tab with ported updater-script) and paste coped data after red marked "then "
It is must be like this:
if file_getprop("/tmp/nfo.prop","NativeSD") == "true"
then
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
"/system/xbin/arp", "/system/xbin/ash", "/system/xbin/awk",
"/system/xbin/basename", "/system/xbin/bbconfig", "/system/xbin/brctl",
"/system/xbin/bunzip2", "/system/xbin/bzcat", "/system/xbin/bzip2",
"/system/xbin/cal", "/system/xbin/cat", "/system/xbin/catv",
"/system/xbin/chgrp", "/system/xbin/chmod", "/system/xbin/chown",
"/system/xbin/chroot", "/system/xbin/cksum", "/system/xbin/clear",
..........
..........
..........
..........
set_perm(0, 0, 06755, "/system/xbin/procrank");
set_perm(0, 0, 06755, "/system/xbin/tcpdump");
set_perm(0, 0, 06755, "/system/xbin/busybox");
set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su", "/system/bin/su");
package_extract_dir("kernel/bootsd", "/boot");
package_extract_dir("kernel/bootsd", "/boot_dir");
package_extract_dir("sdcard", "/sdcard");
package_extract_dir("system", "/system");
else
ui_print("can't find ext4 partition on your SDcard");
ui_print("install failed");
endif;
endif;
##
# ROM SYMLINKS AND PERMISSONS
##
Click to expand...
Click to collapse
Save all changes and close both tabs
Done! updater-script is ready to use
Step6. Prepare AROMA script
Run Nottepad++ (if it is was closed be step5) and open for edit C:\myport\META-INF\com\google\android\aroma-config file
Now change default strings to your likely port name, author, build date etc.
Find this:
ini_set("rom_name", "EXAMPLE");
ini_set("rom_version", "v2");
ini_set("rom_author", "DEVELOPER");
ini_set("rom_device", "HTC HD2");
ini_set("rom_date", "TODAY");
Click to expand...
Click to collapse
Change to this:
ini_set("rom_name", "NexusCM7");
ini_set("rom_version", "v2");
ini_set("rom_author", "YourNickName");
ini_set("rom_device", "HTC HD2");
ini_set("rom_date", "CurrentDate");
Click to expand...
Click to collapse
Save all changes and exit from Nottepad++
Done! Aroma config file is ready to use
This 3 steps is done!
Now yo can create zip archive with your folders & subfolders:
\kernel\
\META-INF\
\sdcard\
\system\
\install.sh
Click to expand...
Click to collapse
and install it via 4EXT Recovery for NativeSD port
Step7. (Optional) Sign created NativeSD zip-archive
This step is optional and I don't know about request of it. I'm just signed my port in UpdatezipCreator
Thats all pplz
My thanks to all who helped me with this, to all xda developers who made this possible and [email protected] who I forgot to thanks
Regard, c1cl0n
u did great help here man thx
seaman2k said:
u did great help here man thx
Click to expand...
Click to collapse
Thanks, hope my work will help other beginners to learn better the NativeSD technology and make our HD2 more greater and useble
If this guide is too hard and not intuitive, tomorrow I can record all steps to video
In fact, everything just seems complicated, yet you can not tell the exact purpose of each file future NativeSD port
Get permission before publishing
Advice: before publishing any ROM that you port to NativeSD, check with the original ROM developer and get their permission. See Forum Rule 12
12. Using the work of others.
If you are developing something that is based on the work of another Member, you MUST first seek their permission, and you must give credit to the member whose work you used.
Click to expand...
Click to collapse
Cheers
Tom
All links removed
Sorry
c1cl0n said:
All links removed
Sorry
Click to expand...
Click to collapse
Would this be better / of additional benefit as a wiki, would allow people to tidy it up a bit, and add in other variations (using the dxixda kitchen on windows, or editing initrd.gz on device (move initrd.gz to /INITRD/ ; make a folder /INITRD/work/ ; cd to /INITRD/work ; then run #gunzip -c ../initrd.gz | cpio -i)?
Would also allow us to have all the NativeSD guides in one place (porting, installation, WP7 installation etc.)
HypoTurtle said:
Would this be better / of additional benefit as a wiki, would allow people to tidy it up a bit, and add in other variations (using the kitchen on windows, editing initrd.gz on device (need to confirm if can be done properly)?
Would also allow us to have all the NativeSD guides in one place (porting, installation, WP7 installation etc.)
Click to expand...
Click to collapse
i used above steps on ubuntu and i can say it help me too much and i success to convert and modded nand rom to nativesd rom with all update i needed for me ..yes the guide is very good with the video i think it will be excellent
thanks. looks perfect and very easy to reproduce by starters.
I will add a link to my thread
Sent from my NexusHD2 using xda premium
as I understand, it is not possible to use nativesd script with sense3.5 roms?
dimdimdim said:
as I understand, it is not possible to use nativesd script with sense3.5 roms?
Click to expand...
Click to collapse
it working boot now
under more dev & fix
You manage to make it boot!? That's great news!
boxmax said:
it working boot now
under more dev & fix
Click to expand...
Click to collapse
OMG, Box, you are here with us again or this is a dream only!!!?
dimdimdim said:
OMG, Box, you are here with us again or this is a dream only!!!?
Click to expand...
Click to collapse
glad to see you dimdimdim & datagr :good:
i edited initrd.gz for "Sense" now working Native SD but with old kernel Ty14 ... market & download FAST no more lag for market ...
i try again for kernel marc .... need some magic
datagr said:
You manage to make it boot!? That's great news!
Click to expand...
Click to collapse
What did I say, boxmax would get it working
Sent from my GT-I9100 using Tapatalk 2
boxmax said:
glad to see you dimdimdim & datagr :good:
i edited initrd.gz for "Sense" now working Native SD but with old kernel Ty14 ... market & download FAST no more lag for market ...
i try again for kernel marc .... need some magic
Click to expand...
Click to collapse
yes, it's worth it. as marc 's kernel made real miracle with sense builds - energy's one has no more limits in usage even taking into consideration ramless of hd2 for that kind of roms. that would be great to beat the result with boxmax's nativesd sense35:good:
Hi
thank you very much
I successfully converted my ROM from NAND to NativeSD
All is boooting and working OK
Just a weird thing : system and data seem to be 200Mo of size, whereas my ext4 partition is 4Gb
any idea ?...
Hi denseye
I'm very glad to see your success
I'm hope this step-by-step guide will help to other beginners
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
Hello Everyone,I own a International Galaxy S3 I9300,and wanted to know one thing
How can I remove modem.bin from ROMS? I just have to delete modem.bin or also have to modify updater-script? Thanks in advance guys! :highfive:
First solution I guess but no harm to look the script and see if there are specific lines for modem.bin and comment them. Most roms come without modem.
Bump before 24h delay is a violation of xda rules.
My mistake, i'm sorry
Anyway, yes i found the lines in the updater-script, they are at the end of the file
Sent from my GT-I9300 using xda app-developers app
EDIT: This are the last lines that regard the modem flash
Code:
ui_print("Flashing kernel");
assert(package_extract_file("pendroz/boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p5"),
delete("/tmp/boot.img"));
ui_print("Flashing modem");
package_extract_file("pendroz/flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
assert(package_extract_file("pendroz/modem.bin", "/tmp/modem.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p7", "/tmp/modem.bin"),
delete("/tmp/modem.bin"));
delete("/tmp/flash_image");
unmount("/system");
unmount("/data");
ui_print("");
ui_print(" Enjoy ");
ui_print(" Please reboot ");
Yes these are the lines. Just remove them and modem won't be flashed.
Striatum_bdr said:
Yes these are the lines. Just remove them and modem won't be flashed.
Click to expand...
Click to collapse
So I must remove only this lines?
Code:
ui_print("Flashing modem");
package_extract_file("pendroz/flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
assert(package_extract_file("pendroz/modem.bin", "/tmp/modem.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p7", "/tmp/modem.bin"),
delete("/tmp/modem.bin"));
delete("/tmp/flash_image");
And leave kernel?
Yes. Kernel has nothing to do with modem.
Striatum_bdr said:
Yes. Kernel has nothing to do with modem.
Click to expand...
Click to collapse
Okay then,will remove the lines and try to flash the rom,i'll let ya know,thank you very much man! :highfive:
Btw other question...the rom i want to install is based on a different build from the one i have now..it doesnt matter if modem will be different?
Sent from my GT-I9300 using xda app-developers app
Any single modem should work with all roms.
Sent from my GT-I9300 using Tapatalk 2
That's why IMO a Rom shouldn't provide any modem.
Agreed. I don't like the assumption that I'd want to upgrade my modem
Sent from my GT-I9300 using Tapatalk 2
Shouldn't he have left this line in his updater-script:
delete("/tmp/flash_image");
wangdaning said:
Shouldn't he have left this line in his updater-script:
delete("/tmp/flash_image");
Click to expand...
Click to collapse
It worked perfectly man,even without that line..
Anyway I agree too with you guys,modem update should be manual or it should be an optional selection in Aroma..
...
...
wangdaning said:
Shouldn't he have left this line in his updater-script:
delete("/tmp/flash_image");
Click to expand...
Click to collapse
It would do no harm leaving it in. Any delete /tmp is good but removing this line:
package_extract_file("pendroz/flash_image", "/tmp/flash_image");
Means theres nothing in flash_image to delete so it shouldn't be the end of the world
Sent from my GT-I9300 using Tapatalk 2
Other question,if I may want to revert to stock 4.1.2 ROM,how do I remove modem.bin from the tar.md5 package? I opened it with winrar and removed modem.bin then repacked,am I good to go??
Thanks!!
Sent from my GT-I9300 using xda app-developers app
bump!
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?