How to pull boot.img from neo v ROM..?
Use 7zip and flash it with flashboot
Sent from my MT15i using xda premium
But I cannot find Boot.img in any part of the rom in Neo v please help
dendenny01 said:
How to pull boot.img from neo v ROM..?
Click to expand...
Click to collapse
May I ask why you need .img of stock kernel?
I want edit edit ramdisk and kernel
dendenny01 said:
I want edit edit ramdisk and kernel
Click to expand...
Click to collapse
I didn't find way to get .img from .sin, but I packed zImage(compiled from source) and kernel.elf.ramdisk.gz(which I got from flashtool->elf extract) into .img so please test it(before you edit it), as I'm not on stock rom, but I did seen boot logo, so it does boot.
I think if you've unlocked the bootloader you can boot `recoveryNeo.img` (the CWM image) and just create a backup?
alvinwong_1234 said:
and just create a backup?
Click to expand...
Click to collapse
of what? kernel? erm, no can do
You can try opening a shell to your phone via adb shell, then type 'su' to get root permissions then type:
Code:
#cat /proc/mtd
And you should get something like this:
Code:
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 04380000 00020000 "system"
mtd4: 04380000 00020000 "cache"
mtd5: 04ac0000 00020000 "userdata"
To get the boot.img use this command:
Code:
# cat /dev/mtd/mtd2 > /sdcard/boot.img
Related
Can we add a new section for the LG Optimus One P500?
Thank You
rotorto said:
Can we add a new section for the LG Optimus One P500?
Thank You
Click to expand...
Click to collapse
I agree!
Bye
Franco
rotorto said:
Can we add a new section for the LG Optimus One P500?
Thank You
Click to expand...
Click to collapse
Yes, please create a forum for the LG Optimus P500.
giacor
came on men
create this section for LG Optimus one with Google!
thanks
Yes!!! You know you want it!
Thanks!
yes please, can you add this section?
yes please, can you add this section?
Add it.
Thanks!
Please, Add it
rotorto said:
Can we add a new section for the LG Optimus One P500?
Thank You
Click to expand...
Click to collapse
Yes I think it would be useful
Proud owner of a LG P500 Optimus One since 2 days, great device, please open a section for it! It deserves that!
I'm seeking a rom dump from the P500 to aid in porting froyo to the LG VS740. I'll also try to make a custom recovery for you as I have done ones for the lg ally and htc incredible as a thank you for dumping the files.
It should be able to be rooted with universal androot or else use the rageagainstthecage-arm5.bin method.
Once rooted from adb shell or terminal app type:
Code:
su
cat proc/mtd
note the mtd partition # of boot & recovery.
then in the dd parts use the mtd number of your boot and recovery partitons
for example if boot is mtd3 on P500 do dd if=/dev/mtd/mtd3 of=/sdcard/boot-dump.img bs=4096
then type
Code:
cd /system
tar zcvf /sdcard/system-dump.tar.gz *
dd if=/dev/mtd/mtd1 of=/sdcard/boot-dump.img bs=4096
dd if=/dev/mtd/mtd0 of=/sdcard/recovery-dump.img bs=4096
Please someone upload these 3 files from p500:
system-dump.tar.gz
boot-dump.img
recovery-dump.img
Thanks again.
Also, in case anyone is worried there is no personal user data in /system thats all in the /data partition.
I agree we need a Optimus One P500 forum.
IMHO it's one of the most interesting middle class Android phones: better screen resolution than HTC Wildfire or Samsung Galaxy 3. An alternative to HTC Aria/Gratia
I have rooted my P500 and i have found this :
cat proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
but when i tried to TAR files the system told me
tar: not found
I have WIN XP Pro and maybe TAR is for linux or i'm wrong in something ...
if you could help me we can make it.
bye and sorry for my english.
Get busybox for phone and do it on phone with terminal eumulator. Optionally do adb pull of your entire system folder and zip it up if all else fails. Need boot and recovery too.
I'd like a section for Optimus One ...
Have someone installed Flash Lite for default browser?
Ok I just downloaded a dump thanks fughy. I am looking at pics and don't see a navigational pad. Can someone confirm it has one or it not & what it uses other than touch screen for navigation as thats needed for recovery. Please list all hardware buttons/keys also please.
I have a custom amon ra recovery that needs to be tested. Please PM if interested. Md5 is below to check against after download.
MD5sum b15d0d4a6588b28b58ee16cf9470ab5f recovery-thunderg_test.img
drellisdee said:
Ok I just downloaded a dump thanks fughy. I am looking at pics and don't see a navigational pad. Can someone confirm it has one or it not & what it uses other than touch screen for navigation as thats needed for recovery. Please list all hardware buttons/keys also please.
I have a custom amon ra recovery that needs to be tested. Please PM if interested. Md5 is below to check against after download.
MD5sum b15d0d4a6588b28b58ee16cf9470ab5f recovery-thunderg_test.img
Click to expand...
Click to collapse
The P500 has no touchpad or something else for navigation. The only keys are:
- Power button on top
- Volume Up/Down on right side
- Menu, Home, Back, Search on front
I would love to create my own custom rom for this device but I'm quite new to this. Is there somewhere a good tutorial on how to create a custom rom based on an original rom?
This LG Optimus is the number ONE
As promised here is a beta amon ra style recovery for opt1 thunderg.
Its untested as I don't have one to test it on.
Key mapping is up/down = vol-up and vol-down
select = power
backup = search
If the keys aren't right use the key code debugger under "other" menu and give me the key code outputs.
Fastboot IF enabled on optimus one can be accessed by "adb reboot bootloader".
The best way to test this if you have fastboot is to do
Code:
fastboot boot recovery-thunderg_test1.img
if done this way it will boot from ram and will be lost upon reboot. IE. its temporary if it needs some changes instead of actually flashing it.
If you need help setting up fastboot/adb drivers reference my post here for the Lg Ally
http://androidforums.com/ally-all-things-root/146564-ally-recovery-img-here-custom-roms.html
It should either be 618e or 618f for adb.
If you don't have fastboot on device this will flash it:
Do this from a su (root) adb shell (preferred) or terminal on phone after you have copied recovery-thunderg_test1.img & flash_image to root of your sdcard. Flash_image is attached to the post linked above.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-thunderg_test1.img
Also if you have a file named install-recovery.sh in system/etc you will need to rename it to install-recovery.sh.bak prior to flashing a recovery.
Download at:
http://www.mediafire.com/file/atz2309jc5d5zqc/recovery-thunderg_test1.img
MD5 = 954c6249e400c0b779b8f47cdb79d87c
This HOWTO is only useful for people who have NOT yet installed a stock recovery or who have lost the custom recovery after KDZ or LGMDP flash.
Why I posted it? Since I have had enough of complaints about screwed phones via ROM Manager, also there is some broken rf.sh script I have heard of.
Step 1:
- Download (see attachment) the flash_image.zip
- unzip it
- and put the flash_image binary on the root of your SD card (via USB cable).
Step 2:
- Dowload a recovery of your choice (CWM or AmonRA) from this thread.
- Unzip it on your local box and find the recovery.img file.
- Put the recovery.img to the root of your SD Card (via USB cable)
Step 3a - via terminal emulator
- Run terminal emulator on your phone (download one from market if you do not have it yet, duh!)
- type these command exactly: $ denotes a normal user, # denotes root. This character should NOT be typed into terminal emulator!
Code:
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
or
Step 3b:
- Install Android SDK (EXE installer recommended for Windows users.)
- run command prompt (cmd.exe) on your Windows box, or run the following from shell on your Linux box:
Code:
> adb shell
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# exit
$ exit
> adb reboot recovery
Step 4:
Now you should find yourself in your shiny new custom recovery. Do whatever you need there.
Q: Is not there an easier way? This seems like a lot of typing? It sucks - I have heard about ROM Manager!
A: ROM Manager's way of flashing recovery is broken by design. Do NOT use it unless you are comfortable with rescuing your phone via ADB/fastboot like many people before.
Q: I already have custom recovery. Do I need to do this if I want to switch from CWM to AmonRA or vice versa?
A: No. This thread has recovery ZIPs when can be flashed from recovery itself.
Q: HELP!!! I screwed and now my phone is stuck in fastboot mode! What should I do?!?!
A: You are officially lame, very lame person. Now go here to fix it.
Q: But my phone is not rooted (no su binary) - the above does not work! I tried to root it via z4root, GingerBreak, SuperOneClick but everything failed! What should I do? Am I stuck with stock ROM?
A: No! See the LGMDP method below.
Nice guide
This way newbies won't be confused where to search.
BTW, a little mistake: in the adb codes it's flash_image recovery /sdcard/recovery.img
Alternative method: Flashing custom recovery via LGMDP.exe
Tried to root it via z4root, GingerBreak, SuperOneClick but everything failed? No problem! Flash the recovery via LGMDP.
Step 1:
Download P500-CWM-3.1.0.0.zip (CWM 3.1.0.0 included, if you want something else, replace recovery.img with whatever you want) and unzip it.
Step 2:
- Browse to the folder where you unpacked the ZIP and run LGMDP-v1.5.exe
- Click Download in menu
- Select Port
- Choose your phone, click Connect
- Click Image Folder button, browse to the directory where you unpacked this
- Click OK about 3 times on the warnings
- Close the window
- Click Download button
- Let it do the job. It will backup your IMEI and MACs to .NV2 file, reboot your phone, flash recovery and restore the NV2 backup. Do NOT interrupt it or disconnect your phone until it says "Download complete"! Do NOT delete the NV2 backup!
Step 3:
Done! Now when you press Home + Volume Down + Power, you should find yourself in your shiny new custom recovery. Now you can flash a rooted ROM via flash zip menu.
Q: I am a moron and have interrupted the process. Now I get a black screen with some weird fastboot text, what to do? HELP!!!!
A: Yes, you are a moron. See [HOWTO] Revive a bricked P500 on fastboot mode (the SHORT way) thread.
Q: Can I just quickly root my stock ROM after flashing recovery? I do not want a custom ROM.
A: Yes. Download su-2.3.6.3-efgh-signed.zip and flash it from recovery. Reboot, download Busybox Installer from the market, run and install busybox on your phone.
--- reserved ---
Thx doktor, it helps some of my friend who lost their recovery while upgrading to official GB...
+1
Nice one man, really useful and funny text.
Yo,added this to the N00B repo.
"Q: Can I just quickly root my stock ROM after flashing recovery? I do not want a custom ROM.
A: Yes. Download su-2.3.6.3-efgh-signed.zip and flash it from recovery. Reboot, download Busybox Installer from the market, run and install busybox on your phone."
In reference to the above words, cud i use this as a method to root my stock GB 2.3.3??? cos nothing else seems to root it and installing sdk and adb and all tat, seems too complex!
Of course.
nice guide TS
but this guide also can use for thunderg recovery right ???
and i not quite understanding ur step 3a
which is this :
type these command exactly: $ denotes a normal user, # denotes root. This character should NOT be typed into terminal emulator!
Click to expand...
Click to collapse
but in my mind just type EXACTLY what the below quote write
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
Click to expand...
Click to collapse
but you say the things in 1st post make me confuse
so just follow and type the word exactly ???
No comment, everything I wanted to say has been censored
get what you meaning already
When I type
flash_image recovery /sdcard/recovery.img
I take the error message
mtd: not writing bad block at 0x00440000
error writing recovery : No space left on device
But I have at least 60MB on my phone's memory...
edit:
OK,that error bricked my phone again...
evripidis said:
error writing recovery : No space left on device
But I have at least 60MB on my phone's memory...
Click to expand...
Click to collapse
Has nothing to do with the space for /recovery on a separate partition.
evripidis said:
edit:
OK,that error bricked my phone again...
Click to expand...
Click to collapse
Congrats.
doktornotor said:
Has nothing to do with the space for /recovery on a separate partition.
Click to expand...
Click to collapse
KDZ is always saving me always!
How can I fix that about /recovery?
Because I don't understand, I don't have a partition for recovery?
If is that, why after KDZ update, original recovery works properly?
I am worried about bad block that error message said...
evripidis said:
I am worried about bad block that error message said...
Click to expand...
Click to collapse
Yeah, am I worried too, should not report any bad sectors (at least not on this phone).
Code:
> adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
I get this
Code:
>adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
In google I found this http://android.modaco.com/content-p...kmod-recovery-for-zte-blade-oled-tft/page/20/
He gets the error at the same point.
And this http://androidforums.com/647576-post25.html
I did everything as I was meant to, but when I get to the point to insert the text, both on pc or on phone I get an error message...What's wrong?
celtic-paolino said:
I did everything as I was meant to, but when I get to the point to insert the text, both on pc or on phone I get an error message...What's wrong?
Click to expand...
Click to collapse
Eh... Insert what text? Where? What error message?
When I have to write the codes in the terminal emulator or in cmd.exe, I get these messages:
TE: su: permission denied
and the rest doesn't obviously work
CMD: doesn't work at all even if I installed the program you said...
I was wondering if anyone had a file for the Amaze to go in the edify_defs folder in the kitchen. Or if someone could help me finishing filling it out.
Thanks!
Code:
#
# The values below should be set in each file in this folder.
#
# Each file represents a device name (set in ro.product.device of
# build.prop)
#
# If yes, then this device requires changing the mount point
# names in the new updater-script or update-script
# DO NOT SET TO 'yes' IF DEVICE IS BY DELL
change_mnt=yes
# If yes, the device is by Dell and requires changing the mount
# point names in the new updater-script or update-script
change_mnt_dell=no
#
# NOTE: The update-script will be converted to updater-script if the
# definition file for the device exists. If 'change_mnt' or
# 'change_mnt_dell' are set to 'yes' then the mount names will
# also be changed.
#
# Mention the mount point names if change_mnt=yes
# Use '\/' instead of '/'
# e.g. sys_mnt=\/dev\/block\/mcblk0p25
#
# If unknown, set to: ???
sys_mnt=\/dev\/block\/mmcblk0p29
cache_mnt=\/dev\/block\/mmcblk0p30
boot_mnt=\/dev\/block\/mmcblk0p22
data_mnt=???
sdcard_mnt=???
# Set this mount point for the modem.bin in Samsung devices like the Galaxy S2
modem_mnt=
# Set this mount point if you know what it is (e.g. on Motorola Atrix)
webtop_mnt=
# Filesystem info for SYSTEM/DATA/CACHE/etc.
# e.g. param1=ext3, param2=EMMC
param1=
param2=
# If SDCARD filesystem is different from above, then mention it
# e.g. param1_sdcard=vfat, param2_sdcard=MTD
param1_sdcard=
param2_sdcard=
# If CACHE filesystem is different from above, then mention it
param1_cache=
param2_cache=
# If yes, the device does not require using a 'tmp' folder when
# flashing the boot.img in the updater-script
#
# e.g. package_extract_file("boot.img", "/dev/block/blah1");
fix_boot=no
# If yes, the device requires a 'tmp' folder when flashing the
# boot.img in the updater-script, PLUS the boot partition name
# needs to be used, rather than just 'boot'
#
# e.g. Replace: write_raw_image("/tmp/boot.img", "boot")
# with: write_raw_image("/tmp/boot.img", "/dev/block/blah1")
fix_boot2=no
# If yes, the device requires a 'dd' command to write the boot.img
#
# e.g. Replace: write_raw_image("/tmp/boot.img", "boot")
# with: run_program("/sbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/blah")
fix_boot3=no
# Device uses /cache instead of /tmp, e.g. when writing boot.img
use_cache_not_tmp=no
This should help.
Cayniarb said:
These are the partition mounts on the Amaze 4G:
Code:
dev: size erasesize name
mmcblk0p24: 00fff600 00000200 "misc"
mmcblk0p23: 00fffc00 00000200 "recovery"
mmcblk0p22: 01000000 00000200 "boot"
mmcblk0p29: 5ffffc00 00000200 "system"
mmcblk0p30: 13fffe00 00000200 "cache"
mmcblk0p31: 9ffffe00 00000200 "userdata"
mmcblk0p32: 01fba800 00000200 "devlog"
mmcblk0p34: 00040000 00000200 "pdata"
mmcblk0p17: 02800000 00000200 "radio"
mmcblk0p21: 02000000 00000200 "adsp"
mmcblk0p19: 007ffc00 00000200 "radio_config"
mmcblk0p25: 00400000 00000200 "modem_st1"
mmcblk0p26: 00400000 00000200 "modem_st2"
mmcblk0p18: 02800000 00000200 "mdm9k"
mmcblk0p20: 007ffa00 00000200 "mdm9k_config"
mmcblk0p27: 00400000 00000200 "mdm_efs1"
mmcblk0p28: 00400000 00000200 "mdm_efs2"
Click to expand...
Click to collapse
Thanks, I got that far. I need everything after the mount points lol
Draciel882 said:
Thanks, I got that far. I need everything after the mount points lol
Click to expand...
Click to collapse
Try taking a file specifically for a similar device (one with two storage mounts) and simply edit it to match the specifications for the Amaze. That's what I did. Sorry but I don't have it anymore.
Binary100100 said:
Try taking a file specifically for a similar device (one with two storage mounts) and simply edit it to match the specifications for the Amaze. That's what I did. Sorry but I don't have it anymore.
Click to expand...
Click to collapse
Thanks anyways haha I was hoping someone would provide me with the file they used.
Sent from my Bulletproof Amaze 4G from xda premium
I've filled in everything I can from what you posted and what I cross referenced from the HTC Flyer file and this is the result of unpacking the rom:
Code:
Creating working folder WORKING_AMAZE_TEST1 ...
Extracting ROM ...
Renaming ...
boot_signed.img -> boot.img
Found system.img
Found boot.img
adsp.img
dzdata_16g.hdr
dzdata_16g.img
dzdata_4g.hdr
dzdata_4g.img
hboot_8x60-lte_1.90.0008_20111101_signedbyaa.nb0
mdm9k.img
mdmrcdata.img
nfc_106.img
pg2fs_spcustom.img
ramdisk.img
rpm.img
sbl1.img
sbl2.img
sbl3.img
tz.img
Adding an update-script ...
od: illegal option -- -
usage: od [-aBbcDdeFfHhIiLlOosvXx] [-A base] [-j skip] [-N length] [-t type]
[[+]offset[.][Bb]] [file ...]
NON-YAFFS/NON-TAR FILE FORMAT DETECTED IN ROM
Fuse installed
Trying to mount the filesystem
dyld: Library not loaded: /usr/local/lib/libfuse.2.dylib
Referenced from: /usr/local/bin/fuse-ext2
Reason: image not found
Filesystem mounted
File system listed, analyzing
Failed to mount the filesystem: mount point empty
Error: No /system/framework folder found!
Press Enter to continue
Anyone?
mount points
Did you figure this out, if so could you send me the template of yours
Umm out of curiosity, what are working on here?
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk
DEFINITIONOFREAL said:
Did you figure this out, if so could you send me the template of yours
Click to expand...
Click to collapse
My problem was because I was in OSX. But I moved to Ubuntu and everything worked like a charm.
Sent from my Bulletproof HTC Amaze 4G
Did anyone create the template? If so, can I have it lol? I tried changing it using what Binary gave but i can't find it for data and sdcard
Please keep all question based threads in the Q&A section.
Thread Moved.
Sent from my Galaxy Note i717, using XDA Premium.
You don't have to be a farmer to know what sh*t smells like.
Hi, I have unlocked the bootloader and had used CWM (recoveryNeo.img). Too bad it is a one-time boot. I was thinking is there a recovery partition.
Code:
# cat /proc/mtd/
dev: size erasesize name
mtd0: 19000000 00020000 "system"
mtd1: 00600000 00020000 "appslog"
mtd2: 06580000 00020000 "cache"
mtd3: 1a400000 00020000 "userdata"
So is there a way to install CWM other than to the system partition? Or I would need to do a fastboot every time I need it?
Mine is a Neo V, but doesn't matter
Use flashtool. Flash kernel boot.img with build-in CWM. Try NightElf kernel.
Try to install this CWM install.RAR
Hey!
Try NightElf's kernel it haves built in cwm
Just put boot.img (boot.img = kernel you downlaoded) into fastboot folder and hold shift and rightclick and "open... here" on command prompt type "fastboot flash boot boot.img" and you have permanent cwm
Hi, I'm working on creating a custom CWM Flashable ROM (zopo zp900).
I'm making a updater script, but I'm having trouble finding all the partitions for my phone, especially the /boot partition.
See the quote down there, that's what I'm trying to achieve except for my device.
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 0087f400 00000200 "recovery"
mmcblk0p22: 00400000 00000200 "boot"
mmcblk0p25: 22dffe00 00000200 "system"
mmcblk0p29: 09800000 00000200 "lib"
mmcblk0p27: 090efc00 00000200 "cache"
mmcblk0p26: 496ffe00 00000200 "userdata"
mmcblk0p30: 014bfe00 00000200 "devlog"
mmcblk0p31: 00040000 00000200 "pdata"
mmcblk0p28: 00010000 00000200 "extra"
Click to expand...
Click to collapse
Many THANKS!
tehPanda said:
Hi, I'm working on creating a custom CWM Flashable ROM (zopo zp900).
I'm making a updater script, but I'm having trouble finding all the partitions for my phone, especially the /boot partition.
See the quote down there, that's what I'm trying to achieve except for my device.
Many THANKS!
Click to expand...
Click to collapse
The boot partition may not be visible to the Linux kernel.
$ cat /proc/mtd
$ ls -l /dev/block
$ mount
Also, have a look in /init.*rc for mount points and run "dmesg" on your newly booted device. The device may be of type mtd or mmc and they are treated quite differently.